Bug#386773: Is this bug blocking migration of 2.6.17 prebuilt modules into testing ?
On Sun, 2006-09-24 at 05:43 -0700, Steve Langasek wrote: > On Sun, Sep 24, 2006 at 12:38:46PM +0100, Tim Day wrote: > > [A load of nonsense about > > nvidia-kernel-legacy-2.6.17 packages > > deleted] > > nvidia-graphics-drivers-legacy (1.0.7174-4 to 1.0.7184-2) > Maintainer: Randall Donald > Section: non-free/x11 > Too young, only 2 of 10 days old > nvidia-glx-legacy/i386 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy/amd64 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy-ia32/amd64 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy-dev (i386, amd64) is buggy! (1 > 0) > nvidia-graphics-drivers-legacy (source) is buggy! (1 > 0) > Not considered > > There are two missing bugs, and three unsatisfiable dependencies. Where are > you seeing prebuilt modules that are compatible with this version? Oooops sorry didn't notice that the nvidia-kernel-legacy-2.6.17* packages in unstable are only built off the 1.0.7182 Nvidia release, but the nvidia-glx-legacy already in testing is 1.0.7184. Doh. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386773: Is this bug blocking migration of 2.6.17 prebuilt modules into testing ?
On Sun, Sep 24, 2006 at 12:38:46PM +0100, Tim Day wrote: > There seem to be prebuilt modules for 2.6.17 in sid ready to migrate > into testing, at least according to the "Why is package X not in testing > yet?" page, but the way I read it they're being blocked by a release > critical bug on nvidia-graphics-legacy-modules-i386, which is presumably > this grave severity one (but there's a bunch of other reasons there too > and I still don't entirely understand the rules; maybe there's the > remainder of the wait period still to run too). > Anyway, since the availability of the 2.6.17 prebuilts presumably fixes > this, can someone mark it fixed or downgrade it or whatever it takes to > unblock things ? nvidia-graphics-drivers-legacy (1.0.7174-4 to 1.0.7184-2) Maintainer: Randall Donald Section: non-free/x11 Too young, only 2 of 10 days old nvidia-glx-legacy/i386 unsatisfiable Depends: nvidia-kernel-legacy-1.0.7184 nvidia-glx-legacy/amd64 unsatisfiable Depends: nvidia-kernel-legacy-1.0.7184 nvidia-glx-legacy-ia32/amd64 unsatisfiable Depends: nvidia-kernel-legacy-1.0.7184 nvidia-glx-legacy-dev (i386, amd64) is buggy! (1 > 0) nvidia-graphics-drivers-legacy (source) is buggy! (1 > 0) Not considered There are two missing bugs, and three unsatisfiable dependencies. Where are you seeing prebuilt modules that are compatible with this version? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386773: Is this bug blocking migration of 2.6.17 prebuilt modules into testing ?
There seem to be prebuilt modules for 2.6.17 in sid ready to migrate into testing, at least according to the "Why is package X not in testing yet?" page, but the way I read it they're being blocked by a release critical bug on nvidia-graphics-legacy-modules-i386, which is presumably this grave severity one (but there's a bunch of other reasons there too and I still don't entirely understand the rules; maybe there's the remainder of the wait period still to run too). Anyway, since the availability of the 2.6.17 prebuilts presumably fixes this, can someone mark it fixed or downgrade it or whatever it takes to unblock things ? [Nvidia legacy for 2.6.16 was a dud by the way... see discussions on the testing mail list around 18th-20th August 2006]. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
