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

[Jeremías Casteglione]

Hi Mattia:

On Tue, 1 Nov 2016 21:56:23 +0000
Mattia Rizzolo <mattia at debian.org> wrote:

> Hi! :)
> 
> On Tue, Nov 01, 2016 at 06:39:42PM -0300, Jeremías Casteglione wrote:
> > > It would be nice to have a backported package of acme-tiny for
> > > Jessie.  
> > 
> > I just pushed to package's repo the debian/stable branch, with the
> > backported version 20160801-1~bpo8+1.  
> [..]
> > This is my very first backport so it might be not so well done yet...
> > I'll be uploading it to backports.d.o soon I hope.  
> 
> I guess you need a sponsor for this too, right? :)

Yes, please? =)

> 
> What I noticed:
> 
> * I discurage using "debian/stable" as a branch name in git:
>   + such naming should be reserved to stable uploads, which this isn't
>     (being a backport)
>   + "stable" changes over the history, if anything this should say
>     "jessie"
>   + summing up: please call that branch either
>     "debian/jessie-backports" (this would follow DEP-11) or
>     "jessie-backports"

Great, thanks! I just pushed the debian/jessie-backports branch.

I guess it's OK to delete debian/stable branch in alioth's repo then? To
avoid confusions and such?

> * 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?

> (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?

> 
> (btw: no need to Cc the ML, it gets all the bug reports messagges
> anyway, being the maintainer)

OK, sure!

Thanks!!


-- 
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/20161101/dead2a76/attachment.sig>