<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=koi8-r">
</head>
<body>
<div>Likely by default it passed -Es to the python interpreter, so doesn't load modules from non-standart path.</div>
<div><br>
</div>
<div><br>
</div>
<div><style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0; margin-bottom:0"></p>
<div>С уважением, <br>
Александр Пыхалов,<br>
программист отдела телекоммуникационной инфраструктуры<br>
управления информационно-коммуникационной инфраструктуры ЮФУ<br>
</div>
<br>
<p></p>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>От:</b> Gary Mills <gary_mills@fastmail.fm><br>
<b>Отправлено:</b> 9 мая 2020 г. 1:31<br>
<b>Кому:</b> OpenIndiana Developer mailing list <oi-dev@openindiana.org><br>
<b>Копия:</b> Alexander Pyhalov <alp@sfedu.ru><br>
<b>Тема:</b> Re: [oi-dev] pkglint fails during publish</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Fri, May 08, 2020 at 07:49:21AM -0500, Gary Mills wrote:<br>
> On Fri, May 08, 2020 at 07:01:36AM +0000, Alexander Pyhalov wrote:<br>
> > Sorry, I meant<br>
> > <a href="https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7">
https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7</a><br>
> <br>
> I have some of those changes in the 2019 source clone, but not all of<br>
> them.<br>
<br>
I made another change shown in your PR: I replaced userland.py in<br>
tools/python/pkglint with the one in my 2020 source clone. With that,<br>
I got the same error during a publish, twice:<br>
<br>
pkglint: Error parsing config value for pkglint.ext.content: No module named 'pkglint'<br>
<br>
The file tools/pkglintrc contains:<br>
<br>
pkglint.ext.content = pkglint.userland<br>
<br>
suggesting that the pkglint command could not find the pkglint module.<br>
I'm wondering if PYTHONPATH is set correctly in the environment.<br>
<br>
In any case, I made the changes in make-rules, which consists only of<br>
altering the definition of PKGLINT by adding /usr/bin/python3.5 in<br>
front of /usr/bin/pkglint . With those changes, I got a successful<br>
publish. I did not expect that result.<br>
<br>
I don't understand why it worked. /usr/bin/pkglint is already a<br>
python3.5 script. Can you explain it? Can anybody explain it?<br>
<br>
<br>
-- <br>
-Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-<br>
</div>
</span></font></div>
</body>
</html>