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.

Sign up for GitHub

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

Jump to bottom

fix migration #2

Closed

chrisguida wants to merge 1 commit into Retropex:knots-for-community from chrisguida:cguida/fix-migration

chrisguida commented Feb 14, 2024 •

edited

Loading

The migration was messed up in two ways:

technically v2transport doesn't exist yet and that will screw up trying to upgrade and downgrade with normal bitcoin core (switching back and forth between knots and core will probably always be awkward until support for two different packages with the same name is supported upstream)
datacarrier, datacarriersize, and permitbaremultisig weren't being initialized, resulting in this message upon installation:

This PR fixes both issues.

Retropex self-assigned this

Retropex added the bug label


          fix migration

d866c41

chrisguida force-pushed the cguida/fix-migration branch from 829be23 to d866c41 Compare

February 15, 2024 20:46

Retropex force-pushed the knots-for-community branch 2 times, most recently from 1f6c25e to d1c38f4 Compare

March 28, 2024 17:31

Owner

Retropex commented Mar 28, 2024

rebased and fixed in this commit d1c38f4
Thanks Chris!

Retropex closed this

BitcoinMechanic mentioned this pull request

add prioritise transaction action #8

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug