diff options
| author | Sam James <sam@gentoo.org> | 2025-05-12 00:50:27 +0100 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2025-05-12 00:55:51 +0100 |
| commit | ca7bdcb2d766e34e77adf3e2bc0923314bdca7bd (patch) | |
| tree | 8ec384015718732d02693058c6c48df08d00cb25 /dev-python/bpython/bpython-0.25.ebuild | |
| parent | a1e1e4b7366c54b65c51d907ded4b7689a679c86 (diff) | |
| download | gentoo-ca7bdcb2d766e34e77adf3e2bc0923314bdca7bd.tar.gz gentoo-ca7bdcb2d766e34e77adf3e2bc0923314bdca7bd.tar.bz2 gentoo-ca7bdcb2d766e34e77adf3e2bc0923314bdca7bd.zip | |
dev-libs/glib: workaround Portage bug with binpkgs
With binpkgs, we seem to sometimes get a new dev-libs/gobject-introspection-1.82
installed which needs >=dev-libs/glib-2.82, but without the new glib. We
then try to build glib, we see that we have a gobject-introspection installed
that is new enough via `has_version` (=> we don't try to bootstrap it), then
when trying to use it via `pkg-config`, it falls off because we don't have
the glib that it needs.
This is obviously a Portage bug in not ensuring that gobject-introspection's
dependencies are satisifed before merging its binpkg, but let's workaround
it here: check thoroughly if the available gobject-introspection is usable. If
it ain't, just bootstrap as if it weren't installed.
(Just closing the bug given we don't have a testcase, not much point
in keeping it open and potentially confusing people. It only happens
sometimes and requires some bad luck, unfortunately. If it were always
the case w/ binpkgs, it'd be far easier to debug.)
Closes: https://bugs.gentoo.org/951487
Thanks-to: Artemis Everfree <artemis@artemis.sh>
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/bpython/bpython-0.25.ebuild')
0 files changed, 0 insertions, 0 deletions
