On Thu, May 14, 2009 at 09:02:52AM -0500, Peter Samuelson wrote: > I thought in that case we were supposed to use 'any' and add an entry > to Packages-arch-specific. Or, if it's just one binary package from a > larger source package, use 'any' and decide in debian/rules whether to > build that binary package (DH_OPTIONS += -Nfoobar, for example).
I've worked on FTBFS-with-new-GCC bugs before, and realized only after putting significant work into the bug that the package didn't build on amd64, only on i386. Therefore, I think that the package should have a proper list of archs that prevents this problem. P-a-s is fine for the buildds, but if you actually want people to volunteer to fix bugs on your package, you shouldn't make it harder on them. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
