Bug#649514: nvidia-cg-toolkit: should this package be orphaned?

Mathieu Malaterre mathieu.malaterre at gmail.com
Thu May 24 12:57:08 UTC 2012


Hi,

On Thu, May 24, 2012 at 2:47 PM, Andreas Beckmann <debian at abeckmann.de> wrote:
> Hi Miguel,
>
> a heavily shuffled, merged, rebased and cleaned up branch can be found here:
>
> git://github.com/anbe42/nvidia-cg-toolkit.git prepare-3.1v2

Here is what I get:

  git clone git://github.com/anbe42/nvidia-cg-toolkit.git
  cd nvidia-cg-toolkit
  git checkout prepare-3.1v2
  make -f ./debian/rules get-orig-source
  mv nvidia-cg-toolkit_3.1.0013.orig-amd64.tar.gz
nvidia-cg-toolkit_3.1.0013.orig-i386.tar.gz ..
  dpkg-buildpackage -rfakeroot -us -uc
make[1]: Entering directory `/tmp/nn/nvidia-cg-toolkit'
/usr/bin/make -C amd64/local/Cg/examples/Tools/cginfo/ \
		CG_INC_PATH=/tmp/nn/nvidia-cg-toolkit/amd64/include
make: Entering an unknown directory
make: *** amd64/local/Cg/examples/Tools/cginfo/: No such file or
directory.  Stop.
make: Leaving an unknown directory
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory `/tmp/nn/nvidia-cg-toolkit'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


> History is arranged to continuously build working packages as commits
> fly by and changelog was rewritten to match.
>
> I'm going to do some upgrade tests before I push this to git.d.o
>
> Please test if this still works as expected.
>
> I also fixed the hardening, --as-needed, and lintian issues.
>
> I removed the Replaces as there were no file conflicts dpkg would have
> to handle. Breaks is sufficient to get rid of the old package.
>
> Please don't drop DMUA or trailing comma on Uploaders.

trailing comma is not well handled by BTS, see extra '(u)' for instance at:
http://packages.qa.debian.org/k/khronos-opencl-headers.html

> If this package is fine fou you,
>  dch -r && git commit && push to github somewhere && update mentors
>
> Nvidia also offers a .deb package 'nvidia-cg-toolkit' that would
> conflict with our split up package if a user would upgrade from our new
> packaging to this package. (It also comes with some insanities like
> /usr/lib64.) Do we want to handle this somehow?

Add a note in the README.Debian to remove the nvidia package first :)
Unless it is available downstream (ubuntu), I do not believe we should
do anything about it.

2cts
-- 
Mathieu





More information about the pkg-nvidia-devel mailing list