Upgrade to 9.04?

[David Fox]

On Sun, Oct 11, 2009 at 11:32 AM, David Fox <dfox94085 at gmail.com> wrote:

> Here's what aptitude shows (this is Jaunty, but only the version
> numbers have been changed to protect the innocent) for linux kernels

Umm. I just reread your post, and it seems you already have
linux-image-generic. But still you've got a problem in the update
scripts preventing the initrd tools from upgrading. Going back and
punting, we discover this:

th1bill at th1bill-desktop:~$ sudo apt-get clean
>
> [sudo] password for th1bill:

Running apt-get clean isn't helpful. What it does is clean out your
package cache in /var/cache/apt/archives, and it's mostly there to get
rid of cruft and keep your /var from getting full. I almost never use
it. More helpful, is "apt-get autoclean" which only removes packages
that aren't available any more and are superseded.  For this
particular purpose - going from LTS to LTS and then to 9.04 - you
probably have a ton of package files taking up space, but those are
only the package debs and they're not affecting your install. I'd only
do that if you were getting out of room.

But it's too late now.

I'd try gong to a terminal and running "sudo update-manager -d". It's
the recommend way to do distribution iupdates. That might not solve
your immediate problem;

OTOH, it might decide you want Karmic :).


> cpio: ./bin/udevinfo: Cannot stat: No such file or directory
>
> update-initramfs: failed for /boot/initrd.img-2.6.28-3-rt

Something (probably the prior update) removed this file and is
confusing the hell out of dpkg with the state your system is in. Using
wajig (or apt-file) I don't see any reference to /bin/udevinfo. And
I'm on Jaunty, and I can't check for other versions.

Googling the text of the cpio error message is one place to start.
Launchpad seems to have found a bug, and I found a very similar
problem in an Ubuntu forum, but no resolution to the problem. Whoever
posted a response was more than unhelpful :(.

Bug #430367 might be relevant, but it's been marked invalid. But
there's a response from Colin Watson (one of the packagers) who points
to another bug. But we're still not sure if this is a real bug or
something else that got dpkg in such a confused state. Maybe dpkg
isn't the right tool now, although you're on the right track, usually
dpkg --configure -a resolves a lot of problems (I did this once during
a Hardy to Intrepid dist-upgrade where I had lost video feedbak
sometime late in the process and I reset after waiting a long time
with the only feedback being tthe HD liight, and I lacked another
machine to ssh in from. Hard, but it fixed things.)





-- 
thanks for letting me change the magnetic patterns on your hard disk.