public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 10/20] meta: mark network and sudo tasks
Date: Wed, 20 Jul 2022 08:47:25 +0300	[thread overview]
Message-ID: <ab9c9fc7-cddc-dcf4-a8f2-b377626860e6@ilbers.de> (raw)
In-Reply-To: <AS4PR10MB53187ED8E6B2138C336B2AAFED8E9@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>

20.07.2022 08:40, Schmidt, Adriaan wrote:
> Anton Mikanovich, Dienstag, 19. Juli 2022 15:00:
>> Network access from tasks is now disabled by default. This means that
>> tasks accessing the network need to be marked as such with the network
>> flag.
>>
>> The same marking is also required for the tasks used sudo.
> When testing in one of our downstream layers I found that the task
> do_containerize in imagetypes_container.bbclass also needs [network] = "1".
>
> Adriaan

Will add in next version, thanks for checking.

There are two main places to test for some missed changes:
1) missed network flags
2) missed old-syntax overrides


  reply	other threads:[~2022-07-20  5:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 12:59 [PATCH v3 00/20] Migrate to Bitbake 2.0 Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 01/20] meta: change deprecated parse calls Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 02/20] scripts/contrib: Add override conversion script Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 03/20] scripts/contrib: configure " Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 04/20] meta-isar: set default branch names Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 05/20] meta: remove non recommended syntax Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 06/20] bitbake: Update to Bitbake 2.0.1 Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 07/20] doc: require zstd tool Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 08/20] meta: update bitbake variables Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 09/20] bitbake.conf: align hash vars with openembedded Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 10/20] meta: mark network and sudo tasks Anton Mikanovich
2022-07-20  5:40   ` Schmidt, Adriaan
2022-07-20  5:47     ` Anton Mikanovich [this message]
2022-07-19 12:59 ` [PATCH v3 11/20] meta: update overrides syntax Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 12/20] sstate: update bbclass Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 13/20] bitbake.conf: declare default XZ and ZSTD options Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 14/20] Revert "devshell: Use different termination test to avoid warnings" Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 15/20] meta: align with OE-core libraries update Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 16/20] Revert "Revert "devshell: Use different termination test to avoid warnings"" Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 17/20] CI: Adopt tests to syntax change Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 18/20] isar-sstate: adopt sstate maintenance script Anton Mikanovich
2022-07-19 12:59 ` [PATCH v3 19/20] Revert "bitbake: Make 3.6.0 the minimum python version" Anton Mikanovich
2022-07-19 13:00 ` [PATCH v3 20/20] Revert "utils/ply: Change md5 usages to work on FIPS enabled hosts" Anton Mikanovich

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=ab9c9fc7-cddc-dcf4-a8f2-b377626860e6@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.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