There is nothing special about that package, apart from that it is normally the first one listed to be installed after the “--> Starting dependency resolution” message. I tried to see if I could see anything using `strace -f dnf …`, but all I can see related to history.sqlite are two failed calls to lstat(). It never tries to open it before it fails… //Peter From: Alexander Kanavin Sent: den 2 maj 2020 18:36 To: Peter Kjellerstedt Cc: OE Core (openembedded-core@lists.openembedded.org) Subject: Re: Failure when generating image with latest OE-Core I haven't seen this, and neither has the autobuilder. Could this be caused by something in 'internal package'? Alex On Sat, 2 May 2020 at 18:27, Peter Kjellerstedt > wrote: After upgrading to the latest master of OE-Core, I get the following error when building an image: DNF version: 4.2.21 cachedir: /rootfs/var/cache/dnf Added oe-repo repo from /oe-rootfs-repo User-Agent: falling back to 'libdnf': could not detect OS or basearch repo: using cache for: oe-repo oe-repo: using metadata from Sat 02 May 2020 04:04:01 PM UTC. Excludes in dnf.conf: rng-tools, shared-mime-info, udev-hwdb --> Starting dependency resolution History database cannot be created: /rootfs/var/lib/dnf/history.sqlite. Error: SQLite error on ":memory:": Executing an SQL statement failed: no such column: 1.2 ---> Package will be installed History database cannot be created: /rootfs/var/lib/dnf/history.sqlite. Error: SQLite error on ":memory:": Executing an SQL statement failed: no such column: 1.2 Error: SQLite error on ":memory:": Executing an SQL statement failed: no such column: 1.2 I assume it is related to the recent rpm/dnf update. Any ideas on what's going on? //Peter