[arch-dev-public] libnl 2.0 rebuild
So, libnl 2.0 was declared stable in October as I just learned. These packages are compatible with libnl 2.0: - crda - iw - wpa_supplicant - hostapd These packages don't as far as I can see: - libpcap - networkmanager These I didn't check: - kismet - net-snmp - knemo - libvirt - simh Can the respective maintainers find out whether there are patches for libnl 2.0 support? I'd like to do the rebuild on the weekend. If we can't fix all packages, we could put a libnl1 package to [extra]. (If there are no patches, it seems that porting to libnl 2.0 is not that difficult, so we could do it ourselves and submit it)
On 01/13/2011 08:24 PM, Thomas Bächler wrote:
So, libnl 2.0 was declared stable in October as I just learned.
These packages are compatible with libnl 2.0: - crda - iw - wpa_supplicant - hostapd
These packages don't as far as I can see: - libpcap - networkmanager
nm doesn't support libnl 2.0 even in master.
These I didn't check: - kismet - net-snmp - knemo - libvirt - simh
Can the respective maintainers find out whether there are patches for libnl 2.0 support? I'd like to do the rebuild on the weekend. If we can't fix all packages, we could put a libnl1 package to [extra].
+1 -- Ionuț
Am 13.01.2011 19:46, schrieb Ionuț Bîru:
nm doesn't support libnl 2.0 even in master.
I think I'll port it and submit them a patch. From what I could see in iw and crda, this is rather easy.
Am 13.01.2011 19:24, schrieb Thomas Bächler:
So, libnl 2.0 was declared stable in October as I just learned.
These packages are compatible with libnl 2.0: - crda - iw - wpa_supplicant - hostapd
These seem to be okay, although I didn't try hostapd yet.
These packages don't as far as I can see: - libpcap
This one was easy.
- networkmanager
I definitely can't fix networkmanager. Or I could, but it would take me all day, at least.
These I didn't check: - kismet - net-snmp - knemo - libvirt - simh
I was able to fix net-snmp, didn't look at the rest yet. Seeing as I can't fix networkmanager, should I introduce a libnl1 package to extra and build everything against that? Or should I still patch the ones I can patch?
On Sat, Jan 15, 2011 at 11:45 AM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 13.01.2011 19:24, schrieb Thomas Bächler:
So, libnl 2.0 was declared stable in October as I just learned.
These packages are compatible with libnl 2.0: - crda - iw - wpa_supplicant - hostapd
These seem to be okay, although I didn't try hostapd yet.
These packages don't as far as I can see: - libpcap
This one was easy.
- networkmanager
I definitely can't fix networkmanager. Or I could, but it would take me all day, at least.
These I didn't check: - kismet - net-snmp - knemo - libvirt - simh
I was able to fix net-snmp, didn't look at the rest yet. Seeing as I can't fix networkmanager, should I introduce a libnl1 package to extra and build everything against that? Or should I still patch the ones I can patch?
I'm trying to port NetworkManager. Can we set up the rebuild in [staging]?
Am 13.01.2011 19:24, schrieb Thomas Bächler:
So, libnl 2.0 was declared stable in October as I just learned.
These packages are compatible with libnl 2.0: - crda - iw - wpa_supplicant - hostapd
These packages don't as far as I can see: - libpcap - networkmanager
These I didn't check: - kismet - net-snmp - knemo - libvirt - simh
I am uploading i686 packages for the following to testing: - libnl - iw - crda - wpa_supplicant - libpcap (with upstream patch) - net-snmp (my own patch) Jan Steffens is trying to fix networkmanager, but this is HUGE. - hostapd is easy, just need an option for libnl2 in .config (see SVN for wpa_supplicant) - kismet looks easy enough to fix - I forgot about libvirt, but iirc it wasn't that hard - No idea about knemo - simh shouldn't even link to libnl, no idea why it does.
participants (3)
-
Ionuț Bîru
-
Jan Steffens
-
Thomas Bächler