I think that would be ok. But I'd like to get the version number of the 1.22 branch bumped and update the Cabal submodule in GHC so I can run more tests as early as possible and perhaps avoid more embarassing bugs like this.
Would it be ok if I bumped the 1.22 branch (to 1.22.3.0 ?). Then when you roll the release we can just update the submodule again. luite On Wed, Apr 15, 2015 at 3:18 PM, Ryan Thomas <r...@ryant.org> wrote: > Hey Luite, > > I can do one but unfortunately I'm in Vietnam without any of my keys until > Sunday. If it can wait until then I would be happy to do it when I return > home. > > Cheers, > > Ryan > > > On Wednesday, 15 April 2015, Luite Stegeman <stege...@gmail.com> wrote: > >> Hi all, >> >> Unfortunately GHC 7.10.1 shipped with a Cabal library that handles >> ghcjs-pkg version numbers wrong, making it unusable to boot GHCJS. >> >> I'd like 7.10.2 to ship with a working version (7.10.2 itself also >> contains an important bugfix for GHCJS), which would require a new minor >> version release. Can we do one soon? Let me know if I can do anything to >> help! >> >> luite >> >>
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel