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

LibraryManager: Cloning from private git repos fails #925

Closed
stelgenhof opened this Issue Mar 30, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@stelgenhof

stelgenhof commented Mar 30, 2017

Configuration

Operating system:
Arch Linux

PlatformIO Version (platformio --version):
PlatformIO, version 3.3.0

Description of problem

I have a separate library stored in a private Git repository (via SSH). When adding this to the platformio.ini configuration and/or updating my project, the git clone process fails with the following error message:

fatal: No path specified. See 'man git-pull' for valid url syntax

Steps to Reproduce

Add library dependency to the platformio.ini as follows:

git+ssh://<username>@<hostname>:<portnumber>/somepath

Note: I use a non-standard SSH port for accessing my git repos via SSH.

Run the build.

Actual Results

fatal: No path specified. See 'man git-pull' for valid url syntax
CalledProcessError: Command '['git', 'clone', '--recursive', '--depth', '1', 'ssh://<username>', '/path/to/project/.piolibdeps/_tmp_installing-a6aa7_-package']' returned non-zero exit status 128

From this last part of the error output, It looks like the full path is truncated after the '@' sign. Expecting to see a format like: ssh://<username>@<hostname>:<portnumber>/somepath

@ivankravets ivankravets added this to the 3.4.0 milestone Mar 30, 2017

@ivankravets ivankravets added the bug label Mar 30, 2017

@ivankravets

This comment has been minimized.

Show comment
Hide comment
@stelgenhof

This comment has been minimized.

Show comment
Hide comment
@stelgenhof

stelgenhof Mar 30, 2017

Ok. Let me try that format. For the time being I'm just updating by manually issuing a git-pull in a terminal session.

stelgenhof commented Mar 30, 2017

Ok. Let me try that format. For the time being I'm just updating by manually issuing a git-pull in a terminal session.

@stelgenhof

This comment has been minimized.

Show comment
Hide comment
@stelgenhof

stelgenhof Mar 30, 2017

Looking at that format, that is actually not how my git server is set up. My server is set up exactly as described here: https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server

Found out it works fine when the user part is removed from the path. So instead of this:

git+ssh://<username>@<hostname>:<portnumber>/somepath

I used this:

git+ssh://<hostname>:<portnumber>/somepath

Which makes actually sense since I am using SSH public keys so a username isn't required.

stelgenhof commented Mar 30, 2017

Looking at that format, that is actually not how my git server is set up. My server is set up exactly as described here: https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server

Found out it works fine when the user part is removed from the path. So instead of this:

git+ssh://<username>@<hostname>:<portnumber>/somepath

I used this:

git+ssh://<hostname>:<portnumber>/somepath

Which makes actually sense since I am using SSH public keys so a username isn't required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment