Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "JD Schroeder" <sweng5080@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] distcc: Fix groupname gid change warning
Date: Thu, 26 Oct 2023 06:50:03 -0700	[thread overview]
Message-ID: <6763.1698328203367625894@lists.openembedded.org> (raw)
In-Reply-To: <4e91e1a677bf0e5e2799a982501d7b4cb81a485f.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 3124 bytes --]

On Wed, Sep 27, 2023 at 09:01 AM, Richard Purdie wrote:

> 
> On Wed, 2023-09-27 at 06:07 -0700, JD Schroeder wrote:
> 
>> On Tue, Sep 12, 2023 at 06:03 AM, Ross Burton wrote:
>> 
>>> On 1 Sep 2023, at 11:03, Alexandre Belloni via
>>> lists.openembedded.org
>>> <alexandre.belloni=bootlin.com@lists.openembedded.org> wrote:
>>> 
>>>> 
>>>> Hello,
>>>> 
>>>> This fails on the autobuilders:
>>>> 
>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/3449/steps/12/logs/stdio
>>>> 
>>>> 
>>>> ERROR: Nothing RPROVIDES 'distcc' (but /home/pokybuild/yocto-
>>>> worker/reproducible/build/meta/recipes-
>>>> core/packagegroups/packagegroup-self-hosted.bb,
>>>> /home/pokybuild/yocto-worker/reproducible/build/meta/recipes-
>>>> devtools/devel-config/distcc-config.bb RDEPENDS on or otherwise
>>>> requires it)
>>>> distcc was skipped: Recipe distcc, package distcc-server: system
>>>> groupname "nogroup" does not have a static ID defined. Add
>>>> nogroup to one of these files: /home/pokybuild/yocto-
>>>> worker/reproducible/build/build-st/meta-selftest/files/static-
>>>> group
>>> 
>>> The same problem would hit the ppp-dialin but that recipe doesn’t
>>> get built in the AB in an environment that has static IPs.
>>> 
>>> Ross
>> 
>> I'm seeing the the warnings being generated in a multi-config Yocto
>> build environment. Is there another way to address and fix the
>> warnings I am having with the distcc and ppp-dialin recipes (possibly
>> during parsing) even if they aren't being built in the AB with static
>> IPs?
> 
> It might help if you could describe how to reproduce the problem you're
> seeing?
> 
> "nogroup" should already exist in the underlying base-passwd file so we
> really need to understand why that isn't working. The patch appears
> just to mask the real problem.
> 
> Cheers,
> 
> Richard

Sorry, it has taken a while for me to get back to this. I'm still seeing these warnings:

WARNING: yocto-4.0/poky/meta/recipes-devtools/distcc/distcc_3.4.bb: distcc: Changing groupname nogroup's gid from (1018) to (65534), verify configuration files!

WARNING: yocto-4.0/poky/meta/recipes-connectivity/ppp-dialin/ppp-dialin_0.1.bb: ppp-dialin: Changing groupname nogroup's gid from (1019) to (65534), verify configuration files!

The "nogroup" *does* exist in base-passed in group.master with "nogroup:*:65534:"

So it appears that something is originally setting the nogroup's gid to 1018 as the distcc recipe is parsed and later it gets changed to 65534 which causes the warning.

My patch fixes the warning and probably is not addressing the underlying problem. If someone has a patch they think addresses the underlying problem (clearing up the warning at the same time), I would be more than happy to test it for them in my environment and see if it fixes the warning.

To reiterate this is a nuisance warning fix and not a fundamental issue I'm seeing with my group ids. Addressing the warning in my build environment helps other new warnings that are introduced to be addressed and not ignored.

Thanks,

JD

[-- Attachment #2: Type: text/html, Size: 3427 bytes --]

      reply	other threads:[~2023-10-26 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 14:23 [PATCH 1/2] distcc: Fix groupname gid change warning JD Schroeder
2023-08-31 14:23 ` [PATCH 2/2] ppp-dialin: " JD Schroeder
2023-09-01 10:03 ` [OE-core] [PATCH 1/2] distcc: " Alexandre Belloni
2023-09-12 11:03   ` Ross Burton
2023-09-27 13:07     ` JD Schroeder
2023-09-27 14:01       ` [OE-core] " Richard Purdie
2023-10-26 13:50         ` JD Schroeder [this message]

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=6763.1698328203367625894@lists.openembedded.org \
    --to=sweng5080@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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