@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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
