• RFS: Update TrustedQSL to upstream release 2.7.3

    From Loren M. Lang@21:1/5 to All on Mon Apr 22 05:00:01 2024
    Hello Debian HAM Team,

    I am interested in joining and helping keep up some of the HAM Radio
    software in Debian. I have been helping to maintain backports of
    TrustedQSL for various Ubuntu releases for the last year:

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

    And lately have been getting into helping more with various Debian
    packages directly. I saw that a new release of TrustedQSL was published
    a couple weeks ago and decided to help import it into Debian. I have
    published my work on Salsa and created MR #1 with the proposed updates:

    https://salsa.debian.org/debian-hamradio-team/trustedqsl/-/merge_requests/1

    I realize that Merge Requests are a little awkward for managing Debian packaging workflows due to maintaining multiple branches so let me know
    if there is a better procedure I should be following for this. I have
    pushed updated branches for master, upstream, and pristine-tar along
    with tags to my fork of the repo for review.

    One little issue I did run into was that it seems the recent 2.7.2
    release wasn't quite merged in correctly. It was tagged, but the
    upstream branch was not updated to match or merged into the master
    branch. I started by doing a fast-forward to the upstream/2.7.2 tag and
    then creating a merge into master before doing any other work on the
    branch. The Git tree object is identical so the resulting merge will
    create an identical checkout, but it will include the appropriate
    upstream commit in the history from the import of the original, pristine tarball.

    Thanks for any feedback with this proposed release.

    73s,
    Loren M. Lang
    K7IW

    [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-----

    iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZiXQRgAKCRDMe9wUn2Md 17lLAP90eT6p4tReiQ86QnU3U4t5IDGUdh3a1nEGvc0zEpQ9kQEAuvPcB27+0uNl /te6Xeh30QRpLZVvizkS1UhfcaiFsAo=
    =GDlu
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony mancill@21:1/5 to Loren M. Lang on Mon Apr 22 06:10:01 2024
    Hello Loren,

    On Sun, Apr 21, 2024 at 07:49:49PM -0700, Loren M. Lang wrote:
    Hello Debian HAM Team,

    I am interested in joining and helping keep up some of the HAM Radio
    software in Debian. I have been helping to maintain backports of
    TrustedQSL for various Ubuntu releases for the last year:

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

    And lately have been getting into helping more with various Debian
    packages directly. I saw that a new release of TrustedQSL was published
    a couple weeks ago and decided to help import it into Debian. I have published my work on Salsa and created MR #1 with the proposed updates:

    https://salsa.debian.org/debian-hamradio-team/trustedqsl/-/merge_requests/1

    Thank you!

    I realize that Merge Requests are a little awkward for managing Debian packaging workflows due to maintaining multiple branches so let me know
    if there is a better procedure I should be following for this. I have
    pushed updated branches for master, upstream, and pristine-tar along
    with tags to my fork of the repo for review.

    Yes, I don't know of a (good) reference workflow for new sponsored
    uploads of new upstream releases. When I sponsor, I typically have
    sponsorees either create a MR for only the main/master branch or
    upload their source package to mentors.debian.net. Pushing all 3
    branches is fine too.

    One little issue I did run into was that it seems the recent 2.7.2
    release wasn't quite merged in correctly. It was tagged, but the
    upstream branch was not updated to match or merged into the master
    branch. I started by doing a fast-forward to the upstream/2.7.2 tag and
    then creating a merge into master before doing any other work on the
    branch. The Git tree object is identical so the resulting merge will
    create an identical checkout, but it will include the appropriate
    upstream commit in the history from the import of the original, pristine tarball.

    This was my mistake. My apologies for the hassle. Thank you for
    addressing it.

    Thanks for any feedback with this proposed release.

    I will take a look in the next week and either provide feedback or
    upload.

    Thank you!
    tony

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

    iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmYl4RsACgkQIdIFiZdL PpbhCw//aZhSZgych0hOv2ih13to3AQ6p/xIlAe1vgyrEKg63vUiEzZnz6uksKrm mHDiUXqVgCTUXJMCLRe/kbpzDVLlw22Nmi1tIPlQscTkb6Sg7XvO6zApYejc2dIq bcbX5SyBVhItDzVR1OFWvWNeTIymhzKqg5ls1GAToOiJktpxQRfpuzUqAreeK7j1 G0LyzpFQMREaXqM9kqS5rsgBQZituGyDHzIxIOR9VWAuFS3wAn7IngvoXPijQ/jt IBzRv0jPXtbSpNmq1pFHeCGN7SUTYqLSHQZgWNqD7FarXdf/PyKnBUyJD7OtoJjh Gicqo8GpJAUjbiSFM5Wzo0Nil3hfXxWdgJe++FnEKOIVMU3PiQQB7fIEJbSEZJAj W5xIKmfDntnCBfHJEaywhwBKWbGX6oHyu9dBjdCaCXcwzyb3A2RfXj+07jn13Pnd DZ/CHTI4vSccR+/FmAcSFV09OmK4F3ZY0QlxChsahrHFdQLKBgGMJgN6l2MZs1Bb QFyFIyy3r565s25GAbFCnc2Rqw6xGhg9p6avIwYxotFxDO5jfBK94rsYocZfNCfb GdcUzZo+XhHdr+V4KpDn3atU32VC7nf2SWkHZtNXzYJp+ZME4tid0+GAwpj+YCbJ umBAKGfsAXmg2/iau7JCQDVgd/nFvtSVjfp69yCNANdjg8uRTB4=
    =8nld
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony mancill@21:1/5 to Loren M. Lang on Wed Apr 24 07:10:01 2024
    Hello Loren,

    On Sun, Apr 21, 2024 at 07:49:49PM -0700, Loren M. Lang wrote:
    https://salsa.debian.org/debian-hamradio-team/trustedqsl/-/merge_requests/1

    Everything looks good with your MR, so it has been merged and uploaded.
    I added your fork in Salsa as a separate git remote, and so I was able
    to merge your upstream branch, pristine-tar branch, and upsteam/2.7.3
    tag as well, and pushed all of those the Debian Hams repo on Salsa.

    Thank you for your contribution!
    Cheers,
    tony

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

    iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmYok8kACgkQIdIFiZdL Ppb+OQ//fQUVHuQMEULpken/O+KKCphDArEnvamm1DBLFiBh444NM5KDibCjz3dd KkNvCNN+P7XBQat4de1kyY/w8S+GYkEIuSAIbPAhPsn1HbJf5X2lAbS4Ty1zBQ1i fbJNSuy/3I/q0alr66w/+xV10ONPB/1L3d39DiijwsM96dSAG3KY6ikz+nTjpExo MxHZtn39qTTAXiGHlSFM5hdZHkeGmJV078WMraCdQDqDN/6CSoD8snjlOGEdSecL wzSjlDR/6vFsrNNmgDvu/dAFreEIJ47JuMYcfTJAX21/9PzkQd7/OI4jCHUIYVHD 4ObLVQdegu2WlsGzpoc1vd8VmBk0rE1EEJN2t0Tc9NtH8pcjK3viFILNbEjZyhtC B6znQUrZmr+LT7z8MNxRn+uzJOSt3gWlyQa8ENqEx1oxhnm+f6hUEyEThwrKezZ4 tG6YEFwOAV9WnOkgmnjm7MgG4fNspE0ATavp8bb10Zk1n2aNGPZulTx1pFD4SnOG ladb+Zb+wjSiq4D0lkj4Wuy7+q4O213b2f2HC+P248/SE1/lBpLfMONT4i0kySRa PyrAHtCxD2sSx3U8NeRPGbLL6+EsP/5s302uzur4tQUDYE1XCZXWSxO6mC342NVB GAzIy0/1nQHIDYNyfUDPp+jR9uiM1A4OslHnFvGcG6kGV5DSvdg=
    =f6ew
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nate Bargmann@21:1/5 to All on Wed Apr 24 14:00:01 2024
    Is there a chance this could be made available to Stable users through backports.debian.org? I ask in case Logbook of The World were to
    require a version of TrustedQSL newer than that which is in Stable.
    Some years back that happened but that was before bdo was more popular.

    73, Nate

    --
    "The optimist proclaims that we live in the best of all
    possible worlds. The pessimist fears this is true."
    Web: https://www.n0nb.us
    Projects: https://github.com/N0NB
    GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819


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

    iF0EABECAB0WIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZijuKAAKCRD7LFEw1VqI GaaEAJ90P8u9TlEZZkB9+RzY8OMqUmD6NACeKDdZFaivi128IxrniGGfXsMh9tA=
    =p2L8
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony mancill@21:1/5 to Nate Bargmann on Wed Apr 24 18:20:01 2024
    On Wed, Apr 24, 2024 at 06:34:00AM -0500, Nate Bargmann wrote:
    Is there a chance this could be made available to Stable users through backports.debian.org? I ask in case Logbook of The World were to
    require a version of TrustedQSL newer than that which is in Stable.
    Some years back that happened but that was before bdo was more popular.

    Hi Nate,

    I will prepare a stable-bpo package for 2.7.3.

    Cheers,
    tony

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

    iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmYpL4IACgkQIdIFiZdL PpYIChAAvxDAgZmwtrVM+Tc1/FLzxkuFZ6hIgJGb/P7+Nxg6dkM2/MjgIH9osLCz 9yXTiWBDysFI9lTSe/RV9ZwGXmV37Es7423GYCM16BtOQoYl8i1GwLHN8a1USwzq n1/9wudAgodPieGomqo46Bs29/Dee8i/v/C9BxJG/2I5mF9lF3h3Y1SvVWXLFxqA QHaCd9lyD4RdvCLb034F3j0MCmf7WKFv6k+UK1pkC0rn1ctltGtPd+3gl8jWtd8V urVg54l3ZF8nAcf9aVv0bcSz7MpGQvtBfjlNeEU8Ye0FrWFqeHJX/dx/3e1V1qFx bc2j2pTzyPfLteujQng9ftGcmddjJHLToVb0aeknk7v9lrCm36Tqj75PWTOZ+8SV dwhlCQlQu+N7KKe7q2tMkXdiRyf+zL8CjakCtnZL1mFMntaB3CBTR6WOwEU2Jrzd xOzdUn+JgePvaPvdZ4arcAUkwrYJgRKnlPMMlImtCAhBt7XQRcIReZJ33iIWU1rV iXnk/DURGyj9jWGX8L2q1tzhD/mtZ+ybmeqo+nmgK385xV4Khri49sDRQPor2qO1 gQ3rnjkJf4COR7TtRLLCYfwZj+YMs2nrU6d8Mj1wAajc9bstTx/ttK8CT+82c9rR gVMURPB2ltsaeqhl68xJKPyVVd+7h0wcwXkC9+xSHLi3j+VI8Bc=
    =Ttgg
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nate Bargmann@21:1/5 to tony mancill on Wed Apr 24 20:20:02 2024
    * On 2024 24 Apr 11:14 -0500, tony mancill wrote:
    On Wed, Apr 24, 2024 at 06:34:00AM -0500, Nate Bargmann wrote:
    Is there a chance this could be made available to Stable users through backports.debian.org? I ask in case Logbook of The World were to
    require a version of TrustedQSL newer than that which is in Stable.
    Some years back that happened but that was before bdo was more popular.

    Hi Nate,

    I will prepare a stable-bpo package for 2.7.3.

    Thanks, Tony.

    - Nate

    --
    "The optimist proclaims that we live in the best of all
    possible worlds. The pessimist fears this is true."
    Web: https://www.n0nb.us
    Projects: https://github.com/N0NB
    GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819


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

    iF0EABECAB0WIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZilMAwAKCRD7LFEw1VqI GYcgAJ9m3Srbvzu4VwhZ9GvQo+FYOkKWiQCfSXR7hzyURErGk50IbBB1Y4tdnK8=
    =Obn8
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony mancill@21:1/5 to Nate Bargmann on Thu Apr 25 06:40:01 2024
    On Wed, Apr 24, 2024 at 01:14:28PM -0500, Nate Bargmann wrote:
    I will prepare a stable-bpo package for 2.7.3.

    I should have mentioned that the backport will need to wait for 2.7.3 to migrate to testing, and that might take some time due to trustedqsl
    being involved in multiple ongoing transitions [1]. Which means I owe
    the Release Managers an apology... I should have noticed that and
    uploaded 2.7.3 to experimental.

    In any event, it may take a while.

    [1] https://tracker.debian.org/pkg/trustedqsl

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Loren M. Lang@21:1/5 to Nate Bargmann on Sat Apr 27 13:00:01 2024
    On Wed, Apr 24, 2024 at 01:14:28PM -0500, Nate Bargmann wrote:
    * On 2024 24 Apr 11:14 -0500, tony mancill wrote:
    On Wed, Apr 24, 2024 at 06:34:00AM -0500, Nate Bargmann wrote:
    Is there a chance this could be made available to Stable users through backports.debian.org? I ask in case Logbook of The World were to
    require a version of TrustedQSL newer than that which is in Stable.
    Some years back that happened but that was before bdo was more popular.

    Hi Nate,

    I will prepare a stable-bpo package for 2.7.3.

    Thanks, Tony.

    Yes, I was actually planning on helping get this into backports as well (assuming Tony doesn't beat me) as that is basically what I am already
    doing with the Ubuntu PPAs, though Debian backports is a bit more of a
    formal procedure in comparison. And yes, as Tony mentioned, it looks
    like we'll need to wait for things to cool down a bit and have
    TrustedQSL get into testing before we can go forward and publish
    anything for backports.

    I originally got into doing this for Ubuntu after spending some time
    helping some users on the ARRL LoTW mailing list hand compile TrustedQSL
    for their Ubuntu boxes and decided I should just start backporting the
    latest Debian Sid release to the various current Ubuntu releases. Since
    Tony's been good about keeping it up-to-date, I just have the easy task
    of adjusting a few build-deps as needed for older Ubuntu releases and
    the occasional patch for compatibility.

    In any case, I decided to preemptively create a backport commit and
    discover what it takes. It looks like this package is simple to backport
    as it currently compiles cleanly on stable. All I had to do was create
    the appropriate changelog entry. I've tested it on Bookworm and it seems
    to be functioning properly. If you are interested in taking a look, I
    updated the backports branch on my fork here:

    https://salsa.debian.org/penguin359/trustedqsl/-/commits/debian/bookworm-backports

    73s,
    Loren
    K7IW



    - Nate

    --
    "The optimist proclaims that we live in the best of all
    possible worlds. The pessimist fears this is true."
    Web: https://www.n0nb.us
    Projects: https://github.com/N0NB
    GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819




    --
    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-----

    iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZizaSAAKCRDMe9wUn2Md 1/+rAQC4XMAK2nmxzKGS/GN9vT6m2GtJuwAaMZCFYSgbs1oBVAD/VlA3QeulCWsU VKltl/qJr++uzv61CPlh862cDcdC1Qk=
    =aCYr
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony mancill@21:1/5 to Loren M. Lang on Fri May 3 18:10:01 2024
    On Sat, Apr 27, 2024 at 03:58:22AM -0700, Loren M. Lang wrote:
    * On 2024 24 Apr 11:14 -0500, tony mancill wrote:
    I will prepare a stable-bpo package for 2.7.3.

    Uploaded and accepted into bpo.

    In any case, I decided to preemptively create a backport commit and
    discover what it takes. It looks like this package is simple to backport
    as it currently compiles cleanly on stable. All I had to do was create
    the appropriate changelog entry. I've tested it on Bookworm and it seems
    to be functioning properly. If you are interested in taking a look, I
    updated the backports branch on my fork here:

    https://salsa.debian.org/penguin359/trustedqsl/-/commits/debian/bookworm-backports

    Hi Loren,

    The commit in your fork looks fine. When I saw the migration of 2.7.3
    to testing, I used "dch --bpo" to quickly create the bookworm-backports changelog, but I could (and should) have simply merged your change.
    Thank you for your efforts here. I will coordinate better for future
    updates.

    Thank you,
    tony

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

    iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmY1C2YACgkQIdIFiZdL PpYW8BAAqUjhXWg064gJ1h65M/lu1XbTS+8zRgkz+CduMxyjbiAk8RduKJFQrPx5 Hn9Rwl0jVmH7tcHQSFu5nRnVB196yiyu1ZWFdsPE9T1/PZRFUAEXYeE7P34+kK9q Za2xvFSzxEpsBeen/cRyqTbYfOnfQ3Gqi+Eg8Q29zxS074d+1KYiY8XqKrgDHc2N 0QdnX1o5qHCa0A92a4CwM3oU5cpzDv1+50RyzmUgM3thdZOerf36bTtAzR1LbPWO V2TGOlJwLWfk9Nx24cyqqXS8uUuEbh4xotJtCP2qyQ8HtLZUAoctD4AlOFjj1ils x8yjM9IjWOdDhu3yFEn9RsChuASdn2uTtzfCqdxBfLe0uU2KcUEPrfpXsFBAGTp7 UGylnXowgS4vlzj/5MXQE9/pXqfUEmY2lJPKwREY5RMyifKM7SKL52wGxWNjM8bM pAgq3+S0/STNimJNKh2ymd9PEhgUlXM08D3jCcHnaiAI9deuW07aTX+JeZqjf/RI RAyjoUveSz1aDZwY9dJO3wIOF0l3GfBBJKAMPib359LcMBiF2av4YnZDPCnZb96a BKmcwQNqsX9PVRRLARPYVncSikqU9fxtbDdPGL+Y9RVQ7CeTpgrrrdfyV8nG5BkR GOeBDibIsrB+8CfmPhrUsV9jaYERuu2cHftpjunKH1f3C8XxAo4=
    =nPA6
    -----END PGP SIGNATURE-----

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