[Pkg-javascript-devel] how to best handle uglifyjs.terser -> terser migration

[Jonas Smedegaard]

Package node-terser provides binary package uglifyjs.terser containing a 
command-line tool by the same name.

Upstream has dropped that and instead provides command-line tool terser.

This change has been prepared in experimental, with a "Breaks" in place.

Problem is: 45 packages build-depends on uglifyjs.terser :-(

How to most sensibly handle a transition?

I cannot File 45 bugreports requesting packages to change at their own 
pace, because it needs to happen at once.

Any thoughts?


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20210927/6ed55e4c/attachment.sig>