Bug#688861: freeze exception: libxvmc/1.0.7-1.1 - adding a libxvmc1-i386:i386 package
Hi,
>>> Not so much related, as a proposed alternative, afaics? The
>>> maintainers appear to have made their opinion quite clear in
>>> #640499 on the originally suggested approach, however...
>> You mean http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640499#66
>> ?
>
> No, I meant
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640499#149
Ah, that one. I must have missed a release manager saying that then - I
don't know your names ;-)
>> He didn't say he's opposed to the patch, just that the release team
>> might not let it through. The release team didn't reply (or I
>> missed it?). libcap2 multiarchification was let in though
>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684647), and
>
> I'm aware of that. :-) (see the release team members involved in
> that discussion).
Oh, saw that name already... ;-)
> That's also a different situation; libcap2 is required to allow us to
> get rid of the monolithic ia32-libs.
Essentially, this is the case here, too: Getting git of
libgl1-nvidia-glx-ia32, as it depended on ia32-libs (and, as reported by
Andreas [1], can't be built with the multiarchified ia32-libs). So
removing ia32-libs is the cause for this breakage. libxvmc was not part
of ia32-libs so libgl1-nvidia-glx-ia32 lacked that dependency, but now
that we must use libgl1-nvidia-glx:i386 and the proper automatically
generated dependencies are used for all architectures, libxvmc is needed
in a foreign-arch version as well, in one way or another.
Kind regards,
Ralf
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684871#27
Reply to: