It would not be a correct solution to mark libgl1-mesa-glx:all as
M-A: foreign, because if it was, this dependency chain would be
considered to be valid:
steam:i386 -> libgl1-mesa-glx:all -> libgl1:amd64 -> libglx0:amd64 -> libglx-mesa0:amd64
and that is clearly not useful, because the i386 binaries in Steam cannot load an amd64 libGL. The "i386ness" needs to be propagated all the way through the dependency chain.
Control: reopen -1
Control: found -1 17.2.0-1
On Fri, 01 Sep 2017 at 23:08:26 +0100, Simon McVittie wrote:
It would not be a correct solution to mark libgl1-mesa-glx:all as
M-A: foreign, because if it was, this dependency chain would be
considered to be valid:
steam:i386 -> libgl1-mesa-glx:all -> libgl1:amd64 -> libglx0:amd64 -> libglx-mesa0:amd64
and that is clearly not useful, because the i386 binaries in Steam cannot
load an amd64 libGL. The "i386ness" needs to be propagated all the way
through the dependency chain.
Thanks for making libgl1-mesa-glx version 17.2.0-1 Architecture: any. However, it is also Multi-Arch: foreign. As I explained in the quoted text, M-A: foreign is not appropriate in this case, and will break cross-architecture packages like steam and wine. It should be M-A: same.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 238:57:19 |
Calls: | 6,624 |
Files: | 12,172 |
Messages: | 5,319,946 |