Control: clone -1 -2 Control: reassign -2 kmscon 10.0.1-1~bpo13+1 Control: affects -2 = Control: block -1 by -2
Am 16.07.2026 um 12:39 schrieb Helmut Grohne: > Package: ncurses-term > Version: 6.6+20260608-2 > Severity: serious > User: [email protected] > Usertags: fileconflict > Control: affects -1 + kmscon > > ncurses-term has an undeclared file conflict. This may result in an > unpack error from dpkg. > > The file /usr/share/terminfo/k/kmscon is contained in the packages > * kmscon/10.0.1-1~bpo13+1 as present in trixie-backports > * ncurses-term/6.6+20260608-2 as present in forky|unstable > > 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 kmscon package in trixie-backports explicitly depends on ncurses-term (<< 6.6+20260608~) in an attempt to avoid the problem, but you are right that this is not sufficient because the unpack order on upgrades to forky is not defined, so there is a 50% chance to run into the file conflict depending on whether kmscon or ncurses-term is unpacked first. Prior art suggests[1] that moving the file in kmscon/trixie-backports to /usr/lib/terminfo is a good way to avoid the file clash. I will look into this later today if nobody beats me to it. Once the file in kmscon has been moved, I can add suitable Replaces to ncurses-term. Before that it makes little sense as it would either require unversioned Replaces or a diversion, and I consider both of these options evil™. Cheers, Sven 1. https://bugs.debian.org/cgi-bin/911515
