From: "Sun, Yi" <yi.sun@intel.com>
To: Baurzhan Ismagulov <ibr@radix50.net>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: Uladzimir Bely <ubely@ilbers.de>
Subject: RE: Build Failed for RISC-V Image Using isar/kas-container
Date: Tue, 15 Apr 2025 00:33:19 +0000 [thread overview]
Message-ID: <BL3PR11MB636371315D67C5A0F2C0CD2B99B22@BL3PR11MB6363.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BL3PR11MB6363AF77280C959E7C18632D99B22@BL3PR11MB6363.namprd11.prod.outlook.com>
BTW, the error will not happen if run that copy command in the docker manually:
# ./kas/kas-container shell
root@fe0d1f3b7b5e:/build# "/repo/scripts:/repo/bitbake/bin:/usr/sbin:/usr/bin:/sbin:/bin" cp -fpPRH "/build/../repo/meta/recipes-devtools/isar-apt/files/distributions.in" "."
Thanks
--Sun, Yi
-----Original Message-----
From: Sun, Yi
Sent: Tuesday, April 15, 2025 08:10
To: Baurzhan Ismagulov <ibr@radix50.net>; isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>
Subject: RE: Build Failed for RISC-V Image Using isar/kas-container
Hi Baurzhan,
Nope, I'm trying to build it on an Ubuntu 22.04.4 LTS native machine.
Thanks
--Sun, Yi
-----Original Message-----
From: Baurzhan Ismagulov <ibr@radix50.net>
Sent: Monday, April 14, 2025 23:54
To: isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>; Sun, Yi <yi.sun@intel.com>
Subject: Re: Build Failed for RISC-V Image Using isar/kas-container
Hello Sun Yi,
On 2025-04-14 19:48, Sun, Yi wrote:
> cp: failed to preserve ownership for './distributions.in': Invalid argument
Is the underlying storage in any way exotic? Like Windows host, cifs share,
etc.
With kind regards,
Baurzhan
--
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/BL3PR11MB636371315D67C5A0F2C0CD2B99B22%40BL3PR11MB6363.namprd11.prod.outlook.com.
next prev parent reply other threads:[~2025-04-15 0:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 6:38 Sun, Yi
2025-04-13 7:41 ` Uladzimir Bely
2025-04-13 8:02 ` Sun, Yi
2025-04-13 8:18 ` Uladzimir Bely
2025-04-13 9:58 ` Sun, Yi
2025-04-13 14:41 ` Uladzimir Bely
2025-04-14 11:48 ` Sun, Yi
2025-04-14 15:53 ` Baurzhan Ismagulov
2025-04-15 0:10 ` Sun, Yi
2025-04-15 0:33 ` Sun, Yi [this message]
2025-04-16 19:53 ` Uladzimir Bely
2025-04-17 0:19 ` Sun, Yi
2025-04-16 15:42 ` Sun, Yi
2025-04-17 5:58 ` Uladzimir Bely
2025-04-17 12:08 ` Sun, Yi
2025-04-17 15:04 ` Uladzimir Bely
2025-04-22 13:14 ` Sun, Yi
2025-04-22 13:56 ` Uladzimir Bely
2025-04-22 15:34 ` Sun, Yi
2025-04-27 9:13 ` Sun, Yi
2025-04-27 11:32 ` Sun, Yi
2025-04-28 7:24 ` Baurzhan Ismagulov
2025-04-30 5:10 ` Sun, Yi
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=BL3PR11MB636371315D67C5A0F2C0CD2B99B22@BL3PR11MB6363.namprd11.prod.outlook.com \
--to=yi.sun@intel.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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