public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com
Subject: Re: [PATCH 1/3] isar-sstate: add well-known task for dpkg-source
Date: Tue, 29 Sep 2026 10:06:16 +0200	[thread overview]
Message-ID: <75b3a277-6f19-44a1-b792-a54d8115aab4@ilbers.de> (raw)
In-Reply-To: <20260922090930.2322146-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Zhihang

On 9/22/26 11:09, 'Felix Moessbauer' via isar-users wrote:
> These currently accumulate under others, but this is a well known isar
> task. We now map them to the deb entry.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>   scripts/isar-sstate | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/scripts/isar-sstate b/scripts/isar-sstate
> index 767661f6..9e78e8f7 100755
> --- a/scripts/isar-sstate
> +++ b/scripts/isar-sstate
> @@ -803,14 +803,14 @@ def sstate_info(target, verbose, filter, arch, **kwargs):
>       archs = list(set([f.arch for f in all_files]))
>       print(f"INFO: found the following archs: {archs}")
>   
> -    key_task = {'deb': 'dpkg_build',
> -                'rootfs': 'rootfs_install',
> -                'bootstrap': 'bootstrap'}
> +    key_task = {'deb': ['dpkg_build', 'dpkg_source'],
> +                'rootfs': ['rootfs_install'],
> +                'bootstrap': ['bootstrap']}
>       recipes = {k: [] for k in key_task.keys()}
>       others = []
>       for pn in set([f.pn for f in all_files]):
>           tasks = set([f.task for f in all_files if f.pn == pn])
> -        ks = [k for k, v in key_task.items() if v in tasks]
> +        ks = [k for k, v in key_task.items() if any(t in tasks for t in v)]
>           if len(ks) == 1:
>               recipes[ks[0]].append(pn)
>           elif len(ks) == 0:
> @@ -820,7 +820,7 @@ def sstate_info(target, verbose, filter, arch, **kwargs):
>       for k, entries in recipes.items():
>           print(f"Cache entries for {k}:")
>           for pn in entries:
> -            artifacts = [f for f in all_files if f.pn == pn and f.task == key_task[k] and f.suffix in ['tgz', 'tar.zst']]
> +            artifacts = [f for f in all_files if f.pn == pn and f.task in key_task[k] and f.suffix in ['tgz', 'tar.zst']]
>               print(f"  - {pn}: {len(artifacts)} entries")
>       print("Other cache entries:")
>       for pn in others:

-- 
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/75b3a277-6f19-44a1-b792-a54d8115aab4%40ilbers.de.

      parent reply	other threads:[~2026-09-29  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  9:09 'Felix Moessbauer' via isar-users
2026-09-22  9:09 ` [PATCH 2/3] isar-sstate: add well-known task for apt tasks 'Felix Moessbauer' via isar-users
2026-09-22  9:09 ` [PATCH 3/3] isar-sstate: show number of signature files on info 'Felix Moessbauer' via isar-users
2026-09-29  8:06 ` Zhihang Wei [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=75b3a277-6f19-44a1-b792-a54d8115aab4@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@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