I have updated with including this update, but it seems it has breaken my mock. Found that when attempting fedora-review, which failed for two independent bugs.
$ mock --init
INFO: mock.py version 5.2 starting (python version = 3.12.0, NVR = mock-5.2-1.fc39), args: /usr/libexec/mock/mock --init
Start(bootstrap): init plugins
INFO: selinux enabled
Finish(bootstrap): init plugins
Start: init plugins
INFO: selinux enabled
Finish: init plugins
INFO: Signal handler active
Start: run
Start: clean chroot
Finish: clean chroot
Mock Version: 5.2
INFO: Mock Version: 5.2
Start(bootstrap): chroot init
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using 'dnf' instead of 'dnf5' for bootstrap chroot
INFO: Package manager dnf detected and used (fallback)
Finish(bootstrap): chroot init
Start: chroot init
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf5 detected and used (direct choice)
Start: installing minimal buildroot with dnf5
execv(/usr/bin/dnf5) failed: No such file or directory
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M 30c8fce73dd24656a01ef432681573f4 -D /var/lib/mock/fedora-rawhide-x86_64-bootstrap/root -a --capability=cap_ipc_lock --bind=/tmp/mock-resolv.8s2su6x1:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-rawhide-x86_64/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --resolv-conf=off /usr/bin/dnf5 --installroot /var/lib/mock/fedora-rawhide-x86_64/root/ --releasever 40 install @buildsys-build --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --setopt=tsflags=nocontexts
execv(/usr/bin/dnf5) failed: No such file or directory
$ rpm -q mock mock-core-configs dnf dnf5
mock-5.2-1.fc39.noarch
mock-core-configs-39.3-1.fc39.noarch
dnf-4.18.1-2.fc39.noarch
dnf5-5.1.8-1.fc39.x86_64
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Should everyone after upgrading the package be required to do that? It seems to be there should be autofixing mechanism in case it does not start on a fresh system.
This update has been submitted for testing by praiskup.
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 pushed to testing.
no regressions noted
I have updated with including this update, but it seems it has breaken my mock. Found that when attempting fedora-review, which failed for two independent bugs.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Just checked
mock-core-configs-39.2-1.fc39.noarchversion is working and entering mock works.@pemensik You need to $ mock -r fedora-40-x86_64 --scrub=all
Should everyone after upgrading the package be required to do that? It seems to be there should be autofixing mechanism in case it does not start on a fresh system.
But strange, today the same version works fine.
mock -r fedora-40-x86_64 --shellworks. Still think it is suspicious.This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by praiskup.
This update has been pushed to stable.