[pkg-wpa-devel] Backports of glib2.0, network-manager, and wpasupplicant

W. Martin Borgert debacle at debian.org
Fri Dec 30 12:25:26 UTC 2011


On 2011-12-30 01:29, Stefan Lippers-Hollmann wrote:
> Backporting just wpasupplicant 0.7.3 to squeeze should be relatively 
> simple (revert to libnl1, drop the udeb), but the exposed DBus ABI 
> expected by network-manager is incompatible, which means a backport 
> could either target squeeze's network-manager XOR wheezy's (XOR 
> backports thereof).

I thought that the new DBus API is supported only by
wpasupplicant >= 0.8? (I should re-read the nm mailing list...)

> Given the implications of these DBus differences 
> and the (r)dependency chain involved, I'd personally recommend to avoid
> introducing this new DBus ABI to squeeze (-backports).

It seems that the danger of breaking all kind of things is high.
I probably will do a "private" backport of all the mentioned
packages, but not upload anything to squeeze-backports. Or use
wheezy...

> Do you observe a particular issue with squeeze's wpasupplicant which
> might be fixable according to the stable release criteria? 

No, I'm interested in the latest network-manager, and if I
understand correctly, this requires a newer wpasupplicant.



More information about the pkg-gnome-maintainers mailing list