From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "OE Core (openembedded-core@lists.openembedded.org)"
<openembedded-core@lists.openembedded.org>
Subject: Failure when generating image with latest OE-Core
Date: Sat, 2 May 2020 16:27:18 +0000 [thread overview]
Message-ID: <0a65790cfa0f43659d0cec942d729b1a@XBOX03.axis.com> (raw)
After upgrading to the latest master of OE-Core, I get the following
error when building an image:
DNF version: 4.2.21
cachedir: <image workdir>/rootfs/var/cache/dnf
Added oe-repo repo from <image workdir>/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: <image workdir>/rootfs/var/lib/dnf/history.sqlite. Error: SQLite error on ":memory:": Executing an SQL statement failed: no such column: 1.2
---> Package <internal package> <version> will be installed
History database cannot be created: <image workdir>/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
next reply other threads:[~2020-05-02 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 16:27 Peter Kjellerstedt [this message]
2020-05-02 16:36 ` Failure when generating image with latest OE-Core Alexander Kanavin
2020-05-02 18:40 ` Peter Kjellerstedt
2020-05-02 22:19 ` [OE-core] " Richard Purdie
2020-05-03 21:11 ` Peter Kjellerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a65790cfa0f43659d0cec942d729b1a@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox