All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Evenson <bevenson@melinkcorp.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] gio-querymodules: error while loading shared libraries: libffi.so.6: cannot open shared object file
Date: Tue, 8 Feb 2022 15:25:46 +0000	[thread overview]
Message-ID: <CH0PR20MB39480F83C8949247D7968800BB2D9@CH0PR20MB3948.namprd20.prod.outlook.com> (raw)
In-Reply-To: <CANNYZj9_bX2BLzXWM6f+OZL9dsjDrycc8TWrZkQMkW0MznYfgg@mail.gmail.com>

Alex,

> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: Monday, February 7, 2022 1:58 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>
> Cc: Patches and discussions about the oe-core layer <openembedded-
> core@lists.openembedded.org>
> Subject: Re: [OE-core] gio-querymodules: error while loading shared
> libraries: libffi.so.6: cannot open shared object file
> 
> Upgrading from one yocto release to a different yocto release with a package
> manager is not supported or tested. You need to replace the image
> completely.
> 

I traced back and I see the gio-querymodules call is inserted in the postrm by gio-module-class.bbclass.  Based on the commit notes, the postrm and postinst steps are an optimization and are not required to succeed.  Therefore I'd argue this should fail gracefully; just because we haven't yet seen this fail during minor upgrade attempts doesn't mean it can't.  I'd propose changing the line:

    ${libexecdir}/${MLPREFIX}gio-querymodules ${libdir}/gio/modules/

in gio-module-cache.bbclass to:

    ${libexecdir}/${MLPREFIX}gio-querymodules ${libdir}/gio/modules/ || true

I tested this change and it fixed my upgrade issue.  I still saw the error message but libglib-2.0 completed its upgrade successfully.  If you don't see any issues with this change, I'll send a patch out later today.

Thanks,
Bryan

> Alex
> 
> On Mon, 7 Feb 2022 at 19:49, Bryan Evenson <bevenson@melinkcorp.com>
> wrote:
> >
> > All,
> >
> > I'm having some upgrade issues related to upgrading libglib-2.0-0.  I have a
> device that is based on the morty release that I am upgrading to a build
> based on the dunfell release.  I am using opkg for a package manager.  During
> upgrade I see the error message in the subject.  I think I have an idea of what
> is happening and I'm looking for help on how to fix it.
> >
> > I seeh that libglib-2.0-0 depends on libffi.  Between the morty release and
> the dunfell release, libffi upgraded from libffi6 to libffi7.  When I upgrade my
> system, libffi upgrades from libffi6 to libffi7 prior to libglib-2.0-0 upgrading.
> When libglib-2.0-0 upgrades, it calls '/usr/libexec/gio-querymodules
> /usr/lib/gio/modules/' in its postrm script.  This postrm script fails and gives
> the error listed the subject line.  I'm assuming that this fails because gio-
> querymodules depends on libffi6 which is no longer installed.
> >
> > Has anyone run into a similar problem and found a way to fix it?  I've tried a
> few different ways to force a different upgrade order and so far nothing
> works.
> >
> > Thanks,
> > Bryan
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#161463):
> > https://lists.openembedded.org/g/openembedded-core/message/161463
> > Mute This Topic: https://lists.openembedded.org/mt/88979156/1686489
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-
> core/unsub
> > [alex.kanavin@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >

  reply	other threads:[~2022-02-08 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 18:49 gio-querymodules: error while loading shared libraries: libffi.so.6: cannot open shared object file Bryan Evenson
2022-02-07 18:58 ` [OE-core] " Alexander Kanavin
2022-02-08 15:25   ` Bryan Evenson [this message]
2022-02-08 16:58     ` Alexander Kanavin
2022-02-08 20:36       ` Bryan Evenson
2022-02-08 21:38         ` Alexander Kanavin
2022-02-11 13:45           ` Bryan Evenson
2022-02-11 15:06             ` Alexander Kanavin
2022-02-11 15:41               ` Bryan Evenson
2022-02-11 23:23                 ` Richard Purdie

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=CH0PR20MB39480F83C8949247D7968800BB2D9@CH0PR20MB3948.namprd20.prod.outlook.com \
    --to=bevenson@melinkcorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.