- alternative-io: updated to version 0.0.1
- blaze-markup: added version 0.5.1.0
- crypto-conduit: updated to version 0.3.2
- cryptohash: updated to version 0.7.5
- darcs: updated to version 2.8.0
- filestore: updated to version 0.4.2
- Graphalyze: cosmetic change
- hamlet: updated to version 1.0.1.1
- happstack-hamlet: updated to version 7.0.1
- happstack-server: updated to version 7.0.1
- HFuse: updated to version 0.2.4.1
- Hipmunk: updated to version 5.2.0.8
- language-javascript: updated to version 0.5.2
- libmpd: updated to version 0.8.0
- lifted-base: updated to version 0.1.0.4
- monad-control: updated to version 0.3.1.2
- persistent: updated to version 0.9.0.3
- regex-compat: use latest version when building with GHC 7.4.1
- skein: updated to version 0.1.0.7
- snap-core: updated to version 0.8.1
- snap-server: updated to version 0.8.1.1
- tls: updated to version 0.9.5
- vty: updated to version 4.7.0.12
- wai-app-static: updated to version 1.2.0.2
- yesod-core: updated to version 1.0.1.1
svn path=/nixpkgs/trunk/; revision=33889
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
haskell-attoparsec-conduit: added version 0.0.0
haskell-blaze-builder-conduit: added version 0.0.0
haskell-conduit: added version 0.0.0.1
haskell-http-conduit: added version 1.0.0
haskell-lifted-base: added version 0.1.0.2
haskell-xml-conduit: added version 0.5.0
haskell-zlib-conduit: added version 0.0.0
svn path=/nixpkgs/trunk/; revision=31141
