Skip to content
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

bump rust branch #213

Closed

Conversation

Suri312006
Copy link
Contributor

Okay after scratching my head for a while i figured it out, turns out you have to go into the rust directory and manually change what ver is checked out. this seems a bit tedious if things are changed in the future, maybe the url's in git submodules should be changed to track the git repo / branch so this happens automatically (as far as i know this is how it should work?)

@Suri312006
Copy link
Contributor Author

can confirm it works!
image

@dbittman
Copy link
Contributor

Ah, right, so the bump of the rust commit is blocked on me merging in another PR that I'm working on. As a work around until then, if you change the .gitmodules in rust so the backtrace URL uses https, that should work locally. Once the change that makes the newest rust commit compile is merged, i'll bump the version.

This is generally how submodules (can) work -- that the actual commit is locked, and the branch can move forward. This allows independent development on the repos without causing compile errors (which is the reason just bumping the rust version here will cause the toolchain to fail to build).

@Suri312006 Suri312006 closed this Jan 3, 2025
@Suri312006 Suri312006 deleted the bump-rust-ver branch January 3, 2025 06:12
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.

2 participants