[arch-dev-public] signoff policy for "any" packages

Dan McGee dpmcgee at gmail.com
Sat Nov 28 12:23:06 EST 2009

On Sat, Nov 28, 2009 at 6:38 AM, Giovanni Scafora
<giovanni at archlinux.org> wrote:
> 2009/11/28, Allan McRae <allan at archlinux.org>:
>> What is the signoff policy for "arch=any" packages?  Do we still need one
>> for each architecture?  Or just one.  If one, should it be form the opposite
>> architecture it was built on?
> For arch=any packages, I think that is enough 1 signoff only.
> Is it right?

The problem with this is when your 1 signoff comes from someone using
the same arch as you, and you put ELF files in the package without
paying attention, you lose.

I think there are multiple ways to make it easier. One is to show that
you have used namcap to verify there are no architecture-dependent
files in the package. Also let people know what architecture you built
it on; a signoff from the opposite architecture would be good enough
as others noted.


More information about the arch-dev-public mailing list