This repository has been archived by the owner on Nov 22, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Windows 7 issues #11
Comments
Thanks for writing back!
|
1., 2.: $ git clone 'ssb://%n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256' git-ssb
Cloning into 'git-ssb'...
Repo not found with ID %n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256
$ git clone "ssb://%n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256" git-ssb
Cloning into 'git-ssb'...
Repo not found with ID %n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256
|
What's on npm is an older version of git-ssb, I wonder if you'll need the latest (which is on ssb-npm). If you're OK with another piece of legwork, you can follow this ssb-npm guide and then reinstall git-ssb with (I could see this as feeling pretty difficult to get started. We're still a pretty young community, and lots of things are still rough around the edges.) |
|
@dy Follow the guide I linked to in my above post; it'll walk you through it. ssb-npm is on ssb itself, so there's a bootstrapping process to follow. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My 2¢ of switching to git-ssb.
1. Not found repo
Trying to clone git-ssb repo to post issues.
$ git clone ssb://%n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256 Cloning into 'I403LQoyf2DtR3WQfCkDKlheQU=.sha256'... Repo not found with ID %n92DiQh7ietE+R+X/I403LQoyf2DtR3WQfCkDKlheQU=.sha256
What does that mean? Is that ok? Is the repo not available now or there is some internal error?
2. Not found issues
Cloning that via https is ok, but cannot get access to issues. Is that due to 1.?
3. Pushing to remote ssb gives EPIPE error
So how to post an issue, eg. this, to remote git-ssb?
The text was updated successfully, but these errors were encountered: