Your message dated Mon, 7 Jan 2008 22:26:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#374503: dpkg: md5sum doesn't exist upgrading to sid dpkg
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dpkg,coreutils
Version: 1.13.21
Severity: serious
dpkg: xserver-xorg: dependency problems, but removing anyway as you request:
x-window-system-core depends on xserver-xorg.
Removing xserver-xorg ...
/var/lib/dpkg/info/xserver-xorg.prerm: line 909: md5sum: command not found
Unpacking xserver-xorg (from .../xserver-xorg_1%3a7.0.22_all.deb) ...
Server symlink checksum doesn't exist. We need to make it
Re-adding lost server symlink checksum
/var/lib/dpkg/tmp.ci/preinst: line 932: md5sum: command not found
dpkg: error processing /var/cache/apt/archives/xserver-xorg_1%3a7.0.22_all.deb
(--unpack):
subprocess pre-installation script returned error exit status 127
Setting up xserver-xorg (7.0.22) ...
/var/lib/dpkg/info/xserver-xorg.postinst: line 1628: md5sum: command not found
/var/lib/dpkg/info/xserver-xorg.postinst: line 1673: md5sum: command not found
cat: /var/lib/x11/xorg.conf.md5sum: No such file or directory
/var/lib/dpkg/info/xserver-xorg.postinst: line 1697: md5sum: command not found
lrwxrwxrwx 1 root root 6 Apr 10 19:57 /usr/bin/md5sum.textutils -> md5sum
$ apt-cache policy dpkg
dpkg:
Installed: 1.13.21
Candidate: 1.13.21
Version table:
*** 1.13.21 0
10 http://ftp.us.debian.org sid/main Packages
$ apt-cache policy coreutils
coreutils:
Installed: 5.94-1
Candidate: 5.94-1
Version table:
5.96-3 0
10 http://ftp.us.debian.org sid/main Packages
*** 5.94-1 0
See also #315784, #313605.
Reinstalling coreutils (5.94-1) fixes the glitch.
--- End Message ---
--- Begin Message ---
Hi,
On Tue, 2006-06-20 at 13:40:55 -0700, Steve Langasek wrote:
> severity 374503 minor
> thanks
>
> On Tue, Jun 20, 2006 at 08:56:04AM -0400, Justin Pryzby wrote:
> > On Tue, Jun 20, 2006 at 08:47:56AM -0400, Michael Stone wrote:
> > > On Tue, Jun 20, 2006 at 08:12:23AM -0400, Justin Pryzby wrote:
> > > >This is more complicated than that, since it involves at least some of
> > > >"testing", and perhaps even some downgrading.
>
> > > Ok, there's no way I can duplicate or reproduce that. Once you start
> > > downgrading you're moving into "on your own" territory.
> > If this turns out to be the cause, then I think dpkg (I guess) should
> > warn the user about downgrades..
>
> Downgrading has never been supported in Debian, and in the general case
> there's no way to fix a downgrade path for a package after the fact if there
> are bugs. If I were the maintainer I would close this bug, but at the very
> least it shouldn't be listed as RC, so downgrading.
Yep, I agree, thus closing.
regards,
guillem
--- End Message ---
