Thanks for looking for and reporting these kind of problems! Isn't this report a fall-out after fixing https://bugs.debian.org/1143626 and that everything will be fine as soon as 3.5.6-2 enters testing?
Mutual installability mixing packages from unstable and testing is not supported, right? The 3.5.6-2 version seems to already be in testing, even though the PTS 'news' section doesn't have any entry for testing migration. Alas, package versioning, file conflicts and upgrade issues usually make my head hurt, and I wish there were more tooling around to detect and regression check these issues. I guess what I'm looking for is a recipe to reproduce the file conflict error in some supported environment. Or better: a suggestion how to untangle the situation from where we are now. /Simon Helmut Grohne <[email protected]> writes: > Package: knot > Version: 3.5.6-2 > Severity: serious > User: [email protected] > Usertags: fileconflict > Control: affects -1 + knot-doc > > knot has an undeclared file conflict. This may result in an unpack > error from dpkg. > > The file /usr/share/doc/knot/README.md is contained in the packages > * knot/3.5.6-2 as present in unstable > * knot-doc/3.5.6-1 as present in forky > > 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. > > Kind regards > > Helmut Grohne > >
signature.asc
Description: PGP signature
