registry team mailing list archive

[Jean-Baptiste Lallement <593509@xxxxxxxxxxxxxxxxxx>]

The problem is not with dkms but with the make command in dkms.conf of
the openafs module.

Here is a patch
--- dkms.conf.orig	2010-08-05 23:47:56.446432083 +0200
+++ dkms.conf.new	2010-08-05 23:47:40.626934117 +0200
@@ -8,7 +8,7 @@
 DEST_MODULE_LOCATION[0]="/updates/dkms/"
 AUTOINSTALL=yes
 
-MAKE[0]="./configure --with-linux-kernel-headers=${kernel_source_dir}
+MAKE[0]="( ./configure --with-linux-kernel-headers=${kernel_source_dir}
     && make
-    && mv src/libafs/MODLOAD-*/openafs.ko . "
+    && mv src/libafs/MODLOAD-*/openafs.ko . )"
 CLEAN="rm -f openafs.ko && make -C src/libafs clean"
 
In the current version of dkms.conf we are logging the output of the command mv


** Changed in: dkms (Ubuntu)
   Importance: Undecided => Low

** Changed in: dkms (Ubuntu)
       Status: New => Triaged

** Package changed: dkms (Ubuntu) => openafs (Ubuntu)

-- 
openafs-modules-dkms leaves ~empty make.log on failing builds
https://bugs.launchpad.net/bugs/593509
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.