https://bugzilla.redhat.com/show_bug.cgi?id=2345150
Backporting fixes seems like it would take some time: https://lists.gnu.org/archive/html/emacs-devel/2025-02/msg01058.html
What are the incompatibilities between 29.4 and 31.1 ?
What are the incompatibilities between 29.4 and 30.1 ?
See https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-30.1#n80 and https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-30.1#n1987 for a detailed list.
+1 to updating in stable releases.
As I observed in devel - looks like RHEL 9 / CentOS Stream 9 only has a fix for the newer CVE (2025-1244) - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7UDNK4ERXLALGWLMYWDDPW2N2QP3BUK3/
And the repo history does not have commits in the date range for which the FreeBSD dev noted fixes made to fix the older CVE-2024-53920
This is probably worth just bringing 30.1 to stable Fedora releases - at work we use the latest Fedora RPM rebuilt in Hyperscale, and users tend to be fine with having to update some of their MELPA packages to adjust, rather than using an older Emacs.
+1
Yeah, I think it should be fine to upgrade. There are some incompatibilites listed, but I don't think they matter much. I upgraded to 30.1 here and I don't see any difference.
Metadata Update from @zbyszek: - Issue tagged with: fast track, updates policy exception
Hmm, with the new emacs I lost syntax highlighting in rpm-spec-mode. This is a bit niche, but not great.
This would be fixed by https://src.fedoraproject.org/rpms/emacs-rpm-spec-mode/pull-request/3 (or a similar patch which references a newer snapshot). It might be time to carry out the unresponsive maintainer process, there.
I merged https://src.fedoraproject.org/rpms/emacs-rpm-spec-mode/pull-request/3 and did another update to a newer shapshot for F42 and rawhide. I think the maintainers are active, just temporarily overloaded.
After over a week, APPROVED (6, 0, 0)
Metadata Update from @fale: - Issue tagged with: pending announcement
Metadata Update from @fale: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.