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

Hello Thomas and Tony, CCing Javascript team (JS Team, please see below for why), and fixing threading, since top-posting is confusing. Reply follows inline: Thomas Koch writes: >> tony mancill hat am 29.03.2022 07:26 geschrieben: >> > On Mon, Mar 28, 2022 at 03:27:17PM -0400, Nicholas D

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

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.

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

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 >

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

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

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

Control: block 886411 by -1 On Sat, 20 Jan 2018 20:38:02 +0530 Pirate Praveen 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,

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

On Thu, 29 Dec 2016 08:36:00 -0800 tony mancill wrote:> So, in summary, I haven't been much progress on an new version (despite > a number of failed starts). I'm happy to work together with someone, > or to help with sponsoring and/or reviewing. I'm packaging reactjs and it

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

On Wed, Dec 28, 2016 at 10:33:06PM +0100, Sascha Steinbiss wrote: Hello Sascha and other interested parties: > Hi Tony, > > On Wed, 04 Nov 2015 22:49:23 -0800 tony mancill wrote: > > On 2015-11-04 14:21, Christoph Biedl wrote: > > > Source: closure-compiler > > > Version:

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

Hi Tony, On Wed, 04 Nov 2015 22:49:23 -0800 tony mancill wrote: > On 2015-11-04 14:21, Christoph Biedl wrote: > > Source: closure-compiler > > Version: 20130227+dfsg1-8 > > Followup-For: Bug #733586 > > > > Gentle ping? The latest upstream release is 20151015 as far as I

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

Source: closure-compiler Version: 20130227+dfsg1-8 Followup-For: Bug #733586 Gentle ping? The latest upstream release is 20151015 as far as I can see. There have been some changes so the present Debianisation cannot simply be forwarded. My skills in Java packaging are however somewhat limited.

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

On 2015-11-04 14:21, Christoph Biedl wrote: Source: closure-compiler Version: 20130227+dfsg1-8 Followup-For: Bug #733586 Gentle ping? The latest upstream release is 20151015 as far as I can see. There have been some changes so the present Debianisation cannot simply be forwarded. My skills in

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

Source: closure-compiler Severity: wishlist Dear Java Team, Please consider updating closure-compiler to a newer upstream version. The most recent tagged release is v20131118. Thank you, tony (filing a reminder bug) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with