Bug#881063: apt-pinning information

2018-01-11 Thread Vincent Lefevre
On 2018-01-11 12:57:02 +0100, David Kalnischkies wrote: > On Thu, Jan 11, 2018 at 02:33:03PM +0900, Osamu Aoki wrote: > > > i.e. if you want to match all packages of any architecture, *:* is > > > OK just like *:any, but * alone is not. > > > > "*" alone seems to be treated as "*:native" (??and

Bug#881063: apt-pinning information

2018-01-11 Thread David Kalnischkies
On Thu, Jan 11, 2018 at 02:33:03PM +0900, Osamu Aoki wrote: > > i.e. if you want to match all packages of any architecture, *:* is > > OK just like *:any, but * alone is not. > > "*" alone seems to be treated as "*:native" (??and "*:all"??) > architectures. (apt-pkg/cacheset.cc) This code

Bug#881063: apt-pinning information

2018-01-10 Thread Osamu Aoki
Hi, I think there is serious lack of documentation on how apt system works. On Wed, Jan 10, 2018 at 04:31:14PM +0100, Vincent Lefevre wrote: > Hi, > > On 2018-01-10 23:11:07 +0900, Osamu Aoki wrote: > > do you still think your statement: > > > > This is incorrect, as not compatible with

Bug#881063: apt-pinning information

2018-01-10 Thread Vincent Lefevre
Hi, On 2018-01-10 23:11:07 +0900, Osamu Aoki wrote: > do you still think your statement: > > This is incorrect, as not compatible with multiarch. The following > should be used for the Package line: > > | Package: *:any > | > | As far as I see the discussion referenced: > |

Bug#881063: apt-pinning information

2018-01-10 Thread Osamu Aoki
Hi, As for https://bugs.debian.org/881063, it has 2 issues: * typo "as as". That is fixed. (thanks) * apt-pinning for multiarch do you still think your statement: This is incorrect, as not compatible with multiarch. The following should be used for the Package line: | Package: