Bug 2272102

Summary:	upx-4.2.3 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	upx	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	gwync
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	upx-4.2.3-1.fc39 upx-4.2.3-1.el8 upx-4.2.3-1.fc38 upx-4.2.3-1.el9 upx-4.2.3-1.fc40	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-06 01:41:20 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 2024-03-28 20:13:44 UTC

Releases retrieved: 4.2.3
Upstream release that is considered latest: 4.2.3
Current version/release in rawhide: 4.2.2-2.fc40
URL: https://upx.github.io/

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


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

Comment 1 Fedora Update System 2024-03-28 20:55:59 UTC

FEDORA-2024-fb0dbe3373 (upx-4.2.3-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-fb0dbe3373

Comment 2 Fedora Update System 2024-03-29 02:23:57 UTC

FEDORA-2024-fb0dbe3373 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-fb0dbe3373`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-fb0dbe3373

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

Comment 3 Fedora Update System 2024-03-29 02:55:27 UTC

FEDORA-2024-df5322cd61 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-df5322cd61`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-df5322cd61

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

Comment 4 Fedora Update System 2024-04-03 19:22:27 UTC

FEDORA-2024-70ee97033b (upx-4.2.3-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-70ee97033b

Comment 5 Fedora Update System 2024-04-03 19:30:29 UTC

FEDORA-EPEL-2024-88820507e6 (upx-4.2.3-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-88820507e6

Comment 6 Fedora Update System 2024-04-03 19:30:30 UTC

FEDORA-EPEL-2024-c6577bc2ed (upx-4.2.3-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c6577bc2ed

Comment 7 Fedora Update System 2024-04-04 01:37:56 UTC

FEDORA-2024-70ee97033b 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-2024-70ee97033b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-70ee97033b

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

Comment 8 Fedora Update System 2024-04-04 01:45:22 UTC

FEDORA-EPEL-2024-c6577bc2ed 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-c6577bc2ed

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

Comment 9 Fedora Update System 2024-04-04 01:52:03 UTC

FEDORA-EPEL-2024-88820507e6 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-88820507e6

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

Comment 10 Fedora Update System 2024-04-06 01:41:20 UTC

FEDORA-2024-fb0dbe3373 (upx-4.2.3-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2024-04-12 01:01:26 UTC

FEDORA-EPEL-2024-88820507e6 (upx-4.2.3-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.

Comment 12 Fedora Update System 2024-04-12 01:14:04 UTC

FEDORA-2024-70ee97033b (upx-4.2.3-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-04-12 01:22:59 UTC

FEDORA-EPEL-2024-c6577bc2ed (upx-4.2.3-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.

Comment 14 Fedora Update System 2024-04-19 21:24:28 UTC

FEDORA-2024-df5322cd61 (upx-4.2.3-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.