-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear David,
Le 01/11/2016 à 15:57, David Kalnischkies a écrit : > On Tue, Nov 01, 2016 at 02:43:21PM +0100, Thibaut Paumard wrote: >> How do you actually use Multi-Arch: allowed? Should a dependent >> package then specify either <package>:same or <package>:foreign? >> Looks > > Neither is valid syntax. What you do with these is depending on a > package with the literal architecture "same" (or "foreign"). Thats > not going to work… > > >> I was able to find documentation about what allowed is supposed >> to do, but not on how to depend on such a package. >> https://wiki.debian.org/Multiarch/HOWTO > > The spec [0] linked from that page says how, but in summary: Thanks, I was not able to parse it correctly apparently. > If a package (lets say perl) is marked as Multi-Arch: allowed your > package foo can depend on perl:any and a perl package from any > (foreign) architecture will statisfy this dependency, while a > 'simple' perl would have just accepted a perl from the architecture > your package foo was built for (with arch:all mapped to > arch:native). > [...] > If it helps: Instead of "perl having Multi-Arch: allowed" envision > it to have a "perl provides perl:any" and you are depending on this > virtual package – which also explains why such a missing provides > causes perl:any to be unresolveable. That makes things clearer, thanks. > > That said, the usecase for 'allowed' is small – mostly > interpreters – and you are trying to use it on… a -dbg package? I > haven't looked closely, but that smells wrong… What are you trying > to express here? The -dbg package is Multi-Arch same. It Depends on the packages for which it provides debugging symbols, some of which are Multi-Arch: allowed. Lintian complains when I don't specify an architecture for those packages: W: gyoto source: dependency-is-not-multi-archified gyoto-dbg depends on gyoto-bin (multi-arch: allowed) N: N: The package is Multi-Arch "same", but it depends on a package that is N: neither Multi-Arch "same" nor "foreign". N: N: Refer to https://wiki.ubuntu.com/MultiarchSpec for details. N: N: Severity: normal, Certainty: possible N: N: Check: group-checks, Type: source N: By the way, by the same logic that interpreters should (or can?) be Multi-Arch: allowed, I expect that - extensions for those interpreters also should (or can?); - any tool that is able to process an input data file to produce a arch-independent output also should (or can?) be either "foreign" or "allowed". Is that correct? > (and have you heard that automatic debug packages are a thing > nowadays?) Yes. Last time I checked, it was not clear how to use them in backports though. > > > Best regards > > David Kalnischkies > > [0] https://wiki.ubuntu.com/MultiarchSpec [1] There are ways around > it. See the "If it helps" remark for a hint. > Kind regards, Thibaut. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYGMy/AAoJEJOUU0jg3ChA+hwQAKh7C+MfqrTPAL8WPQeUVAQh ZT6N2R2ugOmUBwW2wGtLvA1V6A6Nr9QME7Yjs9DVppd8kV5mWmOT1hJMyu+Wn0Hi XNvDIKrH9R6vgdRRyIxZIeSFdedf8QUYmEPnP7hkE8oTazFcTe8LpZfB4Ju3Blbp u+er1S7qSBei9ZEpsYKP13HA9G1C33Y7rTmgCgqm9sxuk7GmPiF5CKGR2JHS7kAZ YVodtJOF7diiuKfP6XQdKNUCgjH7x9EHk8BZ9s4sNeOb+TpAPRlvhTdb4c30i32e vGBUtP8VLRHH8IfxxrldmJecb8StHg+uE1+nM9jBFYRJ/hPAq1z22SeY1COMwyyd JSBaCD24XBC+YGgOBfVTz8F7r6hkumuQoJhgcARhRCVkYPQ9hxYFnzgz1igcoSTt tJ8YKgObWdItjC8MF9a1fayPwS7krAwKdB+/h4aZqft8fXPgc+d16b+8izjRvRhP 1WHp2GnG9Y3Tstvibge7AH13J2u/NxykZc3OyN/SdW1FBdMAEUuVvRGYPG+4ddqL zycMWjmgy+5QS3ts246foT/4OSfG+30ooFct7ikLEnWajzd1u5IocB95/wUzgaKq 0+VNTj8tLUpWibIipNTxDHeVTRpGERzxJGqv20ztgtGSG6bX75gGrFncoev0ykox n7sbt9I4/AUJbqvrFoWM =UNTB -----END PGP SIGNATURE-----
