I can't really look now. The way I got it to install successfully was to apt-get the generic one and let its dependency on virtualbox pull in the rest of the stuff. If I try to aptitude install -s virtualbox-ose now, it says nothing to install because my manual installation of the generic one has already satisfied it.
On Tue, Mar 25, 2008 at 5:58 PM, Daniel Hahler <[EMAIL PROTECTED]> wrote: > On Sunday 23 March 2008 05:36:23 Mackenzie Morgan wrote: > > > On the 21st (or 20th....UTC makes Launchpad say funny things), you > marked > > this fixed, but I'm still having this problem. > > Do you still have that problem? > > I think the fixed packages may have just not been distributed by the time > you > were still experiencing it. Have you checked that you were using the fixed > version(s)? > > If it's still a problem, please file a new bug (or re-open an existing > one) > and provide the output of "dpkg -l | grep virtualbox". > The version where it has been fixed are mentioned in the bug report. > > Please note, that it has only been fixed for new installs of > virtualbox-ose: > if the 386 kernel image has been pulled in already, it will stay installed > of > course: you can just uninstall the linux-image-*-386 packages in this > case. > > > Cheers, > Daniel. > > > > > On Tue, Mar 18, 2008 at 8:42 PM, Daniel Hahler <[EMAIL PROTECTED]> > > > > wrote: > > > Hello, > > > > > > there's a major problem when installing virtualbox-ose or > > > virtualbox-ose-guest-utils in Hardy. > > > > > > These packages each depend on a virtual package > (virtualbox-ose-modules > > > and virtualbox-ose-guest-modules). > > > > > > These virtual packages get provided by packages, which themselves > depend > > > on linux-image-$ABI-$FLAVOR. > > > > > > Now, when installing virtualbox-ose-guest-utils on a system with the > > > "generic" kernel being used/installed, apt does not recognized that > > > using virtualbox-ose-guest-modules-2.6.24-12-generic would be the > better > > > match, but uses the first available "-386" instead. > > > > > > So, when users install virtualbox-ose or the guest modules, they are > > > likely installing an additional kernel image, which isn't required at > > > all and causes confusion/problems on the next boot (e.g. wireless > > > broken). > > > > > > This does not affect users with "generic" kernels on amd64, because > > > there's no 386 flavor available for them. > > > > > > More details are available on: https://launchpad.net/bugs/188579 > > > > > > Any ideas how this can get fixed? > > > > > > > > > Thanks for reading and thinking about it. > > > > > > Happy hacking, > > > Daniel. > > > > > > -- > > > http://daniel.hahler.de/ > > > > > > -- > > > Ubuntu-devel-discuss mailing list > > > Ubuntu-devel-discuss@lists.ubuntu.com > > > Modify settings or unsubscribe at: > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > > -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com <-my blog of Ubuntu stuff apt-get moo
-- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
