Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12141] New: eudev package is missing "render" and "kvm" groups
Date: Fri, 23 Aug 2019 11:40:46 +0000	[thread overview]
Message-ID: <bug-12141-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=12141

            Bug ID: 12141
           Summary: eudev package is missing "render" and "kvm" groups
           Product: buildroot
           Version: 2019.02.3
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jcowgill+busybox at jcowgill.uk
                CC: buildroot at uclibc.org
  Target Milestone: ---

This commit added some extra groups to the systemd package which are now
required by the default udev rules:
https://git.buildroot.net/buildroot/commit/package/systemd/systemd.mk?id=f208cf296c2c7c049d11d15b6d0546214c4d0357

However, those groups were not added to the eudev package which causes udev to
warn on boot:

    [   20.702706] udevd[67]: specified group 'kvm' unknown

I think both the "render" and "kvm" groups need adding.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-08-23 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 11:40 bugzilla at busybox.net [this message]
2019-09-08  1:15 ` [Buildroot] [Bug 12141] eudev package is missing "render" and "kvm" groups bugzilla at busybox.net
2019-09-15 12:33 ` bugzilla at busybox.net
2019-09-15 13:59 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-12141-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox