Likely by default it passed -Es to the python interpreter, so doesn't load modules from non-standart path.
С уважением, Александр Пыхалов, программист отдела телекоммуникационной инфраструктуры управления информационно-коммуникационной инфраструктуры ЮФУ ________________________________ От: Gary Mills <gary_mi...@fastmail.fm> Отправлено: 9 мая 2020 г. 1:31 Кому: OpenIndiana Developer mailing list <oi-dev@openindiana.org> Копия: Alexander Pyhalov <a...@sfedu.ru> Тема: Re: [oi-dev] pkglint fails during publish On Fri, May 08, 2020 at 07:49:21AM -0500, Gary Mills wrote: > On Fri, May 08, 2020 at 07:01:36AM +0000, Alexander Pyhalov wrote: > > Sorry, I meant > > https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7 > > I have some of those changes in the 2019 source clone, but not all of > them. I made another change shown in your PR: I replaced userland.py in tools/python/pkglint with the one in my 2020 source clone. With that, I got the same error during a publish, twice: pkglint: Error parsing config value for pkglint.ext.content: No module named 'pkglint' The file tools/pkglintrc contains: pkglint.ext.content = pkglint.userland suggesting that the pkglint command could not find the pkglint module. I'm wondering if PYTHONPATH is set correctly in the environment. In any case, I made the changes in make-rules, which consists only of altering the definition of PKGLINT by adding /usr/bin/python3.5 in front of /usr/bin/pkglint . With those changes, I got a successful publish. I did not expect that result. I don't understand why it worked. /usr/bin/pkglint is already a python3.5 script. Can you explain it? Can anybody explain it? -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-
_______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev