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

[Steve Langasek]

Oh bah.  Turns out this failed because my patch only set the uname for
the dynamically-linked qemu-user builds, not the static ones that we're
using. :/  Attached is a slightly better (i.e., working) patch.

** Patch added: "qemu-linaro-921078.patch"
   https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/921078/+attachment/2763817/+files/qemu-linaro-921078.patch

-- 
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