Re: Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Utkarsh Gupta <guptautkarsh2102@gmail.com>]

Hi Praveen,

On Wed, Jun 1, 2022 at 1:08 PM Pirate Praveen <praveen@onenetbeyond.org> wrote:
> We have a long standing rc bug (we have not updated to
> latest upstream for long)
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981224#10
>
> Also it caused autopkgtest regression for node-source-map update
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-uglifier/22232351/log.gz
>
> terser is better maintained fork of uglify-js and ruby-terser its
> gem equivalent.
>
> Anyone wants to keep maintaining ruby-uglifier ?

$ reverse-depends src:ruby-uglifier
Reverse-Recommends
* nanoc                         (for ruby-uglifier)

Reverse-Depends
* diaspora                      (for ruby-uglifier)
* gitlab                        (for ruby-uglifier)
* obs-api                       (for ruby-uglifier)
* rails                         (for ruby-uglifier)

Packages without architectures listed are reverse-dependencies in:
all, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el,
s390x

$ reverse-depends -b src:ruby-uglifier
Reverse-Build-Depends
* nanoc                         (for ruby-uglifier)
* open-build-service            (for ruby-uglifier)
* rails                         (for ruby-uglifier)
* ruby-sprockets                (for ruby-uglifier)
* ruby-sprockets-rails          (for ruby-uglifier)


As long as nothing breaks here and the transition from ruby-uglifier
to ruby-terser is smooth, it's all good. Whilst at it, you might also
want to open respective upstream issues so that we don't carry this
delta forever.


- u