public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mathieu.dubois-briand@bootlin.com, bitbake-devel@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Chen Qi <Qi.Chen@windriver.com>
Subject: Re: [bitbake-devel] [PATCH] bin: Hide os.fork() deprecation warning at module level
Date: Thu, 05 Feb 2026 15:29:00 +0000	[thread overview]
Message-ID: <3fd43d892d87fee01b906801cec60b05bb203feb.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260205-mathieu-fork-warning-filter-v1-1-e4bef89403c1@bootlin.com>

On Thu, 2026-02-05 at 15:13 +0100, Mathieu Dubois-Briand via lists.openembedded.org wrote:
> Add the message filtering directly in the python module where the error
> happens, so we do not need to repeat the filter in all consumers. This
> will also make sure the filter is applied in any user of createDaemon().
> 
> Fixes [YOCTO #16080]
> 
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> Suggested-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>  bin/bitbake         | 1 -
>  bin/bitbake-layers  | 1 -
>  bin/bitbake-server  | 1 -
>  bin/bitbake-worker  | 1 -

Nearly! :)

You need to leave bitbake-worker alone as it has a different use of
os.fork().

Cheers,

Richard


  reply	other threads:[~2026-02-05 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 14:13 [PATCH] bin: Hide os.fork() deprecation warning at module level Mathieu Dubois-Briand
2026-02-05 15:29 ` Richard Purdie [this message]
2026-02-05 17:03   ` [bitbake-devel] " Mathieu Dubois-Briand

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=3fd43d892d87fee01b906801cec60b05bb203feb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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