commit f00dc7032076839ab79053bb85bbc81f4ef0e866
Author: lucascouts <lucascs@protonmail.com>
Date: Mon Oct 26 13:51:43 2026 -0300

up(app-emulation/qemu-11.1.2 -> 11.1.2-r1), add(dev-python/qemu-qmp-0.0.6-r1, metadata/md5-cache/{app-emulation/qemu-11.1.2-r1, dev-python/qemu-qmp-0.0.6-r1}), del(metadata/md5-cache/app-emulation/qemu-11.1.2), mod(.autoupdate/packages.toml): fix the qmp-shell collision

Until 2026-10-24 this overlay's qemu-11.1.2 was forked from 10.2.x and
installed /usr/bin/qmp-shell itself. 1855fb827 rebased it onto ::gentoo's
11.1.2, which moves qmp-shell to dev-python/qemu-qmp, but kept the same PVR:
installs of the old image were never rebuilt, and ::gentoo's qemu-qmp blocker
(!<app-emulation/qemu-11.1.2-r0[python]) does not match 11.1.2, so merging
qemu-qmp dies on a file collision (bentoo issue #53).

- qemu: revbump, content unchanged, so the rebase reaches every install.
- qemu-qmp-0.0.6-r1: ::gentoo's ebuild with the blocker raised to -r1, which
lets Portage hand qmp-shell over from the old image. Temporary mirror; its
packages.toml record states the exit condition.

Measured on stub ebuilds merged into a scratch ROOT: the issue's command
collides; revbump alone collides (qemu-qmp is merged first); PDEPEND collides;
revbump + raised blocker merges, qmp-shell ending owned by qemu-qmp. A real
build of qemu-qmp-0.0.6-r1 installs /usr/bin/qmp-shell. pkgcheck clean on
qemu-qmp; gentoo-parity.sh exits 0 on both. Not covered: a real qemu merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>