debootstrap bullseye arm64 on trixie host fails

debootstrap bullseye arm64 on trixie host fails

[Uladzimir Bely]

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.

-- 
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 on the web visit https://groups.google.com/d/msgid/isar-users/abd60b8c3e933a0833597a03e442378e82fe10a7.camel%40ilbers.de.

Re: debootstrap bullseye arm64 on trixie host fails

['MOESSBAUER, Felix' via isar-users]

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.