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

Plugin build asks for github / ssh key passwords on multiple plugins #130

Open
henning opened this issue Dec 12, 2021 · 3 comments
Open

Comments

@henning
Copy link
Contributor

henning commented Dec 12, 2021

After getting the bootstrap process to work for x86_64, I try to run build for all available plugins.
I simply run an ls in the plugins directory and run build for each one.

So far, I have been asked one time for my ssh key password (and forgot to note where exactly/for which plugin), and now I get this:

Cloning into '/home/henning/data/produktion/sound-software-dev/mod-workdir/x86_64/build/wolf-shaper-labs-d0b46c9ece642488efed3cd255df22516966b334/plugins/wolf-shaper/Libs/inih'...
Username for 'https://github.com': 

Is there a reason for this to be like that?
Or can/should I look into it and try to fix it?

@falkTX
Copy link
Member

falkTX commented Dec 12, 2021

Dont try to build all, those repos might not even exist anymore, or have them moved, or something else.
There are quite a few packages in MPB that were made just for testing, but are not useful at all.

@henning
Copy link
Contributor Author

henning commented Dec 13, 2021

too late - I have build 480 plugins now ;)
actually besides these github authentication issues it worked surprisingly well, but clearly i haven't checked the results any further yet.

Impressive work!
Is there a list of the "good" ones that are useful/working?

@rominator1983
Copy link
Contributor

a little late to the game. but in case someone stumbles upon this.
I am also in the league of building them all and have described here that adding github to the known hosts works:
ssh-keyscan github.com >> ~/.ssh/known_hosts

@falkTX I suppose you do not want to add that to the README.md
So after this has been written down here I suppose it is safe to close this issue.

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

No branches or pull requests

3 participants