Le 18/03/2019 à 06:19, Xavier a écrit : > Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : >> Quoting Jonas Smedegaard (2019-03-17 23:48:57) >>> Quoting Xavier (2019-03-17 23:12:51) >>>> Control: reassign 924807 uglify-js >>>> Control: reassign 924809 uglify-js >>>> Control: merge 924807 924809 >>>> >>>> Bug seems to come from conflict between >>>> https://tracker.debian.org/pkg/uglify-js and >>>> https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed >>>> with uglifyjs >>> >>> Problem is packages depending on uglifyjs and webpack together: webpack >>> depends indirectly on node-uglify 2.x, whereas uglifyjs is either a >>> virtual package provided by node-uglify 2.x or (since recently) a real >>> package depending on node-uglyfy-js 3.x. >>> >>> Yes, the problem emerged when node-uglify was introduced as a real >>> package, but the fix is for those packages depending on uglifyjs and >>> webpack together to depend on node-uglify 2.x instead of the virtual >>> package. >>> >>> Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. >> >> Put differently, the problem is packages depending both unversioned and >> transitively versioned on uglifyjs - that works only as long as the >> transitive dependency happens to be newest major release of uglifyjs. >> >> - Jonas > > List of packages that are affected by this change: > > node-uglify > Build Reverse Depends: > ... > > node-uglify > Reverse Depends: > node-uglifyjs-webpack-plugin > emscripten > python3-webassets > python-webassets > uglifyjs > node-uglify-js > python3-livereload > python-livereload > node-with > node-grunt-contrib-uglify > node-transformers > lava-dev > node-dryice > node-constantinople
If I understand (but maybe I'm wrong), this means that in buster it is not possible to have uglifyjs installed with one of these 14 packages or their dependencies (`apt-cache rdepends --recurse node-uglify` returns several thousands package names).