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

[9.10] filepath-1.5 #7550

Open
9 of 33 tasks
juhp opened this issue Oct 26, 2024 · 9 comments
Open
9 of 33 tasks

[9.10] filepath-1.5 #7550

juhp opened this issue Oct 26, 2024 · 9 comments
Labels

Comments

@juhp
Copy link
Contributor

juhp commented Oct 26, 2024

filepath-1.5.2.0 (changelog) is out of bounds for:

@juhp juhp added the ghc-9.10 label Oct 26, 2024
@hasufell
Copy link
Contributor

file-io-0.1.4 (>=1.4.100.0 && < 1.5.0.0). Julian Ospald [email protected] @hasufell. Used by: library

This is not the case.

  if flag(os-string)
    build-depends: filepath >= 1.5.0.0, os-string >= 2.0.0
  else
    build-depends: filepath >= 1.4.100.0 && < 1.5.0.0

@sergv
Copy link
Contributor

sergv commented Oct 27, 2024

directory-ospath-streaming-0.1.0.2 (>=1.4.100 && < 1.5). Sergey Vinokurov [email protected] @sergv. Used by: library

There's logic in cabal to work with both versions

common depends-on-filepath
  if flag(os-string)
    build-depends:
      , filepath >= 1.5
      , os-string >= 2.0
  else
    build-depends:
      , filepath >= 1.4.100 && < 1.5

@andreasabel
Copy link
Contributor

2024-10-27T09:08:54Z AndreasAbel resolv-0.2.0.2-r4

@mrkkrp
Copy link
Contributor

mrkkrp commented Oct 28, 2024

Fixed via revisions:

  • flac
  • lame
  • ormolu
  • stache
  • zip

@brandonchinn178
Copy link
Contributor

@juhp Fourmolu is pinned to < 0.16 because of #7449. Can we unpin fourmolu to resolve this and the other GHC 9.10 tickets?

@bartavelle
Copy link
Contributor

revised filecache

@juhp
Copy link
Contributor Author

juhp commented Oct 30, 2024

Fourmolu is pinned to < 0.16 because of #7449. Can we unpin fourmolu to resolve this and the other GHC 9.10 tickets?

@brandonchinn178 yep it will happen when we actually switch over to ghc-9.10: we will drop most of the current Stackage upperbounds completely.
The "tooling" or rather output quoted here doesn't take current Stackage upperbounds into account, so you don't have to worry.

Everyone: if you believe the latest version of your package already supports 9.10 - no action is needed of course.

@L0neGamer
Copy link
Contributor

L0neGamer commented Oct 31, 2024

ekg updated to use filepath <1.6

@hasufell
Copy link
Contributor

hasufell commented Nov 6, 2024

I'm a bit embarrassed that I have to rely on stackage maintainers to do this excellent work for free.

Maybe core library maintainers need to get more involved in such mass upgrades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants