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

Bug#713914: marked as done (squeeze->wheezy: reminder that kernel should be >= 2.6.32 before upgrade)

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #713914,
regarding squeeze->wheezy: reminder that kernel should be >= 2.6.32 before upgrade
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 owner@bugs.debian.org
immediately.)


-- 
713914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713914
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.13-38
Severity: wishlist

When updating Squeeze to Wheezy, I encountered the following error on
two separate machines:

  WARNING: this version of the GNU libc requires kernel version
  2.6.26 or later. Please upgrade your kernel before installing
  glibc.

It would be very helpful to add more information why 2.6.26 is required,
and what would break when using an older kernel.

For example:
- Does this libc not run at all on older kernels (say because of a new
  syscall interface used)?
- is just one specific feature broken (say NSS)?
- will it be much slower because of feature XY?
- etc.

Background on why this would be useful:
One system where I encountered this problem is a work computer running
an old SuSE version (which I can't upgrade for various reasons); I have
a Debian chroot there for when I need newer Linux software. The other
system is a vServer I bought (at hosteurope.com). I have no control over
the kernel used there (currently 2.6.18). Both these systems are
currently in a half-upgraded state until I determine that I can override
this requirement (probably by replacing uname with a script returning fake
information). If that is not possible, I'll have to somehow rollback the
upgrade or restore from backup.

Knowing the reason behind the refusal to install would be very helpful
when determining what to do next.

Side node: I can understand if such old kernels cannot be supported, but
it would be nice to make the failure mode a bit nicer. Currently it is:
update runs half-through, then libc install aborts, and further package
installation is impossible, because libc is not configured, and cannot
be configured, because it would need a newer kernel. apt-get then
refuses to install other packages (e.g. I couldn't install reportbug on
the affected system anymore).

The requirement for a new kernel should also really be mentioned in the
release notes. I read them before upgrading the vServer, and still ended
up with a broken system.

Best regards
Thomas

--- End Message ---
--- Begin Message --- 
Hi,

We are sorry that we were not able to handle your contribution or
suggestion for changes to the release-notes. I am going over old bugs
and I am closing all the items that were suggested for the release-notes
of Debian releases before stretch. On the good side, some even appear to
have been applied, without the bug being closed.

Please don't hesitate to open a new bug if you think your suggestion is
still valuable for the release-notes of buster. If you do that, we'd
appreciate it when you try to summarize the issue properly when the
closed bug was more than a couple of messages.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: