← Back to team overview

touch-packages team mailing list archive

[Bug 539814] Re: tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels < 2.6.22

 

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: debootstrap (Ubuntu Lucid)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/539814

Title:
  tar: futimens() with a bad file descriptor (AT_FDCWD) causes
  bootstrapping failure with kernels < 2.6.22

Status in Release Notes for Ubuntu:
  Fix Released
Status in debootstrap package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  Fix Released
Status in debootstrap source package in Lucid:
  Won't Fix
Status in tar source package in Lucid:
  Fix Released
Status in tar package in Debian:
  Fix Released
Status in tar package in Fedora:
  Unknown

Bug description:
  Binary package hint: tar

  Bootstrapping Ubuntu Lucid with debootstrap is currently impossible
  with any kernel < 2.6.22, due to a bug in tar - specifically it fails
  because of a change to eglibc.

  According to the debian bug report It seems that before eglibc
  2.10.2-3, calls to futimens failed silently, however due to a patch
  made to eglibc 2.10.2-3, if futimens is called without a valid file
  descriptor, it now fails with an "Bad File Descriptor" error, because
  the corresponding utimensat() syscall was not added until kernel
  2.6.22

  Test Case:
  1) Boot a kernel older than 2.6.22
  2) Attempt to Bootstrap Ubuntu Lucid to any target.
  The bootstrap will fail once it attempts to unpack packages with: tar: ./postinst: Cannot utime: Bad file descriptor

  A patch is available (attached in launchpad) originating from the associated debian bug, that ensures that futimens is only called with a valid file descriptor.
  A debdiff for 1.22-2 ( changing to 1.22-2ubuntu1 ) will be attached shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/539814/+subscriptions