Bug#687268: perl: breaks debsums during squeeze -> wheezy upgrade

Andres Salomon dilinger at queued.net
Tue Sep 11 12:20:12 UTC 2012


On Tue, 11 Sep 2012 14:03:13 +0300
Niko Tyni <ntyni at debian.org> wrote:

> On Tue, Sep 11, 2012 at 03:19:50AM -0700, Andres Salomon wrote:
> > Package: perl
> > Version: 5.14.2-12
> > Severity: critical
> > 
> > I kicked off an upgrade of a machine running stable (squeeze) to the
> > currently frozen testing (wheezy).  During the upgrade, I hit the
> > following:
> 
> It looks to me more like the upgrade is failing first, then debsums
> is run in the failed state.

I think you're right.  Running 'apt-get -f install' the first time
installed wheezy's perl-base, which allowed debsums to function
properly; however, xserver-xorg-core was still failing to upgrade.  The
second 'apt-get -f install' run fixed the issue.  I've attached the
logs from those two calls.


> 
> > dpkg: error
> > processing /var/cache/apt/archives/xserver-xorg-core_2%3a1.12.3-1_i386.deb
> > (--unpack): installing xserver-xorg-core would break existing
> > software configured to not write apport reports Preparing to
> > replace xserver-xorg-input-synaptics 1.2.2-2
> > (using .../xserver-xorg-input-synaptics_1.6.2-1_i386.deb) ...
> > Unpacking replacement xserver-xorg-input-synaptics ... Processing
> > triggers for man-db ... Errors were encountered while
> > processing: /var/cache/apt/archives/xserver-xorg-core_2%3a1.12.3-1_i386.deb
> > Can't locate File/Find.pm in @INC (@INC
> > contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .)
> > at /usr/bin/debsums line 10. BEGIN failed--compilation aborted
> > at /usr/bin/debsums line 10. E: Problem executing scripts
> > DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ];
> > then /usr/bin/debsums --generate=nocheck
> > -sp /var/cache/apt/archives; fi'
> 
> That said, I suppose it would be nice if debsums would fail more
> gracefully when its dependencies, particularly perl/perl-modules,
> aren't in a configured state.

Indeed, but obviously that's a lower priority bug.

There are 3 issues that I see here, let me know if you disagree:

1) either postinst scripts or debsums should fail gracefully if there's
a problem that's not a failed hash check (severity: wishlist)

2) perl-base should never get out of sync with
perl and perl-modules (severity: normal?)

3) xserver-xorg-core breaks upgrades (severity: critical or grave)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: term2.log
Type: text/x-log
Size: 8919 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20120911/fd213740/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: term3.log
Type: text/x-log
Size: 18027 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20120911/fd213740/attachment-0003.bin>


More information about the Perl-maintainers mailing list