|
Description of problem:
ERROR with transaction check vs depsolve:
Version-Release number of selected component (if applicable):
yum --version
3.4.3
Installed: rpm-4.10.3.1-1.fc18.x86_64 at 2013-02-12 16:17
Built : Fedora Project at 2013-02-06 09:54
Committed: Panu Matilainen <pmatilai> at 2013-02-06
Installed: yum-3.4.3-49.fc18.noarch at 2013-02-14 05:02
Built : Fedora Project at 2013-02-06 10:06
Committed: Zdenek Pavlas <zpavlas> at 2013-02-06
Installed: yum-plugin-fastestmirror-1.1.31-9.fc18.noarch at 2013-02-14 05:03
Built : Fedora Project at 2013-02-08 09:05
Committed: Zdenek Pavlas <zpavlas> at 2013-02-08
How reproducible:
yum -y update
Steps to Reproduce:
1. yum -y update
2.
3.
Actual results:
# yum -y update
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
adobe-linux-i386 | 951 B 00:00:00
adobe-linux-x86_64 | 951 B 00:00:00
fedora/18/x86_64/metalink | 21 kB 00:00:00
fedora-chromium | 3.4 kB 00:00:00
http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-18/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-18/x86_64/repodata/repomd.xml
Trying other mirror.
google-chrome | 951 B 00:00:00
jenkins | 951 B 00:00:00
rpmfusion-free-updates | 3.3 kB 00:00:00
rpmfusion-nonfree-updates | 3.3 kB 00:00:00
updates/18/x86_64/metalink | 14 kB 00:00:00
rpmfusion-free-updates/primary_db | 83 kB 00:00:00
Loading mirror speeds from cached hostfile
* fedora: archive.linux.duke.edu
* rpmfusion-free: mirror.nexcess.net
* rpmfusion-free-updates: mirror.nexcess.net
* rpmfusion-nonfree: mirror.nexcess.net
* rpmfusion-nonfree-updates: mirror.nexcess.net
* updates: fedora.mirrors.pair.com
Resolving Dependencies
--> Running transaction check
---> Package ModemManager.x86_64 0:0.6.0.0-2.fc18 will be updated
---> Package ModemManager.x86_64 0:0.6.0.0-3.fc18 will be an update
---> Package NetworkManager.x86_64 1:0.9.7.0-12.git20121004.fc18 will be updated
---> Package NetworkManager.x86_64 1:0.9.7.997-2.fc18 will be an update
---> Package NetworkManager-glib.x86_64 1:0.9.7.0-12.git20121004.fc18 will be updated
---> Package NetworkManager-glib.x86_64 1:0.9.7.997-2.fc18 will be an update
---> Package cairo.i686 0:1.12.10-2.fc18 will be updated
---> Package cairo.x86_64 0:1.12.10-2.fc18 will be updated
---> Package cairo.i686 0:1.12.14-1.fc18 will be an update
---> Package cairo.x86_64 0:1.12.14-1.fc18 will be an update
---> Package cairo-devel.x86_64 0:1.12.10-2.fc18 will be updated
---> Package cairo-devel.x86_64 0:1.12.14-1.fc18 will be an update
---> Package cairo-gobject.i686 0:1.12.10-2.fc18 will be updated
---> Package cairo-gobject.x86_64 0:1.12.10-2.fc18 will be updated
---> Package cairo-gobject.i686 0:1.12.14-1.fc18 will be an update
---> Package cairo-gobject.x86_64 0:1.12.14-1.fc18 will be an update
---> Package cairo-gobject-devel.x86_64 0:1.12.10-2.fc18 will be updated
---> Package cairo-gobject-devel.x86_64 0:1.12.14-1.fc18 will be an update
---> Package cvs.x86_64 0:1.11.23-26.fc18 will be updated
---> Package cvs.x86_64 0:1.11.23-29.fc18 will be an update
---> Package evolution-data-server.x86_64 0:3.6.3-1.fc18 will be updated
---> Package evolution-data-server.x86_64 0:3.6.3-2.fc18 will be an update
---> Package evolution-data-server-devel.x86_64 0:3.6.3-1.fc18 will be updated
---> Package evolution-data-server-devel.x86_64 0:3.6.3-2.fc18 will be an update
---> Package exempi.x86_64 0:2.2.0-5.fc18 will be updated
---> Package exempi.x86_64 0:2.2.0-6.fc18 will be an update
---> Package finger.x86_64 0:0.17-47.fc18 will be updated
---> Package finger.x86_64 0:0.17-48.fc18 will be an update
---> Package gimp.x86_64 2:2.8.2-6.fc18 will be updated
---> Package gimp.x86_64 2:2.8.4-1.fc18 will be an update
---> Package gimp-libs.x86_64 2:2.8.2-6.fc18 will be updated
---> Package gimp-libs.x86_64 2:2.8.4-1.fc18 will be an update
---> Package google-chrome-stable.x86_64 0:24.0.1312.70-181759 will be updated
---> Package google-chrome-stable.x86_64 0:25.0.1364.97-183676 will be an update
---> Package gstreamer1-plugins-good.x86_64 0:1.0.5-1.fc18 will be updated
---> Package gstreamer1-plugins-good.x86_64 0:1.0.5-3.fc18 will be an update
---> Package harfbuzz.i686 0:0.9.9-1.fc18 will be updated
---> Package harfbuzz.x86_64 0:0.9.9-1.fc18 will be updated
---> Package harfbuzz.i686 0:0.9.12-2.fc18 will be an update
--> Processing Dependency: libgraphite2.so.2.0.0 for package: harfbuzz-0.9.12-2.fc18.i686
---> Package harfbuzz.x86_64 0:0.9.12-2.fc18 will be an update
---> Package harfbuzz-devel.x86_64 0:0.9.9-1.fc18 will be updated
---> Package harfbuzz-devel.x86_64 0:0.9.12-2.fc18 will be an update
---> Package httpd.x86_64 0:2.4.3-12.fc18 will be updated
---> Package httpd.x86_64 0:2.4.3-15.fc18 will be an update
---> Package httpd-devel.x86_64 0:2.4.3-12.fc18 will be updated
---> Package httpd-devel.x86_64 0:2.4.3-15.fc18 will be an update
---> Package httpd-manual.noarch 0:2.4.3-12.fc18 will be updated
---> Package httpd-manual.noarch 0:2.4.3-15.fc18 will be an update
---> Package httpd-tools.x86_64 0:2.4.3-12.fc18 will be updated
---> Package httpd-tools.x86_64 0:2.4.3-15.fc18 will be an update
---> Package ibus.x86_64 0:1.4.99.20121109-9.fc18 will be updated
---> Package ibus.x86_64 0:1.5.1-2.fc18 will be an update
---> Package ibus-anthy.x86_64 0:1.4.99.20121006-1.fc18 will be updated
---> Package ibus-anthy.x86_64 0:1.5.0-1.fc18 will be an update
---> Package ibus-gtk2.x86_64 0:1.4.99.20121109-9.fc18 will be updated
---> Package ibus-gtk2.x86_64 0:1.5.1-2.fc18 will be an update
---> Package ibus-gtk3.x86_64 0:1.4.99.20121109-9.fc18 will be updated
---> Package ibus-gtk3.x86_64 0:1.5.1-2.fc18 will be an update
---> Package ibus-libs.x86_64 0:1.4.99.20121109-9.fc18 will be updated
---> Package ibus-libs.x86_64 0:1.5.1-2.fc18 will be an update
---> Package jcifs.noarch 0:1.3.17-5.fc18 will be updated
---> Package jcifs.noarch 0:1.3.17-7.fc18 will be an update
---> Package kernel.x86_64 0:3.7.9-201.fc18 will be installed
---> Package kernel-devel.x86_64 0:3.7.9-201.fc18 will be installed
---> Package kernel-headers.x86_64 0:3.7.7-201.fc18 will be updated
---> Package kernel-headers.x86_64 0:3.7.9-201.fc18 will be an update
---> Package kernel-tools.x86_64 0:3.7.7-201.fc18 will be updated
---> Package kernel-tools.x86_64 0:3.7.9-201.fc18 will be an update
---> Package kernel-tools-libs.x86_64 0:3.7.7-201.fc18 will be updated
---> Package kernel-tools-libs.x86_64 0:3.7.9-201.fc18 will be an update
---> Package libchewing.x86_64 0:0.3.3-5.fc18 will be updated
---> Package libchewing.x86_64 0:0.3.4-2.fc18 will be an update
---> Package libgphoto2.i686 0:2.5.0-3.fc18 will be updated
---> Package libgphoto2.x86_64 0:2.5.0-3.fc18 will be updated
---> Package libgphoto2.i686 0:2.5.0-7.fc18 will be an update
---> Package libgphoto2.x86_64 0:2.5.0-7.fc18 will be an update
---> Package libnm-gtk.x86_64 0:0.9.7.0-6.git20121211.fc18 will be updated
---> Package libnm-gtk.x86_64 0:0.9.7.997-1.fc18 will be an update
---> Package libqb.x86_64 0:0.14.3-2.fc18 will be updated
---> Package libqb.x86_64 0:0.14.4-1.fc18 will be an update
---> Package libuser.x86_64 0:0.58-1.fc18 will be updated
---> Package libuser.x86_64 0:0.58-2.fc18 will be an update
---> Package libuser-devel.x86_64 0:0.58-1.fc18 will be updated
---> Package libuser-devel.x86_64 0:0.58-2.fc18 will be an update
---> Package libuser-python.x86_64 0:0.58-1.fc18 will be updated
---> Package libuser-python.x86_64 0:0.58-2.fc18 will be an update
---> Package linuxconsoletools.x86_64 0:1.4.4-4.fc18 will be updated
---> Package linuxconsoletools.x86_64 0:1.4.4-7.fc18 will be an update
---> Package lohit-assamese-fonts.noarch 0:2.5.2-1.fc18 will be updated
---> Package lohit-assamese-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-bengali-fonts.noarch 0:2.5.2-1.fc18 will be updated
---> Package lohit-bengali-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-devanagari-fonts.noarch 0:2.5.2-1.fc18 will be updated
---> Package lohit-devanagari-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-kannada-fonts.noarch 0:2.5.1-4.fc18 will be updated
---> Package lohit-kannada-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-oriya-fonts.noarch 0:2.5.1-2.fc18 will be updated
---> Package lohit-oriya-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-punjabi-fonts.noarch 0:2.5.1-3.fc18 will be updated
---> Package lohit-punjabi-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-tamil-fonts.noarch 0:2.5.1-3.fc18 will be updated
---> Package lohit-tamil-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package lohit-telugu-fonts.noarch 0:2.5.2-1.fc18 will be updated
---> Package lohit-telugu-fonts.noarch 0:2.5.3-1.fc18 will be an update
---> Package minicom.x86_64 0:2.5-8.fc17 will be updated
---> Package minicom.x86_64 0:2.5-10.fc18 will be an update
---> Package mod_ssl.x86_64 1:2.4.3-12.fc18 will be updated
---> Package mod_ssl.x86_64 1:2.4.3-15.fc18 will be an update
---> Package network-manager-applet.x86_64 0:0.9.7.0-6.git20121211.fc18 will be updated
---> Package network-manager-applet.x86_64 0:0.9.7.997-1.fc18 will be an update
---> Package nm-connection-editor.x86_64 0:0.9.7.0-6.git20121211.fc18 will be updated
---> Package nm-connection-editor.x86_64 0:0.9.7.997-1.fc18 will be an update
---> Package ntfs-3g.x86_64 2:2012.1.15-5.fc18 will be updated
---> Package ntfs-3g.x86_64 2:2013.1.13-1.fc18.1 will be an update
---> Package ntfsprogs.x86_64 2:2012.1.15-5.fc18 will be updated
---> Package ntfsprogs.x86_64 2:2013.1.13-1.fc18.1 will be an update
---> Package numpy.x86_64 1:1.7.0-0.5.rc1.fc18 will be updated
---> Package numpy.x86_64 1:1.7.0-1.fc18 will be an update
---> Package paktype-naqsh-fonts.noarch 0:4.0-2.fc18 will be updated
---> Package paktype-naqsh-fonts.noarch 0:4.0-3.fc18 will be an update
---> Package paktype-tehreer-fonts.noarch 0:4.0-2.fc18 will be updated
---> Package paktype-tehreer-fonts.noarch 0:4.0-3.fc18 will be an update
---> Package phonon-backend-gstreamer.x86_64 2:4.6.2-2.fc18 will be updated
---> Package phonon-backend-gstreamer.x86_64 2:4.6.3-1.fc18 will be an update
---> Package pulseaudio.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-gdm-hooks.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-gdm-hooks.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-libs.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-libs.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-libs-glib2.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-libs-glib2.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-module-bluetooth.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-module-bluetooth.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-module-gconf.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-module-gconf.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-module-jack.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-module-jack.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-module-x11.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-module-x11.x86_64 0:2.1-6.fc18 will be an update
---> Package pulseaudio-utils.x86_64 0:2.1-5.fc18 will be updated
---> Package pulseaudio-utils.x86_64 0:2.1-6.fc18 will be an update
---> Package redhat-lsb.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-core.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-core.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-cxx.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-cxx.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-desktop.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-desktop.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-languages.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-languages.x86_64 0:4.1-10.fc18 will be an update
--> Processing Dependency: perl(XML::LibXML) for package: redhat-lsb-languages-4.1-10.fc18.x86_64
---> Package redhat-lsb-printing.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-printing.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-submod-multimedia.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-submod-multimedia.x86_64 0:4.1-10.fc18 will be an update
---> Package redhat-lsb-submod-security.x86_64 0:4.1-5.fc18 will be updated
---> Package redhat-lsb-submod-security.x86_64 0:4.1-10.fc18 will be an update
---> Package ruby.x86_64 0:1.9.3.374-27.fc18 will be updated
---> Package ruby.x86_64 0:1.9.3.385-28.fc18 will be an update
---> Package ruby-irb.noarch 0:1.9.3.374-27.fc18 will be updated
---> Package ruby-irb.noarch 0:1.9.3.385-28.fc18 will be an update
---> Package ruby-libs.x86_64 0:1.9.3.374-27.fc18 will be updated
---> Package ruby-libs.x86_64 0:1.9.3.385-28.fc18 will be an update
---> Package rubygem-bigdecimal.x86_64 0:1.1.0-27.fc18 will be updated
---> Package rubygem-bigdecimal.x86_64 0:1.1.0-28.fc18 will be an update
---> Package rubygem-io-console.x86_64 0:0.3-27.fc18 will be updated
---> Package rubygem-io-console.x86_64 0:0.3-28.fc18 will be an update
---> Package rubygems.noarch 0:1.8.24-3.fc18 will be updated
---> Package rubygems.noarch 0:1.8.25-1.fc18 will be an update
---> Package sane-backends.x86_64 0:1.0.23-4.fc18 will be updated
---> Package sane-backends.x86_64 0:1.0.23-7.fc18 will be an update
---> Package sane-backends-drivers-scanners.i686 0:1.0.23-4.fc18 will be updated
---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-4.fc18 will be updated
---> Package sane-backends-drivers-scanners.i686 0:1.0.23-7.fc18 will be an update
---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-7.fc18 will be an update
---> Package sane-backends-libs.i686 0:1.0.23-4.fc18 will be updated
---> Package sane-backends-libs.x86_64 0:1.0.23-4.fc18 will be updated
---> Package sane-backends-libs.i686 0:1.0.23-7.fc18 will be an update
---> Package sane-backends-libs.x86_64 0:1.0.23-7.fc18 will be an update
---> Package selinux-policy.noarch 0:3.11.1-76.fc18 will be updated
---> Package selinux-policy.noarch 0:3.11.1-79.fc18 will be an update
---> Package selinux-policy-devel.noarch 0:3.11.1-76.fc18 will be updated
---> Package selinux-policy-devel.noarch 0:3.11.1-79.fc18 will be an update
---> Package selinux-policy-doc.noarch 0:3.11.1-76.fc18 will be updated
---> Package selinux-policy-doc.noarch 0:3.11.1-79.fc18 will be an update
---> Package selinux-policy-targeted.noarch 0:3.11.1-76.fc18 will be updated
---> Package selinux-policy-targeted.noarch 0:3.11.1-79.fc18 will be an update
---> Package xemacs-packages-extra.noarch 0:20121228-1.fc18 will be updated
---> Package xemacs-packages-extra.noarch 0:20130208-3.fc18 will be an update
---> Package xemacs-packages-extra-el.noarch 0:20121228-1.fc18 will be updated
---> Package xemacs-packages-extra-el.noarch 0:20130208-3.fc18 will be an update
---> Package xen-libs.x86_64 0:4.2.1-5.fc18 will be updated
---> Package xen-libs.x86_64 0:4.2.1-7.fc18 will be an update
---> Package xen-licenses.x86_64 0:4.2.1-5.fc18 will be updated
---> Package xen-licenses.x86_64 0:4.2.1-7.fc18 will be an update
---> Package xkeyboard-config.noarch 0:2.6-6.fc18 will be updated
---> Package xkeyboard-config.noarch 0:2.6-7.fc18 will be an update
---> Package xorg-x11-server-utils.x86_64 0:7.5-14.fc18 will be updated
---> Package xorg-x11-server-utils.x86_64 0:7.5-16.fc18 will be an update
---> Package xorg-x11-xkb-utils.x86_64 0:7.7-4.fc18 will be updated
---> Package xorg-x11-xkb-utils.x86_64 0:7.7-5.fc18 will be an update
--> Running transaction check
---> Package graphite2.i686 0:1.1.1-4.fc18 will be installed
---> Package perl-XML-LibXML.x86_64 1:2.0004-1.fc18 will be installed
--> Processing Dependency: perl(XML::SAX::DocumentLocator) for package: 1:perl-XML-LibXML-2.0004-1.fc18.x86_64
--> Processing Dependency: perl(XML::NamespaceSupport) for package: 1:perl-XML-LibXML-2.0004-1.fc18.x86_64
--> Running transaction check
---> Package perl-XML-NamespaceSupport.noarch 0:1.11-8.fc18 will be installed
---> Package perl-XML-SAX.noarch 0:0.99-5.fc18 will be installed
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:3.7.6-201.fc18 will be erased
---> Package kernel-devel.x86_64 0:3.7.6-201.fc18 will be erased
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================
Installing:
kernel x86_64 3.7.9-201.fc18 updates 27 M
kernel-devel x86_64 3.7.9-201.fc18 updates 7.8 M
Updating:
ModemManager x86_64 0.6.0.0-3.fc18 updates 318 k
NetworkManager x86_64 1:0.9.7.997-2.fc18 updates 987 k
NetworkManager-glib x86_64 1:0.9.7.997-2.fc18 updates 311 k
cairo i686 1.12.14-1.fc18 updates 710 k
cairo x86_64 1.12.14-1.fc18 updates 679 k
cairo-devel x86_64 1.12.14-1.fc18 updates 514 k
cairo-gobject i686 1.12.14-1.fc18 updates 23 k
cairo-gobject x86_64 1.12.14-1.fc18 updates 24 k
cairo-gobject-devel x86_64 1.12.14-1.fc18 updates 17 k
cvs x86_64 1.11.23-29.fc18 updates 566 k
evolution-data-server x86_64 3.6.3-2.fc18 updates 3.2 M
evolution-data-server-devel x86_64 3.6.3-2.fc18 updates 316 k
exempi x86_64 2.2.0-6.fc18 updates 390 k
finger x86_64 0.17-48.fc18 updates 25 k
gimp x86_64 2:2.8.4-1.fc18 updates 14 M
gimp-libs x86_64 2:2.8.4-1.fc18 updates 1.2 M
google-chrome-stable x86_64 25.0.1364.97-183676 google-chrome 50 M
gstreamer1-plugins-good x86_64 1.0.5-3.fc18 updates 1.6 M
harfbuzz i686 0.9.12-2.fc18 updates 480 k
harfbuzz x86_64 0.9.12-2.fc18 updates 474 k
harfbuzz-devel x86_64 0.9.12-2.fc18 updates 49 k
httpd x86_64 2.4.3-15.fc18 updates 1.1 M
httpd-devel x86_64 2.4.3-15.fc18 updates 174 k
httpd-manual noarch 2.4.3-15.fc18 updates 1.3 M
httpd-tools x86_64 2.4.3-15.fc18 updates 78 k
ibus x86_64 1.5.1-2.fc18 updates 413 k
ibus-anthy x86_64 1.5.0-1.fc18 updates 159 k
ibus-gtk2 x86_64 1.5.1-2.fc18 updates 40 k
ibus-gtk3 x86_64 1.5.1-2.fc18 updates 40 k
ibus-libs x86_64 1.5.1-2.fc18 updates 191 k
jcifs noarch 1.3.17-7.fc18 updates 445 k
kernel-headers x86_64 3.7.9-201.fc18 updates 813 k
kernel-tools x86_64 3.7.9-201.fc18 updates 74 k
kernel-tools-libs x86_64 3.7.9-201.fc18 updates 19 k
libchewing x86_64 0.3.4-2.fc18 updates 1.6 M
libgphoto2 i686 2.5.0-7.fc18 updates 1.1 M
libgphoto2 x86_64 2.5.0-7.fc18 updates 1.1 M
libnm-gtk x86_64 0.9.7.997-1.fc18 updates 71 k
libqb x86_64 0.14.4-1.fc18 updates 83 k
libuser x86_64 0.58-2.fc18 updates 391 k
libuser-devel x86_64 0.58-2.fc18 updates 64 k
libuser-python x86_64 0.58-2.fc18 updates 50 k
linuxconsoletools x86_64 1.4.4-7.fc18 updates 60 k
lohit-assamese-fonts noarch 2.5.3-1.fc18 updates 73 k
lohit-bengali-fonts noarch 2.5.3-1.fc18 updates 73 k
lohit-devanagari-fonts noarch 2.5.3-1.fc18 updates 48 k
lohit-kannada-fonts noarch 2.5.3-1.fc18 updates 54 k
lohit-oriya-fonts noarch 2.5.3-1.fc18 updates 56 k
lohit-punjabi-fonts noarch 2.5.3-1.fc18 updates 24 k
lohit-tamil-fonts noarch 2.5.3-1.fc18 updates 36 k
lohit-telugu-fonts noarch 2.5.3-1.fc18 updates 62 k
minicom x86_64 2.5-10.fc18 updates 253 k
mod_ssl x86_64 1:2.4.3-15.fc18 updates 94 k
network-manager-applet x86_64 0.9.7.997-1.fc18 updates 213 k
nm-connection-editor x86_64 0.9.7.997-1.fc18 updates 795 k
ntfs-3g x86_64 2:2013.1.13-1.fc18.1 updates 267 k
ntfsprogs x86_64 2:2013.1.13-1.fc18.1 updates 266 k
numpy x86_64 1:1.7.0-1.fc18 updates 2.8 M
paktype-naqsh-fonts noarch 4.0-3.fc18 updates 343 k
paktype-tehreer-fonts noarch 4.0-3.fc18 updates 397 k
phonon-backend-gstreamer x86_64 2:4.6.3-1.fc18 updates 137 k
pulseaudio x86_64 2.1-6.fc18 updates 818 k
pulseaudio-gdm-hooks x86_64 2.1-6.fc18 updates 18 k
pulseaudio-libs x86_64 2.1-6.fc18 updates 451 k
pulseaudio-libs-glib2 x86_64 2.1-6.fc18 updates 25 k
pulseaudio-module-bluetooth x86_64 2.1-6.fc18 updates 89 k
pulseaudio-module-gconf x86_64 2.1-6.fc18 updates 28 k
pulseaudio-module-jack x86_64 2.1-6.fc18 updates 35 k
pulseaudio-module-x11 x86_64 2.1-6.fc18 updates 37 k
pulseaudio-utils x86_64 2.1-6.fc18 updates 86 k
redhat-lsb x86_64 4.1-10.fc18 updates 24 k
redhat-lsb-core x86_64 4.1-10.fc18 updates 35 k
redhat-lsb-cxx x86_64 4.1-10.fc18 updates 14 k
redhat-lsb-desktop x86_64 4.1-10.fc18 updates 18 k
redhat-lsb-languages x86_64 4.1-10.fc18 updates 16 k
redhat-lsb-printing x86_64 4.1-10.fc18 updates 14 k
redhat-lsb-submod-multimedia x86_64 4.1-10.fc18 updates 13 k
redhat-lsb-submod-security x86_64 4.1-10.fc18 updates 13 k
ruby x86_64 1.9.3.385-28.fc18 updates 62 k
ruby-irb noarch 1.9.3.385-28.fc18 updates 73 k
ruby-libs x86_64 1.9.3.385-28.fc18 updates 2.6 M
rubygem-bigdecimal x86_64 1.1.0-28.fc18 updates 72 k
rubygem-io-console x86_64 0.3-28.fc18 updates 44 k
rubygems noarch 1.8.25-1.fc18 updates 174 k
sane-backends x86_64 1.0.23-7.fc18 updates 928 k
sane-backends-drivers-scanners i686 1.0.23-7.fc18 updates 2.2 M
sane-backends-drivers-scanners x86_64 1.0.23-7.fc18 updates 2.2 M
sane-backends-libs i686 1.0.23-7.fc18 updates 90 k
sane-backends-libs x86_64 1.0.23-7.fc18 updates 90 k
selinux-policy noarch 3.11.1-79.fc18 updates 231 k
selinux-policy-devel noarch 3.11.1-79.fc18 updates 1.8 M
selinux-policy-doc noarch 3.11.1-79.fc18 updates 880 k
selinux-policy-targeted noarch 3.11.1-79.fc18 updates 3.8 M
xemacs-packages-extra noarch 20130208-3.fc18 updates 15 M
xemacs-packages-extra-el noarch 20130208-3.fc18 updates 11 M
xen-libs x86_64 4.2.1-7.fc18 updates 411 k
xen-licenses x86_64 4.2.1-7.fc18 updates 74 k
xkeyboard-config noarch 2.6-7.fc18 updates 691 k
xorg-x11-server-utils x86_64 7.5-16.fc18 updates 180 k
xorg-x11-xkb-utils x86_64 7.7-5.fc18 updates 93 k
Removing:
kernel x86_64 3.7.6-201.fc18 @updates 119 M
kernel-devel x86_64 3.7.6-201.fc18 @updates 29 M
Installing for dependencies:
graphite2 i686 1.1.1-4.fc18 updates 81 k
perl-XML-LibXML x86_64 1:2.0004-1.fc18 fedora 366 k
perl-XML-NamespaceSupport noarch 1.11-8.fc18 fedora 18 k
perl-XML-SAX noarch 0.99-5.fc18 fedora 62 k
Transaction Summary
============================================================================================================================================================================================
Install 2 Packages (+4 Dependent packages)
Upgrade 100 Packages
Remove 2 Packages
Total size: 171 M
Downloading Packages:
Running Transaction Check
ERROR with transaction check vs depsolve:
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum
** Found 5 pre-existing rpmdb problem(s), 'yum check' output follows:
maven-one-plugin-1.2-8.fc17.noarch has missing requires of maven-shared-model-converter
mod_python-3.3.1-18.fc17.x86_64 has missing requires of httpd-mmn = ('0', '20051115', 'x86-64')
plexus-appserver-1.0-0.7.a5.fc15.noarch has missing requires of xmlrpc
plexus-runtime-builder-1.0-0.6.a9.fc15.noarch has missing requires of xmlrpc
plexus-xmlrpc-1.0-0.7.b4.3.fc16.noarch has missing requires of xmlrpc
Your transaction was saved, rerun it with:
yum load-transaction /tmp/yum_save_tx.2013-02-22.15-17.YcsZAt.yumtx
[root@sirius ~]# yum --version
3.4.3
Installed: rpm-4.10.3.1-1.fc18.x86_64 at 2013-02-12 16:17
Built : Fedora Project at 2013-02-06 09:54
Committed: Panu Matilainen <pmatilai> at 2013-02-06
Installed: yum-3.4.3-49.fc18.noarch at 2013-02-14 05:02
Built : Fedora Project at 2013-02-06 10:06
Committed: Zdenek Pavlas <zpavlas> at 2013-02-06
Installed: yum-plugin-fastestmirror-1.1.31-9.fc18.noarch at 2013-02-14 05:03
Built : Fedora Project at 2013-02-08 09:05
Committed: Zdenek Pavlas <zpavlas> at 2013-02-08
Expected results:
success. :)
Additional info:
# uname -msrvo
Linux 3.7.5-201.fc18.x86_64 #1 SMP Mon Jan 28 19:54:41 UTC 2013 x86_64 GNU/Linux
*** This bug has been marked as a duplicate of bug 912012 *** |
-
baskervi
- Posts: 13
- Joined: 2016/05/24 18:53:17
GCC Problems upgrading CentOS from 7 to 8
I’m running into a dependency issue with gcc and rpmlib(RichDependencies), but it seems to me that the installed gcc version is OK. Can anyone help point me to the right version of gcc? Also, I can’t figure out how to install rpmlib(RichDependencies). ‘rpm —rebuilddb’ did not fix the issue.Thanks
Error: transaction check vs depsolve:
(gcc >= 8 with gcc < 9) is needed by annobin-8.90-1.el8.0.1.x86_64
rpmlib(RichDependencies) <= 4.12.0-1 is needed by annobin-8.90-1.el8.0.1.x86_64
(annobin if gcc) is needed by redhat-rpm-config-122-1.el8.noarch
rpmlib(RichDependencies) <= 4.12.0-1 is needed by redhat-rpm-config-122-1.el8.noarch
(flatpak-selinux = 1.6.2-2.el8 if selinux-policy-targeted) is needed by flatpak-1.6.2-2.el8.x86_64
rpmlib(RichDependencies) <= 4.12.0-1 is needed by flatpak-1.6.2-2.el8.x86_64
To diagnose the problem, try running: ‘rpm -Va —nofiles —nodigest’.
You probably have corrupted RPMDB, running ‘rpm —rebuilddb’ might fix the issue.
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
[root@scanner ~]# gcc —version
gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
TrevorH
- Site Admin
- Posts: 32527
- Joined: 2009/09/24 10:40:56
- Location: Brighton, UK
Re: GCC Problems upgrading CentOS from 7 to 8
Post
by TrevorH » 2020/07/28 15:12:01
There is no upgrade from CentOS 7 to 8. It is a reinstall. From scratch.
-
baskervi
- Posts: 13
- Joined: 2016/05/24 18:53:17
Re: GCC Problems upgrading CentOS from 7 to 8
Post
by baskervi » 2020/07/28 18:30:57
Gotcha. I’ve read that multiple times. Some folks have been successful, so I had hoped this as well. Thanks for the response. Download of version 8 is complete.
-
kluch
- Posts: 10
- Joined: 2020/05/31 05:47:54
Re: GCC Problems upgrading CentOS from 7 to 8
Post
by kluch » 2020/10/14 13:27:35
baskervi wrote: ↑
2020/07/28 14:14:05
I’m running into a dependency issue with gcc and rpmlib(RichDependencies), but it seems to me that the installed gcc version is OK. Can anyone help point me to the right version of gcc? Also, I can’t figure out how to install rpmlib(RichDependencies). ‘rpm —rebuilddb’ did not fix the issue.ThanksError: transaction check vs depsolve:
(gcc >= 8 with gcc < 9) is needed by annobin-8.90-1.el8.0.1.x86_64
rpmlib(RichDependencies) <= 4.12.0-1 is needed by annobin-8.90-1.el8.0.1.x86_64
…
It is all about perl/python3, just remove them and install after upgrade. It did the trick for me.
-
TrevorH
- Site Admin
- Posts: 32527
- Joined: 2009/09/24 10:40:56
- Location: Brighton, UK
Re: GCC Problems upgrading CentOS from 7 to 8
Post
by TrevorH » 2020/10/14 15:13:57
Upgrades are explicitly unsupported. If you attempt it and it breaks — which it often does — then you get to keep all of the pieces.
-
th3penguinwhisperer
- Posts: 6
- Joined: 2017/04/24 20:16:44
Re: GCC Problems upgrading CentOS from 7 to 8
Post
by th3penguinwhisperer » 2021/05/04 16:48:21
I did this:
dnf -y —releasever=8 —allowerasing —setopt=deltarpm=false distro-sync —disablerepo=appstream
And after that was able to upgrade. (I think I had to remove vim-common and python36-object-base or something similar (you will see the conflicts once you run the command above).
Plesk update failed: Missing Dependency psa-proftpd or u’ERROR with transaction check vs depsolve:’
Symptoms
-
Unable to update Plesk:
PLESK_ERROR: psa-proftpd-xinetd-1.3.5-6.el5.art.x86_64 from installed has depsolving problems
–> Missing Dependency: psa-proftpd = 1.3.5-6.el5.art is needed by package psa-proftpd-xinetd-1.3.5-6.el5.art.x86_64 (installed)
Exception: Failed to solve dependencies:
Missing Dependency: psa-proftpd = 1.3.5-6.el5.art is needed by package psa-proftpd-xinetd-1.3.5-6.el5.art.x86_64 (installed)
Fatal error during packages installation: [u'ERROR with transaction check vs depsolve:', 'psa-proftpd = 1.3.6-11.el7.art is needed by (installed) psa-proftpd-xinetd-1.3.6-11.el7.art.x86_64']
YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'psa-proftpd = 1.3.6-11.el7.art is needed by (installed) psa-proftpd-xinetd-1.3.6-11.el7.art.x86_64'] -
Unable to connect to the server over FTP:
421 Service not available, remote server has closed connection
-
plesk logincommand does not work:# plesk login
ERR [panel] DB query failed: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘psa.ServiceInstallations’ doesn’t exist, query was: DESCRIBEServiceInstallations
DB query failed: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘psa.ServiceInstallations’ doesn’t exist, query was: DESCRIBEServiceInstallations -
Atomic repository may be active on the server:
# yum repolist | grep -i atomic
atomic/7/x86_64 CentOS / Red Hat Enterprise Linux 7 – atomic 747
Cause
Incorrect package installed from a third-party repository.
Resolution
-
Connect to the server via SSH.
-
Remove
psa-proftpd/psa-proftpd-xinetdpackages mentioned in the error message, for example:# rpm -e psa-proftpd-xinetd-1.3.5-6.el5.art –nodeps
# rpm -e psa-proftpd-1.3.5-6.el5.art –nodeps -
In case the Atomic repository is active (see symptoms), add packages to exclusion list:
# echo ‘exclude=psa-proftpd*’ >> /etc/yum.repos.d/atomic.repo
-
Install ProFTP from Web Hosting category in Plesk installer:
# plesk installer
- Server Redundancy
- Linux Containers
- AMP
- Bare Metal Server
- Backup
- Red Hat Virtualization
- Oracle VM Server
- Server Virtualization Software
- Windows Server
- Linux
- Hosting Control Panel
- Plesk
- Web Server
- DNS Server
- SSH
- Colocation Hosting
- Reseller Hosting
- Cloud Hosting
- VPS Hosting
- Dedicated Hosting
- Shared Hosting
- Free Hosting
- Managed Hosting
Startup errors
Startup errors are usually caused by conflicts with dlls of other applications which may be out of date or incompatible with the versions used in Arca Noae Package Manager. An example of this would be another application which utilizes VROBJEX.DLL, such as EVFSGUI through (at least) version 2.5RC7. When EVFSGUI is open, attempting to start Arca Noae Package Manager will result in an error message:
Cannot load window: Could not find class 'VRToolTip'
Check for other dlls in LIBPATH with the same names as those in the Arca Noae Package Manager installation directory.
First run errors
For systems with existing Python installations, please see this page.
On systems with no existing RPM & YUM installation, Arca Noae Package Manager should prompt to download and install the base package upon first program start. In certain instances, it is possible for the initial download of the base package to fail with:
The command terminated with error code 1.
This usually indicates that the TCP/IP stack is not 32-bit. Please upgrade the TCP/IP stack to 32-bit and re-try the operation.
YUM errors
A YUM error may cause the Arca Noae Package Manager main window to be completely blank. A basic failure of this type may be encountered when symbolic links (symlinks) are unavailable on the system or on the volume designated as %UNIXROOT%. Because YUM depends upon Python, and because Python depends upon modules which are referenced through symlinks, these modules cannot be found and thus, YUM fails to start, leaving Arca Noae Package Manager without input to display.
Running YUM from the command line, this condition may be seen more clearly:
There was a problem importing one of the Python modules required to run yum. The error leading to the problem was: dlopen rc=193 extra=X:USRLIBPYTHON2.7LIB-DYNLOADCSTRINGIO.PYD Please install a package which provides this module, or verify that the module is installed correctly.
(X: is a placeholder for the volume designated as %UNIXROOT%.)
This indicates a failure of YUM to resolve a symlinked file pointing to a required module.
See the Netlabs RPM and YUM project page for more assistance.
Another potential cause of such a failure is when YUM, Python, or perhaps RPM has been updated and the new version requires an updated library. The updated library may have been automatically installed, but the older one is still either in use or perhaps an older version is closer in %PATH%, precluding the new version from being loaded. If you have anything in usrlocallib, that’s a good place to start looking for such conflicts.
YUM metadata and cache
These tasks are available from the Manage | YUM tools | Cleanup menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.
Completing transactions
Sometimes, operations fail before completing, leaving the installation and the databases in varying states of inconsistency. This task (without special options) is available from the Manage | YUM tools | Cleanup menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.
Transaction check vs depsolve errors
These are not errors per se (likely nothing is broken or misconfigured with YUM itself), but rather issues with the particular operation which has been requested. Transaction check refers to the requested operation (install xyz, remove qrs, update abc), while depsolve refers to resolving dependencies (either installed packages which are dependent upon a package to be removed, updated, downgraded, or replaced, or packages which must be installed as dependencies of the package already selected for installation).
When Arca Noae Package Manager presents a message panel reporting “ERROR with transaction check vs depsolve:”, carefully read the package names, versions, and operators which follow, as in “abc = 1.1.0-1 is needed by qrs-2.1.0-0”. Bear the following in mind:
= means that exact version/release of the listed package is required.
>= means that version/release or higher is required
The part which may follow is an explanation as to why the dependency cannot be satisfied (perhaps the required package cannot be found in any enabled repository, or perhaps the required package has not been selected for removal, update, or downgrade).
Duplicate package errors
These may or may not be reported during an Arca Noae Package Manager operation, but should be shown at the command line. Often, they cause other (reported) errors, as they indicate some inconsistency either in the filesystem or (more likely) the RPM database. The cause of duplicate package errors can generally be traced to an interruption (program or system crash) while a YUM or RPM operation was in progress. Often the packages themselves are not exact duplicates, but an older version is reported as being installed along with its newer version.
If you find that you are unable to update or remove a package, and are unable to resolve the issue using the steps outlined above under Completing transactions, above, check for and clean duplicates as follows:
- Exit Arca Noae Package Manager.
- Open a shell prompt from an OS/2 window, by typing:
[c:] sh <Enter>
- At the prompt, type:
# package-cleanup --dupes <Enter>
- If any duplicate packages are reported, remove them with:
# package-cleanup --cleandupes <Enter>
- Check for other inconsistencies with:
# package-cleanup --problems <Enter>
- Exit the shell:
# exit <Enter>
- Start Arca Noae Package Manager and attempt to complete any uncompleted transactions from the Manage | YUM tools | Cleanup menu.
- Retry the original update or remove operation.
Sometimes, scriptlet errors may be reported by package-cleanup, preventing the duplicates from being resolved. A typical error report of this kind is:
Error in PREUN scriptlet in rpm package <some package> Failed: <some package>
A possible workaround is to use the –noscripts option on the package-cleanup line:
# package-cleanup --cleandupes --noscripts
This prevents the scriptlet(s) from being called, thus bypassing the supposed error.
In case the duplicate package was also included in an incomplete transaction list, you may use the –cleanup option for yum-complete-transaction (this must be done from the command line, as Arca Noae Package Manager does not provide this functionality):
# yum-complete-transaction --cleanup
Package conflicts
Generally, when one package replaces another (similar content, but different package name), the superseding package does not properly “obsolete” the older package. This is commonly seen with “-debuginfo” packages which do not obsolete the older “-debug” packages. When this happens, Arca Noae Package Manager will return YUM’s error report, which may contain one or more entries resembling:
Transaction Check Error: file /@unixroot/usr/bin/somefile from install of something-debug-n.n.n-n.oc00.arch conflicts with file from package something-debuginfo-n.n.n-n.oc00.arch
Such packages contain the HLL (high-level language) debug data used to help diagnose problems with the named application or library package. This debug data is not needed for the normal use of the application or library, and so is stripped off and packaged separately. Normally, it is not necessary to install the -debug (or newer -debuginfo) package, but when problems occur, and a -debug or -debuginfo package is available, it should be installed.
The conflict occurs when an older -debug package (something-debug) has already been installed, or has mistakenly been selected for install when (the newer) -debuginfo package has been selected for install. While whichever one to be installed should match the binary package’s version and release (e.g., something-1.0.0-1.oc00.i686 requires something-debuginfo-1.0.0-1.oc00.i686), existing debug packages (e.g., something-debug-0.9.9-9.oc00.i686) are not considered obsolete, and thus create a conflict reported by RPM to YUM, and ultimately, to Arca Noae Package Manager.
Early in the use of RPMs on OS/2, this HLL data was packaged as something-debug. Later, the package naming convention changed to something-debuginfo. It is the package naming convention change which causes the conflict, such that a newer “-debuginfo” package is not seen as replacing (obsoleting) a “-debug” package with a lower version and/or release number.
The failure is in the macro used to build the -debuginfo package, which does not add the proper Obsoletes tag to the resulting package.
To resolve this, uninstall any outdated -debug package(s) causing the conflict, and then install the -debuginfo package matching the installed application or library package version and release.
More information concerning -debug and -debuginfo packages, as well as this specific problem with the lack of obsoleting, may be found here:
https://github.com/bitwiseworks/libc/issues/77
http://trac.netlabs.org/rpm/ticket/134
http://trac.netlabs.org/rpm/ticket/149
Similar package conflicts may occur for other types of packages, as well, which do not (for whatever reason) render obsolete another package with a different name. Careful examination of the packages involved in the conflict, what operation was requested, and what already exists should reveal what steps may be taken to resolve the conflict (uninstall one or more packages in order to install one or more new ones, or reevaluate whether the new ones are entirely appropriate, etc.).
RPM errors
The most frequent RPM errors encountered are generally due to incomplete updates, where somehow, RPM or one of its main dependencies has been updated, but a dependency farther down the chain has not. These errors can be difficult to diagnose. The best option is to compare the installed system’s packages to a working system. It may be useful to attempt a different RPM operation (such as Verify) against either the errant package or RPM itself:
[c:] rpm -V rpm <Enter>
Sometimes, RPM may report “[Errno 13] Permission denied” when attempting to access a package for installation (this package may exist inside the YUM cache or anywhere else (assuming RPM is called directly). As OS/2’s Unix Compatibility Subsystem is rooted, unless a third party multi-user component has been installed, the OS/2 shell (CMD, 4OS2, etc.) runs with root privileges, so lack of adequate permissions is very unusual, and tends to be more of an indication of running low on some memory resource (or available file handles) than a real problem. Often, simply closing all other running applications and attempting the operation will suffice to resolve the issue in that session. Otherwise, try rebooting and retrying the operation before starting any other applications.
See the Netlabs RPM and YUM project page for further assistance and to open support tickets specifically related to RPM.
Rebuild RPM database
This task is available from the Manage | YUM tools | Maintenance menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.
Submitting Tickets
Before submitting a ticket, make sure you have read the main wiki page.
Reporting bugs and requesting new features is done through the ticketing system. You may view existing tickets, add comments, and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for the same problem or feature request already created.
- When searching or reporting, select the Package Manager (ANPM) project.
- Please follow the guidelines as discussed in the Reporting Problems – Best Practices page.
This entry last updated: August 31st, 2021 by