Bug 2087917 - lynis-3.0.8 is available
Summary: lynis-3.0.8 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lynis
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Othman Madjoudj
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-18 14:25 UTC by Upstream Release Monitoring
Modified: 2022-07-22 17:51 UTC (History)
4 users (show)

Fixed In Version: lynis-3.0.8-1.fc35 lynis-3.0.8-1.fc36 lynis-3.0.8-1.el9 lynis-3.0.8-1.el8 lynis-3.0.8-1.el7
Clone Of:
Environment:
Last Closed: 2022-07-22 05:09:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 3.0.8 (#2087917) (946 bytes, patch)
2022-05-18 14:25 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2022-05-18 14:25:11 UTC
Latest upstream release: 3.0.8
Current version/release in rawhide: 3.0.7-1.fc36
URL: http://cisofy.com/downloads/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


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


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/1862/

Comment 1 Upstream Release Monitoring 2022-05-18 14:25:18 UTC
Created attachment 1880921 [details]
Update to 3.0.8 (#2087917)

Comment 2 Upstream Release Monitoring 2022-05-18 14:30:58 UTC
the-new-hotness/release-monitoring.org's scratch build of lynis-3.0.8-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=87204912

Comment 3 John Dodson 2022-05-19 02:49:46 UTC
Is there an ETA on this making it to the Repos for 35 & then 36?

Comment 4 Fedora Update System 2022-07-13 18:57:33 UTC
FEDORA-2022-17deaa8319 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-17deaa8319

Comment 5 Fedora Update System 2022-07-13 18:57:34 UTC
FEDORA-EPEL-2022-64c098e1c9 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-64c098e1c9

Comment 6 Fedora Update System 2022-07-13 18:57:35 UTC
FEDORA-EPEL-2022-0981c93ab8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0981c93ab8

Comment 7 Fedora Update System 2022-07-13 18:57:37 UTC
FEDORA-2022-75db14221a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-75db14221a

Comment 8 Fedora Update System 2022-07-14 01:18:58 UTC
FEDORA-2022-17deaa8319 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-17deaa8319`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-17deaa8319

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-07-14 01:19:42 UTC
FEDORA-2022-75db14221a has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-75db14221a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-75db14221a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-07-14 02:03:46 UTC
FEDORA-EPEL-2022-385d397ac9 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-2022-385d397ac9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-07-14 02:03:57 UTC
FEDORA-EPEL-2022-0981c93ab8 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-2022-0981c93ab8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2022-07-14 02:09:35 UTC
FEDORA-EPEL-2022-64c098e1c9 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-64c098e1c9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2022-07-22 05:09:59 UTC
FEDORA-2022-75db14221a has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-07-22 17:15:56 UTC
FEDORA-2022-17deaa8319 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-07-22 17:16:25 UTC
FEDORA-EPEL-2022-0981c93ab8 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2022-07-22 17:24:08 UTC
FEDORA-EPEL-2022-385d397ac9 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2022-07-22 17:51:25 UTC
FEDORA-EPEL-2022-64c098e1c9 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, 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.