This is a tracking bug for initscripts that are not compliant with: https://fedoraproject.org/wiki/FCNewInit/Initscripts
This wiki page is not a Fedora guideline. ;) Please point people to the real page: https://fedoraproject.org/wiki/Packaging/SysVInitScript Which likely has differences (although all the bugs I see off hand do seem to be valid against the real guideline page. )
Thanks Kevin! I'll update the info.
Who decided that LSB compliance is a requirement? I might be missing something. Could you please clarify?
Stop calling it LSB compliance, since that isn't actually what the bugs are?
(In reply to comment #4) > Stop calling it LSB compliance, since that isn't actually what > the bugs are? Good point! If we're trying to make the initscripts compliant, we should really make absolutely clear to what specification. If this is not to be LSB but Fedora Guidelines, let's call it accordingly. Anyway, why do we have the two Fedora initscript wiki pages? This is not a good way how to create a standard. I suggest to merge the two pages (seems to me that the FCNewInit/Initscripts is almost copy and paste of LSB anyway). One more question: Is it really good idea to enforce the "reload" action for all services? I can imagine that some services really do not support reloading config file on-the-fly and reporting status code 3 [unimplemented feature (for example, "reload")] (this example being th part of the guideline ?!) is a valid use case. (There's always the force-reload if we don't care whether the service function will be interrupted or not.)
(In reply to comment #5) > (In reply to comment #4) > > > Stop calling it LSB compliance, since that isn't actually what > > the bugs are? > > Good point! If we're trying to make the initscripts compliant, we > should really make absolutely clear to what specification. If this > is not to be LSB but Fedora Guidelines, let's call it accordingly. > > Anyway, why do we have the two Fedora initscript wiki pages? This > is not a good way how to create a standard. I suggest to merge the > two pages (seems to me that the FCNewInit/Initscripts is almost > copy and paste of LSB anyway). It would be also helpful to have new sample initscript that's compliant with the requirements and that will be discussed in the Packaging Commitee and/or in the developers community even if this action is primarily targeted on RHEL6. All maintainers developing their own versions isn't really how it should work ... > One more question: Is it really good idea to enforce the "reload" > action for all services? I can imagine that some services really > do not support reloading config file on-the-fly and reporting > status code 3 [unimplemented feature (for example, "reload")] > (this example being th part of the guideline ?!) is a valid use > case. (There's always the force-reload if we don't care whether > the service function will be interrupted or not.)
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > It would be also helpful to have new sample initscript that's compliant with > the requirements and that will be discussed in the Packaging Commitee and/or in > the developers community even if this action is primarily targeted on RHEL6. > All maintainers developing their own versions isn't really how it should work Which service and which version of this service is LSB 'almost' compliant now?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is a tracker (wow, only 5 bugs left to go) so bumping to F14 to not get autoclosed.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping