Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#60593 closed defect (worksforme)

Use MacPorts git when syncing with git on OS X Mountain Lion and earlier

Reported by: iefdev (Eric F) Owned by:
Priority: Normal Milestone:
Component: base Version: 2.6.2
Keywords: Cc:
Port:

Description

I setup my install to sync with: wiki:howto/SyncingWithGit

I got the same SSL warning as in #55989. The error output showing it was using a hardcoded path to /usr/bin/git.

Would be great if the same fix was added to work with port [-v] sync as well. I solved it temp with a symlink, for now.

Change History (5)

comment:1 Changed 4 years ago by kencu (Ken)

I use port -v sync exclusively, with a number of local repositories that sync with github, and have not noted it to have this error....are you on Lion still with this problem?

comment:2 in reply to:  1 Changed 4 years ago by iEFdev

Replying to kencu:

I use port -v sync exclusively, with a number of local repositories that sync with github, and have not noted it to have this error....are you on Lion still with this problem?

Yes, that is correct. And I'm using your bootstrap install who took care of the curl issue.

Only local repo I have, controlled by port, is this one. All other (local) repos I have works fine, since I use (only) git, but now when this errored – that output showed it used a hard coded path to /usr/bin/git ... in the command that failed. So, I assume it's the same kind of error as decribed in #55989. And it has the same SSL error output.

comment:3 in reply to:  1 Changed 4 years ago by iEFdev

Replying to kencu:

I use port -v sync exclusively, with a number of local repositories that sync with github, and have not noted it to have this error....are you on Lion still with this problem?

I think I've found the root of it now… I reverted the symlink, just to reproduce the exact output message, but it still worked. Great in one way, but not what I expected. I thought there maybe was some sort of connection cache or something that allowed the connection through. So, now this morning… It still worked without a symlink - but, when I use it on the bootstrap – that's where it fails.

$ sudo boort -v sync

// ...

Synchronizing local ports tree from file:///opt/bootstrap/var/macports/sources/github.com/macports/macports-ports/
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/macports/macports-ports.git/info/refs?service=git-upload-pack
fatal: HTTP request failed
Command failed: /usr/bin/git pull --rebase

I've set it up with:

  • /opt/bootstrap/var/macports/sources/github.com/macports/macports-ports/
  • /opt/local/var/macports/sources/github.com/macports/macports-ports/ -> symlink to other one (ie. I'm using the same repo for both)

So, I guess it's that curl/ssl issue, since it works from the port version using the bootstrapped curl - which the bootstrap version doesn't.

I'm ok using a symlink (for my custom case). I still think it would be better to use git instead of /usr/bin/git. Except solving this issue, it would always use the users desired version of git, through PATH. But, if you want to close it, I'm ok with it.

comment:4 Changed 4 years ago by kencu (Ken)

Resolution: worksforme
Status: newclosed

you could always install git in the bootstrap prefix to fix that...but at a certain point,...just no. :)

glad you sorted it out.

Last edited 4 years ago by kencu (Ken) (previous) (diff)

comment:5 in reply to:  4 Changed 4 years ago by iEFdev

Replying to kencu:

you could always install git in the bootstrap prefix to fix that...but at a certain point,...just no. :)

glad you sorted it out.

Thanks… Yes, agree. But, I'll be fine. Actually I don't need to sync the bootstrap since they use the same repo and Portindex. Will prob flip the repo and the symlinked repo around, so the repo sits in the real port install.

Note: See TracTickets for help on using tickets.