[Pkg-privacy-maintainers] Packaging workflow onioncircuits

[Ulrike Uhlig]

Hi Sascha & all,

On 09.07.19 12:14, Sascha Steinbiss wrote:

> I think this is easily fixed. I will address this in an upcoming upload.

Nice!

> BTW, is it intended to also have Tails releases in the Debian git repo
> with upstream versions newer than the one in Debian? If so, I would be
> glad if you could make sure to also include a pristine-tar tarball for
> the new upstream version so we don't work off different upstream
> sources. I have now imported the orig tarball from Tails [1] to make
> sure we're in sync for now. Thanks!

I tried to update this package myself some days ago and noticed that
there seems to be a missing workflow between Tails and Debian packaging,
mainly the missing pristine-tar file.

The person who had prepared the new upstream version told me they
followed the instructions in the file called HACKING. I created a ticket
on the Tails bugtracker to document how to correctly create a new
upstream version: https://redmine.tails.boum.org/code/issues/16813

I also had issues using gbp on that version of the package and I
wondered if you, Sascha, could document in debian/README.source what
your packaging workflow looks like, so that it can be followed more
easily by someone else. I'm happy to document it myself if you can give
pointers. On a sidenore, I generally prefer using a signed git tags
rather than the tarball in [1]. Do we agree that this tarball has no
signature?

Cheers!
ulrike

> [1]
>
https://deb.tails.boum.org/pool/main/o/onioncircuits/onioncircuits_0.6.orig.tar.xz
>