Your message dated Sun, 7 Mar 2010 08:40:02 +0100
with message-id <20100307074002.ga18...@rivendell>
and subject line Re: Bug#562799: /usr/bin/dpkg is installed with 000 permission
has caused the Debian Bug report #562799,
regarding /usr/bin/dpkg is installed with 000 permission
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
562799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562799
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.15.5.5
Severity: grave
Justification: causes non-serious data loss



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dpkg depends on:
ii  coreutils                     8.1-1      GNU core utilities
ii  libc6                         2.10.2-2   GNU C Library: Shared libraries
ii  lzma                          4.43-14    Compression method of 7z format in

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt                           0.7.25     Advanced front-end for dpkg

-- no debconf information

dpkg stopped working after installing this version of the
package. Investigation revealed that /usr/bin/dpkg had permissions
of 000. `chmod 755 /usr/bin/dpkg` fixed the problem.

I have labelled this 'grave' as a non-obvious workaround is needed to
get dpkg working. Obviously, I couldn't use dpkg -i to downgrade!



--- End Message ---
--- Begin Message ---
Hi,

On Mon, 28 Dec 2009, Cameron Horsburgh wrote:
> Thanks for the reply. You're correct---that command gives
> 
> root root 0 /usr/bin/dpkg
> 
> I ran the dpkg-statoverride command and I couldn't reproduce the
> behaviour, so it seems the issue is resolved. Is this a problem
> peculiar to my system, or have I found a real live bug? :-)
> 
> Thanks for your help.

It's unlikely that any official Debian packages installs such an override.
you can try to grep "statoverride" in /var/lib/dpkg/info/* and see if you
find out a culprit but I doubt it.

Closing the bug. File a new one against the right packages if the search
above returns something.

Cheers,
-- 
Raphaƫl Hertzog

Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/
My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/


--- End Message ---

Reply via email to