[Vmware-package-maintainers] Bug#463400: vmware-package: generated kernel source package uses erroneous control file

Anders Lennartsson anders.lennartsson at foi.se
Thu Jan 31 13:12:37 UTC 2008


Package: vmware-package
Version: 0.21
Severity: normal

The generated package vmware-kernel-source_XXXX_all.deb has a static
control file that makes dp_builddeb in debian/rules build a new
vmware-kernel-source package. The modules are compiled but never
included in a package.

There is a file control.modules.in that seems aimed at precisely this.
I added one line seen in the patch which fixed this particular problem.

the generated kernel source package was made by
fakeroot make-vmpkg VMware-workstation-6.0.2-59824.x86_64.tar.gz
on a amd64/sid box.

Anders

PS

By the way, the line

dh_builddeb --destdir=$(DEB_DESTDIR)

does not have a nice default, if the variable is not defined the
package building fails if one does not have write access to /usr. 
-------------- next part --------------
--- rules.old   2008-01-30 14:55:05.000000000 +0100
+++ rules       2008-01-31 14:04:49.000000000 +0100
@@ -24,6 +24,8 @@
        dh_testroot
        dh_clean -k
 
+       sed 's/_KVERS_/$(KVERS)/g' debian/control.modules.in > $(CURDIR)/debian/control
+
        # Build the module
        -cd vmblock-only && $(MAKE) -C $(KSRC) VM_CCVER=`gcc -dumpversion` VM_KBUILD=26 SUBDIRS=$$PWD SRCROOT=$$PWD/. modules
        cd vmmon-only && $(MAKE) -C $(KSRC) VM_CCVER=`gcc -dumpversion` VM_KBUILD=26 SUBDIRS=$$PWD SRCROOT=$$PWD/. modules


More information about the Vmware-package-maintainers mailing list