- bson: updated to version 0.2.0
- cpu: updated to version 0.1.1
- defaults.nix: cosmetic
- iteratee: updated to version 0.8.9.1
- ListLike: updated to version 3.1.5
- mongoDB: updated to version 1.3.0
- packages.nix: cosmetic
- stringsearch: added version 0.3.6.3
- system-fileio: updated to version 0.3.8
- wai-extra: updated to version 1.2.0.5
svn path=/nixpkgs/trunk/; revision=34517
- HTTP: added version 4000.2.3
- RSA: updated to version 1.2.0.0
- RepLib: updated to version 0.5.2.1
- conduit: updated to version 0.4.1.1
- data-accessor: updated to version 0.2.2.2
- deepseq-th: updated to version 0.1.0.3
- explicit-exception: updated to version 0.1.7
- ghc-mod: updated to version 1.10.15
- gitit: updated to version 0.9.0.1
- hakyll: updated to version 3.2.7.2
- hjsmin: updated to version 0.0.16
- http-conduit: updated to version 1.4.1
- iteratee: updated to version 0.8.8.2
- language-javascript: updated to version 0.5.0
- reactive-banana: updated to version 0.5.0.1
- repa: updated to version 3.1.1.1
- rvar: updated to version 0.2.0.1
- semigroups: updated to version 0.8.3
- simple-sendfile: updated to version 0.2.3
- storable-record: updated to version 0.0.2.5
- unbound: updated to version 0.4.0.2
- wxc: added version 0.90.0.2
svn path=/nixpkgs/trunk/; revision=33802
By now, it happened twice that a commit broke GHC and thus all Haskell packages
we have in Nixpkgs. On such an occasion, I receive well in excess of 3000
notification e-mails from Hydra, and then I receive another 3000 e-mails after
the bug has been fixed. Under these circumstances, subscribing to these
notifications makes no sense for me.
svn path=/nixpkgs/trunk/; revision=33392
