Bug 2132164

Summary:	gnome-text-editor-43.1 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	gnome-text-editor	Assignee:	Kalev Lember <klember>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	fzatlouk, gnome-sig, klember, link, ngompa13
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedFreezeException
Fixed In Version:	gnome-text-editor-43.1-2.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-10 14:22:33 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:	2009540

Description Upstream Release Monitoring 2022-10-04 20:17:35 UTC

Releases retrieved: 43.1
Upstream release that is considered latest: 43.1
Current version/release in rawhide: 43.0-1.fc38
URL: https://gitlab.gnome.org/GNOME/gnome-text-editor

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gnome-text-editor

Comment 1 Fedora Update System 2022-10-04 22:18:02 UTC

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

Comment 2 Fedora Update System 2022-10-05 13:04:45 UTC

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

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

Comment 3 Kalev Lember 2022-10-06 10:04:54 UTC

Proposing as a Freeze Exception as it's still early in the freeze cycle and the gnome-text-editor update has a bunch of nice fixes:

 * Don't toggle editability during (auto)save operations as they can break input methods and cause input stalls.
 * Fix ctrl+home/end keyboard shortcut usage
 * Spellcheck improvements
 * Provide full document paths in tab tooltips
 * Fix bugreport_url in about dialog
 * Use stdout for --version output
 * Documentation updates
 * Translation updates

Comment 4 Fedora Update System 2022-10-06 14:17:04 UTC

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

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

Comment 5 František Zatloukal 2022-10-09 15:28:29 UTC

Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/957

The decision to classify this bug as an FreezeException was made.

Comment 6 Fedora Update System 2022-10-10 14:22:33 UTC

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