[Xastir] Bug#952116: [russo at bogodyn.org: Re: Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL]

[Tom Russo]

Then the git sha displayed in Xastir will be the git sha in your package
repo.  That is probably OK, though, and will accurately reflect its status
in your package management system.

If you want the About box to have the SHA-1 in our repo, you should just
hack XastirGitStamp to display our SHA-1 instead of using git to probe for it,
or have it return nothing at all.  You're already patching our stuff to fit
in with your choices, this should be no big deal.

The feature is in place to allow our power users (all of whom build from source
themselves and don't use packaged versions) to see what version of the code
they're actually using based on their git SHAs.  It's gonna stay there.


On Sun, Feb 23, 2020 at 08:32:57PM +0100, we recorded a bogon-computron collision of the <myon at debian.org> flavor, containing:
> Re: Tom Russo 2020-02-23 <20200223182310.GA7622 at bogodyn.org>
> > The script looks in the top level of the Xastir source tree being built
> > for the presence of a .git directory.  The fact that the source tree is under
> > a package directory that is itself in git should have no impact (there will
> > then be a .git directory at a higher level, and our script will simply 
> > be unaware of it and return no SHA at all).
> 
> In the packaging repo, xastir is in the top level directory.
> 
> https://salsa.debian.org/debian-hamradio-team/xastir
> 
> Christoph

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]