- cabal-devel - Haskell.org

[Help wanted] Unexplained CI failure for #9088
by Theophile Hécate Choutri 11 Aug '23

11 Aug '23

Hi everyone, a nasty CI failure for #9088 <https://github.com/haskell/cabal/pull/9088> is preventing us from finishing the release of cabal-3.10.2.0. I am out of my depth regarding how to fix it. It seems that it's a mere matter of accepting new output for the CLI's golden tests, but evidently it's not that simple, as Brandon also had trouble with it. Here is the output of the CI: https://github.com/haskell/cabal/actions/runs/5799856732/job/15720762229#st… Thank you for your help.

1 0

03/08/2023 Cabal meeting minutes
by Theophile Hécate Choutri 03 Aug '23

03 Aug '23

Hi everyone You will find below the minutes of the Cabal meeting that was held on the 03/08/2023. This meeting occurs every two weeks and is absolutely open to developers, newcomers and stakeholders. Do contact the dev team if you want an invitation to the event. --- ## 3.10.2.0 patch release Hécate: The pipeline situation seems to have been fixed, as such Mikołaj & I are able to run GitLab pipelines for cabal. I suggest that once the following PRs are merged, the release process (including security fixes) resume. I'd ideally like it to be done by next week. * https://github.com/haskell/cabal/pull/9088 ## 3.12.1.0 major release Hécate: In accordance with the planned schedule of GHC 9.8, we would like to perform a major release at the end of August. This would be a good idea to highly promote cabal-head nightlies and make sure that the 3.12.1.0 release is already used by people in all but name before we formally create the tag and publish the binaries. (f-a et al.): Things we should warn users about: - `cabal check`: cabal now warns about missing upper bounds. I have a PR ready to address this (ignore some checks) but #8427 needs to be merged first. ## Other topics ### Yvan * I have a working `flake.nix` and `shell.nix` that declare my dev environment to work on Cabal, do you think I should share it in a PR? * I was about to write a detailed issue where I explain why https://cabal.readthedocs.io/en/latest/nix-integration.html doesn't work at all (or it's very poorly documented and I don't understand how to properly use it). Instead of fixing it, I'm in favor of removing it because I think it's overall not a good idea to have this kind of integration. * Hécate: Action Item: We should take the pulse of the community for a couple of releases. We should point to https://nixos.wiki/wiki/Haskell for transition. * If time permits, I also wanted to have feedback on my currently open PRs https://github.com/haskell/cabal/pulls/yvan-sraka.

2 1

20/07/2023 Cabal meeting minutes
by Theophile Hécate Choutri 20 Jul '23

20 Jul '23

Hi everyone You will find below the minutes of the Cabal meeting that was held on the 20/07/2023. This meeting occurs every two weeks and is absolutely open to developers, newcomers and stakeholders. Do contact the dev team if you want an invitation to the event. --- # 3.10 backports * https://github.com/haskell/cabal/pull/9141 * https://github.com/haskell/cabal/pull/9088 ## Future work wishlist Gershom would like to have an override of cabal.project imports. There are many code paths that are not always entirely lined up. Hécate would like to refactor some of the code paths that live independently of each-other, do the same things, but output different observable results when called the same way. The typical case is one code path living in lib:Cabal, another living in cabal-install, and they could be factored. # Current progress Francesco A. is looking at #7544, to see whether it fits `cabal check` needs. Kristen is reviewing https://github.com/haskell/cabal/pull/9134 Suganya is waiting for #9018 to be merged and working in parallel to typify other errors. Good job Suganya! We discussed the relationship between GHC 9.8 and the accompanying Cabal release. Ben suggested that the Cabal release could be a minor release. However, given that in 9.8 we have `jsem` which requires Cabal support, it seems appropriate for this to be a major release (Cabal-3.12). Hecate agreed. We will try to have a major release branch for GHC 9.8 alpha 3 in late August Ben enquired about the "inplace" flag and its semantics, related to a bug encountered during GHC development: https://gitlab.haskell.org/ghc/ghc/-/issues/23594

1 0

Fwd: Cabal/ | Repository mirroring paused
by Mikolaj Konarski 11 Jul '23

11 Jul '23

Hello, Any idea what this is about? I guess the mirror of cabal's github repo on gitlab? Did anything change there? Cheers, Mikolaj ---------- Forwarded message --------- From: GitLab <gitlab(a)gitlab.haskell.org> Date: Tue, Jul 4, 2023 at 11:11 PM Subject: Cabal/ | Repository mirroring paused To: <mikolaj.konarski(a)gmail.com> Repository mirroring on haskell/cabal has been paused due to too many failures. The last failure was: 13:updating ref with hooks: running pre-receive hooks: GitLab: You are not allowed to push code to protected branches on this project.. To resume mirroring update your repository mirroring settings. —

3 6

A pure Matrix room for Hackage/Cabal
by Artem Pelenitsyn 03 Jul '23

03 Jul '23

Dear Hackage/Cabal devs, geekosaur created a purely Matrix room for us and shared the admin bit with me: https://matrix.to/#/#hackage:matrix.org We'd be happy to share more and have you there, at the least! This is prompted by the announcement earlier today: https://libera.chat/news/matrix-deportalling tldr; is that the "portal mode" where you can participate in an IRC-first room from Matrix transparently will be decommissioned by the end of the month. Other options are on the table. E.g. I think @fgaz is researching the "plumbing mode" where you have a pure-Matrix room with a connection to a IRC-native room like #hackage(a)libera.chat, but I don't know enough about it. As far as I understand, this new room I'm announcing here does not close any doors. Personally, I'd hope that we all just move to Matrix and forget the IRC horror where we suggest newcomers to use a paid (!!!) solution like IRCCloud if they want to address a question to Cabal devs (who only hang out on IRC) and have a better than 1970s-experience (and a mobile client). -- Kind regards, Artem

1 0

Fwd: Cabal security advisory proposal
by Theophile Hécate Choutri 02 Jul '23

02 Jul '23

Hi everyone, We have received another proposal regarding the Sovereign Tech Fund grants. I'd be happy to spend some time on Thursday to make sure we're on the same page. In the meantime, please do not hesitate to provide feedback. Cheers, Hécate ---------- Forwarded message --------- From: Trevis Elser <trevis(a)flipstone.com> Date: Sun, 2 Jul 2023 at 17:27 Subject: Cabal security advisory proposal To: hecate(a)haskell.foundation <hecate(a)haskell.foundation> Hi there! You may have heard the German government is accepting proposals to work on OSS (https://sovereigntechfund.de/en/challenges/) I'm working on putting together a submission for my employer, Flipstone, to add a cabal feature allowing a check of dependencies against the new security advisories database. @David Thrane Christiansen Suggested reaching out to you to get any suggestions in submitting this and to see if you might have anything for us to add particularly to the section that is as follows: "Describe your relationship to the maintainers of this technology. Are you yourself the maintainer? Do they know you plan to do this work and do they support it? Please tell us more about how you obtained their support and how you plan to work together to make sure your contributions are accepted." For what it's worth my thought is that we'd use the external command functionality that I've seen you've contributed to at https://github.com/haskell/cabal/pull/9063 to at least initially build this out and then perhaps work to get it merged or not. Finally, I'd love to hear if you have thoughts on accurately representing cabal for the questions: "How are decisions regarding this technology's development made? Please describe the project's governance model." and "How does this project handle security risks? Are there policies, procedures, or tools in place to minimize the introduction of vulnerabilities or undesired contributions?" Thanks so much for your time! -- Trevis Elser | Chair Stability Working Group | Software Engineer

1 0

Sovereign Tech Fund application
by Adam Gundry 29 Jun '23

29 Jun '23

Hi Cabal Devs, I've been working with Duncan, Mikolaj and others at Well-Typed on a grant application to the Sovereign Tech Fund (https://sovereigntechfund.de/en/) to try to raise funds for Cabal maintenance in general, and pushing forward the replacement of the custom build-type in particular (based on a plan from Duncan). Unfortunately we're scrambling to get this ready on a fairly tight schedule (the application deadline is next week), which is why we've not been able to discuss this more widely before now. But if you're interested to see what we are planning, the draft proposal is here: https://docs.google.com/document/d/1-pIdxPbHjbN_rLN72gzCoe_hpEXXrWzmPuFxO8V… Any feedback you may have (preferably by comments on the document) would be most welcome. Hopefully none of this is particularly controversial, but if you see anything incorrect or problematic, please do let us know. I'll be away next week, so one of the others will be finishing off the draft and submitting it. Best wishes, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

1 0

CPP guards for very old Cabal versions in the tests: what do we do?
by Theophile Hécate Choutri 03 Jun '23

03 Jun '23

Hi everyone, While exploring the code base, I stumbled across such CPP guards: #if MIN_VERSION_Cabal(1,25,0) I am wondering if such guards are still justified after 6 and a half years. I have opened a consultation here: https://github.com/haskell/cabal/issues/8998. Please chime in. Cheers, Hécate

1 0

cabal-dev meeting schedule
by Francesco Ariis 18 May '23

18 May '23

Hello everyone, at today cabal-dev meeting we talked about the proposal of shifting the fortnightly dev meeting by _one week_ [1], to accommodate more people (namely, Emily). Question: - would anyone else be affected (more likely/unlikely to join the meeting) with this date change? [1] so 25 May, 8 June, etc. instead of 18 may, 1 June, 15 June, etc.

2 1

Data constructor of VersionIntervals not exported
by Daniel Trstenjak 16 May '23

16 May '23

Hi, I'm trying to update my tool cabal-bounds[1] to the newest version of the Cabal library. My tool needs to convert a [VersionInterval] into a VersionRange, which currently doesn't seem to be possible, because the data constructor of VersionIntervals isn't exported from Distribution.Types.VersionInterval. Best regards, Daniel Trstenjak [1] https://github.com/dan-t/cabal-bounds

3 3