Re: [oi-dev] $WS_TOOLS/python-integrate-project
Thank you both. Marcel, I will let you know if I am successful with texttable or not. -- Původní e-mail -- Od: Marcel Telka Komu: OpenIndiana Developer mailing list Datum: 28. 11. 2022 17:44:57 Předmět: Re: [oi-dev] $WS_TOOLS/python-integrate-project "On Mon, Nov 28, 2022 at 05:16:47PM +0100, Nona Hansel wrote: > However, updating texttable, I ran > > > $WS_TOOLS/python-integrate-project texttable > > in oi-userland/components/python/texttable directory or in oi-userland/ and > got this mesage: > > -bash: /python-integrate-project: No such file or directory You need this first: WS_TOOLS=$(git rev-parse --show-toplevel)/tools or alternatively (the above one is more reliable) WS_TOOLS=$(gmake print-value-WS_TOOLS) Anyway, I assume the texttable update will fail now using the python-integrate-project tool, because the tool is very strict. It requires really _all_ declared dependencies by a project, and it also requires all tests to pass. This was usually not the case earlier where testing was usually simply skipped. I'm currently in a middle (or at beginnig? :-)) of converting all Python projects to python-integrate-project and to include all dependencies for them, also for testing. I now have ca 80 Python projects in the queue waiting for something (usually for other projects to get integrated first). I started with handfull already integrated Python projects to convert them to python-integrate-project (and possibly update them), but because of dependencies I'm now at vastly higher number :-). The texttable is not in my queue yet, so you can try to convert it to use python-integrate-project (and let me know the result). > How do I use this command? And is it usable for every python component? You can try to read draft of documentation for perl-integrate-module at: https://github.com/mtelka/oi-userland/blob/pim-doc/doc/perl-modules.md The perl-integrate-module is similar tool as python-integrate-project but targetting Perl. The usage of both tools should be as similar as possible (modulo differences caused by Perl and Python itself; for example Python have no problem with versions, while Perl does). HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | | homepage: http://telka.sk/ | +---+ ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] $WS_TOOLS/python-integrate-project
Hello, I've seen in several Makefiles saying they have been automatically generated using this command $WS_TOOLS/python-integrate-project name_of_the_component However, updating texttable, I ran $WS_TOOLS/python-integrate-project texttable in oi-userland/components/python/texttable directory or in oi-userland/ and got this mesage: -bash: /python-integrate-project: No such file or directory How do I use this command? And is it usable for every python component? Thank you. Best regards, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Running gmake check in multiple directories
Hello, I'm trying to update texinfo and I have troubles running gmake test. Texinfo has tests in multiple locations, in the build/ they can be found in: amd64/info/t/ amd64/install-info/tests/ amd64/tp/tests/test-scripts/ amd64/tp/tests/many_input_files/ amd64/Pod-Simple-Texinfo/ amd64/texindex/tests/ amd64/util/tests/ When I run gmake check in every folder with tests, they run normally. Yet, using just gmake test in texinfo/ directory, only tests in amd64/info/t/ run, others (from next directories) just don't run at all. Using gmake test in the current version 6.8 all tests run correctly (plus the structure of the source code is basically the same). It seems that only in the updated version there is a problem with running all of them automatically. I didn't play with test related variables in Makefile (current state of work can be seen here: https://github.com/balrog-nona/oi-userland/commit/e15da6f6 ae1de62578bfe09634bfa57a05df1d4d) Can anybody give me the hint about where the problem might be? Thank you. Best regards, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Error message after gmake test
Thank you, Andreas, I will do that. -- Původní e-mail -- Od: Andreas Wacknitz Komu: oi-dev@openindiana.org Datum: 7. 11. 2022 15:44:08 Předmět: Re: [oi-dev] Error message after gmake test " Am 07.11.22 um 15:33 schrieb Nona Hansel: > Hello, > > it's been a while since I last contributed to OI (not counting > yesterday's straight forward sudo update). Today I'm trying to update > sed. When I run gmake test, I get this message: > > make[1]: Leaving directory > '/export/home/nona/oi-userland/components/text/sed/build/amd64' > /usr/bin/touch > /export/home/nona/oi-userland/components/text/sed/build/amd64/.built > /bin/rm -f -rf > /export/home/nona/oi-userland/components/text/sed/build/test/amd64 > /bin/mkdir -p > /export/home/nona/oi-userland/components/text/sed/build/test/amd64 > (cd /export/home/nona/oi-userland/components/text/sed/build/amd64 ; \ > /usr/bin/env \ > /usr/gnu/bin/make \ > check) \ > &> > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -results > print "#!/bin/sh" > > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ transform-64-results; > print '/bin/cat > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -results > | \\' >> > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ transform-64-results; > print '/usr/gnu/bin/sed ' '-e > "s|/export/home/nona/oi-userland/components/text/sed/build/amd64|\\$(@D)| g" > ' '-e "s|/usr/perl5/5.36/bin/perl|\\$(PERL)|g" ' '-e > "s|/export/home/nona/oi-userland/components/text/sed/sed-4.9|\\$(SOURCE_ DIR)|g" > ' "-e 's|/usr/lib/python3.9|\$(PYTHON_DIR)|g'" '-n ' '-e "/TOTAL/p" ' > '-e "/SKIP/p" ' '-e "/PASS/p" ' '-e "/FAIL/p" ' '-e "/ERROR/p" ' ' \\' > >> > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ transform-64-results; > print '> > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/results -64.snapshot' > >> > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ transform-64-results; > > /bin/bash > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ transform-64-results; > > [ -e > /export/home/nona/oi-userland/components/text/sed/test/results-all.master > ] || exit 1; /usr/gnu/bin/diff -uNb > /export/home/nona/oi-userland/components/text/sed/test/results-all.master > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/results -64.snapshot > > > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -diffs; > print "Test results in > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -results"; > if [ -s > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -diffs > ]; then print "Differences found."; /bin/cat > /export/home/nona/oi-userland/components/text/sed/build/test/amd64/test-64 -diffs; > exit 2; else print "No differences found."; fi > gmake: *** [/export/home/nona/oi-userland/make-rules/configure.mk:210: > /export/home/nona/oi-userland/components/text/sed/build/amd64/.tested-and- compared] > Error 1 > > It confuses me. From the files build/test/amd64/results-64.snapshot > and build/test/amd64/test-64-results I can see that the tests ran fine > and mostly passed with a few skipped. > > I copied the contents of build/test/amd64/results-64.snapshot into > test/results-64.master because I thought that the build system would > compare those files, yet I get the above message. We have a new default to results-all.master. You'll have to either rename your results-64.master file to results-all.master or set USE_COMMON_TEST_MASTER= no in the Makefile. Regards, Andreas ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Error message after gmake test
Hello, it's been a while since I last contributed to OI (not counting yesterday's straight forward sudo update). Today I'm trying to update sed. When I run gmake test, I get this message: make[1]: Leaving directory '/export/home/nona/oi-userland/components/text/ sed/build/amd64' /usr/bin/touch /export/home/nona/oi-userland/components/text/sed/build/amd 64/.built /bin/rm -f -rf /export/home/nona/oi-userland/components/text/sed/build/test/ amd64 /bin/mkdir -p /export/home/nona/oi-userland/components/text/sed/build/test/ amd64 (cd /export/home/nona/oi-userland/components/text/sed/build/amd64 ; \ /usr/bin/env \ /usr/gnu/bin/make \ check) \ &> /export/home/nona/oi-userland/components/text/sed/build/test/amd64/ test-64-results print "#!/bin/sh" > /export/home/nona/oi-userland/components/text/sed/build/ test/amd64/transform-64-results; print '/bin/cat /export/home/nona/oi- userland/components/text/sed/build/test/amd64/test-64-results | \\' >> / export/home/nona/oi-userland/components/text/sed/build/test/amd64/transform- 64-results; print '/usr/gnu/bin/sed ' '-e "s|/export/home/nona/oi-userland/ components/text/sed/build/amd64|\\$(@D)|g" ' '-e "s|/usr/perl5/5.36/bin/perl |\\$(PERL)|g" ' '-e "s|/export/home/nona/oi-userland/components/text/sed/sed -4.9|\\$(SOURCE_DIR)|g" ' "-e 's|/usr/lib/python3.9|\$(PYTHON_DIR)|g'" '-n ' '-e "/TOTAL/p" ' '-e "/SKIP/p" ' '-e "/PASS/p" ' '-e "/FAIL/p" ' '-e "/ ERROR/p" ' ' \\' >> /export/home/nona/oi-userland/components/text/sed/build/ test/amd64/transform-64-results; print '> /export/home/nona/oi-userland/ components/text/sed/build/test/amd64/results-64.snapshot' >> /export/home/ nona/oi-userland/components/text/sed/build/test/amd64/transform-64-results; /bin/bash /export/home/nona/oi-userland/components/text/sed/build/test/amd 64/transform-64-results; [ -e /export/home/nona/oi-userland/components/text/sed/test/results-all. master ] || exit 1; /usr/gnu/bin/diff -uNb /export/home/nona/oi-userland/ components/text/sed/test/results-all.master /export/home/nona/oi-userland/ components/text/sed/build/test/amd64/results-64.snapshot > /export/home/ nona/oi-userland/components/text/sed/build/test/amd64/test-64-diffs; print "Test results in /export/home/nona/oi-userland/components/text/sed/build/ test/amd64/test-64-results"; if [ -s /export/home/nona/oi-userland/ components/text/sed/build/test/amd64/test-64-diffs ]; then print "Differences found."; /bin/cat /export/home/nona/oi-userland/components/ text/sed/build/test/amd64/test-64-diffs; exit 2; else print "No differences found."; fi gmake: *** [/export/home/nona/oi-userland/make-rules/configure.mk:210: / export/home/nona/oi-userland/components/text/sed/build/amd64/.tested-and- compared] Error 1 It confuses me. From the files build/test/amd64/results-64.snapshot and build/test/amd64/test-64-results I can see that the tests ran fine and mostly passed with a few skipped. I copied the contents of build/test/amd64/results-64.snapshot into test/ results-64.master because I thought that the build system would compare those files, yet I get the above message. Could you please give me advice of how to run tests correctly? Best regards, Nona___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] samba package needs a maintainer
I can confirm - I get the same error on my build machine as Andreas. -- Původní e-mail -- Od: Andreas Wacknitz Komu: oi-dev@openindiana.org Datum: 15. 3. 2022 16:35:22 Předmět: Re: [oi-dev] samba package needs a maintainer "Am 15.03.22 um 14:51 schrieb Stephan Althaus: > On 3/15/22 14:23, Andreas Wacknitz wrote: >> Hi all, >> >> our samba package doesn't build at the moment. It fails in the 64-bit >> part probably because of a missing flag. >> Alas this prevents for fixing man page collisions that have been >> introduced by an update of illumogs-gate (IPD4). >> >> I have stopped our nightly illumos-gate builds at rhe moment because of >> this but we need to find a solution for it soon. >> When the jenkins job will be ra-activated before we have a solution >> either everybody needs to uninstall samba or we need to obsolete the >> samba package. >> >> Short: We need to find a maintainer for the samba package otherwise it's >> doomed for OI. >> >> Regards, >> Andreas >> >> >> ___ >> oi-dev mailing list >> oi-dev@openindiana.org >> https://openindiana.org/mailman/listinfo/oi-dev > > Hello! > > I gave it a try. It seems some symbols are "lost" ;-) > > > [2687/3948] Linking bin/default/librpc/tools/ndrdump > Undefined first referenced > symbol in file > __gmpn_sec_powm_itch /usr/lib/amd64/libhogweed.so.5 > __gmpn_sec_invert /usr/lib/amd64/libhogweed.so.5 > __gmpz_limbs_write /usr/lib/amd64/libgnutls.so > __gmpn_sec_div_r_itch /usr/lib/amd64/libhogweed.so.5 > __gmpz_limbs_finish /usr/lib/amd64/libgnutls.so > __gmpn_sec_invert_itch /usr/lib/amd64/libhogweed.so.5 > __gmpz_limbs_modify /usr/lib/amd64/libgnutls.so > __gmpn_sec_powm /usr/lib/amd64/libhogweed.so.5 > __gmpn_sec_add_1_itch /usr/lib/amd64/libhogweed.so.5 > __gmpn_sec_mul_itch /usr/lib/amd64/libhogweed.so.5 > __gmpz_roinit_n /usr/lib/amd64/libgnutls.so > __gmpn_sec_mul /usr/lib/amd64/libhogweed.so.5 > __gmpn_sec_add_1 /usr/lib/amd64/libhogweed.so.5 > __gmpn_sec_div_r /usr/lib/amd64/libhogweed.so.5 > __gmpn_cnd_sub_n /usr/lib/amd64/libgnutls.so > __gmpn_cnd_add_n /usr/lib/amd64/libgnutls.so > __gmpz_limbs_read /usr/lib/amd64/libgnutls.so > ld: fatal: symbol referencing errors. No output written t > > > Anyone 'knows' some of these and has a hint ? > > Greetings, > > Stephan > That's not the problem I have on my build machine: Undefined first referenced symbol in file set_field_buffer source3/utils/regedit_dialog.c.39.o set_form_win source3/utils/regedit_dialog.c.39.o set_form_sub source3/utils/regedit_dialog.c.39.o field_buffer source3/utils/regedit_dialog.c.39.o set_current_field source3/utils/regedit_dialog.c.39.o form_driver source3/utils/regedit_dialog.c.39.o post_form source3/utils/regedit_dialog.c.39.o unpost_form source3/utils/regedit_dialog.c.39.o free_field source3/utils/regedit_dialog.c.39.o free_form source3/utils/regedit_dialog.c.39.o dynamic_field_info source3/utils/regedit_dialog.c.39.o new_form source3/utils/regedit_dialog.c.39.o pos_form_cursor source3/utils/regedit_dialog.c.39.o new_field source3/utils/regedit_dialog.c.39.o set_field_back source3/utils/regedit_dialog.c.39.o set_field_opts source3/utils/regedit_dialog.c.39.o ld: fatal: symbol referencing errors. No output written to /export/home/andreas/oi-userland/components/network/samba/build/amd64/bin/ default/source3/utils/samba-regedit collect2: error: ld returned 1 exit status This looks more like a missing -lcurses (or a misdetection of ncurses vs. curses). Yours might be another problem or one that's just with your configuration. Andreas > > > ___ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] meld and gmake REQUIRED_PACKAGES
Thank you, I totally forgot to check solaris-userland. -- Původní e-mail -- Od: Alan Coopersmith Komu: oi-dev@openindiana.org Datum: 4. 1. 2022 18:30:04 Předmět: Re: [oi-dev] meld and gmake REQUIRED_PACKAGES "On 1/4/22 4:27 AM, Nona Hansel wrote: > Such errors are always hard for me to understand. Isn't it weird that it's > looking for .pyc files which aren't part of either manifests/sample- manifest.p5m > nor meld.p5m? Everywhere I only have.py files. The build system is being helpful and automatically adding the compiled .pyc file for every .py file listed in the manifest: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/transforms/autopy > When I check the build directory, I can see that the program installed into build/prototype/i386/usr/ not into build/prototype/i386/mangled like gmake is looking for. Is there a way to fix it? It's doing the right thing - mangled is only for files mangled by the userland-mangler build tool. The rest should be under build/prototype/i386 as you have (note that it's looking for usr/... as the path under there). You might look at what the Solaris build of meld does - but it's still using Python 3.7 (I think just because it was updated before there were 3.9 versions of all the dependencies available in Solaris): https://github.com/oracle/solaris-userland/blob/master/components/gnome/ meld/Makefile -alan- ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] meld and gmake REQUIRED_PACKAGES
Hello, I'm working on updating meld and during gmake REQUIRED_PACKAGES I got a long error message to every .py file from .p5m. One example for all: Couldn't find 'usr/lib/python3.9/site-packages/meld/windowstate.pyc' in any of the specified search directories: /export/home/nona/oi-userland/components/developer/meld /export/home/nona/oi-userland/components/developer/meld/build /export/home/nona/oi-userland/components/developer/meld/build/prototype/ i386 /export/home/nona/oi-userland/components/developer/meld/build/prototype/ i386/mangled /export/home/nona/oi-userland/components/developer/meld/meld-3.21.0 make[1]: *** [/export/home/nona/oi-userland/make-rules/ips.mk:481: /export/ home/nona/oi-userland/components/developer/meld/build/manifest-i386-meld. depend] Error 1 make[1]: Leaving directory '/export/home/nona/oi-userland/components/ developer/meld' gmake: *** [/export/home/nona/oi-userland/make-rules/ips.mk:515: REQUIRED_ PACKAGES] Error 2 Such errors are always hard for me to understand. Isn't it weird that it's looking for .pyc files which aren't part of either manifests/sample- manifest.p5m nor meld.p5m? Everywhere I only have.py files. When I check the build directory, I can see that the program installed into build/prototype/i386/usr/ not into build/prototype/i386/mangled like gmake is looking for. Is there a way to fix it? Current state of related files can be seen here: https://github.com/balrog- nona/oi-userland/commit/87723c83c1492fea03e4254a1860278d04cae4be Thank you for any suggestion. All the best, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] What to do with python module dependancies?
Hello Gary, I believe that when you have a packages that has dependencies, these dependencies must be added as individual packages themselves. After incorporating them (which means create a folder, Makefile, .p5m file and separate PR), your python package would find them. As for knowing in advance how many dependencies a package has, I usually check the package in Fedora and Suse and see their spec files: https://src.fedoraproject.org/ https://build.opensuse.org/ I hope this was helpful. Best regards, Nona -- Původní e-mail -- Od: Gary Mills Komu: oi-dev@openindiana.org Datum: 18. 7. 2021 16:02:07 Předmět: [oi-dev] What to do with python module dependancies? "I'm working on a python package that imports many other python modules. So far I've discovered two python modules that don't have corresponding packages in OI. There should be dependancies on these two packages, but the automatic mechanism seems not to add them. How can I add them myself? Do I do it directly in the P5M file? The original package builds and installs with the setup.py method. It doesn't check for dependancies at all. I don't notice missing dependancies until I test the module and get an error message when an "import" fails. I'd like to be able to build a package that does not have this problem. -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Numpy - upgrade for Python 3.X
Hello, I'm thinking about updating numpy since we have it just for Python 2.7. But before doing any changes, I wanna consult some things for having a clearer view of what to do. First, when I run pkg search -H -r -o pkg.name 'depend:require:library/python/numpy' I get: library/python-2/numpy which tells me that there are no packages with numpy as a dependency, right? Second, the newest version of numpy https://github.com/numpy/numpy/releases supports Python 3.7. and 3.9. Is that okay? I believe it is because Python 3.5. doesn't have numpy today anyway and according to this web https:// endoflife.date/python security support for Python 3.5. has ended 10 months ago. I assume I can start working on it on Monday but it won't be finished any time soon - the Makefile looks very complicated to me. Thank you for your insights. Any tips about this upgrade would be much appreciated. Best regards, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Variable PATH in Makefile (tornado)
Thank you, PATH=$(PATH.illumos) worked! -- Původní e-mail -- Od: Andreas Wacknitz Komu: oi-dev@openindiana.org Datum: 14. 4. 2021 13:19:36 Předmět: Re: [oi-dev] Variable PATH in Makefile (tornado) "Am 14.04.21 um 12:40 schrieb Nona Hansel: > Hello, > > I'm having some problems updating tornado. Currently, the PATH > variable in Makefile is defined in the older mode like this: > PATH=/usr/bin:/usr/gnu/bin:/usr/sbin > Like this, tornado builds, installs and publishes fine. > The old settings prefer / priorize our own tools over the GNU ones because /usr/bin comes before /usr/gnu/bin. When you look in make-rules for the definitions of PATH.gnu and PATH.illumos then you will see that PATH.illumos does something similar. It priorizes our tools over the GNU tools, but nevertheless it also includes the GNU binaries path. So I would expect that the right thing to do would be to use PATH=$(PATH.illumos) here. Andreas ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Variable PATH in Makefile (tornado)
Hello,
I'm having some problems updating tornado. Currently, the PATH variable in
Makefile is defined in the older mode like this:
PATH=/usr/bin:/usr/gnu/bin:/usr/sbin
Like this, tornado builds, installs and publishes fine.
When I change it to the newer mode:
PATH=$(PATH.gnu)
It builds fine, but fails during gmake install with this message:
Copying tornado.egg-info to /export/home/nona/oi-userland/components/python/
tornado/build/prototype/i386/usr/lib/python2.7/vendor-packages/tornado-5.1.1
-py2.7.egg-info
running install_scripts
gfind /export/home/nona/oi-userland/components/python/tornado/build/
prototype/i386/usr/lib/python2.7/vendor-packages -type f -exec gawk '/^#!.*
python/{print FILENAME}{nextfile}' {} + | xargs gsed -i -e '1 s;^.*$;#!/usr/
bin/python2.7;'
gsed: no input files
gmake: *** [/export/home/nona/oi-userland/make-rules/setup.py.mk:113: /
export/home/nona/oi-userland/components/python/tornado/build/i86-2.7/.
installed] Error 123
Do you have any idea why it doesn't work? How can I fix it?
Thank you!
Best regards,
Nona
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Fwd: Re: requests-37
Hello again, since I have installed new versions today, I get the same warning every time I use pkg. /usr/lib/python3.7/vendor-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (4.0.0) doesn't match a supported version! RequestsDependencyWarning) But it looks like the version 2.25.1 could work with chardet 4.0.0: https://github.com/psf/requests/blame/master/setup.py#L44 Can I try to update requests to this version or was there a particular reason why to have 2.22? Regards, Nona -- Původní e-mail -- Od: Nona Hansel Komu: OpenIndiana Developer mailing list Datum: 17. 2. 2021 10:22:26 Předmět: Re: [oi-dev] requests-37 " I'm trying to fix it and the requests publishes and locally installs fine, but when I try to use it in python3.7: >>> import requests I get this message: /usr/lib/python3.7/vendor-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (4.0.0) doesn't match a supported version! RequestsDependencyWarning) When I ask pipdeptree, it gives me this: requests==2.22.0 - chardet [required: >=3.0.2,<3.1.0, installed: 4.0.0] - idna [required: >=2.5,<2.9, installed: 2.10] - urllib3 [required: >=1.21.1,<1.26,!=1.25.0, installed: 1.25.1] It looks like the version of chardet and maybe idna are outside of requests' scope of supported versions. Is there a way how to make requests use the previous versions? Thank you! -- Původní e-mail -- Od: Aurélien Larcher Komu: OpenIndiana Developer mailing list Datum: 16. 2. 2021 18:57:38 Předmět: Re: [oi-dev] requests-37 "Probably I messed up the rebase and -$(PYV) is missing from the manifest in the fmri. On 2/16/21, Nona Hansel wrote: > > Hello, > > > > > I'm trying to install requests-37 which according to it's Makefile we > should > provide, but when I ask for it: > > > > > $ pfexec pkg info -r library/python/requests* > > > > > it doesn't show it nor it shows requests-39. > > > > > It can't be found here: > https://pkg.openindiana.org/hipster/en/search.shtml? > action=Search=requests-37=1 > > and when I try to find requests-35 in this website, it finds the previous > version. > > > > > Isn't there something wrong with this component? > > > > > Thank you, > > Nona > -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ""___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] requests-37
I'm trying to fix it and the requests publishes and locally installs fine, but when I try to use it in python3.7: >>> import requests I get this message: /usr/lib/python3.7/vendor-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (4.0.0) doesn't match a supported version! RequestsDependencyWarning) When I ask pipdeptree, it gives me this: requests==2.22.0 - chardet [required: >=3.0.2,<3.1.0, installed: 4.0.0] - idna [required: >=2.5,<2.9, installed: 2.10] - urllib3 [required: >=1.21.1,<1.26,!=1.25.0, installed: 1.25.1] It looks like the version of chardet and maybe idna are outside of requests' scope of supported versions. Is there a way how to make requests use the previous versions? Thank you! -- Původní e-mail -- Od: Aurélien Larcher Komu: OpenIndiana Developer mailing list Datum: 16. 2. 2021 18:57:38 Předmět: Re: [oi-dev] requests-37 "Probably I messed up the rebase and -$(PYV) is missing from the manifest in the fmri. On 2/16/21, Nona Hansel wrote: > > Hello, > > > > > I'm trying to install requests-37 which according to it's Makefile we > should > provide, but when I ask for it: > > > > > $ pfexec pkg info -r library/python/requests* > > > > > it doesn't show it nor it shows requests-39. > > > > > It can't be found here: > https://pkg.openindiana.org/hipster/en/search.shtml? > action=Search=requests-37=1 > > and when I try to find requests-35 in this website, it finds the previous > version. > > > > > Isn't there something wrong with this component? > > > > > Thank you, > > Nona > -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] requests-37
Hello, I'm trying to install requests-37 which according to it's Makefile we should provide, but when I ask for it: $ pfexec pkg info -r library/python/requests* it doesn't show it nor it shows requests-39. It can't be found here: https://pkg.openindiana.org/hipster/en/search.shtml? action=Search=requests-37=1 and when I try to find requests-35 in this website, it finds the previous version. Isn't there something wrong with this component? Thank you, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
-- Původní e-mail -- Od: Aurélien Larcher Komu: OpenIndiana Developer mailing list Datum: 2. 2. 2021 0:58:32 Předmět: Re: [oi-dev] Tasks to focus on " On Thu, Jan 28, 2021 at 3:55 AM Gary Mills mailto:gary_mi...@fastmail.fm)> wrote: "On Wed, Jan 27, 2021 at 03:14:14PM +0100, Aurélien Larcher wrote: > > My list is pretty much the same except that Python 3.9 is now packaged > together with some modules (including pip and pipdeptree for > convenience) and that we will skip 3.8. > Also we are going to jump to pkg supporting 3.9 as Andy did recently. > In the top priorities: > - Moving packages to use Python 3.7 instead of 2.7 or 3.5. > - Adding python modules for 3.7 and 3.9. > - Updating Clang. > > One urgent task is to move away from Python 2.7 and 3.5. > For example all these dependencies need to be addressed: the more hands > the better. > alarcher@narval:/export/home/alarcher$ pkg search -H -r -o [2]pkg.name (http://pkg.name) > 'depend:require:runtime/python-27' | sed -e '/library\/python/d' | sort > -u > application/cluster/cluster-glue I decided on Python upgrades, starting with the cluster-glue package. I'd like to determine if newer versions are available, since they may use newer Python versions. However, I couldn't find any mention of Python except for this line in Makefile: REQUIRED_PACKAGES += runtime/python-27 " The list of packages I provided does not contain Python modules per se but software relying on Python 2.7. This could be e.g. because of providing Python bindings. On the other hand you can find in the directory https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python (https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python) all the python modules provided in oi-userland. It may be more pleasant to update these components to support Python 3.7 and 3.9 beforehand. As you see fit. " Hi, do I get it right that the task now is to "just" add Python 3.7 and 3. 9. to the python modules or is it to deprecate Python 2.7. plus add Python 3.7 and 3. 9? Thank you! " " I decided I needed to install python39 on my development system first, using python37 as a model. I do have a few questions. Is it version 3.9.1 that you are using? What did you do with the tkinter manifest? What configure options did you use? I suppose most of the answers are in your Makefile . > This is a long list of packages that should be either patched to use > 3.7, updated to a recent version supporting 3.X or simply removed if > they are obsolete. > Of course due to dependency hell we may need to update some of the > python packages in the meantime to provide >= 3.7 versions. > So far ~25% of the Python modules have been upgraded (within a week, so > the task is not as humongous as one would think). I'm sure I'll discover most of those things as I go along. -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- ___ oi-dev mailing list oi-dev@openindiana.org(mailto:oi-dev@openindiana.org) https://openindiana.org/mailman/listinfo/oi-dev (https://openindiana.org/mailman/listinfo/oi-dev) " -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
-- Původní e-mail -- Od: Aurélien Larcher Komu: OpenIndiana Developer mailing list Datum: 2. 2. 2021 0:58:32 Předmět: Re: [oi-dev] Tasks to focus on " On Thu, Jan 28, 2021 at 3:55 AM Gary Mills mailto:gary_mi...@fastmail.fm)> wrote: "On Wed, Jan 27, 2021 at 03:14:14PM +0100, Aurélien Larcher wrote: > > My list is pretty much the same except that Python 3.9 is now packaged > together with some modules (including pip and pipdeptree for > convenience) and that we will skip 3.8. > Also we are going to jump to pkg supporting 3.9 as Andy did recently. > In the top priorities: > - Moving packages to use Python 3.7 instead of 2.7 or 3.5. > - Adding python modules for 3.7 and 3.9. > - Updating Clang. > > One urgent task is to move away from Python 2.7 and 3.5. > For example all these dependencies need to be addressed: the more hands > the better. > alarcher@narval:/export/home/alarcher$ pkg search -H -r -o [2]pkg.name (http://pkg.name) > 'depend:require:runtime/python-27' | sed -e '/library\/python/d' | sort > -u > application/cluster/cluster-glue I decided on Python upgrades, starting with the cluster-glue package. I'd like to determine if newer versions are available, since they may use newer Python versions. However, I couldn't find any mention of Python except for this line in Makefile: REQUIRED_PACKAGES += runtime/python-27 " The list of packages I provided does not contain Python modules per se but software relying on Python 2.7. This could be e.g. because of providing Python bindings. On the other hand you can find in the directory https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python (https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python) all the python modules provided in oi-userland. It may be more pleasant to update these components to support Python 3.7 and 3.9 beforehand. As you see fit. " Hello, I'll also try to update some of these. " " I decided I needed to install python39 on my development system first, using python37 as a model. I do have a few questions. Is it version 3.9.1 that you are using? What did you do with the tkinter manifest? What configure options did you use? I suppose most of the answers are in your Makefile . > This is a long list of packages that should be either patched to use > 3.7, updated to a recent version supporting 3.X or simply removed if > they are obsolete. > Of course due to dependency hell we may need to update some of the > python packages in the meantime to provide >= 3.7 versions. > So far ~25% of the Python modules have been upgraded (within a week, so > the task is not as humongous as one would think). I'm sure I'll discover most of those things as I go along. -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- ___ oi-dev mailing list oi-dev@openindiana.org(mailto:oi-dev@openindiana.org) https://openindiana.org/mailman/listinfo/oi-dev (https://openindiana.org/mailman/listinfo/oi-dev) " -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev "___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Missing locale zh_CN.GB18030
Hi, I'm trying to update findutils. Some test are skipping because I don't have zh_CN.GB18030 locale on my system. How can I get it? pfexec pkg info -r doesn't work for me in this case. Thank you in advance. Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Python components
Hi, I'm thinking about updating two Python packages - tqdm and colorama. Currently, there is variable PYTHON_VERSIONS= 3.5 in both Makefiles which means, if I understand it correctly, that the package is build for Python 3.5. I wonder if I should let this variable like this or should I increase Python version. If so, to what version? Or should we have more versions at the same time? Thank you, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
