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 +0000 > Resent-From: Iain R. Learmonth <irl@debian.org> > Resent-To: debian-bugs-dist@lists.debian.org > Resent-CC: Debian Hamradio Maintainers <debian-hams@lists.debian.org> > Date: Sun, 23 Feb 2020 10:47:38 +0000 > From: Iain R. Learmonth <irl@debian.org> > Reply-To: Iain R. Learmonth <irl@debian.org>, 952116@bugs.debian.org > To: Debian Bug Tracking System <submit@bugs.debian.org> > > > > 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
Attachment:
signature.asc
Description: PGP signature