Created attachment 5094 [details] Proposal for a fix to the buggy spec file in xemacs-21.4.22.src.rpm When using package xemacs-21.4.22-24mga4.src.rpm to build xemacs a second installation following a previous one (with or without rebuild) fails. The $RPM_BUILD_ROOT directory is not removed at the very begining of %install stage so that a few `ln -s' (without -f) & `mkdir' (without -p) operations fail. One has to remove this directory by hand and rerun installation. The creation of the list of files included in the main package (the `rpm-files') is buggy because of 2 successive "... > rpm-files" commands (the second one cancels the first; they are both usefull) The following attachment is my proposal for a fix to that problem.
This package doesn't have a maintainer and is at risk of being dropped before too long, partially due to that. I would recommend joining the Mageia packaging team and becoming the maintainer of this package yourself. You can find information about doing that on the Mageia Wiki, and you should also join the dev@ml.mageia.org mailing list and send a message there expressing your interest if you are interested.
CC: (none) => fundawang, nanardonSource RPM: (none) => xemacsKeywords: (none) => PATCH, Triaged
(In reply to David Walser from comment #1) > This package doesn't have a maintainer and is at risk of being dropped > before too long, partially due to that. I would recommend joining the > Mageia packaging team and becoming the maintainer of this package yourself. > You can find information about doing that on the Mageia Wiki, and you should > also join the dev@ml.mageia.org mailing list and send a message there > expressing your interest if you are interested. I sent my answer to your suggestion a few days ago. Did you get it ? Do you have any comment about my interest on joining the Mageia packaging team ?
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
CC'ing lmenut who maintains xemacs-ess and might be familiar with xemacs packaging. Gilles, if you are still interested in getting involved in packaging, I would advise you to check this page about our mentoring program: https://wiki.mageia.org/en/Becoming_a_Mageia_Packager By a quick look at the current spec file, I believe the issue is still valid in Mageia 5 and Cauldron, but I'll let Gilles confirm: http://svnweb.mageia.org/packages/cauldron/xemacs/current/SPECS/xemacs.spec?view=markup Regarding deleting $RPM_BUILD_ROOT at the beginning of %install, this should not be necessary in Mageia, it is done automatically by our RPM macros.
CC: (none) => lmenut
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Resolution: (none) => OLDStatus: NEW => RESOLVED
(In reply to Marja van Waes from comment #5) > As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status > on 2015-09-19. It is is no longer maintained, which means that it will not > receive any further security or bug fix updates. > > This issue may have been fixed in a later Mageia release, so, if you still > see it and didn't already do so: please upgrade to Mageia 5 (or, if you read > this much later than this is written: make sure you run a currently > maintained Mageia version) > > If you are able to reproduce it against a maintained version of Mageia, you > are encouraged to > 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to > "REOPENED" > 2. click on "Version" and change it against that version of Mageia. If you > know it's valid in several versions, select the highest and add MGAxTOO in > whiteboard for each other valid release. > Example: it's valid in cauldron and Mageia 5, set to cauldron and add > MGA5TOO. > 3. give as much relevant information as possible. If you're not an > experienced bug reporter and have some time: please read this page: > https://wiki.mageia.org/en/How_to_report_a_bug_properly > > If you see a similar issue, but are _not_sure_ it is the same, with the same > cause, then please file a new bug report and mention this one in it (please > include the bug number, too). > > > If you would like to help fixing bugs in the future, don't hesitate to join > the > packager team via our mentoring program [1] or join the teams that fit you > most [2]. > [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager > [2] http://www.mageia.org/contribute/ I confirm that the same problem occurs with the spec file from xemacs-21.4.22-26mga5.src.rpm. Exactly the same failure concerning the final content of "rpm-files" so that the patch I proposed last year is still valid (may be apart the removal of %buildroot prior to install) I reopen this bug for mga5.
Resolution: OLD => (none)Status: RESOLVED => REOPENEDVersion: 4 => 5
@ Gilles, Thanks for reopening the bug report. Unfortunately, we don't have anyone who has time to work on xemacs, and it was obsoleted in cauldron because of the huge problems with it. See https://bugs.mageia.org/show_bug.cgi?id=11254#c36 If you customized xemacs, and would like to port your customization to emacs, then please read: https://wiki.mageia.org/en/Guide_to_customizing_Emacs Alternatively, you can consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager and reimport and maintain xemacs after you graduate. Kind regards, Marja
Resolution: (none) => WONTFIXStatus: REOPENED => RESOLVEDCC: (none) => marja11
CC: (none) => vincentmosier
CC: vincentmosier => (none)