magneto 2 installtion error on composer install - installation

While installing magento 2.4.4 i got an issue like
Install of laminas/laminas-dependency-plugin failed
[RuntimeException]
Failed to execute git checkout '73cfb63ddca9d6bfedad5e0a038f6d55063975a3' -- && git reset --hard '73cfb63ddca9d6bfedad5e0a038f6d55063975a3' --
fatal: reference is not a tree: 73cfb63ddca9d6bfedad5e0a038f6d55063975a3
anybody faced this issue,or anyone give a suggestion to fix this issue.
Thanks in advance

I encountered the same issue. I managed to continue the 'composer install' command by executing 'composer require laminas/laminas-dependency-plugin'. It started installing the requested version defined in my composer.lock. So I don't understand what the problem is/was.

Related

Composer always fails to install symfony/var-dumper

I'm trying to install the latest version of Laravel 8 on the latest version of Homestead. When I run composer install or composer update, installation of symfony/var-dumper always fails:
Installing symfony/var-dumper (v5.2.6): Extracting archive
Install of symfony/var-dumper failed
[ErrorException]
file_get_contents(/home/vagrant/code/vendor/symfony/var-dumper/Resources/bin/var-dump-server):
Failed to open stream: No such file or directory
Despite the error exception, the file /vendor/symfony/var-dumper/Resources/bin/var-dump-server does exist.
Things I've tried:
Deleting the lock file and re-running composer update
Manually specifying specific versions of var-dumper, e.g. composer require symfony/var-dumper:5.2.0
I always get the same errors.
Remove /vendor folder, then run:
composer update -v
This turned out to be a compatibility issue with Composer 2.x. I downgraded to the 1.x channel using composer self-update --1, then ran composer install again, and the installation succeeded.
Composer version 2.2.4 2022-01-08 12:30:42
and
symfony/var-dumper v5.4.3
is working just fine

ORO-CRM Composer Install - Failed to download composer/composer

For Install OroCRM in windows i have followed -> https://stackoverflow.com/a/40929643/8416476 after successful the command git clone -b 1.9.0 https://github.com/orocrm/platform-application.git orocrm then i try to run composer install --prefer-dist --no-dev Here i am getting error.
Installing composer/composer (1.0.0-p1): Downloading (failed) Failed to download composer/composer from dist: The
"https://api.github.com/repos/orocrm/composer/zipball/833ce984264204e7d6576ab082660105c7d8f04c"
file could not be downloaded (HTTP/1.1 404 Not Found)
How can i solve the issue.
Note : OroCRM in Windows
Install composer globally using https://getcomposer.org/Composer-Setup.exe
Then just run composer install --prefer-dist --no-dev from within application folder. This error is very odd and why are you trying to download 1.9.0 version? It is copy paste error or you specifically need this one?
Try Linux platform with Xampp for better convenient. refer https://oroinc.com/orocrm/doc/current/system-requirements#system-requirements

Composer update - RuntimeException

After installing Composer I try to do a composer update which tells me this:
[Symfony\Component\Process\Exception\RuntimeException]
The process has been signaled with signal "11".
I'm running OSX 10.6.8 (old, I know). What causes this error?
composer self-update ran just fine.
signal 11 is a segmentation fault. I guess there is a problem with your version of php.
can you show us the output of php --version ? and can you upgrade it if it's not the latest version ?
I had The process has been signaled with signal "6". error and I had to run below commands:
$brew upgrade subversion
$brew link --overwrite subversion
and the issue went! :)
brew upgrade subversion
brew link --overwrite subversion
The above commands solves errors related to Symphony when running
composer global update

pod install command shows error

I'm trying to install a pod file with the following contents
>platform :ios, '7.0'
>pod 'Brightcove-Player-SDK', '~> 4.1.5'
But when i used the command 'pod install' in Terminal, i got the following error.
[!] Unable to locate the executable `git`
/Library/Ruby/Gems/1.8/gems/claide-0.4.0/lib/claide/command.rb:217:in `run':undefined method `verbose?' for nil:NilClass (NoMethodError)
from /Library/Ruby/Gems/1.8/gems/cocoapods-0.29.0/lib/cocoapods/command.rb:51:in `run'
from /Library/Ruby/Gems/1.8/gems/cocoapods-0.29.0/bin/pod:24
from /usr/bin/pod:23:in `load'
from /usr/bin/pod:23
Could someone please explain what the problem is?
I checked this solution on https://stackoverflow.com/a/18356219/3150731 according to that, installing github should have fixed the problem but, that also did not work in my case.
Thanks in advance
The problems where not with the downloading i downloaded everything and installed cocoa pods but was not able to install my pod file in my project workspace as i didn't create an username and email for the git. After doing that i was able to install my pod file
following are the codes to set your username and emailid for your git using terminal
git config --global user.name "Firstname Lastname"
git config --global user.email "your_email#youremail.com"
The ruby script is complaining that git cannot be found. To fix that, you have got to install git-scm. Make sure to integrate it with terminal..
First, you need to have installed Git in your computer, download from here:
http://git-scm.com/download/mac
One you have it, run next command:
sudo gem install cocoapods
And finally, you can install dependencies in your proyect:
pod install

Swiftmailer Error Composer Install

i am installing composer dependencies by 'composer install'.
it download bunch of packages but after swiftmailer it gives me error
[UnexpectedValueException]
'C:\Users\DELL\Downloads\laravel-4\vendor/swiftmailer/swiftmailer/72e34d......54c82f.1' is not a zip archive.
what does it mean?
For me this problem happened due to the order composer was installing the files.
The work around that worked for me was to go into \vendor\composer\autoload_real.php and comment out the following line
require $vendorDir . '/swiftmailer/swiftmailer/lib/swift_required.php';
and then run composer again
Running composer install with the --prefer-source option, fixed this problem for me.

Resources