Can not update doctrine-orm-module 3 in Laminas project - doctrine-orm

I am trying to update Doctrine Module in my Laminas project to version 3 using Composer but I am getting errors.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install doctrine/doctrine-orm-module 3.0.5
- Conclusion: don't install doctrine/doctrine-orm-module 3.0.4
- Conclusion: don't install doctrine/doctrine-orm-module 3.0.3
- Conclusion: don't install doctrine/doctrine-orm-module 3.0.2
- Conclusion: don't install doctrine/doctrine-orm-module 3.0.1
- Conclusion: remove doctrine/doctrine-module 2.1.10
- Installation request for doctrine/doctrine-orm-module ^3.0 -> satisfiable by doctrine/doctrine-orm-module[3.0.0, 3.0.1, 3.0.2,
3.0.3, 3.0.4, 3.0.5].
- Conclusion: don't install doctrine/doctrine-module 2.1.10
- doctrine/doctrine-orm-module 3.0.0 requires doctrine/doctrine-module ^4.0 -> satisfiable by doctrine/doctrine-module[4.0.0, 4.0.1, 4.0.2, 4.0.3].
- Can only install one of: doctrine/doctrine-module[4.0.0, 2.1.10].
- Can only install one of: doctrine/doctrine-module[4.0.1, 2.1.10].
- Can only install one of: doctrine/doctrine-module[4.0.2, 2.1.10].
- Can only install one of: doctrine/doctrine-module[4.0.3, 2.1.10].
- Installation request for doctrine/doctrine-module (locked at 2.1.10) -> satisfiable by doctrine/doctrine-module[2.1.10].
Installation failed, reverting ./composer.json to its original content.
Any ideas as to why doctrine-orm-module is not installing. I have tried uninstalling and re-installing doctrine-orm-module but with no luck.
Many thanks in advance.
Edit
composer.json
{
"name": "kryten/direct_sites",
"description": "Direct Sites",
"license": "",
"keywords": [
"framework",
"zf3",
"Ecommerce"
],
"homepage": "http://framework.zend.com/",
"require": {
"php": ">=7.3",
"laminas/laminas-component-installer": "^2.1",
"laminas/laminas-mvc": "^3.1",
"laminas/laminas-filter": "^2.9",
"laminas/laminas-crypt": "^3.3",
"laminas/laminas-mvc-plugin-flashmessenger": "^1.1",
"laminas/laminas-i18n": "^2.9",
"ocramius/proxy-manager": "^2.2",
"krytenuk/refresh-redirect": "^2.0",
"krytenuk/logger": "^2.0",
"krytenuk/recaptchav2": "^2.0",
"krytenuk/mailchimp": "^0.2.0",
"laminas/laminas-serializer": "^2.9",
"laminas/laminas-mvc-i18n": "^1.1",
"gedmo/doctrine-extensions": "^2.4",
"laminas/laminas-permissions-acl": "^2.7",
"laminas/laminas-navigation": "^2.9",
"laminas/laminas-cache": "^2.8",
"ocramius/package-versions": "^1.4",
"laminas/laminas-feed": "^2.12",
"symfony/filesystem": "^4.2",
"laminas/laminas-dependency-plugin": "^1.0",
"krytenuk/messenger": "^1.1",
"laminas/laminas-file": "^2.8",
"doctrine/doctrine-orm-module": "2.1"
},
"autoload": {
"psr-4": {
"Application\\": "module/Application/src/",
"Auth\\": "module/Auth/src/",
"Admin\\": "module/Admin/src/",
"Author\\": "module/Author/src/",
"User\\": "module/User/src/"
}
}
}
I am trying to run the command composer require doctrine/doctrine-orm-module and I get the response Using version ^3.0 for doctrine/doctrine-orm-module followed by the message above.

Try cleaning up the vendor/ directory as it might contain the too old version of doctrine/doctrine-module installed previously.
As another solution, I suggest you execute composer update and see if there are any errors.
Usually, in such cases the most common problem is that composer require ... does not upgrade the existing packages.

Related

Error while installing CFN-cli, Could not find a version that satisfies the requirement aws-sam-translator>=1.50.0

I am trying to setup my dev environment for cloudformation and while installing cfn-cli (coudformation ClI) I am getting below error. I am following official aws documentation. https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/what-is-cloudformation-cli.html
the error come while trying to install
pip3 install cloudformation-cli
Error
Could not find a version that satisfies the requirement aws-sam-translator>=1.50.0 (from cfn-lint>=0.43.0->cloudformation-cli)(from versions: 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.6.0, 1.6.1, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.13.1, 1.13.2, 1.14.0, 1.15.0, 1.15.1, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.19.1, 1.20.0, 1.20.1, 1.21.0, 1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.28.1, 1.29.0, 1.30.0, 1.30.1, 1.31.0, 1.32.0, 1.33.0, 1.34.0, 1.35.0, 1.36.0, 1.37.0, 1.38.0, 1.39.0, 1.40.0, 1.42.0) No matching distribution found for aws-sam-translator>=1.50.0 (from cfn-lint>=0.43.0->cloudformation-cli)

conda create environment command gives 'Found conflicts! Looking for incompatible packages.'

I installed miniconda via choco install miniconda3.
Creating a python3 environment works fine.
conda create --name envA python=3 --verbose
But creating a python2 environment has a problem.
conda create --name envB python=2 --verbose
Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working...
Found conflicts! Looking for incompatible packages.
failed
Traceback (most recent call last):
...
File "C:\Users\fred\miniconda3\lib\site-packages\conda\resolve.py", line 352, in find_conflicts
raise UnsatisfiableError(bad_deps, strict=strict_channel_priority)
conda.exceptions.UnsatisfiableError
#cel gets credit for this
Switching to mamba provided better diagnostics.
mamba create -n foo python=2
Looking for: ['python=2']
conda-forge/win-64 Using cache
conda-forge/noarch Using cache
Encountered problems while solving:
- nothing provides vc 9.* needed by python-2.7.12-0
Then use mamba to find vc.
mamba search vc
# Name Version Build Channel
vc 14.1 h21ff451_1 conda-forge
vc 14.1 h6d1b3ff_2 conda-forge
...
The vc v9 can be found in the defaults channel.
mamba search 'vc[channel=defaults]'
# Name Version Build Channel
vc 9 h2eaa2aa_6 pkgs/main
...
Updating the .condarc with the defaults channel, corrected the problem.
channels:
- conda-forge
- defaults
channel_priority: disabled
As a final note, should someone else find themselves in this situation...
The ~/.condarc got changed (dropping the defaults channel) as part of installing mambaforge.

TypeError: Cannot read property 'serve:before' of undefined on Ionic CLI 2.2.1 + Gulp 4

I am developing a Web Application that have a lot of legacy dependencies.
On the trial of updating some packages, I updated the gulp/gulpfile.js and tinkered then to run. Gulp was on version 3.5 and now is on 4.0.
By the way, the error thrown in the terminal by running : ionic serve --address localhost --nobrowser is :
Error: spawn cordova EACCES
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
Mind letting us know? https://github.com/driftyco/ionic-cli/issues
******************************************************
Dependency warning - for the CLI to run correctly,
it is highly recommended to install/upgrade the following:
Please update your Cordova CLI to version >=4.2.0 `npm install -g cordova`
******************************************************
TypeError: Cannot read property 'serve:before' of undefined
at Object.runWithGulp (/usr/lib/node_modules/ionic/lib/cli.js:237:17)
at Object.runr (/usr/lib/node_modules/ionic/lib/cli.js:194:18)
at /usr/lib/node_modules/ionic/lib/cli.js:54:9
at _fulfilled (/usr/lib/node_modules/ionic/node_modules/q/q.js:787:54)
at /usr/lib/node_modules/ionic/node_modules/q/q.js:816:30
at Promise.promise.promiseDispatch (/usr/lib/node_modules/ionic/node_modules/q/q.js:749:13)
at /usr/lib/node_modules/ionic/node_modules/q/q.js:557:44
at flush (/usr/lib/node_modules/ionic/node_modules/q/q.js:108:17)
at process._tickCallback (internal/process/next_tick.js:61:11)
Cannot read property 'serve:before' of undefined (CLI v2.2.1)
Your system information:
Cordova CLI: undefined
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 5.4
Node Version: v10.16.3
Xcode version: Not installed
Then, some patch of the gulpfile.js :
gulp.task('build', gulp.series('bundle', 'copyTask', 'revTask', 'revReplaceTask'));
gulp.task('default', gulp.series('sassTask', 'cleanTask', 'build', 'watchTask'));
gulp.task('serve:before', gulp.series('cleanTask', 'watchTask', 'build'));
Before the tinkering, gulp.task('serve:before' [...]) functioned well. I guess it is related with the Ionic 2.2.1 CLI.
If someone could help me by a hint or an advice for mismatching the problem, I would be glad.
This happened to me while I upgraded Node to v12 which forced me to upgrade Gulp to v4.
The solution that worked for me is:
Go to npm\node_modules\ionic\lib\cli.js (Wherever it's located).
Change the following lines as such in cli.js:
237: if (true || gulp.tasks[beforeHook]) {
257: if (true || gulp.tasks[afterHook]) {
270: return Q.nfcall(null/*gulp.start.bind(gulp)*/, hookName)
Basically, the reason is that gulp.tasks and gulp.start don't exist in Gulp v4.
By putting true || in the first occurrences, gulp.tasks won't run and by putting null in the last occurrence, the gulp.start won't run.
I hope this helps the next people that encounter this problem.

Upgrade Expo react-native-svg dependency version

My Expo project requires the latest version of react-native-svg library to render my SVGs correctly. Currently it's version 9.3.5
From package-json.lock, I see that my current Expo SDK 32 has version 8.0.10 listed.
"dependencies": {
"react-native-svg": {
"version": "8.0.10",
"resolved": "https://registry.npmjs.org/react-native-svg/-/react-native-svg-8.0.10.tgz",
"integrity": "sha512-gsG5GUdvlox67+ohLnq3tZSqiYBmz4M5lKKeUfnJZ8EPrMMS5ZgaVj7Zcccee1VvINS5xQaoenUJdha/GEo34w==",
"requires": {
"color": "^2.0.1",
"lodash": "^4.16.6",
"pegjs": "^0.10.0"
}
}
}
I have tried just installing latest react-native-svg alongside Expo by using
npm install react-native-svg#9.3.5
However, when running the app I get an error:
Tried to register two views with the same name RNSVGRect
So how can I force Expo to use the latest version? I don't see any react-native-svg dependencies anywhere and changing the package-lock.json directly doesn't seem like a good idea.
Short answer to my question is: you can't. At least not without some ugly hacks that are more trouble than they're worth.
The good news is that SDK 33 now comes with "react-native-svg": "~9.4.0" as a dependency and this is almost the latest version as of this writing.

Composer fails to update with zfc-user-doctrine-orm

i have the following composer.json
{
"name": "zendframework/skeleton-application",
"description": "Skeleton Application for ZF2",
"license": "BSD-3-Clause",
"keywords": [
"framework",
"zf2"
],
"homepage": "http://framework.zend.com/",
"require": {
"php": ">=5.3.3",
"zendframework/zendframework": "2.2.*",
"doctrine/doctrine-orm-module": "*",
"bjyoungblood/bjy-authorize": "1.2.*",
"zf-commons/zfc-user": "dev-master",
"zendframework/zend-developer-tools": "*",
"zendframework/zftool": "dev-master",
"swiftmailer/swiftmailer" : "*",
"mwillbanks/zfc-twitter-bootstrap": "*"
}
}
after I added the require zf-commons/zfc-user-doctrine-orm, Composer was unable to perform the command composer update giving a large error message:
composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for zf-commons/zfc-user dev-master -> satisfiable by
zf-commons/zfc-user[dev-master].
- Conclusion: don't install zf-commons/zfc-user 0.1.2
- Conclusion: remove zendframework/zendframework 2.2.0
- zf-commons/zfc-user 0.0.1 requires zendframework/zendframework 2.0.* -> sa
tisfiable by zendframework/zendframework[2.0.0, 2.0.0rc1, 2.0.0rc2, 2.0.0rc3, 2.
0.0rc4, 2.0.0rc5, 2.0.0rc6, 2.0.0rc7, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6,
2.0.7, 2.0.8].
- zf-commons/zfc-user-doctrine-orm 0.0.1 requires zendframework/zendframewor
k 2.0.* -> satisfiable by zendframework/zendframework[2.0.0, 2.0.0rc1, 2.0.0rc2,
2.0.0rc3, 2.0.0rc4, 2.0.0rc5, 2.0.0rc6, 2.0.0rc7, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2
.0.5, 2.0.6, 2.0.7, 2.0.8].
- zf-commons/zfc-user 0.1.0 requires zendframework/zendframework 2.1.* -> sa
tisfiable by zendframework/zendframework[2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.
5].
- zf-commons/zfc-user 0.1.1 requires zendframework/zend-view 2.1.* -> satisf
iable by zendframework/zendframework[2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5],
zendframework/zend-view[2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5].
- zf-commons/zfc-user-doctrine-orm 0.1.0 requires zendframework/zendframewor
k 2.1.* -> satisfiable by zendframework/zendframework[2.1.0, 2.1.1, 2.1.2, 2.1.3
, 2.1.4, 2.1.5].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc1].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc2].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc3].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc4].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc5].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc6].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.0rc7].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.1].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.2].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.3].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.4].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.5].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.6].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.7].
- Can only install one of: zendframework/zendframework[2.2.0, 2.0.8].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.0].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.1].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.2].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.3].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.4].
- Can only install one of: zendframework/zendframework[2.2.0, 2.1.5].
- don't install zendframework/zend-view 2.1.0|don't install zendframework/ze
ndframework 2.2.0
- don't install zendframework/zend-view 2.1.1|don't install zendframework/ze
ndframework 2.2.0
- don't install zendframework/zend-view 2.1.2|don't install zendframework/ze
ndframework 2.2.0
- don't install zendframework/zend-view 2.1.3|don't install zendframework/ze
ndframework 2.2.0
- don't install zendframework/zend-view 2.1.4|don't install zendframework/ze
ndframework 2.2.0
- don't install zendframework/zend-view 2.1.5|don't install zendframework/ze
ndframework 2.2.0
- Installation request for zendframework/zendframework == 2.2.0.0 -> satisfi
able by zendframework/zendframework[2.2.0].
- zf-commons/zfc-user-doctrine-orm 0.1.1 requires zf-commons/zfc-user 0.* ->
satisfiable by zf-commons/zfc-user[0.0.1, 0.1.0, 0.1.1, 0.1.2].
- Installation request for zf-commons/zfc-user-doctrine-orm * -> satisfiable
by zf-commons/zfc-user-doctrine-orm[0.0.1, 0.1.0, 0.1.1].
How do I fix this error message?
Your composer file works fine for me. This is possibly caused because you're using the dev-master of zf-commons/zfc-user rather than a tagged version number.
Because of this Composer is using an old version that exists in your Composer cache, rather than downloading a new version. You can tell it's using an old version as Composer is referring to zf-commons/zfc-user 0.0.1 but the current version is 0.1.2. The old version of zf-commons/zfc-user has a dependency on and old version of zendframework/zendframework which is clashing with the other modules that require a newer version.
If you replace:
"zf-commons/zfc-user": "dev-master",
with:
"zf-commons/zfc-user": "~0.1.2",
It should force Composer to download the 0.1.2 or newer version of that module.
In 2015, this work fine for me
"zf-commons/zfc-user": "1.*",
"zf-commons/zfc-user-doctrine-orm": "^1.0"
I had the same problem, so i changed some dependencies with dev-master to their last versions and it worked. My composer.json file:
{
"name": "zendframework/skeleton-application",
"description": "Skeleton Application for ZF2",
"license": "BSD-3-Clause",
"keywords": [
"framework",
"zf2"
],
"homepage": "http://framework.zend.com/",
"require": {
"php": ">=5.5",
"zendframework/zendframework": "~2.5",
"zendframework/zftool": "dev-master",
"doctrine/doctrine-orm-module": "^0.10.0",
"zendframework/zend-developer-tools": "dev-master",
"bjyoungblood/bjy-profiler": "dev-master",
"doctrine/migrations": "^1.4",
"doctrine/orm": "^2.5",
"rradutzu/zend2-doctrine-dynamic-db": "^0.0.4",
"zf-commons/zfc-rbac" : "~2.4",
"zf-commons/zfc-user": "1.4.4",
"zf-commons/zfc-user-doctrine-orm": "^1.0.1"
}
}