Skip to content
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

network 2.8.0.1 & 3.0.1.0 #4427

Closed
2 of 51 tasks
mihaimaruseac opened this issue Mar 17, 2019 · 3 comments
Closed
2 of 51 tasks

network 2.8.0.1 & 3.0.1.0 #4427

mihaimaruseac opened this issue Mar 17, 2019 · 3 comments

Comments

@mihaimaruseac
Copy link
Contributor

mihaimaruseac commented Mar 17, 2019

(opening new issue as list of packages out of bounds changed)

network-3.0.1.0 is out of bounds for:

network-3.0.0.1 (Stackage upper bounds) is out of bounds for:

network-3.0.0.0 (Stackage upper bounds) is out of bounds for:

network-2.8.0.0 (Stackage upper bounds) is out of bounds for:

Replaces #4312.

@rblaze
Copy link
Contributor

rblaze commented Mar 17, 2019 via email

@bergmark
Copy link
Member

There was also a network-2.8.0.1 release:

network-2.8.0.1 (Stackage upper bounds) is out of bounds for:

I will disable lambdabot-core since a revision changed it to not allow network 2.8.x.

@bergmark bergmark changed the title network 3.0.1.0 network 2.8.0.1 & 3.0.1.0 Apr 27, 2019
@bergmark bergmark mentioned this issue Apr 27, 2019
3 tasks
@rblaze
Copy link
Contributor

rblaze commented Apr 28, 2019

dbus-1.2.6 published.

peti referenced this issue in lambdabot/lambdabot Apr 29, 2019
This is a stopgap measure to make TravisCI happy; the proper fix is to
follow the API changes, but that will require updating some dependencies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants