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

["Peter Kjellerstedt" <peter.kjellerstedt@axis.com>]

> -----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