public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH 1/1] isar-apt: fix race-condition in do_cache_config
Date: Fri, 5 Jun 2026 17:22:40 +0300	[thread overview]
Message-ID: <b2f4f983-6dc8-4f7c-ae41-4e5e6a3c0319@ilbers.de> (raw)
In-Reply-To: <d66bb0d7-ec11-45b4-8ab1-99c33c9c05c2@ilbers.de>

04.06.2026 12:39, Anton Mikanovich wrote:
> Hello Felix,
>
> Thanks for the fix.
> It looks like the patch is working, but on the full CI other issue 
> observed.
> Don't think it is related, but rechecking will take some time.
>
> Just in case, here is the failure during do_rootfs_install task of
> isar-image-base recipe for virtualbox-bullseye target:
>
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-rJzE6r/16-example-raw_0.3_all.deb (--unpack):
> cannot access archive 
> '/tmp/apt-dpkg-install-rJzE6r/16-example-raw_0.3_all.deb': No such 
> file or directory
>
Ok, I've found the reason of one more race in do_rootfs_install:
Apt-get don't cache debs from isar-apt (because of file:// scheme) to
/var/cache/apt/archives, so our isar-apt locking on 
rootfs_install_pkgs_download
don't really work.
Will merge this fix and prepare the next fix for do_rootfs_install soon.

-- 
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/b2f4f983-6dc8-4f7c-ae41-4e5e6a3c0319%40ilbers.de.

  reply	other threads:[~2026-06-05 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 11:46 'Felix Moessbauer' via isar-users
2026-06-03 11:56 ` 'MOESSBAUER, Felix' via isar-users
2026-06-04  9:39   ` Anton Mikanovich
2026-06-05 14:22     ` Anton Mikanovich [this message]
2026-06-05 14:24 ` 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=b2f4f983-6dc8-4f7c-ae41-4e5e6a3c0319@ilbers.de \
    --to=amikan@ilbers.de \
    --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