Skip to contentSkip to conversation

Failure when generating image with latest OE-Core

DISCUSSION Peter Kjellerstedt 3 participants 5 messages May 2, 2020 – May 3, 2020

lore
Share & tools
lore
#0 lore 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

#1 lore raw

I haven't seen this, and neither has the autobuilder. Could this be caused by something in 'internal package'?

Alex

Quoted 27 lines · Peter Kjellerstedt

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

#2 lore raw

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 <[email protected]>
Sent: den 2 maj 2020 18:36
To: Peter Kjellerstedt <[email protected]>
Cc: OE Core ([email protected]) <[email protected]>
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 <[email protected]<mailto:[email protected]>> 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: <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

#3 lore raw
In reply to Peter Kjellerstedt
Quoted 21 lines · Peter Kjellerstedt

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

Quoted 2 lines

I assume it is related to the recent rpm/dnf update. Any ideas on what's going on?

Was this a build from scratch with a clean TMPDIR or an existing build directory?

Cheers,

Richard

#4 lore raw
Quoted 33 lines

-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Richard Purdie
Sent: den 3 maj 2020 00:20
To: [email protected]; Alexander Kanavin <[email protected]>
Subject: Re: [OE-core] Failure when generating image with latest OE-Core

Quoted 21 lines · Peter Kjellerstedt

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

Quoted 2 lines

I assume it is related to the recent rpm/dnf update. Any ideas on what's going on?

Quoted 6 lines

Was this a build from scratch with a clean TMPDIR or an existing build directory?

Cheers,

Richard

Ok, I figured out the problem. In accordance with
https://sqlite.org/quirks.html#dblquote, we have added:

CFLAGS += "-DSQLITE_DQS=0"
BUILD_CFLAGS += "-DSQLITE_DQS=0"

in an sqlite3_%.bbappend. This causes an SQL statement that migrates the history database to version 1.2 to fail.

I will send a patch to avoid the problem.

//Peter