Re: RE: workaround for broken postuninstall during upgrade?

["Jeff Johnson" <n3npq jbj gmail com>]

On 11/29/06, Huttner, Michael N. <michael huttner gs com> wrote:
> 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.

Got it, thanks.

Here's what I would do:

   in %post of the new package, rename the directory to Something Else

    <the old package erasure with busted %postun runs>

   in %triggerpostun of the new package, rename the directory back to
its original name.

A bit hacky, but will upgrade.

Hint: check the old and new package manifests closely. Because of the hackery,
rpm will *NOT* remove any files that were contained in the old
package, but are not
present in the new package. Replacements (i.e. new package file
replaces old package
file) will be fine, additions as well, its only deletions that you
need to check for.

hth

73 de Jeff