From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
Subject: Re: [PATCH] Fix cache-deb-src functionality for non-amd64 builds
Date: Tue, 22 Jul 2025 11:02:01 +0000 [thread overview]
Message-ID: <3223fea8d6e6cad1748a18a391b2aa2a06849023.camel@siemens.com> (raw)
In-Reply-To: <1fe9d1d61cf2db06b18823d331fa5d13a4c21bf5.camel@siemens.com>
On Tue, 2025-07-22 at 06:35 +0000, 'cedric.hombourger@siemens.com' via
isar-users wrote:
> On Tue, 2025-07-22 at 07:27 +0200, Cedric Hombourger wrote:
> > On Thu, 2025-07-17 at 13:51 +0300, Anton Mikanovich wrote:
> > > Commit f0da749f introduced `apt-cache -o Dir=${rootfs} dumpavail`
> > > method to get info about packages installed in rootfs, instead of
> > > parsing dpkg.log previuosly used.
> >
> > previously
> >
> > >
> > > But it does not work in case of foreing architecture used. The
> > > list
> >
> > foreign
> >
> > > comes empty and no source packages get downloaded.
> > >
> > > Instead, chroot into the rootfs and run this inside. The
> > > difference:
> >
> > Yes but with a significant performance hit (QEMU)
> > I can recheck our options. This is a reminder that I had earlier
> > proposed
> > https://lists.isar-build.org/isar-users/20250515150727.1764989-1-cedric.hombourger@siemens.com/T/#t
> > (probably does not address this specific issue though)
>
> That issue did ring a bell and I was able to find the fix I had
> suggested earlier "specify target architecture for apt-cache lookups"
>
>
> https://lists.isar-build.org/isar-users/20250417201747.90299-1-cedric.hombourger@siemens.com/
If that works here as well, it would be WAY better than falling back to
a changeroot.
Felix
>
>
> --
> Cedric Hombourger
> Siemens AG
> www.siemens.com
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/3223fea8d6e6cad1748a18a391b2aa2a06849023.camel%40siemens.com.
next prev parent reply other threads:[~2025-07-22 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 10:51 Anton Mikanovich
2025-07-22 5:27 ` 'cedric.hombourger@siemens.com' via isar-users
2025-07-22 6:35 ` 'cedric.hombourger@siemens.com' via isar-users
2025-07-22 11:02 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-07-22 11:44 ` 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=3223fea8d6e6cad1748a18a391b2aa2a06849023.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@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