Atomicparsley package completely broken

Bug #1597933 reported by teo1978 on 2016-06-30
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
atomicparsley (Ubuntu)
Undecided
Unassigned

Bug Description

Run:
sudo apt-get install atomicparsley.

This installs the package without errors.

Expected: should be able to run
 $ atomicparsley

Observed:

$ atomicparsley
atomicparsley: command not found

$ sudo find / -name atomicparsley
[no output]

Either the package silently failed to install, or the executable was not installed in any of the default binary paths (nor a symbolic link was created), or its name is not atomicparsley which would be stupid.

Below is the complete output from installing the package:

$ sudo apt-get install atomicparsley
[sudo] password for teo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libhdb9-heimdal libkdc2-heimdal libntdb1 linux-image-4.2.0-23-generic
  linux-image-4.2.0-25-generic linux-image-4.2.0-27-generic linux-image-4.2.0-30-generic
  linux-image-4.2.0-34-generic linux-image-4.2.0-35-generic linux-image-4.2.0-36-generic
  linux-image-extra-4.2.0-23-generic linux-image-extra-4.2.0-25-generic
  linux-image-extra-4.2.0-27-generic linux-image-extra-4.2.0-30-generic
  linux-image-extra-4.2.0-34-generic linux-image-extra-4.2.0-35-generic
  linux-image-extra-4.2.0-36-generic linux-signed-image-4.2.0-23-generic
  linux-signed-image-4.2.0-25-generic linux-signed-image-4.2.0-27-generic
  linux-signed-image-4.2.0-30-generic linux-signed-image-4.2.0-34-generic
  linux-signed-image-4.2.0-35-generic linux-signed-image-4.2.0-36-generic python-ntdb
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  atomicparsley
0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.
Need to get 118 kB of archives.
After this operation, 307 kB of additional disk space will be used.
Get:1 http://es.archive.ubuntu.com/ubuntu/ wily/universe atomicparsley amd64 0.9.2~svn110-4 [118 kB]
Fetched 118 kB in 0s (334 kB/s)
Selecting previously unselected package atomicparsley.
(Reading database ... 530943 files and directories currently installed.)
Preparing to unpack .../atomicparsley_0.9.2~svn110-4_amd64.deb ...
Unpacking atomicparsley (0.9.2~svn110-4) ...
Setting up atomicparsley (0.9.2~svn110-4) ...

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: atomicparsley 0.9.2~svn110-4
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jun 30 23:53:10 2016
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4.3
 libgcc1 1:5.2.1-22ubuntu2
 libstdc++6 5.2.1-22ubuntu2
 zlib1g 1:1.2.8.dfsg-2ubuntu4
InstallationDate: Installed on 2013-10-11 (993 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: atomicparsley
UpgradeStatus: Upgraded to wily on 2016-01-18 (164 days ago)

teo1978 (teo8976) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in atomicparsley (Ubuntu):
status: New → Confirmed
J G Miller (jgmiller) wrote :

NOT a bug but a misunderstanding.

The original report is in error concerning the name of the executable.

DISTRIB_CODENAME="xenial"
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

# apt-get install atomicparsley
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  atomicparsley
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 114 kB of archives.
After this operation, 299 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe i386 atomicparsley i386 0.9.2~svn110-4 [114 kB]
Fetched 114 kB in 0s (175 kB/s)
Selecting previously unselected package atomicparsley.
(Reading database ... 780436 files and directories currently installed.)
Preparing to unpack .../atomicparsley_0.9.2~svn110-4_i386.deb ...
Unpacking atomicparsley (0.9.2~svn110-4) ...
Setting up atomicparsley (0.9.2~svn110-4) ...

# dpkg -l atomicparsley
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=========================================-=========================-=========================-=======================================================================================
ii atomicparsley 0.9.2~svn110-4 i386 read, parse and set metadata of MPEG-4 and 3gp files

# dpkg -L atomicparsley
/.
/usr
/usr/bin
/usr/bin/AtomicParsley <============= executable in /usr/bin
/usr/share
/usr/share/doc
/usr/share/doc/atomicparsley
/usr/share/doc/atomicparsley/copyright
/usr/share/doc/atomicparsley/changelog.Debian.gz

# ll /usr/bin/AtomicParsley
-rwxr-xr-x 1 root root 256360 2010-10-29 01:39 /usr/bin/AtomicParsley*

The name of the executable is "AtomicParsley" not "atomicparsley".

Perhaps the package installation script could create a convenience symbolic link from the mixed case executable file to an all lower case format could be provided to avoid unecessary trauma for those who expect the executable to be all lower case? However it should be noted that other software which uses AtomicParsley eg "get_iplayer" correctly uses the mixed case named binary.

J G Miller (jgmiller) wrote :

"or its name is not atomicparsley which would be stupid."

Not all executables have all lower case names. Some software authors prefer to give their executables the same mixed case name as the "project name", Xorg as in /usr/bin/Xorg perhaps being the most used binary with an uppercase name.

Ben Johnson (a03-6eo-chg) wrote :

Is there any specific reason for which this has not been marked invalid and closed?

Dylan Aïssi (daissi) on 2019-05-09
Changed in atomicparsley (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers