Gelöst: yum update: Konflikt --skip-broken?

DiViNe

DiViNe

Mitglied
Guten Morgen

Ich kann kein yum update mehr durchführen. :hilfe:

Anfangs stand auch etwas von Problemen mit libgcrypt drinn. Habe darum folgendes gemacht:
rpm --erase --nodeps libgcrypt-1.5.3-13.el7_3.1.x86_64 libgcrypt-1.5.3-14.el7.x86_64 libgcrypt-1.5.3-14.el7.i686
yum install libgcrypt




yum update
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: centos.bio.lmu.de
* epel: epel.besthosting.ua
* extras: artfiles.org
* updates: centos.mirror.iphh.net
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket NetworkManager.x86_64 1:1.4.0-20.el7_3 markiert, um veraltet zu werden

[...] wegen der Länge habe ich diese Einträge gekürzt
---> Paket gtk-update-icon-cache.x86_64 0:3.22.10-4.el7 markiert, um aktualisiert zu werden
---> Paket kernel.x86_64 0:3.10.0-514.el7 markiert, um gelöscht zu werden
---> Paket systemd.x86_64 0:219-42.el7_4.4 markiert, um aktualisiert zu werden
---> Paket systemd.x86_64 0:219-42.el7_4.4 markiert, um aktualisiert zu werden
--> Konflikt wird verarbeitet: systemd-219-42.el7_4.10.x86_64 kollidiert mit dracut < 033-499
--> Konflikt wird verarbeitet: gtk-update-icon-cache-3.22.10-5.el7_4.x86_64 kollidiert mit gtk2 < 2.24.29

--> Abhängigkeitsauflösung beendet
Fehler: systemd conflicts with dracut-033-463.el7_3.2.x86_64
Fehler: gtk-update-icon-cache conflicts with gtk2-2.24.28-8.el7.x86_64
Sie können versuchen, mit --skip-broken das Problem zu umgehen.

** 287 bereits bestehende(s) rpmdb Problem(e) gefunden, »yum check« gibt Folgendes aus:
1:NetworkManager-1.8.0-11.el7_4.x86_64 ist ein Duplikat von 1:NetworkManager-1.4.0-20.el7_3.x86_64
1:NetworkManager-libnm-1.8.0-11.el7_4.x86_64 ist ein Duplikat von 1:NetworkManager-libnm-1.4.0-20.el7_3.x86_64
alsa-lib-1.1.3-3.el7.x86_64 ist ein Duplikat von alsa-lib-1.1.1-1.el7.x86_64
apr-1.4.8-3.el7_4.1.x86_64 ist ein Duplikat von apr-1.4.8-3.el7.x86_64

[...] wegen der Länge habe ich diese Einträge gekürzt
yum-3.4.3-154.el7.centos.noarch ist ein Duplikat von yum-3.4.3-150.el7.centos.noarch
yum-plugin-fastestmirror-1.1.31-42.el7.noarch ist ein Duplikat von yum-plugin-fastestmirror-1.1.31-40.el7.noarch



Kann man sagen wie es zu diesem Problem gekommen ist?

Ich möchte es nicht verschlimmern und Frage mich, ob ich diese Patkete
dracut-033-463.el7_3.2.x86_64
gtk2-2.24.28-8.el7.x86_64

mit rpm --erase --nodeps löschen soll, oder yum update --skip-borken machen soll.
Oder gibt es eine ander Lösung für das Problem?

Danke für eure Hilfe.
 
Hi Marce

Danke für dein Input. Habe yum clean all ausgeführt. Nebst den bestehenden Fehlermeldungen motzt er noch wegen Repos die er nicht findet.:


yum update
Geladene Plugins: fastestmirror
base | 3.6 kB 00:00:00
epel/x86_64/metalink | 25 kB 00:00:00
epel | 4.7 kB 00:00:00
extras | 3.4 kB 00:00:00
updates | 3.4 kB 00:00:00
(1/7): base/7/x86_64/group_gz | 156 kB 00:00:00
(2/7): epel/x86_64/group_gz | 266 kB 00:00:00
epel/x86_64/primary_db FAILED
https://mirror.imt-systems.com/epel...6b87332e113370c4cb6743b89f-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found ] 0.0 B/s | 0 B --:--:-- ETA
Anderer Spiegelserver wird versucht.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/articles/1320623

If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/

epel/x86_64/updateinfo FAILED
https://ftp.fau.de/epel/7/x86_64/re...cb4565e897e2c458ce90beed1f-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found ] 0.0 B/s | 0 B --:--:-- ETA
Anderer Spiegelserver wird versucht.
epel/x86_64/updateinfo FAILED
https://mirror.imt-systems.com/epel...cb4565e897e2c458ce90beed1f-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found ] 0.0 B/s | 0 B --:--:-- ETA
Anderer Spiegelserver wird versucht.
(3/7): extras/7/x86_64/primary_db | 185 kB 00:00:00
epel/x86_64/updateinfo FAILED 9% [========= ] 0.0 B/s | 2.0 MB --:--:-- ETA
http://mirror.euserv.net/linux/fedo...cb4565e897e2c458ce90beed1f-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found ] 0.0 B/s | 2.0 MB --:--:-- ETA
Anderer Spiegelserver wird versucht.
(4/7): epel/x86_64/primary_db | 6.3 MB 00:00:00
(5/7): epel/x86_64/updateinfo | 915 kB 00:00:00
(6/7): base/7/x86_64/primary_db | 5.7 MB 00:00:01
(7/7): updates/7/x86_64/primary_db | 6.9 MB 00:00:01
Determining fastest mirrors
* base: centos.alpha-labs.net
* epel: epel.besthosting.ua
* extras: centos.alpha-labs.net
* updates: centos.mirrors.psw.services
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket NetworkManager.x86_64 1:1.4.0-20.el7_3 markiert, um veraltet zu werden


Ab hier folgt dann wieder der gleiche Output wie oben.
 
Poste bitte mal Deine /etc/redhat-release, den Inhalt von /etc/yum.repos.d/ (und ggf. den Inhalt aller Dateien dort) und die komplette Ausgabe von yum update.

Verwende bitte [ code]-Tags dafür.

Alternativ binde das epel-Repo nochmals komplett neu ein.
 
Gerne:

/etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

/etc/yum.repos.d/
-rw-r--r--. 1 root root 3830 30. Aug 2017 CentOS-Vault.repo
Code:
# CentOS Vault contains rpms from older releases in the CentOS-7
# tree.

#c7.0.1406
[C7.0.1406-base]
name=CentOS-7.0.1406 - Base
baseurl=http://vault.centos.org/7.0.1406/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.0.1406-updates]
name=CentOS-7.0.1406 - Updates
baseurl=http://vault.centos.org/7.0.1406/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.0.1406-extras]
name=CentOS-7.0.1406 - Extras
baseurl=http://vault.centos.org/7.0.1406/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.0.1406-centosplus]
name=CentOS-7.0.1406 - CentOSPlus
baseurl=http://vault.centos.org/7.0.1406/centosplus/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.0.1406-fasttrack]
name=CentOS-7.0.1406 - CentOSPlus
baseurl=http://vault.centos.org/7.0.1406/fasttrack/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

# C7.1.1503
[C7.1.1503-base]
name=CentOS-7.1.1503 - Base
baseurl=http://vault.centos.org/7.1.1503/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.1.1503-updates]
name=CentOS-7.1.1503 - Updates
baseurl=http://vault.centos.org/7.1.1503/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.1.1503-extras]
name=CentOS-7.1.1503 - Extras
baseurl=http://vault.centos.org/7.1.1503/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.1.1503-centosplus]
name=CentOS-7.1.1503 - CentOSPlus
baseurl=http://vault.centos.org/7.1.1503/centosplus/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.1.1503-fasttrack]
name=CentOS-7.1.1503 - CentOSPlus
baseurl=http://vault.centos.org/7.1.1503/fasttrack/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

# C7.2.1511
[C7.2.1511-base]
name=CentOS-7.2.1511 - Base
baseurl=http://vault.centos.org/7.2.1511/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.2.1511-updates]
name=CentOS-7.2.1511 - Updates
baseurl=http://vault.centos.org/7.2.1511/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.2.1511-extras]
name=CentOS-7.2.1511 - Extras
baseurl=http://vault.centos.org/7.2.1511/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.2.1511-centosplus]
name=CentOS-7.2.1511 - CentOSPlus
baseurl=http://vault.centos.org/7.2.1511/centosplus/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.2.1511-fasttrack]
name=CentOS-7.2.1511 - CentOSPlus
baseurl=http://vault.centos.org/7.2.1511/fasttrack/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

# C7.3.1611
[C7.3.1611-base]
name=CentOS-7.3.1611 - Base
baseurl=http://vault.centos.org/7.3.1611/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.3.1611-updates]
name=CentOS-7.3.1611 - Updates
baseurl=http://vault.centos.org/7.3.1611/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.3.1611-extras]
name=CentOS-7.3.1611 - Extras
baseurl=http://vault.centos.org/7.3.1611/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.3.1611-centosplus]
name=CentOS-7.3.1611 - CentOSPlus
baseurl=http://vault.centos.org/7.3.1611/centosplus/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

[C7.3.1611-fasttrack]
name=CentOS-7.3.1611 - CentOSPlus
baseurl=http://vault.centos.org/7.3.1611/fasttrack/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0

-rw-r--r--. 1 root root 1331 30. Aug 2017 CentOS-Sources.repo
Code:
# CentOS-Sources.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base-source]
name=CentOS-$releasever - Base Sources
baseurl=http://vault.centos.org/centos/$releasever/os/Source/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates-source]
name=CentOS-$releasever - Updates Sources
baseurl=http://vault.centos.org/centos/$releasever/updates/Source/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras-source]
name=CentOS-$releasever - Extras Sources
baseurl=http://vault.centos.org/centos/$releasever/extras/Source/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that extend functionality of existing packages
[centosplus-source]
name=CentOS-$releasever - Plus Sources
baseurl=http://vault.centos.org/centos/$releasever/centosplus/Source/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
 
-rw-r--r--. 1 root root 630 30. Aug 2017 CentOS-Media.repo
Code:
# CentOS-Media.repo
#
#  This repo can be used with mounted DVD media, verify the mount point for
#  CentOS-7.  You can use this repo and yum to install items directly off the
#  DVD ISO that we release.
#
# To use this repo, put in your DVD and use it with the other repos too:
#  yum --enablerepo=c7-media [command]
#
# or for ONLY the media repo, do this:
#
#  yum --disablerepo=\* --enablerepo=c7-media [command]

[c7-media]
name=CentOS-$releasever - Media
baseurl=file:///media/CentOS/
        file:///media/cdrom/
        file:///media/cdrecorder/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7


-rw-r--r--. 1 root root 314 30. Aug 2017 CentOS-fasttrack.repo
Code:
# CentOS-Media.repo
#
#  This repo can be used with mounted DVD media, verify the mount point for
#  CentOS-7.  You can use this repo and yum to install items directly off the
#  DVD ISO that we release.
#
# To use this repo, put in your DVD and use it with the other repos too:
#  yum --enablerepo=c7-media [command]
#
# or for ONLY the media repo, do this:
#
#  yum --disablerepo=\* --enablerepo=c7-media [command]

[c7-media]
name=CentOS-$releasever - Media
baseurl=file:///media/CentOS/
        file:///media/cdrom/
        file:///media/cdrecorder/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#cat CentOS-fasttrack.repo
#CentOS-fasttrack.repo

[fasttrack]
name=CentOS-7 - fasttrack
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=fasttrack&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/fasttrack/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7


-rw-r--r--. 1 root root 649 30. Aug 2017 CentOS-Debuginfo.repo
Code:
#CentOS-fasttrack.repo

[fasttrack]
name=CentOS-7 - fasttrack
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=fasttrack&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/fasttrack/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[root@chdcvshare01 yum.repos.d]#cat CentOS-Debuginfo.repo
# CentOS-Debug.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#

# All debug packages from all the various CentOS-7 releases
# are merged into a single repo, split by BaseArch
#
# Note: packages in the debuginfo repo are currently not signed
#

[base-debuginfo]
name=CentOS-7 - Debuginfo
baseurl=http://debuginfo.centos.org/7/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-Debug-7
ena



-rw-r--r--. 1 root root 1309 30. Aug 2017 CentOS-CR.repo
Code:
# CentOS-CR.repo
#
# The Continuous Release ( CR )  repository contains rpms that are due in the next
# release for a specific CentOS Version ( eg. next release in CentOS-7 ); these rpms
# are far less tested, with no integration checking or update path testing having
# taken place. They are still built from the upstream sources, but might not map
# to an exact upstream distro release.
#
# These packages are made available soon after they are built, for people willing
# to test their environments, provide feedback on content for the next release, and
# for people looking for early-access to next release content.
#
# The CR repo is shipped in a disabled state by default; its important that users
# understand the implications of turning this on.
#
# NOTE: We do not use a mirrorlist for the CR repos, to ensure content is available
#       to everyone as soon as possible, and not need to wait for the external
#       mirror network to seed first. However, many local mirrors will carry CR repos
#       and if desired you can use one of these local mirrors by editing the baseurl
#       line in the repo config below.
#

[cr]
name=CentOS-$releasever - cr
baseurl=http://mirror.centos.org/centos/$releasever/cr/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=0


-rw-r--r--. 1 root root 1664 30. Aug 2017 CentOS-Base.repo
Code:
# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates]
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7



-rw-r--r--. 1 root root 1050 2. Okt 2017 epel-testing.repo
Code:
[epel-testing]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/$basearch
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

[epel-testing-debuginfo]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/$basearch/debug
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-debug-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

[epel-testing-source]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/SRPMS
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-source-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1


-rw-r--r--. 1 root root 951 2. Okt 2017 epel.repo
Code:
[epel-testing]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/$basearch
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

[epel-testing-debuginfo]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/$basearch/debug
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-debug-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

[epel-testing-source]
name=Extra Packages for Enterprise Linux 7 - Testing - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/testing/7/SRPMS
metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-source-epel7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#
[root@chdcvshare01 yum.repos.d]#cat epel.repo
[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

[epel-debuginfo]
name=Extra Packages for Enterprise Linux 7 - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch/debug
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

[epel-source]
name=Extra Packages for Enterprise Linux 7 - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/7/SRPMS
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-source-7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1



Max Zeichen von 1000 wurde erreicht, deshalb in zwei Posts
 
Alternativ binde das epel-Repo nochmals komplett neu ein.

Habe es neu eingebunden. Hier für die Mitleser als info:
Code:
ls -l /etc/yum.repos.d/
    epel-testing.repo
   
rpm -qf /etc/yum.repos.d/epel-testing.repo
    epel-release-7-10.noarch
    epel-release-7-11.noarch

yum remove epel-release-7-10.noarch epel-release-7-11.noarc


wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
rpm -ivh epel-release-latest-7.noarch.rpm

yum repolist
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.alpha-labs.net
 * epel: epel.besthosting.ua
 * extras: centos.alpha-labs.net
 * updates: centos.mirrors.psw.services
Repo-ID                                                                                            Repo-Name:                                                                                                                      Status
!base/7/x86_64                                                                                     CentOS-7 - Base                                                                                                                  9'591
!epel/x86_64                                                                                       Extra Packages for Enterprise Linux 7 - x86_64                                                                                  12'491
!extras/7/x86_64                                                                                   CentOS-7 - Extras                                                                                                                  448
!updates/7/x86_64

Diese Fehler sind nun weg:
epel/x86_64/updateinfo FAILED 9% [========= ] 0.0 B/s | 2.0 MB --:--:-- ETA

Die Fehler siehe oben, bzw hier:
Code:
--> Konflikt wird verarbeitet: systemd-219-42.el7_4.10.x86_64 kollidiert mit dracut < 033-499
--> Konflikt wird verarbeitet: gtk-update-icon-cache-3.22.10-5.el7_4.x86_64 kollidiert mit gtk2 < 2.24.29

sowie

Code:
             ist ein Duplikat

bestehen aber noch
 
hast Du in der yum.conf irgendeine exclude-Anweisung drin oder sowas ähnliches? Was sagt uname -a bei Dir bzw. ein yum info zu den problematischen Paketen?

Bitte poste die komplette Ausgabe von yum update.
 
Gerne:

uname -a
Code:
Linux chdcvshare01.ch.viamat.com 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Nein, ein ganz normales yum.conf

yum update ausgabe ist 1:1 das geliche wie im posting oben. Einzig die Fehlermeldung ist weg:
epel/x86_64/updateinfo FAILED 9% [========= ] 0.0 B/s | 2.0 MB --:--:-- ETA


yum info macht eine sehr lange Ausgabe. Kann diese auch nicht mit der Code-Formatierung hier posten, da nicht erlaubt (zu lange). Hat aber auch keine Fehlerinfos drinn.
 
???
Code:
yum info dracut
z.B. liefert hier ca. 20 Zeilen...

und bitte, poste die komplette aktuelle Ausgabe von yum update - ich will mir das hier nicht aus mehr oder weniger vielen, unvollständigen Posts zusammensuchen müssen... Wenn ich darauf Lust hätte würde ich Dicht nicht darum bitten.
 
Code:
yum info dracut
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.intergenia.de
 * epel: epel.besthosting.ua
 * extras: de.mirror.guru
 * updates: de.mirror.guru
Installierte Pakete
Name       : dracut
Architektur : x86_64
Version    : 033
Ausgabe    : 463.el7_3.2
Größe : 866 k
Quelle      : installed
Aus Quelle  : updates
Zusammenfassung: Initramfs generator using udev
URL        : https://dracut.wiki.kernel.org/
Lizenz      : GPLv2+ and LGPLv2+
Beschreibung: dracut contains tools to create a bootable initramfs for 2.6 Linux kernels.
            : Unlike existing implementations, dracut does hard-code as little as possible
            : into the initramfs. dracut contains various modules which are driven by the
            : event-based udev. Having root on MD, DM, LVM2, LUKS is supported as well as
            : NFS, iSCSI, NBD, FCoE with the dracut-network package.

Name       : dracut
Architektur : x86_64
Version    : 033
Ausgabe    : 502.el7_4.1
Größe : 874 k
Quelle      : installed
Zusammenfassung: Initramfs generator using udev
URL        : https://dracut.wiki.kernel.org/
Lizenz      : GPLv2+ and LGPLv2+
Beschreibung: dracut contains tools to create a bootable initramfs for 2.6 Linux kernels.
            : Unlike existing implementations, dracut does hard-code as little as possible
            : into the initramfs. dracut contains various modules which are driven by the
            : event-based udev. Having root on MD, DM, LVM2, LUKS is supported as well as
            : NFS, iSCSI, NBD, FCoE with the dracut-network package.


Folgende Fehler sind aufgetreten:
Dieser Beitrag ist zu lang um verarbeitet zu werden. Bitte kürze ihn.

Dies passiert auch wenn ich den CODE benutze.
 
Hey Marce!

Danke für dein Input.

Ich war gerade in den Ferien, deshalb erst jetzt meine Antwort.
Den Threat habe ich auch gefunden, hatte einfach ein wenig angst alles die Einträge in der DB zu löschen. Aber wenn es keine andere/sicherer Methode gibt, dann werde ich diese ausprobieren.

LG
 
Hallo

Habe mir folgendes Scipt gemacht:

Code:
for vari in `cat /root/packete.txt`; do rpm -e --justdb --nodeps "$vari"; done
In der Text-Datei waren alle Pakete drinn. Dies hat geholfen, es geht wieder. Besten Dank.


==== Threat Closed ====
 

Ähnliche Themen

Fedora 20 - Unlösbare Paket-Duplikat Konflikte

Wieder mal Probleme mit yum

Gnome Classic Desktop: Home-Inhalt Icons ausblenden

Zurück
Oben