[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash



Hi Daniel :)

On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote:
> I might have overcomplicated things a bit with the current packaging
> approach (e.g. providing apache configuration). You might want to take a
> look yourself and share your thoughts.

I think your apache snippet is cool, actually.
I improved it a bit the thing, by moving it to be a config snippet,
instead of being treated as a virtualhost, and by using dh_apache2
instead of manually try (and fail, e.g. you forgot to remove the thing
when removing the package) to get it right :)

> If you're up for it, I gratefully would like to accept your offer to
> co-maintain this package. Additionally it might be worth to ask having
> it under the umbrella of Debian Let's Encrypt [2].
> 
> Let me know if you think we can base our work on what I've done so far,
> or if we instead should make a fresh start.

See this:
https://anonscm.debian.org/git/letsencrypt/letsencrypt.sh.git/
I updatd it to the released version.  I kind of changed a bit the git
repository layout (using debian/master instead of debian/experimental,
and using master (following the upstream one) instead of
upstream/experimental.  README.source is not really the thing I followed
to import the new source, but as I did a lot of stuff while updating the
thing I think we'll need the next release to see what we actually need
to do to import a new upstream (also, I'm not really a gbp master, I
committed the pristine-tar info manually with `pristine-tar commit...`)

I did a buch of other changes, that you may agree or not, please have a
look and comment on them; I'm quite open, if you don't like some commits
I can happily accept to see them reverted (some/most of them, some other
I definitely want to see them keep)

You should have commit access on it, so feel free to just push stuff and
at most we can discuss it later.

I've already installed the resulting .deb on one of my servers, but I
have to admit that I already have some infrastructure around LE, so I
won't use the packaged configuration, nor the apache snippet by myself
(at least not yet).

Something I need help/suggestion for: I quite dislike the name
letsencrypt.sh-challenge-response-apache2, I find it way too long :\
Can we think of something more nice? :)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: