← Back to team overview

kernel-packages team mailing list archive

[Bug 817187] Re: change in readlink() errno in 2.6.39 and later kernels causes FTBFS for packages with older gnulib

 

lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".

** Changed in: libvirt (Ubuntu Lucid)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/817187

Title:
  change in readlink() errno in 2.6.39 and later kernels causes FTBFS
  for packages with older gnulib

Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in libvirt source package in Lucid:
  Won't Fix
Status in linux source package in Lucid:
  Invalid
Status in libvirt source package in Maverick:
  Invalid
Status in linux source package in Maverick:
  Invalid
Status in libvirt source package in Natty:
  Invalid
Status in linux source package in Natty:
  Invalid
Status in libvirt source package in Oneiric:
  Invalid
Status in linux source package in Oneiric:
  Invalid
Status in libvirt source package in Hardy:
  Invalid
Status in linux source package in Hardy:
  Invalid
Status in m4 package in Debian:
  Fix Released

Bug description:
  When building packages in a chroot with gnulib testcases for readlink() on a 2.6.39 (Oneiric or newer) kernel, these packages may FTBFS. This is due to the following:
  http://lists.gnu.org/archive/html/bug-gnulib/2011-03/msg00308.html

  "coreutils' "make check" failed on rawhide due to a kernel change
  in how readlink and readlinkat treat the empty file name.
  Before, they'd fail with ENOENT.  Now, it's EINVAL."

  This was discovered when preparing security updates for libvirt, but
  will affect more than libvirt, (see Debian http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=630902). For libvirt, the patch in the above bug
  can be applied to gnulib/tests/test-areadlink.h to get these building
  again on newer releases. This is SRU-worthy, as libvirt will not build
  once the buildds are running newer kernels. If it is not SRUd before
  the next security update, the security team will do it as part of
  their update process.

  Upstream kernel commit that introduced the change:
  65cfc6722361570bfe255698d9cd4dccaf47570d

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