All of lore.kernel.org
 help / color / mirror / Atom feed
From: mrksvolk@googlemail.com
To: antonin.godard@bootlin.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 5/5] go-mod-update-modules: include the generated files from the class
Date: Wed, 23 Sep 2026 19:23:06 +0200	[thread overview]
Message-ID: <JYUTLT.IUWOIA0CTIB23@googlemail.com> (raw)
In-Reply-To: <DLLWONAJMUWW.JNH415ZXTGVI@bootlin.com>

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

Sure. Just tell me, if and when you want the patch.

On Tue, Sep 22 2026 at 16:14:03 +02:00:00, Antonin Godard via 
lists.openembedded.org 
<antonin.godard=bootlin.com@lists.openembedded.org> wrote:
> Hi,
> 
> On Tue Sep 22, 2026 at 11:23 AM CEST, Markus Volk via 
> lists.openembedded.org wrote:
>>  A new recipe could not be parsed before its first update_modules run
>>  because it had to require the two generated files itself. Include 
>> them
>>  from the class instead, relative to the recipe, so a missing file is
>>  tolerated until the task has written it.
> 
> This has the following side-effect for recipes already including the 
> file(s):
> 
> stdio: WARNING: 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale_1.102.3.bb: 
> Duplicate inclusion for 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale-go-mods.inc 
> in 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale_1.102.3.bb
> stdio: WARNING: 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale_1.102.3.bb: 
> Duplicate inclusion for 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale-licenses.inc 
> in 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-networking/recipes-connectivity/tailscale/tailscale_1.102.3.bb
> stdio: WARNING: 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-extended/simpleiot/simpleiot_0.18.5.bb: 
> Duplicate inclusion for 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-extended/simpleiot/simpleiot-go-mods.inc 
> in 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-extended/simpleiot/simpleiot_0.18.5.bb
> stdio: WARNING: 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible_2025.05.28.bb: 
> Duplicate inclusion for 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible-go-mods.inc 
> in 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible_2025.05.28.bb
> stdio: WARNING: 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible_2025.05.28.bb: 
> Duplicate inclusion for 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible-licenses.inc 
> in 
> /srv/pokybuild/yocto-worker/meta-virt/build/meta-openembedded/meta-oe/recipes-support/crucible/crucible_2025.05.28.bb
> 
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/4515>
> 
> If this is merged we'll need to adjust these recipes. Also if this is 
> merged
> please send an update to
> <https://git.yoctoproject.org/yocto-docs/tree/documentation/migration-guides/migration-6.1.rst>
> on the documentation mailing list to let people know why this is 
> happening in
> their build.
> 
> Thanks,
> Antonin
> 
> 
> 


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

  reply	other threads:[~2026-09-23 19:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  9:23 [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange Markus Volk
2026-09-22  9:23 ` [oe-core][PATCH 2/5] cpan: survive the Makefile that MakeMaker rebuilds under us Markus Volk
2026-09-26 14:05   ` Paul Barker
2026-09-26 19:03     ` Markus Volk
2026-09-22  9:23 ` [oe-core][PATCH 3/5] spdx_license: give UnknownId a name Markus Volk
2026-09-22  9:23 ` [oe-core][PATCH 4/5] license_finder: normalise license texts before hashing Markus Volk
2026-09-22  9:23 ` [oe-core][PATCH 5/5] go-mod-update-modules: include the generated files from the class Markus Volk
2026-09-22 14:14   ` Antonin Godard
2026-09-23 17:23     ` mrksvolk [this message]
2026-09-23 18:03     ` Khem Raj
2026-09-25 11:18   ` Ross Burton
2026-09-25 16:27     ` Markus Volk
2026-09-22  9:33 ` Patchtest results for [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange patchtest
2026-09-26 13:53 ` Paul Barker

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=JYUTLT.IUWOIA0CTIB23@googlemail.com \
    --to=mrksvolk@googlemail.com \
    --cc=antonin.godard@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.