Bug#733586: closure-compiler: new upstream version available

[Thomas Koch]

Hello,

sorry, I was under the wrong impression that closure-compiler would be abandoned upstream and that it would eventually die of age and be removed.
I packaged closure-compiler as a dependency of the code review system Gerrit which however couldn't be packaged at the time due to GWT.

Whoever does another upload to closure-compiler please also remove me from uploaders.

Thank you!

> tony mancill <tmancill at debian.org> hat am 29.03.2022 07:26 geschrieben:
> 
>  
> Hello Nicholas,
> 
> On Mon, Mar 28, 2022 at 03:27:17PM -0400, Nicholas D Steeves wrote:
> > Control: unblock 886411 by -1
> > 
> > Hi Tony and Thomas,
> > 
> > This package came to my attention via #975505, where it was noted that
> > MathJax2 has had to disable functionality because of too ancient of a
> > closure-compiler, and at this time it appears that MathJax3 will have to
> > do the same.
> > 
> > Closure-compiler is a candidate for salvaging:
> > 
> >   https://wiki.debian.org/PackageSalvaging
> >   https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
> > 
> > The ideal resolution would be for one of the listed Uploaders to resume
> > maintenance of the package, but orphaning is of course also an option :-)
> 
> The closure-compiler package is officially a team-maintained package by
> the Java Team, so you or anyone else who is interested in joining Java
> Team and maintaining the package is welcome to do so.  That is, please
> feel free to add yourself to Uploaders.
> 
> That said, it's more of a JavaScript tool than a Java package, and so
> the package could also be moved to another team if that's preferable.
> 
> I will gladly help with either of those options, or with reviewing and
> sponsoring an upload of a newer version if one is made available.
> 
> Finally, I have never been a user of closure-compiler - my packaging
> work on it has been under the Java Team umbrella - and I have
> (obviously) been unable to devote sufficient time to it.  I will remove
> myself from Uploaders to avoid any future confusion.
> 
> > Pirate Praveen <praveen at debian.org> writes:
> > 
> > > Control: block 886411 by -1
> > >
> > > On Sat, 20 Jan 2018 20:38:02 +0530 Pirate Praveen <praveen at debian.org>
> > > wrote:> Being more familiar with nodejs packaging, I prefer to go back to
> > >> google-closure-compiler-js. But if there is a newer closure-compiler,
> > >> it'd make my work a lot easier.
> > >> 
> > >
> > > Hi Tony,
> > >
> > > Digging deeper, I found out even the javascript version is built using
> > > java sources (using gwt). So I have to update the java sources even for
> > > javascript version.  Hope you are still interested in updating
> > > closure-compiler and we can collaborate.
> > 
> > Hi Pirate!
> > 
> > I noticed that you were able to complete #886411 ITP: node-react using
> > some other method (perhaps google-closure-compiler-js, or perhaps
> > disabling functionality?), so I've unset the block relation.  It seemed
> > worthwhile keep you in the CC list in case you wanted to create a
> > "switch to closure-compiler" bug, and block it with this one (#733586).
> > 
> > 
> > Kind regards,
> > Nicholas
> 
> Cheers,
> tony