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
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.
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
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
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
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,
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
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
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
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
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,
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
12 matches
Mail list logo
