Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1444818 - Update Emacs to 25.2
Summary: Update Emacs to 25.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Jan Synacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-24 11:41 UTC by Jan Synacek
Modified: 2017-05-12 19:23 UTC (History)
4 users (show)

Fixed In Version: emacs-25.2-2.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-12 19:23:31 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan Synacek 2017-04-24 11:41:16 UTC 
https://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00619.html
Comment 1 Fedora Update System 2017-04-25 08:21:51 UTC 
emacs-25.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-63544fcd26
Comment 2 Fedora Update System 2017-04-25 10:33:08 UTC 
emacs-25.2-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8205ac257e
Comment 3 Fedora Update System 2017-04-25 10:34:06 UTC 
emacs-25.2-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-476fa97670
Comment 4 Fedora Update System 2017-04-25 19:26:27 UTC 
emacs-25.2-1.fc24 has been pushed to the Fedora 24 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-2017-476fa97670
Comment 5 Fedora Update System 2017-04-25 21:30:03 UTC 
emacs-25.2-1.fc26 has been pushed to the Fedora 26 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-2017-63544fcd26
Comment 6 Fedora Update System 2017-04-25 23:49:24 UTC 
emacs-25.2-1.fc25 has been pushed to the Fedora 25 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-2017-8205ac257e
Comment 7 Fedora Update System 2017-04-27 19:54:05 UTC 
emacs-25.2-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Comment 8 Fedora Update System 2017-05-01 18:15:55 UTC 
emacs-25.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2017-05-02 11:09:34 UTC 
emacs-25.2-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3eeabab24b
Comment 10 Fedora Update System 2017-05-03 01:02:24 UTC 
emacs-25.2-2.fc24 has been pushed to the Fedora 24 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-2017-3eeabab24b
Comment 11 Fedora Update System 2017-05-12 19:23:31 UTC 
emacs-25.2-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.