The breakage is caused due to the upper bound on exceptions being removed between 1.2.0.1 and 1.2.0.2, which of course caused a breakage when one of the dependencies (i.e. exceptions) had a major release. Don't remove upper bounds, it breaks code.

Note that even if we release 1.2.0.3 with re-added upper bounds, it won't fix the issue as cabal will still happily use 1.2.0.2 if the dependency planner deems it's an acceptable version.


On Wed, May 7, 2014 at 2:35 PM, Roman Cheplyaka <roma@ro-che.info> wrote:
No. In my opinion, there's no good reason why a package should remain broken for
more than a day, given that there are people who has found, reported, and fixed
the issue. All the actual work is done, now someone just has to push a button.

* Oliver Charles <ollie@ocharles.org.uk> [2014-05-07 13:29:40+0100]
> Isn't a 4 day turn around on a pull request a little hasty?
>
> - ocharles
>
>
> On Wed, May 7, 2014 at 8:50 AM, Roman Cheplyaka <roma@ro-che.info> wrote:
>
> > Hi Max,
> >
> > are you still maintaining the 'temporary' package?
> > There's a breakage waiting to be fixed (with a patch):
> > https://github.com/batterseapower/temporary/pull/12
> >
> > If I don't hear from you in two days, I'll request maintainership and/or
> > fork the package.
> >
> > Roman
> >
> > _______________________________________________
> > Libraries mailing list
> > Libraries@haskell.org
> > http://www.haskell.org/mailman/listinfo/libraries
> >
> >

_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://www.haskell.org/mailman/listinfo/libraries