Bug 703141 - [Indic] post scriptlet fails during anaconda upgrade
Summary: [Indic] post scriptlet fails during anaconda upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: fonts-indic
Version: 5.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: beta
: ---
Assignee: Pravin Satpute
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks: rhel57rtt
TreeView+ depends on / blocked
 
Reported: 2011-05-09 12:28 UTC by Pavel Holica
Modified: 2011-07-21 06:41 UTC (History)
3 users (show)

Fixed In Version: fonts-indic-2.3.1.1-2.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 06:41:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
upgrade.log (20.20 KB, text/x-log)
2011-05-09 12:29 UTC, Pavel Holica
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0978 0 normal SHIPPED_LIVE fonts-indic enhancement update 2011-07-20 15:45:16 UTC

Description Pavel Holica 2011-05-09 12:28:39 UTC
Description of problem:
Packages from fonts-hindic 

Version-Release number of selected component (if applicable):
fonts-hindi-2.3.1.1-1.el5.noarch
fonts-bengali-2.3.1.1-1.el5.noarch
fonts-oriya-2.3.1.1-1.el5.noarch
fonts-tamil-2.3.1.1-1.el5.noarch
fonts-kannada-2.3.1.1-1.el5.noarch
fonts-punjabi-2.3.1.1-1.el5.noarch
fonts-malayalam-2.3.1.1-1.el5.noarch
fonts-telugu-2.3.1.1-1.el5.noarch
fonts-gujarati-2.3.1.1-1.el5.noarch
RHEL5.7 Client 20110502.1 x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL5.6 Client GA x86_64 with all packages
2. Upgrade to RHEL5.7 Client 20110502.1 x86_64
3. grep -B 1 failed upgrade.log
  
Actual results:
Upgrading fonts-hindi-2.3.1.1-1.el5.noarch
error: %post(fonts-hindi-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
Upgrading fonts-bengali-2.3.1.1-1.el5.noarch
error: %post(fonts-bengali-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
--
Upgrading fonts-oriya-2.3.1.1-1.el5.noarch
error: %post(fonts-oriya-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
Upgrading fonts-tamil-2.3.1.1-1.el5.noarch
error: %post(fonts-tamil-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
Upgrading fonts-kannada-2.3.1.1-1.el5.noarch
error: %post(fonts-kannada-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
Upgrading fonts-punjabi-2.3.1.1-1.el5.noarch
error: %post(fonts-punjabi-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
Upgrading fonts-malayalam-2.3.1.1-1.el5.noarch
error: %post(fonts-malayalam-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
--
Upgrading fonts-telugu-2.3.1.1-1.el5.noarch
error: %post(fonts-telugu-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9
--
Upgrading fonts-gujarati-2.3.1.1-1.el5.noarch
error: %post(fonts-gujarati-2.3.1.1-1.el5.noarch) scriptlet failed, exit status 9

Expected results:
No errors should be present

Additional info:

Comment 1 Pavel Holica 2011-05-09 12:29:24 UTC
Created attachment 497777 [details]
upgrade.log

Comment 3 Alexander Todorov 2011-05-25 08:18:03 UTC

*** This bug has been marked as a duplicate of bug 469190 ***

Comment 4 Pravin Satpute 2011-06-22 06:59:52 UTC
hi Alexander,

  I have given patch for this, even updated errata for same, see fixed in version fonts-indic-2.3.1.1-2.el5.
  I think better to proceed with this bug.

Comment 5 Pravin Satpute 2011-06-23 06:43:31 UTC
#469190 has few more packages giving the same error, here i tried to fix this problem in fonts-indic spec file iteslf. 

Let see if it works. If its working same way we can apply in other fonts packages as well.

Comment 8 errata-xmlrpc 2011-07-21 06:41:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0978.html


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