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

Re: [pkg-wpa-devel] libnl3 soname change



Am Montag, 19. Dezember 2011, 09:03:47 schrieb Gaudenz Steinlin:
> Hi
> 
> On Sun, 18 Dec 2011 20:16:08 +0100, Heiko Stübner <heiko@sntech.de> wrote:
> > Hi,
> > 
> > Am Donnerstag 15 Dezember 2011, 22:13:43 schrieb Stefan Lippers-Hollmann:
> > > Hi
> > > 
> > > On Thursday 15 December 2011, Joey Hess wrote:
> > > > Heiko Stübner wrote:
> > > > > So the question would be on how to proceed to get this into
> > > > > unstable without breaking to much.
> > > 
> > > [...]
> > > 
> > > I have prepared and tested (for the non-udeb cases, see below) iw[1]
> > > and wpasupplicant[2] in svn now, likewise hostapd[3] will switch to
> > > libnl-3 >= 3.2 (from libnl1) after it gets available in unstable (no
> > > urgency at all).
> > > 
> > > Something seems to be missing for the udeb handling though:
> > > Package: wpasupplicant-udeb
> > > [...]
> > > Depends: libc6-udeb (>= 2.13), libcrypto1.0.0-udeb (>= 1.0.0),
> > > libnl-3-200-udeb (>= 3.2.3), libnl-genl-3-200, busybox-udeb
> > > ^^^^^^^^^^^^^^^^ I'm not overly familiar with udeb specifics, but I
> > > think this is
> > > missing something equivalent to
> > > 
> > > 	DEB_DH_MAKESHLIBS_ARGS_libnl-3-200 := -V"libnl-3-200 (>=
> > > 
> > > $(DEB_UPSTREAM_VERSION))" --add-udeb=$(udeb) in libnl3's debian/rules.
> > 
> > my understanding of udeb handling is also only rudimentary :-)
> > 
> > As I did not split the udeb libnl-genl-3 resides at the moment in
> > libnl-3-200- udeb. The dependencies all have a "-udeb" in its package
> > name, but libnl- genl-3-200 has not. So my guess would be, that a
> > libnl-genl-3-200-udeb is also necessary.
> 
> I'll try to look into the udeb issues but not before Thursday this week.
> If anyone has time to do this before I'm more than happy. If you have
> any specific questions I can answer mails even before.
just as a heads up, libnl3.2.3 is in unstable now ... and provides separate 
udebs for libnl and libnl-genl.

Heiko


Reply to: