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 bogon-computron collision of the <[email protected]> flavor, containing: > > 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 04:58:23 +0000 (UTC) > Resent-From: [email protected] > Date: Thu, 23 Jul 2020 04:39:29 +0000 > From: Debian testing autoremoval watch <[email protected]> > To: [email protected] > > > > xastir 2.1.6-1 is marked for autoremoval from testing on 2020-08-06 > > It is affected by these RC bugs: > 957970: xastir: ftbfs with GCC-10 > > _______________________________________________ > Xastir mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir -- 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] _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
