--allow-newer seems to be broken

[duog]

I've been hacking on this a bit, and I noticed that the --allow-newer flag in PerformBuild doesn't seem to work due to haskell/cabal#4719.

[snoyberg]

I didn't even remember we had an --allow-newer flag. Because Stackage enforces bounds, we can't use this for the official builds. I'm not sure what your use case is or how you're trying to use stackage-curator.

[duog]

I've been using stackage curator to benchmark some work ghc.
I hacked some instrumentation in, and I use it to run stackage build plans with different builds of ghc. It even builds tests + benchmarks!
Just letting you know it was broken in case it bites someone else.

[snoyberg]

Very cool!

I'm not sure what the best workaround for this is, but if you're interested in it, a workaround is editing the .cabal files to strip out all of the bounds information after unpacking.

[duog]

I have been patching all the configure-args adding --allow-newer --allow-older, seems to work.

[snoyberg]

Oh, cool. I don't see a downside to including that if you want to send a PR.

…

On Mon, Aug 28, 2017 at 10:18 AM, Doug Wilson ***@***.***> wrote: I have been patching all the configure-args adding --allow-newer --allow-older, seems to work. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBByWEwpHFYTVwR_s2xTPu6CqvvA9dks5scmm3gaJpZM4PD6Wq> .

[duog]

I will at some point. I've also got support for Cabal 2, which was quite a few changes, which I'll also send you.

[duog]

This is messy. --allow-newer and --allow-older were removed for Setup in
haskell/cabal@a95b8f4

But serialization of GenericPackageDescription was fixed in
haskell/cabal@c72fd0e

So this could be fixed with some messy logic conditional on the Cabal version, but it's probably not worth the hassle if no-one is using it.