public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
	Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
	amikan <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "akarpovich@ilbers.de" <akarpovich@ilbers.de>
Subject: Re: [PATCH 3/3] rootfs: Deny packages download during install
Date: Thu, 30 Jul 2026 08:18:51 +0200	[thread overview]
Message-ID: <92b21dd8-8d06-4732-9a9a-1cab84536a39@siemens.com> (raw)
In-Reply-To: <83d691b164f521b52ab0cc32c879e064939548c6.camel@siemens.com>

On 30.07.26 08:10, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Wed, 2026-07-29 at 21:39 +0200, Jan Kiszka wrote:
>> On 10.06.26 08:48, Anton Mikanovich wrote:
>>> During the command rootfs_install_pkgs_install no actuall packages
>>> downloading should be done. All the debs must be precached and already
>>> placed in /var/cache/apt/archives, so apt-get can reuse them.
>>>
>>> Currently any downloads in this command are really succeed because we
>>> still have "network" flag on for using sudo, which masks all the
>>> caching issues in previous rootfs install commands.
>>>
>>> To prevent such a cases add "--no-download" option to apt-get.
>>>
>>> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>>> ---
>>>  meta/classes-recipe/rootfs.bbclass | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
>>> index 81384340..f4580421 100644
>>> --- a/meta/classes-recipe/rootfs.bbclass
>>> +++ b/meta/classes-recipe/rootfs.bbclass
>>> @@ -402,7 +402,7 @@ rootfs_install_pkgs_install[progress] = "custom:rootfs_progress.PkgsInstallProgr
>>>  rootfs_install_pkgs_install[network] = "${TASK_USE_SUDO}"
>>>  rootfs_install_pkgs_install() {
>>>      sudo -E chroot "${ROOTFSDIR}" \
>>> -        /usr/bin/apt-get ${ROOTFS_APT_ARGS} ${ROOTFS_PACKAGES}
>>> +        /usr/bin/apt-get ${ROOTFS_APT_ARGS} --no-download ${ROOTFS_PACKAGES}
>>>  }
>>>  
>>>  ROOTFS_INSTALL_COMMAND += "rootfs_restore_initrd_tooling"
>>
>> This commit subtly breaks xenomai-images when generating a compat 
>> userland:
>>
>> kas.yaml:kas/board/qemu-amd64.yaml:kas/opt/xenomai-3.3.x.yaml:kas/opt/linux-6.12.yaml:kas/opt/compat.yaml
>>
>> ...
>> | (Reading database ... 9732 files and directories currently installed.)
>> | Preparing to unpack .../systemd-sysv_252.39-1~deb12u2_amd64.deb ...
>> | Unpacking systemd-sysv (252.39-1~deb12u2) ...
>> | Setting up systemd-sysv (252.39-1~deb12u2) ...
>> | E: Internal Error, Pathname to install is not absolute 'libxenomai1_3.3.2_i386.deb'
>> | 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 (/work/build/../../repo/recipes-core/images/demo-image.bb:do_rootfs_install) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 79 tasks of which 61 didn't need to be rerun and 1 failed.
>>
>> Target distro is trixie here. xenomai-images revision is 
>> 74664edd99cb44c830060207c4dcf5c9ff83c341 with isar set to 
>> b90b722fc2666b806a64f0bf5ca0feeb9b6f203b.
>>
>> Any idea where this could come from??
> 
> Isn't that exactly what Aliaksei fixes in "rootfs: Fix URL parsing"?
> In short, the error happens because the arch part is currently
> stripped.
> 
> [1] https://groups.google.com/g/isar-users/c/rQg0t7GyofM/m/oYZ7z2aEAwAJ
> 

Good hint to look there, but I rather suspect it's "rootfs: Add version
and arch for downloaded package"
(https://groups.google.com/g/isar-users/c/rQg0t7GyofM/m/LORd42aEAwAJ)

Let me try...

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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/92b21dd8-8d06-4732-9a9a-1cab84536a39%40siemens.com.

  reply	other threads:[~2026-07-30  6:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  6:48 [PATCH 0/3] Rootfs install race fix for isar-apt packages Anton Mikanovich
2026-06-10  6:48 ` [PATCH 1/3] rootfs: Allow locking on single install command Anton Mikanovich
2026-06-10  8:23   ` 'MOESSBAUER, Felix' via isar-users
2026-06-11  7:01     ` Anton Mikanovich
2026-06-11 10:08       ` 'MOESSBAUER, Felix' via isar-users
2026-06-10  6:48 ` [PATCH 2/3] rootfs: Download isar-apt packages under isar-apt lock Anton Mikanovich
2026-06-10  6:48 ` [PATCH 3/3] rootfs: Deny packages download during install Anton Mikanovich
2026-06-15  8:55   ` 'MOESSBAUER, Felix' via isar-users
2026-06-15  9:02     ` 'MOESSBAUER, Felix' via isar-users
2026-06-15  9:12     ` Anton Mikanovich
2026-07-29 19:39   ` 'Jan Kiszka' via isar-users
2026-07-30  6:10     ` 'MOESSBAUER, Felix' via isar-users
2026-07-30  6:18       ` 'Jan Kiszka' via isar-users [this message]
2026-06-12 10:53 ` [PATCH 0/3] Rootfs install race fix for isar-apt packages 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=92b21dd8-8d06-4732-9a9a-1cab84536a39@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=akarpovich@ilbers.de \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.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