newer versions of knetworkmanager require libnl >= 1.0-pre6, and we've also noticed that our existing knetworkmanager builds against libnl-1.0-pre5 experience some pretty drastic memory leaks that are presumably fixed in newer releases of libnl. Just checked, libnl-1.0-pre8 is the latest available upstream.
yep, we need to update libnl in F8 and devel and push the libnl-pre8 patch upstream to NM SVN.
and F-7 also?
Well; why? The only reason to update F7's libnl is if F7 gets a 2.6.24 kernel update, which is the whole reason why -pre7 and later are necessary. Note that -pre7 is ABI _in_compatible with earlier releases; so we should have a good reason to push an F7 update other than "it's better" I think.
Does "because it closes a large reported memory leak" not count as a good enough reason?
No. Because we can backport fixes at the maintainer's discretion.
It might be good enough to update. We need to figure out what other packages might use libnl, then make a decision as to whether we can break the API/ABI and require rebuilds of those just to make stuff work for NM/knetworkmanager.
Also consider that knetworkmanger updates are blocked until libnl is updated (to libnl >= 1.0-pre6)
and that there is a memory leak with the current libnl knetworkmanager combination. i have seen knm use 1gb ram as a result
is there a particular reason that you're looking specifically at pre6? From what I see, pre8 is the latest available.
http://mail.kde.org/pipermail/kde-networkmanager/2007-November/000251.html the next release of knetworkmanager for the 0.6.5 branch of NM requires at least pre6
NM currently doesn't work with 2.6.22.9-91.fc7 and libnl-1.0-pre8, erroring out with malformed netlink message errors deep inside libnl somewhere. Until that's figured out, this ain't gonna happen. NetworkManager: <info> Bringing up device eth0 -- Error: Invalid message: type=0x10 length=252 flags=<MULTI> sequence-nr=1196720416 pid=4294963195
Issues resolved, pushing out updates for rawhide and F8.
what about f7
For F7, we have to work a bit harder because NM in F7 uses netlink to receive wireless events too, which libnl does not handle currently.
NetworkManager-0.7.0-0.6.7.svn3204.fc8, libdhcp-1.27-4.fc8, libnl-1.0-0.15.pre8.git20071218.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager libdhcp libnl'
again this bug is for Fedora 7 not Fedora 8
NetworkManager-0.7.0-0.6.7.svn3204.fc8, libdhcp-1.27-4.fc8, libnl-1.0-0.15.pre8.git20071218.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
1.1 for F7: please test knetworkmanager builds against it. Of course NM won't run with this build until I update NM, but it would be useful to know if there are build time issues with knm too. http://koji.fedoraproject.org/koji/taskinfo?taskID=417400
netlabel_tools-0.17-6.fc7, libdhcp-1.24-6.fc7, NetworkManager-0.6.6-1.fc7, libnl-1.1-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update netlabel_tools libdhcp NetworkManager libnl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-2346
netlabel_tools-0.17-6.fc7, libdhcp-1.24-6.fc7, NetworkManager-0.6.6-1.fc7, libnl-1.1-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.