Control: tag -1 + moreinfo Hi,
intrigeri: > I am basically clueless about multiarch stuff. Is anyone else on the > team knowledgeable in this area, or should we seek help elsewhere? Thanks to Helmut's help on IRC I took a closer look. 1. apparmor This package is arch:any and builds architecture-specific binaries, so after reading a bit of https://wiki.ubuntu.com/MultiarchSpec, it seems dubious to me that it "should be allowed to satisfy the dependencies of a package of another architecture than its own". I mean, this might work in the specific "armhf on arm64" case but it won't work e.g. for "amd64 on arm64" because apparmor_parser simply cannot be executed there. Riku, is that right or did I understand the meaning of "Multi-Arch: foreign" wrong? (Only matters if I'm wrong above:) I had a look and I believe that the only thing that can potentially expose the architecture is apparmor_parser, so this boils down to "is the output of apparmor_parser architecture-dependent?"; we can make this package Multi-Arch: foreign if, and only if, the answer to this question is "no". John, do you know the answer by heart? 2. apparmor-utils This package is arch:any as well. I admit I'm not sure why and it may be a leftover from previous implementation of these tools: nowadays this package installs only Python 3 and shell scripts. I think it could be converted to arch:all and then possibly Multi-Arch: foreign can be added. Cheers, -- intrigeri