Kirk Madera

I also encountered on `algolia/algoliasearch-magento`. This only occurs when using the "copy" strategy. The symlink strategy works as expected. Trace: ``` Analyzed 93 packages to resolve dependencies Analyzed 121 rules...

This occurs after deploying via the symlink strategy, then deploying later via the copy strategy. `magento-force: true` must be enabled in order for this to get far enough to hit...

The fix for this may be a built in redeploy script. We have a bash script that we use that looks something like this: ``` packageInfo=$(composer info); cp composer.json composer.json.bak;...

I figured out that it happens to work, so long as there are no class naming conflicts. I am only using this as a temporary solution to proxy a middleware...

Definitely makes sense to make a change like this in a major version change. This is functional at the moment with sharing the same namespace because there are not any...

I also ran into this. As a temporary fix, you can apply this: ``` file { '/usr/lib64/openvpn/plugin/lib/openvpn-auth-pam.so': ensure => link, target => '/usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so', require => File['/usr/lib64/openvpn/plugin/lib'], } ```

After working with this more, I ran into an issue with VirtualBox not being able to create symlinks. I talked to Mat (@aepod) on our team and realized that I...

I figured out that I had to run a couple of additional commands. ``` cd /vagrant/data/magento2; git checkout master; # develop is the default branch and I wanted to work...

I added enough notes for this to be sufficient for Windows users. I think this is safe to pull in.

Fixes #70