[Pkg-privacy-maintainers] [Pkg-privacy-commits] [torbrowser-launcher] branch debian/sid updated (4afa77b -> 118514f)

Roger Shimizu rogershimizu at gmail.com
Tue Nov 21 14:37:22 UTC 2017

Dear intrigeri,

On Sun, Nov 19, 2017 at 7:49 PM, intrigeri <intrigeri at debian.org> wrote:
> Hi,
> Roger Shimizu:
>> rosh pushed a change to branch debian/sid
>> in repository torbrowser-launcher.
>>       from  4afa77b   torbrowser-launcher (0.2.8-5)
>>       adds  ba1689b   Rebuild as 0.2.8-3~bpo9+1 for stretch-backports
>>       adds  e967023   Rebuild as 0.2.8-3~bpo8+1 for jessie-backports-sloppy
>>       adds  d751bca   Merge branch 'debian/jessie-backports-sloppy'
>>       adds  3768e91   Rebuild as 0.2.8-4~bpo9+1 for stretch-backports
>>       adds  4ba7e9b   Rebuild as 0.2.8-4~bpo8+1 for jessie-backports-sloppy
>>        new  81838cc   Merge branch 'debian/jessie-backports-sloppy'
>>        new  cdceedf   Rebuild as 0.2.8-5~bpo9+1 for stretch-backports
>>        new  118514f   Rebuild as 0.2.8-5~bpo8+1 for jessie-backports-sloppy
> Isn't this a mistake? I don't think the backports uploads should be
> mentioned in debian/changelog on the debian/sid branch.

No, it's intended.
I always sync bpo branch and master (debian/sid for this pkg).
It may be not necessary, but does no harm, either.

I see many of your commits contains "Gbp:" tag. Is it a special gbp workflow?
Maybe it's easier for you if I also follow that workflow?
If so, please let me know. Thanks!

> Cheers, and thanks for uploading all these backports!

No problem.
I think it makes people life easier.

Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

More information about the Pkg-privacy-maintainers mailing list