Bug#629983: [libc6] I also had this on possible upgrade to 2.13-6

June 12th, 2011 - 01:50 pm ET by David Baron | Report spam

Package: libc6
Version: 2.13-4

Please enter the report below this line.
Problem is that, whatever be the offending file, the only alternatives are to
go ahead anyway or abort ALL upgrades. On my system, six packages are pulled
with lib6 upgrades. The mix of new and old will crash out X, for instance.

I got my system going again by downloading testing packages with the live CD
and then downgrading to my system after temporarily preventing x-windows start
up, i.e. kdm.

The new locales and glibc.doc are apparently OK.

A version of this bug was listed as grave and then withdrawn. Since the
partial upgrade will render a (x-window running) unusable, I would upgrade
this bug.

System information.
Architecture: i386
Kernel: Linux 2.6.39-1-686-pae

Debian Release: wheezy/sid
990 unstable www.debian-multimedia.org
990 unstable http.us.debian.org
990 unstable debian.tagancha.org
990 unstable debian.scribus.net
990 unstable debian.pengutronix.de
650 testing security.debian.org
650 testing http.us.debian.org
650 testing dl.google.com
500 stable security.debian.org
500 stable http.us.debian.org
500 stable deb.opera.com
500 karmic ppa.launchpad.net
500 intrepid ppa.launchpad.net
101 experimental-snapshots qt-kde.debian.net
1 experimental debian.co.il

Package information.
Depends (Version) | Installed
==-+-=libc-bin (= 2.13-4) | 2.13-4
libgcc1 | 1:4.6.0-11

Recommends (Version) | Installed
=-+-=libc6-i686 | 2.13-4

Suggests (Version) | Installed
==-+-=glibc-doc | 2.13-6
debconf | 1.5.39
OR debconf-2.0 |
locales | 2.13-6

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/str...">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Courier New'; font-size:8pt; font-weight:400; font-style:normal;">
Package: libc6
Version: 2.13-4
 
 Please enter the report below this line. 
Problem is that, whatever be the offending file, the only alternatives are to go ahead anyway or abort ALL upgrades. On my system, six packages are pulled with lib6 upgrades. The mix of new and old will crash out X, for instance.
 
I got my system going again by downloading testing packages with the live CD and then downgrading to my system after temporarily preventing x-windows start up, i.e. kdm.
 
The new locales and glibc.doc are apparently OK.
 
A version of this bug was listed as grave and then withdrawn. Since the partial upgrade will render a (x-window running) unusable, I would upgrade this bug.
 
 System information. 
Architecture: i386
Kernel: Linux 2.6.39-1-686-pae
 
Debian Release: wheezy/sid
 990 unstable www.debian-multimedia.org 
 990 unstable http.us.debian.org 
 990 unstable debian.tagancha.org 
 990 unstable debian.scribus.net 
 990 unstable debian.pengutronix.de 
 650 testing security.debian.org 
 650 testing http.us.debian.org 
 650 testing dl.google.com 
 500 stable security.debian.org 
 500 stable http.us.debian.org 
 500 stable deb.opera.com 
 500 karmic ppa.launchpad.net 
 500 intrepid ppa.launchpad.net 
 101 experimental-snapshots qt-kde.debian.net 
 1 experimental debian.co.il 
 
 Package information. 
Depends (Version) | Installed
==-+-==
libc-bin (= 2.13-4) | 2.13-4
libgcc1 | 1:4.6.0-11
 
 
Recommends (Version) | Installed
=-+-==
libc6-i686 | 2.13-4
 
 
Suggests (Version) | Installed
==-+-==
glibc-doc | 2.13-6
debconf | 1.5.39
 OR debconf-2.0 | 
locales | 2.13-6
 
 
 
 
 </body></html>

To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Follow the discussion Replies

1 reply

Make a reply

Replies

#1 Jonathan Nieder

June 12th, 2011 - 04:40 pm ET | Report spam

Hi,

Thanks for following up.

David Baron wrote:

[Subject: Re: Bug#629983: [libc6] I also had this on possible upgrade to 2.13-6]

Please keep in mind that these show up as emails, so the subject line
is a good place to put a message in context.

Problem is that, whatever be the offending file, the only alternatives are to
go ahead anyway or abort ALL upgrades.

This bug report is about a situation in which libc6.preinst cancels
the upgrade because there are files around that would interfere with
it. (Some of the possible situations in which it can trigger have
been tracked down and will be corrected automatically in the next
upload.) In particular, it was about the lack of clarity in the error
message, such that it seemed to imply one fix, renaming to add a .old
suffix, would work when it didn't.

As far as I can tell, you are talking about something else. The usual
dpkg behavior (as described in the Debian policy manual) after
"preinst upgrade" fails is for the old "postinst abort-upgrade" will
be called and the upgrade of this package to be cancelled. Then the
higher-level package manager takes over and has a chance to finish
unwinding the upgrade and put things in a sane state.

Do I understand correctly that you are saying that last step didn't
proceed to your satisfaction? (For example, maybe it downgraded too
many packages, or maybe it didn't downgrade enough.)

On my system, six packages are pulled
with lib6 upgrades. The mix of new and old will crash out X, for instance.

I've never heard of this behavior. Please file a new bug.

A version of this bug was listed as grave and then withdrawn.

Probably you are referring to Bug#629534 of 2.13-5, which was fixed (not
withdrawn :)) in 2.13-6 by adding the preinst check.

Hope that helps,
Jonathan

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Follow the discussion Replies

Reply to this message

Create a new topic Replies

Make a reply

Make your own search

Bug#629983: [libc6] I also had this on possible upgrade to 2.13-6

Similar topics

Replies