On 27.5.2013 12:56, Eran Ben Natan wrote:
I have an RPM that installs a file named informix.xml under Jboss deploy
directory.
This file contains DB connection details that are set after
installation, so I declared it as config file.
After upgrade, RPM creates the .rpmsave file, and unfortunately Jboss
tries to deploy it and fails.
Is there a way to control the location of the .rpmsave file? Or other
way to work around this problem?
I prefer not to put this file outside Jboss and create sym link.
On first place I would investigate why JBoss server tries to load
.rpmsave file.
After quick googling I find:
https://github.com/bobmcwhirter/jboss-cloud/blob/master/specs/jboss-as5-cloud-mod_cluster.spec
and
http://bb10.com/java-jboss-user/2003-05/msg00414.html
This is definitely not the way how configuration files should be handled.
Contact Jboss maintainers and tell them that they should not move
rpmsave and rpmnew files in scriptlets automatically.
Correct way is to mark config files as
%config(noreplace)
and after each installation/upgrade look for all rpmsave and rpmnew
files and merge them manually.
I personally use rpmconf (in package rpmconf) for that task.
Mirek
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
