Failure when generating image with latest OE-Core

Failure when generating image with latest OE-Core

[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

Re: Failure when generating image with latest OE-Core

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

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 <peter.kjellerstedt@axis.com>
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
>
>

[-- Attachment #2: Type: text/html, Size: 1812 bytes --]

Re: Failure when generating image with latest OE-Core

[Peter Kjellerstedt]

[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]

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 <alex.kanavin@gmail.com>
Sent: den 2 maj 2020 18:36
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: OE Core (openembedded-core@lists.openembedded.org) <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 <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>> 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

[-- Attachment #2: Type: text/html, Size: 5550 bytes --]

Re: [OE-core] Failure when generating image with latest OE-Core

[Richard Purdie]

On Sat, 2020-05-02 at 16:27 +0000, 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: <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?

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

Cheers,

Richard

Re: [OE-core] Failure when generating image with latest OE-Core

[Peter Kjellerstedt]

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 3 maj 2020 00:20
> To: openembedded-core@lists.openembedded.org; Alexander Kanavin
> <alex.kanavin@gmail.com>
> Subject: Re: [OE-core] Failure when generating image with latest OE-Core
> 
> On Sat, 2020-05-02 at 16:27 +0000, 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: <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?
> 
> 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