Re: [Xen-devel] [PATCH v2] tools/mkrpm: improve version.release handling

2015-03-30 Thread Ian Campbell
On Wed, 2015-03-25 at 14:01 +, George Dunlap wrote: Reviewed-by: George Dunlap george.dun...@eu.citrix.com Tested-by: George Dunlap george.dun...@eu.citrix.com Applied, thanks. ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [PATCH v2] tools/mkrpm: improve version.release handling

2015-03-26 Thread Olaf Hering
On Wed, Mar 25, George Dunlap wrote: Reviewed-by: George Dunlap george.dun...@eu.citrix.com Tested-by: George Dunlap george.dun...@eu.citrix.com Thanks. Whoever is in charge, please backport to staging-4.5 as well. Olaf ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH v2] tools/mkrpm: improve version.release handling

2015-03-25 Thread George Dunlap
On 03/24/2015 02:37 PM, Olaf Hering wrote: An increasing version and/or release number helps to update existing packages without --force as in rpm Uvh --force xen.rpm. Instead its possible to do rpm -Fvh *.rpm to update only already installed packages. The usage of --force disables

[Xen-devel] [PATCH v2] tools/mkrpm: improve version.release handling

2015-03-24 Thread Olaf Hering
An increasing version and/or release number helps to update existing packages without --force as in rpm Uvh --force xen.rpm. Instead its possible to do rpm -Fvh *.rpm to update only already installed packages. The usage of --force disables essentials checks such as file conflict detection. As a