Besides the point, I believe that you and Ciaran are a minority in testing packages on multiple architectures. However a non-fatal warning would not hamper your ability to work. If it can be configured that would of course even be better.
Paul
Yay for being part of the minority. I have access to sparc, mips, and x86 hardware, but I usually keep my commits to stuff that only affects mips (and sometimes sparc). But Weeve raises a valid point. If a dev is updating a package that has multiple arch keywords, only the keyword(s) that the dev has access to and has tested on should be changed if a masked->unstable or unstable->stable move is needed. Probably the *only* exceptions to this will be for packages which do not need compiling, like shell-script-based packages (my crossdev script for example).
At minimum, send an email to the arch lead or arch mail alias, or even ping on IRC before tweaking keywords.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond
-- [EMAIL PROTECTED] mailing list
