[pkg-gnupg-maint] salsa repositories layout

Christoph Biedl debian.axhn at manchmal.in-ulm.de
Sun May 16 11:05:10 BST 2021


a few days ago, I uploaded new versions of libgpg-error and gnupg to
experimental. As you might have noticed, the repositories at salsa have
not been updated yet. That's my task no doubt, but to do so I need to
understand the idea about the repective repository layout, and I failed
in that regard. Is there a description how things should be done?

In detail:

* libgpg-error

The branches upstream/master and debian/master are pretty obvious - but
what is upstream (currently at ea4755d ("New upstream version 1.38")
for? It's neither upstream's master (that's upstream/master) nor the
unpacked upstream release tarball (as I'd expect), so I have no clue how
to continue that one. Comparing to the related orig.tar, it lacks
various .in and .m4 but also some other files.

* gnupg2

Likewise, how was the content of d82b0f1ef ("New upstream version
2.2.27") generated?

Additionally, since upstream had different branches for 2.2 and 2.3
development, the change will be fairly huge. No problem for me, but that
might become fairly noisy on some notification channels.

* experimental branch

Both repositories have "experimental" branches from old times. Both my
uploads should be there as well. I'd prefer to hard-reset them to a
place related to the respective upstream commits since in my opinion a
continuation creates more confusion than clarity. Or is there a better
way to deal with it?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20210516/067a0709/attachment.sig>

More information about the pkg-gnupg-maint mailing list