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.

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

Polkadot install instructions do not work #1372

Closed
ggwpez opened this issue Sep 3, 2023 · 5 comments · Fixed by #1643
Closed

Polkadot install instructions do not work #1372

ggwpez opened this issue Sep 3, 2023 · 5 comments · Fixed by #1643
Labels
T11-documentation This PR/Issue is related to documentation.

Comments

@ggwpez
Copy link
Member

ggwpez commented Sep 3, 2023

Install instructions in the Polkadot README should be fixed.
@ggwpez ggwpez added the T11-documentation This PR/Issue is related to documentation. label Sep 3, 2023
This was referenced Sep 6, 2023
Closed
Merged
@kianenigma
Copy link
Contributor

What doesn't work about it, precisely? I haven't read or validate the whole thing, but it does cover various installation options.

@ggwpez
Copy link
Member Author

ggwpez commented Sep 11, 2023 •
edited
Loading

I have not tried it, but from a glance eg the binary path looks wrong ./target/release/polkadot.
This report came in the over chat from someone internally, I did not verified past that.

@rajdeep7Singh
Copy link

Hi @kianenigma @ggwpez I am facing a similar issue while running development node. I have asked on stackexcahnge as well. https://substrate.stackexchange.com/questions/9959/unable-to-run-development-node-after-repo-migration?noredirect=1#comment9955_9959

Can you guys help please?

@skunert
Copy link
Contributor

skunert commented Sep 19, 2023

@rajdeep7Singh The current problem is that --dev used to use the polkadot-dev runtime which will not be available anymore (and polkadot-native is already disabled by default). The command currently does not work as described in the install instructions.
A workaround for you in the meantime is to run cargo run -- --chain rococo-dev instead.

The situation will be improved by #1304, after it lands the dev chainspec will mean rococo-dev.

@rajdeep7Singh
Copy link

rajdeep7Singh commented Sep 19, 2023 •
edited
Loading

Got it! I thought it only used the polkadot runtime and specs with different configurations. Thanks i ll run a rococo-dev and import required pallets if it works. Thanks for the information

@skunert skunert mentioned this issue Sep 20, 2023
Merged
skunert added a commit that referenced this issue Sep 22, 2023
@skunert
Use correct target dir in polkadot readme (#1643)
fb0fd3e 
Closes #1372 

This fixes the target directories in the polkadot readme. I verified
manually the Ubuntu based install works on a fresh cloud machine. Build
from source also worked as described.

Since #1304 landed `--dev` also works again (not on v1.1.0 though), so I
would consider the install instructions fixed.
bgallois pushed a commit to duniter/duniter-polkadot-sdk that referenced this issue Mar 25, 2024
@skunert
Use correct target dir in polkadot readme (paritytech#1643)
d349b45 
Closes paritytech#1372 

This fixes the target directories in the polkadot readme. I verified
manually the Ubuntu based install works on a fresh cloud machine. Build
from source also worked as described.

Since paritytech#1304 landed `--dev` also works again (not on v1.1.0 though), so I
would consider the install instructions fixed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T11-documentation This PR/Issue is related to documentation.
Projects
Documentation
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use correct target dir in polkadot readme skunert/polkadot-sdk
4 participants
@kianenigma @skunert @ggwpez @rajdeep7Singh