I'm trying to install Doctrine Migrations in a new Symfony 4.1 project.
I just created this proejct with composer create-project specifying the website skeleton.
From the documentation (http://symfony.com/doc/master/bundles/DoctrineMigrationsBundle/index.html):
$ composer require doctrine/doctrine-migrations-bundle "^2.0"
This fails with these errors:
Your requirements could not be resolved to an installable set of
packages.
Problem 1
- The requested package doctrine/doctrine-migrations-bundle ^2.0 is satisfiable by doctrine/doctrine-migrations-bundle[2.0.x-dev,
v2.0.0-alpha1, v2.0.0-beta1] but these conflict with your requirements
or minimum-stability.
Problem 2
- symfony/orm-pack v1.0.5 requires doctrine/doctrine-migrations-bundle ^1.3 -> satisfiable by
doctrine/doctrine-migrations-bundle[1.3.x-dev, v1.3.0, v1.3.1] but
these conflict with your requirements or minimum-stability.
- symfony/orm-pack v1.0.5 requires doctrine/doctrine-migrations-bundle ^1.3 -> satisfiable by
doctrine/doctrine-migrations-bundle[1.3.x-dev, v1.3.0, v1.3.1] but
these conflict with your requirements or minimum-stability.
- symfony/orm-pack v1.0.5 requires doctrine/doctrine-migrations-bundle ^1.3 -> satisfiable by
doctrine/doctrine-migrations-bundle[1.3.x-dev, v1.3.0, v1.3.1] but
these conflict with your requirements or minimum-stability.
- Installation request for symfony/orm-pack (locked at v1.0.5, required as *) -> satisfiable by symfony/orm-pack[v1.0.5].
I am at a loss.
I ran into the same issue and here's what I did to get it working:
composer unpack orm
composer require doctrine/migrations "v2.0.0-beta1"
composer require doctrine/doctrine-migrations-bundle "v2.0.0-alpha1"
As I understand it, the orm-pack was required to be unpacked so that migrations can be upgraded to match doctrine-migrations-bundle's version.
Hope it works for you too.
I've tried steady_daddy's approach but it didn't work for me. What actually worked for me was:
composer unpack orm
composer remove doctrine/doctrine-migrations-bundle
composer require doctrine/doctrine-migrations-bundle "v2.0.0-beta2"
Probably you also have to set the "minimum-stability" option to "beta" in your composer.json file.
More information about unpacking the Symfony packs you can find at http://fabien.potencier.org/symfony4-unpack-the-packs.html
Related
I'm trying to build an IOS app using EAS service expo, but when I try to build, there is an error while install pods on build details expo. And this is the error.
Unable to find a specification for `UMTaskManagerInterface` depended upon by `EXLocation`
I try to install pod by npm i pod-install but still get error. Is this because I build on Windows, or what should I do to fix this error? I also try to find the error in GitHub forum, and it's say adding path pod in ios/Podfile which I can't find it in my expo project. Where is ios/Podfile file located in expo project?
This is the full error
Installing pods
Using Expo modules
Auto-linking React Native modules for target `MMS`: RNCAsyncStorage, RNCCheckbox, RNDateTimePicker, RNGestureHandler, RNPermissions, RNReanimated, RNScreens, react-native-safe-area-context, and react-native-viewpager
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `RCT-Folly` from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Adding spec repo `trunk` with CDN `https://cdn.cocoapods.org/`
CocoaPods 1.11.2 is available.
To update use: `sudo gem install cocoapods`
For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.11.2
[!] Unable to find a specification for `UMTaskManagerInterface` depended upon by `EXLocation`
You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* mistyped the name or version.
* not added the source repo that hosts the Podspec to your Podfile.
[stderr] [!] `<PBXResourcesBuildPhase UUID=`13B07F8E1A680F5B00A75B9A`>` attempted to initialize an object with an unknown UUID. `2EE81B3C866A4A13B6460929` for attribute: `files`. This can be the result of a merge and the unknown UUID is being discarded.
pod exited with non-zero code: 1
Edit*
i try using expo build:ios-> archive is working perfectly. why using eas build -p ios i got that error?
I`m trying to install Scrapy from PyPi using below command.
gcloud composer environments update $(AIRFLOW_ENVIRONMENT_NAME) \
--update-pypi-packages-from-file requirements.txt \
--location $(AIRFLOW_LOCATION)
requirements.txt is like this.
google-api-python-client==1.7.*
google-cloud-datastore==1.7.*
Scrapy==2.0.0
After running gcloud command, It will cause an invalid argument but it runs successfully in the local environment.
gcloud composer environments update xxxx \
--update-pypi-packages-from-file requirements.txt \
--location asia-northeast1
ERROR: (gcloud.composer.environments.update) INVALID_ARGUMENT: Found 1 problem:
1) Error validating key Scrapy. PyPi dependency name is not formatted properly. It must be lowercase and follow the format of 'identifier' specified in PEP-508.
Is there any way to install?
As the previous answer stated, the error that you are receiving now is quite clear and it's caused by the wrong formatting of the dependency. It should be scrapy==2.0.0 instead of Scrapy==2.0.0 inside the requirements.txt.
I would like to add that to avoid the installation error when you fix the formatting, you should add one more dependency to your list and that is attrs==19.2.0. I was able to install your requirements to my environment by specifying the following list:
google-api-python-client==1.7.*
google-cloud-datastore==1.7.*
scrapy==2.0.0
attrs==19.2.0
Even though you adjust package name in requirements.txt file according to PEP-508 document prerequisites, formatting certan package name in lowercase layout scrapy==2.0.0, the issue most probably will remain the same and updating process will stuck with the error:
Failed to install PyPI packages
Generally, this kind of error appears then the source PyPI package has some external dependencies or this package is sensitive on some system-level libraries that GCP Composer doesn't support.
In this case a vendor recommends two ways either using KubernetesPodOperator to build own custom image and use it in particular Kubernetes Pod or deploy PyPi package as a local Python library, uploading shared object libraries for the PyPI dependency to Airflow /plugins directory, find more info here.
This is similar to an unanswered question from a year ago. Supposedly I have an update for drupal/core:
$ composer outdated "drupal/*"
drupal/core 8.6.10 8.6.12 Drupal is an open source content ...
But when I run update ...
$ composer update drupal/core --with-dependencies
Dependency "asm89/stack-cors" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "composer/semver" is also a root requirement, but is not explicitly whitelisted. Ignoring.
[ ... ]
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Package phpunit/phpunit-mock-objects is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
> Drupal\Core\Composer\Composer::preAutoloadDump
> Drupal\Core\Composer\Composer::ensureHtaccess
I'm trying to follow the instructions to update drupal 8 via composer found here: https://www.drupal.org/docs/8/update/update-core-via-composer
I had the same issue today with updating Drupal and the following process helped me solve the issue.
Run the composer update command using the specific version you are trying to update to. In this instance it would be composer require drupal/core:8.6.12 --update-with-dependencies If there is an issue blocking the update this should show you a list of problems. in my case I tried to update to version 8.6.11 and it output the following.
Problem 1
. Installation request for drupal/core 8.6.11 -> satisfiable by
drupal/core[8.6.11].
. Can only install one of: twig/twig[1.x-dev, v1.35.3].
. Can only install one of: twig/twig[v1.35.3, 1.x-dev].
. Can only install one of: twig/twig[1.x-dev, v1.35.3].
. drupal/core 8.6.11 requires twig/twig ^1.38.2 -> satisfiable by
twig/twig[1.x-dev, v1.38.2].
. Conclusion: don't install twig/twig v1.38.2
. Installation request for twig/twig (locked at v1.35.3, required as
^1.35.0) -> satisfiable by twig/twig[v1.35.3].
If there is no problem listed try clearing the composer cache composer clearcache and then try the update command again.
you can also try running the why-not composer command to see if that highlights any issues composer why-not drupal/core:8.6.12
In my case the issue was that the twig component required for 8.6.12 was v1.38.2 but was capped at a lower version 1.35 in the composer file. I used the following command to update the twig version and that allowed me to update to Drupal 8.6.12 using my normal update process.
composer require twig/twig:1.35.2
I hope this helps.
I'm following this guide to "Update core via Composer" and I have my backups. The document says to run
composer update drupal/core --with-dependencies
When I do, I get:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
> Drupal\Core\Composer\Composer::preAutoloadDump
> Drupal\Core\Composer\Composer::ensureHtaccess
drush core-status says I'm on version 8.4.3, so I expected the composer update command to move me to 8.4.5.
Later the document says to "Review the status report page for errors" and the only error listed is that I need to be on version 8.4.5
There must be something missing from the update documentation, and I can't figure out what it is.
Edit: Thanks Robb Davis, I tried:
rm -rf vendor
rm composer.lock
composer update drupal/core --with-dependencies
That gave me no change -- leaving me with an 8.4.3 installation.
I tried composer require drupal/core:8.5 which gave me:
$ composer require drupal/core:8.5
./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 drupal/drupal dev-master -> satisfiable by drupal/drupal[dev-master].
- don't install drupal/core 8.5.0|remove drupal/drupal dev-master
- Installation request for drupal/core 8.5 -> satisfiable by drupal/core[8.5.0].
Installation failed, reverting ./composer.json to its original content.
Nothing in that message makes any sense to me. So I'm still lost.
I was trying to update 8.5 to 8.6. Dumping the core and vendor folders in addition to the composer.lock file did not work for me.
I was able to resolve this issue by removing the core/composer.json line from the merge-plugin include array and running composer update drupal/core --with-dependencies.
My merge-plugin key in the composer.json file in the docroot looks like:
"merge-plugin": {
"include": [],
"recurse": true,
"replace": false,
"merge-extra": false
}
yes this is kind of foobar. There is a blog post about it here:
https://orkjern.com/updating-to-drupal-85-with-composer
The solution in the blog didn't work for me but a solution in the comments did:
Delete your vendors directory
Delete your .lock file
Run composer update drupal/core --with-dependencies
This will rebuild / redownload everything but it seems to work and updates properly to 8.5 (the most recent stable version of core).
I am newbie to Django-haystack. I got an error while following Django-Haystack documentation.
Command execution order, I followed:
I started elasticsearch server (1.7.3) using command prompt and I am able to access http://127.0.0.1:9200/
python manage.py rebuild_index
Output:
WARNING: This will irreparably remove EVERYTHING from your search index in connection 'default'.
Your choices after this are to restore from backups or rebuild via the rebuild_index command.
Are you sure you wish to continue? [y/N] y
Error:
packages\haystack\backends\elasticsearch_backend.py", line 28, in
raise MissingDependency("The 'elasticsearch' backend requires the installation of 'elasticsearch'. Please refer to the documentation.")
haystack.exceptions.MissingDependency: The 'elasticsearch' backend requires the installation of 'elasticsearch'. Please refer to the documentation.
Current Platform (Windows):
1. Django 1.8
2. elasticsearch: 1.9.0 (installed through pip)
3. pyelasticsearch: 0.0.5 (installed through pip)
4. elasticseach: 1.7.3 (downloaded to start elasticsearch server)
I have tried adding the 'elasticsearch' also to my installed apps but the same error exists.
It seems there is version compatibility problems (perhaps in pyelasticseach) as I found some others also faced the same issue. Any help would be appreciated. Thanks.