* Peter Palfrader [2012-06-24 15:34 +0200]:
> Helmut Grohne schrieb am Freitag, dem 08. Juni 2012:
>
> > The tor package seems to provide an architecture independent interface
> > (i.e. command line and architecture independent network protocols such
> > as socks and ssl). As such it should be marked as Multi-Arch: foreign.
> > In practise that would allow installing the following combination of
> > packages: dpkg:amd64 tor:i386 tor-geoipdb. This set is currently not
> > installable, since the tor dependency on tor-geoipdb needlessly enforces
> > that tor uses the same architecture as dpkg.
>
> The impact of that change, or why it is even needed, is not entirely
> obvious.
weasel noted that tor-dbg exists and depends on tor. Since dpkg
currently handles arch all packages as if they were native for
dependency resolution [1], this leads to this situation:
* tor-dbg requires tor to be installed for the same arch as tor-dbg.
* tor-geoipdb:all should be happy with tor installed for any arch, but
currently depends on tor on the native arch.
According to [2] and in theory, the fix for this bug is:
Package: tor
Architecture: any
Depends: ...
Multi-Arch: allowed
^^^^^^^
Package: tor-dbg
Architecture: any
Depends: tor (= ${binary:Version}), ${misc:Depends}
Package: tor-geoipdb
Architecture: all
Depends: tor:any (>= ${source:Version}), ${misc:Depends}
^^^^
In practice, I think delaying this for after Wheezy as you suggested is
the way to go because:
* debfoster and presumably other programs have no idea about the arch
suffix :any.
* :any is currently neither used in Ubuntu nor in Debian. Introducing
the first package with such a dependency a week before the freeze
even though it is known to break existing tools would hardly be sane.
Regards
Carsten
[1]
https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages
[2]
https://wiki.ubuntu.com/MultiarchSpec#Extended_semantics_of_per-architecture_package_relationships
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
