Orphaning nodejs packages

I've orphaned the following nodejs packages. I do not have time to maintain them any more. nodejs-onetime nodejs-oop nodejs-opn nodejs-pac-proxy-agent nodejs-pac-resolver nodejs-param-case nodejs-parserlib nodejs-pascal-case nodejs-path-case nodejs-path-exists nodejs-pend nodejs-pify

Re: Packaging the Javascript layer of Prometheus & Grafana

On Wed, Aug 29, 2018 at 3:25 PM Nicolas Mailhot wrote: > Hi, > > I'm currently investigating the packaging of Prometheus and Grafana in > Fedora/Epel. > > Grafana OTOH has a clean codebase with a build process that uses yarn to > get third-party javascript >

Orphaning Node.js module packages

I'm orphaning: nodejs-proxy-agent nodejs-superagent-proxy nodejs-grunt-html-validation nodejs-fd-slicer nodejs-test nodejs-agent-base nodejs-colors They FTBFS and I don't have time to fix them and don't use them any more. Piotr ___ nodejs mailing list

Re: native modules in epel7 ftbfs

On Mon, Feb 27, 2017 at 10:08 AM, Tom Hughes <t...@compton.nu> wrote: > On 27/02/17 08:46, Piotr Popieluch wrote: > >> >> >> On Sun, Feb 26, 2017 at 11:40 PM, Tom Hughes <t...@compton.nu >> <mailto:t...@compton.nu>> wrote: >> >> O

Re: native modules in epel7 ftbfs

On Sun, Feb 26, 2017 at 11:40 PM, Tom Hughes <t...@compton.nu> wrote: > On 26/02/17 22:28, Piotr Popieluch wrote: > > Now I cannot get any of the native modules built. It seems they haven't >> been rebuild in years and are broken from at least the last update to 6.x. >>

Re: Updating nodejs-bytes

nodejs-connect and nodejs-compression have broken deps now. My first look at nodejs-connect gives me the impression that it is not trivial to update. Zuzana, do I understand correctly that you are working on updating those packages? Op vr 17 feb. 2017 om 11:03 schreef Tom Hughes

Re: [HELPWANTED] Building jquery for F24 branch

Op wo 7 dec. 2016 om 21:46 schreef Piotr Popieluch <piotr1...@gmail.com>: > Op wo 7 dec. 2016 10:02 schreef Christopher <ctubb...@fedoraproject.org>: > > Is there an alternative or workaround for packages which require this fix? > There's a potential XSS vulnerability in

Re: [HELPWANTED] Building jquery for F24 branch

Op wo 7 dec. 2016 10:02 schreef Christopher : 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

Re: Updating EPEL

On 08/10/2016 11:29 AM, Zuzana Svetlikova wrote: > Hi, > > since nodejs currently present in EPEL is archaic and going EOL in ~7w, > it might be time to finally update it. > If anyone has any comments or suggestions, I'm all ears. > Otherwise I'll start with the update tomorrow or on Friday.

Re: Node.js security update

On Fri, Jun 24, 2016 at 4:23 PM, Stephen Gallagher wrote: > On 06/24/2016 10:21 AM, Zuzana Svetlikova wrote: > > Hi, > > > > the security update was released yesterday, Node.js in f23 and f24 is > updated, > > the version available in Rawhide wasn't affected. > > > >

Re: Builds failing on EPEL7 ppc builders

On 01/12/2016 03:52 PM, Tom Hughes wrote: > On 12/01/16 14:48, Tom Hughes wrote: >> On 12/01/16 14:45, Piotr Popieluch wrote: >> >>> Apparently the ExclusiveArch line is incorrect. The "noarch" shouldn't >>> be there. >>> >>>

Re: pnemade pushed to nodejs-deep-extend (el6). "Specify exclusively arch list as per nodejs packaging guidelines"

On Wed, Jan 13, 2016 at 3:18 PM, Parag Nemade wrote: > Hi Tom, > > On Wed, Jan 13, 2016 at 7:40 PM, Tom Hughes wrote: > > On 13/01/16 13:58, Parag Nemade wrote: > > > >> Yes you are right. The guidelines are not clear. I am not sure if > >> someone removed

Re: sntp

On 12/13/2015 06:12 PM, Tom Hughes wrote: > So we have a load more broken dependencies because sntp 2.x has been > pushed in rawhide but it requires nodejs 4.x. > > It seems it really does require 4.x as it uses various "harmony" > features, some of which don't even work under node 0.10 even with

Re: Thoughts on a NodeJS packaging group

I think we forgot about asking Ralph Bean... :( @Ralph, would you like to join the nodejs-sig and would you like to give acl access to group::nodejs-sig for your existing nodejs package? Piotr On 11/13/2015 07:44 PM, Jared K. Smith wrote: > > On Wed, Nov 11, 2015 at 5:23 PM, Jared K. Smith >