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 507608 - openoffice.org-ogltrans prints a warning on update
Summary: openoffice.org-ogltrans prints a warning on update
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openoffice.org
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: beta
: ---
Assignee: Caolan McNamara
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-23 13:19 UTC by Alexander Todorov
Modified: 2009-07-02 13:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 503003
Environment:
Last Closed: 2009-07-02 13:29:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alexander Todorov 2009-06-23 13:19:18 UTC 
+++ This bug was initially created as a clone of Bug #503003 +++

Description of problem:
When "yum update"ing to the latest openoffice.org-ogltrans, I see the following warning:
grep: /usr/lib64/openoffice.org/extensions/ogltrans.oxt/description.xml: No such file or directory      
  Updating       : 1:openoffice.org-ogltrans-3.1.0-11.3.fc11.x86_64                               29/72 

rpm -q --scripts openoffice.org-ogltrans yields this:
preinstall scriptlet (using /bin/sh):
# deregister old extension if it is still there
unopkg remove --shared `grep identifier /usr/lib64/openoffice.org/extensions/ogltrans.oxt/description.xml | cut -d '"' -f 2` > /dev/null 2>&1 || :

That file doesn't exist, so the grep is printing an error to stderr. Perhaps there should be an output redirection inside the backquotes?

Version-Release number of selected component (if applicable):
openoffice.org-ogltrans-3.1.0-11.3.fc11.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Update to the latest version
  
Actual results:
Warning message

Expected results:
No warning message

--- Additional comment from caolanm on 2009-05-28 06:02:04 EDT ---

indeed

--- Additional comment from fedora-triage-list on 2009-06-09 12:42:41 EDT ---


This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from dtardon on 2009-06-15 03:29:44 EDT ---

*** Bug 505981 has been marked as a duplicate of this bug. ***

--- Additional comment from updates on 2009-06-23 03:38:29 EDT ---

openoffice.org-3.1.0-11.4.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/openoffice.org-3.1.0-11.4.fc11
Comment 2 Caolan McNamara 2009-06-23 13:50:22 UTC 
Now, that's just a massive pain in my ass, how are we even handling RHEL-6 bugs. Especially as my understanding was that we were importing a some stage during the F-12 cycle, and that's a F-11 OOo, not the latest F-12 one.
Comment 3 Caolan McNamara 2009-07-02 13:29:41 UTC 
The consensus seems to be that the way to handle these is to consider rawhide the development branch for RHEL-6 for the moment, i.e. fixed in F-12 branch is fixed, so...
Note You need to log in before you can comment on or make changes to this bug.