-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http-types-0.11 #2976
Comments
I'm a little frustrated that a package that so many people depend on released a major version to fix the capitalization of a joke status code. 😞 aristidb/http-types#68 aristidb/http-types@0.9.1...f5b4b24 |
|
hackernews has been updated to accomodate the teapot fix.
…On Sun, Oct 22, 2017 at 8:43 AM, Dennis Gosnell ***@***.***> wrote:
hailgun has been updated for http-types-0.10 in version 0.4.1.6:
https://bitbucket.org/robertmassaioli/hailgun/pull-
requests/23/remove-upper-version-bound-on-http-types/diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2976 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA1bPBT9Q35ra_-R6BGwTAYCCgdr8-PAks5su2KmgaJpZM4QByRj>
.
--
Cell: 1.630.740.8204
|
Fixed in IPv6DB-0.2.3 |
|
|
|
Aforementioned |
New entry:
|
FYI, there is |
As you upgrade to |
The only real difference is the elimination of the blaze-builder dependency
which has been a redirect to bytestring's Builder for a long time so having
a package work with both 0.10 and 0.11 should not be too difficult.
Dan Burton <[email protected]> schrieb am So., 10. Dez. 2017, 21:58:
… As you upgrade to http-types-0.11, I recommend maintaining compatibility
with http-types-0.10 if possible, since that is probably the version that
will make it into the next LTS series.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2976 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB3-EgdnfIEfFJpga9tVaXkouf14aGqks5s_EXggaJpZM4QByRj>
.
|
I've updated the issue's description to reflect new upper bound issues with http-types 0.11. |
Fix in |
Fix in btw, got error on latest nightly build plan
|
@freizl update to |
Re: the error, you have to update |
I can't tell if everyone was pinged when this was updated for http-types 0.11, here are the current TODOs: http-types-0.11 is out of bounds for:
|
Fixed in |
Please note that we will be moving to http-types-0.11 for nightlies soon, and incompatible packages will be dropped from the build plan until compatibility is restored. |
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
Fixed in http://hackage.haskell.org/package/bloodhound 0.15.0.1 |
Hold the phone. We may not be moving to http-types 0.11 after all, see #3226 for details. |
Per the reasons explained in in #3226 and linked issues, Stackage has chosen not to switch over to http-types 0.11. We will stick with http-types 0.10 on the nightlies until the next release is out (presumably 0.12, hopefully soon?), at which point I'm sure we will be pinging you all again with a reminder to upgrade. |
Superceded by #3232 |
- `text` is already 1.2.3.0 as commercialhaskell/stackage#3147 is resolved AFAICS - `http-types` bound is surprisingly low due: commercialhaskell/stackage#2976
http-types-0.11 is out of bounds for:
The text was updated successfully, but these errors were encountered: