Your message dated Sat, 14 Nov 2009 11:41:24 +0000
with message-id <1258198884.4378.5.ca...@wintermute>
and subject line Re: [Pkg-virtualbox-devel] Bug#555127:
virtualbox-ose-guest-utils: Unclear how to get modules for newer kernel versions
has caused the Debian Bug report #555127,
regarding virtualbox-ose-guest-utils: Unclear how to get modules for newer
kernel versions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
555127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555127
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: virtualbox-ose-guest-utils
Version: 3.0.10-dfsg-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
$ sudo aptitude install -t unstable linux-image-2.6-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
firmware-linux-free{a} linux-image-2.6.31-1-amd64{a}
The following packages will be upgraded:
linux-image-2.6-amd64
1 packages upgraded, 2 newly installed, 0 to remove and 354 not upgraded.
Need to get 27.4MB of archives. After unpacking 99.0MB will be used.
Do you want to continue? [Y/n/?] e
Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for wintermute
Preconfiguring packages ...
(Reading database ... 205462 files and directories currently installed.)
Removing linux-image-2.6.30-1-amd64 ...
Purging configuration files for linux-image-2.6.30-1-amd64 ...
Running postrm hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.30-2-amd64
Found initrd image: /boot/initrd.img-2.6.30-2-amd64
done
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.30-1-amd64
/boot/vmlinuz-2.6.30-1-amd64
rmdir: failed to remove `/lib/modules/2.6.30-1-amd64': Directory not empty
dpkg: warning: while removing linux-image-2.6.30-1-amd64, directory
'/lib/modules/2.6.30-1-amd64' not empty so not removed.
Removing linux-image-2.6.31-trunk-amd64 ...
Purging configuration files for linux-image-2.6.31-trunk-amd64 ...
Running postrm hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.30-2-amd64
Found initrd image: /boot/initrd.img-2.6.30-2-amd64
done
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.31-trunk-amd64
/boot/vmlinuz-2.6.31-trunk-amd64
Selecting previously deselected package linux-image-2.6.31-1-amd64.
(Reading database ... 205460 files and directories currently installed.)
Unpacking linux-image-2.6.31-1-amd64 (from
.../linux-image-2.6.31-1-amd64_2.6.31-1_amd64.deb) ...
Selecting previously deselected package firmware-linux-free.
Unpacking firmware-linux-free (from .../firmware-linux-free_2.6.31-1_all.deb)
...
Preparing to replace linux-image-2.6-amd64 2.6.30+21 (using
.../linux-image-2.6-amd64_2.6.31+22_amd64.deb) ...
Unpacking replacement linux-image-2.6-amd64 ...
Selecting previously deselected package linux-image-amd64.
Unpacking linux-image-amd64 (from .../linux-image-amd64_2.6.31+22_amd64.deb) ...
Setting up linux-image-2.6.31-1-amd64 (2.6.31-1) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.31-1-amd64
Running update-grub.
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.31-1-amd64
Found initrd image: /boot/initrd.img-2.6.31-1-amd64
Found linux image: /boot/vmlinuz-2.6.30-2-amd64
Found initrd image: /boot/initrd.img-2.6.30-2-amd64
done
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 2.6.31-1-amd64
/boot/vmlinuz-2.6.31-1-amd64
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.31-1-amd64
/boot/vmlinuz-2.6.31-1-amd64
Setting up firmware-linux-free (2.6.31-1) ...
Setting up linux-image-2.6-amd64 (2.6.31+22) ...
Setting up linux-image-amd64 (2.6.31+22) ...
Press return to continue.
Installing 2.6.31 didn't seem to trigger a DKMS build of the virtualbox
modules. If it was not intended to, then please consider this a request
to make it so. :)
- -- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (430, 'testing'), (420, 'unstable'), (410, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages virtualbox-ose-guest-utils depends on:
ii libc6 2.10.1-5 GNU C Library: Shared libraries
ii pciutils 1:3.1.4-2 Linux PCI Utilities
Versions of packages virtualbox-ose-guest-utils recommends:
ii virtualbox-ose-guest-sourc 3.0.10-dfsg-1 x86 virtualization solution - gues
ii virtualbox-ose-guest-x11 3.0.10-dfsg-1 x86 virtualization solution - X11
virtualbox-ose-guest-utils suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkr28YYACgkQshl/216gEHg7HQCffkFLgrRmlzYxXPGPh3iSc5p+
63gAoNNIgIdUHkVb+qpKakYTapE/S5W2
=sc0C
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sat, 2009-11-14 at 12:35 +0100, Michael Meskes wrote:
> tag 555127 unreproducible
> tag 555127 moreinfo
>
> thanks
>
> > run-parts: executing /etc/kernel/postinst.d/dkms 2.6.31-1-amd64
> > /boot/vmlinuz-2.6.31-1-amd64
>
> This should rebuild your vbox modules and it does for me.
Oh, I didn't notice that. Nevertheless, I didn't see any anything appear
in updates/dkms. However when I actually booted into the new kernel, I
think the dkms init script arranged for the modules to be built
(certainly, it spent quite some time doing something)...
So either I overlooked the presence of the modules before rebooting, or
they were built automatically on the next reboot. Either way the modules
were built without my intervention and before they were needed, so no
bug. :)
--
Sam Morris
https://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
--- End Message ---
