Control: tag -1 + moreinfo
On 1/19/26 09:08, zhangpan wrote:
Package: qemu-user-static
Version: 1:10.0.3+ds-3
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
What led up to the situation:
I attempted to install `pbuilder` and `qemu-user-static` for cross-build
environment, but encountered an unresolvable dependency loop between
qemu-related packages.
What exactly I did:
1. Ran `sudo apt update` to synchronize package lists.
2. Ran `sudo apt install pbuilder qemu-user-static` to install required build
tools.
What was the outcome of this action:
The installation failed with a dependency conflict error. Key issues:
1. My current installed version of `qemu-user-static` is 1:10.0.3+ds-3, which depends
on `qemu-user (>= 1:10.0.7+ds-0+deb13u1+b1)` and `qemu-user-binfmt (>=
1:10.0.7+ds-0+deb13u1+b1)`.
2. The Debian unstable repository provides a newer version of `qemu-user`
(1:10.2.0+ds-2), whose recommended dependency `qemu-user-binfmt
(1:10.2.0+ds-2)` breaks the existing `qemu-user-static`.
So do you have stable/trixie debian system, or unstable? I don't
understand. Why the version in unstable is relevant here?
3. This forms a closed dependency loop: upgrading to satisfy dependencies
breaks existing packages, while keeping existing packages fails to meet the
dependency requirements of `qemu-user-static`.
Note that qemu-user-static is provided by new qemu-user-binfmt in sid.
There's no loop. This works the same way as t64 transition worked
during upgrade to trixie.
Also, qemu-user-statc package in trixie (10.0.x) is a dummy package
which provides transition to qemu-user (which is now built statically)
and qemu-user-binfmt.
4. The error log shows "Unable to satisfy dependencies. Reached two conflicting
assignments" (detailed logs are attached).
What outcome I expected instead:
`qemu-user-static` should be installed successfully without dependency
conflicts, or the package's `Depends`/`Breaks` fields should be configured to
avoid such a loop.
It is installed successfully without conflicts when you use either
trixie or sid. When you have mixed environment, well, everything can
happen, depending on the particular mix you have.
I tested upgrade from trixie to the new version where qemu-user-static
does not exist as a separate package but provided by qemu-user-binfmt -
it appears to work fine. But maybe I missed something in the tests.
Additional Notes:
1. The bug exists in Debian forky/sid (unstable) branch.
But you filed the bug against the trixie version of qemu?
Now I'm even more confused.
2. No existing bug reports in the Debian BTS cover this specific dependency
loop.
3. Attached are the full system information, package version details, and error
logs for further verification.
Attached where? I don't see anything attached to this bug report?
Thanks,
/mjt
