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 :) Also, FYI, whilst most of Debian's buildd allows network connection, ubuntu's don't, so your package would have FTBFS there. > The easiest solution is to disable the test for now, but in the yes please. > long term it would be good to package boulder for Debian and use > it for offline testing. > > How are you currently testing the other Let’s Encrypt clients? > > Would you be interested in packaging boulder together? 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. > > In the meantime I did 3 more trivial commits, that I pushed. > > > > (hope you don't mind the extra commits, but imho that's the main > > advantage of keeping packages in a team, have the team mates being able > > to do such sillyness! ;)) > > Yes, your commits are very welcome. > > Which repository did you push to? master is still at 771996d: > > https://anonscm.debian.org/cgit/letsencrypt/acmetool.git Turns out I wrote something I didn't do, pushed now. Please ping once you disabled those tests -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature