On Sat, Aug 02, 2008 at 10:06:00PM +0200, Harald Dunkel wrote: > Package: nvidia-kernel-source > Version: 173.14.09-3 > Severity: serious > > Hi folks, > > If I try to build the nvidia modules using module-assistant, then > I get > > > % export SIGNCHANGES=true > % module-assistant -f -t -u /tmp/modules build nvidia-kernel > Warning: sudo not found. Automatic package installations not possible! > Extracting the package tarball, /usr/src/nvidia-kernel.tar.bz2, please wait... > /usr/bin/make -f debian/rules clean > make[1]: Entering directory `/tmp/modules/usr_src/modules/nvidia-kernel' > # select which makefile to use. > rm -f /tmp/modules/usr_src/modules/nvidia-kernel/Makefile || true > : > : > dh_installdeb > dh_gencontrol -- -v173.14.09-3 > dh_md5sums > dh_builddeb --destdir=/tmp/modules > dpkg-deb: building package `nvidia-kernel-2.6.26' in > `/tmp/modules/nvidia-kernel-2.6.26_173.14.09-3_amd64.deb'. > make[1]: Leaving directory `/tmp/modules/usr_src/modules/nvidia-kernel' > # Build a .changes file. > dpkg-genchanges -b -e" <[EMAIL PROTECTED]>" > -u"/tmp/modules/usr_src/modules/nvidia-kernel/../.." > > /tmp/modules/usr_src/modules/nvidia-kernel/../../nvidia-kernel-2.6.26_173.14.09-3_.changes > dpkg-genchanges: binary-only upload - not including any source code > dpkg-genchanges: failure: cannot fstat file > /tmp/modules/usr_src/modules/nvidia-kernel/../../nvidia-kernel-2.6.26_173.14.09-3_amd64.deb: > No such file or directory > make: *** [kdist] Error 2 > BUILD FAILED! > See > /tmp/modules/var_cache_modass/nvidia-kernel-source.buildlog.2.6.26.1217702319 > for details. > Build failed. Press Return to continue... > > > AFAICS the "../.." in calling dpkg-genchanges is messed up. Should be > "../../..". And the *.changes file should be named something like > "nvidia-kernel-2.6.26_173.14.09-3_amd64.changes", depending upon the > output of dpkg-architecture. > > The same problem exists for the old legacy modules, AFAICS. It would > be very nice if this could be fixed.
Does it work if you are root and don't use the -u option (which I must admit I didn't even know existed before now)? If it does, then I would not consider it a serious bug since it works in the mode the vast majority of users actually use. It would still be nice to get it fixed of course. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
