[Xastir] Fwd: xastir is marked for autoremoval from testing

[David Ranch]

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 <bunk at debian.org> updated it to 2.1.6 and it 
seems like the alert was closed.  So, I think for the time being, the 
Debian's repos and downstreams (Ubuntu, Mint, etc) will continue to 
include Xastir.  :-)

--David
KI6ZHD




On 07/24/2020 05:22 PM, Tom Russo wrote:
> 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 actually bring
> them to our attention directly instead of just marking the package for removal.
>
> I had even answered that issue on their issue tracker back in April.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957970
>
>
> Also, you had posted back in April about this very same issue
> (http://xastir.org/pipermail/xastir/2020-April/025317.html).  This Debian
> issue was in fact the reason we pushed out a 2.1.6 point release.  The gcc10
> issues were fixed in Feb, but only available on the master branch until then.
> The issues were trivial to fix.
>
> On Fri, Jul 24, 2020 at 06:07:27PM -0600, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
>> On Fri, Jul 24, 2020 at 03:32:49PM -0600, we recorded a bogon-computron collision of the <russo at bogodyn.org> 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 from the autoremoval posting what the new errors are?
>> I just built Xastir with gcc 10 on FreeBSD with no errors.
>>
>> Don't know what the problem is on Debian.  Any details you can provide
>> would help.
>>
>> They marked Xastir for autoremoval because we had a single archaic optional
>> script that used Python 2.7, too.  I removed that script precisely to deal
>> with that autoremoval issue.
>>
>>> On Fri, Jul 24, 2020 at 01:42:48PM -0700, we recorded a bogon-computron collision of the <xastir at trinnet.net> 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: 	debian-hams at lists.debian.org
>>>> Date: 	Thu, 23 Jul 2020 04:39:29 +0000
>>>> From: 	Debian testing autoremoval watch <noreply at release.debian.org>
>>>> To: 	xastir at packages.debian.org
>>>>
>>>>
>>>>
>>>> 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
>>>> Xastir at lists.xastir.org
>>>> 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
>>> Xastir at lists.xastir.org
>>> 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
>> Xastir at lists.xastir.org
>> http://xastir.org/mailman/listinfo/xastir