Is there an alternative or workaround for packages which require this fix? There's a potential XSS vulnerability in jquery I'd like to patch... but can't if I can't get a successful build. If the fix cannot be backported to F24, can grunt be downgraded to the last working version in F24?

On Wed, Dec 7, 2016 at 2:36 AM Piotr Popieluch <> wrote:

I had to update a lot of (circular)  dependencies and was worried to break something in the released branches.

Op wo 7 dec. 2016 01:30 schreef Christopher <>:
On Tue, Dec 6, 2016 at 7:21 PM Dan Callaghan <> wrote:
Excerpts from Christopher's message of 2016-12-07 00:08 +00:00:
> Just want to re-ping this list to see if there's any help anybody can offer
> for this FTBFS on F24 for js-jquery and js-jquery1.
> In short, it seems there is a failure with npm uglify task. It seems to
> only affect the f24 branch. f23 and f25, using the same code, seems to
> build perfectly fine.
> This is blocking any progress on fixing/patching/updating both js-jquery1
> and js-jquery in F24.
> Does anybody know what's different in F24 that would affect npm uglyify?

Your error:

    Verifying property uglify.all exists in config...Warning: An error
    occurred while processing a template (tmpl.indexOf is not
    a function). Use --force to continue.

looks suspiciously like this bug:

Yeah, after some investigation. I concur. This is, which was fixed in F25, but not in F24.
I've reopened. Hopefully it can be fixed in F24?
which caused a FTBFS in F24 one of my Nodejs packages as well. There was
no resolution in F24 for... whatever reason.

Dan Callaghan <>
Senior Software Engineer, Products & Technologies Operations
Red Hat
nodejs mailing list --
To unsubscribe send an email to
nodejs mailing list --
To unsubscribe send an email to