Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
On Fri, Aug 21, 2009 at 11:56:32AM -0700, Randall Donald wrote: On Thu, 2009-08-20 at 10:04 +0200, Pierre Bauduin wrote: Package: nvidia-glx-ia32 Severity: serious What's funny about this is you want a package to be in testing but filing a RC bug just added to reasons preventing that. What does it take for non-free packages to move to testing? Is it automatic or not? With 2.6.30 now in testing, nvidia-glx no longer works in testing until we get the new version moved in. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
On Wed, 2009-10-28 at 11:36 -0400, Lennart Sorensen wrote: On Fri, Aug 21, 2009 at 11:56:32AM -0700, Randall Donald wrote: On Thu, 2009-08-20 at 10:04 +0200, Pierre Bauduin wrote: Package: nvidia-glx-ia32 Severity: serious What's funny about this is you want a package to be in testing but filing a RC bug just added to reasons preventing that. What does it take for non-free packages to move to testing? Is it automatic or not? With 2.6.30 now in testing, nvidia-glx no longer works in testing until we get the new version moved in. The testing transition first requires a kernel module package to satisfy the dependancy. Add to that no RC bugs. And even then some manual trickery might be required. -- Randall Donald ra...@khensu.org http://www.khensu.orgrdon...@debian.org Programmer/Debian Developer GnuPG: 6C27DEAB -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
So can we build and upload the kernel modules or should we bug the kernel-modules-non-free package person to add us (since that should now work)? We probably should go ahead with that soon. For all but 71xx which I think we will drop for this release since it no longer works. -- Randall Donald ra...@khensu.org http://www.khensu.orgrdon...@debian.org Programmer/Debian Developer GnuPG: 6C27DEAB -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
On Wed, Oct 28, 2009 at 12:08:49PM -0700, Randall Donald wrote: So can we build and upload the kernel modules or should we bug the kernel-modules-non-free package person to add us (since that should now work)? We probably should go ahead with that soon. For all but 71xx which I think we will drop for this release since it no longer works. Well we will have to essentially. nvidia seems to have clearly states they do not intend to update 71xx for the new Xorg release. So only 2D support unless nuevou (sp?) gets done someday for those older cards. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
Lennart Sorensen wrote: On Fri, Aug 21, 2009 at 11:56:32AM -0700, Randall Donald wrote: On Thu, 2009-08-20 at 10:04 +0200, Pierre Bauduin wrote: Package: nvidia-glx-ia32 Severity: serious What's funny about this is you want a package to be in testing but filing a RC bug just added to reasons preventing that. What does it take for non-free packages to move to testing? Is it automatic or not? With 2.6.30 now in testing, nvidia-glx no longer works in testing until we get the new version moved in. It takes the same as main packages: aging, installability, buildability, no new RC bugs, not breaking any package that is already in testing. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534873: [pkg-nvidia-devel] Bug#534873: Bug#534873: would be nice if nvidia-glx-ia32 185.18.14-2 amd64 could be in testing as soon as possible
On Wed, Oct 28, 2009 at 10:24:21AM -0700, Randall Donald wrote: On Wed, 2009-10-28 at 11:36 -0400, Lennart Sorensen wrote: On Fri, Aug 21, 2009 at 11:56:32AM -0700, Randall Donald wrote: On Thu, 2009-08-20 at 10:04 +0200, Pierre Bauduin wrote: Package: nvidia-glx-ia32 Severity: serious What's funny about this is you want a package to be in testing but filing a RC bug just added to reasons preventing that. What does it take for non-free packages to move to testing? Is it automatic or not? With 2.6.30 now in testing, nvidia-glx no longer works in testing until we get the new version moved in. The testing transition first requires a kernel module package to satisfy the dependancy. Add to that no RC bugs. And even then some manual trickery might be required. I thought the excuse entry of 'section non-free/X11' might need manual intervention. So can we build and upload the kernel modules or should we bug the kernel-modules-non-free package person to add us (since that should now work)? -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
