> Wheezy currently has ia32-libs 20120102, so unblocking nvidia-* at the moment seems like it would just cause a different bunch of issues?
That depends on the future of ia32-libs in wheezy. Has there been a decision, yet? I could do the following: * revert the changes to the *-ia32 packages, making them non-transitional again * the package will be buildable in testing only (because it needs the old ia32-libs) but I would upload it to unstable, not tpu * the reinstated *-ia32 packages will be unusable (maybe uninstallable) in sid (but that won't block a transition to wheezy), everything else will be fine * I'll try to loosen the dependencies on ia32-libs to not block a possible transition of the ia32-libs version currently in sid (that transition would break *-ia32 built from n-g-d in testing, but can be fixed by a new upload of n-g-d with transitional *-ia32 packages again) I need to upload a new upstream release (304.43) anyway, fixes some bugs, add support for new hardware ... that could be bundled with above changes. I just tested: * the 304.37-1 packages are installable in wheezy, including the transitional -ia32 ones * libgl1-nvidia-glx:i386 and :amd64 are not co-installable due to lack of multiarch support in libxvmc1 (#640499) => no 32-bit nvidia support on amd64 * 32-bit nvidia support on amd64 (needed for e.g. wine) could be restored by reinstating the n-g-d *-ia32 packages if the old monolithic ia32-libs stays in wheezy Andreas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
