Re: print/foliate missing dependencies?

[Greg Troxel <gdt%lexort.com@localhost>]

Rhialto <rhialto%falu.nl@localhost> writes:

> I installed the package I built for misc/foliate (and it works where I
> built it) on another machine, and there I get this error when I try to
> start it:
>
> radl:~$ foliate
>
> (gjs:7971): Gjs-CRITICAL **: 14:59:56.058: JS ERROR: Error: Requiring GLib, version 2.0: Typelib file for namespace 'GLib', version '2.0' not found
> @resource:///org/gnome/gjs/modules/script/package.js:13:14
> @/usr/pkg/bin/foliate:2:1
>
> (gjs:7971): Gjs-CRITICAL **: 14:59:56.058: Script /usr/pkg/bin/foliate threw an exception
>
> so it seems there is some dependency that isn't declared.
> How do I even find what it wants? I don't even see files in my file
> system with those names.

First step is to compare what upstream documents as dependencies vs what
is in the pkgsrc package.  Any discrepancies are pkgsrc bugs to fix.  If
upstream is unclear or omits things, that's an upstream bug which should
be filed in their tracker.  Of course, many upstreams are buggy.

Another useful thing is to try to build it in a bulk environment.  But
it may have a runtime dependency that is not expressed.

You could run ktrace, and then kdump -m0 | egrep NAMI.

You could diff the set of packages installed on the build machine
against the other, reduce diffs to zero, bisect.

You could do a build saving all the output on the machine that works,
and look at things that are build dependencies, and add those on the
non-working machine.

You could "pkgin sk", and "pkgin -n ar", on the build machine, ensure
that that's right, and remove all the non-keepable (apparently that's
the French term for automatic=yes :-) packages and see if it still
works.  After making one more backup than you think you need of course.