Re: [openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

2015-07-13 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 UPD: in the end, we went the easy way, emulating .rpmnew process in %post scriptlets (see the patch linked in my previous email, if you want to see details). AFAIK there is no distinguished directive or macro that would allow to maintain .rpmnew

Re: [openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

2015-07-07 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/02/2015 06:35 PM, Matt Riedemann wrote: This change in neutron [1] renames the linuxbridge and openvswitch plugin config files. I'm familiar with the %config(noreplace) directive in rpm but I'm not sure if there is a special trick with

[openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

2015-07-02 Thread Matt Riedemann
This change in neutron [1] renames the linuxbridge and openvswitch plugin config files. I'm familiar with the %config(noreplace) directive in rpm but I'm not sure if there is a special trick with rpm to rename a config file while not losing the changes in the config file during the upgrade.

Re: [openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

2015-07-02 Thread Kyle Mestery
On Thu, Jul 2, 2015 at 10:35 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: This change in neutron [1] renames the linuxbridge and openvswitch plugin config files. I'm familiar with the %config(noreplace) directive in rpm but I'm not sure if there is a special trick with rpm to rename a

Re: [openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

2015-07-02 Thread Matt Riedemann
On 7/2/2015 10:39 AM, Kyle Mestery wrote: On Thu, Jul 2, 2015 at 10:35 AM, Matt Riedemann mrie...@linux.vnet.ibm.com mailto:mrie...@linux.vnet.ibm.com wrote: This change in neutron [1] renames the linuxbridge and openvswitch plugin config files. I'm familiar with the