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

parachain build error with polkadot-stable2407-3, as patched crates are missing vendoring #6185

Closed
2 tasks done
clangenb opened this issue Oct 23, 2024 · 2 comments
Closed
2 tasks done
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@clangenb
Copy link
Contributor

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

I had to downgrade a few crates after upgrading to 2024-3 with psvm because the crates haven't been found. The affected crates can be seen here, ajuna-network/ajuna-parachain@13c02b8.

Downgrading them fixes the issue.

Steps to reproduce

  1. Get a parachain
  2. run psvm -v polkadot-stable2407-3
  3. cargo tree -i -p sp-core
@clangenb clangenb added I10-unconfirmed Issue might be valid, but it's not yet known. I2-bug The node fails to follow expected behavior. labels Oct 23, 2024
@clangenb clangenb changed the title parachain build error with polkadot-stable202407-3, as patched crates are missing vendoring parachain build error with polkadot-stable2407-3, as patched crates are missing vendoring Oct 23, 2024
@xlc
Copy link
Contributor

xlc commented Oct 23, 2024

related: polkadot-fellows/runtimes#493

I raised this issue somewhere (can't find it anymore, I guess I asked someone in one of the Element room), but essentially the patch are not published to crates.io, which is very bad.

@clangenb
Copy link
Contributor Author

Hmm, I see. I agree that this should be fixed. Otherwise, the only one who benefit from patches are node operators or devs who depend on the git source of the polkadot sdk. But the latter don't need to care about releases in the first place. Thanks for answering.

I will close this issue though in favor of #6206, as the underlying issue is the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

No branches or pull requests

2 participants