When using to dnf to build a root filesystem from scratch, the following error occurs: ERROR: core-image-sato-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/oe-rootfs-repo --installroot=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs --setopt=logdir=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/temp makecache' returned 1: error: cannot open Packages database in /var/lib/rpm Error: Error: rpmdb open failed This used to work, and the offending commit has been identified by bisection to be https://github.com/rpm-software-management/dnf/commit/3ddf684b7c67a2b384aa99dde53d8a43218f2e68 If I added a --releasever=oe-core explicitly to the command line, a different issue happens: ERROR: core-image-sato-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/oe-rootfs-repo --installroot=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs --setopt=logdir=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/temp --releasever=oe-core makecache' returned 1: Added oe-repo repo from /home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/oe-rootfs-repo failed calculating RPMDB checksum
I can confirm that if the above commit is reverted, the issue disappears. I'll adopt that as a temporary fix.
Please can you little bit narrow the problem. Please can you try to remove as much as possible options from command and find minimal reproducer? Thanks a lot
In Yocto context we need all of these switches to avoid contamination of dnf configuration from the host (if the host distro happens to use dnf/rpm). I guess you can have a minimal reproducer by: a) having a system that is not using dnf/rpm, i.e. debian, so /var/lib/rpm is absent (maybe temporarily renaming that dir will work too). b) running 'dnf --installroot=<dir> makecache' where <dir> exists, but is empty. I'll try to verify if that works on my machine a bit later.
(In reply to Alex Kanavin from comment #3) > I guess you can have a minimal reproducer by: > a) having a system that is not using dnf/rpm, i.e. debian, so /var/lib/rpm > is absent (maybe temporarily renaming that dir will work too). > b) running 'dnf --installroot=<dir> makecache' where <dir> exists, but is > empty. > > I'll try to verify if that works on my machine a bit later. I can now confirm this. You can even drop 'makecache': # dnf --installroot=/home/ak/development/poky/build-64/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs error: cannot open Packages database in /var/lib/rpm Error: Error: rpmdb open failed
Please what is in directory /var/lib/rpm and is the directory existing?
The directory doesn't exist.
Even if it did exist, it should not be accessed when --installroot is in use, as Yocto is cross-compiling for an entirely different system (that includes building own versions of rpm and dnf), and so we don't want any information from the host to contaminate the build.
Ok, first problem appears when you don't have a permissions for directory where you search for rpmdb. The second issue in Comment 1 I still cannot reproduce
Both problems should be solved by my pull-request https://github.com/rpm-software-management/dnf/pull/793. Thanks for your report.
I can confirm that the above commits fix the issue. Thanks!
dnf-plugins-core-2.0.0-1.fc26 libdnf-0.8.2-1.fc26 dnf-2.4.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e95959f0d
dnf-2.4.0-1.fc26 dnf-plugins-core-2.0.0-1.fc26 dnf-plugins-extras-2.0.0-1.fc26 libdnf-0.8.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e95959f0d
dnf-2.4.0-1.fc26, dnf-plugins-core-2.0.0-1.fc26, dnf-plugins-extras-2.0.0-1.fc26, libdnf-0.8.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e95959f0d
dnf-2.4.0-1.fc26, dnf-plugins-core-2.0.0-1.fc26, dnf-plugins-extras-2.0.0-1.fc26, libdnf-0.8.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.