Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-26 Thread Andres Mejia
Package: debian-policy Version: 3.8.1.0 Severity: wishlist Tags: patch Support for architecture wildcards has been added to dpkg-1.13.13, yet there's no clear policy as to how architecture wildcards should be used for other tools such as sbuild and pbuilder. There has been recent discussions abou

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-26 Thread Andrew McMillan
I support this proposal, as written. Clearly this should have been in policy some time ago. Cheers, Andrew. On Tue, 2009-05-26 at 18:50 -0400, Andres Mejia wrote: > Package: debian-policy > Version: 3.8.1.0 > Severity: wishlist > Tags: patch > > Support f

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Julien Cristau
On Tue, May 26, 2009 at 18:50:42 -0400, Andres Mejia wrote: > @@ -2723,7 +2725,8 @@ Package: libc6 > In the main debian/control file in the source > package, or in the source package control file > .dsc, one may specify a list of architectures > - separated by

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Andres Mejia
On Wednesday 27 May 2009 06:51:58 Julien Cristau wrote: > On Tue, May 26, 2009 at 18:50:42 -0400, Andres Mejia wrote: > > @@ -2723,7 +2725,8 @@ Package: libc6 > > In the main debian/control file in the source > > package, or in the source package control file > > .dsc, one m

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Julien Cristau
On Wed, May 27, 2009 at 07:30:57 -0400, Andres Mejia wrote: > On Wednesday 27 May 2009 06:51:58 Julien Cristau wrote: > > This makes it sound like you can't mix architecture names and > > architecture wildcards. Is that on purpose? > > Current policy has this wording and I didn't want to change

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Andres Mejia
On Wednesday 27 May 2009 07:49:09 Julien Cristau wrote: > On Wed, May 27, 2009 at 07:30:57 -0400, Andres Mejia wrote: > > On Wednesday 27 May 2009 06:51:58 Julien Cristau wrote: > > > This makes it sound like you can't mix architecture names and > > > architecture wildcards. Is that on purpose? >

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Andrew McMillan
On Wed, 2009-05-27 at 14:33 -0400, Andres Mejia wrote: > > > > > > Current policy has this wording and I didn't want to change that, so > > > yes, it's on purpose. > > > > Not quite. Current policy says "arch list or 'any' or 'all'" and that's > > fine (at least for debian/control), because it wou

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-05-27 Thread Andres Mejia
On Wednesday 27 May 2009 17:22:19 Andrew McMillan wrote: > On Wed, 2009-05-27 at 14:33 -0400, Andres Mejia wrote: > > > > Current policy has this wording and I didn't want to change that, so > > > > yes, it's on purpose. > > > > > > Not quite. Current policy says "arch list or 'any' or 'all'" and

Bug#530687: debian-policy: Please provide policy for architecture wildcards

2009-06-23 Thread Guillem Jover
Hi! On Tue, 2009-05-26 at 18:50:42 -0400, Andres Mejia wrote: > Package: debian-policy > Version: 3.8.1.0 > Severity: wishlist > Tags: patch > Support for architecture wildcards has been added to dpkg-1.13.13, yet there's > no clear policy as to how architecture wildcards should be used for other