Thanks so much for clarifying this. My understanding is that for now,
what I'm doing by putting a hold on virtualbox-ose-source so it won't
upgrade to the new version that doesn't look like module-assistant can
work with is the correct procedure. But this will be all settled and
working normally once we get 2.6.23 kernels ready to go.
This, on Lenny, is with the 1.5.2 version of Virtualbox stuff, but by
the time all this is sorted it'll be 1.5.4 and the new kernel sources
and modules builders all coming into Lenny at the same time so
everything will be working again.
Cool. As long as I can use Virtualbox in the meantime. Too bad about
the Nvidia drivers though. As I've said, we have (in a way I don't
understand but it doesn't really matter) an older source for Virtualbox
1.5.2 available for module assistant to work with but NVidia doesn't.
So for that we are forced to use the downloaded NVidia binary from
nvidia.com. I managed to remove the Sid sources, purge
xserver-xorg-core and friends and all the Debian nvidia stuff, reinstall
the Lenny versions (along with putting back the gnome stuff), and
install the NVidia binary. So actually this is nice in a way because I
no longer need to mix distributions (got rid of apt.conf too). All
fully Lenny now.
To sum up, yeah things don't exactly jive right now but it'll be fixed
up shortly so this bug will no longer exist. At least I hope it's
shortly. Depends upon how soon the 2.6.23 kernels are ready for Lenny
acceptance.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
