Hi Andres, Quoting Andres Salomon (2022-01-20 19:46:13) > On Thu, 02 Dec 2021 22:41:48 +0100 Jonas Smedegaard wrote: > > Source package chromium build-depends on uglifyjs.terser which will > > soon be dropped. > > > > Please instead build-depend on package terser, and use the > > executable "terser".
> I'm going to add a build-dep on "terser | uglifyjs.terser", since the > terser package is still only in experimental. That should be unneded: uglifyjs.terser 4.1.2-9 in unstable and testing provides terser as virtual package. > However, I'm concerned about the uglifyjs.terser executable going > away; what is the timeline for that? It would be ideal if the > /usr/bin/uglifyjs.terser symlink remained at least for the bookworm > release, so users don't need a special patch when doing > bullseye-backports. After bookworm, users can switch to > /usr/bin/terser and not need to patch anything for bookworm backports. I agree that a more gentle migration would be nicer. Unfortunately Terser is already dangerously old - v4.1.2 was released in July 2019, v4.8.0 was released in May 2020. Upstream does not provide any support for older releases. Backports will need to carry a small patch. Unfortunately. So to answer your question: uglifyjs.terser will be dropped any day now! Plan is to drop it as soon as verified among the packages that have prepared for the switch, that there are no surprises among them. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
