[oi-dev] No module named 'pkg'

[Andreas Wacknitz]

Am 05.03.21 um 15:10 schrieb Klaus Ziegler:
>
> Hi Stephan,
>
> yes, indeed I haven't run gmake setup in the top-level oi-userland
> directory,
> what I have done now:
> klausz at sunfire % gmake setup
> setup components
> make[1]: Entering directory '/ws/klausz/oi-userland/components'
> /bin/mkdir -p /ws/klausz/oi-userland/sparc/logs
> /usr/bin/pkgrepo create file:/ws/klausz/oi-userland/sparc/repo
> /usr/bin/pkgrepo add-publisher -s
> file:/ws/klausz/oi-userland/sparc/repo userland
> /usr/bin/pkgrepo rebuild -s file:/ws/klausz/oi-userland/sparc/repo
> Initiating repository rebuild.
> building tools...
>
> After that I've built the latest gawk and tried:
> gmake sample-manifest <- okay
> gmake pre-publish <------------------------ STILL the SAME ERROR:
> ImportError: No module named 'pkg'
>
> My problem is that SPARC does not have a:
> /usr/lib/python3.5/vendor-packages directory:
> klausz at sunfire % cd /usr/lib/python2.7/vendor-packages/ < - is there :-)
> klausz at sunfire % cd /usr/lib/python3.5/vendor-packages
> -bash: cd: /usr/lib/python3.5/vendor-packages: No such file or directory
This simply means you are missing Python-3.5 version packages/modules.
We are far ahead with package updates
on i386 and are now working on adding 3.7 and 3.9 package versions.
Python-2.7 is out of support since beginning of this year
and many newer module versions don't support 2.7 anymore. So we have to
either remove Python-2.7 versions or keep the last supported
version for Python-2.7.

>
> that's where I think the "pkg module" lives - right?
> how do I build/get this directory - it's not worth symlinking the
> python2.7 directory since that is 32bit and the python3.5 installation
> is 64bit per default - what to do to migrate userland for SPARC
> from python2.7 to python3.5 ?
You can look at our package history. Alexander has been merging many
parts of OmniOS's IPS version with the help of the OmniOS people last year.
When your IPS already tries to use python-3.5 modules you are in a bad
situation and need to find a way to bootstrap the missing modules.

> All the SPARC packages (100) which I've already built are done via
> a home-gown script which do all the steps by hand rather than
> to use "gmake publish" - I allready had a valid repo, which is the
> the step done by "gmake setup".
This sounds like a way to bootstrap the missing packages. You should be
aware that you'll also need to update some of your make include files
in oi-userland/make-rules and probably also some template files in
oi-userland/templates and transforms in oi-userland/transforms.

Best regards,
Andreas
>
> Much Regards
> Klaus
>
> On 04.03.21 00:13, Stephan Althaus wrote:
>> On 03/03/21 08:48 PM, Till Wegmueller wrote:
>>> Hi
>>>
>>> IPS itself https://github.com/OpenIndiana/pkg5/ or the path in the
>>> components directory
>>>
>>> -Till
>>>
>>> On 03.03.21 16:38, Klaus Ziegler wrote:
>>>> Hi,
>>>>
>>>> I've been able to compile python3.5 on SPARC and wanted to decom
>>>> my workaround for building packages in oi-userland, unfortunately
>>>>
>>>> gmake pre-publish still tells me:
>>>>
>>>> Traceback (most recent call last):
>>>>    File "/ws/klausz/oi-userland/tools/userland-mangler", line 38,
>>>> in <module>
>>>>      import pkg.fmri
>>>> ImportError: No module named 'pkg'
>>>>
>>>> can anybody tell me where and what module I have to build to be
>>>> able to use
>>>> python3.5 to build packages, I hope it's not in the illumos-gate :-(
>>>>
>>>> Much Regards
>>>> Klaus
>>>>
>>>> _______________________________________________