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

Release checklist for GHC 9.6 #8571

Closed
bgamari opened this issue Nov 3, 2022 · 14 comments
Closed

Release checklist for GHC 9.6 #8571

bgamari opened this issue Nov 3, 2022 · 14 comments

Comments

@bgamari
Copy link
Contributor

bgamari commented Nov 3, 2022

Describe the bug
Here we will track the status of the Cabal release which will ship will GHC 9.6.

@Mikolaj Mikolaj added the release label Nov 7, 2022
@Mikolaj
Copy link
Member

Mikolaj commented Nov 7, 2022

A couple of things for the list:

  • collect any new GHC extensions we'd need to add to Cabal; set a date when the list is finalized so that we can implement it
  • add 9.6 to the list of known GHC versions; for this to be serious, CI should run with 9.6; it recently started running with 9.4 but some work remains (update of changelog.d, now maintained by @fgaz , and some doctest woes with 9.4)

@coot
Copy link
Collaborator

coot commented Nov 9, 2022

@bgamari @Kleidukos this doesn't fit here (as it's not just cabal); for the cabal haddock-project command, we also need haddock-2.26.1 to be released.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 12, 2023

Ben says no more extensions are needed this time. This tests it and currently passes: https://gitlab.haskell.org/ghc/ghc/-/blob/master/testsuite/tests/driver/T4437.hs

@Mikolaj
Copy link
Member

Mikolaj commented Jan 14, 2023

now that GHC 9.6.1-alpha1 is out, it would be great to add it to CI but, alas, this requires some extra work (at least a switch to ghcup in CI): #8675

@Mikolaj
Copy link
Member

Mikolaj commented Jan 23, 2023

The 3.10 branch is cut: https://github.com/haskell/cabal/tree/first-cut-of-3.10

With a lot of luck, the Cabal-syntax and Cabal packages contained therein will be included in the official 3.10 release unchanged, except for the version numbers, copyrights and similar release busywork.

A binary for dogfooding:

ghcup --no-cache install cabal -u 'https://gitlab.haskell.org/haskell/cabal/-/jobs/1317949/artifacts/raw/out/cabal-install-3.9-x86_64-linux-alpine.tar.xz' first-cut-of-3.10

@jneira
Copy link
Member

jneira commented Jan 23, 2023

congrats to all cabal maintainers and contributors, great work!
The equivakent for windows would be ghcup --no-cache install cabal -u https://gitlab.haskell.org/haskell/cabal/-/jobs/1317954/artifacts/raw/out/cabal-install-3.9-x86_64-windows.zip first-cut-of-3.10?

EDIT: it worked for me, i guess it is correct cause is from last pipeline

@Bodigrim
Copy link
Collaborator

Bodigrim commented Jan 23, 2023

The equivalent for macOS M2 is ghcup --no-cache install cabal -u 'https://gitlab.haskell.org/haskell/cabal/-/jobs/1317953/artifacts/raw/out/cabal-install-3.9-aarch64-darwin.tar.xz' first-cut-of-3.10.

The new Cabal warns me on every new dependency that

Warning: Error verifying fetched tarball
/Users/andrew/.cabal/packages/hackage.haskell.org/active/0.2.0.16/active-0.2.0.16.tar.gz,
will redownload:
/Users/andrew/.cabal/packages/hackage.haskell.org/01-index.tar: withFile: does
not exist (No such file or directory)

How can I disable this noise? I don't understand the warning: /Users/andrew/.cabal/packages/hackage.haskell.org/01-index.tar is certainly there.

@jneira
Copy link
Member

jneira commented Jan 23, 2023

i also have seen those warnings building cabal itself:

D:\cabal\packages\hackage.haskell.org\data-array-byte\0.1.0.1\data-array-byte-0.1.0.1.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\hashable\1.4.2.0\hashable-1.4.2.0.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\haskell-lexer\1.1.1\haskell-lexer-1.1.1.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\microstache\1.0.2.3\microstache-1.0.2.3.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\network-uri\2.6.4.2\network-uri-2.6.4.2.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\parsec\3.1.16.1\parsec-3.1.16.1.tar.gz,
will redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile:
does not exist (El sistema no puede encontrar la ruta especificada.)
Warning: Error verifying fetched tarball
D:\cabal\packages\hackage.haskell.org\tasty\1.4.3\tasty-1.4.3.tar.gz, will
redownload: D:\cabal\packages\hackage.haskell.org\01-index.tar: withFile: does
not exist (El sistema no puede encontrar la ruta especificada.)

@Mikolaj
Copy link
Member

Mikolaj commented Jan 23, 2023

That's strange. I'm not getting these warnings. Maybe something changed in the hackage-security packages or similar. Could you please file an issue? Does it persist after cabal update? After cabal clean? After moving away ~.cabal?

@Bodigrim
Copy link
Collaborator

Bodigrim commented Jan 23, 2023

@Mikolaj isn't it #8500? It persists for any new downloads after cabal update or cabal clean. Try to build a package you have not built before, or purge ~/.cabal/packages to force re-downloading.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 24, 2023

You are right, I'm getting it now.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 30, 2023

@bgamari @Kleidukos this doesn't fit here (as it's not just cabal); for the cabal haddock-project command, we also need haddock-2.26.1 to be released.

So how is this part progressing? Users are getting restless... ;)

@Bodigrim
Copy link
Collaborator

@Mikolaj could you please make a Hackage release for Cabal 3.10?

@Mikolaj
Copy link
Member

Mikolaj commented Mar 13, 2023

@Bodigrim: at your service, it's released.

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

5 participants