Bug 2020039

Summary:	et-6.1.9 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	et	Assignee:	Jason Gauci <jgmath2000>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	extras-orphan, filbranden, jgmath2000
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	et-6.1.9-1.el8 et-6.1.9-1.fc35 et-6.1.9-1.fc34	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-05 00:36: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 2021-11-03 22:55:11 UTC

Latest upstream release: 6.1.9
Current version/release in rawhide: 6.1.8-1.fc35
URL: https://mistertea.github.io/EternalTerminal/

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

Comment 1 Fedora Update System 2021-11-04 22:40:00 UTC

FEDORA-EPEL-2021-5600503dc1 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-5600503dc1

Comment 2 Fedora Update System 2021-11-04 22:40:06 UTC

FEDORA-2021-532fcdde8a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-532fcdde8a

Comment 3 Fedora Update System 2021-11-04 22:40:11 UTC

FEDORA-2021-808fab651c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-808fab651c

Comment 4 Fedora Admin user for bugzilla script actions 2021-11-05 00:04:56 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Update System 2021-11-05 00:36:20 UTC

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

Comment 6 Fedora Update System 2021-11-05 01:22:35 UTC

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

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

Comment 7 Fedora Update System 2021-11-05 01:38:28 UTC

FEDORA-2021-808fab651c has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-808fab651c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-808fab651c

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

Comment 8 Fedora Update System 2021-11-13 01:06:49 UTC

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

Comment 9 Fedora Update System 2021-11-13 01:13:09 UTC

FEDORA-2021-808fab651c has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.