From: "'Badrikesh Prusty' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: default "Rules-Requires-Root: no", make it configurable
Date: Thu, 18 Sep 2025 23:32:22 -0700 (PDT) [thread overview]
Message-ID: <c5f273e3-ff2d-4501-bfd2-557f18c11906n@googlegroups.com> (raw)
In-Reply-To: <7fed93b4-d62b-4a2d-b8d8-4dd214c2eac6@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1692 bytes --]
Hi Jan,
Created a patch v2: https://groups.google.com/g/isar-users/c/S4gYxHjKqe0
Addressed the comments.
I didn't find any any snake4 recipes in isar's next branch:
meta-isar/recipes-app/snake4/files/debian/control
I hardcoded "Rules-Requires-Root: no" as suggested and performed various
check isar-ci-fast, isar-ci-dev tests. Also tested with upstream
repositories: meta-iot2050, isar-cip-core, meta-tensorbox and the builds
are progressing fine.
Thanks,
Badrikesh
On Wednesday, September 17, 2025 at 2:13:19 PM UTC+5:30 Jan Kiszka wrote:
> On 17.09.25 10:26, Anton Mikanovich wrote:
> > 17/09/2025 11:18, Jan Kiszka wrote:
> >> Hi Anton,
> >>
> >> I see this patch in your test queue but it's not ready for upstream yet
> >> - just to avoid that it accidentally lands in next.
> >>
> >> Jan
> >>
> > Hello Jan,
> >
> > Thanks for keeping an eye on it, I'm just trying to find unbuildable
> > patches
> > as early as possible, so sometimes CI is running even before looking
> > inside of
> > the patch contents or discussions. Will wait for work on it to be
> finished.
> >
> > P.S. I hope we will went to automatic input control sometimes.
>
> Makes sense, thanks for the explanation!
>
> Jan
>
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/c5f273e3-ff2d-4501-bfd2-557f18c11906n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2419 bytes --]
prev parent reply other threads:[~2025-09-19 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 20:42 'Badrikesh Prusty' via isar-users
2025-09-07 20:54 ` 'Badrikesh Prusty' via isar-users
2025-09-08 5:28 ` 'Jan Kiszka' via isar-users
2025-09-08 8:02 ` 'Felix Moessbauer' via isar-users
2025-09-11 9:43 ` 'Prusty, Badrikesh' via isar-users
2025-09-17 8:18 ` 'Jan Kiszka' via isar-users
2025-09-17 8:26 ` Anton Mikanovich
2025-09-17 8:28 ` 'Jan Kiszka' via isar-users
2025-09-19 6:32 ` 'Badrikesh Prusty' via isar-users [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=c5f273e3-ff2d-4501-bfd2-557f18c11906n@googlegroups.com \
--to=isar-users@googlegroups.com \
--cc=badrikesh.prusty@siemens.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