Karsten Merker <mer...@debian.org> (2015-03-30): > I have run some further tests in the meantime. Those have shown > that the effect happens on my local armhf build box when I build > "by hand", but not when I use pbuilder. > > The significant difference between both is that I have arch:all > packages built by the syslinux source package (isolinux and > syslinux-common) installed on my system, but not in the chroot > used by pbuilder. If I uninstall those arch:all packages, the > effect does not occur anymore. This means that building on a > buildd will probably be safe for now, but if one architecture > should in the future add a built-using for an arch-specific > package, whose source also builds some arch:all package that is a > build-dependency of the installer on another platform, the > problem would probably crop up on the buildds as well. With the > current setup, I think the chance that this will actually happen > in the forseeable future is rather low, but it would of course be > better to find a "proper" solution for the issue.
OK, thanks for the extra checks. Keeping this bug report open at important severity and bumping it to serious whenever it becomes a practical issue looks like a reasonable thing to do, so let's do that. Mraw, KiBi.
signature.asc
Description: Digital signature
