Description of problem: Update emacs and check that there's no rpm-spec mode available anymore. rpm-spec mode has been extracted to a separated package since F19, but the commit has been backported on F18 [1] while emacs-rpm-spec-mode has no F18 branch. Two solutions: 1. revert backported commit 2. create a new branch on F18 for emacs-rpm-spec-mode Since it disrupts packagers using emacs workflow, i suggest that we stick to solution 1. and the change documented in release notes. [1] http://pkgs.fedoraproject.org/cgit/emacs.git/commit/?h=f18&id=4e102e78971b8bc2abd1bae29d65619e347dcd5f
Hi, thank for the bug. It seems that files were removed by git merge from f19(version 24.2) to f18 (version 24.2) In rawhide it was removed by https://bugzilla.redhat.com/show_bug.cgi?id=857865 I suggest to either backport also emacs-rpm-spec-mode to f18 or again include files (lost by git merge).
rpm-spec-mode files have been again added to emacs package. scm-commit (http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130408/998153.html) -> modified
emacs-24.2-18.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-24.2-18.fc18
Package emacs-24.2-18.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing emacs-24.2-18.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5559/emacs-24.2-18.fc18 then log in and leave karma (feedback).
emacs-24.2-18.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
What about F19?
Also why was there no changelog entry about the removal? :)
Okay re-opening for F19.
There is separate package in F19 called emacs-rpm-spec-mode. BZ for that case was already created (https://bugzilla.redhat.com/show_bug.cgi?id=973082). Therefore I am closing that as duplicate. *** This bug has been marked as a duplicate of bug 973082 ***