glib-2.84.1_2,2 conflicts with gobject-introspection-1.78.1_2,1

I am attempting to update ports on two FreeBSD 14.2-R boxes and am running into the following message:

Code:
pkg-static: glib-2.84.1_2,2 conflicts with gobject-introspection-1.78.1_2,1 (installs files into the same place).  Problematic file: /usr/local/lib/girepository-1.0/GLib-2.0.typelib
*** Error code 1

I see this error whether I use portmaster -a or make install. This has brought things pretty much to a screeching halt (update-wise) as everything seems to depend on GLib2.

Am I doing something wrong?
 
Read /usr/ports/UPDATING:
Code:
20250402:
  AFFECTS: users of devel/glib20 and devel/gobject-introspection building outside of Poudriere
  AUTHOR: arrowd@FreeBSD.org

  New versions of glib started to require gobject-introspection as a build
  dependency, while gobject-introspection requires glib to build. This forms a
  dependency cycle that is dealt with by introducing the @bootstrap flavor for
  mentioned ports. This solution is suggested by the upstream as well, see
  https://discourse.gnome.org/t/dealing-with-glib-and-gobject-introspection-circular-dependency/18701

  When building devel/glib20 in Poudriere no manual intervention is required.
  The devel/glib20@bootstrap gets built first and provides for
  devel/gobject-introspection@bootstrap. This in turn provides for a normal
  devel/glib20 build, which finally fulfills a dependency for normal devel/gobject-introspection

  Users that are building outside of the isolated environments will be ending
  up with useless glib-bootstrap and gobject-introspection-bootstrap packages
  installed after each update. These can be removed with

  pkg remove glib-bootstrap gobject-introspection-bootstrap
 
In addition to what SirDice said above me I also suggest paying more attention to the forum as well. It's only been a few weeks (iirc) since someone else asked the exact same question; their thread is still on the first index page:

I think you'll find this interesting because I also posted a full set of instructions there, explaining how you can resolve this.
 
Indeed. Thank you for pointing that out. I had looked at UPDATING, but had not yet figured out how to read it.
 
Back
Top