registry team mailing list archive

[Keith Ward <539814@xxxxxxxxxxxxxxxxxx>]

Firstly, apologies to anyone if the following comment comes across as
confrontational, but this bug has gone on far too long.

I've gone ahead Subscribed SRU to this bug, as it is urgent, due to the
fact it prevents any system with a kernel older than 2.6.22 from
bootstrapping lucid - (which means it applies to dapper), as tar simply
fails due to the previously mentioned utime errors.

I'm surprised this hasn't been patched already especially as it was
previously mentioned that debian patched it a long long time ago. I'm
even more surprised that Lucid was released without this being fixed -
especially as the patch has been available since at least march!

Just to clarify this bug prevents any type of bootstrapping from Dapper
or running of tar on any kernel < 2.6.22, (this means you can't
debootstrap lucid on the majority of Xen Hosts, as they run kernel
2.6.18!

While I agree that it is not possible to support every kernel known to
man, due to the fact this this applies to more than just dapper - there
are a lot of hosts running .18 kernels, for various reasons: mostly xen
hosts, and the fact a patch has been available since the beginning half
of the year, and has been fixed in *both* Debian and fedora, just makes
the whole situation we are now in, completely unbelievable.

The resolution to this problem is to either use the patch I attached a
few months ago from the debian bug, and push that for an SRU (It fixes
this bug, and only this bug). Or to push the package from maverick into
lucid as an SRU (this bug according to the debian information at debbugs
is fixed in version 1.23-1).

As to which option is preferred i shall leave up to the developers,
personally if we're updating the package again, it may be an idea to
push over the version from maverick as opposed to just creating a new
-rev for 1.22.

Regards,

-- 
tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM)
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.