Fedora Merge Review: emacs http://cvs.fedora.redhat.com/viewcvs/devel/emacs/ Initial Owner: coldwell
Slapping an FE-Legal block on this package. This package can't go into F7 until 224627 is properly resolved.
Removed FE-Legal since bug 224627 has been resolved, and added the later bug to FE-Legal for completeness
I assume you guys have directly communication with emacs's upstream. Could you guys please ask upstream to update their * vhdl-mode * verilog-mode I would be nice that to see these be fixed upstream so that I can obsolete emacs-verilog-mode on rawhide.
It seems that verilog mode in Emacs is up to date: http://cvs.savannah.gnu.org/viewvc/emacs/lisp/progmodes/verilog-mode.el?root=emacs&view=log The vhdl-mode in Emacs is old, so someone who uses and understands this mode should update it. Please feel free to open a new bug (RFE) about it.
I have already done so http://lists.gnu.org/archive/html/bug-gnu-emacs/2009-12/msg00232.html However, I'm hoping someone else to do it instead of me since first I'm using emacs since a week, second I'm crowded with huge amount of workload for FEL. The vhdl-mode is heavily targeting proprietary vhdl simulators while, we have opensource vhdl simulators on fedora : e.g ghdl and freehdl. I've created a patch: http://lists.gnu.org/archive/html/bug-gnu-emacs/2009-12/msg00309.html There are a few more improvements which need to be made. But I don't have much experience with emacs to get that fixed. Upstream is enforcing compatibility with older versions. The help of an experienced emacs user would be appreciated
Mass reassigning all merge reviews to their component. For more details, see this FESCO ticket: https://fedorahosted.org/fesco/ticket/1269 If you don't know what merge reviews are about, please see: https://fedoraproject.org/wiki/Merge_Reviews How to handle this bug is left to the discretion of the package maintainer.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.