Re: Preventing a broken release arch from blocking testing migration

2022-06-17 Thread Daniel Gröber
Hi Andrey, On Fri, Jun 17, 2022 at 05:51:36PM +0500, Andrey Rahmatullin wrote: > On Fri, Jun 17, 2022 at 02:01:42PM +0200, Daniel Gröber wrote: > > my package yosys has a test failure on mips64el that I can't figure out and > > consequently got removed from testing. I'm wondering how to deal with

Re: Preventing a broken release arch from blocking testing migration

2022-06-17 Thread Andrey Rahmatullin
On Fri, Jun 17, 2022 at 02:01:42PM +0200, Daniel Gröber wrote: > my package yosys has a test failure on mips64el that I can't figure out and > consequently got removed from testing. I'm wondering how to deal with this? > > From reading the policy it seems I can use the Architecture field to list

Re: Preventing a broken release arch from blocking testing migration

2022-06-17 Thread Jérémy Lal
Le ven. 17 juin 2022 à 14:31, Daniel Gröber a écrit : > Hi Mentors, > > my package yosys has a test failure on mips64el that I can't figure out and > consequently got removed from testing. I'm wondering how to deal with this? > > From reading the policy it seems I can use the Architecture field

Preventing a broken release arch from blocking testing migration

2022-06-17 Thread Daniel Gröber
Hi Mentors, my package yosys has a test failure on mips64el that I can't figure out and consequently got removed from testing. I'm wondering how to deal with this? From reading the policy it seems I can use the Architecture field to list all arches except mips64el. Is that the right thing to do