Package: 
libwinpr2-2t64,libfreerdp-server2-2t64,libfreerdp2-2t64,libuwac0-0t64,libfreerdp-client2-2t64,libfreerdp-shadow-subsystem2-2t64,libfreerdp-shadow2-2t64,libwinpr-tools2-2t64
Version: 2.11.2+dfsg1-1.1~exp1
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + libfreerdp-client2-2 libfreerdp-server2-2 
libfreerdp-shadow-subsystem2-2 libfreerdp-shadow2-2 libfreerdp2-2 libuwac0-0 
libwinpr-tools2-2 libwinpr2-2
X-Debbugs-Cc: [email protected], Lukas Märdian <[email protected]>

8 packages from freerdp2 have an undeclared file conflict. This may
result in an unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2 is contained
in the packages
 * libfreerdp-client2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libfreerdp-client2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2
 * /usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.11.2
are contained in the packages
 * libfreerdp-client2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libfreerdp-client2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libfreerdp-server2.so.2 is contained
in the packages
 * libfreerdp-server2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libfreerdp-server2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libfreerdp-server2.so.2
 * /usr/lib/x86_64-linux-gnu/libfreerdp-server2.so.2.11.2
are contained in the packages
 * libfreerdp-server2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libfreerdp-server2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libfreerdp-shadow-subsystem2.so.2 is
contained in the packages
 * libfreerdp-shadow-subsystem2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libfreerdp-shadow-subsystem2-2t64/2.11.2+dfsg1-1.1~exp1 as present in 
experimental

The files
 * /usr/lib/x86_64-linux-gnu/libfreerdp-shadow-subsystem2.so.2
 * /usr/lib/x86_64-linux-gnu/libfreerdp-shadow-subsystem2.so.2.11.2
are contained in the packages
 * libfreerdp-shadow-subsystem2-2/2.11.2+dfsg1-1+b1 as present in 
trixie|unstable
 * libfreerdp-shadow-subsystem2-2t64/2.11.2+dfsg1-1.1~exp1 as present in 
experimental

The file /usr/lib/x86_64-linux-gnu/libfreerdp-shadow2.so.2 is contained
in the packages
 * libfreerdp-shadow2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libfreerdp-shadow2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libfreerdp-shadow2.so.2
 * /usr/lib/x86_64-linux-gnu/libfreerdp-shadow2.so.2.11.2
are contained in the packages
 * libfreerdp-shadow2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libfreerdp-shadow2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2 is contained in the
packages
 * libfreerdp2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libfreerdp2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2
 * /usr/lib/x86_64-linux-gnu/libfreerdp2.so.2.11.2
are contained in the packages
 * libfreerdp2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libfreerdp2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libuwac0.so.0 is contained in the
packages
 * libuwac0-0
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libuwac0-0t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libuwac0.so.0
 * /usr/lib/x86_64-linux-gnu/libuwac0.so.0.2.0
are contained in the packages
 * libuwac0-0/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libuwac0-0t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libwinpr-tools2.so.2 is contained in
the packages
 * libwinpr-tools2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libwinpr-tools2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libwinpr-tools2.so.2
 * /usr/lib/x86_64-linux-gnu/libwinpr-tools2.so.2.11.2
are contained in the packages
 * libwinpr-tools2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libwinpr-tools2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The file /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 is contained in the
packages
 * libwinpr2-2
   * 2.10.0+dfsg1-1 as present in bookworm
   * 2.10.0+dfsg1-1~bpo11+1 as present in bullseye-backports
   * 2.3.0+dfsg1-2+deb11u1 as present in bullseye
 * libwinpr2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

The files
 * /usr/lib/x86_64-linux-gnu/libwinpr2.so.2
 * /usr/lib/x86_64-linux-gnu/libwinpr2.so.2.11.2
are contained in the packages
 * libwinpr2-2/2.11.2+dfsg1-1+b1 as present in trixie|unstable
 * libwinpr2-2t64/2.11.2+dfsg1-1.1~exp1 as present in experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
[email protected] for assistance.

Reply via email to