rpm4/rpm5 incompat: rpm5 firing on provides

Jeffrey Johnson n3npq at me.com
Tue Oct 30 17:04:03 CET 2012


On Oct 30, 2012, at 11:48 AM, Elan Ruusamäe wrote:

> On 30.10.2012 17:42, Jeffrey Johnson wrote:
>> Its rather unusual to expect
>> a script to run after all package contents -- including
>> the trigger script -- have been removed.
> the trigger is to migrate config files from "initscripts" package from redhat to pld "rc-scripts" package
> 

Duplicating what scripts one expects, and marking with %config so no
local modifications are lost, and then
	Obsoletes: initscripts < X.Y.Z
	Conflicts: initscripts < X.Y.Z
	Provides: initscripts = X.Y.Z
is the "standard" way that a package renaming from "ini scripts" -> "rc-files" is achieved.

Note no trigger needed and that %config is used (which cannot be achieved through
scripting because there is no ability to track %confoig file states into an rpmdb).

> so if "initscript" package is removed (replaced by rc-scripts), trigger locates interface configs to directory "rc-scripts" expects
> 

Is the directory renaming really necessary? That is a different problem than package renaming.

And the copy would have to be done much earlier than %triggerpostun with an ordering
dependency, to ensure that the contents that need to be copied/saved exist and haven't
already been removed.

73 de Jeff



More information about the pld-devel-en mailing list