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
[email protected]
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

-----BEGIN PGP SIGNATURE-----

iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZygi0QAKCRDMe9wUn2Md 13yaAP9Ug4KV+JWrGMjwArKBhZY2tvdbvaPS4syGbCpjaEteTAD/cFZn/au9HwBz dskMZZzFcGeEuXvFlDj+NofFLmUTSqI=
=euqH
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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
[email protected]
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

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmcsR10ACgkQIdIFiZdL PpaRpw//cFa/XVa3sibtqcNMUw0NgdHqTVS2D1ptJVkwxr+nHvFIMxIQ/l9gbaRQ VFUhS8mKE9c+dhgZipPXXjO5ne2h5CqmZCDHJMssKoDQudECQKetY/ede/v2RVFg 4T2I0+SegNw6zH7Mng5KRaZq2FHeElYebeC4lmejvQaCllp5evsk7iuj/ytmgJZ0 B3G+eBzB+ShiGcEL9IDitkam302fzmIDuPquGuicswTM4T9yQMLtfxrzZfrLmgwT UNi7B7NoT4uI1LB3dZDT58OnHaXRQxpwTWrl0yYDnKzjl0rnVYizoo64pJvt11QX H+PQ7J1O7TB59P815DwyzE8ocrQh8dbPksbPPjVVWORko9uqNTNkFcN+5G6807nG XFh3ZnEFy2RcA4ncad/P/WYRixDbeMGS4q0+Z/zOIOzECOHQRwNFkw7aYTn4zdD9 HijILwztVOLpEAbS5jihfZ+krI00wLjThnPXc7/8/+Olf+CM4RX+NhtXGGSYw7zK Fdk+MMslWDX740OG/9uO2TUef1bt9vh6KDFpj8kvDSwnD6++mXMN9rPYLrNSg3ak ir3kKiaznWQsLFCcbd1AsrCkxO0MazoFt1Jz3VW9ok1fVubnVKtVEqDpz+PjJxhe H1q5cESt4HMYVCoechdZZT+EAK4OsEnbvOw04cjyj4D/A50Pv2s=
=2ddR
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Nov 07, 2024 at 04:51:42AM +0000, tony mancill wrote:

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

Thanks for that. Unfortunately, this last month was a little too busy so
I didn't have a chance to look at the 2.7.5 release till now, but maybe
I'll beat you for the next release. :-)

I am working on the backports for Ubuntu now for my PPA:

https://launchpad.net/~penguin359/+archive/ubuntu/trustedqsl

But it looks like the pristine-tar branch is missing the latest release.
Would you mind pushing that?

Also, the one extra commit that I did try add in to the previous release
was adding the gbp.conf config file. It just helps ensure that
pristine-tar is enabled for users git-buildpackage when using "gbp clone"
or "gbp push" regardless of their local default. I'll probably include
that the next chance I get to generate a release.

Always glad to contribute,
Loren

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
[email protected]
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

--
Loren M. Lang
[email protected]
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

-----BEGIN PGP SIGNATURE-----

iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZ14TGwAKCRDMe9wUn2Md 122WAPwLE8ULx/n6T1b2N3SKyJgVU3KYaGnglJNdEH40s5hp1QEAhv9Bhv1qwS63 ZJj4QTjV45YQWWt6hDpxGzpz8d27lQM=
=JXAB
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Dec 14, 2024 at 03:22:08PM -0800, Loren M. Lang wrote:

On Thu, Nov 07, 2024 at 04:51:42AM +0000, tony mancill wrote:

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

Thanks for that. Unfortunately, this last month was a little too busy so
I didn't have a chance to look at the 2.7.5 release till now, but maybe
I'll beat you for the next release. :-)

I am working on the backports for Ubuntu now for my PPA:

https://launchpad.net/~penguin359/+archive/ubuntu/trustedqsl

But it looks like the pristine-tar branch is missing the latest release. Would you mind pushing that?

I just noticed that the original tarball in the Debian archive for 2.7.5 appears to be one that gbp buildpackage auto-generated from the upstream branch, not the official tarball from ARRL due to the missing
pristine-tar. It just has the top-level folder renamed. I've adjusted my backports script to just pull it from the repository instead.

I ran into this issue before when I didn't have pristine-tar enabled
before and I've added --git-no-create-orig to my wrapper script around
gbp buildpackage to avoid confusion. Ideally, it should be a gbp.conf
option, but gbp doesn't seem to support that in a config file.

Also, the one extra commit that I did try add in to the previous release
was adding the gbp.conf config file. It just helps ensure that
pristine-tar is enabled for users git-buildpackage when using "gbp clone"
or "gbp push" regardless of their local default. I'll probably include
that the next chance I get to generate a release.

Always glad to contribute,
Loren

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
[email protected]
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

--
Loren M. Lang
[email protected]
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

--
Loren M. Lang
[email protected]
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

-----BEGIN PGP SIGNATURE-----

iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZ190ZQAKCRDMe9wUn2Md 123fAP9qXJHAOeACPMs2vWdCsOkv+erau+TpSN8IRjAL129jtwEA5Ij4VRBYwKJC Cz7WHrv/wttGXFD4Evi7H6TmZJN+Rww=
=tUA9
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Dec 15, 2024 at 04:29:30PM -0800, Loren M. Lang wrote:

On Sat, Dec 14, 2024 at 03:22:08PM -0800, Loren M. Lang wrote:

On Thu, Nov 07, 2024 at 04:51:42AM +0000, tony mancill wrote:

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

Thanks for that. Unfortunately, this last month was a little too busy so
I didn't have a chance to look at the 2.7.5 release till now, but maybe I'll beat you for the next release. :-)

I am working on the backports for Ubuntu now for my PPA:

https://launchpad.net/~penguin359/+archive/ubuntu/trustedqsl

But it looks like the pristine-tar branch is missing the latest release. Would you mind pushing that?

Apologies for the delay. Done now. (Explanation, not that it
matters... Some Debian packaging teams eschew pristine-tar in favor of
using the upstream branch only, and so I sometimes update my tooling
defaults and forget to switch them back.)

I just noticed that the original tarball in the Debian archive for 2.7.5 appears to be one that gbp buildpackage auto-generated from the upstream branch, not the official tarball from ARRL due to the missing
pristine-tar. It just has the top-level folder renamed. I've adjusted my backports script to just pull it from the repository instead.

That's a good catch. I will take better care with 2.7.6.

I ran into this issue before when I didn't have pristine-tar enabled
before and I've added --git-no-create-orig to my wrapper script around
gbp buildpackage to avoid confusion. Ideally, it should be a gbp.conf
option, but gbp doesn't seem to support that in a config file.

For the next upload we can add some notes to debian/README.source.

Also, the one extra commit that I did try add in to the previous release was adding the gbp.conf config file. It just helps ensure that
pristine-tar is enabled for users git-buildpackage when using "gbp clone" or "gbp push" regardless of their local default. I'll probably include
that the next chance I get to generate a release.

Please do add it. My apologies again for the unnecessary extra effort.

Cheers,
tony

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmdo6xwACgkQIdIFiZdL PpZilRAAhaa+hmtiSCxWJk7CXYJa0l5b2+j2OOrLVvWTNdGg4TLpukWmHMpFfy3t rlH56AplOZpTprUzy2hbtK3ThrB2Qx0pP3uq7v9ckZf3jjZlPLHWEzENUhN7H5bq +J8C/bQvmsdAuCLnjljLiW34H4ncVQlggbLPk/fuU/xjIcwVwlULn8OoRISpPllh Eabq1kLV51lrb3W+zExlsLmuTMJVKjK7/lDK857w8dS63wwDrcxXdA3YakcVjje6 zY6ReZck9hPw+jZgsGzmZ7Z6M/NJrMluoTvukW3dm/FP5qe1cSuVHRNi7WRXUbDH ZDtVT+on5aa8Yj1rcvgBkHkhJANCGHSJcRczDfKzozhImAuxB5xi+iOzBluxX79E QSE7DiL804cTZr2mNX/iy5oUtPblk3KsmtzHogtFbFLRvC0VUzIG6s5GGrVTFM1a M6YDQwYtEome9wFlqeUlqrIupGXbACSOMcyYEM5bFkSuhyHa6kI77llwzxdkgU0L TWrnMnQ7ZwCDjfxs6EH7cqEL/x8e3uXfBi/hAYiHBWVfB17h1lVZwQfCwCRac37d PaDruYEDn50d+NoD220ynd5Pg3jU5qPSBbMGgj+j901WC3yx9gush4aDsFJP++1r 2iH7t0hP0G39NqyHIBqWp1fP+a2wYutKV2WGOCQBNXBtHtq6WRM=
=Tksg
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)