Bug 979125 change the RPM spec file so that standalone.conf was marked as a %config file so that it was not silently overwritten when upgrading. Since that is a file with expect many users to edit, it would probably be better set to %config(noreplace), so that the new version is created as a .rpmnew file and the existing configuration untouched. Right now (with %config) we overwrite the settings, although a backup saves to .rpmsave, and this can lead to JBoss or customer applications not working correctly because they are missing the custom settings.
Hi Fernando, could you please tell me in which git repo the rpmspec files reside? I'd like to check if this issue is still valid.
This is the dist-git repo "jbossas-standalone" branch jb-eap-6.4-rhel-6 : %config %{jbhomedir}/bin/standalone.conf So I guess the answer is that this change was not implemented. I don't see it ever getting the 3-acks BTW.
A bit late to change the behaviour for 6.4.x, we are already at .10. It has been fixed in EAP 7 instead: %config(noreplace) %{confdir}/%{standaloneService}.conf I suggest we close this as obsolete.
Brad, could we close as WONTFIX as per c#6 ?
It is easy to mark it as noreplace and perhaps it should have been marked like that from 6.0.1. It *is* a significant change of behaviour though, so I will wait for the 3-acks and for it to be added to a CP payload before making the change. P.S.: I am re-assigning this to Permaine as I am no longer in the EAP team.
Fixed, will be in 6.4.15 CR3.
Confirmed, fix is indeed in CP15, hence I'm verifying this for EAP 6.4.15.CP.CR3;
Released on May 18 as part of EAP 6.4.15.