361.45.x migration (was: Re: r6827 - in /packages/nvidia-graphics-drivers/tags/367.44-1: ./ debian/ debian/module/debian/patches/)

Luca Boccassi luca.boccassi at gmail.com
Wed Sep 7 10:14:02 UTC 2016

On Wed, 2016-09-07 at 11:34 +0200, Andreas Beckmann wrote:
> On 2016-09-07 11:31, Luca Boccassi wrote:
> > BTW, any idea why 361.45.x migration to testing is being held up? I
> > can't see anything on the reasons page:
> > 
> > https://qa.debian.org/excuses.php?package=nvidia-graphics-drivers
> Try go get the answer from
> https://release.debian.org/britney/update_output.txt
> Andreas

I think it's the PPC CUDA packages. Given there are no ppc64el builds of
the new versions (no upstream releases), migrating would break the
ppc64el libcuinj64-7.5 nvidia-cuda-dev nvidia-cuda-toolkit
nvidia-profiler nvidia-visual-profiler packages since libcuda1 would no
longer be available.

trying: nvidia-graphics-drivers
skipped: nvidia-graphics-drivers (0, 44, 16)
    got: 62+941: a-3:i-18:a-0:a-0:a-0:m-0:m-0:p-35:p-5:s-1:m-941
    * ppc64el: libcuinj64-7.5, nvidia-cuda-dev, nvidia-cuda-toolkit,
nvidia-profiler, nvidia-visual-profiler

What do we do about this? Do we want to remove the ppc64 CUDA until
upstream releases a new version of the drivers?

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160907/f530daaa/attachment.sig>

More information about the pkg-nvidia-devel mailing list