Bug 2103115

Summary:	rbanffy-3270-fonts-3.0.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	rbanffy-3270-fonts	Assignee:	Davide Cavalca <davide>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	davide
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rbanffy-3270-fonts-3.0.0-1.fc37 rbanffy-3270-fonts-3.0.0-1.fc36 rbanffy-3270-fonts-3.0.0-1.fc35	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-14 15:36:17 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-07-01 13:23:38 UTC

Releases retrieved: 3.0.0
Upstream release that is considered latest: 3.0.0
Current version/release in rawhide: 2.3.1-2.fc36
URL: https://github.com/rbanffy/3270font

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/rbanffy-3270-fonts

Comment 1 Fedora Update System 2022-07-14 15:34:01 UTC

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

Comment 2 Fedora Update System 2022-07-14 15:36:17 UTC

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

Comment 3 Fedora Update System 2022-07-14 16:39:03 UTC

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

Comment 4 Fedora Update System 2022-07-14 16:44:47 UTC

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

Comment 5 Fedora Update System 2022-07-15 01:20:50 UTC

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

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

Comment 6 Fedora Update System 2022-07-15 02:09:17 UTC

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

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

Comment 7 Fedora Update System 2022-07-23 01:59:45 UTC

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

Comment 8 Fedora Update System 2022-07-23 02:27:14 UTC

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