Package: libchafa-dev Version: 1.18.1-1 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
libchafa-dev ships chafa.pc which contains: `Requires: glib-2.0` Because of this Requires field, any invocation of `pkgconf --libs chafa` will also look up glib-2.0.pc. On a system with only libchafa-dev installed (but not libglib2.0-dev), this fails: $ pkgconf --libs chafa Package glib-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `glib-2.0.pc' to the PKG_CONFIG_PATH environment variable Package 'glib-2.0', required by 'chafa', not found Installing libglib2.0-dev resolves the issue. Since libchafa-dev exposes a public API that includes <glib.h> (visible in /usr/include/chafa/chafa.h) and its .pc file unconditionally requires glib-2.0, I assume libglib2.0-dev should be a runtime dependency of libchafa-dev -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEuVOE/FJ0HcdfWSw//lAdKwFeZPsFAmn8e6IACgkQ/lAdKwFe ZPtAnA/+I8ik9chnuCAaCIJfH2Ztgrnhv4omZO35cSKKth0iL0O+ajWKxRvMBqLO Nco49yanFKbM8CJ2mkIHuVNpYmFsF1znq3HAxwkBG3wMdgez00G14dahiSMm2ZOk vdWGgHFoIFC4VssSW+tYg5SAh2LBUdD9L44bxQ9+jf50CyqKK8YBx7eLe/erq+Nq srlqcwRuR4f/6K3dX5oofHBGfJpCI8Kn6jHx1PWqpEw8cUQ5JP4qHLH+4jY7kViH f7Ori5v1dqqXRvsnd20upBb0TNj4Q8khNX5Ev5ZD2NHE0+yNkWdZgOKrIn+gTU7o NcCLCkG5GoVjddxE7CBhmr9O06WeCMCUiY1Spr5q7MoPdSlnXTBeov239yG7jcj3 vCVta200OQptMtoVLXXMIQugBKl4W1pV57xL/y+reKmVrX36vj7VVW3/WW38nD1E L9rG5hEQij7wecv81pBxzux9cp6sQEizhOcXLSPIJ11TXfYultnv9J78GcKpYBlS 18/DAUJbQxES7EN5HQ274Rox15GSf55ynm4KJFxMT3o43E8iAkGt3OjL3585eRuD zwxywC6nh6O+tvAF5/FuYqrGoaiyDVOC9xqCpBVReV/HdIGD5wqGvvErHZKb5KnC Qp7QeiR/BNdmmSxX6lbksVl2zez0auHdWetiAUOcXlNrB2RYgAE= =F3G1 -----END PGP SIGNATURE-----
