On Tue, 8 Feb 2022 at 16:25, Bryan Evenson <beven...@melinkcorp.com> wrote:
> 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.
>
This change will mask all failures that happen for any reason, not just the
one you saw, so I am not going to accept it. The correct fix is to figure
out what would be the correct order of updating and why opkg isn't able to
perform the mass-update in that order.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161524):
https://lists.openembedded.org/g/openembedded-core/message/161524
Mute This Topic: https://lists.openembedded.org/mt/88979156/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
