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

[Nilesh Patra]

On 27 September 2021 3:48:52 pm IST, Pirate Praveen <praveen at onenetbeyond.org> wrote:
>
>
>On 27 September 2021 5:10:59 am IST, Jonas Smedegaard <dr at jones.dk> wrote:
>>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?
>
>Is all packages maintained by js team? File bugs against packages not maintained by js team and give them a heads up when this be uploaded to unstable.
>
>We can request a transition tracker from release team.

This really should be done. Makes tracking much easier than doing manually 

>If we fix a day for uploading to unstable, more people can join and help with fixing packages. We can coordinate on irc/pad and upload. I can volunteer. If some more join, we can do it in a few days.

I volunteer to help fix and upload packages that will be broken w/ this change. If it can happen on a weekend, that'd be awesome.

Nilesh

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.