startpar and insserv status

Jesse Smith jessefrgsmith at
Tue Nov 13 20:48:28 GMT 2018

On 11/13/18 4:22 PM, Dmitry Bogatov wrote:
> [2018-11-11 19:18] Jesse Smith <jessefrgsmith at>
>> On 11/11/18 5:08 PM, Dmitry Bogatov wrote:
>>> Hello, Petter.
>>> What is status of src:startpar and src:insserv? They both seems to have
>>> alioth as Vcs- fields, so they were not updated for some time. As you
>>> may know, on @debian-init-diversity (in CC) there is activity on
>>> bringing sysvinit back to glory. I wander,
>>>  * Is there some development for src:startpar/src:insserv somewhere,
>>>    which is not uploaded?
>>>  * Is it okay if move packages under debian/ on salsa, set mailing list
>>>    as maintainer and you as uploader?
>> While this may be a little outside the scope of this conversation, I'm
>> maintaining startpar and insserv upstream. Will be happy to field
>> questions or concerns about the upstream status and code if need be.
> Sure. Mind to take a look at bugs in src:startpar and src:insserv,
> closing non-present bugs and tagging `fixed-upstream' bugs, resolved
> in your git?

I plan to do this after the current release cycle. I was asked to get
sysvinit-2.92 out the door in time for Debian Buster so I'm focused on
testing it at the moment.

After the next sysvinit release I can put aside time to go through the
insserv and startpar reports.

More information about the Debian-init-diversity mailing list