Page 1 of 1

nVIDIA 280.13

PostPosted: Aug 16th, '11, 10:59
by bertaerts
On August 1st nVIDIA released the driver 280.13.
It is already available in Cauldron: nvidia-current-cuda-opencl-280.13-1.mga2.nonfree.x86_64.rpm

When will it appear in Mageia 1 updates_testing or backports_testing?

Re: nVIDIA 280.13

PostPosted: Aug 23rd, '11, 14:43
by bertaerts

Re: nVIDIA 280.13

PostPosted: Aug 23rd, '11, 15:16
by dubigrasu

Re: nVIDIA 280.13

PostPosted: Aug 23rd, '11, 20:46
by bertaerts
Thanks for the link.
Usage was very simple.
I am now running 280.13

But I now don't understand these 5 minutes of work is not yet part of Mageia 1 ;-)

Re: nVIDIA 280.13

PostPosted: Aug 23rd, '11, 22:37
by doktor5000
bertaerts wrote:But I now don't understand these 5 minutes of work is not yet part of Mageia 1 ;-)


You just volunteered to do those 5 minutes of work as a packager, and the following Quality Assurance testing
to ensure everything still works as it should and nothing else breaks? Go for it!

Re: nVIDIA 280.13

PostPosted: Aug 25th, '11, 11:23
by bertaerts
Hi doktor5000,

In my understanding, the 5 minutes were needed to run the script to create the .rpm files.

I would assume that they could be put immediately in Mageia 1 nonfree/updates_testing, as 280.13 is not a beta but an nVIDIA recommended release.
And that all people who have enabled the nonfree/updates_testing repository would test it and create a bug report in case of an issue.

But I do not know the procedure in Mageia to get an rpm in the testing repo...

Kind regards,

Bert

Re: nVIDIA 280.13

PostPosted: Aug 25th, '11, 12:07
by doktor5000
Immediately when the packager/maintainer has the time for it.
I saw you also added a bug report for it: https://bugs.mageia.org/show_bug.cgi?id=2498
That would be the beginning of the procedure. I'll try to look into it.

Re: nVIDIA 280.13

PostPosted: Aug 25th, '11, 13:11
by doktor5000
Ah, now is see the problem, after switching my brain on :)
The problem is: This is merely a pure version update, no bugfix or security update.
So it should go to backports, and the backports policy is still being discussed and backports media
is not yet open, so guess you have to wait. But should be no problem, as you already have the new version.