Your message dated Mon, 05 Sep 2016 06:30:25 +0200 with message-id <[email protected]> and subject line Re: Bug#835507: Please clarify that sysvinit support decision is not going to expire has caused the Debian Bug report #835507, regarding Please clarify that sysvinit support decision is not going to expire to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 835507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835507 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tech-ctte There has recently been a thread on debian-devel ("Is missing SysV-init support a bug?) about the decision by a package maintainer to drop sysvinit support from their package. The maintainer has said they are reconsidering, which is good. But, the discussion on -devel has shown that there are some other maintainers who are considering similar steps, and that the project's view on this is not settle. So: would the TC please clarify that the decision that For the record, the TC expects maintainers to continue to support the multiple available init systems in Debian. That includes merging reasonable contributions, and not reverting existing support without a compelling reason. still stands, and that the answer to this queston However, that was two years ago. How long should we be expected to continue maintaining sysvinit scripts? is "indefinitely, and specifically until a contrary decision by the TC" (subject to quibbles over the exact meaning of "maintaining"). Or to put it another way: The answer to "is missing sysvinit support a bug" is "yes, and it will continue to be regarded as a bug until further notice". Of course a maintainer is not required to personally fix every bug, but a maintainer should not introduce bugs without good reasons, and should merge reasonable bugfix contributions. Thanks, Ian.
--- End Message ---
--- Begin Message ---]] Ian Jackson Hi Ian, > So: would the TC please clarify that the decision that > > For the record, the TC expects maintainers to continue to support > the multiple available init systems in Debian. That includes > merging reasonable contributions, and not reverting existing > support without a compelling reason. > > still stands, and that the answer to this queston > > However, that was two years ago. How long should we be expected to > continue maintaining sysvinit scripts? > > is "indefinitely, and specifically until a contrary decision by the > TC" (subject to quibbles over the exact meaning of "maintaining"). We discussed this in the last CTTE meeting on IRC and agreed to decline to issue a statement, and I'm therefore closing this bug. If you would like us to have a formal vote about not issuing a statement, please let us know and we can go through the motions for that. We agree that there is a need for Policy to be updated to document the current requirements and we'll get that work on getting that started. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
