search

commercialhaskell / stackage

Stable Haskell package sets: vetted consistent packages from Hackage
https://www.stackage.org/
MIT License
531 stars 804 forks source link

network-3.2.0.0 #7381

Closed andreasabel closed 4 months ago

andreasabel commented 7 months ago

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

yaxu commented 7 months ago

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

byorgey commented 7 months ago

haxr fixed via Hackage revision.

kazu-yamamoto commented 7 months ago

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

adetokunbo commented 7 months ago

tmp-proc is fixed via a new release

maksbotan commented 6 months ago

Done with revisions:

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

jgm commented 6 months ago

pandoc 3.2 fixes this.

ysangkok commented 6 months ago

@maksbotan Yes, servant-multipart PR is at

andreasabel commented 6 months ago

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

ysangkok commented 6 months ago

ftp-client fixed in v0.5.1.6

andreasabel commented 6 months ago

After running check again, there is a new failure:

rblaze commented 6 months ago

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 commented 6 months ago

@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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

sendfile has a new release to fix.

ysangkok commented 6 months ago

scotty fixed with revision

ysangkok commented 5 months ago
jappeace commented 5 months ago

keter bumped by release

ysangkok commented 5 months ago
ysangkok commented 5 months ago

streamly fixed

davidsd commented 4 months ago

network-transport-tcp fixed

ysangkok commented 4 months ago
ysangkok commented 4 months ago
ysangkok commented 4 months ago
rkaippully commented 4 months ago
alaendle commented 4 months ago

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.