- blaze-html: updated to version 0.4.3.4
- gloss: updated to version 1.7.3.1
- hashtables: updated to version 1.0.1.4
- repa: updated to version 3.1.2.1
- skein: updated to version 0.1.0.6
svn path=/nixpkgs/trunk/; revision=33859
- cabal2nix: updated to version 1.31
- gloss: updated to version 1.7.2.1
- repa-algorithms: updated to version 3.1.0.1
- repa-bytestring: deleted obsolete package
- repa-examples: updated to version 3.1.0.1
- repa-io: updated to version 3.1.0.1
- repa: updated to version 3.1.0.1
- semigroups: updated to version 0.8.0.1
svn path=/nixpkgs/trunk/; revision=33659
- MemoTrie: updated to version 0.4.11
- X11: updated to version 1.6.0
- derive: updated to version 2.5.8
- gloss: updated to version 1.7.1.1
- haskell-src-exts: updated to version 1.13.0
- haskell-src-meta: updated to version 0.5.1.2
- hlint: updated to version 1.8.28
svn path=/nixpkgs/trunk/; revision=33528
- blaze-html: updated to version 0.4.3.2
- ghc-mod: updated to version 1.10.12
- gloss: updated to version 1.7.0.1
svn path=/nixpkgs/trunk/; revision=33436
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
- Hipmunk: updated to version 5.2.0.7
- cairo: updated to version 0.12.3
- digest: updated to version 0.0.1.1
- glib: updated to version 0.12.3
- gloss: updated to version 1.6.2.1
- gtk: updated to version 0.12.3
- language-javascript: updated to version 0.4.10
- pango: updated to version 0.12.3
- zeromq-haskell: updated to version 0.8.4
svn path=/nixpkgs/trunk/; revision=32947
I know that GLURaw is currently a modification of the generated file.
Not making the change prevents GLURaw from being loaded into ghci.
svn path=/nixpkgs/trunk/; revision=29290
