Bug 2154123

Summary:	trafficserver-9.1.4-rc0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	trafficserver	Assignee:	Jered Floyd <jered>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jered, zrhoffman
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	trafficserver-9.1.4-1.el9 trafficserver-9.1.4-1.el8 trafficserver-9.1.4-1.fc37 trafficserver-9.1.4-1.fc36 trafficserver-9.1.4-1.el7	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-29 00:36:45 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 2022-12-15 22:18:53 UTC

Releases retrieved: 8.1.6-rc0, 9.1.4-rc0
Upstream release that is considered latest: 9.1.4-rc0
Current version/release in rawhide: 9.1.3-3.fc38
URL: https://trafficserver.apache.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://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/254347/


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

Comment 1 Fedora Update System 2022-12-20 00:48:54 UTC

FEDORA-EPEL-2022-53c9c8c84a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-53c9c8c84a

Comment 2 Fedora Update System 2022-12-20 00:48:55 UTC

FEDORA-EPEL-2022-47a8accb45 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-47a8accb45

Comment 3 Fedora Update System 2022-12-20 00:48:56 UTC

FEDORA-2022-62b61a8542 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-62b61a8542

Comment 4 Fedora Update System 2022-12-20 00:48:57 UTC

FEDORA-EPEL-2022-8362ddfe7c has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8362ddfe7c

Comment 5 Fedora Update System 2022-12-20 00:48:59 UTC

FEDORA-2022-489ea47e69 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-489ea47e69

Comment 6 Fedora Update System 2022-12-21 01:29:45 UTC

FEDORA-EPEL-2022-53c9c8c84a 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-53c9c8c84a

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

Comment 7 Fedora Update System 2022-12-21 01:53:25 UTC

FEDORA-EPEL-2022-47a8accb45 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-47a8accb45

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

Comment 8 Fedora Update System 2022-12-21 02:02:39 UTC

FEDORA-EPEL-2022-8362ddfe7c 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-8362ddfe7c

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

Comment 9 Fedora Update System 2022-12-21 02:26:04 UTC

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

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

Comment 10 Fedora Update System 2022-12-21 02:36:04 UTC

FEDORA-2022-62b61a8542 has been pushed to the Fedora 37 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-62b61a8542`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-62b61a8542

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

Comment 11 Fedora Update System 2022-12-29 00:36:45 UTC

FEDORA-EPEL-2022-53c9c8c84a has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2022-12-29 00:55:30 UTC

FEDORA-EPEL-2022-47a8accb45 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2022-12-29 01:09:34 UTC

FEDORA-2022-62b61a8542 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-12-29 01:15:34 UTC

FEDORA-2022-489ea47e69 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-12-29 01:16:22 UTC

FEDORA-EPEL-2022-8362ddfe7c has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.