72f5821169
add source
2014-11-18 18:26:34 -07:00
ee85520942
new upstream release 0.10.33
...
http://blog.nodejs.org/2014/10/23/node-v0-10-33-stable/
- This release disables SSLv3 to secure Node.js services against the POODLE
attack. (CVE-2014-3566; RHBZ#1152789) For more information or to learn how
to re-enable SSLv3 in order to support legacy clients, please see the upstream
release announcement linked above.
2014-11-18 18:22:09 -07:00
f46f1163b1
add Provides nodejs-punycode (RHBZ#1151811)
2014-10-21 12:13:10 -07:00
d68cb2c1b4
refresh utf8 reversion patch
2014-09-17 21:23:08 -07:00
c9b274dcea
new upstream release 0.10.32
...
http://blog.nodejs.org/2014/08/19/node-v0-10-31-stable/
http://blog.nodejs.org/2014/09/16/node-v0-10-32-stable/
2014-09-17 20:33:19 -07:00
870eb6e416
fix UTF-8 change reversion patch for v0.10.30
2014-07-31 21:56:53 -07:00
ea65a91fc7
Revert "allow UTF-8 change to happen"
...
Can't do this just yet. :-(
This reverts commit b7cebd90d1
2014-07-31 21:53:32 -07:00
b7cebd90d1
allow UTF-8 change to happen
...
http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/
I've looked into this further and I think Debian is being a bit
too pedantic; not worth fighting with this patch every release. ;-)
2014-07-31 17:42:33 -07:00
677c42d6ff
new upstream release 0.10.30
...
http://blog.nodejs.org/2014/07/31/node-v0-10-30-stable/
2014-07-31 17:24:19 -07:00
50877fbc3a
new upstream release 0.10.29
...
http://blog.nodejs.org/2014/06/16/node-v0-10-29-stable/
- The invalid UTF8 fix has been reverted since this breaks v8 API, which cannot
be done in a stable distribution release. This build of nodejs will behave as
if NODE_INVALID_UTF8 was set. For more information on the implications, see:
http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/
2014-06-18 23:36:28 -07:00
7269177e52
fix old changelog entry
2014-05-02 17:51:14 -07:00
a0beb2b8b2
new upstream release 0.10.28
...
There is no dfference between 0.10.27 and 0.10.28 for Fedora, as the only
thing updated was npm, which is shipped seperately. The latest was only
packaged to avoid confusion. Please see the v0.10.27 changelog for relevant
changes in this update:
http://blog.nodejs.org/2014/05/01/node-v0-10-27-stable/
2014-05-02 17:51:03 -07:00
1e46137691
new upstream release 0.10.25
...
http://blog.nodejs.org/2014/02/18/node-v0-10-26-stable/
2014-02-19 20:59:43 -07:00
25d126753c
new upstream release 0.10.25
...
http://blog.nodejs.org/2014/01/23/node-v0-10-25-stable/
2014-01-27 15:30:48 -07:00
7379e62cbb
upstream install script installs the headers now
2013-12-19 11:39:02 -07:00
54cf0adca3
new upstream release 0.10.24
...
http://blog.nodejs.org/2013/12/19/node-v0-10-24-stable/
2013-12-19 11:26:54 -07:00
79b29fceec
new upstream release 0.10.23
...
http://blog.nodejs.org/2013/12/11/node-v0-10-23-stable/
2013-12-12 11:02:53 -07:00
fb183ee57b
refresh gyp bundled dep removal patch
2013-11-12 14:56:28 -07:00
d21c6c8b99
new upstream release 0.10.22
...
http://blog.nodejs.org/2013/11/12/node-v0-10-22-stable/
2013-11-12 14:31:09 -07:00
95269f1759
new upstream release 0.10.21
...
http://blog.nodejs.org/2013/10/18/node-v0-10-21-stable/
- resolves an undisclosed security vulnerability in the http module
2013-10-18 16:12:50 -07:00
ded32609ba
new upstream release 0.10.20
...
http://blog.nodejs.org/2013/09/30/node-v0-10-20-stable/
2013-09-30 17:18:36 -07:00
6f09c657d4
new upstream release 0.10.19
...
http://blog.nodejs.org/2013/09/24/node-v0-10-19-stable/
2013-09-24 17:30:22 -07:00
793585cd7d
new upstream release 0.10.18
...
http://blog.nodejs.org/2013/09/04/node-v0-10-18-stable/
2013-09-06 15:24:49 -07:00
2f74c1f475
new upstream release 0.10.17
...
http://blog.nodejs.org/2013/08/21/node-v0-10-17-stable/
2013-08-27 01:35:24 -07:00
980a4c5439
add v8-devel and %{?_isa} to -devel Requires
2013-08-16 20:17:28 -07:00
b9edecaefd
new upstream release 0.10.16
...
http://blog.nodejs.org/2013/08/16/node-v0-10-16-stable/
2013-08-16 20:15:05 -07:00
e9f69b1411
fix typo in _isa macro in v8 Requires
...
v8.i686 still never got dragged in, thanks to the automatic soname-
based provides, but this makes yum attempt to do some crazy stuff [1]
and crash and burn when spot's conflicting chromium repo is installed.
[1] https://lists.fedoraproject.org/pipermail/users/2013-August/439753.html
2013-08-14 02:07:55 -07:00
a22461bf51
new upstream release 0.10.14
...
http://blog.nodejs.org/2013/07/25/node-v0-10-14-stable/
2013-07-25 14:22:08 -07:00
06ed0ee13f
remove RPM macros, etc. now that they've migrated to nodejs-packaging
2013-07-10 03:03:28 -07:00
c10bc717a2
new upstream release 0.10.13
...
http://blog.nodejs.org/2013/07/09/node-v0-10-13-stable/
2013-07-10 02:56:13 -07:00
b751ee7a54
copy mutiple versioned packages implementation from nodejs-packaging
2013-06-18 20:15:13 -07:00
689af2fd68
build docs as noarch
...
sorry for not noticing this before
2013-06-18 20:15:12 -07:00
d46eff9f81
split off a -packaging subpackage with RPM macros, etc.
...
This way nodejs-packaging can be approved and imported without
forcing a nodejs update at the same time.
2013-06-18 20:15:07 -07:00
62a5b1000e
new upstream release 0.10.12
...
http://blog.nodejs.org/2013/06/18/node-v0-10-12-stable/
2013-06-18 19:49:37 -07:00
30653ec3f2
fill in missing changelog entries
2013-05-30 19:52:24 -07:00
aab18e6056
new upstream release 0.10.9
...
http://blog.nodejs.org/2013/05/30/node-v0-10-9-stable/
2013-05-30 19:51:42 -07:00
f7500b9771
new upstream release 0.10.8
2013-05-28 20:44:29 -07:00
07d9fe983d
add the tarball stripping script
2013-05-28 20:23:27 -07:00
9e89193903
add the new stripped tarball to sources
...
sorry for the extra commit, `fedpkg new-sources` doesn't work with
`git rebase --interactive` :-(
2013-05-28 20:17:30 -07:00
3a54e91338
patch Makefile so we can just remove all bundled deps completely
2013-05-28 20:12:55 -07:00
44e85aef7e
strip openssl from the tarball; it contains prohibited code (RHBZ#967736)
2013-05-28 20:08:10 -07:00
0c69a9595a
new upstream release 0.10.7
2013-05-28 19:55:25 -07:00
7db6e8f74b
new upstream release 0.10.6
...
http://blog.nodejs.org/2013/05/14/node-v0-10-6-stable/
2013-05-15 12:28:06 -07:00
d0c6d3a9e2
nodejs-fixdep: work properly when a package has no dependencies
2013-05-06 14:34:09 -07:00
e0f6b9832c
nodejs-symlink-deps: make it work when --check is used and just
...
devDependencies exist
2013-04-29 04:47:26 -07:00
8075b2b362
new upstream release 0.10.5
...
http://blog.nodejs.org/2013/04/23/node-v0-10-5-stable/
2013-04-24 08:46:51 -07:00
3c3551aba6
add no-op macro to provide spec compatibility with EPEL
2013-04-14 18:21:43 -07:00
727d8ef2fd
new upstream release 0.10.4
...
http://blog.nodejs.org/2013/04/11/node-v0-10-4-stable/
2013-04-14 18:19:38 -07:00
63f157c85c
Remove extra source tarball entries
...
No reason to force packagers to download anything but the one that
the spec file refers to.
2013-04-09 07:44:59 -04:00
f8a8f5bf68
nodejs-symlink-deps: symlink unconditionally in the buildroot
2013-04-03 19:34:39 -07:00
T.C. Hollingsworth
Stephen Gallagher