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 7976] New: mkuser script fails with: user already exists with group nogroup
Date: Thu, 26 Mar 2015 12:23:07 +0000 (UTC)	[thread overview]
Message-ID: <bug-7976-163@https.bugs.busybox.net/> (raw)

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

           Summary: mkuser script fails with: user already exists with
                    group nogroup
           Product: buildroot
           Version: 2015.02
          Platform: PC
        OS/Version: Windows
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: tommygunsster at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


The file:

buildroot-2015.02/support/scripts/mkusers 

Lines: 170-173:
    # check the user does not already exist in another group
    if [ -n "${_ugroup}" -a "${_ugroup}" != "${group}" ]; then
        fail "user already exists with group '${_ugroup}'\n"
    fi

Issue causes a total failure to build if the user exists with the group
already.  This shouldn't happen as it actually has less work to do right?

My work around was to comment the fail line and all seems to have continued to
work properly.

I don't know what impacts this has but as it's not failing to a real "problem"
and the mkusers script is new from what I can find, I doubt there will be any
major issues.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2015-03-26 12:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 12:23 bugzilla at busybox.net [this message]
2015-03-26 12:35 ` [Buildroot] [Bug 7976] mkuser script fails with: user already exists with group nogroup bugzilla at busybox.net
2015-03-26 14:28 ` bugzilla at busybox.net
2015-03-26 16:30 ` bugzilla at busybox.net
2015-03-26 17:23 ` bugzilla at busybox.net
2015-03-26 17:37 ` bugzilla at busybox.net
2015-03-26 20:34 ` bugzilla at busybox.net
2015-03-26 20:36 ` bugzilla at busybox.net
2015-03-26 21:11 ` bugzilla at busybox.net
2015-03-29 15:37 ` bugzilla at busybox.net
2015-03-29 17:18 ` bugzilla at busybox.net
2015-03-29 17:19 ` bugzilla at busybox.net
2015-03-29 17:24 ` bugzilla at busybox.net
2015-03-29 18:04 ` bugzilla at busybox.net
2015-03-29 18:09 ` 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-7976-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