Your message dated Tue, 30 Sep 2008 21:41:30 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#495359: perl is in an unusable state during
etch->lenny dist-upgrade and breaks the upgrade process
has caused the Debian Bug report #495359,
regarding perl is in an unusable state during etch->lenny dist-upgrade and
breaks the upgrade process
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.)
--
495359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495359
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: perl is in an unusable state during etch->lenny dist-upgrade and
breaks the upgrade process
Package: perl
Version: 5.10.0-13
Severity: critical
Justification: breaks unrelated software
Scenario:
- etch system with latest security updates (August 16th 2008)
- replaced etch by lenny in /etc/apt/sources.list
- first run successfully
aptitude install dpkg aptitude
(as stated in http://www.mail-archive.com/[EMAIL PROTECTED]/msg11612.html)
- now the real thing: aptitude dist-upgrade
after installing and unpacking a lot of stuff, maintainer scripts start
to fail with messages like:
Can't locate File/Copy.pm in @INC (@INC contains: /home/glaweh/bin/perl5
/etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /u
BEGIN failed--compilation aborted at /usr/bin/defoma-app line 7.
dpkg: error processing gs-common (--remove):
subprocess pre-removal script returned error exit status 2
Errors were encountered while processing:
gs-common
State of the perl packages at this time:
n033:/# dpkg -l perl perl-base perl-modules
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version
+++-=============-============
iU perl 5.10.0-11.1
ii perl-base 5.8.8-7etch3
iU perl-modules 5.10.0-11.1
and the whole upgrade-process stops.
I think I encountered the same bug already in previous debian
releases and proposed at that time to make one of the depedencies in the perl
dependency loop a pre-depends instead... this worked for me at that time.
an easier solution may be to merge all three packages into 1 package to avoid
inconsistencies completely.
The impact on the mirror network is neglegible, it would add 3.2M per
architecture, the size of the only arch:all package perl-modules.
I have a backup of the etch system, so in case you want me to check for
something specific i can reproduce this in a chroot.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages perl depends on:
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libdb4.6 4.6.21-8 Berkeley v4.6 Database Libraries [
ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime
ii perl-base 5.10.0-13 minimal Perl system
ii perl-modules 5.10.0-13 Core Perl modules
Versions of packages perl recommends:
ii netbase 4.32 Basic TCP/IP networking system
ii perl-doc 5.10.0-11.1 Perl documentation
Versions of packages perl suggests:
ii libterm-readline-gnu-perl 1.17a-2+b1 Perl extension for the GNU Readlin
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Sep 30, 2008 at 04:42:26PM +0200, Henning Glawe wrote:
> On Mon, Sep 22, 2008 at 09:47:56PM +0300, Niko Tyni wrote:
> > On Tue, Aug 19, 2008 at 11:12:12PM +0300, Niko Tyni wrote:
> > It's been a month now with no update to this bug. I assume the above
> > is correct and debsums does not have an upgrade problem of its own.
> >
> > There's now a fixed gs-common package in lenny, so I'll close this in
> > a few days as well unless convinced otherwise.
>
> I think you can close it safely; I redid the upgrade last night (had too much
> to do before job-wise), and did not observe any problems due to perl version
> mismatches.
Thanks, closing.
--
Niko Tyni [EMAIL PROTECTED]
--- End Message ---
