Comment 5 for bug 1185896

Revision history for this message
Steve Langasek (vorlon) wrote :

> Which leads me to wonder if multiarch-support is actually correct in being M-A:foreign.

It is, though the reason isn't altogether obvious. The reason it was made M-A: foreign was to break what was otherwise a dependency loop for adding foreign architectures: libc6 Depends: libgcc1 Pre-Depends: multiarch-support Depends: libc6. Since the whole purpose of multiarch-support was to ensure that libraries for your primary arch were not disappeared out from underneath the linker during the transition to multiarch, we don't care about multiarch-support for any except the primary architecture... you can't possibly install the foreign-arch multiarch-support package *before* transitioning to multiarch, and if you do it *afterwards* it no longer matters.

Indeed, now that the transition is complete (since wheezy has released with multiarch-support), we could update debhelper to no longer add the multiarch-support Pre-Depends in unstable.