Ipa Rpm Conflicts
does anybody see this:
unning transaction Warning: RPMDB altered outside of yum.
** Found 8 pre-existing rpmdb problem(s), ‘yum check’ output follows:
ipa-admintools-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-admintools:
ipa-admintools-4.4.0-14.el7.CentOS.noarch ipa-client-4.4.0-14.el7.CentOS.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7.CentOS.x86_64
ipa-client-common-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-client-common:
ipa-client-common-4.4.0-14.el7.CentOS.noarch ipa-common-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.el7.CentOS.noarch ipa-python-compat-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-python-compat:
ipa-python-compat-4.4.0-14.el7.CentOS.noarch ipa-server-4.4.0-14.el7.CentOS.x86_64 has installed conflicts freeipa-server: ipa-server-4.4.0-14.el7.CentOS.x86_64
ipa-server-common-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-server-common:
ipa-server-common-4.4.0-14.el7.CentOS.noarch ipa-server-dns-4.4.0-14.el7.CentOS.noarch has installed conflicts freeipa-server-dns:
ipa-server-dns-4.4.0-14.el7.CentOS.noarch
this in .rpm I guess and started appearing after upg to 7.3.
*freeipa* is naming convention Fedora uses, right? Some remnants rebase did not take care of?
regards, L.
3 thoughts on - Ipa Rpm Conflicts
upstream issue https://bugzilla.redhat.com/show_bug.cgi?id=1370134
Cheers
Tru
Hello,
For the sake of the archives, since yesterday (or since I noticed that)
and w/ an up-to-date CentOS 7.3.1611, I get this:
** Found 3 pre-existing rpmdb problem(s), ‘yum check’ output follows:
ipa-client-4.4.0-14.el7.CentOS.7.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7.CentOS.7.x86_64
ipa-client-common-4.4.0-14.el7.CentOS.7.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.el7.CentOS.7.noarch ipa-common-4.4.0-14.el7.CentOS.7.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.el7.CentOS.7.noarch
That seems to be the same issue, and I confirm that the workaround described in comment #17 at the bug page does work, whereas `yum remove` ’em all then `yum install` ’em back doesn’t work.
Regards,
That’s correct. Got the same on my laptop. removed the package there…
Am Freitag, den 04.08.2017, 18:28 +0200 schrieb wwp: