Hi all, I'm filing a report upstream currently, but there's a lack of activity so let's not hold our collective breath.
I'll take a wee dig into the program and see if I can find a point where it parses the config file to exit on N0CALL-1. Couple of questions: * Debian Janitor has given us some updates and there's a 2.9.0+dfsg-3 sat UNRELEASED. Will we see any issues from this being added to the distro at this stage if combined with a fix? * Is exiting gracefully if N0CALL-1 is found going to cause a failed upgrade? -- Hibby MM0RFN On Sun, 25 Apr 2021, at 7:42 PM, Apostolos Kefalas wrote: > On Sun, 2021-04-25 at 17:54 +0300, Heikki Hannikainen wrote: > > > > > > > I think it should be possible to detect the "N0CALL" configurations on > > > upgrade and disable the service, thus reaching the same state as with my > > > above change for new installs. > > > > Right, something like a grep for the bad "^mycall\s+N0CALL-1" would be a > > suitable trigger. > > > > - Hessu > > > IMHO this check should be done by aprx and if mycall is not configured should > exit properly. > > I would open an issue at https://github.com/PhirePhly/aprx/issues > >
