Skip to content

Move to get Haskell packages from CHaP #4078

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

Merged
merged 1 commit into from
Nov 8, 2022
Merged

Move to get Haskell packages from CHaP #4078

merged 1 commit into from
Nov 8, 2022

Conversation

andreabedini
Copy link
Contributor

This moves the repository to use cardano-haskell-packages (CHaP) repository.

This is currently blocked by input-output-hk/io-sim#37. CHaP had been pre-populated with the dependencies of the lastest release of cardano-node, but ouroboros-network has progressed in the meantime requiring a newer version of io-sim which is not in CHaP yet.

@michaelpj
Copy link
Contributor

This is currently blocked by input-output-hk/io-sim#37.

It doesn't have to be blocked: use a s-r-p for now, and then we can remove it once that is merged. We can still get this PR in before that.

@michaelpj
Copy link
Contributor

Note that shell.nix is using cabalWrapped, which can and should go.

@andreabedini
Copy link
Contributor Author

It doesn't have to be blocked: use a s-r-p for now, and then we can remove it once that is merged. We can still get this PR in before that.

ok, I will chase this up on Monday.

Copy link
Contributor

@michaelpj michaelpj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it went green!

@andreabedini
Copy link
Contributor Author

Now at least it builds. Left to do is to remove one srp at the time so see if we can improve on the situation.

@michaelpj
Copy link
Contributor

I think we could merge this as is and then work from this point? any objections?

@andreabedini
Copy link
Contributor Author

I think we could merge this as is and then work from this point? any objections?

I am just trying to see if the new io-sim packages help.

@andreabedini
Copy link
Contributor Author

But perhaps you made a good point that it can be done in a separate PR

@michaelpj
Copy link
Contributor

I am just trying to see if the new io-sim packages help.

I just tried that and they don't work with the version of typed-protocols being used 😅 So I think let's move on for now.

@andreabedini andreabedini marked this pull request as ready for review October 26, 2022 10:06
@andreabedini andreabedini requested review from newhoggy, a team, bolt12 and nfrisby as code owners October 26, 2022 10:06
@andreabedini
Copy link
Contributor Author

Ok, let's call this done. We will improve on it later.

@michaelpj
Copy link
Contributor

We just got compatible typed-protocols published, I'm just trying to see if I can roll that into this also.

@michaelpj michaelpj requested a review from dnadales as a code owner October 26, 2022 15:02
@michaelpj
Copy link
Contributor

Worked locally, pushing it.

@nfrisby
Copy link
Contributor

nfrisby commented Oct 26, 2022

By reading the new text in CONTRIBUTING.md, will I understand everything I need to understand in order to review the rest of this PR? Thanks!

cc @andreabedini @michaelpj

@michaelpj
Copy link
Contributor

michaelpj commented Oct 26, 2022

@nfrisby if you read it and you don't understand, then I regard that as a deficiency in the text and please say so :) you might also need to read the CHaP readme, which is linked.

@michaelpj
Copy link
Contributor

@coot is this good to go?

@coot
Copy link
Contributor

coot commented Nov 2, 2022

@michaelpj this is only about using CHaP, not releasing anything to it, right? The next version of packages from this repo needs to be released from the release/cardano-node.1.35.x branch not master.

@andreabedini
Copy link
Contributor Author

this is only about using CHaP, not releasing anything to it, right? The next version of packages from this repo needs to be released from the release/cardano-node.1.35.x branch not master.

@coot correct, we are only replacing source-repository-packages with equivalent ones in CHaP.

@michaelpj
Copy link
Contributor

Yes, this doesn't say anything about how you release your packages. It should help with releasing packages, in that if you have a "clean" cabal.project with CHaP, then you know that your released package will build downstream without any additional config. However, I'm not sure it's worth backporting these changes to the release branch just for that! We can do what we need to do for the 1.35 release and just take this forward on master.

@amesgen
Copy link
Member

amesgen commented Nov 4, 2022

I'm hoping to be able to borrow the Windows CI fix from input-output-hk/cardano-node#4590 when it lands, if it works...

FYI: @coot already tries to integrate it as part of #4134

@michaelpj
Copy link
Contributor

bors try

iohk-bors bot added a commit that referenced this pull request Nov 7, 2022
This moves the repository to use cardano-haskell-packages (CHaP) repository.
@michaelpj
Copy link
Contributor

So close. It went green but conflicts with #4103. Rebased to fix conflicts.

@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 7, 2022

try

Timed out.

1 similar comment
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 7, 2022

try

Timed out.

@andreabedini
Copy link
Contributor Author

bors try

iohk-bors bot added a commit that referenced this pull request Nov 8, 2022
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 8, 2022

try

Build failed:

@andreabedini
Copy link
Contributor Author

building of '/nix/store/xnyardh9jz8l16yrv80d2azx1rvlbg0y-ouroboros-consensus-byron-test-test-test-0.1.0.0-check' timed out after 900 seconds of silence

@amesgen
Copy link
Member

amesgen commented Nov 8, 2022

bors retry

iohk-bors bot added a commit that referenced this pull request Nov 8, 2022
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 8, 2022

@michaelpj
Copy link
Contributor

bors merge

@michaelpj
Copy link
Contributor

no idea if that will work

@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 8, 2022

@iohk-bors iohk-bors bot merged commit 8b21e2b into master Nov 8, 2022
@iohk-bors iohk-bors bot deleted the chap branch November 8, 2022 14:43
@michaelpj
Copy link
Contributor

hallelujah

@amesgen amesgen mentioned this pull request Nov 15, 2022
9 tasks
iohk-bors bot added a commit that referenced this pull request Nov 15, 2022
4148: Add simple `hie.yaml` r=amesgen a=amesgen

# Description

This is necessary due to a bug somewhere in HLS 1.7 vs 1.8, which was upgraded in #4078.



Co-authored-by: Alexander Esgen <[email protected]>
iohk-bors bot added a commit that referenced this pull request Nov 19, 2022
4148: Add simple `hie.yaml` r=amesgen a=amesgen

# Description

This is necessary due to a bug somewhere in HLS 1.7 vs 1.8, which was upgraded in #4078.



Co-authored-by: Alexander Esgen <[email protected]>
amesgen added a commit that referenced this pull request Dec 14, 2022
This input was added in #3661, but was not actually used. Now, that we tell
people to run `niv update hackage.nix` in the CONTRIBUTING guide (see #4078), we
should fix this.
amesgen added a commit that referenced this pull request Dec 15, 2022
This input was added in #3661, but was not actually used. Now, that we tell
people to run `niv update hackage.nix` in the CONTRIBUTING guide (see #4078), we
should fix this.
newhoggy pushed a commit that referenced this pull request Jan 2, 2023
This input was added in #3661, but was not actually used. Now, that we tell
people to run `niv update hackage.nix` in the CONTRIBUTING guide (see #4078), we
should fix this.
newhoggy pushed a commit that referenced this pull request Jan 5, 2023
This input was added in #3661, but was not actually used. Now, that we tell
people to run `niv update hackage.nix` in the CONTRIBUTING guide (see #4078), we
should fix this.
coot pushed a commit that referenced this pull request Jan 5, 2023
This input was added in #3661, but was not actually used. Now, that we tell
people to run `niv update hackage.nix` in the CONTRIBUTING guide (see #4078), we
should fix this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants