From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "ubely@ilbers.de" <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: debootstrap bullseye arm64 on trixie host fails
Date: Wed, 24 Jul 2024 07:00:49 +0000 [thread overview]
Message-ID: <57e5b6d845cb590553e247ef77e2a7aa95747dee.camel@siemens.com> (raw)
In-Reply-To: <abd60b8c3e933a0833597a03e442378e82fe10a7.camel@ilbers.de>
On Wed, 2024-07-24 at 09:23 +0300, Uladzimir Bely wrote:
> Hello all.
>
> Some time ago I faced with the issue when debootstrapping arm64
> bullseye system when host qemu version >=8.1. Other architectures and
> target distros (both <= buster and >=bookworm) are not affected, only
> bullseye-arm64 combination.
>
> This makes me use qemu-8.0.5 on host despite 8.2.3 is considered
> stable
> in Gentoo.
>
> I also checked that the issue is reproduced (in Virtualbox machine)
> on
> Debian Trixie, that uses qemu-8.2.4.
>
> The issue https://gitlab.com/qemu-project/qemu/-/issues/2377 was
> opened
> but with no response for now.
>
> Does someone else use host trixie and could confirm this? I'm afraid
> that the issue will pop up when trixie becomes stable.
>
> By the way, we have "Migrate to mmdebstrap" patchset on the list and
> mmdebstrap is not affected.
Then this would be another reason to switch over to mmdebstrap.
I also hope, that we can configure mmdebstrap to use package caches and
apt retries and rate limits. With the recent hickups of the
snapshots.d.o, we really need a solution that is robust. Otherwise we
cannot build against snapshots in CI.
Anyways, I wouldn't spend too much effort into repairing debootstrap,
while most people seem to use mmdebstrap these days anyways.
Felix
>
> --
> Best regards,
> Uladzimir.
>
>
>
--
Siemens AG, Technology
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 on the web visit https://groups.google.com/d/msgid/isar-users/57e5b6d845cb590553e247ef77e2a7aa95747dee.camel%40siemens.com.
prev parent reply other threads:[~2024-07-24 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 6:23 Uladzimir Bely
2024-07-24 7:00 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=57e5b6d845cb590553e247ef77e2a7aa95747dee.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.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