Re: [macports-ports] branch master updated: py-certbot 0.10.0: new port

[Marius Schamschula]

Rainer,

OK. I can move it to security as certbot.

Currently only python 2.7 is supported, but the letsencrypt/certbot web site 
does mention that python 3.x support is planned (but on a back burner), so I 
wanted to leave in that option. There are some issues with rfc-3339 support.

Of course, such a change can be undone when that day comes, if ever….

> On Jan 15, 2017, at 9:53 AM, Rainer Müller  wrote:
> 
> On 01/14/2017 01:22 AM, Marius Schamschula wrote:
>> Marius Schamschula (Schamschula) pushed a commit to branch master
>> in repository macports-ports.
>> 
>> https://github.com/macports/macports-ports/commit/34767d74a27ef02f00bde27cb79a762f46bd6b00
>>  
>> 
>> The following commit(s) were added to refs/heads/master by this push:
>>  new 34767d7  py-certbot 0.10.0: new port
>> 34767d7 is described below
>> 
>> commit 34767d74a27ef02f00bde27cb79a762f46bd6b00
>> Author: Marius Schamschula  
>> AuthorDate: Fri Jan 13 18:22:14 2017 -0600
>> 
>> py-certbot 0.10.0: new port
>> 
>> An ACME Let's Encrypt client that can obtain certs and extensibly
>> update server configurations
>> ---
>>  python/py-certbot/Portfile | 48 
>> ++
>>  1 file changed, 48 insertions(+)
>> 
>> diff --git a/python/py-certbot/Portfile b/python/py-certbot/Portfile
>> new file mode 100644
>> index 000..8e3cb67
>> --- /dev/null
>> +++ b/python/py-certbot/Portfile
>> @@ -0,0 +1,48 @@
>> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
>> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
>> +
>> +PortSystem  1.0
>> +PortGroup   github 1.0
>> +PortGroup   python 1.0
>> +
>> +github.setupcertbot certbot 0.10.0 v
>> +namepy-certbot
>> +categories-append   security
>> +license Apache-2
>> +maintainers mps openmaintainer
>> +description An ACME Let's Encrypt client that can obtain certs and 
>> extensibly \
>> +update server configurations.
>> +long_description${description}
>> +platforms   darwin
>> +homepagehttps://letsencrypt.org/ Why 
>> did you call this port py-certbot? This is meant to be used as a standalone 
>> tool and not as a python module. The port should use the name "certbot" and 
>> the maintainer should decide to use a single python version (only if really 
>> necessary, provide +pythonXY variants). Look at python tool ports like bzr, 
>> mercurial, and others for examples.
> 
> Rainer

Marius
--
Marius Schamschula

Re: [macports-ports] branch master updated: py-certbot 0.10.0: new port

[Rainer Müller]

On 01/14/2017 01:22 AM, Marius Schamschula wrote:
> Marius Schamschula (Schamschula) pushed a commit to branch master
> in repository macports-ports.
>
> https://github.com/macports/macports-ports/commit/34767d74a27ef02f00bde27cb79a762f46bd6b00
>
> The following commit(s) were added to refs/heads/master by this push:
> new 34767d7 py-certbot 0.10.0: new port 34767d7 is described below
>
> commit 34767d74a27ef02f00bde27cb79a762f46bd6b00 Author: Marius Schamschula 
> 
> AuthorDate: Fri Jan 13 18:22:14 2017 -0600
>
> py-certbot 0.10.0: new port An ACME Let's Encrypt client that can obtain certs
> and extensibly update server configurations ---
>  python/py-certbot/Portfile | 48 
> ++
>  1 file changed, 48 insertions(+)
>
> diff --git a/python/py-certbot/Portfile b/python/py-certbot/Portfile new file 
> mode 100644
> index 000..8e3cb67 --- /dev/null +++ b/python/py-certbot/Portfile @@ -0,0
> +1,48 @@ +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 + +PortSystem
> 1.0 +PortGroup github 1.0 +PortGroup python 1.0 + +github.setup certbot
> certbot 0.10.0 v +name py-certbot +categories-append security +license
> Apache-2 +maintainers mps openmaintainer +description An ACME Let's Encrypt
> client that can obtain certs and extensibly \ + update server configurations.
> +long_description ${description} +platforms darwin +homepage
> https://letsencrypt.org/
Why did you call this port py-certbot? This is meant to be used as a standalone
tool and not as a python module. The port should use the name "certbot" and the
maintainer should decide to use a single python version (only if really
necessary, provide +pythonXY variants). Look at python tool ports like bzr,
mercurial, and others for examples.

Rainer

Re: [macports-ports] branch master updated: py-certbot 0.10.0: new port

[Ryan Schmidt]

> On Jan 13, 2017, at 18:22, Marius Schamschula  wrote:
> 
> Marius Schamschula (Schamschula) pushed a commit to branch master
> in repository macports-ports.
> 
> https://github.com/macports/macports-ports/commit/34767d74a27ef02f00bde27cb79a762f46bd6b00
> 
> The following commit(s) were added to refs/heads/master by this push:
>  new 34767d7  py-certbot 0.10.0: new port
> 34767d7 is described below
> 
> commit 34767d74a27ef02f00bde27cb79a762f46bd6b00
> Author: Marius Schamschula 
> AuthorDate: Fri Jan 13 18:22:14 2017 -0600
> 
> py-certbot 0.10.0: new port
> 
> An ACME Let's Encrypt client that can obtain certs and extensibly
> update server configurations
> ---
>  python/py-certbot/Portfile | 48 
> ++
>  1 file changed, 48 insertions(+)
> 
> diff --git a/python/py-certbot/Portfile b/python/py-certbot/Portfile
> new file mode 100644
> index 000..8e3cb67
> --- /dev/null
> +++ b/python/py-certbot/Portfile
> @@ -0,0 +1,48 @@
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> +
> +PortSystem  1.0
> +PortGroup   github 1.0
> +PortGroup   python 1.0
> +
> +github.setupcertbot certbot 0.10.0 v
> +namepy-certbot
> +categories-append   security
> +license Apache-2
> +maintainers mps openmaintainer
> +description An ACME Let's Encrypt client that can obtain certs and 
> extensibly \
> +update server configurations.
> +long_description${description}
> +platforms   darwin
> +homepagehttps://letsencrypt.org/
> +
> +python.versions 27 34 35 36
> +python.default_version \
> +27

The py36 subport doesn't build:

Error: Dependency 'py36-configargparse' not found.

I've been seeing this kind of thing a lot. We need to be verifying that our 
changes build properly before committing.