<br><br><div class="gmail_quote">2009/1/25 Michael B. Trausch <span dir="ltr"><<a href="mailto:mike@trausch.us">mike@trausch.us</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sun, 25 Jan 2009 21:42:55 -0500<br>
Joshua Kite <<a href="mailto:jwkite@gmail.com">jwkite@gmail.com</a>> wrote:<br>
<br>
> I have a machine that had Ubuntu Feisty on it. I needed to add some<br>
> packages when I realized the shortcomings of not keeping a distro<br>
> current; the Feisty packages have been archived because it is no<br>
> longer supported. Long story short, I ultimately ended up changing<br>
> the sources.list file to point to Hardy and managed to mostly get the<br>
> box upgraded. However, I continually had issues apt installing<br>
> linux-generic and other kernel-related packages. I had run in to<br>
> dependency hell.<br>
<br>
</div>The problem here is that you skipped from Feisty to Hardy. Probably<br>
the best bet would have been to upgrade from Feisty (7.04) to Gutsy<br>
(7.10), and then to Hardy (8.04).<br>
<br>
Officially speaking, Ubuntu's upgrading infrastructure only supports<br>
upgrading from one release to the next immediate release; the only<br>
exception for that is from LTS to LTS. For example, users of Dapper<br>
did not have to upgrade from Dapper to Edgy to Feisty to Gutsy to<br>
Hardy. They were able to skip Edgy, Feisty, and Gutsy altogether and<br>
just upgrade directly to Hardy. When the next LTS comes out, Hardy<br>
will be able to upgrade directly to it, as well.<br>
<br>
I don't suppose that there is probably a way to revert the packages to<br>
the state that they were in before you started with this. Given that,<br>
I would wipe the drive and install Intrepid. :-P<br>
<br>
You mentioned 2.2 kernels. I don't know what you're referring to,<br>
there; Ubuntu uses the 2.6 series and has all the way back to Ubuntu<br>
4.10, the very first release (which used Linux 2.6.8 for its kernel).<br>
<br>
Could you provide some extra data? If you could pastebin the following<br>
files:<br>
<br>
/boot/grub/menu.lst<br>
/var/log/apt/term.log [Only starting from the upgrade]<br>
<br>
Also, the output of the following commands will be useful:<br>
<br>
ls -ld /boot/*<br>
dpkg -l<br>
<br>
I mentioned pastebin because some of these are going to be quite<br>
lengthy and shouldn't be on-list. I'd recommend pasting them there and<br>
then providing links here.<br>
<br>
--- Mike<br>
<font color="#888888"><br>
--<br>
My sigfile ran away and is on hiatus.<br>
<a href="http://www.trausch.us/" target="_blank">http://www.trausch.us/</a><br>
</font><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></blockquote></div><br>Mike,<br><br>Thanks for the help. I'm sending this email from another computer, so I don't have the right kernel info in front of me. I tried upgrading from Feisty to Gutsy but that's when the dependency problems began. A number of applications no longer worked, so I figured it wouldn't hurt to manually change the source.list from gutsy to hardy and see what happened. The upgrade has not been smooth, but at least I've kept my configurations in tact. I've found that some apps, such as apache2 were removed and had to be reinstalled, but I was able to do so without overwriting the config.<br>
<br>I've found some instructions that involve chroot (<a href="http://ubuntuforums.org/showthread.php?t=1034523">http://ubuntuforums.org/showthread.php?t=1034523</a>). I'll give them a try. If they don't work then I'll copy and paste the files you requested and see if they point us anywhere.<br>
<br>Thanks again,<br><br>Josh<br>