Hey Tom,
This is really an Xastir Debian packager issue. Doing a little digging,
I see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957970
It seems that alert was based on xastir/2.1.4+git20191127.bb66a77-3 but
since then, Adrian Bunk updated it to 2.1.6 and it
seems like the
The issue referenced (957970) is precisely the one that led to the fixes
back in Feb, and predate 2.1.6. So it sounds like they actually need to update
their package and try again, even though it's *claiming* that 2.1.6 doesn't
build. If there are still issues, it would be good if they'd
On Fri, Jul 24, 2020 at 03:32:49PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
>
> Well, we already fixed failures to build with gcc10 with commit c61e49b2
> in February, shortly before release 2.1.6. Wonder what new ones might have
> crept in.
>
> Can you tell
Well, we already fixed failures to build with gcc10 with commit c61e49b2
in February, shortly before release 2.1.6. Wonder what new ones might have
crept in.
Can you tell from the autoremoval posting what the new errors are?
On Fri, Jul 24, 2020 at 01:42:48PM -0700, we recorded a
Saw this warnings about compiling with GCC10 for Xastir and many other
ax25-apps, ax25-tools, ax25-utils, Linpac, axmail, UroNode, Quisk,
Soapy*, etc.
---David
Forwarded Message
Subject:xastir is marked for autoremoval from testing
Resent-Date:Thu, 23 Jul 2020
