Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
The bug in question is related to Debian packaging, not Xastir's source code. Someone hacked in a modification to the configure script to add the git SHA to the version number in the AC_INIT call for the purposes of Debian packaging (with which the Xastir group has nothing to do). This was a broken hack, and they appear already to have undone it. The version number in AC_INIT *IS* used to construct the TOCALL, so it was wrong to have modified it. We didn't do that, someone named Tony Mancil did in their package repo back in November. As of this morning, there is a new commit in the Debian package repo undoing that: https://salsa.debian.org/debian-hamradio-team/xastir/commits/master On Sun, Feb 23, 2020 at 10:16:34AM -0700, we recorded a bogon-computron collision of the flavor, containing: > This is super puzzling, as Xastir has no commit b40016c, and the commit > that added the git version string to the version number used internally by > Xastir is NOT used for the TOCALL. > > Xastir's internal version number (used only in the Help->About dialog) has > had the git SHA-1 in it since Xastir commit ba3b807 in 2017, and this has > not impacted the AX.25 TOCALL in all that time. > > I have been using Xastir off of the development branch forever, and can > transmit just fine. My TOCALL is APX215. > > Could the commit referenced be a commit in a Debian repo that somehow > added the SHA-1 to something other than what Xastir's build system does? > > On Sun, Feb 23, 2020 at 07:57:02AM -0800, we recorded a bogon-computron > collision of the flavor, containing: > > > > I don't know if anyone saw this yet... > > > > --David > > KI6ZHD > > > > > > Forwarded Message > > Subject:Bug#952116: xastir: Impossible to transmit due to malformed > > TOCALL > > Resent-Date:Sun, 23 Feb 2020 10:57:01 + > > Resent-From:Iain R. Learmonth > > Resent-To: debian-bugs-d...@lists.debian.org > > Resent-CC: Debian Hamradio Maintainers > > Date: Sun, 23 Feb 2020 10:47:38 + > > From: Iain R. Learmonth > > Reply-To: Iain R. Learmonth , 952...@bugs.debian.org > > To: Debian Bug Tracking System > > > > > > > > Package: xastir > > Version: 2.1.4+git20191127.bb66a77-2 > > Severity: grave > > Justification: renders package unusable > > > > Hi, > > > > Commit b40016c updated a patch on the version number to add a git commit > > reference as part of the version number. Xastir uses this version number > > to form the TOCALL, which is usuall of the form APXnnn but now has a > > plus followed by the 7 digit ref. This does no longer fit in the 6 bytes > > allowed for a TOCALL in the AX.25 protocol. It also prevents operation > > with APRS-IS. > > > > Thanks, > > Iain. > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Tom RussoKM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
Xastir's versions are goofy. The history of this is ancient, and there has been no reason to ungoof it. Even numbers are releases, odd numbers are working development versions, and are generally not updated for every commit --- Xastir 2.1.5 just means "development branch after stable 2.1.4". The TOCALL for the current development version of Xastir should be APX215, and there should be no need for finer granularity to show which commit on every transmit. The ambiguity of "which commit of the dev branch am I using?" is resolved using the Help->About box. This can only matter to the user him/her self, and need not be transmitted in every packet. A TOCALL of APX215 should be enough for all interested parties on the receive end. If there is a need for a stable release so that distros can have a stable version, we should push one out. There is an open project on github for our next release with a number of required fixes before we do it. There was a flurry of activity on some of those issues a while back, but between people being injured, having other projects, and what not, nothing's been done for quite a while. If there is a real need for a stable release, we could probably use a little help. The open issues that we expected to have fixed for the next release (nominally dubbed Xastir 2.2.0) can be seen at: https://github.com/Xastir/Xastir/projects/2 Some might need punting. On Sun, Feb 23, 2020 at 08:56:54AM -0800, we recorded a bogon-computron collision of the flavor, containing: > > Hello Dave, > > The scenario here seems to be if you're running an intermediate release > Xastir and not an official tagged release. > > Dave, yes, I see you on APRS-IS : https://aprs.fi/info/a/KB3EFS and it shows > you're running v2.15 (APX215) per the "Last Path" line: > >KB3EFS>*APX215* via TCPIP*,qAC,T2ONTARIO > > > The question here is if you're running a version of Xastir that's between > v2.15 and v2.16, what should Xastir report as it's version to APRS-IS? It's > not clear if it's illegal but maybe this would be legal: > >APX21G > > --David > KI6ZHD > > > > > On 02/23/2020 08:43 AM, David A Aitcheson wrote: > > I did & was checking validity before making noise... > > > > Given that I only am able to be on APRS via an Internet connection > > (read: no radio use allowed)... > > > > Given that I only build from source (read: I don't use a package from a > > repository)... > > > > I think that it is not effecting me... > > > > David KI6ZHD - can you see me ( "KB3EFS" ) on the map in NY State? > > > > 73 > > Dave > > KB3EFS > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Tom RussoKM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
This is super puzzling, as Xastir has no commit b40016c, and the commit that added the git version string to the version number used internally by Xastir is NOT used for the TOCALL. Xastir's internal version number (used only in the Help->About dialog) has had the git SHA-1 in it since Xastir commit ba3b807 in 2017, and this has not impacted the AX.25 TOCALL in all that time. I have been using Xastir off of the development branch forever, and can transmit just fine. My TOCALL is APX215. Could the commit referenced be a commit in a Debian repo that somehow added the SHA-1 to something other than what Xastir's build system does? On Sun, Feb 23, 2020 at 07:57:02AM -0800, we recorded a bogon-computron collision of the flavor, containing: > > I don't know if anyone saw this yet... > > --David > KI6ZHD > > > Forwarded Message > Subject: Bug#952116: xastir: Impossible to transmit due to malformed > TOCALL > Resent-Date: Sun, 23 Feb 2020 10:57:01 + > Resent-From: Iain R. Learmonth > Resent-To:debian-bugs-d...@lists.debian.org > Resent-CC:Debian Hamradio Maintainers > Date: Sun, 23 Feb 2020 10:47:38 + > From: Iain R. Learmonth > Reply-To: Iain R. Learmonth , 952...@bugs.debian.org > To: Debian Bug Tracking System > > > > Package: xastir > Version: 2.1.4+git20191127.bb66a77-2 > Severity: grave > Justification: renders package unusable > > Hi, > > Commit b40016c updated a patch on the version number to add a git commit > reference as part of the version number. Xastir uses this version number > to form the TOCALL, which is usuall of the form APXnnn but now has a > plus followed by the 7 digit ref. This does no longer fit in the 6 bytes > allowed for a TOCALL in the AX.25 protocol. It also prevents operation > with APRS-IS. > > Thanks, > Iain. > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Tom RussoKM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
David, I did a "update-xastir" using the script included in the source code that gets the latest and greatest from Github via git at 10:57 EST today. My OS is Ubuntu 14.04.06?-LTS. Yes, I know it is beyond EOL. This is the best I can do given the tools and scripts I have to work with. Given that it is "illegal" (just like my saying my callsign at the end of every voice transmission has been deemed illegal) I might as well just give up on Ham Radio all together. KB3EFS OUT On 2/23/20 11:56 AM, David Ranch wrote: > > Hello Dave, > > The scenario here seems to be if you're running an intermediate > release Xastir and not an official tagged release. > > Dave, yes, I see you on APRS-IS : https://aprs.fi/info/a/KB3EFS and it > shows you're running v2.15 (APX215) per the "Last Path" line: > > KB3EFS>*APX215* via TCPIP*,qAC,T2ONTARIO > > > The question here is if you're running a version of Xastir that's > between v2.15 and v2.16, what should Xastir report as it's version to > APRS-IS? It's not clear if it's illegal but maybe this would be legal: > > APX21G > > --David > KI6ZHD > > > > > On 02/23/2020 08:43 AM, David A Aitcheson wrote: >> I did & was checking validity before making noise... >> >> Given that I only am able to be on APRS via an Internet connection >> (read: no radio use allowed)... >> >> Given that I only build from source (read: I don't use a package from >> a repository)... >> >> I think that it is not effecting me... >> >> David KI6ZHD - can you see me ( "KB3EFS" ) on the map in NY State? >> >> 73 >> Dave >> KB3EFS > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
Thank you for the bug report. This is easily addressed. Since we are building from a snapshot - i.e., a version somewhere between 2.1.4 and 2.1.5, is there a preference for which we use for configure? Given that 2.1.5 isn't released yet, my inclination is to use 2.1.4. I will prepare the update but check for guidance from the list before uploading. Thanks, tony On Sun, Feb 23, 2020 at 07:57:02AM -0800, David Ranch wrote: > > I don't know if anyone saw this yet... > > --David > KI6ZHD > > > Forwarded Message > Subject: Bug#952116: xastir: Impossible to transmit due to malformed > TOCALL > Resent-Date: Sun, 23 Feb 2020 10:57:01 + > Resent-From: Iain R. Learmonth > Resent-To:debian-bugs-d...@lists.debian.org > Resent-CC:Debian Hamradio Maintainers > Date: Sun, 23 Feb 2020 10:47:38 + > From: Iain R. Learmonth > Reply-To: Iain R. Learmonth , 952...@bugs.debian.org > To: Debian Bug Tracking System > > > > Package: xastir > Version: 2.1.4+git20191127.bb66a77-2 > Severity: grave > Justification: renders package unusable > > Hi, > > Commit b40016c updated a patch on the version number to add a git commit > reference as part of the version number. Xastir uses this version number > to form the TOCALL, which is usuall of the form APXnnn but now has a > plus followed by the 7 digit ref. This does no longer fit in the 6 bytes > allowed for a TOCALL in the AX.25 protocol. It also prevents operation > with APRS-IS. > > Thanks, > Iain. > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir signature.asc Description: PGP signature ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
Hello Dave, The scenario here seems to be if you're running an intermediate release Xastir and not an official tagged release. Dave, yes, I see you on APRS-IS : https://aprs.fi/info/a/KB3EFS and it shows you're running v2.15 (APX215) per the "Last Path" line: KB3EFS>*APX215* via TCPIP*,qAC,T2ONTARIO The question here is if you're running a version of Xastir that's between v2.15 and v2.16, what should Xastir report as it's version to APRS-IS? It's not clear if it's illegal but maybe this would be legal: APX21G --David KI6ZHD On 02/23/2020 08:43 AM, David A Aitcheson wrote: I did & was checking validity before making noise... Given that I only am able to be on APRS via an Internet connection (read: no radio use allowed)... Given that I only build from source (read: I don't use a package from a repository)... I think that it is not effecting me... David KI6ZHD - can you see me ( "KB3EFS" ) on the map in NY State? 73 Dave KB3EFS ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
I did & was checking validity before making noise... Given that I only am able to be on APRS via an Internet connection (read: no radio use allowed)... Given that I only build from source (read: I don't use a package from a repository)... I think that it is not effecting me... David KI6ZHD - can you see me ( "KB3EFS" ) on the map in NY State? 73 Dave KB3EFS On 2/23/20 10:57 AM, David Ranch wrote: > > I don't know if anyone saw this yet... > > --David > KI6ZHD > > > Forwarded Message > Subject: Bug#952116: xastir: Impossible to transmit due to > malformed TOCALL > Resent-Date: Sun, 23 Feb 2020 10:57:01 + > Resent-From: Iain R. Learmonth > Resent-To: debian-bugs-d...@lists.debian.org > Resent-CC: Debian Hamradio Maintainers > Date: Sun, 23 Feb 2020 10:47:38 + > From: Iain R. Learmonth > Reply-To: Iain R. Learmonth , 952...@bugs.debian.org > To: Debian Bug Tracking System > > > > Package: xastir > Version: 2.1.4+git20191127.bb66a77-2 > Severity: grave > Justification: renders package unusable > > Hi, > > Commit b40016c updated a patch on the version number to add a git commit > reference as part of the version number. Xastir uses this version number > to form the TOCALL, which is usuall of the form APXnnn but now has a > plus followed by the 7 digit ref. This does no longer fit in the 6 bytes > allowed for a TOCALL in the AX.25 protocol. It also prevents operation > with APRS-IS. > > Thanks, > Iain. > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL
I don't know if anyone saw this yet... --David KI6ZHD Forwarded Message Subject: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL Resent-Date:Sun, 23 Feb 2020 10:57:01 + Resent-From:Iain R. Learmonth Resent-To: debian-bugs-d...@lists.debian.org Resent-CC: Debian Hamradio Maintainers Date: Sun, 23 Feb 2020 10:47:38 + From: Iain R. Learmonth Reply-To: Iain R. Learmonth , 952...@bugs.debian.org To: Debian Bug Tracking System Package: xastir Version: 2.1.4+git20191127.bb66a77-2 Severity: grave Justification: renders package unusable Hi, Commit b40016c updated a patch on the version number to add a git commit reference as part of the version number. Xastir uses this version number to form the TOCALL, which is usuall of the form APXnnn but now has a plus followed by the 7 digit ref. This does no longer fit in the 6 bytes allowed for a TOCALL in the AX.25 protocol. It also prevents operation with APRS-IS. Thanks, Iain. ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
