26.1.2017, 19.18, lejeczek kirjoitti: > dear devel > > is this true that every rpm downgrade goes kind of a ... "haywire" ? > > I've tried a few and... > > ~]$ yum downgrade ctdb > --> Running transaction check > ---> Package ctdb.x86_64 0:4.4.4-9.el7 will be a downgrade > --> Processing Dependency: samba-client-libs = 4.4.4-9.el7 for package: > ctdb-4.4.4-9.el7.x86_64 > ---> Package ctdb.x86_64 0:4.4.4-12.el7_3 will be erased > --> Running transaction check > ---> Package samba-client-libs.i686 0:4.4.4-9.el7 will be installed > <= ????? > > ~]$ yum downgrade bind > Resolving Dependencies > --> Running transaction check > ---> Package bind.x86_64 32:9.9.4-38.el7_3 will be a downgrade > --> Processing Dependency: bind-libs = 32:9.9.4-38.el7_3 for package: > 32:bind-9.9.4-38.el7_3.x86_64 > ---> Package bind.x86_64 32:9.9.4-38.el7_3.1 will be erased > --> Running transaction check > ---> Package bind.x86_64 32:9.9.4-38.el7_3.1 will be erased > ---> Package bind-libs.i686 32:9.9.4-38.el7_3 will be installed <= ???? > > etc. > and system has no signle 686 rpm. Some kind of a curse my boxes suffer > from? :) It looks like resolving the dependencies is the problem. If you tried downgrading bind with a "yum downgrade bind bind-libs bind-license bind-utils bind-chroot bind-libs-lite", it would work.