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-3.2.0.0 #7381

Closed
40 of 44 tasks
andreasabel opened this issue Apr 15, 2024 · 27 comments
Closed
40 of 44 tasks

network-3.2.0.0 #7381

andreasabel opened this issue Apr 15, 2024 · 27 comments

Comments

@andreasabel
Copy link
Contributor

andreasabel commented Apr 15, 2024

network-3.2.0.0 (changelog) (Grandfathered dependencies) is out of bounds for:

andreasabel added a commit to andreasabel/stackage that referenced this issue Apr 15, 2024
@yaxu
Copy link
Contributor

yaxu commented Apr 15, 2024

fixed for tidal-1.9.5 https://hackage.haskell.org/package/tidal-1.9.5

@byorgey
Copy link
Contributor

byorgey commented Apr 16, 2024

haxr fixed via Hackage revision.

@kazu-yamamoto
Copy link

Please use the latest http2 which is free from this issue.

@adetokunbo
Copy link
Contributor

tmp-proc is fixed via a new release

@maksbotan
Copy link
Contributor

Done with revisions:

  • servant-server
  • servant-http-streams
  • servant-client

@tchoutri @ysangkok please make PRs for servant-multipart and ping me.

@jgm
Copy link
Contributor

jgm commented May 16, 2024

pandoc 3.2 fixes this.

@ysangkok
Copy link
Contributor

@maksbotan Yes, servant-multipart PR is at

@andreasabel
Copy link
Contributor Author

Fixed acid-state by revision: https://hackage.haskell.org/package/acid-state-0.16.1.3/revisions/

@ysangkok
Copy link
Contributor

ftp-client fixed in v0.5.1.6

@andreasabel
Copy link
Contributor Author

After running check again, there is a new failure:

  • dbus-1.3.3 (>=3.1.2.1 && < 3.2). Andrey Sverdlichenko blaze@ruddy.ru @rblaze, Stackage upper bounds. Used by: library

@rblaze
Copy link
Contributor

rblaze commented May 23, 2024

After running check again, there is a new failure:

* [ ]  dbus-1.3.3 (>=3.1.2.1 && < 3.2). Andrey Sverdlichenko [blaze@ruddy.ru](mailto:blaze@ruddy.ru) @rblaze, Stackage upper bounds. Used by: library

dbus-1.3.5 was uploaded on May 6th, why 1.3.3 is used instead?

@ysangkok
Copy link
Contributor

@rblaze It's because versions above 1.3.3 require network-3.2 and higher, which Stackage doesn't have, because not enough packages have been made compatible.

@rblaze
Copy link
Contributor

rblaze commented May 23, 2024

I don't understand the failure :( Either the new stackage snapshot will include 3.2.0.0, and all other packages have to be updated, or the snapshot will include 3.1.x.x, and using 1.3.3 is okay.

Is any action required on my side?

@alaendle
Copy link
Member

So to summarize - everything is alright for dbus (@andreasabel, @rblaze, @ysangkok). I just rechecked - and the list in the first comment is up-to-date - still 21 packages need to adopt.

@alaendle
Copy link
Member

I don't understand the failure :( Either the new stackage snapshot will include 3.2.0.0, and all other packages have to be updated, or the snapshot will include 3.1.x.x, and using 1.3.3 is okay.

Is any action required on my side?

No need for any action on your side.

@telser
Copy link
Contributor

telser commented May 23, 2024

sendfile has a new release to fix.

@ysangkok
Copy link
Contributor

scotty fixed with revision

@ysangkok
Copy link
Contributor

  • hsOpenSSL fixed
  • happstack fixed in 7.9.1.1

@jappeace
Copy link
Contributor

keter bumped by release

@ysangkok
Copy link
Contributor

  • network-bsd fixed with revision
  • happstack-server fixed with reivison

@ysangkok
Copy link
Contributor

streamly fixed

@davidsd
Copy link
Contributor

davidsd commented Jul 9, 2024

network-transport-tcp fixed

@ysangkok
Copy link
Contributor

ysangkok commented Jul 9, 2024

@ysangkok
Copy link
Contributor

  • systemd fixed in release
  • influxdb fixed in release

@ysangkok
Copy link
Contributor

  • swagger2 fixed in v2.8.9

@rkaippully
Copy link
Contributor

@alaendle
Copy link
Member

Since this issue was rather old I decided to allow the newer network version - effectively disabling four remaining packages - as soon as a compatible revision/release of these package appear on hackage they would get re-enabled (semi-)automatically.

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