Re: Depends: libfoo:foreign ???
On Thu, May 09, 2013 at 08:43:22AM +0200, Niels Thykier wrote:
> On 2013-05-09 07:56, Paul Wise wrote:
> > On Thu, May 9, 2013 at 1:08 PM, Andreas Beckmann wrote:
> >> I just noticed that we have the first amd64 package in the archive that
> >> has dependencies on :i386 qualified libraries:
> >> Package: teamspeak-client
> > It appears that will block it from reaching testing:
> Indeed, Britney does not support those annotations (at the moment?). To
> avoid issues with this kind of thing, we made her consider such
> dependencies for unsatisfiable.
> So for now anything using that form in Depends or Pre-Depends will not
> reach testing (without manual intervention from the Release team and I
> am not sure how likely "we" are to do that).
> > http://packages.qa.debian.org/t/teamspeak-client.html
> > The proper thing to do would be to remove the amd64 package entirely
> > and have users install the i386 version.
> Indeed, I believe that should work.
It is the indended solution. If it doesn't work then that is a bug and
needs to be fixed.
>  Though she ignores them in Recommends/Suggests and possibly also in
A Depends like in this case is never right since it mixes biarch
(libc6-i386) packages with multiarch (libfoo:i386).
I would say that a foreign dependency on a library is never right. If
the source compiles binaries for the foreign arch then the package
should be build on the foreign arch directly. Period.
Also, iirc, the use of foreign dependencies is only supposed to be on
packages with Multi-Arch: allowed. This is for interpreters and
plugins/lib bindings where the normal automatic method can't work. So
maybe DAK could be made more restrictive here.