[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#428655: marked as done (libc6: preinst check makes upgrading old libc6 versions impossible)

Your message dated Wed, 13 Jun 2007 13:17:39 +0200
with message-id <20070613111739.GH21684@artemis.intersec.eu>
and subject line Bug#428655: libc6: preinst check makes upgrading old libc6 versions impossible
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: libc6
Version: 2.3.6.ds1-13
Severity: grave
Justification: renders package unusable

If you currently have an old libc6 version (eg: 2.3.6.ds1-13) & kernel
(eg: 2.4.20-686) installed, then it is impossible to upgrade libc6 or the
kernel.

When you attempt to upgrade libc6, the preinst script complains about
the kernel version being lower than 2.6.1:

=========================
Preparing to replace libc6 2.3.6.ds1-13 (using .../libc6_2.5-9+b1_i386.deb) ...
WARNING: POSIX threads library NPTL requires kernel version
2.6.1 or later. If you use a kernel 2.4, please upgrade it
before installing glibc.
=========================

But when you attempt to upgrade the kernel, at least one of the kernel package
(linux-image-2.6-686) sub-dependencies depends on a more recent version
of libc6 than you currently have installed. This causes apt-get to
attempt to upgrade libc6 before the kernel, and you hit the same error as
above.

Please find a way to enable people with old libc6 & kernel versions to
upgrade cleanly. Perhaps an explicit package dependency to 2.6 so apt-get can
sort out the dependancies.

Or if an automatic clean upgrade is not possible, then please add more info to
libc6's preinst error so admins know how to manually fix the problem.

Maybe admins in this unfortunate situation need need to disable the check
in the libc6 preinst then upgrade the kernel and libc6, then reboot
immediately.

Or they need to first upgrade to the last version of libc6 which
didn't have this check (but which is hopefully new enough for 
the kernel's sub-dependencies) before upgrading the kernel, then
upgrade libc6 afterwards & reboot immediately.

My current work-around is to switch over to stable until this problem is fixed.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux rr002701e001 2.4.20-686 #1 Mon Jan 13 22:22:30 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages libc6 depends on:
ii  tzdata                        2007e-3    Time Zone and Daylight Saving Time

--- End Message ---
--- Begin Message --- 
On Wed, Jun 13, 2007 at 12:07:54PM +0200, David Purdy wrote:
> Package: libc6
> Version: 2.3.6.ds1-13
> Severity: grave
> Justification: renders package unusable
> 
> If you currently have an old libc6 version (eg: 2.3.6.ds1-13) & kernel
> (eg: 2.4.20-686) installed, then it is impossible to upgrade libc6 or the
> kernel.

  Yes it's possible. Users are supposed to have a kernel 2.6 when they
run etch. For user that lived up to here with a 2.4 kernel (wow!) then
the "fix" is to install etch's 2.6 kernel, then to upgrade to
unstable/lenny.

  This is the standard upgrade path, and it will work.


  You have may ways to do that, one is to add etch _and_ sid sources in
your apt/sources.list, and then have a /etc/apt/preferences with:

------8<---------------
Package: *
Pin: release a=stable
Pin-Priority: 990

Package: *
Pin: release a=unstable
Pin-Priority: 200
------>8---------------

  that will make stable your default distribution (stable being etch
right now). Then upgrade your kernel, dependencies and upgrade will
work. After having done that, you can (at your choice) remove the
preferences file, or rewrite it to:


------8<---------------
Package: *
Pin: release a=stable
Pin-Priority: 500

Package: *
Pin: release a=unstable
Pin-Priority: 990
------>8---------------

  If you want to really understand what that does, and why I chose
200/500/990, please read apt_preferences(5).

HAND
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgplYqkMGhvsd.pgp
Description: PGP signature


--- End Message ---
Reply to: