From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: RE: [PATCH] sstate: Make image cache imagetype-specific
Date: Wed, 22 Dec 2021 15:26:22 +0000 [thread overview]
Message-ID: <AS4PR10MB53184048A6AA342B1F8AC5FFED7D9@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4f919718-1285-f9bf-f390-2d86f22e8d60@ilbers.de>
Anton Mikanovich, 22. Dezember 2021 15:56:
> To: isar-users <isar-users@googlegroups.com>
> Subject: Re: [PATCH] sstate: Make image cache imagetype-specific
>
> 15.12.2021 15:57, Anton Mikanovich wrote:
> > Building of isar-image-base for targets qemuamd64-buster-tgz and
> > qemuamd64-buster-cpiogz with one bitbake call fails with:
> >
> > ERROR: mc:qemuamd64-buster-tgz:isar-image-base-1.0-r0 do_rootfs: Package
> already staged
> >
> > This is caused by sstate cache conflict for those two packages.
> > We need to add image type to sstate manifest data to fix the issue.
> >
> > Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>
> Does anyone against merging this first to fix the full CI, and rebuild
> workdir sharing after the release?
It's fine with me. The restructuring of the imaging process will be a bigger thing we should start after the release.
Adriaan
next prev parent reply other threads:[~2021-12-22 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 12:57 Anton Mikanovich
2021-12-15 14:33 ` Schmidt, Adriaan
2021-12-16 9:22 ` Anton Mikanovich
2021-12-16 14:56 ` Jan Kiszka
2021-12-17 10:53 ` Baurzhan Ismagulov
2021-12-17 11:24 ` Jan Kiszka
2021-12-22 14:56 ` Anton Mikanovich
2021-12-22 15:26 ` Schmidt, Adriaan [this message]
2021-12-23 10:55 ` 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=AS4PR10MB53184048A6AA342B1F8AC5FFED7D9@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
--to=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--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