[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: plan of deep learning team for next stable release?

Dear non-free autobuilders,

On debian-ai we are wondering about how to tag packages that need
Debian's cuda packages installed to build, i.e. for their runtime tests.
That said, is possibly the mere addition of a cuda package as build
dependency sufficient to point to a particular subset of buildds?

The number of packages in need of a CUDA-savvy buildd I expect to be
less than 20 in 2020 from debian-ai and also for Debian Med I only have
about two packages in mind that would make immediate use of CUDA.

Since packages needing a non-free autobuild need to register anyway,
maybe there is not too much overhead for a support of CUDA on the
non-free buildd? I would be prepared to help with a machine if that is a


On 01.12.20 15:20, Christian Kastner wrote:
> On 12/1/20 1:01 PM, Steffen Möller wrote:
>> The way to go is via our non-free autobuilders, not? 
>> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd
> That would probably be the way to go, however I have slight doubts that
> modifying an existing buildd would be accepted as a solution.
>> Since many DDs are using the CUDA drivers already, I think we have
>> already decided to trust them.
>> It should be somehow possible for me to come up with a buildd machine
>> should this help the discussion.
> That sounds great!
> My gut thinks that the hardware is the key issue here. We already have
> Nvidia drivers and CUDA in the archive, but those cost volunteer time,
> not project money.
> Best,
> Christian

Reply to: