Bug#844339: [PATCH v2 2/4] libvirt-daemon-system.{config,templates,postinst}: warn if allocated uid/gid cannot be used

2016-11-18 Thread Mauricio Faria de Oliveira
On 11/18/2016 06:24 AM, Guido Günther wrote: Exactly. That's why NEWS.Debian is nicer iff the user libvirt-qemu exists but with "wrong" (legacy) uid/gid on existing installations and Debconf is better for new installations where the uid/gid is already taken. Thanks for the debconf/NEWS.Debian

Bug#844339: [PATCH v2 2/4] libvirt-daemon-system.{config,templates,postinst}: warn if allocated uid/gid cannot be used

2016-11-18 Thread Guido Günther
Hi Mauricio, On Thu, Nov 17, 2016 at 07:53:55PM -0200, Mauricio Faria de Oliveira wrote: > On 11/17/2016 05:37 PM, Guido Günther wrote: > > I'm basically fine with all of this (but did not du any actual testing) > > Cool. > > > but we should not warn if the user/group already exists (even with

Bug#844339: [PATCH v2 2/4] libvirt-daemon-system.{config,templates,postinst}: warn if allocated uid/gid cannot be used

2016-11-17 Thread Mauricio Faria de Oliveira
On 11/17/2016 05:37 PM, Guido Günther wrote: I'm basically fine with all of this (but did not du any actual testing) Cool. but we should not warn if the user/group already exists (even with the wrong uid). Otherwise we'd warn over and over again, we don't want to force users to change

Bug#844339: [PATCH v2 2/4] libvirt-daemon-system.{config,templates,postinst}: warn if allocated uid/gid cannot be used

2016-11-17 Thread Guido Günther
Hi, On Thu, Nov 17, 2016 at 10:51:40AM -0200, Mauricio Faria de Oliveira wrote: > If the libvirt-qemu user/group already exists with different > uid/gid than the allocated numeric ID (64055), or if this ID > is already in use by another user/group, stop/ask user if it > is OK to continue (e.g., no

Bug#844339: [PATCH v2 2/4] libvirt-daemon-system.{config,templates,postinst}: warn if allocated uid/gid cannot be used

2016-11-17 Thread Mauricio Faria de Oliveira
If the libvirt-qemu user/group already exists with different uid/gid than the allocated numeric ID (64055), or if this ID is already in use by another user/group, stop/ask user if it is OK to continue (e.g., no plans to perform guest migration over NFS) or abort to go fix the problem.