Bug#695229: chromium-inspector: should be 'Multi-Arch: foreign' so that chromium:{arch} is installable

2012-12-05 Thread Jonathan Nieder
Hi, Peter Samuelson wrote: In order to install chromium:i386 on my amd64 system, its dependency, chromium-inspector, would need to be Multi-Arch: foreign. This is because it is Architecture: all, which in a multi-arch context is calculated as Architecture: {primary installed arch}. Are you

Bug#695229: chromium-inspector: should be 'Multi-Arch: foreign' so that chromium:{arch} is installable

2012-12-05 Thread Peter Samuelson
[Jonathan Nieder] Are you sure? Could you send output from trying to install it? I used interactive aptitude and it can't install chromium:i386 because it can't find a candidate for the chromium-inspector dependency. (I had always thought that in the multi-arch world Arch: all meant with

Bug#695229: chromium-inspector: should be 'Multi-Arch: foreign' so that chromium:{arch} is installable

2012-12-05 Thread Jonathan Nieder
Peter Samuelson wrote: [Jonathan Nieder] (I had always thought that in the multi-arch world Arch: all meant with the same architecture as its dependencies.) That's what they want you to think! No, for dependency resolution purposes, arch:all is equivalent to arch:{dpkg's primary arch}.

Bug#695229: chromium-inspector: should be 'Multi-Arch: foreign' so that chromium:{arch} is installable

2012-12-05 Thread Jonathan Nieder
Daniel Hartwig wrote: On 6 December 2012 15:26, Jonathan Nieder jrnie...@gmail.com wrote: so that dpkg, apt, and aptitude can agree on what to do here? Do they currently disagree? No, I was just confused. Contrary to my expectation, dpkg follows the spec. In my mental model, there is no