[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: Update TrustedQSL to upstream release 2.7.4



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

Attachment: signature.asc
Description: PGP signature


Reply to: