So I am trying to add php-fpm to have it work with nginx. But the issue I am having is I already have some other php stuff in there like php-common and now it's having conflicts. So centOS is suggesting I use --skip-broken but i'm not sure if that's the best way to go? Would there be any issues if I do end up using that to install php-fpm?
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
* base: dallas.tx.mirror.xygenhosting.com
* epel: www.gtlib.gatech.edu
* extras: mirror.millry.co
* updates: mirror.cs.vt.edu
* webtatic: us-east.repo.webtatic.com
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php-fpm.x86_64 0:5.3.3-27.el6_5.1 will be installed
--> Processing Dependency: php-common(x86-64) = 5.3.3-27.el6_5.1 for package: php-fpm-5.3.3-27.el6_5.1.x86_64
--> Running transaction check
---> Package php-common.x86_64 0:5.3.3-27.el6_5.1 will be installed
--> Processing Conflict: php55w-common-5.5.16-1.w6.x86_64 conflicts php-common < 5.5.0
--> Finished Dependency Resolution
Error: php55w-common conflicts with php-common-5.3.3-27.el6_5.1.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
If you know what you are doing, you can upgrade PHP by:
yum install yum-plugin-replace
yum replace php-common --replace-with=php55w-common
It will likely give you a message “WARNING: Unable to resolve all providers …”. This is normal, and you can continue by tying “y“. You will be given a chance to see what packages will be installed and removed before again being given a chance to confirm.
Then you can continue with your previous installation command
Related
I'm trying to use install snowflake-connector-python to a Cloud Composer environment but keep receiving an error that pops up in the UI, "Failed to install PyPI Packages. Check the Cloud Build log for details". The build log doesn't seem overly helpful and is very long, so I'll just show some of the notable things here.
This is a warning that shows after installing snowflake-connector-python and its dependencies.
Installing collected packages: pycryptodomex, asn1crypto, oscrypto, jmespath, botocore, s3transfer, boto3, isodate, msrest, azure-core, azure-storage-blob, azure-common, snowflake-connector-python
Successfully installed asn1crypto-1.4.0 azure-common-1.1.25 azure-core-1.8.1 azure-storage-blob-12.5.0 boto3-1.14.63 botocore-1.17.63 isodate-0.6.0 jmespath-0.10.0 msrest-0.6.19 oscrypto-1.2.1 pycryptodomex-3.9.8 s3transfer-0.3.3 snowflake-connector-python-2.3.2
+ [[ -z fail ]]
+ python3 -m pipdeptree --warn fail
Warning!!! Possibly conflicting dependencies found:
* botocore==1.17.63
- docutils [required: >=0.10,<0.16, installed: 0.16]
This is the final error notification.
The command '/bin/sh -c bash installer.sh $COMPOSER_PYTHON_VERSION fail' returned a non-zero code: 1
ERROR
ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1
I'm running the image composer-1.12.1-airflow-1.10.10 in zone us-central1-c and is using python 3. I've tried installing different versions of the package with no luck, and have tried doing it via the UI and via gcloud. Any help as to the root of this problem would be much appreciated!
I tried trying to install older versions of snowflake-connector-python but that didn't work.
What did end up working was adding docutils==0.15 to the list of packages to install. This fixed the dependency conflict warning and led to a successful build.
Previously, I've received dependency conflict warnings that led to successful builds. But for this case, I actually needed to resolve that conflict.
The answer from nate did not work for me, the PyPi package install succeeds in CloudBuild but then the Web Server fails to update and rolls back installing the packages.
In order to get this working we had to downgrade our Composer to the September release which comes with docutils==0.15.2.
The image we used was composer-1.12.1-airflow-1.10.9, it seems that any image in airflow 1.10.10 or above has this issue as they come with docutils==0.16 as standard. You can see which version of docutils is in an image by using this link and expanding the PyPi packages column.
I am trying to install Openstack using DevStack. After correctly creating the user stack and running ./stack.sh, the script starts to install the required dependencies until it hits Obtaining file:///opt/stack/cinder. Then I obtain the following errors:
Exception:
ContextualVersionConflict: (grpcio 1.21.1 (/usr/local/lib/python2.7/dist-packages), Requirement.parse('grpcio<1.16.0,>=1.0.0'), set(['tooz']))
I understand that there is a conflict in grpcio, but I don't know how to solve it. I already unsuccessfully tried to install a specific version between 1.0.0 and 1.16.0.
The Devstack version I am using is the latest from the git master.
I think I solved the problem myself.
I had the tooz package installed with version 1.62 which was causing the issue.
After removing that package the installation completed.
I am installing a custom debian package on debian 6 machine.
This is my control file
Package: [[name]]
Version: 5.1
Section: hello/world
Priority: Optional
Architecture: all
Essential: no
Depends: my-dependent-package (>> 0.2.1)
Installed-Size: 1000
Maintainer: Test test#test.com
Description: _DESCRIPTION_
Here the my-dependent-package doesnt get auto upgraded when newer versions are released.
i always do sudo apt-get update before installing.
installing the debian from an internal mirror and using
sudo apt-get install mypackage
the dependent package "my-dependent-package" is also available in the same internal mirror.
the internal mirrors are defined in /etc/apt/sources.list
both the packages come from same mirror
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
my-package : Depends: my-dependent-package (>> 0.2.1) but it is not going to be installed
E: Broken packages
Installation succeeds when I manually install the "my-dependent-package". I was expecting it to be auto installed by the "my-package" as I have mentioned it in control file.
How can I enable it ?
Debian assigns priorities to suites and packages.
Most likely your local repository has a low priority, which results in being excluded from automatic updates.
Configure apt to assign a higher priority to your repository, so it get's automatically selected.
See the AptPreferences documentation for more information.
(It's really impossible to give you a walkthrough without more knowledge on your actual setup)
I am trying to install OMD in my CentOS 6.6 linux machine using this link [https://mathias-kettner.de/checkmk_install_with_omd.html.][1] Initially I installed epel repoistory and then when in tried installing OMD it says the following.
[root#ctg-alpha-mon1 /]# yum install --nogpgcheck omd-0.42-0.42-
centos55.14.x86_64.rpm
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, kabi, presto, refresh-packagekit, security, tmprepo,
: verify, versionlock
Loading support for CentOS kernel ABI
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirrors.centarra.com
* epel: lug.mtu.edu
* extras: mirrors.centarra.com
* updates: mirrors.centarra.com
No package omd-0.42-0.42-centos55.14.x86_64.rpm available.
Error: Nothing to do
I tried 'yum search omd* ' or 'yum search omd-' but still it says no package available.
How do I install omd? I am pretty new to this.
Will omd package be available in the linux for us to install or should I get it from somewhere and then install it?
Any help is much appreciated.
Thanks
The OMD package is not available on a yum repository, except for subscribers.
OMD package has to be downloaded from their site or lookup the community version. Have a look at http://omdistro.org/ and https://labs.consol.de/de/nagios/omd-repository/
I try to install PHP-FPM for NGINX then get same errors, with remi repository.
Maybe have version conflate with php-common, How can i fix it.
yum --enablerepo=remi install php-fpm
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: centos.mirror.transip.nl
* extras: centos.mirror.transip.nl
* remi: remi-mirror.dedipower.com
* updates: centos.mirror.transip.nl
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php-fpm.x86_64 0:5.3.14-1.el5.remi set to be updated
--> Processing Dependency: php-common = 5.3.14-1.el5.remi for package: php-fpm
--> Finished Dependency Resolution
php-fpm-5.3.14-1.el5.remi.x86_64 from remi has depsolving problems
--> Missing Dependency: php-common = 5.3.14-1.el5.remi is needed by package php-fpm-5.3.14- 1.el5.remi.x86_64 (remi)
Error: Missing Dependency: php-common = 5.3.14-1.el5.remi is needed by package php-fpm- 5.3.14-1.el5.remi.x86_64 (remi)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
You'll need to install/update php-common manually first.
Try this:
rpm -i http://rpms.famillecollet.com/enterprise/5/remi/x86_64/php-common-5.3.14-1.el5.remi.x86_64.rpm
If you get a conflict (say due to an earlier version already installed), use
rpm -i http://rpms.famillecollet.com/enterprise/5/remi/x86_64/php-common-5.3.14-1.el5.remi.x86_64.rpm --force
The old version can be removed without taking its dependencies with it like this
rpm -e --nodeps php-common-5.3.10-1.el5.remi.x86_64