Bug#296077: marked as done (upgrade-reports: Upgrade from Woody to Sarge: System hosed)
Your message dated Tue, 17 May 2005 19:20:18 +1000
with message-id <1007a32a0505170220427eb58a@mail.gmail.com>
and subject line Closed
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Feb 2005 02:23:14 +0000
>From debian-bugs@rolf.leggewie.biz Sat Feb 19 18:23:13 2005
Return-path: <debian-bugs@rolf.leggewie.biz>
Received: from postman2.arcor-online.net (postman.arcor.de) [151.189.20.157]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2gkb-0000A6-00; Sat, 19 Feb 2005 18:23:13 -0800
Received: from [127.0.0.1] (G0e02.g.pppool.de [80.185.14.2])
(authenticated bits=0)
by postman.arcor.de (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id j1K2NANM007777;
Sun, 20 Feb 2005 03:23:11 +0100 (MET)
Message-Id: <200502200223.j1K2NANM007777@postman.arcor.de>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Rolf Leggewie <debian-bugs@rolf.leggewie.biz>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: upgrade-reports: Upgrade from Woody to Sarge: System hosed
X-Mailer: reportbug 3.2
Date: Sun, 20 Feb 2005 03:23:09 +0100
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: upgrade-reports
Version: woody -> sarge
Severity: critical
Justification: breaks the whole system
Hi,
about a week ago I took the plunge and upgraded one of my machines from
Woody to Sarge. Apart from the official packages I also had some
packages from backports or compiled from source. After replacing woody
in sources.list with sarge, I did an apt-get upgdate and after that an
apt-get dist-upgrade. As expected quite a number of packages were
scheduled for being upgraded. What was a bit unexpected was that there
were also a large number of packages scheduled for removal. I aborted
to make a backup of /etc/ and to direct the output of apt-get into a
file so that I would be able to install later on the packages that had
been removed. This way, I thought, everything would go smoothly.
Unfortunately, that was not the case. The upgrade ended half-way
through telling me that there was an undefined symbol Perl_gthr_key_ptr.
Going from there I found out with Google's help that there had
previously been similar bugs classified when dist-upgrading from woody
to sarge (278417, 278495 and 279232, possibly others, apparently there
is no way search to search for a string in bug reports present in the
BTS system). These were classified as RC.
Apparently the abortion of the upgrade is due to the fact that perl is
in an inconsistent state out of which the system cannot free itself.
And indeed 'dpkg -l perl*|grep ^i' tells me that perl, perl-modules and
perl-suid are version 5.8.4 -5, installed but unconfigured (iU) and that
perl-base is 5.6.1-8.8 (ii), perl-t k is 800.025-2 (iU) and perlmagick
is 5.4.4.5-1woody (ii). As advised on #debian, I tried via aptitude if
that was able to fix the mess, but quickly found out that it would most
likely only make matters worse. Thus I backed off and have not touched
the system since.
I have the following information still on file and can make it available
on request. I hope you understand that I do not include it yet in this
bug report for reasons of privacy and so as not to flood the BTS.
- tar file of /etc (and /home) before the upgrade
pre-upgrade /var I have unfortunately no copy of
- output of apt-get on what packages to install and which to remove
- output of dpkg -l right after the failed upgrade
- and of course the system itself in its current state
My assumption is that from this it should be possible to somehow
reconstruct what packages were installed at the time I tried the upgrade
and thus analyze what triggered this failure.
Best regards
Rolf Leggewie
-- System Information:
Debian Release: 3.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26.desktop041204
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
---------------------------------------
Received: (at 296077-done) by bugs.debian.org; 17 May 2005 09:20:50 +0000
>From ajdlinux@gmail.com Tue May 17 02:20:50 2005
Return-path: <ajdlinux@gmail.com>
Received: from zproxy.gmail.com [64.233.162.198]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DXyFt-000809-00; Tue, 17 May 2005 02:20:50 -0700
Received: by zproxy.gmail.com with SMTP id 34so1555411nzf
for <296077-done@bugs.debian.org>; Tue, 17 May 2005 02:20:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=DrEf5VXLinOGIHMnhuC7T79gKQ3gOJcmqmgIk6ALvr0zoZiBQPeWlxbYM/ht3EHcm2fS92yD65Efw2qC58+6gv9DitqSA1IkePUauTQCuHapfGnyqy8KU0KW04Wo/bwgNPc2u5Aq+His2lg02DqFCBPO7chyt/UVE+NMTedpaX0=
Received: by 10.36.80.4 with SMTP id d4mr26807nzb;
Tue, 17 May 2005 02:20:18 -0700 (PDT)
Received: by 10.36.57.5 with HTTP; Tue, 17 May 2005 02:20:18 -0700 (PDT)
Message-ID: <1007a32a0505170220427eb58a@mail.gmail.com>
Date: Tue, 17 May 2005 19:20:18 +1000
From: Andrew Donnellan <ajdlinux@gmail.com>
Reply-To: Andrew Donnellan <ajdlinux@gmail.com>
To: 296077-done@bugs.debian.org
Subject: Closed
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Delivered-To: 296077-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.0 required=4.0 tests=BAYES_01,ONEWORD autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
I've closed this because I believe the issues described have been resolved.
Andrew Donnellan
--=20
Heritage Linux Group
http://www.heritagelinux.tk
Reply to: