preventing known-damaging third-party to fedora/epel package upgrade?

Ville Skyttä ville.skytta at iki.fi
Thu Jul 12 18:53:39 UTC 2012


On 2012-07-12 18:01, Paul Wouters wrote:

> Unfortunately, the spec file from upstream did not use
> %config(noreplace). Someone enabled epel and ran "yum update" and the
> EPEL package was seen as an upgrade, and the noreplae bug in their
> package caused our package to blow away their configuration.

noreplace doesn't work like that. Whether it was present in the old
package doesn't matter - the file doesn't even have to be %config in it,
all that counts on upgrades is what's in the new package.

But note also that if the file installed from the old package is
unmodified at time of upgrade (again no matter if it's config at all, or
config with or without noreplace), it will be silently replaced with no
.rpm* backups left behind on upgrade no matter whether the config file
in the new package is noreplace or not.


More information about the devel mailing list