Bug 2304673

Summary:	perl-Test-Harness-3.50 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	perl-Test-Harness	Assignee:	Jitka Plesnikova <jplesnik>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jplesnik, mspacek, paul, perl-devel, ppisar
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-Test-Harness-3.50-1.fc42 perl-Test-Harness-3.50-1.fc41 perl-Test-Harness-3.50-1.fc40	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-08-15 14:10:47 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:
Bug Depends On:
Bug Blocks:	2232293, 2301034

Description Upstream Release Monitoring 2024-08-13 18:35:08 UTC

Releases retrieved: 3.50
Upstream release that is considered latest: 3.50
Current version/release in rawhide: 3.48-512.fc41
URL: http://metacpan.org/dist/Test-Harness/

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Test-Harness

Comment 1 Fedora Update System 2024-08-15 14:01:02 UTC

FEDORA-2024-b55f3ba501 (perl-Test-Harness-3.50-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b55f3ba501

Comment 2 Fedora Update System 2024-08-15 14:10:47 UTC

FEDORA-2024-b55f3ba501 (perl-Test-Harness-3.50-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2024-08-15 14:14:12 UTC

FEDORA-2024-020085fc1a (perl-Test-Harness-3.50-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-020085fc1a

Comment 4 Fedora Update System 2024-08-15 14:19:36 UTC

FEDORA-2024-020085fc1a (perl-Test-Harness-3.50-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2024-08-15 14:20:21 UTC

FEDORA-2024-43f9b47244 (perl-Test-Harness-3.50-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-43f9b47244

Comment 6 Paul Howarth 2024-08-15 15:11:36 UTC

Could you also do an update for Fedora 39? The tests for perl-TAP-Formatter-JUnit fail there too with the current perl-Test-Harness.

Comment 7 Fedora Update System 2024-08-16 02:07:32 UTC

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

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

Comment 8 Fedora Update System 2024-08-24 01:52:58 UTC

FEDORA-2024-43f9b47244 (perl-Test-Harness-3.50-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.