From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Cross-building for older releases on trixie broken?
Date: Fri, 19 Sep 2025 11:23:06 +0300 [thread overview]
Message-ID: <7dffd1d05be653b03c844296d58f8183791118b5.camel@ilbers.de> (raw)
In-Reply-To: <4dca8e24-ece6-405c-8f99-28f39d85780e@siemens.com>
On Thu, 2025-09-18 at 07:49 +0200, 'Jan Kiszka' via isar-users wrote:
> Hi,
>
> for some days, I'm playing with a trixie-based kas container
> (currently
> available via kas-isar:next from upstream), and I it seems I ran into
> an
> issue that might be isar-related: Building e.g. qemu-arm64:bookworm
> with
> that container fails:
>
> > Setup apt archive
> > -----------------
> >
> > Merged Build-Depends: debhelper-compat (= 13), build-
> > essential:amd64,
> crossbuild-essential-arm64:amd64, apt-utils:amd64, libc-dev:arm64,
> libstdc++-dev:arm64
> > Filtered Build-Depends: debhelper-compat (= 13),
> build-essential:amd64, crossbuild-essential-arm64:amd64,
> apt-utils:amd64, libc-dev:arm64, libstdc++-dev:arm64
> > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
> '/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive/sbuild-
> build-depends-main-dummy.deb'.
> > Ign:1 copy:/build/sshd-regen-keys-QAjoa6/resolver-
> > ruuPrM/apt_archive
> ./ InRelease
> > Get:2 copy:/build/sshd-regen-keys-QAjoa6/resolver-
> > ruuPrM/apt_archive
> ./ Release [609 B]
> > Ign:3 copy:/build/sshd-regen-keys-QAjoa6/resolver-
> > ruuPrM/apt_archive
> ./ Release.gpg
> > Get:4 copy:/build/sshd-regen-keys-QAjoa6/resolver-
> > ruuPrM/apt_archive
> ./ Sources [690 B]
> > Get:5 copy:/build/sshd-regen-keys-QAjoa6/resolver-
> > ruuPrM/apt_archive
> ./ Packages [733 B]
> > Fetched 2032 B in 0s (0 B/s)
> > Reading package lists...
> > Reading package lists...
> >
> > Install main build dependencies (apt-based resolver)
> > ----------------------------------------------------
> >
> > Installing build dependencies
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > E: Unable to locate package sbuild-build-depends-main-dummy
> > apt-get failed.
> > E: Package installation failed
> > Not removing build depends: cloned chroot in use
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > E: Unable to locate package sbuild-build-depends-main-dummy
> > apt-get failed.
> >
>
> That was part of the sshd-regen-keys package build, but all package
> seem
> to fail this way.
>
> I suspect we are improperly using the host dpkg tooling here, rather
> than that from the target distro (see other recent discussions we had
> here)...
>
> Jan
>
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center
Hello, Jan.
I took a quick look at this. It seems cross-building is broken for
trixie host only for bookworm target. Buster, bullseye and trixie
targets looks OK.
The reason is still not clear for me - some failure happens with
apt/dependencies, even before dpkg-buildpackage is called.
Will try to debug.
--
Best regards,
Uladzimir.
--
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/7dffd1d05be653b03c844296d58f8183791118b5.camel%40ilbers.de.
next prev parent reply other threads:[~2025-09-19 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 5:49 'Jan Kiszka' via isar-users
2025-09-19 8:23 ` Uladzimir Bely [this message]
2025-09-19 9:32 ` 'Jan Kiszka' via isar-users
2025-10-03 13:50 ` Uladzimir Bely
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=7dffd1d05be653b03c844296d58f8183791118b5.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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