[pkg-nvidia-devel] Bug#493470: Bug#493470: building nvidia module package using module-assistant fails

Harald Dunkel harald.dunkel at t-online.de
Fri Aug 8 05:54:46 UTC 2008

Lennart Sorensen wrote:
> 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)?

Using root the build problem is gone, but now signing the package
fails. I cannot use fakeroot either, because then m-a complains
early about no write permission to /var/cache/modass. If I make
/usr/src writable by me, and use

	export MA_VARDIR=/tmp/modass
	fakeroot module-assistant -f -t build nvidia-kernel

then it works (except for the broken *.changes file name). But I
would like to avoid using /usr for building modules.

Something like

	module-assistant -f -u /usr/src/modules -t build nvidia-kernel

fails regardless whether I am root. Seems that handling an explicit
build directory is broken, so I would suggest to focus on this problem

> 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.

So you mean I should build the nvidia packages as root in /usr, and
not sign them?

> It would still be nice to get it fixed of course.

Indeed, this would be very nice. The other module packages I tried
(omfs, madwifi, virtualbox-ose) don't have this problem.



More information about the Pkg-nvidia-devel mailing list