One known blocker for upgrading terser is that the executable has changed name. I should have adjusted all packages in the Javascript team and filed bugreports against packages outside the team, and now in theory all packages should succesfully build with terser v4.8 available in experimental.
Next step in upgrading terser to v4.8 is to test if that theory holds true. I have not found time for testing that for some time, and also don't have the experience in that task so I guess others in the team are more efficient in doing it than me. So consider this an invitation to help modernizing terser package: 1. Test-build all reverse-build-dependencies of terser in a build environment with experimental terser 4.8.0-1 installed 2a. if many builds fail, report that to 988...@bugs.debian.org 2b. if few builds fail, file bugreport against those packages 3. report summary of tests made to 988...@bugs.debian.org Thanks for considering! - Jonas P.S. If noone else does this, I will do it myself at some point, just not sure when... -- * 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