<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 11.01.22 um 20:51 schrieb Klaus
Ziegler:<br>
</div>
<blockquote type="cite"
cite="mid:2750979b-d08e-01a5-0b00-042c9bd98e88@haus-gisela.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi Fritz,<br>
<br>
this publish error can be fixed in:<br>
.../oi-userland/tools/python/pkglint:<br>
<br>
@@ -333,8 +333,6 @@<br>
<br>
if bits == 32 and path64:<br>
result = _("32-bit object '%s' in 64-bit
path")<br>
- elif bits == 64 and not path64:<br>
- result = _("64-bit object '%s' in 32-bit
path")<br>
return result<br>
<br>
def file_action(self, action, manifest, engine,
pkglint_id="001"):<br>
<br>
@Andreas,<br>
perhaps we should make this the default, as we anyway move forward<br>
to migrate more and more apps/libs/tool to be only 64bit, what di
you think?<br>
</blockquote>
There are other things possible: Either add a "pkg.linted=true"
column if only a single action is affected or add a transform rule
in the manifest, eg.<br>
<transform path=usr/lib/python3.7/site-packages/.*\.so ->
default pkg.linted.userland.action001.2 true><br>
<br>
This way you can deliberately turn the error off.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:2750979b-d08e-01a5-0b00-042c9bd98e88@haus-gisela.de"> <br>
Many Regards<br>
Klaus<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/11/22 18:10, Friedrich Kink via
oi-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e32a2567-8ea6-847d-12dc-af436613037f@fkink.de">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<p>Hi all,</p>
<p>based on Andreas' comment I rebuild rrdtool exclusively 2for
64-bit. This added also support for all bindings lua, tcl,
perl, ruby (v2.6) and pyhton (v3.7). Though python created
some headache. It build needs an ugly tweak of the configure
script to find the right header files. The issue is cause by <font
face="Courier New">/usr/include/pyhton</font><font
face="Courier New, Courier, monospace">3.7</font><b>m. </b>Both
version <font face="Courier New, Courier, monospace">python3.7</font>
and <font face="Courier New, Courier, monospace">pyhton3.7m</font>
reports back PYTHON_VERSION 3.7. Based on this return the
PYTHON_INCLUDES is always created as <font face="Courier New,
Courier, monospace">/usr/include/pyhton3.7 </font>which
does not exist. Is this intentional (the real path is <font
face="Courier New, Courier, monospace">/usr/include/pyhton3.7m,</font>
just a warmup question ;-). But the real problem I have with
this python binding is this error when publishing:</p>
<p><font face="Courier New, Courier, monospace">
/usr/bin/python3.5 /usr/bin/pkglint \<br>
-f
/usr/share/src/myoi-userland/tools/pkglintrc
/usr/src/myoi-userland/components/image/rrdtool/build/manifest-i386-rrdtool.depend.res<br>
Lint engine setup...<br>
Starting lint run...<br>
ERROR userland.action001.2 64-bit object
'usr/lib/python3.7/site-packages/rrdtool.cpython-37m.so' in
32-bit path<br>
WARNING pkglint.action005.1 obsolete dependency check
skipped: unable to find dependency <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:pkg:/image/library/libpng16@1.6.37-2020.0.1.0"
moz-do-not-send="true">pkg:/image/library/libpng16@1.6.37-2020.0.1.0</a>
for <a class="moz-txt-link-abbreviated
moz-txt-link-freetext"
href="mailto:pkg:/image/rrdtool@1.7.2,5.11-2022.0.0.0"
moz-do-not-send="true">pkg:/image/rrdtool@1.7.2,5.11-2022.0.0.0</a></font></p>
<p>Is there a way to overcome this problem or should i just
remove the python3.7 binding (basically all pathon3.x
versions)? BTW phyton2.7 would work without problem including
publishing but I didn't want to create a dependency to this
soon to be deprecated/removed version.</p>
<p>kind regards,</p>
<p> Fritz</p>
<p>PS: What about failing tests? Are they just to be reported or
should I try to fix them?<br>
</p>
</blockquote>
</blockquote>
It would be good to fix failing tests. Alas it's not always possible
and sometimes it would take more time than reasonable.<br>
So you should decide whether it's worth the efforts to fix a test.
In my opinion it depends on the importance and severity of the
failure.<br>
In this case it's only marginally as we probably don't have many
rrdtool users with japanese locale settings.<br>
<br>
Regards,<br>
Andreas<br>
</body>
</html>