Re: multi-version nodejs-colors for nodejs-cli-table

2015-02-20 Thread T.C. Hollingsworth
On Feb 20, 2015 8:37 AM, Piotr Popieluch piotr1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm reviewing Ralph's nodejs-cli-table [1]. The module depends on nodejs-colors 1.0.3. Fixdep doesn't work as the module uses new features introduced in 1.0.0.

Re: Mixed case module names

2014-11-16 Thread T.C. Hollingsworth
On Nov 16, 2014 3:57 AM, Tom Hughes t...@compton.nu wrote: I'm working on a review (BZ#1086245) for nodejs-jsonstream. Now the interesting thing is that the module it is packaging is actually called JSONStream in the npm registry and there is in fact a separate jsonstream module. The general

Re: SSLv3 disabled in node v0.10.33

2014-11-16 Thread T.C. Hollingsworth
On Nov 11, 2014 12:44 AM, Stephen Gallagher sgall...@redhat.com wrote: On Nov 10, 2014, at 11:19 PM, T.C. Hollingsworth tchollingswo...@gmail.com wrote: Upstream disabled SSLv3 in v0.10.33. I've been putting off dealing with it because I've been very busy, but I already got a request

Re: EPEL7 status

2014-07-29 Thread T.C. Hollingsworth
I've been poking at this when I had time throughout the day and have got mostly everything to build now. I just need a few more packages branched for EPEL7 to finish out the rest. The remaining packages are: jasmine-node → waiting on jasmine branch nodejs-detective → needs nodejs-esutils

Re: nodejs-packagiing improvements

2014-03-30 Thread T.C. Hollingsworth
On Fri, Mar 21, 2014 at 10:59 AM, Jamie Nguyen j...@jamielinux.com wrote: I'm not sure I'd use or promote such a feature. And I don't blame you given I did such a poor job at putting forward my proposal. :-) I'm singing the benefits of the new dependency style without explaining what's so much

Re: Node no longer searching global library?

2014-02-26 Thread T.C. Hollingsworth
On Wed, Feb 26, 2014 at 3:45 PM, Tom Hughes t...@compton.nu wrote: Am I going mad, or is there a bug that means node is no longer searching the global library directory by default? node has never done this in Fedora proper. Whether or not you are going mad depends on whether you used my old

Re: [HEADSUP] npm in EPEL broken due to rel-eng issue

2014-01-03 Thread T.C. Hollingsworth
On Fri, Jan 3, 2014 at 7:35 AM, Troy Dawson tdaw...@redhat.com wrote: Hi T.C. What was the outcome of this. This was a transient buildroot issue which has been resolved. Your issue is different. I just barely noticed that none of my el6 nodejs packages have a Provides: npm(package) The

Re: [HEADSUP] npm in EPEL broken due to rel-eng issue

2014-01-03 Thread T.C. Hollingsworth
On Fri, Jan 3, 2014 at 3:03 PM, Troy Dawson tdaw...@redhat.com wrote: I knew I'd seen it at one point. Thank you very much, and I hope they merge it soon. That also has the ExclusiveArch I'd been looking for. Unfortunately, that ExclusiveArch macro doesn't work on EL6 either because we can't

Re: [HEADSUP] npm in EPEL broken due to rel-eng issue

2014-01-03 Thread T.C. Hollingsworth
On Fri, Jan 3, 2014 at 3:39 PM, T.C. Hollingsworth tchollingswo...@gmail.com wrote: I went ahead and fixed all the packages that were missing npm(foo) provides in EPEL6; I'm just waiting for builds and necessary buildroot overrides to shake out. You weren't the only one missing it BTW, even