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
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)
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
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:
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
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
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
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
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,
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
** 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
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
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,
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
@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
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
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
** 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
@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
19 matches
Mail list logo
