[Letsencrypt-devel] Bug#841919: Bug#841919: Bug#841919: Bug#841919: Bug#841919: acme-tiny: Please provide a backport for jessie

[Jeremías Casteglione]

On Wed, 2 Nov 2016 06:56:20 +0000
Mattia Rizzolo <mattia at debian.org> wrote:

> > > * Uploads to backports don't close bugs, so even if you put a Closes:
> > >   there you'd need to close this bug manually nonetheless  
> > 
> > OK, thanks... No problem with that, but I still need to upload it to
> > backports right? Even if you are going to sponsoring it?  
> 
> Yeah, that's fine.  It just means you'll have to manually mail
> nnnn-done to close this bug once the backport is accepted.

Good, thanks for the upload!

> > > (on a related note, I also noticed only now that there is no upstream/*
> > > tags metching the upstream releases; could you please add them too?)  
> > 
> > I'm not sure about that... All the commits in the upstream branch were
> > auto done by git-dpm... And upstream didn't make any release either,
> > really. That's why we use the timestamp of last commit for the package
> > version and such.
> > 
> > So not sure about any tags, sorry, but I'm OK to adding whatever is
> > missing =)
> > 
> > There are actually 3 commits in the upstream branch, one for each
> > "release". I guess you mean to tag those commits?  
> 
> Ouch, I didn't realized you were using git-dpm u.U
> Hence my surprise, because with gbp the upstream tags are created at
> upstream import time, whilst with git-dpm that's all part of the
> `git-dpm tag` command run while uploading.
> I pushed a commit configuring git-dpm's tags to be sane, and run it
> while building the backport, and now there is also a upstream/ tag.
> *shrug* nvm for the older ones.

Great, I didn't know about the `git-dpm tag` thing...

Thanks for your help Mattia.

Cheers,


-- 
Jeremías
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/letsencrypt-devel/attachments/20161102/743b747f/attachment.sig>