Bug 963111 - libnl3-3.2.24 is available
Summary: libnl3-3.2.24 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libnl3
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-15 07:32 UTC by Upstream Release Monitoring
Modified: 2014-02-08 05:09 UTC (History)
5 users (show)

Fixed In Version: libnl3-3.2.24-1.fc20
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-08 05:09:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2013-05-15 07:32:52 UTC
Latest upstream release: 3.2.22
Current version in Fedora Rawhide: 3.2.21
URL: http://www.infradead.org/~tgr/libnl/files/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Hiroaki KAWAI 2013-07-24 08:05:42 UTC
+1 for update to 3.2.22 because current 3.2.11 has a bug that does not expose NL_ACT_* definition in <netlink/cache.h>

https://github.com/tgraf/libnl/commit/2005c2ecacdf5e1ba5be630c85f1288eeb8ad6af

Comment 2 Hiroaki KAWAI 2013-07-24 08:06:11 UTC
+1 for update to 3.2.22 because current 3.2.21 has a bug that does not expose NL_ACT_* definition in <netlink/cache.h>

https://github.com/tgraf/libnl/commit/2005c2ecacdf5e1ba5be630c85f1288eeb8ad6af

Comment 3 Dan Williams 2013-07-25 21:21:22 UTC
Unfortunately 3.2.22 also has a bug where it doesn't properly clear the link address family data when calling rtnl_link_set_address_family() which causes a double-free :(

Comment 4 Paul Wouters 2013-09-24 15:05:46 UTC
I built 3.2.22 with the upstream patch for the double-free. Let me know if you're okay with releasing it as an update.

Comment 5 Thomas Graf 2013-10-07 23:53:18 UTC
(In reply to Paul Wouters from comment #4)
> I built 3.2.22 with the upstream patch for the double-free. Let me know if
> you're okay with releasing it as an update.

I'm fine with that.

Comment 6 Upstream Release Monitoring 2013-10-31 06:41:22 UTC
Latest upstream release: 3.2.23
Current version/release in Fedora Rawhide: 3.2.22-2.fc21
URL: http://www.infradead.org/~tgr/libnl/files/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 7 Upstream Release Monitoring 2014-01-22 08:54:36 UTC
Latest upstream release: 3.2.24
Current version/release in Fedora Rawhide: 3.2.22-2.fc21
URL: http://www.infradead.org/~tgr/libnl/files/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 8 Fedora Update System 2014-01-23 15:19:17 UTC
libnl3-3.2.24-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/libnl3-3.2.24-1.fc20

Comment 9 Fedora Update System 2014-01-24 07:45:16 UTC
Package libnl3-3.2.24-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libnl3-3.2.24-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1436/libnl3-3.2.24-1.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2014-02-08 05:09:04 UTC
libnl3-3.2.24-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.