public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Sun, Yi" <yi.sun@intel.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Build Failed for RISC-V Image Using isar/kas-container
Date: Sun, 27 Apr 2025 17:13:44 +0800	[thread overview]
Message-ID: <aA31SH0LDkL14Tgy@ysun46-mobl.ccr.corp.intel.com> (raw)
In-Reply-To: <aAe29hiwtKQxIPe7@ysun46-mobl.ccr.corp.intel.com>

On 22.04.2025 23:34, Sun, Yi wrote:
>On 22.04.2025 16:56, Uladzimir Bely wrote:
>>On Tue, 2025-04-22 at 21:14 +0800, Sun, Yi wrote:
>>>On 17.04.2025 08:58, Uladzimir Bely wrote:
>>>>
>>>> Hello.
>>>>
>>>> This looks like a temporary bug, when `ubuntu-ports` repo is
>>>> temporary
>>>> not synchronized with `ubuntu` one. We periodicaly face it and
>>>> can't do
>>>> anything with it.
>>>>
>>>> I also this issue now when crossbuilding riscv64 and arm64 ubuntu-
>>>> noble
>>>> targets. It was not reproduced week ago.
>>>>
>>>> There are two options to get a successfull build:
>>>>
>>>> 1. Disable cross-compile option - but it is relatively slow.
>>>> 2. Use some snapshot that is known to work.
>>>>
>>>> For example, this additional configuration (I used one-week-ago
>>>> snapshot) works for me:
>>>>
>>>> ```
>>>> Mirror selection
>>>> - [*] Use the distros snapshot mirror
>>>>  - (*) Custom date
>>>>    - (20250410T000000Z) Custom snapshot date
>>>> ```
>>>>
>>>> I'm attaching kas configuration I can get working build with.
>>>
>>>Hi Uladzimir,
>>>
>>>I'm adding some actual .bb files for my project and have a few
>>>questions.
>>>
>>>1, It seems the installation of the linux-libc-dev package is failing
>>>in the host rootfs.
>>>Have you happened to run into this issue before?
>>>
>>>```
>>>> Broken libc6-dev:amd64 Depends on linux-libc-dev:amd64 < none @un
>>>> pH >                                       
>>>>   Considering linux-libc-dev:amd64 1 as a solution to libc6-
>>>> dev:amd64 24                                     
>>>>   Considering linux-libc-dev:amd64 1 as a solution to libc6-
>>>> dev:amd64 24                                     
>>>> Done                                                               
>>>>                                           
>>>> Some packages could not be installed. This may mean that you
>>>> have                                            
>>>> requested an impossible situation or if you are using the
>>>> unstable                                           
>>>> distribution that some required packages have not yet been
>>>> created                                           
>>>> or been moved out of
>>>> Incoming.                                                          
>>>>                      
>>>> The following information may help to resolve the
>>>> situation:                                                 
>>>>                                                                    
>>>>                                           
>>>> The following packages have unmet
>>>> dependencies:                                                      
>>>>         
>>>>  libc6-dev : Depends: linux-libc-dev but it is not
>>>> installable                                               
>>>> E: Unable to correct problems, you have held broken
>>>> packages.                                                
>>>> WARNING: exit code 100 from a shell
>>>> command.                                                           
>>>>       
>>>> DEBUG: Executing shell function
>>>> rootfs_do_umounts                                                  
>>>>           
>>>> DEBUG: Shell function rootfs_do_umounts
>>>> finished                                                           
>>>>   
>>>> DEBUG: Python function do_rootfs_install
>>>> finished                                                           
>>>>  
>>>ERROR: Task (/build/../repo/meta-isar/recipes-devtools/sbuild-
>>>chroot/sbuild-chroot-host-db2m.bb:do_rootfs_install) failed with exit
>>>code '1'                                                            
>>>```
>>>
>>
>>Yes, it happend at least previous week (not only for riscv64, but also
>>for e.g. arm64) and using snapshot was a working solution.
>>
>>You can see this issue in e.g. CrossTest.test_cross in our Gitlab CI
>>https://gitlab.isar-build.org/ilbers/isar/-/jobs/2159
>>
>>Today it seems to be fixed by ubuntu upstream just works with main
>>ubuntu/ubuntu-ports repos.
>
>You saved me again! I was using the snapshot you mentioned last time: "20250410T000000Z".
>
>Anyway, I just rebuilt the project without the snapshot, and everything is working perfectly now!
>
>By the way, is there a way to get a full list of available snapshots? I checked https://snapshot.ubuntu.com/, but couldn't find a clear way to list all the snapshot timestamps.
>
>>
Hi @Uladzimir 

Could you please guide me a bit on how to get a snapshot timestamp?
For example, if I want to use the snapshot on 2025/04/22 where I had
a successful pass, how can I find the exact timestamp for it?

Thanks
    --Sun, Yi

-- 
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/aA31SH0LDkL14Tgy%40ysun46-mobl.ccr.corp.intel.com.

  reply	other threads:[~2025-04-27  9:14 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
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 [this message]
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=aA31SH0LDkL14Tgy@ysun46-mobl.ccr.corp.intel.com \
    --to=yi.sun@intel.com \
    --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