You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running dev-master via composer. During testing of the fix for #164 each time I did a composer update, composer said that phpdox (vendor/bin) had been changed and interactively asked what I wanted to do with the changes. I didn't modify anything in vendor.
For automated builds through jenkins, I could destroy my workspace and the install would succeed, just during the upgrade path from one commit to another on dev-master was when I saw this behavior.
Sorry I don't have any other data or logs available at this time.
The text was updated successfully, but these errors were encountered:
This seems to have been triggered by the fact the file composer/bin/phpdox has been committed without the executable bit set and composer automagically fixing that so it can be used as intended.
Instead of throwing an error right away of course this leads to a modified file causing trouble upon update.
I corrected the permissions with commit 061847a, which fixed the issue for me.
To get the fix run composer update and simply discard the changes on this file, it shouldn't ask on further update runs.
I'm running dev-master via composer. During testing of the fix for #164 each time I did a composer update, composer said that phpdox (vendor/bin) had been changed and interactively asked what I wanted to do with the changes. I didn't modify anything in vendor.
For automated builds through jenkins, I could destroy my workspace and the install would succeed, just during the upgrade path from one commit to another on dev-master was when I saw this behavior.
Sorry I don't have any other data or logs available at this time.
The text was updated successfully, but these errors were encountered: