Re: [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Tue, Oct 4, 2022 at 4:34 PM Marcel Telka wrote: > On Fri, Sep 30, 2022 at 07:16:18PM +0200, s...@pandora.be wrote: > > > > Part of the problem is, I think, that there is no maintainer any longer, > as far as I know, for the mkdocs component in oi-userland. > > > > If someone knows how to build mkdocs with python 3 (which is perhaps > possible, I don't know, I have no experience with building python > components) then this would solve most of the problem, I think ... > > > > Thanks for your work on this, because as I confirmed, there are indeed > really issues with the mkdocs python2.7. > > > > Several people related to the oi-docs are aware that we have a Python > 2.7 problem, but we are unsure how to fix it, I think. > > > > For example in my Vagrantfile I have a comment about a missing 2.7 > 'futures' component: > > > > > https://github.com/OpenIndiana/vagrantfiles/blob/main/oi-docs/Vagrantfile > > > > # there used to be a futures package in the repo ... > > # library/python/futures seems to have a problem now > > pfexec pkg install -v \ > > git lynx links\ > > library/python/futures \ > > library/python/mkdocs \ > > developer/documentation-tool/mdl > > # as of 21/9/2021 futures IPS is missing so install by pip > > pfexec pip install futures > > > > Because such "pip install" actions print a clear warning by Python that > we are using an unsupported Python 2.7, it is clear that something must be > done. > > The futures python package was obsoleted in May 2021 in OpenIndiana. > The reason is, apparently, this - see https://pypi.org/project/futures/: > > It does not work on Python 3 due to Python 2 syntax being used in the > codebase. Python 3 users should not attempt to install it, since the > package is already included in the standard library. > Marcel is right, there were a few modules to ensure the transition from Python 2 to Python 3 such as this one and other backport.* packages. Migrating to Python 3 as default and obsoleting these transitional packages should be enough. > > > Regards. > > -- > +---+ > | 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 > -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] pkg update Problems with python 3.5
Hello, I setup a virtual machine running OpenIndiana with installation image OI-hipster-gui-20211031.iso. (the latest) After setup I started pkg update. Since I follow the mailing list, I heard that python has been updated. Is this a problem? And where is the solution? Rem.: I used to download/intall a copy of isfdb.org, which uses python 2.7. I am a little sad that this version is no longer included, and or uninstalled. Best regards Klaus Protocol of the update root@openindiana:/export/home/isg# pkg update Creating Plan (Solver einrichten): - Traceback (most recent call last): File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 1525, in __plan_op File "/usr/lib/python3.5/vendor-packages/pkg/client/image.py", line 4640, in make_update_plan File "/usr/lib/python3.5/vendor-packages/pkg/client/image.py", line 4480, in __make_plan_common File "/usr/lib/python3.5/vendor-packages/pkg/client/imageplan.py", line 1431, in plan_update File "/usr/lib/python3.5/vendor-packages/pkg/client/imageplan.py", line 1410, in __plan_update_solver File "/usr/lib/python3.5/vendor-packages/pkg/client/imageplan.py", line 474, in __run_solver File "/usr/lib/python3.5/vendor-packages/pkg/client/imageplan.py", line 1399, in solver_cb File "/usr/lib/python3.5/vendor-packages/pkg/client/pkg_solver.py", line 1370, in solve_update_all File "/usr/lib/python3.5/vendor-packages/pkg/client/pkg_solver.py", line 574, in __enforce_unique_packages File "/usr/lib/python3.5/vendor-packages/pkg/client/pkg_solver.py", line 2761, in __gen_dependency_clauses File "/usr/lib/python3.5/vendor-packages/pkg/client/pkg_solver.py", line 2831, in __gen_negation_clauses File "/usr/lib/python3.5/vendor-packages/pkg/client/pkg_solver.py", line 2831, in MemoryError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pkg", line 5968, in handle_errors File "/usr/bin/pkg", line 5954, in main_func File "/usr/bin/pkg", line 2292, in update File "/usr/lib/python3.5/vendor-packages/pkg/client/client_api.py", line 1572, in _update File "/usr/lib/python3.5/vendor-packages/pkg/client/client_api.py", line 1404, in __api_op File "/usr/lib/python3.5/vendor-packages/pkg/client/client_api.py", line 1258, in __api_plan File "/usr/lib/python3.5/vendor-packages/pkg/client/client_api.py", line 1230, in __api_plan File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 1579, in __plan_op File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 1171, in __plan_common_exception File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 5498, in log_operation_end File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 828, in log_operation_end self.operation_result = result File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 377, in __setattr__ op.end_time = misc.time_to_timestamp(None) File "/usr/lib/python3.5/vendor-packages/pkg/misc.py", line 128, in time_to_timestamp MemoryError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pkg", line 5975, in handle_errors File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 813, in abort File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 778, in abort self.operation_result = result File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 377, in __setattr__ op.end_time = misc.time_to_timestamp(None) File "/usr/lib/python3.5/vendor-packages/pkg/misc.py", line 128, in time_to_timestamp MemoryError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pkg", line 6155, in File "/usr/bin/pkg", line 6110, in handle_errors File "/usr/lib/python3.5/vendor-packages/pkg/client/api.py", line 813, in abort File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 778, in abort self.operation_result = result File "/usr/lib/python3.5/vendor-packages/pkg/client/history.py", line 377, in __setattr__ op.end_time = misc.time_to_timestamp(None) File "/usr/lib/python3.5/vendor-packages/pkg/misc.py", line 128, in time_to_timestamp MemoryError Segmentation Fault (Speicherabzug geschrieben) ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] pkg update Problems with python 3.5
On Wed, Oct 05, 2022 at 01:16:38PM +, Klaus Elsbernd wrote: > I setup a virtual machine running OpenIndiana with installation image > OI-hipster-gui-20211031.iso. (the latest) > > After setup I started pkg update. Since I follow the mailing list, I heard > that python has been updated. Is this a problem? And where is the solution? I do not think your problem is related to python version. I see a lot of "MemoryError" lines in your log. Maybe you have not enough RAM assigned to your virtual machine? > Rem.: I used to download/intall a copy of isfdb.org, which uses python 2.7. > I am a little sad that this version is no longer included, and or > uninstalled. The runtime/python-27 package is still available in OI repos. 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
Re: [oi-dev] pkg update Problems with python 3.5
Hallo Marcel, Am 05.10.2022 um 15:22 schrieb Marcel Telka: I do not think your problem is related to python version. I see a lot of "MemoryError" lines in your log. Maybe you have not enough RAM assigned to your virtual machine? Well you're right. It had only 4GB Memory configured. I doubled it to 8GB and the update worked. I thought, 4GB would be enough. Thank you. System seems to work, nevertheless, vbox additions not. Now I get the following error messages: WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed WARNING: /pci@0,0/pci8086,le31@c (xhci0): Connecting device on port 1 failed 120/120 Delete service svc:/network/socket-fiIter as there are no supporting manifests Delete service svc:/network/ssl/proxy as there are no supporting manifests Delete instance openldap_24 from service svc:/network/Idap/server Configuring devices. Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.154 Wed Jun 22 04:43:29 UTC 202 2 Installing virtualbox Additions doesn't help. Even worse, vbox services won't start. = root@openindiana:/export/home/isg# svcs -x svc:/application/virtualbox/vboxservice:default (VirtualBox Service.) State: maintenance since 5. Oktober 2022 urn 18:21:06 CEST Reason: Start method failed repeatedly, last exited with status 1. See: http://illumos.org/msg/SMF-8000-KS See: /var/svc/log/application-virtualbox-vboxservice:default.log Impact: This service is not running. svc:/application/virtualbox/vboxmslnk:default (VirtualBox Mouse module link.) State: maintenance since 5. Oktober 2022 urn 18:21:07 CEST Reason: Start method failed repeatedly, last exited with status 1. See: http://illumos.org/msg/SMF-8000-KS See: /var/svc/log/application-virtualbox-vboxmslnk:default.log Impact: This service is not running. root@openindiana:/export/home/isg# less /var/svc/log/application-virtualbox-vbox application-virtualbox-vboxmslnk:default.log application-virtualbox-vboxservice:default.log root@openindiana:/export/home/isg# less /var/svc/log/application-virtualbox-vbox next pkg update round. Perhaps I should re-install the whole system with more memory in the first place. Klaus WARNING: mod_load: cannot load module 'vboxms' WARNING: vboxms: unable to resolve dependency, module 'drv/vboxguest' not found Oct 5 19:06:39 svc.startdC9J: svc:/application/virtualbox/vboxmslnk:default: Method "/usr/sbin/vb oxmslnk" failed with exit status 1. /usr/kernel/drv/amd64/vboxguest: undefined symbol 'removectx' /usr/kernel/drv/amd64/vboxguest: undefined symbol 'installctx' WARNING: mod_load: cannot load module 'vboxguest' Oct 5 19:06:40 svc.startdC9J: svc:/application/virtualbox/vboxservice:default: Method "/usr/bin/V BoxService" failed with exit status 1. Oct 5 19:06:40 svc.startdC9J: svc:/application/virtualbox/vboxmslnk:default: Method "/usr/sbin/vb oxmslnk" failed with exit status 1. /usr/kernel/drv/amd64/vboxguest: undefined symbol 'removectx' /usr/kernel/drv/amd64/vboxguest: undefined symbol 'installctx' WARNING: mod_load: cannot load module 'vboxguest' Oct 5 19:06:41 svc.startdC9J: svc:/application/virtualbox/vboxservice:default: Method "/usr/bin/V BoxService" failed with exit status 1. /usr/kernel/drv/amd64/vboxguest: undefined symbol 'removectx' /usr/kernel/drv/amd64/vboxguest: undefined symbol 'installctx' WARNING: mod_load: cannot load module 'vboxguest' Oct 5 19:06:41 svc.startdC9J: svc:/application/virtualbox/vboxservice:default: Method "/usr/bin/V BoxService" failed with exit status 1. Oct 5 19:06:41 svc.startdC9J: svc:/application/virtualbox/vboxmslnk:default: Method "/usr/sbin/vb oxmslnk" failed with exit status 1. Oct 5 19:06:41 svc.startdC9J: application/virtualbox/vboxservice:default failed: transitioned to maintenance (see 'svcs -xv' for details) Oct 5 19:06:41 svc.startdC9J: application/virtualbox/vboxmslnk:default failed: transitioned to ma intenance (see 'svcs -xv' for details) Oct 5 19:06:53 openindiana savecore: System dump time: Mon Oct 3 14:36:37 2022 Oct 5 19:06:53 openindiana savecore: Panic crashdump pending on dump device but dumpadm -n in eff ect; run savecore(8) manually to extract. Image UUID eb6462a5-dc6d-e818-bb6f-acl4abl0e7d3. Oct 5 19:06:55 openindiana genunix: /usr/kernel/drv/amd64/vboxguest: undefined symbol Oct 5 19:06:55 openindiana
