Bug 57478 - preun script causes error during upgrade
Summary: preun script causes error during upgrade
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Powertools
Classification: Retired
Component: kwintv
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-13 17:59 UTC by Michael Schwendt
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-12-13 17:59:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Michael Schwendt 2001-12-13 17:59:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120

Description of problem:
Upgrading a Red Hat kwintv package to a newer package release without using
special RPM options removes the consolehelper link from /usr/bin/kv4lsetup.

preuninstall scriptlet (through /bin/sh):
rm /usr/bin/kv4lsetup


Version-Release number of selected component (if applicable):
0.8.5-5, 0.8.5-6 (than preview)

How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh kwintv-some-old-package.rpm
2. rpm -Uvh kwintv-0.8.5-5.i386.rpm
3. file /usr/bin/kv4lsetup



Actual Results:  /usr/bin/kv4lsetup: No such file or directory

(Additionally, rpm -e kwintv would fail to erase because of the preun
returning an error on the non-existant file/link. And rpm -e --noscripts as
a work-around doesn't remove the kwintv fonts from font path.)

Expected Results:  /usr/bin/kv4lsetup: symbolic link to consolehelper

(Additionally, rpm -e kwintv without no problems.)

Additional info:

kwintv development continues at  http://www.kwintv.org  and fixes a series
of bugs in 0.8.5 and later.

Comment 1 Than Ngo 2001-12-14 17:33:10 UTC
it's a bug in old version. it's fixed in kwintv-0.8.5-7. You find it in
ftp://people.redhat.com/than/7.1

Notice: this bug will appear if you update kwintv-0.8.5-7, because preun in old
rpm will run by updating!

But updating next version will work correct!

I will update 0.8.10 soon.


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