Devuan bug report logs - #548
eudev: postinst fails when kvm group present

Full log

Message #40 received at 548@bugs.devuan.org (full text, mbox, reply):

Received: (at 548) by bugs.devuan.org; 22 Feb 2021 00:00:01 +0000
Return-Path: <olaf@ueda.ne.jp>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Mon, 22 Feb 2021 00:00:01 +0000 (UTC)
Received: from mo-sw.mose-mail.jp (mo-sw1800-0.mose-mail.jp [202.238.237.1])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id F3756F60D83
	for <548@bugs.devuan.org>; Mon, 22 Feb 2021 00:53:01 +0100 (CET)
Received: by mo-sw.mose-mail.jp (mose-mo-sw1800) id 11LNqvxA000990; Mon, 22 Feb 2021 08:52:58 +0900
Received: from quark (localhost [127.0.0.1])
	by mbox.mose-mail.jp (mose-mbox1801) id 11LNqsas010508
	for <548@bugs.devuan.org>; Mon, 22 Feb 2021 08:52:56 +0900
Received: from olaf (uid 1000)
	(envelope-from olaf@ueda.ne.jp)
	id 285097
	by quark (DragonFly Mail Agent v0.11);
	Mon, 22 Feb 2021 08:52:54 +0900
References: <161335070595.15755.13300177891033620677.reportbug@vostro> <YDJLa93PayOG/r/B@ascii> <307f0fd2e77aad5973df6c3c24a4346caa0181f7.camel@gmail.com>
User-agent: mu4e 1.0; emacs 26.1
From: Olaf Meeuwissen <paddy-hack@member.fsf.org>
To: svante.signell@gmail.com,
        devuan developers internal list <devuan-dev@lists.dyne.org>
Cc: Ralph Ronnquist <ralph.ronnquist@gmail.com>, 548@bugs.devuan.org
Subject: Re: [devuan-dev] bug#548: #548: Cannot reproduce
In-reply-to: <307f0fd2e77aad5973df6c3c24a4346caa0181f7.camel@gmail.com>
Date: Mon, 22 Feb 2021 08:52:54 +0900
Message-ID: <87lfbht1ux.fsf@quark>
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Status: No, score=0.2 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Hi,

Svante Signell writes:

> On Sun, 2021-02-21 at 23:00 +1100, Ralph Ronnquist wrote:
>> You'll need to make sure the kvm group has a gid > 1000.

Mostly correct.  My original report mentioned I had a regular group as
opposed to a system group.  The exact ranges for these are customizable
but the defaults are such that regular groups get 1000-60000.
BTW, the defaults are in /etc/login.defs.  You're looking for GID_MIN
and GID_MAX.  The system group values, SYS_GID_MIN and SYS_GID_MAX are
mentioned in comments.

>> E.g. edit /etc/group and change the kvm line from say 106 to 10666,
>> then
>>
>> # apt-get install --reinstall eudev
>>
>> fails with:
>> ----
>> The group `kvm' already exists and is not a system group. Exiting.
>> dpkg: error processing package eudev (--configure):
>>  installed eudev package post-installation script subprocess returned
>> error exit status 1
>> Processing triggers for man-db (2.8.5-2) ...
>> Errors were encountered while processing:
>>  eudev
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Problem is if non-system groups: input, kvm and render should be
> allowed or not. The whole idea of system group names is that these
> names should be reserved?? WDYT?

I also mentioned this possibility, that kvm might have to be a system
group, in my original issue but could not find any definitive list of
system groups in Debian Policy and didn't look elsewhere.

If these groups must be system groups, then I think the right thing to
do is to log the discrepancy, change the group's ID *and* reassign the
group for all file system entries that have the old ID.

For the time being, I am still using my regular kvm group, i.e. with a
GID > 1000.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join

Send a report that this bug log contains spam.