[chiark.chat] Re: RFH: sysvinit etc. in Debian

[Andreas Messer]

Hi Ian,

On Tue, Oct 16, 2018 at 04:49:32PM +0100, Ian Jackson wrote:
> Martin Steigerwald writes ("Re: [chiark.chat] Re: RFH: sysvinit etc. in Debian"):
> > You may like to check the packaging work of Andreas Messer within Devuan 
> > regarding elogind.
> > 
> > https://git.devuan.org/devuan-packages/elogind
> > 
> > See for example branch "suites/ascii". Here for example the changelog 
> > from it:
> 
> Right.  When I investigated elogind I found the Devuan work and I
> reviewed the packaging.  I started with err, the ceres branch IIRC.
> It looked good to me, so I fixed the things that needed to be fixed to
> make it built on buster.
> 
> Peter then tried it out and got some, but not all, desktoppy things
> working.  His findings are here:
> [...]

Nice to hear. Unfortunately, I was not able to spent time on elogind the
last months by myself, So any help is really appreciated. Some days ago, 
I started some work to get the latest upstream version from elogind into
the repository but I did not finished that work yet.

> Yesterday prompted by some discussion in #devuan I took a look at the
> ascii branch too.  It does seem to have some further fixes but I don't
> *think* any of them are relevant to the trouble that Peter reported.
> 
> > Maybe you can use some of this work or work together with the maintainer 
> > in Devuan.
> 
> That would be great, indeed.  I'm not sure exactly how to structure
> this cooperation.  Right now we have been treating Devuan as an
> upstream (and I have been doing some considerable git branch format
> violence in our git branch).

Any patches, help or git pull requests are welcome. I also have the feeling,
that the current Devuan elogind package repo is not in the best shape
regarding its structure. It was actually my first package and I'm still 
a beginner in this.

I'm currently going to clarify with the Devuan guys, how the packaging 
workflow shall be for future devuan version, one of them has clear idea of
this but i did not understand it yet. In parallel I'll start
a small guide document on how a package repo should be structured 
and handled. Mostly to remind my self of that but maybe this is usefull
for others as well

> If we get something working it would be sensible to send our patches
> to Devuan I guess ?  Or maybe to elogind upstream ?  I notice that the
> Devuan git branches are a bit behind.

You're patches are welcome. Since we're approaching winter and evenings
become longer, there is a good chance that I'll be able to become more
active again.

cheers,
Andreas

-- 
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20181019/243d83ce/attachment.sig>