Hi, Bastian disagrees with me that there is a bug here off list.
On Fri, Nov 06, 2026 at 12:05:26PM +0100, Helmut Grohne wrote: > linux-image-6.12.115+deb13.1-riscv64-dbg has an undeclared file > conflict. This may result in an unpack error from dpkg. > > The file > /usr/lib/debug/.build-id/90/772e7b336781d21fcb7f165943e58430842d86.debug > is contained in the packages > * linux-image-6.12.115+deb13-riscv64-dbg/6.12.115-1 as present in > trixie-security > * linux-image-6.12.115+deb13.1-riscv64-dbg/6.12.115-2 as present in > trixie-security > > 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 file. The practical instance of this bug may be unsolvable now. We're not uploading a new package to trixie-security to add Replaces or similar. However, there is a fundamental problem here that resurfaces now and then: Colliding build ids. This is not exactly a new problem. It is even documented at https://docs.kernel.org/kbuild/reproducible-builds.html#debug-info-conflicts. So to me it looks like our CONFIG_BUILD_SALT is not unique enough and this is the problem actually being reported here. Helmut

