:: Re: [devuan-dev] sysvinit in debian…
Página Inicial
Delete this message
Reply to this message
Autor: Evilham
Data:  
Para: devuan-dev
Assunto: Re: [devuan-dev] sysvinit in debian is under threat of being dropped for buster...
Am 15/10/2018 um 14:09 schrieb Evilham:
> Am 15/10/2018 um 14:04 schrieb Nico Schottelius:
>>
>> Evilham <devuan@???> writes:
>>> *yes*. Who is going to write up there? :-)
>>> Someone who may be taken a tiny bit seriously with Debian?
>>
>> If you are looking for someone, It might be good to get in touch w/ Axel Beckert (Xtaran) - Debian
>> package maintainer and afaik liking the Devuan project (IRC/freenode: xtaran)
>>
>> Send greetings from me, if you approach him.
>>
>
> True!
>
> I remember chatting with him about a systemd bug in your chat a few
> weeks ago and he was a very open and pragmatic person.
>
> What I'd think is that instead of waiting for DNG to go nuts over this
> (and it may happen) we should follow the discussion and have them see
> that there is interest in *helping* the package stay in Debian, it may
> be clever to somehow "centralise" that communication to reduce that
> overhead.
>
> I signed up to debian-devel for starters to follow the discussion more
> closely; but it'd be nice if someone else took over that :-D.


Sorry, this couldn't wait, so I sent an email on debian-devel, which is
probably being moderated, posting it here as well so you are aware.


Dear debian-devel,

Am 15/10/2018 um 15:20 schrieb Jonathan Dowland:

- Zitierten Text ausblenden -
> [ re-adding TG who requested CCs in an earlier message, but has not
> set Mail-Followup-To:. You've probably missed half the conversation,
> Thorsten… ]
>
> On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote:
>> I believe Andreas Henriksson is right, the packages are going to be
>> removed unless someone with time and interest show up to take care of
>> them. A good start would be to split initscripts off from the sysvinit
>> binary packages, to let them live separate lives. It will be sad, but
>> the proper way for Debian to handle unmaintained packages in a sad
>> state.
>
> Is it worth interested parties reaching out to the Devuan project
> regarding person-power for sysvinit maintenance? As a derivative
> distribution, I imagine their lives would become much harder if we did
> drop sysvinit; they would have to pay the cost of maintaining the
> sysvinit package themselves (which is what I am proposing they do now)
> *as well* as a rapidly growing delta of sysvinit-support/initscripts in
> lots of other packages, as they steadily rotted in Debian.



it's my first time writing to this ML, which calls for a quick
hello/intro and the FYI that I intended to send:

The quick hello/intro:
I go on the internet by Evilham and have been using Debian for ages.
When it was time for me to give back to the community, systemd and
Devuan were both already a thing, and things ended up bringing me to
help Devuan first.

The FYI:
Devuan is not blind to this topic or reticent to contributing in Debian,
the discussion is indeed taking place over at devuan-dev and, without
having discussed it thoroughly yet, many are of the opinion that it *is*
in everyone's best interest to keep the packages in Debian, and in a
good state.

https://lists.dyne.org/lurker/message/20181015.100838.2018520a.en.html

At least personally speaking, there is interest in helping Debian from
Devuan, as most of us see that there is big benefit in both distros.

However, as you are aware, maintaining a distro is a lot of work (BTW:
thank you all for your contribution to Debian), there have been
priorities other than supervising state of packages in Debian.

I don't think many were aware of the state of things and that this was
the path these (very critical) packages were following in Debian.


Where to now?
At devuan-dev, Adam Sampson has suggested that the debian-bsd and
debian-hurd communities are also very interested in keeping non-systemd
things working, which is why I'd hope this won't end up in non-systemd
support being dropped, but that this thread becomes the distress call
that the topic needed.

If I had to guess, this requires some organisation first, and since it
may require cross-communities organisation it may be somewhat tricky.

From Devuan's side, there is a weekly meeting happening on (UTC)
Wednesday evening, where this will surely be a big topic.

Just letting you know, things are moving (albeit somewhat late and slowly).

Best regards,
--
Evilham