[Bug 539814] Re: 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)
It would have been nice if someone could have at least published a .dev on this. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
I can't even `apt-get source tar` to patch tar, because of a non-working tar. This is a pain in the ass and should have been in the changelogs. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
I have just hit this problem upgrading from hardy 8.04 to lucid 10.04, so you don't need to go back as far as dapper to see it. I now have a partially upgraded system, and a aptitude safe-upgrade gives Preconfiguring packages ... tar: ./postinst: Cannot utime: Bad file descriptor tar: ./preinst: Cannot utime: Bad file descriptor tar: ./prerm: Cannot utime: Bad file descriptor tar: ./postrm: Cannot utime: Bad file descriptor tar: ./conffiles: Cannot utime: Bad file descriptor tar: ./md5sums: Cannot utime: Bad file descriptor tar: ./control: Cannot utime: Bad file descriptor tar: .: Cannot utime: Bad file descriptor tar: Exiting with failure status due to previous errors dpkg-deb: subprocess tar returned error exit status 2 dpkg: error processing /var/cache/apt/archives/bash_4.1-2ubuntu3_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/bash_4.1-2ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Tar version is 1.22-2, and /bin/tar is the same as the binary on another working 10.04.1 system gnulib is not installed - same as on another working 10.04.1 system One difference is that the working system has: ldd `which tar` linux-gate.so.1 = (0x00f66000) librt.so.1 = /lib/tls/i686/cmov/librt.so.1 (0x00574000) libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0x00ad) libpthread.so.0 = /lib/tls/i686/cmov/libpthread.so.0 (0x00665000) /lib/ld-linux.so.2 (0x007b8000) whereas the broken one has: # ldd `which tar` linux-gate.so.1 = (0xe000) librt.so.1 = /lib/librt.so.1 (0xb7fcc000) libc.so.6 = /lib/libc.so.6 (0xb7e83000) libpthread.so.0 = /lib/libpthread.so.0 (0xb7e6b000) /lib/ld-linux.so.2 (0x8000) -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
P.S. both have libc version 2.11.1-0ubuntu7.2 Given the bug, it is hard for me to install libc-i686 on the broken one... Ah: the broken one has a 2.6.17-12-386 kernel! not 2.6.32 - broken one was upgraded by boot into recovery mode with netroot aptitude update aptitude safe-upgrade - utime trouble... -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Please add something about this to the release notes. I've just upgraded a production Linode (Xen based) guest and it's broken. Abiword freezes when accessing help is surely of lesser importance than your computer is now broken. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 539814] Re: 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)
On 6/9/10 12:50 PM, Paul van Genderen wrote: Is it possible to upgrade an existing vm or container? If the vm is running a 2.6.18, then the upgrade will fail as it will on any non-vms. The reason xen was mentioned is that many dom0's run 2.6.18 and many domU's run the dom0's kernel, so this issue is relevant to both dom0 as well as domU upgrades. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Is it possible to upgrade an existing vm or container? -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Debian has released a patch, that fixes just this problem, in January? See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563726 for more details. - Specifically http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=563726#66. Patch attached. Keith ** Patch added: Patch from above debian bug, which fixes this. http://launchpadlibrarian.net/49944671/tar-futimens.patch ** Changed in: tar (Ubuntu Lucid) Status: New = Fix Released ** Changed in: tar (Ubuntu) Status: New = Fix Released -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Apologies - set these to the wrong status. -Keith ** Changed in: tar (Ubuntu) Status: Fix Released = In Progress ** Changed in: tar (Ubuntu Lucid) Status: Fix Released = In Progress ** Changed in: tar (Ubuntu) Status: In Progress = Fix Released -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
** Changed in: ubuntu-release-notes Status: Won't Fix = Triaged -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Any status updates? How quickly might this get into SRU? Thanks, D. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 539814] Re: 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)
On Sat, Apr 24, 2010 at 21:57:51 -, Steve Langasek wrote: On Thu, Apr 22, 2010 at 10:35:49PM -, Nathan Stratton Treadway where that does happen. I wonder if there is any chance the Ubuntu project could come up with some policy regarding support for those situations (for Maverick, obviously). I don't believe this is likely to happen, fwiw; we can certainly have the discussion, but supporting two-year-old kernels for LTS upgrade purposes already requires ongoing work, and I don't believe we're ever going to be able to support running the Ubuntu userspace on an arbitrary non-Ubuntu kernel except on a best-effort basis (like in this case). I don't think anyone would expect support for arbitrary kernel versions, but perhaps the outcome of such a discussion would be to pick specific outside of the current release versions for some level of support. (For example, supporting 2.6.18 because so many Xen hosts are currently tied to that version, or supporting chroot installs under old Ubuntu releases going back some number of releases, etc.) Also, there is some middle ground between supported as in we guarantee everything will work on this kernel version and unsupported. Something like we'll try to keep things working on this Linux kernel unless there is a good reason not to, and if we can't we'll be sure to warn you might be perfectly appropriate for this type of usage. Perhaps a compromise would be to add a one-line paragraph saying something like Users who would like to run Lucid using a kernel older than 2.6.24 should see ThisPage, pointing to a page somewhere under help.ubuntu.com or wiki.ubuntu.com. [Using 2.6.24 because that was the version in Hardy.] [...] Under the circumstances, perhaps it's better to simply use the release notes to warn users off of upgrading to 10.04 until these issues are fixed, and focus on getting these SRUs done? I'll leave it to you to decide if it's easier to just write a release note that specifically mentions these bugs (e.g. LP: #539814 and LP: #552816), or to do a generic note that points to a Wiki page. The former is a little more streamlined, though the latter would allow users who discover other running-on-older-kernel issues to add them to the list later. Either way, the point is just to get some warning in front of people before they start an upgrade and then discover that their system/installation is broken Nathan -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 539814] Re: 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)
On Thu, Apr 22, 2010 at 10:35:49PM -, Nathan Stratton Treadway wrote: Ah! I see, there is currently no attempt to support any case where one's kernel comes from outside the Ubuntu installation being upgraded. As Dmitry mentions (and as indicated by the general discussion here), I think there are a lot of people who are using Ubuntu one way or another where that does happen. I wonder if there is any chance the Ubuntu project could come up with some policy regarding support for those situations (for Maverick, obviously). I don't believe this is likely to happen, fwiw; we can certainly have the discussion, but supporting two-year-old kernels for LTS upgrade purposes already requires ongoing work, and I don't believe we're ever going to be able to support running the Ubuntu userspace on an arbitrary non-Ubuntu kernel except on a best-effort basis (like in this case). Anyway, on the topic of the Lucid release notes, I certainly understand the desire to keep them as short as possible. On the other hand, it really seems that even a user advanced enough to be running e.g. a Xen server would prefer to have *some* warning before initiating an upgrade to Lucid that is doomed to abort mid-upgrade this way (leaving dpkg/apt/aptitude in a broken configuration) When declining the release notes task I was thinking in terms of chroots which can easily be recovered after the fact. Xen is obviously a different matter; given that this also affects running on Xen, I agree we should document this in the release notes. Perhaps a compromise would be to add a one-line paragraph saying something like Users who would like to run Lucid using a kernel older than 2.6.24 should see ThisPage, pointing to a page somewhere under help.ubuntu.com or wiki.ubuntu.com. [Using 2.6.24 because that was the version in Hardy.] I would be willing to create the initial version of such a page, provided that you were interested in linking to it (and especially if someone what was more familiar than I am with the existing wiki/help pages could recommend a good location for creating it). Under the circumstances, perhaps it's better to simply use the release notes to warn users off of upgrading to 10.04 until these issues are fixed, and focus on getting these SRUs done? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
@Steve: I agree, i think this is the best solution, given how little time we have before release. How do distributions upgrades work? I just downloaded upgrade-manager- core and was greeted by a bunch of python scripts... which means I'm not gonna look through them. Does anyone know how this works? What is the backend in the upgrade? Will tar get pulled from SRU? If it tar gets pulled from the stable release, we have an issue, if it gets pulled from SRU, then we're in the clear. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Snippet from 2.6.18 kernel ouput with old tar and with the patched version. ** Attachment added: 2.6.18 tar output http://launchpadlibrarian.net/45043681/tar.log -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
Andrew, Your patched worked great. I'm running 2.6.18-164.15.1.el5xen -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
** Summary changed: - Impossible to bootstrap Lucid on Dapper + 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) -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: 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)
@Steve, Ah! I see, there is currently no attempt to support any case where one's kernel comes from outside the Ubuntu installation being upgraded. As Dmitry mentions (and as indicated by the general discussion here), I think there are a lot of people who are using Ubuntu one way or another where that does happen. I wonder if there is any chance the Ubuntu project could come up with some policy regarding support for those situations (for Maverick, obviously). (I would be happy to open new bug for that issue if you thought there would be any interest in pursuing the idea further, especially if you could give me a hint as to what package such a bug should be be filed against.) Anyway, on the topic of the Lucid release notes, I certainly understand the desire to keep them as short as possible. On the other hand, it really seems that even a user advanced enough to be running e.g. a Xen server would prefer to have *some* warning before initiating an upgrade to Lucid that is doomed to abort mid-upgrade this way (leaving dpkg/apt/aptitude in a broken configuration) Perhaps a compromise would be to add a one-line paragraph saying something like Users who would like to run Lucid using a kernel older than 2.6.24 should see ThisPage, pointing to a page somewhere under help.ubuntu.com or wiki.ubuntu.com. [Using 2.6.24 because that was the version in Hardy.] I would be willing to create the initial version of such a page, provided that you were interested in linking to it (and especially if someone what was more familiar than I am with the existing wiki/help pages could recommend a good location for creating it). -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
