Opened 3 years ago
Closed 3 years ago
#127 closed defect (fixed)
Installation unsucessfull (Mac)
Reported by: | Fernando | Owned by: | Olly Betts |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Other | Version: | 1.4.1 |
Keywords: | Cc: |
Description
brew tap survex/survex https://git.survex.com/homebrew-survex
Returns "Error: Tap survex/survex remote mismatch. git://git.survex.com/homebrew-survex != https://git.survex.com/homebrew-survex"
Change History (6)
comment:1 Changed 3 years ago by
comment:2 Changed 3 years ago by
I've just updated the homebrew repo to Survex 1.4.1, though this looks like a problem before it gets to actually installing anything.
comment:3 Changed 3 years ago by
Any feedback?
Perhaps originally you omitted the https:
part:
brew tap survex/survex git.survex.com/homebrew-survex
If homebrew assumed git://
when no scheme was given that would probably explain this.
comment:4 Changed 3 years ago by
Milestone: | 1.4.2 |
---|
comment:5 Changed 3 years ago by
You could also try removing the tap and then adding it back making sure it's with the https://
explicit:
brew untap --force survex/survex brew tap survex/survex https://git.survex.com/homebrew-survex
There's now a new Survex release and an updated homebrew package (notably it uses the newer homebrew wxwidgets package instead of the old wxmac package), but your problem isn't with installing the package as far as I can see.
comment:6 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fernando replied by email:
It worked!!!
Is this a first install, or was it installed before?
I don't understand where it's getting
git://git.survex.com/homebrew-survex
from - it's an alternate way to access the same repo, but less good as the connection is not encrypted so potentially someone could intercept the connection and return a different repo contents to you. Since homebrew runs scripts from the repo, that's not good. It's also more likely to hit problems with firewalls, whereas a firewall can't realistically blockhttps:
or else web browsing won't work, and it can't intercept it and mess with the contents in unhelpful ways because of the encryption.I checked the repo history and we've never advertised the
git:
URL.Perhaps this will help:
If not, can you check what this says: