RE: workaround for broken postuninstall during upgrade?

["Huttner, Michael N." <michael huttner gs com>]

The broken rpm has a postuninstall script with "rm -rf
/opt/myapp-1.2.3/*" which removes everything under the install prefix,
including all new content provided by updating with the new rpm release.
The upgrade (via "up2date -u myapp")works perfectly, except we are left
with an empty directory under the install prefix.

-----Original Message-----
From: Jeff Johnson [mailto:n3npq jbj gmail com] 
Sent: Tuesday, November 28, 2006 8:09 PM
To: RPM Package Manager
Subject: Re: workaround for broken postuninstall during upgrade?

On 11/28/06, Huttner, Michael N. <michael huttner gs com> wrote:
> I've got an rpm installed on a large number of machines.  This package
has a
> defective postuninstall script (eg, "rm -f /myapp") which will remove
new
> payload content in an upgrade.  We need to find a creative solution
which
> allows users to upgrade this broken rpm, ideally via "up2date -u
myapp".  Is
> there any way to provide an upgrade, combination of new packages, or
trigger
> which can do this?   I do not as yet know any way to prevent the bad
package
> postuninstall or force the bad package to completely uninstall itself
before
> upgrading with a new package.
>

If you meant literally that an already deployed package is failing to
upgrade because
"rm -f /myapp" is failing in %postun, then adding
     touch /myapp
to the newer packages %post will create the missing ingredient that
the already deployed package needs in order to succeed.

Otherwise you need to supply more specific details of why %postun is
failing.

73 de Jeff