Package: mpg321
Version: 0.2.10.3

Files are installed by mpg321 which allow it to be run as mpg123 as well. These
files are not known by the package system. For example:

[EMAIL PROTECTED]:~# dpkg -s mpg123
Package: mpg123
Status: purge ok not-installed
[...]
[EMAIL PROTECTED]:~# ls /usr/bin/mpg123
ls: /usr/bin/mpg123: No such file or directory
[EMAIL PROTECTED]:~# apt-get --reinstall install mpg321
[...]
[EMAIL PROTECTED]:~# ls /usr/bin/mpg123
/usr/bin/mpg123
[EMAIL PROTECTED]:~# dpkg -S mpg123
dpkg: *mpg123* not found.

I'm not sure this is really a bug, but my expectation was that the "dpkg -S"
command would list mpg321 as the owner of the "*mpg123*" files.

I'm using Debian GNU/Linux unstable with self-compiled kernel 2.6.13.2 and libc6
 2.3.5-4.

Andrei

-- 
[EMAIL PROTECTED] # http://movzx.net # jabber:[EMAIL PROTECTED]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to