autobuilding src:nvidia-* [non-free]

Philipp Kern pkern at debian.org
Mon Aug 6 15:07:54 UTC 2012


On Mon, Aug 06, 2012 at 04:39:26PM +0200, Andreas Beckmann wrote:
> On 2012-08-06 16:02, Philipp Kern wrote:
> >> nvidia-graphics-modules
> > I'd have expected an arch:all dkms package here.
> src:nvidia-graphics-modules builds prebuilt kernel modules
> (nvidia-kernel-$KVERS-$FLAVOR) built from nvidia-kernel-source
> (src:nvidia-graphics-drivers) (the module-assistant/make-kpkg/...
> package) and is restricted to i386 and amd64 - as it uses blobs that are
> only available for these two archs.

I gathered. That doesn't answer my point, though. It is the *last* package
in the archive doing so, instead of using dkms. It does mean that it needs to
be updated on every kernel ABI bump. (Also in theory the ABI compatibility
guarantee of the Debian Linux packages is that they can add new symbols at any
time, they just won't drop old ones. But I guess that's not as relevant for the
nvidia packages. Packages other than the kernel would pass the "-V" argument to
dh_makeshlibs to get the right effect.)

> > It also does not use
> > Built-Using, which might cause GPL-compliance issues?
> Didn't know about this field - will look into and use it in the future.
> 
> So I would ideally need a
> Built-Using: nvidia-graphics-drivers (= $V1), linux (= $V2)
> 
> Does this also influence testing migration? I.e. does n-g-m now wait for
> n-g-d (= $V1)

No. It's dak-only.

Kind regards
Philipp Kern
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 588 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20120806/cd3c1356/attachment-0001.pgp>


More information about the pkg-nvidia-devel mailing list