Description of problem: When I start emacs after installing the Singular-emacs package, I get an immediate error: Symbol's value as variable is void: singular-emacs-home-directory This is due to the definition in /usr/share/emacs/site-lisp/site-start.d/singular-init.el: ;; update singular-emacs-home-directory (setq singular-emacs-home-directory (concat singular-emacs-home-directory ;; we check for trailing slash and backslash ;; but unconditionally insert a slash. ;; Hopefully that works on NT, too. (if (memq (aref singular-emacs-home-directory (1- (length singular-emacs-home-directory))) '(?/ ?\\)) "" "/"))) It says "update" and it is doing a setq, plus singular-emacs-home-directory is used in the body (hence the error), meaning that this code expects that singular-emacs-home-directory was set by defvar somewhere else. But it wasn't. Version-Release number of selected component (if applicable): Singular-emacs-3.1.5-5.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Singular-emacs 2. Start emacs 3. Actual results: An error at startup. Expected results: No errors at startup. Additional info:
I believe it would need a patch like this (using rpm macros): (setq singular-emacs-home-directory "%{_emacs_sitelispdir}/singular") before the code that sets and uses it in the same expression. But then it prints an error of an undefined 'current-menubar' symbol. Looks like it does not work with emacs in f19 at least, and either did not trigger an error before when setting and using an undefined variable in the same expression, or nobody ever cared about it. Last Changelog entry of the emacs files is from 2000. I think it may be better to just disable the emacs subpackage. Any suggestion? I made a report backpointing to here about this issue in the Singular trac at http://www.singular.uni-kl.de:8002/trac/ticket/510
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
It looks like this has not been resolved yet.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Jerry, do you have an idea of how to correct it? You get to the state of what upstream said to do after running: $ sudo mv /usr/share/emacs/site-lisp/site-start.d/singular-init.el /usr/share/emacs/site-lisp/singular/.emacs-singular and to revert to likely even more broken, current package, run: $ sudo mv /usr/share/emacs/site-lisp/singular/.emacs-singular /usr/share/emacs/site-lisp/site-start.d/singular-init.el But it still has the problems I reported, but upstream had closed it as a not a bug in http://www.singular.uni-kl.de:8002/trac/ticket/510
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.