Your message dated Tue, 22 Nov 2016 19:24:33 -0800 with message-id <[email protected]> and subject line Re: Bug#845369: debian-policy: [5.6.8] Not fully updated for "any all" has caused the Debian Bug report #845369, regarding debian-policy: [5.6.8] Not fully updated for "any all" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 845369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845369 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: debian-policy Severity: minor In policy 3.9.3.0 (at least according to upgrading-checklist.txt): 5.6.8 The `Architecture' field in `*.dsc' files may now contain the value `any all' for source packages building both architecture-independent and architecture-dependent packages. The current 5.6.8 does describe `any all`, but unfortunately it also still contains this paragraph which is no longer correct since this change: In the main `debian/control' file in the source package, this field may contain the special value `all', the special architecture wildcard `any', or a list of specific and wildcard architectures separated by spaces. If `all' or `any' appears, that value must be the entire contents of the field. Most packages will use either `all' or `any'. I'd suggest updating this to: In the main `debian/control' file in the source package, this field may contain the special value `all', the special architecture wildcard `any', the special combination `any all`, or a list of specific and wildcard architectures separated by spaces. If `all', `any', or `any all` appears, that value must be the entire contents of the field. Most packages will use either `all', `any', or `any all`. (Credit for noticing this should go to sarnold on #launchpad). Cheers, Olly
--- End Message ---
--- Begin Message ---Olly Betts <[email protected]> writes: > In policy 3.9.3.0 (at least according to upgrading-checklist.txt): > 5.6.8 > The `Architecture' field in `*.dsc' files may now contain the > value `any all' for source packages building both > architecture-independent and architecture-dependent packages. > The current 5.6.8 does describe `any all`, but unfortunately it also still > contains this paragraph which is no longer correct since this change: > In the main `debian/control' file in the source package, this field > may contain the special value `all', the special architecture wildcard > `any', or a list of specific and wildcard architectures separated by > spaces. If `all' or `any' appears, that value must be the entire > contents of the field. Most packages will use either `all' or `any'. This paragraph isn't talking about that file. As it says at the top of the paraagraph, this is about the debian/control file. The *.dsc file of a source package is not the debian/control file. If you read down two more paragraphs, you'll find: In the Debian source control file .dsc, this field contains a list of architectures and architecture wildcards separated by spaces. When the list contains the architecture wildcard any, the only other value allowed in the list is all. which does indeed allow the behavior that you expect. Unfortunately, the Debian control file format contains multiple fields that have different allowable values and different semantics in the various possible files, and one has to read carefully to see whether a particular value is allowed in that context. One could imagine a world in which this was designed differently and different fields were used in those different contexts, but that's water under the bridge at this point. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--- End Message ---
