Hi Helmut, Thank you for the bug report! Let me see if I understand the situation correctly:
1. bison (the executable) being marked Multi-Arch: foreign is not inherently broken, since in a cross-build situation we are running the bison binary in the host (instead of the target) architecture. 2. The broken part is bison depending on libbison-dev, which cannot possibly be Multi-Arch: foreign (as it needs to be linked into the binary being built). 3. So the desired end state (for both options) is that bison (the executable binary, whatever its package name) remaining Multi-Arch: foreign but not depending on libbison-dev. Am I understanding this correctly? Chuan-kai
