Quoting Helmut Grohne (2024-12-01 22:02:27) > Package: eye > Version: 1:10.30.11~ds-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > Control: affects -1 + ruby-eye > > eye has an undeclared file conflict. This may result in an unpack error > from dpkg.
Is it not adequate that eye declares a versioned Breaks? > The file /usr/bin/eye is contained in the packages > * eye/1:10.30.11~ds-1 as present in unstable > * ruby-eye > * 0.7-5 as present in bullseye > * 0.7-5.1 as present in bookworm > > 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. How would the collision happen, when ruby-eye does not exist in unstable/testing where eye provides the conflicting file? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
