Benefit of targeting any arch instead of known succesful ones is to help porters identify where work is needed - a.k.a. not hide problems, as we're all abiding to in our Social Contract.
You need not be concerned about FTBFS on strange archs affecting the package migrating to testing: Only FTBFS on archs already in testing are treated as severe - i.e. only regressions count. Only if this package lacks a proper testsuite and you know that builds on some archs even though technically succeeding will produce broken code. If that's the case I urge you to make it more visible e.g. to porters - one way could be to add arch checks in debian/rules that checks for build architecture and fails with a suitably descriptive error message that porters can see in build logs for those archs. Hope that helps, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
