[Bug 921078] Re: FATAL: kernel too old ← how old is too old?

Steve Langasek steve.langasek at canonical.com
Mon Feb 20 17:40:21 UTC 2012


Ok, so the build log certainly shows the option being picked up but it
sure isn't helping uname.  Will dig deeper here.

> The continued failure could simply be because the current ARM chroots
> aren't up-to-date with the more recently-relaxed libc6,

No, the uname output shows that the qemu change is ineffective.  Also,
we haven't made any changes to libc6 to relax the version check,
*because* it shouldn't be needed if qemu is DTRT.

> Also, Steve's comment above that "The precise eglibc on amd64 and armel
> has 2.6.24 as a minimum kernel version" is demonstrably false.

Sorry, I meant "amd64 and i386", not "amd64 and armel".  Apparently
armel has completely supplanted i386 in my mind.

> Other than "newer is better", has anyone actually made a cogent argument
> for why we want our non-x86 ports to have a higher MIN_KERNEL_SUPPORTED
> than amd64 and i386 do?

I'll leave that to Matthias.  But the 2.6.24 is actually the exception
rather than the rule here: amd64 and i386 have a lower compat level than
Debian and the other Ubuntu archs to support the hardy build chroots in
Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/921078

Title:
  FATAL: kernel too old ← how old is too old?

Status in “eglibc” package in Ubuntu:
  Triaged
Status in “qemu-linaro” package in Ubuntu:
  Triaged

Bug description:
  PPA buildds currently run Hardy, because they require Xen for VM
  security.  This means that all builds of precise packages freak out
  because libc6 isn't upgradable in the build deps:

  	Preparing to replace libc6 2.13-24ubuntu2 (using .../libc6_2.13-24ubuntu4_armel.deb) ...
  	Unpacking replacement libc6 ...
  	FATAL: kernel too old
  	dpkg: warning: subprocess old post-removal script returned error exit status 1
  	dpkg - trying script from the new package instead ...
  	FATAL: kernel too old
  	dpkg: error processing /var/cache/apt/archives/libc6_2.13-24ubuntu4_armel.deb (--unpack):
  	 subprocess new post-removal script returned error exit status 1
  	FATAL: kernel too old
  	dpkg: error while cleaning up:
  	 subprocess installed pre-installation script returned error exit status 1
  	Errors were encountered while processing:
  	 /var/cache/apt/archives/libc6_2.13-24ubuntu4_armel.deb
  	E: Sub-process /usr/bin/dpkg returned an error code (1)

  As a result, nothing at all will build.

  How old is too old?  It would be good to list which minimum kernel
  revision to boot into, so we don't end up having to bisect through
  lots of kernels.  We generally have to do a lot of mangling to try and
  make newer ones work with Xen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/921078/+subscriptions




More information about the foundations-bugs mailing list