Control: tags -1 moreinfo On 2014-10-22 18:11, Wookey wrote: > Package: lintian > Version: 2.5.28 > Severity: normal > > It seems that Lintian does not understand arch-qualified dependencies, > or build-dependencies. > > If a package has an arch-qualified build-dependency on a > build-essential package, such as on libc:armhf, then lintian complains > about depends-on-build-essential-package-without-using-version > > But when the dependency is on a package from a foreign arch this is > not wrong. This applies to both build-deps and deps. > > An example package which triggers this is cross-gcc-4.9-armel (currently in > NEW). > >
Yes, Lintian does not support ":$arch" and I would like to see documentation on the relations between "pkg", "pkg:any" and "pkg:$arch" dependencies before implementing it. In particular, it is not clear to me whether (e.g.) "pkg:$arch" implies "pkg:any" or/and "pkg" (or/and vice versa). Nor is it clear to me to what extend the "pkg:$arch" relations are supported. I presume dpkg and APT in Jessie know of them (since you are filing the bug); what about Wheezy? ~Niels -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
