Skip to content

contrib: remove obsolete scripts and move lockfile updates to justfile#575

Draft
satsfy wants to merge 1 commit intorust-bitcoin:masterfrom
satsfy:cleanup-contrib-scripts
Draft

contrib: remove obsolete scripts and move lockfile updates to justfile#575
satsfy wants to merge 1 commit intorust-bitcoin:masterfrom
satsfy:cleanup-contrib-scripts

Conversation

@satsfy
Copy link
Copy Markdown
Contributor

@satsfy satsfy commented May 1, 2026

Based on #574 (comment)

Remove contrib scripts that are no longer used and fold the lockfile update flow into the justfile.

This deletes:

  • bitcoind/contrib/extra_tests.sh
  • contrib/crates.sh
  • contrib/update-lock-files.sh

And moves lock file generation to justfile.

@tcharding
Copy link
Copy Markdown
Member

NACK patch 2. I believe there is a facility in cargo rbmt already for this.

Re patch 1, I know I have context in mind but for either new reviewers or future debuggers can you flesh out the git log. Here is a post I always point devs to to learn the craft of git log writing.

https://chris.beams.io/posts/git-commit/

Copy link
Copy Markdown
Collaborator

@jamillambert jamillambert left a comment

Choose a reason for hiding this comment

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

Patch 2 is NACKed and patch 1 is in #574. So currently there is nothing here. But...

What Tobin really means is please look at rust-bitcoin and copy what is done there in this PR for updating lock files.

extra_tests.sh was a manual runner for version-specific tests
that are now covered by CI. crates.sh listed workspace crates
for test scripts that have since been reorganised.
@satsfy
Copy link
Copy Markdown
Contributor Author

satsfy commented May 2, 2026

NACK patch 2. I believe there is a facility in cargo rbmt already for this.

Attempted to use cargo rbmt lock, but it runs cargo check --all-features -Z direct-minimal-versions which currently fails on this repo due to inconsistent minimum version bounds across Cargo.toml files. Sample output:

Output Logs

$ cargo rbmt lock
Updating lock files in: /home/renato/Desktop/rust-bitcoin/corepc2
Checking direct minimal versions...
$ cargo check --all-features -Z direct-minimal-versions
    Updating crates.io index
error: failed to select a version for `serde`.
    ... required by package `jsonrpc v0.20.0 (/home/renato/Desktop/rust-bitcoin/corepc2/jsonrpc)`
    ... which satisfies path dependency `jsonrpc` of package `corepc-client v0.13.0 (/home/renato/Desktop/rust-bitcoin/corepc2/client)`
    ... which satisfies path dependency `corepc-client` of package `bitcoind v0.38.0 (/home/renato/Desktop/rust-bitcoin/corepc2/bitcoind)`
versions that meet the requirements `^1` are: 1.0.0

all possible versions conflict with previously selected packages.

  previously selected package `serde v1.0.103`
    ... which satisfies dependency `serde = "^1.0.103"` of package `corepc-client v0.13.0 (/home/renato/Desktop/rust-bitcoin/corepc2/client)`
    ... which satisfies path dependency `corepc-client` of package `bitcoind v0.38.0 (/home/renato/Desktop/rust-bitcoin/corepc2/bitcoind)`

failed to select a version for `serde` which could resolve this conflict
Error updating lock files: command exited with non-zero code `cargo check --all-features -Z direct-minimal-versions`: 101

Making it work required bumping minimum bounds in nearly every Cargo.toml in the workspace (serde, serde_json, base64, log, tar, flate2, tempfile, native-tls...). Didn't follow through because of how many changes it would introduce. Do you suggest going ahead or another course of action? Alternatively, nyonson (not pinging yet) may have context on whether rbmt is meant to handle these issues or if using rbmt may be not be the right choice.

@satsfy satsfy marked this pull request as draft May 2, 2026 23:27
@satsfy satsfy force-pushed the cleanup-contrib-scripts branch from 5a4fd2c to f426e07 Compare May 2, 2026 23:28
@satsfy
Copy link
Copy Markdown
Contributor Author

satsfy commented May 2, 2026

Latest rebase improves commit message and removed NACKed solution.

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.

3 participants