These rebuilds are broken, as they were still performed using nodejs-packaging -12 release, not -13 release, so the results still point to the versioned node_modules directory.
eg
https://kojipkgs.fedoraproject.org/packages/linux-sgx/2.26/6.fc43/data/logs/x86_64/root.log https://kojipkgs.fedoraproject.org/packages/statsd/0.8.6/14.fc43/data/logs/noarch/root.log https://kojipkgs.fedoraproject.org/packages/marked/2.0.0/12.fc43/data/logs/noarch/root.log
are all showing wrong nodejs-packaging, and the 'sgx-pccs' daemon still fails to start due to broken paths.
Updated build that fixes the upgrade issue using a %pretrans script. NB, downgrade will still have trouble as going from a dir -> file is not supported by RPM either, but AFAIK downgrades are not required to work.
This update has been unpushed.
This update has been unpushed.
I'd suggest waiving the failed QEMU CI test. I've found no useful info in the jenkins job log beyond "Test environment installation failed: Install packages". Since the packages install fine in a rawhide container I suspect the CI job is attempting to install the new QEMU packages, without the matching libnfs, which of course won't work due to the soname change.
Works as expected
This update unfortunately left my laptop in an unbootable state. I had version 2.06~rc1.4.fc34 installed previously, and after upgrading to this and rebooting, any attempt to boot an OS from the grub menu resulted in:
error: symbol 'grub_calloc' not found
For benefit of anyone else hitting this, I had to boot into Fedora rescue media from a USB stick, chroot into my real install, and run 'grub2-install /dev/sda' to fix it.
This version crashes immediately on startup https://bugzilla.redhat.com/show_bug.cgi?id=1779335
This fixes the flaws in https://bugzilla.redhat.com/show_bug.cgi?id=1776359
Those warnings are absolutely nothing todo with entangle. They are bugs in countless other applications gsettings schemas.
Darktable stops crashing with this update installed.
This release breaks compatibility with a libvirt feature
This update exposes a bug in libcap-ng which completely breaks ability to start libvirt KVM / LXC guests. As such it must not be pushed to stable until a resolution is found. See
https://bugzilla.redhat.com/show_bug.cgi?id=1352064 https://bugzilla.redhat.com/show_bug.cgi?id=1352066