Comments

64 Comments
karma

Tested building dnsperf with this build and seems working fine.

BZ#2333304 Please branch and build ck for EPEL 10
karma

Fixes parsing of IPv6 routes

distribution-gpg-keys-1.105-1.fc39.noarch and mock-core-configs-41.2-1.fc39.noarch work well together. That allows rawhide mockbuilds to work again.

Updates RPM-GPG-KEY-fedora-rawhide-primary to RPM-GPG-KEY-fedora-42-primary

But strange, today the same version works fine. mock -r fedora-40-x86_64 --shell works. Still think it is suspicious.

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.

Just checked mock-core-configs-39.2-1.fc39.noarch version is working and entering mock works.

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

No, that is a mistake, created it. There is a new build also for f37 as well.

Side tag seems no longer existing, but the build were not successful. A new update would be created.

recheck

@carlwgeorge Have you tried it with enabled (rhel-)CRB repository? dnf builddep bind-dyndb-ldap.spec installed bind-devel-9.16.23-7.el9.x86_64 to me. As did just dnf install bind-devel. Can you provide detailed steps and list of enabled repositories you have tried? It should not replace bind-devel in current build.

Mixing bind9-next instead of normal bind package is an error, hopefully fixed in release 3. It should be alternative version used only when user has chosen to switch to it. It were not intended to replace bind package from CentOS/RHEL and it has to be fixed to not do that. Please check last version does not push itself into your system.

Bug #2122841 affects also this build and may prevent working FreeIPA deployment. It is working fine separately, but will not work with -E pkcs11 parameter correctly.

BZ#2119132 bind-9.18.6 is available

Ah, I made error during merging. Thus changelog mentions unbound-1.16.0-1, but build is unbound-1.16.0-3

@ozeszty Consider filling a bug on jwhois component to request that. But it seems Fedora maintainer keeps it working even after upstream has stopped adding commits.

I have unbound build failing now on f36. I have verified in mockbuild it passes unittest without a crash with this update.

It installs fine on f35. However, why is not even readme contained in the package? It just has a binary and license file. It is enough?