Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
Andrey Ponomarenko wrote: The compatibility report between 1.1 and 3.2.2 versions of libnl generated by abi-compliance-checker [1] tool (see attachment: abi_compat_report.html) may be of help. [1] http://forge.ispras.ru/projects/abi-compliance-checker now back online: *API changes/compatibility test results for the libnl library* http://upstream-tracker.org/versions/libnl.html thanks Andrey. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On Tue, Nov 08, 2011 at 02:13:09PM -0500, Stephen Gallagher wrote: On Tue, 2011-11-08 at 12:52 -0600, Dan Williams wrote: It certainly has a different soname, so yeah, we can have a -compat package. But that would still mean a ton of stuff busted for rebuilds while packages get fixed up. A few upstream packages already work with libnl2, and the delta between 2 and 3 is hugely smaller than from 1 to 3. I don't think rebuilds are as big an issue as broken compatibility. I'd recommend carrying compat-libnl1 for at least one Fedora release while we port the affected applications to libnl 3. Hi, Dan, have you decided on whether there will be a compat library? Thanks! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On 11/09/2011 12:08 AM, Dan Williams wrote: On Tue, 2011-11-08 at 22:21 +0100, Jiri Moskovcak wrote: On 11/08/2011 06:10 PM, Dan Williams wrote: Hi, At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* - does it mean NM in F17 will handle bridging? That the current plan, yes. But even if it didn't, we'd probably still - that would be awesome want to bump libnl. - sure, I didn't want it to sound like you have to support bridging if you bump to v3 ;) Thank you, Jirka Dan mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Heads up: bumping libnl to v3 in rawhide/F17 soon
Hi, At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
Dan Williams (d...@redhat.com) said: At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Can we ship libnl-1.1 as a parallel-installed compatibility library, at least in the short term? Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On Tue, 2011-11-08 at 12:41 -0500, Bill Nottingham wrote: Dan Williams (d...@redhat.com) said: At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Can we ship libnl-1.1 as a parallel-installed compatibility library, at least in the short term? I believe libnl3 *might* be parallel installable; I've had conversations with tgraf about how to make it so. I'll investigate once the upstream git repo comes back online. In the past the problem was mainly with the devel package and the location of the headers and the .pc file (ie, it was always /usr/include/netlink no matter what the version of libnl) but I believe Thomas fixed that earlier this summer for libnl3. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
Dan Williams (d...@redhat.com) said: I believe libnl3 *might* be parallel installable; I've had conversations with tgraf about how to make it so. I'll investigate once the upstream git repo comes back online. In the past the problem was mainly with the devel package and the location of the headers and the .pc file (ie, it was always /usr/include/netlink no matter what the version of libnl) but I believe Thomas fixed that earlier this summer for libnl3. I'm less concerned about the old version being around to develop against - I'd just rather not have the whole repo hae issues while people are still porting. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On Tue, 2011-11-08 at 13:05 -0500, Bill Nottingham wrote: Dan Williams (d...@redhat.com) said: I believe libnl3 *might* be parallel installable; I've had conversations with tgraf about how to make it so. I'll investigate once the upstream git repo comes back online. In the past the problem was mainly with the devel package and the location of the headers and the .pc file (ie, it was always /usr/include/netlink no matter what the version of libnl) but I believe Thomas fixed that earlier this summer for libnl3. I'm less concerned about the old version being around to develop against - I'd just rather not have the whole repo hae issues while people are still porting. It certainly has a different soname, so yeah, we can have a -compat package. But that would still mean a ton of stuff busted for rebuilds while packages get fixed up. A few upstream packages already work with libnl2, and the delta between 2 and 3 is hugely smaller than from 1 to 3. repoquery --whatrequires libnl for F16 says: NetworkManager (fixed upstream) anaconda crda (wifi regulatory database) dropwatch hostapd (upstream works with libnl2) ipvsadm iw (upstream works with libnl2) keepalived kismet knemo libvirt lldpad netcf netlabel_tools powertop python-ethtool quota-nld sssd wimax wimax-tools wpa_supplicant (upstream works with libnl2) Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On Tue, 2011-11-08 at 12:52 -0600, Dan Williams wrote: It certainly has a different soname, so yeah, we can have a -compat package. But that would still mean a ton of stuff busted for rebuilds while packages get fixed up. A few upstream packages already work with libnl2, and the delta between 2 and 3 is hugely smaller than from 1 to 3. I don't think rebuilds are as big an issue as broken compatibility. I'd recommend carrying compat-libnl1 for at least one Fedora release while we port the affected applications to libnl 3. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On 11/08/2011 06:10 PM, Dan Williams wrote: Hi, At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* - does it mean NM in F17 will handle bridging? mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On Tue, 2011-11-08 at 22:21 +0100, Jiri Moskovcak wrote: On 11/08/2011 06:10 PM, Dan Williams wrote: Hi, At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* - does it mean NM in F17 will handle bridging? That the current plan, yes. But even if it didn't, we'd probably still want to bump libnl. Dan mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: bumping libnl to v3 in rawhide/F17 soon
On 11/08/2011 09:10 PM, Dan Williams wrote: Hi, At some point here I'm going to bump libnl to version 3 in rawhide. The libnl 1.1 we use today is way out of date and we want version 3 for the enhanced capabilities like bonding, bridging, vlan, etc. This *does* mean an API break, so packages will need to be updated for libnl3. The majority of the changes are simply function renames and changed structure names. There's no porting guide that I'm aware of but I and others working on NetworkManager have spent time porting from libnl1.1 to libnl3 this cycle so we can point you in the right direction. The compatibility report between 1.1 and 3.2.2 versions of libnl generated by abi-compliance-checker [1] tool (see attachment: abi_compat_report.html) may be of help. [1] http://forge.ispras.ru/projects/abi-compliance-checker -- Andrey Ponomarenko Mandriva Linux/ROSA Laboratory abi_compat_report.html.tar.gz Description: GNU Zip compressed data -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
