Hello community,

here is the log from the commit of package nodejs-child-process-close for 
openSUSE:Factory checked in at 2014-10-24 10:46:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/nodejs-child-process-close (Old)
 and      /work/SRC/openSUSE:Factory/.nodejs-child-process-close.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "nodejs-child-process-close"

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/nodejs-child-process-close/nodejs-child-process-close.changes
    2014-09-23 10:46:05.000000000 +0200
+++ 
/work/SRC/openSUSE:Factory/.nodejs-child-process-close.new/nodejs-child-process-close.changes
       2014-10-24 10:46:11.000000000 +0200
@@ -1,0 +2,5 @@
+Thu Oct  9 15:07:51 UTC 2014 - [email protected]
+
+- use nodejs-packaging for building
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ nodejs-child-process-close.spec ++++++
--- /var/tmp/diff_new_pack.BNh9zz/_old  2014-10-24 10:46:11.000000000 +0200
+++ /var/tmp/diff_new_pack.BNh9zz/_new  2014-10-24 10:46:11.000000000 +0200
@@ -26,11 +26,12 @@
 Group:          Development/Languages/Other
 Url:            https://github.com/piscisaureus/child-process-close
 Source:         
http://registry.npmjs.org/%{base_name}/-/%{base_name}-%{version}.tgz
-BuildRequires:  nodejs
+BuildRequires:  nodejs-packaging
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildArch:      noarch
 ExclusiveArch:  %{ix86} x86_64 %{arm} noarch
-%{?nodejs_requires}
+
+%nodejs_find_provides_and_requires
 
 %description
 This module makes child process objects, (created with spawn, fork, exec or 
execFile) emit the close event in node v0.6 like they do in node v0.8. This 
makes it easier to write code that works correctly on both version of node. 

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to