[oi-dev] How to handle an unresolved dependency?

[Andreas Wacknitz]

Am 24.11.21 um 15:55 schrieb Gary Mills:
> I'm working on the upgrade of an OI package called "fio".  Here's
> part of an error message I got:
>
>    $ gmake REQUIRED_PACKAGES
>    ...
>    .../components/sysutils/fio/build/manifest-i386-fio.depend has unresolved dependency '
>        depend type=require fmri=__TBD pkg.debug.depend.file=six/__init__.py \
>            pkg.debug.depend.reason=usr/bin/fio2gnuplot \
>            pkg.debug.depend.type=python \
>            pkg.debug.depend.path=usr/bin \
>            pkg.debug.depend.path=usr/lib/python3.9 \
>            pkg.debug.depend.path=usr/lib/python3.9/lib-dynload \
>            pkg.debug.depend.path=usr/lib/python3.9/site-packages \
>            pkg.debug.depend.path=usr/lib/python3.9/vendor-packages \
>            pkg.debug.depend.path=usr/lib/python39.zip'.
>
> Indeed, the file usr/lib/python3.9/vendor-packages/six/__init__.py
> does not exist.  That's because the entire python module is contained
> in the file usr/lib/python3.9/vendor-packages/six.py .  How do I fix
> the manifest so that this dependency is accepted?
>
>
In many cases it's just needed to update the dependencies by running
"gmake REQUIRED_PACKAGES".
This will update the Makefile and you can check the new entries against
the old ones.
If Python is involved you sometime also need to
- either add new packages (typically we don't want that)
- or add a bypass-generate entry in the manifest