[Debian-med-packaging] Bug#974555: fixed in edtsurf 0.2009-8

Andreas Tille andreas at an3as.eu
Sat Nov 14 18:43:25 GMT 2020


On Sat, Nov 14, 2020 at 07:14:27PM +0100, Paul Gevers wrote:
> > So the only solution I can imagine for this problem is to not
> > run the test at all on i386.  What do you think?
> 
> I can imagine a lot more, like track down why it hangs and fix the
> underlying issue. But I understand in your area, there's a lot of
> packages that don't work (properly) on i386.

I admit I was simply missing a "given my current time constraints" after
my imagination sentence.

> I still wonder though, does this mean the package is broken on i386? If
> so, shouldn't it be fixed for that reason? Or if that's really not
> possible (time constraints of volunteers), shouldn't the package be
> removed from i386 altogether, if you know it's broken. The question I'm
> asking is: what is this autopkgtest result telling you?

Providing those tools on i386 is probably only for the sake of
completeness of architecture coverage.  It has no practical usage
any more in this field.

> I have no clue about this package and it uses,

Me neither.  Steffen, Pranav, what do you think?

> just flushing some ideas
> that come to my mind.

Thanks a lot for all your effort in autopkgtests 

    Andreas.


> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list