Red Hat Bugzilla – Bug 837169
acpid should use libnl
Last modified: 2015-02-18 08:44:46 EST
acpid appears to use a bundled version of libnl (libnetlink). Is it possible for acpid to use the separately-packaged libnl, or even better, libnl3?
It seems to use its own non-compatible implementation, thus currently it is not possible to switch to libnl/libnl3. The code has to be rewritten, I will file RFE ticket upstream.
This is on the TODO for acpid. It's not very high priority, though. Is this causing trouble with the normal functioning of acpid? Or is there trouble on the horizon?
I'm sure it works fine, it's just less-than-ideal. Maybe if you could describe the shortcomings in the standard version that led you to bundle and customize it, Jaroslav or myself might be able to produce a patch against acpid or upstream libnl3 that lets acpid drop its version.
There are two possible reasons that I bundled netlink support with acpid. First, it may have been that there was no official libnl at the time, so I took the unofficial one and incorporated it into the code for acpid. The second possibility is that I was unaware of the existence of a standard libnl. Either way it has nothing to do with shortcomings in the standard version.
A patch to remedy this would be great.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.