search

WordPress / meta-environment

A collection of scripts that provision the official WordPress.org websites into a Varying Vagrant Vagrants installation.
190 stars 69 forks source link

VVV: Error on install of site-wordpress-meta-environment #148

Closed paaljoachim closed 3 years ago

paaljoachim commented 3 years ago

I am going through the setup instructions here: https://github.com/WordPress/contributor-day-handbook/blob/master/*Start%20Here%20-%20General%20Guides/How%20to%20setup%20VVV.md

---> To enable these environments, check if you have a config/config.yml file in your VVV folder. If you don't have a config.yml file, then run vagrant status and it will be created for you. In config.yml, look for the wordpress-trunk and wordpress-meta-environment and change skip_provisioning: true to skip_provisioning: false and save. Finally, run vagrant up --provision to apply the change. This will take some time to run, especially if you have enabled the Meta environment.

I changed wordpress-meta-environment: skip_provisioning: false

Then ran run vagrant up --provision

I see this in terminal:

==> default: Running provisioner: site-wordpress-one (shell)...
  default: Running: /var/folders/wp/jwpvvbxs6mj88nny94lz164m0000gn/T/vagrant-shell20210410-2365-mttk0y.sh
  default:  ▷ Running the 'site-wordpress-one' provisioner...
  default:  * Reloading Nginx config files
  default:  ✔ The 'site-wordpress-one' provisioner completed in 3 seconds.
==> default: Running provisioner: site-wordpress-two (shell)...
  default: Running: /var/folders/wp/jwpvvbxs6mj88nny94lz164m0000gn/T/vagrant-shell20210410-2365-1ne9lbr.sh
  default:  ▷ Running the 'site-wordpress-two' provisioner...
  default:  * Reloading Nginx config files
  default:  ✔ The 'site-wordpress-two' provisioner completed in 3 seconds.
==> default: Running provisioner: site-wordpress-trunk (shell)...
  default: Running: /var/folders/wp/jwpvvbxs6mj88nny94lz164m0000gn/T/vagrant-shell20210410-2365-txz95.sh
  default:  ▷ Running the 'site-wordpress-trunk' provisioner...
  default:  * Downloading wordpress-trunk, git cloning from https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop.git into /srv/www/wordpress-trunk
  default:  * wordpress-trunk Site Template clone successful
  default:  ✔ gifsicle pre-build test passed successfully
  default:  ✔ jpegtran pre-build test passed successfully
  default:  ✔ optipng pre-build test passed successfully
  default: npm WARN @emotion/native@10.0.27 requires a peer of react-native@>=0.14.0 <1 but none is installed. You must install peer dependencies yourself.
  default: npm WARN @WordPress.org/e2e-test-utils@5.1.1 requires a peer of puppeteer@>=1.19.0 but none is installed. You must install peer dependencies yourself.
  default: npm WARN react-native-url-polyfill@1.2.0 requires a peer of react-native@* but none is installed. You must install peer dependencies yourself.
  default: npm WARN react-test-renderer@16.14.0 requires a peer of react@^16.14.0 but none is installed. You must install peer dependencies yourself.
  default: npm WARN sinon-test@3.0.0 requires a peer of sinon@2.x - 9.x but none is installed. You must install peer dependencies yourself.
  default: npm WARN tsutils@3.21.0 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
  default: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/fsevents):
  default: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  default: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
  default: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  default: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
  default: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  default:  * Reloading Nginx config files
default:  ✔ The 'site-wordpress-trunk' provisioner completed in 468 seconds.
==> default: Running provisioner: site-wordpress-meta-environment (shell)...
  default: Running: /var/folders/wp/jwpvvbxs6mj88nny94lz164m0000gn/T/vagrant-shell20210410-2365-ptf3go.sh
  default:  ▷ Running the 'site-wordpress-meta-environment' provisioner...
  default:  * Downloading wordpress-meta-environment, git cloning from https://github.com/WordPress/meta-environment.git into /srv/www/wordpress-meta-environment
  default:  * wordpress-meta-environment Site Template clone successful
  default: Cloning into '/srv/www/wordpress-meta-environment/meta-repository'...
  default: Updating files: 15% (441/2844)
  default: Updating files: 16% (456/2844)
  default: Updating files: 17% (484/2844)
  default: Updating files: 18% (512/2844)
  default: Updating files: 19% (541/2844)
  default: Updating files: 20% (569/2844)
  default: Updating files: 21% (598/2844)
  default: Updating files: 22% (626/2844)
  default: Updating files: 23% (655/2844)
  default: Updating files: 24% (683/2844)
  default: Updating files: 25% (711/2844)
  default: Updating files: 26% (740/2844)
  default: Updating files: 27% (768/2844)
  default: Updating files: 28% (797/2844)
  default: Updating files: 29% (825/2844)
  default: Updating files: 30% (854/2844)
  default: Updating files: 30% (868/2844)
  default: Updating files: 31% (882/2844)
  default: Updating files: 32% (911/2844)
  default: Updating files: 33% (939/2844)
  default: Updating files: 34% (967/2844)
  default: Updating files: 35% (996/2844)
  default: Updating files: 36% (1024/2844)
  default: Updating files: 37% (1053/2844)
  default: Updating files: 38% (1081/2844)
  default: Updating files: 39% (1110/2844)
  default: Updating files: 40% (1138/2844)
  default: Updating files: 41% (1167/2844)
  default: Updating files: 42% (1195/2844)
  default: Updating files: 43% (1223/2844)
  default: Updating files: 44% (1252/2844)
  default: Updating files: 45% (1280/2844)
  default: Updating files: 45% (1291/2844)
  default: Updating files: 46% (1309/2844)
  default: Updating files: 47% (1337/2844)
  default: Updating files: 48% (1366/2844)
  default: Updating files: 49% (1394/2844)
  default: Updating files: 50% (1422/2844)
  default: Updating files: 51% (1451/2844)
  default: Updating files: 52% (1479/2844)
  default: Updating files: 53% (1508/2844)
  default: Updating files: 54% (1536/2844)
  default: Updating files: 55% (1565/2844)
  default: Updating files: 56% (1593/2844)
  default: Updating files: 57% (1622/2844)
  default: Updating files: 58% (1650/2844)
  default: Updating files: 59% (1678/2844)
  default: Updating files: 60% (1707/2844)
  default: Updating files: 61% (1735/2844)
  default: Updating files: 62% (1764/2844)
  default: Updating files: 63% (1792/2844)
  default: Updating files: 63% (1807/2844)
  default: Updating files: 64% (1821/2844)
  default: Updating files: 65% (1849/2844)
  default: Updating files: 66% (1878/2844)
  default: Updating files: 67% (1906/2844)
  default: Updating files: 68% (1934/2844)
  default: Updating files: 69% (1963/2844)
  default: Updating files: 70% (1991/2844)
  default: Updating files: 71% (2020/2844)
  default: Updating files: 72% (2048/2844)
  default: Updating files: 73% (2077/2844)
  default: Updating files: 74% (2105/2844)
  default: Updating files: 75% (2133/2844)
  default: Updating files: 76% (2162/2844)
  default: Updating files: 77% (2190/2844)
  default: Updating files: 78% (2219/2844)
  default: Updating files: 79% (2247/2844)
  default: Updating files: 79% (2274/2844)
  default: Updating files: 80% (2276/2844)
  default: Updating files: 81% (2304/2844)
  default: Updating files: 82% (2333/2844)
  default: Updating files: 83% (2361/2844)
  default: Updating files: 84% (2389/2844)
  default: Updating files: 85% (2418/2844)
  default: Updating files: 86% (2446/2844)
  default: Updating files: 87% (2475/2844)
  default: Updating files: 88% (2503/2844)
  default: Updating files: 89% (2532/2844)
  default: Updating files: 90% (2560/2844)
  default: Updating files: 91% (2589/2844)
  default: Updating files: 92% (2617/2844)
  default: Updating files: 93% (2645/2844)
  default: Updating files: 94% (2674/2844)
  default: Updating files: 95% (2702/2844)
  default: Updating files: 95% (2722/2844)
  default: Updating files: 96% (2731/2844)
  default: Updating files: 97% (2759/2844)
  default: Updating files: 98% (2788/2844)
  default: Updating files: 99% (2816/2844)
  default: Updating files: 100% (2844/2844)
  default: Updating files: 100% (2844/2844), done.
  default: Warning: md5 hash checks are not available for nightly downloads.
  default: Warning: si-contact-form: Plugin not found.
  default: Warning: The 'si-contact-form' plugin could not be found.
  default: Error: No plugins installed.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
paaljoachimromdahl@Paals-MacBook-Pro vagrant-local %

@iandunn @tomjn

Otto42 commented 3 years ago

I don't know why it would be trying to install the si-contact-form plugin. We don't use it on wordpress.org.

tomjn commented 3 years ago

It may have been used in the distant past, few people have access to update the list of plugins used in the meta environment

iandunn commented 3 years ago

It's currently used on jobs.wordpress.net, but was retired from the w.org/plugins repo.

@coffee2code, do you want it keep it on production? If so, then maybe the Meta Environment should check out the latest tag via SVN?

few people have access to update the list of plugins used in the meta environment

I reached out to @tomjn, and he's agreed to help maintain this as a committer 🎉

I'd also be happy to merge a PR that implements whatever Scott thinks is best for Jobs, and grant commit access here to anyone who's already earned Meta commit, and anyone who develops a track record for PRs that are mostly commit-ready out of the box.

Having said that, I still think it's probably best to focus most of our energy on site-specific environments.

coffee2code commented 3 years ago

I would just remove any reference to the si-contact-form plugin from the meta environment.

It's of no critical importance to the jobs site, and its use should get supplanted with something else. In the meantime, its loss is not an issue.