0
Good afternoon to all
I am trying to install a package by Composer on the Laravel, and by typing "Composer require Bert/ldap-Authenticator" it does the installation, but produces the following result:
Using version ^0.2.4 for berg/ldap-authenticator
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies <including require-dev)
- Removing doctrine/dbal (v2.5.1)
- Removing phpspec/php-diff (v1.0.2)
- Removing doctrine/common (v2.5.0)
- Removing doctrine/annotations (v1.2.6)
- Removing doctrine/cache (v1.4.1)
- Removing doctrine/collections (v1.3.0)
- Removing doctrine/lexer (v1.0.1)
- Removing spekkionu/laravel-zend-acl (2.0.2)
- Removing zendframework/zend-permissions-acl (2.3.9)
- Removing rmccue/requests (v1.6.1)
- Removing guzzlehttp/guzzle (6.0.2)
- Removing illuminate/html (v5.0.0)
- Removing guzzlehttp/psr7 (1.1.0)
- Removing psr/http-message (1.0)
- Removing guzzlehttp/promises (1.0.1)
- Removing danielstjules/stringy (1.10.0)
- Removing phpspec/phpspec (2.2.1)
- Removing xethron/migrations-generator (dev-15 e5e86ef)
- Removing way/generators (dev-feature/laravel-five-stable)
[RuntimeException]
Failed to execute git status --porcelain --untracked-files=no
'git' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
require [--dev] [--prefer-source] [--prefer-dist] [--no-plugins] [--no-progress] [--no-update] [--update-no-dev] [--update-with-dependencies] [--ignore-platform-regs] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--] [<packages>]...
Then I entered the system and everything stopped working. My luck that when I went to do the update I had made a backup just before.
What do you think is going on? I don’t believe it’s any conflict with the package I’m installing.
When installing the package, Composer automatically updated Composer.json and Composer.lock (kicking). Some package has been updated on this, in the second line it informs
./composer.json has been updatedtries to upgrade from the backup only to Composer.lock to see if this is the case– Renato Tavares
It was no. I climbed only the Composer.lock, but still it had not been handcuffed
– Isaias Lima
It’s strange, but the Composer never removed these things from the previous facility!
– Isaias Lima