Bug 481296 - Error in postun script
Summary: Error in postun script
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: phonon
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: kde42
TreeView+ depends on / blocked
 
Reported: 2009-01-23 13:57 UTC by Quentin Armitage
Modified: 2009-01-23 14:33 UTC (History)
5 users (show)

Fixed In Version: 4.3.0-2.fc11
Clone Of:
Environment:
Last Closed: 2009-01-23 14:33:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Quentin Armitage 2009-01-23 13:57:29 UTC
Description of problem:
yum update reports the following error:
  Cleanup        : phonon                                                 82/86 
/var/tmp/rpm-tmp.qUB4s6: line 4: syntax error: unexpected end of file
warning: %postun(phonon-4.2.96-3.fc11.i386) scriptlet failed, exit status 2

Version-Release number of selected component (if applicable):
4.2.96-3

How reproducible:
Whenever phonon is updated by yum

Steps to Reproduce:
1.yum update phonon
2.
3.
  
Actual results:
yum reports error above

Expected results:
No error

Additional info:
There appears to be a colon missing at the end of the third line of the postun section of the phonon.spec file.

Comment 1 Kevin Kofler 2009-01-23 14:12:03 UTC
Confirming, it's a typo introduced in 4.2.96-3 which is still there in 4.3.0-1. Putting on the KDE42 blocker because this cannot be fixed once the update is out (any user with one of the broken builds will have to rpm -e --noscripts it after upgrading to a fixed version).

Comment 2 Kevin Kofler 2009-01-23 14:12:32 UTC
Fixing.

Comment 3 Kevin Kofler 2009-01-23 14:14:57 UTC
Fix committed.

Comment 4 Kevin Kofler 2009-01-23 14:33:39 UTC
Package: phonon-4.3.0-2.fc11 Tag: dist-f11 Status: complete Built by: kkofler

F9 and F10 (official packages) not affected. Rex, you will need to fix kde-redhat testing though.


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