On Tue, Nov 01, 2016 at 07:51:30PM -0300, JeremÃas Casteglione wrote:
> 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?
I deleted it ^^
> > * 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
-done to close this bug once the backport is accepted.
> > (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.
--
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
___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
