Bug 2255164

Summary: dhcpcd-10.0.6 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: dhcpcdAssignee: Petr Menšík <pemensik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mosvald, pemensik, pzacik
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dhcpcd-10.0.6-1.fc40 dhcpcd-10.0.6-1.fc38 dhcpcd-10.0.6-1.fc39 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-12-21 18:36:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2023-12-18 23:33:55 UTC
Releases retrieved: 10.0.6
Upstream release that is considered latest: 10.0.6
Current version/release in rawhide: 10.0.5-1.fc40
URL: https://roy.marples.name/projects/dhcpcd

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://docs.fedoraproject.org/en-US/package-maintainers/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/11429/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/dhcpcd

Comment 1 Fedora Update System 2023-12-21 14:23:46 UTC
FEDORA-2023-20b3082b67 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-20b3082b67

Comment 2 Fedora Update System 2023-12-21 14:50:23 UTC
FEDORA-2023-1874834244 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1874834244

Comment 3 Fedora Update System 2023-12-21 15:28:09 UTC
FEDORA-2023-92b6bcca39 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-92b6bcca39

Comment 4 Fedora Update System 2023-12-21 18:36:10 UTC
FEDORA-2023-20b3082b67 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2023-12-22 02:52:19 UTC
FEDORA-2023-1874834244 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-2023-1874834244`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1874834244

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

Comment 6 Fedora Update System 2023-12-22 03:39:15 UTC
FEDORA-2023-92b6bcca39 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-92b6bcca39`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-92b6bcca39

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

Comment 7 Fedora Update System 2023-12-30 01:30:43 UTC
FEDORA-2023-92b6bcca39 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2024-01-06 02:01:26 UTC
FEDORA-2023-1874834244 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.