RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 806074 - libreoffice-debuginfo does not obsolete openoffice.org-debuginfo
Summary: libreoffice-debuginfo does not obsolete openoffice.org-debuginfo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libreoffice
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: alpha
: ---
Assignee: Caolan McNamara
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-22 20:31 UTC by Tomas Pelka
Modified: 2012-06-20 12:53 UTC (History)
2 users (show)

Fixed In Version: libreoffice-3.4.5.2-9.el6
Doc Type: Bug Fix
Doc Text:
No Documentation needed
Clone Of:
Environment:
Last Closed: 2012-06-20 12:53:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0798 0 normal SHIPPED_LIVE new packages: libreoffice 2012-06-19 21:00:52 UTC

Description Tomas Pelka 2012-03-22 20:31:49 UTC
Description of problem:
SSIA

Version-Release number of selected component (if applicable):
libreoffice-3.4.5.2-8

How reproducible:
100%

Steps to Reproduce:
1. Install (all including debuginfo) latest openoffice.org-*.rpm
2. update to libreoffice
3.
  
Actual results:
after update to libreoffice, openoffice.org-debuginfo is still present on the system

Expected results:
libreoffice-debuginfo should obsolete openoffice.org-debuginfo

Additional info:

Comment 1 David Tardon 2012-03-23 06:39:20 UTC
dtardon->tpelka: seriously? :-)

(In reply to comment #0)
> Expected results:
> libreoffice-debuginfo should obsolete openoffice.org-debuginfo

In general, -debuginfo package is generated automatically by rpmbuild and it is not possible to touch its headers from the spec. Luckily for you, we already generate it ourselves, so it is easy to fix this. Otherwise I would just have put the obsoletes/provides into -core .-)

dtardon->caolanm: fixed in Fedora

Comment 2 Tomas Pelka 2012-03-23 08:09:40 UTC
Yes seriously, in case we retire ooo.org we have to ensure that ALL ooo.org related packages will be replaced.

If it is possible by other components I do not understand why it should be a nonsense for lo.

Comment 5 Caolan McNamara 2012-05-01 09:04:24 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No Documentation needed

Comment 7 errata-xmlrpc 2012-06-20 12:53:19 UTC
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/RHEA-2012-0798.html


Note You need to log in before you can comment on or make changes to this bug.