Re: apt-pinning information
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 multiarch. The following
> > should be used for the Package line:
> >
> > | Package: *:any
> > |
> > | As far as I see the discussion referenced:
> > | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881047#10
> >
> > There is "this matches the documented behavior".
>
> With the use of a ":". What is said is that:
>
> As a special exception to the architecture wildcard rules, apt
> also accepts * in place of any, so you can write:
>
> /libfreetype6/:linux-*
> /libfreetype6/:*
>
> And this matches the documented behavior: [...]"
>
> 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)
> > At least as I see apt-doc, it is still having apt line like mine.
>
> The apt documentation has still not been fixed.
That is where we need update first.
Other than these multiarch related syntax and regex syntax, I don't see
"Obsoletes" mentioned in dependency documentation but I see it in the
source.
The most interesing information source were:
https://wiki.debian.org/Multiarch/HOWTO
https://wiki.ubuntu.com/MultiarchCross
> > So where is this documentation referenced.
> >
> > Also, does this match arch all package?
>
> The issue is that there is currently no mention of multiarch at all in
> the apt_preferences(5) man page. I've added the APT Development Team
> to Cc.
Someone knowledgeable needs to update:
doc/apt_preferences.5.xml
doc/guide.dbk
Osamu
Reply to: