i was tring to install ansible via yum repo and i keep getting this error msg which i never came cross before ,
Resolving Dependencies
--> Running transaction check
---> Package ansible-tower.noarch 0:2.1.1-1.el6 will be installed
--> Processing Dependency: proot for package: ansible-tower-2.1.1-1.el6.noarch
--> Finished Dependency Resolution
Error: Package: ansible-tower-2.1.1-1.el6.noarch (ans)
Requires: proot
What is proot ? its not package as far as i know
any advise for this ?
PRoot is a user-space implementation of chroot, mount --bind, and binfmt_misc.
If it is not available in the CentOS repositories it can be found here: http://proot.me/
(but you probably already know this ;) )
Related
I am facing issues in " yum install krb5-server" on RHEL 6.9 .This I am doing to install Kerberos on MapR 5.2 cluster. Issue mentioned below:
[root#master ~]# yum install krb5-server
Loaded plugins: product-id, refresh-packagekit, search-disabled-repos, security, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package krb5-server.x86_64 0:1.10.3-57.el6 will be installed
--> Processing Dependency: krb5-libs = 1.10.3-57.el6 for package: krb5-server-1.10.3-57.el6.x86_64
--> Running transaction check
---> Package krb5-libs.i686 0:1.10.3-57.el6 will be installed
--> Processing Dependency: libselinux.so.1 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libresolv.so.2(GLIBC_2.2) for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libresolv.so.2 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libm.so.6 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libkeyutils.so.1(KEYUTILS_0.3) for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libkeyutils.so.1 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libdl.so.2 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libcom_err.so.2 for package: krb5-libs-1.10.3-57.el6.i686
--> Processing Dependency: libc.so.6(GLIBC_2.9) for package: krb5-libs-1.10.3-57.el6.i686
--> Running transaction check
---> Package glibc.i686 0:2.12-1.192.el6 will be installed
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.192.el6.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.192.el6.i686
---> Package keyutils-libs.i686 0:1.4-5.el6 will be installed
---> Package libcom_err.i686 0:1.41.12-22.el6 will be installed
---> Package libselinux.i686 0:2.0.94-7.el6 will be installed
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.14.3-23.3.el6_8 will be installed
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for krb5-libs which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of krb5-libs of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude krb5-libs.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of krb5-libs installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of krb5-libs installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: krb5-libs-1.10.3-57.el6.i686 != krb5-libs-1.10.3-65.el6.x86_64
Error: Protected multilib versions: libcom_err-1.41.12-22.el6.i686 != libcom_err-1.41.12-23.el6.x86_64
[root#master ~]#
Yum errors like this happen if the system is installed from newer installation media and then subscribed to software channels which only provide older package versions. I usually see it when people install the betas and then do not enable the beta channels after installation (which is a manual step).
The hint is in this line:
Protected multilib versions: krb5-libs-1.10.3-57.el6.i686 != krb5-libs-1.10.3-65.el6.x86_64
Error: Protected multilib versions: libcom_err-1.41.12-22.el6.i686 != libcom_err-1.41.12-23.el6.x86_64
Yum tries to install version 1.10.3-57.el6, while 1.10.3-65 is already installed. (You can ignore the i686/x86_64 difference, yum goes really wrong while trying to figure out what to install here.)
Red Hat Enterprise Linux 6.9 has been released, so it is not the usual beta problem. You need to check the channel subscriptions with yum repolist -v and then use subscription-manager repos --disable=… --enable=… to fix the channel configuration.
If you use Satellite, the policy applied to your system might feed it the wrong version of the operating system. In this case, you may have to make the changes in the Satellite infrastructure.
If, for some reason, you need an EUS version of Red Hat Enterprise Linux (older than 6.9), you should just set up a new system with that. Downgrades can be rather difficult.
How about removing yum cache, and then the retry it.
# yum clean all
or
# rm -rf /var/cache/yum
# yum update
# yum install krb5-server
I have an old version of Fedora, version 18, and I need to install google-chrome as well as other packages. However when installing google-chrome, version 43, I'm getting errors for a number of dependencies I should have. I think it is due to having an old Fedora version, version 18. I can not update it because Fedora 22 is too slow in my old PC.
[rodolk#Gandalf Downloads]$ sudo yum install google-chrome-stable
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package google-chrome-stable.x86_64 0:43.0.2357.132-1 will be installed
--> Processing Dependency: lsb >= 4.0 for package: google-chrome-stable-43.0.2357.132-1.x86_64
--> Processing Dependency: libnss3.so(NSS_3.14.3)(64bit) for package: google-chrome-stable-43.0.2357.132-1.x86_64
--> Finished Dependency Resolution
Error: Package: google-chrome-stable-43.0.2357.132-1.x86_64 (google-chrome)
Requires: lsb >= 4.0
Error: Package: google-chrome-stable-43.0.2357.132-1.x86_64 (google-chrome)
Requires: libnss3.so(NSS_3.14.3)(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[rodolk#Gandalf Downloads]$
Thanks in advance.
One solution could be to tweak your /etc/yum.repos.d/fedora.repo file to force him to point on the fedora 18 old repo. Unfortunately I don't think they are maintained anymore (see the void directory at http://mirror.chpc.utah.edu/pub/fedora/linux/releases/).
Otherwise, you can try older versions of chrome (available at http://www.filehippo.com/download_google_chrome/) but you'll have to refuse any proposed upgrade if you manage to install it. Not a good solution tho, because of possible security breach present in older versions.
I suggest installing Fedora with a lightweight GUI (which I suspect is the reason of the degraded peformances on your old machine), like KDE or xfce. You can find more choices here: https://spins.fedoraproject.org/.
I'm trying to update MongoDB 2.4 to 2.6 on my 64-bit CentOS machine. I have removed the old 10gen repository package and created the /etc/yum.repos.d/mongodb.repo file with the new configuration as explained here.
However, when I run sudo yum install mongodb-org, I get the following error:
Error: mongodb-org conflicts with mongodb-org-server
This is the output in the shell:
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mongodb-org.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Dependency: mongodb-org-server = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-shell = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-mongos = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-tools = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Running transaction check
---> Package mongodb-org-mongos.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-server.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-shell.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-tools.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Conflict: mongodb-org-2.6.1-0.1.rc0.x86_64 conflicts mongo-10gen-server
--> Finished Dependency Resolution
Error: mongodb-org conflicts with mongodb-org-server
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Has anyone else encountered anything similar? What is the best course of action here? Should I try using the --skip-broken option? I did a fresh installation in a new box a couple of days ago and did not encounter any problems.
Thanks for your help with this.
My best guess is that the yum build was broken when they updated to version 2.6.1-0.1.rc0.
For a temporary fix you could:
Try the unstable version, which is currently 2.5.5
yum install mongodb-org-unstable
or the regular mongodb package that comes with OS
yum install -y mongodb mongodb-server
Actually I had the same problem, the process that worked for me was:
Stop all mongo processes
service mongoInstance stop
Remove mongodb
yum remove -y mongodb
If not removed yet
rpm -e --noscripts mongodb-server
After that you may install mongodb-org and re-enable your processes.
During the release of version 2.6.1-rc0, packages were accidentally published into the MongoDB yum and apt repositories such that new and upgrade requests would install the release candidate 2.6.1-rc0 instead of 2.6.0 (stable release).
Users expecting to install, upgrade to, or retain version 2.6.0 may have inadvertently installed version 2.6.1-rc0, which is a release candidate and not recommended for production use. However, we do not expect that accidentally updating to 2.6.1-rc0 will adversely affect your data or operations.
The packages were incorrectly published on April 22, 5:30pm EDT. The issue was resolved on April 23, 11:30AM EDT. Users who attempted to install or upgrade to version 2.6.0 during this time were affected by this issue.
More information for this issue can be found here: https://jira.mongodb.org/browse/SERVER-13691
Ernie Hershey from MongoDB just answered my post on the MongoDB user group:
https://groups.google.com/forum/#!topic/mongodb-user/5xRQW7ER4hE
Basically, there is a bug in how MongoDB RC packages are generated. So you need to run yum makecache before running yum install mongodb-org. That should fix the problem.
I have a helper rpm package which is used to install the necessary dependencies in order for some software to work; the problem is that the dependency packages required are the 32bit ones, which can't be installed on CentOS 64bit without the --setopt=protected_multilib=false flag.
To manually install the dependencies I'd just run:
# yum install --setopt=protected_multilib=false libXrandr.i686
# yum install --setopt=protected_multilib=false gtk2.i686
# yum install --setopt=protected_multilib=false libXtst.i686
This would correctly install the 32bit version of the packages.
The problem appears when installing the helper package directly, as it seems there's no way to force --setopt=protected_multilib=false for the dependencies.
When trying to install the package (locally, using yum --nogpgcheck --setopt=protected_multilib=false localinstall centos_helper-0-0.x86_64.rpm) I get the following error:
Examining centos_helper-0-0.x86_64.rpm: centos_helper-0-0.x86_64
Marking centos_helper-0-0.x86_64.rpm to be installed
Loading mirror speeds from cached hostfile
* base: mirror.dattobackup.com
* extras: mirror.metrocast.net
* rpmforge: mirror.de.leaseweb.net
* updates: mirror.dattobackup.com
Resolving Dependencies
--> Running transaction check
---> Package centos_helper.x86_64 0:0-0 will be installed
--> Processing Dependency: libXrandr.i686 for package: centos_helper-0-0.x86_64
--> Processing Dependency: gtk2.i686 for package: centos_helper-0-0.x86_64
--> Processing Dependency: libXtst.i686 for package: centos_helper-0-0.x86_64
--> Finished Dependency Resolution
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: gtk2.i686
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: libXrandr.i686
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: libXtst.i686
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
This is the same error I get when trying to install the dependencies by hand without the protected_multilib=false flag.
The .spec file I'm using to create the package has the following content:
Summary: CentOS helper file
Name: centos_helper
Version: 0
Release: 0
License: Public
Group: Applications/System
Requires: libXrandr.i686,gtk2.i686,libXtst.i686
%description
Installer CentOS helper package
%files
Any way to have the dependencies correctly install?
You might want to look at http://www.rpm.org/wiki/PackagerDocs/ArchDependencies
I prefer referencing sonames myself, that way yum will look up what dependancy to install.
I've had major CentOS upgrades failing because if this.
This if for recent RPM versions only : 4.6 or so. If you're on something older :
Requires: real-soname.so.1()(64bit), real-soname.so.1, packagename
From memory, you might need a tweak.
I am trying to install yum-utils package to resolve a broken installation, but it fails due to a conflict:
sudo yum install yum-utils --skip-broken
returns
Loaded plugins: fastestmirror, priorities, security, update-motd
Loading mirror speeds from cached hostfile
Setting up Install Process
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.
--> Running transaction check
---> Package yum-utils.noarch 0:1.1.30-6.11.amzn1 will be installed
--> Processing Conflict: yum-utils-1.1.30-6.11.amzn1.noarch conflicts system-release <= 2011.09-1.33
--> Finished Dependency Resolution
Packages skipped because of dependency problems:
yum-utils-1.1.30-6.11.amzn1.noarch from amzn-updates
I am finding myself in a catch-22 situation and I don't know how to resolve it. Cannot install any package with yum because of a broken installation (it recommends to run yum-complete-transaction which is in yum-utils), but installing yum-utils also fails.
Any help would be greatly appreciated.
Thanks,
M
Okay, I ran into the same problem - yum bombed out and I couldn't install yum-complete-transaction.
In the end, what I did was copy /usr/sbin/yum-complete-transaction across from another Amazon instance, then ran it and after it finished the remaining transactions installed the 'yum-utils' package.
I know this is probably not the 'most correct' method to fix it, but it worked and quite frankly, if it's stupid but worked, it's not stupid :)