Bug#1092278: libc6-dev-i386 and libc6-dev-s390 have undeclared file conflicts

[Helmut Grohne <helmut@subdivi.de>]

Package: libc6-dev-i386,libc6-dev-s390
Severity: normal
Justification: undeclared cross architecture file conflict cannot be experienced using apt
User: debian-qa@lists.debian.org
Usertags: fileconflict
User: debian-amd64@lists.debian.org
Usertags: amd64
User: debian-s390@lists.debian.org
Usertags: s390x

Hi Aurelien,

while looking into non-amd64 /usr-move issues, I noticed that
technically speaking libc6-dev-i386 and libc6-dev-s390 have an
undeclared file conflict. Since libc6-dev-s390 depends on libc6-s390 and
that happens to conflict with libc6-i386, you cannot experience this
conflict when using apt. Technically though, you may dpkg --unpack a
libc6-dev-s390 on a system that has libc6-dev-i386 unpacked and doing so
fails.

I suggest that libc6-dev-i386 declares "Conflicts: libc6-dev-s390" to
make this explicit. It can reasonably be mutual. The main benefit of
this change is helping QA tools that diagnose undeclared file conflicts.

Thanks for considering

Helmut