On Sun, May 15, 2016 at 06:07:30PM +, Mattia Rizzolo wrote:
> Then, uploaded :)
Mattia, Harlan, thank you for the sponsorship!
Peter
On Sun, May 15, 2016 at 05:39:31PM +, Mattia Rizzolo wrote:
> On Sun, May 15, 2016 at 01:30:39PM -0400, Peter Colberg wrote:
> > Please try building acmetool commit fb8b2a5, which disables the
> > OCSP test to avoid network access in the build chroot.
>
> yeah, that one does build.
Please do
On Sun, May 15, 2016 at 01:30:39PM -0400, Peter Colberg wrote:
> Please try building acmetool commit fb8b2a5, which disables the
> OCSP test to avoid network access in the build chroot.
yeah, that one does build.
Given that you seem to be here, maybe you can double check these lintian
tags?
W:
On Sun, May 15, 2016 at 01:30:39PM -0400, Peter Colberg wrote:
> Hi Mattia,
>
> Please try building acmetool commit fb8b2a5, which disables the
> OCSP test to avoid network access in the build chroot.
Sorry, I pushed too fast, that should be commit 4244a83.
Peter
Hi,
2016-05-15 19:26 GMT+02:00 Mattia Rizzolo :
>
> I only maintain letsencrypt.sh that doesn't have tests, so I'm not
> really testing it. I don't know about the other clients.
>
but there are tests:
https://github.com/lukas2511/letsencrypt.sh/blob/master/test.sh :)
--
Hi Mattia,
Please try building acmetool commit fb8b2a5, which disables the
OCSP test to avoid network access in the build chroot.
Peter
On Sun, May 15, 2016 at 01:14:54PM -0400, Peter Colberg wrote:
> Thanks for catching this. I built the package in an sbuild chroot,
> which by default does not block network connections. The test is
> trying to contact the Let’s Encrypt staging server.
As you probably know that's not allowed :)
Hi Mattia,
On Sun, May 15, 2016 at 03:55:04PM +, Mattia Rizzolo wrote:
> So, I was about to upload, but it failed to build:
>
>dh_auto_test -O--buildsystem=golang
> cd obj-x86_64-linux-gnu
> go test -v github.com/hlandau/acme/acmeapi
>
control: owner -1 !
control: tag -1 moreinfo
On Sat, May 14, 2016 at 03:23:56PM -0400, Peter Colberg wrote:
> Would you do the honour of uploading acmetool?
>
> git clone https://anonscm.debian.org/git/letsencrypt/acmetool.git
> cd acmetool && pristine-tar checkout
Hi Dmitry,
The RFS for the acmetool package is now two months old; in the
meantime, Harlan Lieberman-Berg of the Debian Let’s Encrypt team
has reviewed [1] the package, which resulted in these changes [2].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817091#38
[2]
Dear Debian Let’s Encrypt team,
Is there anybody among you who would have time to sponsor acmetool?
The package has already been reviewed by Harlan Lieberman-Berg,
so all that is left to do for now is the actual upload.
https://bugs.debian.org/817091#47
Thanks,
Peter
Hi Harlan,
On Sat, Mar 26, 2016 at 12:06:08AM -0400, Harlan Lieberman-Berg wrote:
> When the blocks are resolved, ping me and I'll definitely take a look.
Thanks to Dmitry Smirnov, all golang dependencies have been uploaded.
The package "acmetool" is ready for sponsorship:
git clone
Dear Debian Let's Encrypt team,
I have switched the Maintainer of the acmetool package to Debian
Let's Encrypt and moved the alioth repository. I will ping you
for sponsorship once all golang dependencies have been uploaded.
git clone https://anonscm.debian.org/git/letsencrypt/acmetool.git
Peter Colberg writes:
> Did you find the time to take a brief look at the acmetool package to
> decide whether the Debian Let’s Encrypt team will provide sponsorship?
Hi Peter!
This definitely seems like something that could fit very well under the
Let's Encrypt team's
Hi Harlan,
Did you find the time to take a brief look at the acmetool package to
decide whether the Debian Let’s Encrypt team will provide sponsorship?
Regards,
Peter
Hi Dmitry,
Seeing that you have sponsored an impressive number of golang-*
packages, would you be willing to sponsor the initial upload of
acmetool [1] and its dependencies?
[1] https://bugs.debian.org/817865
The tool is promising to be useful to many Debian users that seek a
robust, but
On Thursday, 17 March 2016 5:07:39 PM AEDT Peter Colberg wrote:
> Seeing that you have sponsored an impressive number of golang-*
> packages, would you be willing to sponsor the initial upload of
> acmetool [1] and its dependencies?
I'd love to but I have to prioritise so unfortunately I won't be
Hi Peter!
The Let's Encrypt team might be able to help you get sponsorship for
this. Quick question -- besides the implementation language, what are
the main differences between this tool and acme-tiny?
Sincerely,
--
Harlan Lieberman-Berg
~hlieberman
Hi Harlan,
[Cc'ing Debian Go team]
On Thu, Mar 17, 2016 at 11:34:12PM -0400, Harlan Lieberman-Berg wrote:
> The Let's Encrypt team might be able to help you get sponsorship for
> this. Quick question -- besides the implementation language, what are
> the main differences between this tool and
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I hope you are now as delighted as I was to finally reap the fruits of
your labour, after having waded through all the dependent packages.
I am looking for a sponsor for the package "acmetool":
git clone
20 matches
Mail list logo