Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

chore: downgrade neptune to 5.1.x #1618

Closed
wants to merge 1 commit into from
Closed

chore: downgrade neptune to 5.1.x #1618

wants to merge 1 commit into from

Conversation

vmx
Copy link
Contributor

@vmx vmx commented Jul 1, 2022

Downgrading neptune makes the master branch build again.

Downgrading `neptune` makes the master branch build again.
@cryptonemo
Copy link
Collaborator

I'm preferring #1615 to this and may merge. We were waiting on @porcuquine to release Neptune v7, but could merge while it's still a neptune branch if causing issues.

@storojs72
Copy link
Contributor

storojs72 commented Jul 1, 2022

Downgrading neptune is good workaround, but it doesn't free us from updating bellperson here in rust-fil-proofs. And unfortunately we will get this issue with build again and again when versions of bellperson become different. Should we may be prefer upgrading dependencies rather than downgrading?

@cryptonemo
Copy link
Collaborator

Closing since #1615 was merged

@cryptonemo cryptonemo closed this Jul 22, 2022
@vmx vmx deleted the downgrade-neptune51x branch December 19, 2023 16:45
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants