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

vagrant provision fails - http for WordPress repo vs https #561

Closed
jeckman opened this Issue Feb 2, 2015 · 5 comments

Comments

Projects
None yet
3 participants
@jeckman

jeckman commented Feb 2, 2015

Running vagrant provision returns these errors:

svn: E120108: Unable to connect to a repository at URL 'http://core.svn.wordpress.org/trunk'

svn: E120108: Unable to connect to a repository at URL 'http://develop.svn.wordpress.org/trunk'

Looks to me like the repo does respond to their https versions - where would I change that for my existing develop and trunk sites inside vagrant?

Perhaps the issue is just that the http versions are down and will be back, but it would be nice to get them over https if one so chooses

@jeckman

This comment has been minimized.

jeckman commented Feb 2, 2015

Here's what I did.

sudo vagrant ssh
cd /vagrant/www/wordpress-trunk
svn relocate https://core.svn.wordpress.org/trunk

cd /vargrant/www/wordpress-develop
svn relocate https://develop.svn.wordpress.org/trunk

Will this persist now across vagrant up/down?

@cfoellmann

This comment has been minimized.

Member

cfoellmann commented Feb 2, 2015

that will be fine on up/down and even when you re-run provision.

@jeremyfelt jeremyfelt added the bug label Feb 22, 2015

@jeremyfelt jeremyfelt added this to the 1.3.0 (Next Release) milestone Feb 22, 2015

@jeremyfelt

This comment has been minimized.

Member

jeremyfelt commented Feb 22, 2015

It would be nice to detect existing http checkouts and run svn relocate during provisioning now that we're using the HTTPS repositories.

@jeremyfelt jeremyfelt modified the milestones: Future Release, 1.3.0 Jul 20, 2015

@jeremyfelt jeremyfelt modified the milestones: 1.3.0, Future Release Jul 20, 2015

@jeremyfelt

This comment has been minimized.

Member

jeremyfelt commented Jul 20, 2015

At this point it's probably better to make sure this scenario is well documented either as a FAQ via #605 or in the wiki. We've been forced HTTPS a while now and I haven't heard much.

We should document this as part of the 1.3.0 changelog.

@jeremyfelt jeremyfelt removed this from the 1.3.0 milestone Feb 21, 2016

@jeremyfelt

This comment has been minimized.

Member

jeremyfelt commented Mar 10, 2017

It looks like we did this in 9c1d453 :)

@jeremyfelt jeremyfelt closed this Mar 10, 2017

@jeremyfelt jeremyfelt added this to the 1.3.0 milestone Mar 10, 2017

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