./blt.sh blt:update error - Update seems broken on Windows & Mac about blt

[grasmash]

I would guess that this is a file permissions issue. I would suggest running chmod or chown on your project to ensure that you have the permission to overwrite files like blt.sh.

[justinlevi]

I ended up starting from scratch so I'm not sure what the issue ended up being but seems like it's now working as expected.

Update: spoke too soon. I'm running that command within drupal-vm and the root directory have 777 permissions as does blt.sh

user:group = vagrant:vagrant

[justinlevi]

I tried again on my mac at home today, got some different permissions errors, set executable on all of the scripts, and got a bit further but now I'm seeing the update fail at this line:

svn: E175002: Unable to connect to a repository at URL 'https://github.com/acquia/blt/branches/8.x/template/blt.sh'
svn: E175002: OPTIONS of 'https://github.com/acquia/blt/branches/8.x/template/blt.sh': Could not read status line: connection was closed by server (https://github.com)

$sudo ./blt.sh blt:update

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
Buildfile: /Users/justinwinter/Sites/data/build/custom/phing/build.xml
 [property] Loading /Users/justinwinter/Sites/data/project.yml
 [property] Loading /Users/justinwinter/Sites/data/build/core/phing/build.yml
     [copy] default.local.settings.php omitted, is up to date
     [echo] Executing commands against multisite "default"
     [echo] Using settings file /Users/justinwinter/Sites/data/docroot/sites/default/settings/local.settings.php
 [property] Loading /Users/justinwinter/Sites/data/build/custom/phing/build.yml

project > blt:update:

[echo] You may be prompted to trust GitHub's SSL certification and to enter your GitHub password.
[echo] If you have two factor authentication enabled for GitHub, you must use an access token in lieu of a password.
[echo] GitHub access tokens can be generated here: https://github.com/settings/tokens

Press any key to continue 
Copying down upstream changes to the BLT template.
Error validating server certificate for 'https://github.com:443':
- The certificate is not issued by a trusted authority. Use the
  fingerprint to validate the certificate manually!
  Certificate information:
- Hostname: github.com
- Valid: from Thu, 10 Mar 2016 00:00:00 GMT until Thu, 17 May 2018 12:00:00 GMT
- Issuer: www.digicert.com, DigiCert Inc, US
- Fingerprint: d7:9f:07:61:10:b3:92:93:e3:49:ac:89:84:5b:03:80:c1:9e:2f:8b
  (R)eject, accept (t)emporarily or accept (p)ermanently? t
  svn: E175002: Unable to connect to a repository at URL 'https://github.com/acquia/blt/branches/8.x/template/blt.sh'
  svn: E175002: OPTIONS of 'https://github.com/acquia/blt/branches/8.x/template/blt.sh': Could not read status line: connection was closed by server (https://github.com)

BUILD FAILED
/Users/justinwinter/Sites/data/build/core/phing/tasks/blt.xml:9:121: Task exited with code 1

Total time: 20.7133 seconds

[justinlevi]

On the update-scaffold, is this path supposed to be "branches"? If I try to go to the generated URL, I get a 404.
https://github.com/acquia/blt/branches/8.x/template/scripts/blt/update-scaffold#L35

This does however resolve.
https://github.com/acquia/blt/blob/8.x/template/scripts/blt/update-scaffold#L35

[grasmash]

@justinlevi The branches URL is correct. It works via svn but does not seem to work over port 80 via a web browser.

Are you certain that you've successfully authenticated with GitHub?

[justinlevi]

@grasmash Yes, I've definitely successfully authenticated with github.

vagrant@data:/var/www/data$ ssh -T [email protected]
The authenticity of host 'github.com (192.30.252.123)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,192.30.252.123' (RSA) to the list of known hosts.
Hi justinlevi! You've successfully authenticated, but GitHub does not provide shell access.
vagrant@data:/var/www/data$

[justinlevi]

I've also tried running this from my host mac as well as within an ssh session on the VM with Mac and Windows

[grasmash]

@justinlevi What do you get when you run svn export https://github.com/acquia/blt/branches/8.x/template/README.md README.md --force ?

[justinlevi]

From within the Drupal-VM on my mac, I get this:

vagrant@data:/var/www/data$ svn export https://github.com/acquia/blt/branches/8.x/template/README.md README.md --force
A    README.md
Export complete.
vagrant@data:/var/www/data$ 

From my mac host in the same directory:

$svn export https://github.com/acquia/blt/branches/8.x/template/README.md README.md --force
Error validating server certificate for 'https://github.com:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: github.com
 - Valid: from Thu, 10 Mar 2016 00:00:00 GMT until Thu, 17 May 2018 12:00:00 GMT
 - Issuer: www.digicert.com, DigiCert Inc, US
 - Fingerprint: d7:9f:07:61:10:b3:92:93:e3:49:ac:89:84:5b:03:80:c1:9e:2f:8b
(R)eject, accept (t)emporarily or accept (p)ermanently? t
A    README.md
Export complete.

Running the following, still results in the same Permission denied error as before on my host as well as within the VM.

$ ./blt.sh blt:update

[grasmash]

@justinlevi That's interesting. svn export https://github.com/acquia/blt/branches/8.x/template/README.md README.md --force works for you. The blt:update script essentially just runs that command in a loop, replacing the value of README.md with other various filepaths.

Odd. I can only imagine a few scenarios that would cause this:

1. When run via blt:update the ownership or permissions of a related file or library is causing a problem.
2. Variable replacement the bash script is not working as expected. Perhaps encapsulating the svn command arguments in quotations would solve this...

I'd debug this by stripping down the update-scaffold.sh script to just:

GIT_ROOT=$(git rev-parse --show-toplevel)
cd $GIT_ROOT
svn export https://github.com/acquia/blt/branches/8.x/template/blt.sh blt.sh --force

If that works, try:

GIT_ROOT=$(git rev-parse --show-toplevel)
BLT_BRANCH=8.x
# Upstream directories to pull. These will be prefixed with "template/".
BLT_DIRS=(
  "blt.sh"
)
# Move into repository root.
cd $GIT_ROOT
# Iteratively pull down upstream directories.
for i in "${BLT_DIRS[@]}"
  do
    svn export https://github.com/acquia/blt/branches/$BLT_BRANCH/template/$i $i --force
done

And if that works... then I have no idea ;)

[justinlevi]

@grasmash First of all, thanks a ton for sticking it out with me on this one. Sure enough I was able to go through each of your commands above without any issue.

Yet, running /blt.sh blt:update still throws that error.

On a whim, I decided to try to run blt:update on a completely fresh install, seeing that with the behat tests, and sure enough it worked??!!

I'm wondering if my issues were related to one of two things:

1. I was originally working off an older version of Bolt, and manually merged the latest commits to my files, before running the command. So maybe I missed a file or something...
2. I was also running my own instance of drupal-vm within blted8/box so perhaps this was causing issues somehow.

This has all been great though as it's forced me to dig a bit deeper into everything so again, thanks for your time.

[justinlevi]

Just adding a bit more to this for reference. This issue here seems very similar
Varying-Vagrant-Vagrants/VVV#58

Seems that it could be a Windows Vagrant NFS issue and I couldn't find a fix anywhere unfortunately.