According to more restrictive libdb licence policy exists effort to remove libdb's dependencies. Iproute package is now built with libdb requirement(due to arpd tool), it seems that arpd doesn't support other database.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
What's the proposed solution? splitting arpd into a sub-package? Dropping it? The tool uses Berkeley DB. Is that not commonly used anymore? What alternative do other tools use instead? Or is there a replacement for libdb package?
Hi Phil, most of other tools supports more then only one database (BerkeleyDB), so there is possibility to use another backend database. But in case of arpd I don't see any good solution. Support from upstream we can't expect. From communication with upstrem turned out, that arpd is rarely used, rarely tested and no changes have occurred in 10 years. In this situation would be the best solution to create a patch for support another database. Now I can't say if some libdb-compat will preserve, but we would like to remove all libdb packages and it's dependencies.
(In reply to Filip Januš from comment #3) > Hi Phil, > most of other tools supports more then only one database (BerkeleyDB), so > there is possibility to use another backend database. > But in case of arpd I don't see any good solution. Support from upstream we > can't expect. From communication with upstrem turned out, that arpd is > rarely used, rarely tested and no changes > have occurred in 10 years. > > In this situation would be the best solution to create a patch for support > another database. Now I can't say if some libdb-compat will preserve, but we > would like to remove all libdb packages and it's dependencies. That doesn't answer my question, sorry. What's wrong with BDB, are you about to remove it from Fedora or is it just about libdb? If the latter is the case, what alternative is there to interface against BDB? Thanks, Phil
If you are asking for proposed solution. From my point of view is the simplest solution edit code of arpd and change usage of libdb to some different database or remove arpd. Because I don't know about database with compatible API with BDB.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.