[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Multiarch in Debian unstable

On Tue, Jun 28, 2011 at 10:58:47AM +0200, Joachim Breitner wrote:
> Am Montag, den 27.06.2011, 11:54 +0100 schrieb Steve Langasek:
> > Next steps for maintainers
> > ==========================
> > 
> > If you are a maintainer of a shared library package, you can convert it to
> > multiarch today following the instructions in the Debian wiki:
> > 
> >   http://wiki.debian.org/Multiarch/Implementation
> > 
> > If you have any questions about the multiarchification of libraries, please
> > don't hesitate to ask on debian-devel@lists.debian.org.

> I think I have successfully converted libnss-gw-name.¹ But it depends on
> libnl, which has not been converted, which would result in this:

> $ ldd debian/libnss-gw-name/./usr/lib/x86_64-linux-gnu/libnss_gw_name.so.2
> 	linux-vdso.so.1 =>  (0x00007fffcf558000)
> 	libnl.so.1 => /usr/lib/libnl.so.1 (0x00007f6fce913000)
> 	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6fce590000)
> 	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6fce30d000)
> 	/lib64/ld-linux-x86-64.so.2 (0x00007f6fced8c000)

> Does this mean that I should wait and add a Depends on the new libnl
> version once it comes out? Or will my package just not be
> foreign-installable until libnl upgrades, in which case everything works
> smoothly without changes or uploads from my side?

The latter - it's fine to convert these in parallel, with each individual
package only becoming foreign-installable once the dependencies are

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@ubuntu.com                                     vorlon@debian.org

Reply to: