Commit graph

187 commits

Author SHA1 Message Date
Stephen Gallagher
f2c3b615ec Upgrade to Node.js 4.2.2 (LTS) 2015-12-01 19:48:58 -05:00
T.C. Hollingsworth
de20ac7b30 new upstream release 0.10.36
http://blog.nodejs.org/2015/01/26/node-v0-10-36-stable/
- Please note that several upstream releases were skipped due to regressions
  reported in the upstream bug tracker.  Please also review the 0.10.34 and
  0.10.35 changelogs available at the above URL for a list of all changes.
2015-02-19 01:02:09 -07:00
T.C. Hollingsworth
72f5821169 add source 2014-11-18 18:26:34 -07:00
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
f7500b9771 new upstream release 0.10.8 2013-05-28 20:44:29 -07:00
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
T.C. Hollingsworth
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
Stephen Gallagher
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
T.C. Hollingsworth
ab6e60ba98 new upstream release 0.10.3
http://blog.nodejs.org/2013/04/03/node-v0-10-3-stable/
2013-04-03 12:40:15 -07:00
T.C. Hollingsworth
b57b5fed59 new upstream release 0.10.2
http://blog.nodejs.org/2013/03/28/node-v0-10-2-stable/
2013-03-31 16:46:53 -07:00
T.C. Hollingsworth
321c2077f0 new upstream release 0.10.1
http://blog.nodejs.org/2013/03/21/node-v0-10-1-stable/
2013-03-21 18:12:03 -07:00
Stephen Gallagher
1d4119d71f Update sources 2013-03-11 16:33:59 -04:00
T.C. Hollingsworth
db8a0a99d8 fix minor bugs in RPM magic 2013-01-01 17:46:31 -07:00
T.C. Hollingsworth
be1b4d9305 new upstream release 0.9.5 2013-01-01 17:46:18 -07:00
T.C. Hollingsworth
1407a24b65 new upstream release 0.9.4
- system library patches are now upstream
- respect optflags
- include documentation in subpackage
2012-12-26 19:57:50 -07:00
Stephen Gallagher
cdb693ef29 Initial import (#815018). 2012-12-18 08:51:29 -05:00
Fedora Release Engineering
91fc113fe8 Initial setup of the repo 2012-12-18 13:40:14 +00:00