Hello Loren, I had noticed the new version and prepared an update and uploaded it before I saw your post to the list. Please be assured that it wasn't done intentionally. FWIW, my procedure is pretty exactly the same as yours - upgrade, install locally, run some interactive tests. Since you are willing to help maintain the package, I will wait to hear from you for the next update, if that's okay with you. Regarding the GBP workflow, something that has worked in the past is for you to push the branches to your fork and then signal that you're ready for an upload. The sponsor adds a remote for your fork and then merges the 3 GBP branches from your fork to the main repo. Apologies for the duplicated efforts - that's the tradeoff with team-maintained packages. Thank you, tony On Sun, Nov 03, 2024 at 05:26:50PM -0800, Loren M. Lang wrote: > Hello Debian HAM Team, > > I have the next release of TQSL ready for release: > > https://salsa.debian.org/debian-hamradio-team/trustedqsl/-/merge_requests/3 > > And it is passing all pipeline jobs: > > https://salsa.debian.org/penguin359/trustedqsl/-/pipelines/757172 > > I also ran a few interactive tests with loading my cert and signing logs > without any issues. > > I realize that merge requests are a little awkward due to the nature of > GBP workflows utilizing 3 different branches so let me know if there is > a better workflow I should be following to contribute to the development > and maintenance of the trustedqsl package. > > 73s, > Loren > K7IW > -- > Loren M. Lang > lorenl@north-winds.org > http://www.north-winds.org/ > > > Public Key: http://www.north-winds.org/lorenl_pubkey.asc > Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA
Attachment:
signature.asc
Description: PGP signature