registry team mailing list archive

["Michael K. Edwards" <m.k.edwards@xxxxxxxxx>]

I hacked a bit on debootstrap to teach it about lucid-proposed, and can
confirm that this updated tar resolves the inability to debootstrap
lucid on an old kernel (in this case, the 2.6.18 variant shipped with
RHEL5.4).  Thanks for following up and driving this to closure; I was
not looking forward to backporting enough current packages to lenny to
run the LAMP stack app I need.  (RHEL was of course not even an option,
userland-wise; but as long as I leave it on there as the boot
environment, I don't have to deal with the hardware.)

The debootstrap hack I did was pretty gross, and doesn't know about
lucid-updates or lucid-security.  Assuming this version of tar makes it
out of lucid-proposed, will it go to lucid or lucid-updates?  If the
latter, it won't do people a lot of good unless there's a better way
than my hack to get debootstrap to use -updates right out the chute.  Is
there another debootstrap floating around that does know how to compress
the "debootstrap, update sources.list, apt-get update, apt-get dist-
upgrade" sequence down to a single pass?

-- 
tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels < 2.6.22
https://bugs.launchpad.net/bugs/539814
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.