[OE-core] [PATCH 32/42] libdnf: upgrade 0.28.1 -> 0.33.0

[Alexander Kanavin]

On Tue, 21 May 2019 at 21:05, <richard.purdie at linuxfoundation.org> wrote:
> > On Tue, 21 May 2019 at 20:44, Richard Purdie
> > <richard.purdie at linuxfoundation.org> wrote:
> > > On Mon, 2019-05-20 at 16:11 +0200, Alexander Kanavin wrote:
> > > > Signed-off-by: Alexander Kanavin <alex.kanavin at gmail.com>
> > > > ---
> > > >  .../libdnf/{libdnf_0.28.1.bb =>
> > > > libdnf_0.33.0.bb}               | 2
> > > > +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >  rename meta/recipes-devtools/libdnf/{libdnf_0.28.1.bb =>
> > > > libdnf_0.33.0.bb} (95%)
> > >
> > > libdnf-native build failure:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/850
> > >
> > > Could be caused by the other fix? :/
> >
> > No, this looks different, and probably specific to the c++ compiler
> > on
> > Debian 9 host - what gcc version does it have?
>
> purdie at debian9-ty-2:~$ gcc --version
> gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516

Right, on my Ubuntu 18.04 gcc is 7.3, and apparently a bug that may be
triggering this has been fixed from 7.x onwards:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56480

I reported this upstream, meanwhile I guess we should defer the update
(the alternative - adding '-fpermissive' to c++ flags for libdnf is
really not a good way to 'fix' things :-/ )
https://github.com/rpm-software-management/libdnf/issues/733

Alex