Le dim. 12 avr. 2026 à 09:37, Helmut Grohne <[email protected]> a écrit :
> Package: qjs > Version: 0.14.0-1 > Severity: serious > User: [email protected] > Usertags: fileconflict > Control: affects -1 + quickjs > > qjs has an undeclared file conflict. This may result in an unpack error > from dpkg. > > The files > * /usr/bin/qjs > * /usr/bin/qjsc > are contained in the packages > * qjs/0.14.0-1 as present in unstable > * quickjs > * 2025.04.26-1 as present in trixie > * 2025.04.26-1+b1 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 files. > I think not allowing legacy quickjs and quickjs-ng's version of qjs is the behavior we want, so this: --- a/debian/control +++ b/debian/control @@ -16,7 +16,9 @@ Package: qjs Architecture: any Multi-Arch: foreign Depends: ${misc:Depends}, ${shlibs:Depends} -Provides: quickjs-ng +Provides: quickjs +Conflicts: quickjs +Replaces: quickjs Recommends: qjs-doc @Sebastian Humenda <[email protected]> do you think it's ok ? Jérémy
