Bug 1763782

Summary: emacs: update to 26.3 to use new GNU ELPA key
Product: [Fedora] Fedora Reporter: Riccardo Schirone <rschiron>
Component: emacsAssignee: Robin Lee <robinlee.sysu>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: dan.cermak, jkeating, jonathan.underwood, jsynacek, msekleta, pep, phracek, robinlee.sysu, wes.turner
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: emacs-26.3-1.fc31 emacs-26.3-1.fc30 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 01:54:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Riccardo Schirone 2019-10-21 15:14:49 UTC
Description of problem:
While trying to install spacemacs many packages are not downloaded and there are issues with signatures.


Version-Release number of selected component (if applicable):
emacs-26.2-1.fc30


How reproducible:
Always


Steps to Reproduce:
1) `git clone https://github.com/syl20bnr/spacemacs ~/.emacs.d`
2) `emacs`.

Actual results:
Some packages cannot be checked and others are not downloaded. At the end, spacemacs does not work as expected.


Expected results:
All packages are correctly downloaded, checked for the right signature, and installed


Additional info:
I tried the package emacs-26.3-1.fc32 and it works well in F30 as well.

Comment 2 Riccardo Schirone 2019-10-22 07:49:40 UTC
Hi Wes, yes that should work. I think you can also use `koji download-build -a x86_64 -a noarch 1376499`.

Comment 3 Dan Čermák 2019-11-29 09:01:57 UTC
Could Emacs please receive the update also on the stable branches? This is a pretty big show stopper to use Emacs on Fedora 30 & 31.

Comment 4 Robin Lee 2019-12-08 07:47:58 UTC
I also vote for a update for F31/30. And I am happy to co-maintain emacs. My FAS ID is 'cheeselee'.

Comment 5 Dan Čermák 2019-12-09 10:02:25 UTC
(In reply to Robin Lee from comment #4)
> I also vote for a update for F31/30. And I am happy to co-maintain emacs. My
> FAS ID is 'cheeselee'.

I second that offer, FAS ID is `defolos`.

Comment 6 Jan Synacek 2019-12-10 11:24:27 UTC
This is very low priority for me right now and I'm not able to fix it. I have added commit rights for both "cheeselee" and "defolos". Feel free to commit a fix.

Comment 7 Fedora Update System 2019-12-10 17:44:25 UTC
FEDORA-2019-212afebfaf has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-212afebfaf

Comment 8 Fedora Update System 2019-12-10 17:44:26 UTC
FEDORA-2019-65f29378bd has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-65f29378bd

Comment 9 Fedora Update System 2019-12-11 01:04:22 UTC
emacs-26.3-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-212afebfaf

Comment 10 Fedora Update System 2019-12-11 01:41:55 UTC
emacs-26.3-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-65f29378bd

Comment 11 Fedora Update System 2019-12-12 01:54:37 UTC
emacs-26.3-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2020-01-04 22:14:17 UTC
emacs-26.3-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.