Hi Mattia > > * you're using any-amd64 and any-i386, then why do you explicitly list > hurd-i386 kfreebsd-amd64 kfreebsd-i386 too? Ok. I will remove these. > * you're changing only one binary, what about the others? from what I'm > seeing the failure is in the configure step which is done by all > binaries, so this change wouldn't fix the FTBFS) A mistake. But can I exclude arm only for the qt5 libraries? The qt5 libraries have never been in testing so I guess it may be easier. Do you know of any package where only the a part is built for all architectures? > * why are you not closing the bug? Because it isn't solved. I would prefer to port the code to use GL that works on arm but until that is done I will exclude arm. I will reduce the bugs severity as soon as version -10 is uploaded. > * do you know that to allow the testing migration you'd still need to > remove the binaries from unstable by filing a bug against > ftp.debian.org? actually that would be enough, even without > restricting the architecures where you build, then you can leave the > packages in FTBFS state there until it could build again. Sorry, I didn't know but that sounds reasonable. But if I keep the qt4 binaries in but only restrict the qt5 binaries. Do I then still need to file a bug?
Regards Gudjon
