Lynis needs updating in FC40 - in, https://bugzilla.redhat.com/show_bug.cgi?id=2087917 I whined about version updates - deja-vu... running lynis elicits the following message... Program update status... UPDATE AVAILABLE =============================================================================== Lynis update available =============================================================================== Current version is more than 4 months old Current version : 311 Latest version : 312 Please update to the latest version. New releases include additional features, bug fixes, tests, and baselines. Download the latest version: Packages (DEB/RPM) - https://packages.cisofy.com Website (TAR) - https://cisofy.com/downloads/ GitHub (source) - https://github.com/CISOfy/lynis =============================================================================== Reproducible: Always Steps to Reproduce: 1. Run lynis on FC40 (3.1.1-1.fc40) 2. 3. Actual Results: Update message (see above) & old bugs still present. Expected Results: No update message & fixed bugs. Is there a "working" method for checking updates for packages such as lynis? What is the lynis -> FC version timing schedule? (for the packager?)
FEDORA-2024-0071696ab1 (lynis-3.1.2-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0071696ab1
FEDORA-2024-ff8c484cbc (lynis-3.1.2-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ff8c484cbc
FEDORA-EPEL-2024-6dff8fabf2 (lynis-3.1.2-1.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6dff8fabf2
FEDORA-EPEL-2024-0cf47ee5a9 (lynis-3.1.2-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-0cf47ee5a9
FEDORA-2024-84e6aff552 (lynis-3.1.2-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-84e6aff552
FEDORA-2024-ff8c484cbc has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ff8c484cbc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ff8c484cbc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-0cf47ee5a9 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-0cf47ee5a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-6dff8fabf2 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6dff8fabf2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-84e6aff552 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-84e6aff552` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-84e6aff552 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0071696ab1 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0071696ab1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0071696ab1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-84e6aff552 (lynis-3.1.2-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-ff8c484cbc (lynis-3.1.2-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-0071696ab1 (lynis-3.1.2-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-0cf47ee5a9 (lynis-3.1.2-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-6dff8fabf2 (lynis-3.1.2-1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
Thanks folks, greatly appreciated (it's now in the repos). But how do we keep it (FC repo version) up to date? Other than waiting for the, "Current version is more than 4 months old" message that Lynis emits?
I have reported, upstream at https://github.com/CISOfy/lynis/issues/1562 that the version of lynis now in FC40 (lynis-3.1.2-1.fc40) now emits the following, kadmin.local: unable to get default realm when kerberos is not enabled/used. Hopefully it will be fixed soon (probably just an error message rediretion problem). But when a new version is issued, how can we get it included in the distribution/repos as early after release as possible? (This is effectively a repeat of my question in my last comment above)
When a new version is released, an automated process files a bug in Bugzilla requesting an update. The maintainers get an email notification of that, and that currently includes myself. Then we do local test builds, and submit updates. Once submitted, builds will sit in updates-testing until they have been there 1 week, or have received enough positive karma from testers.
OK thanks - hopefully that will avoid the "4 Months old" message.
That is my goal. :)