Bug 2180562 - Update gedit to release 44.2
Summary: Update gedit to release 44.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2190039
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-21 18:53 UTC by Tadej Janež
Modified: 2023-10-08 04:25 UTC (History)
5 users (show)

Fixed In Version: gedit-44.2-1.fc39 gedit-stable-3820230522225855.1 gedit-44.2-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-22 22:58:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tadej Janež 2023-03-21 18:53:40 UTC
Description of problem:
The current versions of gedit in Fedora are:
rawhide         gedit-43~alpha-3.fc38	
Fedora 38	gedit-43~alpha-3.fc38	
Fedora 37	gedit-43~alpha-2.fc37	
Fedora 36	gedit-42.2-1.fc36

The latest upstream release is 44.2 (released on Jan 19, 2023):
https://gitlab.gnome.org/GNOME/gedit/blob/44.2/NEWS

Could you update it?

Comment 1 Yaakov Selkowitz 2023-04-26 22:08:58 UTC
As of gedit 43, tepl is required, which needs to be reinstated.

Comment 2 Yaakov Selkowitz 2023-04-26 23:15:22 UTC
Test builds of 44 for F38 and rawhide: https://copr.fedorainfracloud.org/coprs/yselkowitz/gedit-44/monitor/

Comment 3 Yaakov Selkowitz 2023-05-15 22:08:11 UTC
tepl is back in; filed: https://src.fedoraproject.org/rpms/gedit/pull-request/7

Comment 4 Tadej Janež 2023-05-17 08:02:59 UTC
(In reply to Yaakov Selkowitz from comment #3)
> tepl is back in; filed:
> https://src.fedoraproject.org/rpms/gedit/pull-request/7

Great. I've reviewed the pull request.

@rstrode, could you review and merge the pull request?

Comment 5 Fedora Update System 2023-05-22 22:55:16 UTC
FEDORA-2023-3350e559ff has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3350e559ff

Comment 6 Fedora Update System 2023-05-22 22:56:59 UTC
FEDORA-2023-e83d7a66eb has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e83d7a66eb

Comment 7 Fedora Update System 2023-05-22 22:58:24 UTC
FEDORA-2023-3350e559ff has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-05-23 01:55:03 UTC
FEDORA-FLATPAK-2023-d44dbff135 has been submitted as an update to Fedora 38 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-d44dbff135

Comment 9 Fedora Update System 2023-05-24 01:58:45 UTC
FEDORA-FLATPAK-2023-d44dbff135 has been pushed to the Fedora 38 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-d44dbff135

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

Comment 10 Fedora Update System 2023-05-24 14:18:24 UTC
FEDORA-2023-e83d7a66eb has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e83d7a66eb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e83d7a66eb

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

Comment 11 Fedora Update System 2023-06-01 01:48:42 UTC
FEDORA-FLATPAK-2023-d44dbff135 has been pushed to the Fedora 38 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-06-09 01:59:34 UTC
FEDORA-2023-e83d7a66eb has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Red Hat Bugzilla 2023-10-08 04:25:06 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.