Hi Jordi,

On Wed, Jul 06, 2016 at 09:18:49AM +0200, Jordi Mallach wrote:
> This is all good news! I still use fcgiwrap myself so co-maintaining
> sounds about right (although I'm happy to downgrade myself to Uploader
> and have you as the main Maintainer if you want).

Great! I would be fine either way, but Maintainer might be better for
the sake of hinting (when the time comes) that I am ready to become DD.

> Also happy about svn → git, it's something that's been on the list for
> all of my packages but I've never come around to it.

Please take a close look at the carefully restored history:

git clone https://anonscm.debian.org/git/users/pc-guest/fcgiwrap.git

I have split the larger svn commits into multiple git commits so that
each commit corresponds to one changelog entry. I verified that the
debian/ tags match exactly the versions in snapshot.debian.org.

Would you be fine if we generate the changelog using "gbp dch" only
right before each upload? This keeps the history simple and avoids
potential merge conflicts in the changelog.

> I can give you the DM upload permissions straight away; I'm very happy
> about you joining and caring about fcgiwrap!

Yes, that would be nice.

Could you also advocate for me to join collab-maint? I sent a request
myself on alioth, but so far my account (pc-guest) has not been added.

> There's lots of bits that should be fed to gnosek via pull requests. In
> particular, every distro have their own crazy patches for systemd unit
> files. It would be nice to get something sorted in that direction. Our
> systemd changes were mostly all proposed by the Debian systemd people,
> and I think all of them make sense.

That would be my next step after uploading the current version. I will
see how to best integrate our patches and file pull requests upstream.

There is an open pull request [1] for a multi-instance systemd unit,
which would allow running fcgiwrap under multiple users using the same
systemd template, instead of running everything under www-data. In
case of a serious bug in one CGI app, this separation prevents the
hijacking of other CGI apps or the webserver itself.

[1] https://github.com/gnosek/fcgiwrap/pull/17

Peter

Attachment: signature.asc
Description: PGP signature

Reply via email to