| View previous topic :: View next topic |
| Author |
Message |
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 930
|
 Posted: Fri Feb 14, 2025 9:44 am Post subject: edk2-bin and qemu |
 |
|
| Code: |
(sys-firmware/edk2-bin-202408:0/0::gentoo, ebuild scheduled for merge) USE="-secureboot" ABI_X86="(64)" conflicts with
~sys-firmware/edk2-bin-202202 required by (app-emulation/qemu-9.1.2:0/0::gentoo, installed) USE="aio alsa bzip2 curl fdt filecaps gnutls gtk jpeg ncurses nls oss pam pin-upstream-blobs png seccomp slirp spice udev usb usbredir vhost-net vnc xattr -accessibility -bpf -capstone -debug -doc -fuse -glusterfs -infiniband -io-uring -iscsi -jack -jemalloc -keyutils -lzo -multipath -nfs -numa -opengl -pipewire -plugins -pulseaudio -python -rbd -sasl -sdl -sdl-image (-selinux) -smartcard -snappy -ssh -static-user -systemtap -test -vde -virgl -virtfs -vte -xdp -xen -zstd" ABI_X86="(64)" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13" QEMU_SOFTMMU_TARGETS="x86_64 -aarch64 -alpha -arm -avr -cris -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="-aarch64 -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -or1k -ppc -ppc64 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -x86_64 -xtensa -xtensaeb"
^ ^^^^^^
|
This is totally unreadable. I don't have a 200" tv connected. _What_ is the conflict here? Is there a tool that can look at this in a more meaningful way? |
|
| Back to top |
|
 |
sdauth
l33t
Joined: 19 Sep 2018
Posts: 681
Location: Ásgarðr
|
| Posted: Fri Feb 14, 2025 10:48 am Post subject: |
|
|
Hello,
I have the same message if I oneshot edk2-bin-202408 :
emerge -1a --usepkg=n =sys-firmware/edk2-bin-202408
since installed qemu-9.1.2 requires (according to ebuild)
EDK2_OVMF_VERSION="202202"
aka sys-firmware/edk2-bin-202202
it shows the same message.
Maybe the EDK2 variable in qemu ebuild could be modified to use 202408.
That said, I'm not sure why you would get this message, unless manually trying to oneshot edk2-bin-202408.
If you emerge again =sys-firmware/edk2-bin-202202, it should solve the issue I think. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23113
|
| Posted: Fri Feb 14, 2025 3:04 pm Post subject: Re: edk2-bin and qemu |
|
|
| Princess Nell wrote: | | Code: | (sys-firmware/edk2-bin-202408:0/0::gentoo, ebuild scheduled for merge) USE="-secureboot" ABI_X86="(64)" conflicts with
~sys-firmware/edk2-bin-202202 required by (app-emulation/qemu-9.1.2:0/0::gentoo, installed) USE="aio alsa bzip2 curl fdt filecaps gnutls gtk jpeg ncurses nls oss pam pin-upstream-blobs png seccomp slirp spice udev usb usbredir vhost-net vnc xattr -accessibility -bpf -capstone -debug -doc -fuse -glusterfs -infiniband -io-uring -iscsi -jack -jemalloc -keyutils -lzo -multipath -nfs -numa -opengl -pipewire -plugins -pulseaudio -python -rbd -sasl -sdl -sdl-image (-selinux) -smartcard -snappy -ssh -static-user -systemtap -test -vde -virgl -virtfs -vte -xdp -xen -zstd" ABI_X86="(64)" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13" QEMU_SOFTMMU_TARGETS="x86_64 -aarch64 -alpha -arm -avr -cris -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="-aarch64 -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -or1k -ppc -ppc64 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -x86_64 -xtensa -xtensaeb"
^ ^^^^^^ |
This is totally unreadable. I don't have a 200" tv connected. _What_ is the conflict here? Is there a tool that can look at this in a more meaningful way? |
The carets are indented to be directly under the offending qualifier on an arbitrarily wide line, assuming you use a proper fixed width font. (Thus, it looks wrong in browsers.) The carets are under the ~ and the 202202, so those are the parts about which it warns. Hypothetically, if it had been complaining about USE=-python, the carets would have been indented by 432 spaces, so that they started under the -python no matter how wide your screen was. Also, I think the number of carets is always equal to the width of the word at which it points.
This looks like a fairly typical "Updates were skipped" warning, but you cut that off, so I cannot be certain. |
|
| Back to top |
|
|
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 930
|
| Posted: Fri Feb 14, 2025 5:22 pm Post subject: |
|
|
This is the complete message:
| Code: |
localhost ~ # emerge -upDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 11.63 s (backtrack: 0/20).
[ebuild U ] dev-libs/openssl-3.3.3 [3.3.2-r2]
[ebuild U ] net-misc/dhcpcd-10.1.0-r1 [10.1.0]
WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
sys-firmware/edk2-bin:0
(sys-firmware/edk2-bin-202408:0/0::gentoo, ebuild scheduled for merge) USE="-secureboot" ABI_X86="(64)" conflicts with
~sys-firmware/edk2-bin-202202 required by (app-emulation/qemu-9.1.2:0/0::gentoo, installed) USE="aio alsa bzip2 curl fdt filecaps gnutls gtk jpeg ncurses nls oss pam pin-upstream-blobs png seccomp slirp spice udev usb usbredir vhost-net vnc xattr -accessibility -bpf -capstone -debug -doc -fuse -glusterfs -infiniband -io-uring -iscsi -jack -jemalloc -keyutils -lzo -multipath -nfs -numa -opengl -pipewire -plugins -pulseaudio -python -rbd -sasl -sdl -sdl-image (-selinux) -smartcard -snappy -ssh -static-user -systemtap -test -vde -virgl -virtfs -vte -xdp -xen -zstd" ABI_X86="(64)" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13" QEMU_SOFTMMU_TARGETS="x86_64 -aarch64 -alpha -arm -avr -cris -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="-aarch64 -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -or1k -ppc -ppc64 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -x86_64 -xtensa -xtensaeb"
^ ^^^^^^
localhost ~ #
|
So yes, update was skipped. |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2019
|
| Posted: Fri Feb 14, 2025 6:02 pm Post subject: |
|
|
| Princess Nell wrote: | | Code: | | WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: |
|
No action required. I've said for years that this phrase is too harsh and should be changed (or hidden would be fine as well). My suggestion in a bug was:
| Code: | | INFO: One or more updates/rebuilds have been skipped due to a dependency requirement: |
|
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2728
|
| Posted: Fri Feb 14, 2025 6:07 pm Post subject: |
|
|
I've changed the code to quote tags below to be able to format text in a way to point out what's important:
| Quote: |
localhost ~ # emerge -upDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 11.63 s (backtrack: 0/20).
[ebuild U ] dev-libs/openssl-3.3.3 [3.3.2-r2]
[ebuild U ] net-misc/dhcpcd-10.1.0-r1 [10.1.0]
WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
sys-firmware/edk2-bin:0
(sys-firmware/edk2-bin-202408:0/0::gentoo, ebuild scheduled for merge) USE="-secureboot" ABI_X86="(64)" conflicts with
~sys-firmware/edk2-bin-202202 required by (app-emulation/qemu-9.1.2:0/0::gentoo, installed) USE="aio alsa bzip2 curl fdt filecaps gnutls gtk jpeg ncurses nls oss pam pin-upstream-blobs png seccomp slirp spice udev usb usbredir vhost-net vnc xattr -accessibility -bpf -capstone -debug -doc -fuse -glusterfs -infiniband -io-uring -iscsi -jack -jemalloc -keyutils -lzo -multipath -nfs -numa -opengl -pipewire -plugins -pulseaudio -python -rbd -sasl -sdl -sdl-image (-selinux) -smartcard -snappy -ssh -static-user -systemtap -test -vde -virgl -virtfs -vte -xdp -xen -zstd" ABI_X86="(64)" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13" QEMU_SOFTMMU_TARGETS="x86_64 -aarch64 -alpha -arm -avr -cris -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="-aarch64 -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -i386 -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -or1k -ppc -ppc64 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -x86_64 -xtensa -xtensaeb"
^ ^^^^^^
localhost ~ #
|
That's the important part. Qemu 9.1.2 requires edk2-bin-202202 but 202408 is available. That's just a warning that edk2-bin cannot be updated because of qemu.
However I don't have that warning. You have something weird going on on your system. For me this warning only appears if I try to explicitly update edk2-bin. Do you have it in your world file? What does `emerge --deselect edk2-bin` say?
Best Regards,
Georgi
Last edited by logrusx on Fri Feb 14, 2025 6:31 pm; edited 5 times in total |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2019
|
| Posted: Fri Feb 14, 2025 6:12 pm Post subject: |
|
|
| logrusx wrote: | | I don't know why ~sys-firmware/edk2-bin-202202 is marked with ~, for me it's stable, |
The ~ means all revisions when used as an atom version operator (at the beginning of an atom). This has nothing to do with stable/unstable. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2728
|
| Posted: Fri Feb 14, 2025 6:12 pm Post subject: |
|
|
| grknight wrote: | | logrusx wrote: | | I don't know why ~sys-firmware/edk2-bin-202202 is marked with ~, for me it's stable, |
The ~ means all revisions when used as an atom version operator (at the beginning of an atom). This has nothing to do with stable/unstable. |
I already edited my post but thanks for the explanation!
Best Regards,
Georgi |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2728
|
| Posted: Fri Feb 14, 2025 6:31 pm Post subject: |
|
|
I have edited my post above several times, whoever read it might want to check if they read the last version.
Best Regards,
Georgi |
|
| Back to top |
|
|
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 930
|
| Posted: Fri Feb 14, 2025 11:56 pm Post subject: |
|
|
Yes, it's in the world file.
| Code: |
localhost ~ # emerge --deselect edk2-bin
>>> Removing sys-firmware/edk2-bin from "world" favorites file...
localhost ~ #
|
A world update (--pretend) now lists only the two updated ebuilds, and a re-emerge of qemu doesn't try to pull in an edk2-bin update either. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2728
|
|
| Back to top |
|
|
|
Portage & Programming
