Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#345020: cdrecord: Overly(?) strict permissions on /usr/bin/readcd: reportbug
fails,
which was filed against the cdrecord package.
It has been closed by one of the developers, namely
Eduard Bloch <[EMAIL PROTECTED]>.
Their explanation is attached below. If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
------------------------------------------------------------------------
Subject:
Re: cdrecord: Overly(?) strict permissions on /usr/bin/readcd: reportbug
fails
From:
Eduard Bloch <[EMAIL PROTECTED]>
Date:
Tue, 21 Mar 2006 01:11:14 +0100
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
#include <hallo.h>
* Greg Kochanski [Wed, Dec 28 2005, 02:35:03PM]:
Package: cdrecord
Version: 4:2.01+01a03-4
Severity: minor
The file permissions on /usr/bin/readcd are overly strict: one cannot
even read the file unless superuser. This causes reportbug
to complain. (And if you run reportbug as superuser, it correctly
complains about *that*.)
$ ls -l /usr/bin/readcd
-rws--x--- 1 root cdrom 145172 Dec 4 02:13 /usr/bin/readcd
Our scripts don't do that. I guess you have configured a
dpkg-statoverride hook in ancient times where it was "recommended" way.
Did you upgrade from pre-Sarge to Sid? Any way, check and fix with
dpkg-statoverride or find the program changing your permissions.
Eduard.
That may have been it. Up until a recent re-install, I had been
running an up-up-up-graded Debian for upwards of 4 years.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
