Bug#1101910: libwinpr3-dev fails to coinstall overwriting itself

[Michael Tokarev <mjt@tls.msk.ru>]

Control: found -1 3.3.0+dfsg1-1

On Wed, 2 Apr 2025 08:26:18 +0200 Helmut Grohne <helmut@subdivi.de> wrote:
> Package: libwinpr3-dev
> Version: 3.14.1+dfsg-2
> Severity: serious
> User: debian-qa@lists.debian.org
> Usertags: fileconflict
>
> libwinpr3-dev explicitly declares its ability to coinstall.
> Unfortunately, that doesn't work as well as advertised:
>
> mmdebstrap --variant=essential --verbose unstable /dev/null --architecture=amd64,i386 --include=libwinpr3-dev,libwinpr3-dev:i386
>
> Unpacking libwinpr3-dev:i386 (3.14.1+dfsg-2) ...
> dpkg: error processing archive /tmp/apt-dpkg-install-agqSM1/31-libwinpr3-dev_3.14.1+dfsg-2_i386.deb (--unpack):
>  trying to overwrite shared '/usr/include/winpr3/winpr/buildflags.h', which is different from other instances of package libwinpr3-dev:i386
> Errors were encountered while processing:
>  /tmp/apt-dpkg-install-agqSM1/31-libwinpr3-dev_3.14.1+dfsg-2_i386.deb
> E: Sub-process env returned an error code (1)
>
> I'm not sure there is much of a use case of coinstalling these and in
> particular given the freeze timing, I recommend just removing
> "Multi-Arch: same" from the binary package as a stop gap measure rather
> than trying to figure out what those differences really are or how they
> could be moved to multiarch locations.
heh.  It's been this way since pre-historic times.  See also #874222.

I don't have other pending changes for this package.  Can we downgrade
this bug report to non-RC?

/mjt