Centos ошибка при установке пакета

Whenever I want to use command yum install <packagename> I get error:

No package available

For example,

[root@cpanel1 etc]# yum install autossh
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.t-2.net
 * extras: centos.t-2.net
 * updates: centos.t-2.net
No package autossh available.
Error: Nothing to do
[root@cpanel1 etc]#

How do I make it work?

Rahul's user avatar

Rahul

13.3k3 gold badges43 silver badges54 bronze badges

asked Jul 25, 2016 at 10:46

Kunok's user avatar

13

These steps might help you,

  1. yum clean all & yum clean metadata

  2. Check the files in /etc/yum.repos.d and make sure that they don’t all have enabled = 0 for each repo (there may be more than one per file).

  3. Finally you would be able to do yum update and search for desired packages.

answered Jul 25, 2016 at 12:11

Rahul's user avatar

RahulRahul

13.3k3 gold badges43 silver badges54 bronze badges

For CentOS/RHEL 7, autossh is no longer available in Repoforge repository. So you will need to build and compile it from the source, here is what you should do:

$ sudo yum install wget gcc make
$ wget http://www.harding.motd.ca/autossh/autossh-1.4e.tgz
$ tar -xf autossh-1.4e.tgz
$ cd autossh-1.4e
$ ./configure
$ make
$ sudo make install

answered Jul 25, 2016 at 11:19

2

First install EPEL(Extra Packages for Enterprise Linux), then install your need packagename

$ yum -y install epel-release
$ yum -y install autossh

answered Sep 14, 2022 at 11:52

Subfire's user avatar

autossh is also available with epel repo:

# mkdir /usr/src/epel && cd "$_"
# wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-10.noarch.rpm
# rpm -ihv epel-release-7-10.noarch.rpm
# yum install autossh

answered Aug 29, 2017 at 2:14

maxime_039's user avatar

3

You should also check /etc/yum.conf file or /etc/yum.repos.d/ files to make sure your package is not excluded in yum.

exclude=apache* httpd* mod_* mysql* MySQL* mariadb* da_* *ftp* exim* sendmail* php* bind-chroot* dovecot*

answered Jun 15, 2021 at 10:20

Mojtaba Rezaeian's user avatar

Note that autossh package is available with the «epel» repository. To install it:

# mkdir /usr/src/epel && cd "$_"
# wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-10.noarch.rpm
# rpm -ihv epel-release-7-10.noarch.rpm
# yum install autossh

This answer may be generalized for other packages in the «epel» distribution.

Toby Speight's user avatar

Toby Speight

8,4623 gold badges26 silver badges50 bronze badges

answered Oct 10, 2017 at 9:50

user254894's user avatar

1

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

BEFORE TRYING ANY OF THIS, HAVE A BACKUP OF YOUR MACHINE, YOU COULD DAMAGE YOUR OS MORE/COMPLETELY

It seems that your yum variable $releasever is somehow corrupt,
it usually is caused by missing centos-release package on the machine for some obscure reasons.

You can check if you have the package by: 

    rpm -qi centos-release

You will probably see: 

    "package centos-release is not installed"

First find out the exact centos version that you have by executing as root: 

    cat /etc/redhat-release

You will see something like this: 

    CentOS Linux release 7.3.1611 (Core)

You can fetch the centos-release package from repo by:

    wget http://vault.centos.org/centos/7.3.1611/updates/x86_64/Packages/centos-release-7-3.1611.el7.centos.2.5.x86_64.rpm

Now run reinstall centos-release package via rpm:

    sudo rpm -Uvh --replacepkgs centos-release-7-3.1611.el7.centos.2.5.x86_64.rpm

As next you can try to install something with yum and you might get: 

    [root@dcos-master3 ikerlan]# sudo yum install wget
    error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
    error: cannot open Packages index using db5 - (-30969)
    error: cannot open Packages database in /var/lib/rpm
    CRITICAL:yum.main:

    Error: rpmdb open failed

Now you can try to reboot the machine or try to use the following command to rebuild the rpm db: 

    rpm --rebuilddb

Источник

Whenever I want to use command yum install <packagename> I get error:

No package available

For example,

[root@cpanel1 etc]# yum install autossh
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.t-2.net
 * extras: centos.t-2.net
 * updates: centos.t-2.net
No package autossh available.
Error: Nothing to do
[root@cpanel1 etc]#

How do I make it work?

Rahul's user avatar

Rahul

13.3k3 gold badges43 silver badges54 bronze badges

asked Jul 25, 2016 at 10:46

Kunok's user avatar

13

These steps might help you,

  1. yum clean all & yum clean metadata

  2. Check the files in /etc/yum.repos.d and make sure that they don’t all have enabled = 0 for each repo (there may be more than one per file).

  3. Finally you would be able to do yum update and search for desired packages.

answered Jul 25, 2016 at 12:11

Rahul's user avatar

RahulRahul

13.3k3 gold badges43 silver badges54 bronze badges

For CentOS/RHEL 7, autossh is no longer available in Repoforge repository. So you will need to build and compile it from the source, here is what you should do:

$ sudo yum install wget gcc make
$ wget http://www.harding.motd.ca/autossh/autossh-1.4e.tgz
$ tar -xf autossh-1.4e.tgz
$ cd autossh-1.4e
$ ./configure
$ make
$ sudo make install

answered Jul 25, 2016 at 11:19

2

First install EPEL(Extra Packages for Enterprise Linux), then install your need packagename

$ yum -y install epel-release
$ yum -y install autossh

answered Sep 14, 2022 at 11:52

Subfire's user avatar

autossh is also available with epel repo:

# mkdir /usr/src/epel && cd "$_"
# wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-10.noarch.rpm
# rpm -ihv epel-release-7-10.noarch.rpm
# yum install autossh

answered Aug 29, 2017 at 2:14

maxime_039's user avatar

3

You should also check /etc/yum.conf file or /etc/yum.repos.d/ files to make sure your package is not excluded in yum.

exclude=apache* httpd* mod_* mysql* MySQL* mariadb* da_* *ftp* exim* sendmail* php* bind-chroot* dovecot*

answered Jun 15, 2021 at 10:20

Mojtaba Rezaeian's user avatar

Note that autossh package is available with the «epel» repository. To install it:

# mkdir /usr/src/epel && cd "$_"
# wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-10.noarch.rpm
# rpm -ihv epel-release-7-10.noarch.rpm
# yum install autossh

This answer may be generalized for other packages in the «epel» distribution.

Toby Speight's user avatar

Toby Speight

8,4623 gold badges26 silver badges50 bronze badges

answered Oct 10, 2017 at 9:50

user254894's user avatar

1

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

В дан­ном руко­вод­стве мы будем исполь­зо­вать толь­ко коман­ду yum, так как она рабо­та­ет и в CentOS 7 и в 8.

Коман­да yum/dnf исполь­зу­ет репо­зи­то­рии для сво­ей рабо­ты. Очень важ­но понять, как с ними рабо­тать в систе­ме. Кон­фи­ги репо­зи­то­ри­ев CentOS опи­сы­ва­ют пути, по кото­рым систе­ма может брать уста­но­воч­ные фай­лы для паке­тов, а так­же пра­ви­ла рабо­ты с сами­ми репозиториями.

1. Про­смотр репозиториев.

Так­же мы можем полу­чить подроб­ное опи­са­ние для каж­до­го вклю­чен­но­го репозитория:

2. Добав­ле­ние репо­зи­то­рия командой.

Для добав­ле­ния репо­зи­то­рия мы можем вос­поль­зо­вать­ся коман­дой yum-config-manager, для это­го сна­ча­ла нуж­но уста­но­вить yum-utils:

* на осно­ве ссыл­ки https://yum.mariadb.org/10.5/centos8-amd64 будет добав­лен репозиторий.

3. Добав­ле­ние репо­зи­то­рия через файл.

Так­же мы можем создать кон­фи­гу­ра­ци­он­ный файл с опи­са­ни­ем репо­зи­то­рия. Все фай­лы нахо­дят­ся в ката­ло­ге /etc/yum.repos.d. Напри­мер, созда­дим файл с добав­ле­ни­ем репо­зи­то­рия mariadb:

[mariadb]

name = MariaDB

baseurl = http://yum.mariadb.org/10.5/centos8-amd64

gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB

gpgcheck=1

enabled=1

* где:

  • name — про­из­воль­ное имя репозитория.
  • baseurl — путь, по кото­ро­му систе­ма может заби­рать паке­ты из репозитория.
  • gpgkey — путь до откры­то­го gpg-клю­ча. Нужен для про­вер­ки циф­ро­вой под­пи­си пакетов.
  • gpgcheck — нуж­но ли про­ве­рять циф­ро­вую под­пись пакетов.
  • enabled — опция вклю­ча­ет или выклю­ча­ет репозиторий.

4. Вре­мен­ное вклю­че­ние и отклю­че­ние репо­зи­то­ри­ев во вре­мя опе­ра­ций (на при­ме­ре репо­зи­то­рия EPEL).

Отклю­чить во вре­мя обновления:

yum update —disablerepo=epel

Вклю­чить во вре­мя обновления:

yum update —enablerepo=epel

Отклю­чить во вре­мя установки:

yum install —disablerepo=epel

Вклю­чить во вре­мя установки:

yum install —enablerepo=epel

5. Посто­ян­ное отключение/включение репозиториев.

Мы можем отклю­чить наш репо­зи­то­рий командой:

yum-config-manager —disable <имя репозитория>

* для выпол­не­ния дан­ной коман­ды мы долж­ны уста­но­вить в систе­му пакет yum-utils.

Напри­мер:

yum-config-manager —disable yum.mariadb.org_10.5_centos8-amd64

Раз­ре­шить репо­зи­то­рий мож­но той же коман­дой с опци­ей —enable:

yum-config-manager —enable yum.mariadb.org_10.5_centos8-amd64

Так­же мы можем выпол­нить настрой­ку в кон­фи­гу­ра­ци­он­ном фай­ле, например:

vi /etc/yum.repos.d/mariadb.repo

Нахо­дим:

enabled=1

… и меня­ем на:

enabled=0

* в дан­ном при­ме­ре 1 раз­ре­ша­ет репо­зи­то­рий, а 0 запрещает.

6. Управ­ле­ние пото­ка­ми в CentOS 8

dnf module list nodejs

dnf module enable nodejs:12

7. Настрой­ка опций.

Наши репо­зи­то­рии настра­и­ва­ют­ся с помо­щью опций, кото­рые пере­чис­ле­ны в кон­фи­гу­ра­ци­он­ном фай­ле. Мы можем так­же их зада­вать командой:

yum-config-manager —save —setopt=<имя репозитория>.<имя опции>=<значение>

Напри­мер:

yum-config-manager —save —setopt=mariadb.module_hotfixes=1

Процесс установки и обновления пакетов

1. Уста­нов­ка пакета:

yum install <имя пакета>

2. Обнов­ле­ние всех уста­нов­лен­ных пакетов:

yum update

3. Обнол­ве­ние кон­крет­но­го пакета

yum update <имя пакета>

4. Уста­но­вить пакет из опре­де­лен­но­го репозитория:

yum —disablerepo=»*» —enablerepo=thirdparty install nginx

* как гово­ри­лось выше, мы можем опе­ри­ро­вать опци­я­ми disablerepo и enablerepo для вклю­че­ния и отклю­че­ния репо­зи­то­рия во вре­мя уста­нов­ки. В дан­ном при­ме­ре мы запре­ти­ли все и раз­ре­ши­ли уста­но­вить нуж­ный нам пакет из репо­зи­то­рия thirdparty.

Обслуживание

1. Уда­лить кэш для спис­ков паке­тов в репо­зи­то­ри­ях, а так­же загру­жен­ные исход­ни­ки для пакетов:

yum clean —enablerepo=* all

Заблокировать установку и обновление пакетов

В неко­то­рых слу­ча­ях, может воз­ник­нуть необ­хо­ди­мость запре­тить уста­нов­ку и обнов­ле­ние опре­де­лен­ных паке­тов. Есть несколь­ко спо­со­бов это сделать.

1. Во время обновления (разово)

Дан­ный метод мож­но исполь­зо­вать при обнов­ле­нии паке­тов. Мы с помо­щью клю­ча -x про­сто ука­зы­ва­ем через запя­тую те, кото­рые не долж­ны быть обнов­ле­ны, например:

yum -x postgresql*,asterisk update

* дан­ной коман­дой мы обно­вим все паке­ты, кро­ме asterisk и тех, назва­ние кото­рых начи­на­ет­ся на postgresql.

2. Постоянный запрет в yum.conf

Ана­ло­гич­но, мож­но запре­тить как уста­нов­ку, так и обнов­ле­ние в кон­фи­гу­ра­ци­он­ном фай­ле yum.conf. Откры­ва­ем его командой:

vi /etc/yum.conf

Добав­ля­ем:

exclude=postgresql* asterisk

* в дан­ном при­ме­ре мы так­же запре­тим уста­нов­ку и обнов­ле­ние asterisk, а так­же паке­тов, назва­ние кото­рых начи­на­ет­ся на postgresql.

3. Настройка репозитория

Ну и так­же мы можем забло­ки­ро­вать уста­нов­ку и обнов­ле­ние через кон­фи­гу­ра­ци­он­ный файл репо­зи­то­рия. Например:

vi /etc/yum.repos.d/pgdg-redhat-all.repo

И доба­вим:

[pgdg12]
…
exclude=postgresql12*

* в дан­ном при­ме­ре мы бло­ки­ру­ем пакет postgresql12.

Возможные ошибки

Рас­смот­рим при­ме­ры оши­бок, с кото­ры­ми мы можем столк­нуть­ся и спо­со­бы их решения.

1. Curl error (60): SSL peer certificate or SSH remote key was not OK

Ошиб­ка появ­ля­ет­ся при попыт­ке выпол­нить опе­ра­цию обнов­ле­ния или уста­нов­ки пакетов.

При­чи­на: сер­ти­фи­кат под­клю­чен­но­го репо­зи­то­рия не про­хо­дит про­вер­ку. Воз­мож­но, он про­сро­чен или выдан не дове­рен­ным цен­тром сертификации.

Реше­ние: про­бле­му мож­но решить на сто­роне сер­ве­ра (если мы явля­ем­ся его адми­ни­стра­то­ром), напри­мер, полу­чив пра­виль­ный сер­ти­фи­кат у Let’s Encrypt. На сто­роне кли­ен­та мож­но отклю­чить про­вер­ку SSL для репо­зи­то­рия командой:

yum-config-manager —save —setopt=<имя репозитория>.sslverify=0

Или в кон­фи­гу­ра­ци­он­ном фай­ле репо­зи­то­рия доба­вить или изме­нить стро­ку с sslverify:

sslverify=0

* дан­ная опция зада­ет необ­хо­ди­мость про­вер­ки SSL для репозитория.

2. Error: GPG validation FAILED

Ошиб­ка появ­ля­ет­ся при попыт­ке уста­но­вить пакет.

При­чи­на: систе­ма не может загру­зить и импор­ти­ро­вать gpg-ключ. Это воз­мож­но в раз­ных сце­на­ри­ях, напри­мер, в настрой­ках репо­зи­то­рия не ука­зан путь до него, но при этом ука­за­но, что про­вер­ка под­пи­си необ­хо­ди­ма или ключ не уда­лось загру­зить и импортировать.

Реше­ние: для неко­то­рых паке­тов идет отдель­ная инструк­ция по настрой­ке репо­зи­то­рия, в част­но­сти, уста­нов­ки клю­ча GPG. Или мы можем отклю­чить про­вер­ку gpg командой:

yum-config-manager —save —setopt=<имя репозитория>.gpgcheck=0

Или через кон­фи­гу­ра­ци­он­ный файл:

gpgcheck=0

Источник

When trying to install or update anything in yum, I get a list of requires, removing and obsoleted by:

Loaded plugins: downloadonly, fastestmirror
Setting up Update Process
Determining fastest mirrors
epel/metalink                                                                                                        |  14 kB     00:00     
 * epel: mirrors.mit.edu
base                                                                                                                 | 3.7 kB     00:00     
base/primary_db                                                                                                      | 4.6 MB     00:00     
epel                                                                                                                 | 4.4 kB     00:00     
epel/primary_db                                                                                                      | 3.9 MB     00:00     
extras                                                                                                               | 3.4 kB     00:00     
extras/primary_db                                                                                                    |  30 kB     00:00     
updates                                                                                                              | 3.4 kB     00:00     
updates/primary_db                                                                                                   | 2.1 MB     00:00     
Resolving Dependencies
--> Running transaction check
---> Package db4.x86_64 0:4.7.25-18.el6_4 will be obsoleted
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: psa-courier-imap-4.15-cos6.build1200150114.15.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd-tools-2.2.15-39.el6.centos.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-15.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-2.6.32-33.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd-2.2.15-39.el6.centos.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.1-20.el6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: python-libs-2.6.6-52.el6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: subversion-1.6.11-12.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: 4:perl-5.10.1-136.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.3.9-3.el6_0.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: 2:postfix-2.8.17-14042513.x86_64
---> Package db4-cxx.x86_64 0:4.7.25-18.el6_4 will be obsoleted
---> Package db4-devel.x86_64 0:4.7.25-18.el6_4 will be obsoleted
---> Package db4-utils.x86_64 0:4.7.25-18.el6_4 will be obsoleted
---> Package libc-client.x86_64 0:2007e-11.el6 will be updated
---> Package libc-client.x86_64 0:2007f-4.el7.1 will be an update
---> Package libdb4.x86_64 0:4.8.30-13.el7 will be obsoleting
---> Package libdb4-cxx.x86_64 0:4.8.30-13.el7 will be obsoleting
---> Package libdb4-devel.x86_64 0:4.8.30-13.el7 will be obsoleting
---> Package libdb4-utils.x86_64 0:4.8.30-13.el7 will be obsoleting
---> Package libmcrypt.x86_64 0:2.5.8-9.el6 will be updated
---> Package libmcrypt.x86_64 0:2.5.8-13.el7 will be an update
---> Package mod_perl.x86_64 0:2.0.4-11.el6_5 will be updated
---> Package mod_perl.x86_64 0:2.0.8-10.20140624svn1602105.el7 will be an update
--> Processing Dependency: httpd-mmn = 20120211x8664 for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
--> Processing Dependency: perl(Linux::Pid) for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
--> Processing Dependency: perl(:MODULE_COMPAT_5.16.3) for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
--> Processing Dependency: libdb-5.3.so()(64bit) for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
---> Package perl-BSD-Resource.x86_64 0:1.29.03-3.el6 will be updated
---> Package perl-BSD-Resource.x86_64 0:1.29.07-1.el7 will be an update
--> Processing Dependency: perl(:MODULE_COMPAT_5.16.3) for package: perl-BSD-Resource-1.29.07-1.el7.x86_64
---> Package php-imap.x86_64 0:5.3.3-40.el6_6 will be updated
---> Package php-imap.x86_64 0:5.4.16-2.el7 will be an update
--> Processing Dependency: php(zend-abi) = 20100525-64 for package: php-imap-5.4.16-2.el7.x86_64
--> Processing Dependency: php(api) = 20100412-64 for package: php-imap-5.4.16-2.el7.x86_64
---> Package pigz.x86_64 0:2.2.5-1.el6 will be updated
---> Package pigz.x86_64 0:2.3.1-1.el7 will be an update
--> Processing Dependency: libz.so.1(ZLIB_1.2.5.1)(64bit) for package: pigz-2.3.1-1.el7.x86_64
---> Package vconfig.x86_64 0:1.9-8.1.el6 will be updated
---> Package vconfig.x86_64 0:1.9-16.el7 will be an update
---> Package wireless-tools.x86_64 1:29-5.1.1.el6 will be updated
---> Package wireless-tools.x86_64 1:29-13.el7 will be an update
--> Running transaction check
---> Package db4.x86_64 0:4.7.25-18.el6_4 will be obsoleted
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: psa-courier-imap-4.15-cos6.build1200150114.15.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd-tools-2.2.15-39.el6.centos.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-15.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-2.6.32-33.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd-2.2.15-39.el6.centos.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.1-20.el6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: python-libs-2.6.6-52.el6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: subversion-1.6.11-12.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: 4:perl-5.10.1-136.el6_6.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.3.9-3.el6_0.1.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python-4.8.0-38.el6_6.x86_64
--> Processing Dependency: libdb-4.7.so()(64bit) for package: 2:postfix-2.8.17-14042513.x86_64
---> Package mod_perl.x86_64 0:2.0.8-10.20140624svn1602105.el7 will be an update
--> Processing Dependency: httpd-mmn = 20120211x8664 for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
--> Processing Dependency: perl(:MODULE_COMPAT_5.16.3) for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
--> Processing Dependency: libdb-5.3.so()(64bit) for package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64
---> Package perl-BSD-Resource.x86_64 0:1.29.07-1.el7 will be an update
--> Processing Dependency: perl(:MODULE_COMPAT_5.16.3) for package: perl-BSD-Resource-1.29.07-1.el7.x86_64
---> Package perl-Linux-Pid.x86_64 0:0.04-18.el7 will be installed
--> Processing Dependency: perl(:MODULE_COMPAT_5.16.3) for package: perl-Linux-Pid-0.04-18.el7.x86_64
---> Package php-imap.x86_64 0:5.4.16-2.el7 will be an update
--> Processing Dependency: php(zend-abi) = 20100525-64 for package: php-imap-5.4.16-2.el7.x86_64
--> Processing Dependency: php(api) = 20100412-64 for package: php-imap-5.4.16-2.el7.x86_64
---> Package pigz.x86_64 0:2.3.1-1.el7 will be an update
--> Processing Dependency: libz.so.1(ZLIB_1.2.5.1)(64bit) for package: pigz-2.3.1-1.el7.x86_64
--> Processing Conflict: libdb4-4.8.30-13.el7.x86_64 conflicts filesystem < 3
--> Finished Dependency Resolution
--> Finding unneeded leftover dependencies
Found and removing 0 unneeded dependencies
Error: Package: iproute-2.6.32-33.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: httpd-tools-2.2.15-39.el6.centos.x86_64 (@base)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: 2:postfix-2.8.17-14042513.x86_64 (@PSA_12_0_18-dist)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: rpm-build-4.8.0-38.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: rpm-libs-4.8.0-38.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: php-imap-5.4.16-2.el7.x86_64 (epel)
           Requires: php(zend-abi) = 20100525-64
           Installed: php-common-5.3.3-40.el6_6.x86_64 (@updates)
               php(zend-abi) = 20090626
           Available: php-common-5.3.3-38.el6.x86_64 (base)
               php(zend-abi) = 20090626
Error: Package: 4:perl-5.10.1-136.el6_6.1.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: pigz-2.3.1-1.el7.x86_64 (epel)
           Requires: libz.so.1(ZLIB_1.2.5.1)(64bit)
Error: Package: httpd-2.2.15-39.el6.centos.x86_64 (@base)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: python-libs-2.6.6-52.el6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: perl-Linux-Pid-0.04-18.el7.x86_64 (epel)
           Requires: perl(:MODULE_COMPAT_5.16.3)
Error: Package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64 (epel)
           Requires: httpd-mmn = 20120211x8664
           Installed: httpd-2.2.15-39.el6.centos.x86_64 (@base)
               httpd-mmn = 20051115
Error: Package: php-imap-5.4.16-2.el7.x86_64 (epel)
           Requires: php(api) = 20100412-64
           Installed: php-common-5.3.3-40.el6_6.x86_64 (@updates)
               php(api) = 20090626
           Available: php-common-5.3.3-38.el6.x86_64 (base)
               php(api) = 20090626
Error: Package: subversion-1.6.11-12.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: apr-util-1.3.9-3.el6_0.1.x86_64 (@base)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: libdb4 conflicts with filesystem-2.4.30-3.el6.x86_64
Error: Package: perl-BSD-Resource-1.29.07-1.el7.x86_64 (epel)
           Requires: perl(:MODULE_COMPAT_5.16.3)
Error: Package: pam-1.1.1-20.el6.x86_64 (@base)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: psa-courier-imap-4.15-cos6.build1200150114.15.x86_64 (@PSA_12_0_18-dist)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64 (epel)
           Requires: perl(:MODULE_COMPAT_5.16.3)
Error: Package: mod_perl-2.0.8-10.20140624svn1602105.el7.x86_64 (epel)
           Requires: libdb-5.3.so()(64bit)
Error: Package: rpm-python-4.8.0-38.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: cyrus-sasl-2.1.23-15.el6_6.1.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
Error: Package: rpm-4.8.0-38.el6_6.x86_64 (@updates)
           Requires: libdb-4.7.so()(64bit)
           Removing: db4-4.7.25-18.el6_4.x86_64 (@base)
               libdb-4.7.so()(64bit)
           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

How can I fix my dependencies so everything updates properly?

asked Feb 14, 2015 at 4:15

Nahydrin's user avatar

It appears you have a Centos 6 machine but have configured the Epel repository for Centos 7. That is not going to work. Remove it and install the Centos 6 Epel Repository at:

wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

Make sure you uninstall anything you added from the Centos 7 Epel repository as well.

That should do it.

answered Feb 14, 2015 at 5:00

Ricardo's user avatar

RicardoRicardo

7395 silver badges6 bronze badges

1

Run the following:

yum remove epel-release

Then run:

yum update

That should fix your problem.

Giacomo1968's user avatar

answered Feb 14, 2015 at 20:26

Emmanuel's user avatar

1

It was true that I mistakenly used Epel repository for Centos 7 in Centos 6 machine. And I tried above solution but they did the trick half way. Here is what finally worked for me.

  1. yum remove epel-release
  2. rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/Packages/e/epel-release-6-8.noarch.rpm
  3. yum clean all
  4. yum repolist
  5. yum update -y

Giacomo1968's user avatar

answered Apr 13, 2018 at 10:17

Aanokpe Rai's user avatar

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

Понравилась статья? Поделить с друзьями:

Интересное по теме:

  • Centos ошибка при настройке базового репозитория
  • Centos 7 проверка файловой системы на ошибки
  • Cem e001 ошибка
  • Center position is no good ошибка фанук
  • Centek мультиварка коды ошибок

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии