[root@rawhide s]# /usr/sbin/qemu-system-x86_64 -device help
/usr/sbin/qemu-system-x86_64: symbol lookup error: /usr/sbin/qemu-system-x86_64: undefined symbol: fdt_setprop, version LIBFDT_1.2
Downgrading libfdt from 1.8.0-1.fc45 to 1.7.2-9.fc44 fixes it again.
I see the F44 update has been pulled, can the F45/Rawhide be pulled too, please? Thanks
@adamwill for the qemu issue, as far as I can tell a rebuild of qemu would also solve the problem. Could that be arranged for Rawhide instead? It's a bit broken right now...
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by bodhi
It seems like python3-libfdt no longer provides
python3.14dist(libfdt), which it's supposed to do.This update also broke qemu:
[root@rawhide s]# /usr/sbin/qemu-system-x86_64 -device help /usr/sbin/qemu-system-x86_64: symbol lookup error: /usr/sbin/qemu-system-x86_64: undefined symbol: fdt_setprop, version LIBFDT_1.2
Downgrading libfdt from 1.8.0-1.fc45 to 1.7.2-9.fc44 fixes it again.
I see the F44 update has been pulled, can the F45/Rawhide be pulled too, please? Thanks
@bluca we'd need a releng ticket for that, as it's already stable - this would be an untag request.
@adamwill for the qemu issue, as far as I can tell a rebuild of qemu would also solve the problem. Could that be arranged for Rawhide instead? It's a bit broken right now...
d'oh, I just filed the untag ticket. Still...the same thing might affect other deps too, right? Maybe an untag is safest...
Yeah anything that uses that symbol (which became a static inline in 1.8.0 which is an ABI break) will fail to load, and requires a rebuild.
There's also a new 1.8.1 version that reverts the change and fixes the issue: https://github.com/dgibson/dtc/commit/040c1f7e29e25785d2d84044b1a766aa819d527a