Bug 2039604 - libreswan-4.6 is available
Summary: libreswan-4.6 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreswan
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 03:38 UTC by Upstream Release Monitoring
Modified: 2022-01-20 14:53 UTC (History)
2 users (show)

Fixed In Version: libreswan-4.6-1.fc36 libreswan-4.6-1.fc34 libreswan-4.6-1.fc35
Clone Of:
Environment:
Last Closed: 2022-01-12 04:06:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-366 0 None None None 2022-01-12 03:39:18 UTC

Description Upstream Release Monitoring 2022-01-12 03:38:14 UTC
Latest upstream release: 4.6
Current version/release in rawhide: 4.5-1.fc36
URL: https://libreswan.org/

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/1715/

Comment 1 Upstream Release Monitoring 2022-01-12 03:47:10 UTC
the-new-hotness/release-monitoring.org's scratch build of libreswan-4.6-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=81125535

Comment 2 Fedora Update System 2022-01-12 04:03:50 UTC
FEDORA-2022-8c63bacf90 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8c63bacf90

Comment 3 Fedora Update System 2022-01-12 04:06:58 UTC
FEDORA-2022-8c63bacf90 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2022-01-12 14:09:32 UTC
FEDORA-2022-42e0892147 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-42e0892147

Comment 5 Fedora Update System 2022-01-12 18:01:31 UTC
FEDORA-2022-a4bca77f88 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4bca77f88

Comment 6 Fedora Update System 2022-01-13 01:11:38 UTC
FEDORA-2022-42e0892147 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 --advisory=FEDORA-2022-42e0892147`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-42e0892147

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

Comment 7 Fedora Update System 2022-01-13 01:50:19 UTC
FEDORA-2022-a4bca77f88 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a4bca77f88`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4bca77f88

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

Comment 8 Fedora Update System 2022-01-20 08:32:50 UTC
FEDORA-2022-a4bca77f88 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-01-20 14:53:03 UTC
FEDORA-2022-42e0892147 has been pushed to the Fedora 35 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.