- BNFC-meta: updated to version 0.3.0.3
- HUnit: added version 1.2.4.3
- multirec: updated to version 0.7.2
- resourcet: updated to version 0.3.2.2
svn path=/nixpkgs/trunk/; revision=34489
- clientsession: updated to version 0.7.5
- gloss: updated to version 1.7.4.1
- haskeline: enable terminfo support and patch to support mtl >= 2.1
- HaskellForMaths: updated to version 0.4.5
- HsOpenSSL: updated to version 0.10.3.1
- language-javascript: updated to version 0.5.3
- mtl: added version 2.1.1
- network: updated to version 2.3.0.13
- repa-algorithms: updated to version 3.1.3.1
- repa-examples: updated to version 3.1.3.1
- repa-io: updated to version 3.1.3.1
- repa: updated to version 3.1.3.2
- resourcet: updated to version 0.3.2.1
- RSA: updated to version 1.2.1.0
- yesod-auth: updated to version 1.0.2
- yesod-form: updated to version 1.0.0.3
- yesod: updated to version 1.0.1.3
- zlib-enum: updated to version 0.2.2
svn path=/nixpkgs/trunk/; revision=33913
- blaze-html: updated to version 0.4.3.3
- failure: updated 0.2.0.1
- resourcet: updated to version 0.3.2
- zlib-bindings: updated to version 0.1.0.1
svn path=/nixpkgs/trunk/; revision=33469
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
- cautious-file: updated to version 1.0.1
- hmatrix: updated to version 0.14.0.1
- random-fu: updated to version 0.2.2.0
- resourcet: added version 0.3.0
- sendfile: updated to version 0.7.6
- test-framework: added version 0.6
svn path=/nixpkgs/trunk/; revision=33354
