[Pkg-utopia-maintainers] Bug#631836: Bug#631836: Please transition avahi for multiarch

[Steve Langasek]

On Wed, Jun 29, 2011 at 04:31:55AM +0200, Michael Biebl wrote:
> Am 29.06.2011 03:46, schrieb Michael Biebl:
> > Hi Steve,
> > 
> > Am 27.06.2011 18:18, schrieb Steve Langasek:
> >> Source: avahi
> >> Version: 0.6.30-3
> >> Tags: patch
> >> User: ubuntu-devel at lists.ubuntu.com
> >> Usertags: origin-ubuntu oneiric ubuntu-patch
> >>
> >> Hi folks,
> >>
> >> Please find attached a patch to avahi to transition it to use of the
> >> multiarch library paths as described at
> >> <http://wiki.debian.org/Multiarch/Implementation>.  This patch has been
> >> applied and is being used successfully in Ubuntu 11.04, and should be safe
> >> to apply in Debian now that multiarch has been bootstrapped there.
> >>
> >> Would be great if you could apply this patch to the Debian package, so we
> >> can whittle away ia32-libs for wheezy. :)

> > Unfortunately this patch does not apply on top of 0.6.30-3.
> > Could you send me an updated patch, please?

Gah, sorry for that :/

> I did some manual mangling and committed the patch as
> http://anonscm.debian.org/gitweb/?p=pkg-utopia/avahi.git;a=commitdiff;h=b35783ce93bf4a91782087b37ef737dbe82a698a

> I would very much appreciate if you could look over that.

Yes, that looks ok.

> What I don't understand yet is, why avahi-daemon is Multi-Arch: foreign
> whereas all other avahi-* binary packages aren't.

In general, I think we should only add Multi-Arch: foreign to packages which
have reverse-dependencies that are Multi-Arch: same; otherwise it's
technically correct but uninteresting metadata.  avahi-daemon has
libnss-mdns as a reverse-dependency, so it needs to declare itself
Multi-Arch: foreign to let those reverse-deps be multiarch co-installable
with only one instance of the daemon.

> Could you also explain to me (or point me to the relevant documentation)
> why python-avahi changed from arch all to arch any.

Sorry for the lack of documentation.  Unfortunately I didn't even document
it well enough for myself locally, so I'm struggling to remember now why I
did this.  I *think* it had to do with the fact that libavahi-common-data is
Architecture: any / Multi-Arch: same, because the gdbm database files are
not architecture-independent, and you need a python-gdbm that corresponds to
the architecture of libavahi-common-data that you have installed.  But since
you can't actually install more than one copy of python on your system at a
time, and python-avahi depends on python (obviously), I can't now work out
after the fact why I thought this was needed.  It may just be a bug in my
thinking at the time - if everything installs ok using an Architecture: all
python-avahi, then feel free to drop this change.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20110629/11e2fca5/attachment.pgp>