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

Bug#817865: marked as done (RFS: acmetool/0.0.49 [ITP] -- automatic certificate acquisition tool for Let's Encrypt)

Your message dated Sun, 15 May 2016 18:07:30 +0000
with message-id <20160515180728.GS16231@chase.mapreri.org>
and subject line Re: [Letsencrypt-devel] Bug#817865: RFS: acmetool/0.0.49 [ITP] -- automatic certificate acquisition tool for Let's Encrypt
has caused the Debian Bug report #817865,
regarding RFS: acmetool/0.0.49 [ITP] -- automatic certificate acquisition tool for Let's Encrypt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
817865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817865
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 https://anonscm.debian.org/git/pkg-go/packages/acmetool.git

  cd acmetool && pristine-tar checkout ../acmetool_0.0.49.orig.tar.gz

For verification, these are the current branch heads:

  git show-ref --heads
  8ae9df6d4dd330b269303b44c6b9c9f6bc3f5ce9 refs/heads/master
  7ebb219ff2f4fe4cabc603ef2f4e5155b041c772 refs/heads/pristine-tar
  1d8a3d99536b3472709a4b184afbdc8b10ebc2f6 refs/heads/upstream

It builds these binary packages:

  acmetool -- automatic certificate acquisition tool for Let's Encrypt

More information about acmetool can be obtained from

https://hlandau.github.io/acme

If you decide to sponsor this package, please change the distribution
from UNRELEASED to unstable before upload. I will import the uploaded
source package into the git repository and push a tag afterwards.

Regards,
Peter

--- End Message ---
--- Begin Message --- 
On Sun, May 15, 2016 at 01:58:28PM -0400, Peter Colberg wrote:
> On Sun, May 15, 2016 at 05:39:31PM +0000, 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 a "git fetch" and "git reset --hard origin/master" to fix
> a search&replace accident. I promise to never overwrite HEAD again :-(

don't worry, I can deal with it ;)
(and already did that, as i received your second email when writing mine
and checked).

BTW, yeah, that's a really bad thing to do in a context like, after you
explicitly asked somebody else to pull... That should have been the
place for a follow up fixup commit :)

> > W: acmetool: spelling-error-in-readme-debian acme acme (duplicate word) acme
> 
> That is a false positive:

I wouldn't mind a override.

> > I: acmetool: spelling-error-in-binary usr/bin/acmetool unkown unknown
> 
> I searched for this spelling error before in all of the Golang
> packages but could not find it, so it must be in the Go standard
> library. I will file an upstream issue with golang/go.

I see.

> > There is also this one, but my guess is that is'a false positive?
> > I: acmetool: spelling-error-in-binary usr/bin/acmetool writeN written
> 
> Yes, the trailing capital letter is characteristic of a false positive
> that I have seen in other packages before.

I wonder if that's another good place for an override and/or a lintian
bug.

> > PS: I had already pulled and worked too.  I *think* that since some
> > debhelper versions where the -O was internally refactored it's not
> > strictly needed anymore to carry on the -O in all the overrides.
> 
> I will ask the Debian Go maintainers whether -O--buildsystem=golang
> can be dropped safely.

ok

> In any case, it’s fixed in commit 4244a83,
> which is ready for upload.

Then, uploaded :)

I also tagged the release in git ^^

-- 
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  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: