Hide Forgot
Description of problem: Libreoffice in RHEL 6.5 no longer obsoletes openoffice.org, which causes problems in certain cases. For instance, if you try "yum --skip-broken install \*", yum tries to get you both openoffice.org and libreoffice, downloads everything, and then fails in the transaction check: file /usr/bin/oobase conflicts between attempted installs of openoffice.org-base-1:3.2.1-19.6.el6_2.7.x86_64 and libreoffice-base-1:4.0.4.2-9.el6.x86_64 (Many other files are shared, and there's nothing in the metadata that would make yum skip openoffice.org* in the fist place, allowing the transaction to pass. Note: there are some other packages that must be excluded because of similar issues; there are bug reports for them.) Likewise, if you have openoffice.org-writer-3.2.1-19.6.el6_2.7, which is the latest OO version-release in RHEL-6 (from RHSA-2012:0705), and you run "yum install libreoffice-writer", you get: Installing: libreoffice-writer i686 1:4.0.4.2-9.el6 rhel-i386-server-optional-6 5.1 M ... file /usr/bin/oowriter from install of libreoffice-writer-1:4.0.4.2-9.el6.i686 conflicts with file from package openoffice.org-writer-1:3.2.1-19.6.el6_2.7.i686 Shouldn't libreoffice-writer (and friends) still obsolete openoffice.org-writer (and their OO counterparts)? That would allow "yum install *" to work, and make "yum install libreoffice-whatever" replace OO if it's installed.
> Shouldn't libreoffice-writer (and friends) still obsolete > openoffice.org-writer (and their OO counterparts)? That would allow "yum > install *" to work, and make "yum install libreoffice-whatever" replace OO > if it's installed. Yes, they should. The obsoletes were unintentionally lost. We can add them back easily enough, but it will be a bit late, I guess...
That's fine; in the meantime, we can just exclude OO on the yum command lines in our recipes.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Created attachment 928403 [details] yum debug Full debug output from yum
I can't fix this without an approved "exception" flag
yeah, I don't see that we need to address debuginfo, we can ignore that. Its just the langpack that needs to be addressed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1423.html