Re: [OpenIndiana-discuss] mirrors
On Fri, Jul 19, 2024 at 11:28:46AM +0200, Udo Grabowski (IMK) wrote: > Got this from Princeton (they used the Georgia mirror...), they > cannot rsync because they probably have the wrong path (from gatech): https://openindiana.org/pipermail/oi-dev/2024-June/033662.html -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Repository Cleanup
On Wed, Jul 03, 2024 at 07:32:12PM +0200, Andreas Wacknitz via openindiana-discuss wrote: > Am 03.07.24 um 07:13 schrieb Goetz T. Fischer: > > On Sat, 22 Jun 2024 13:58:55 +0200, Till Wegmüller wrote: > > > To update the system cleanly use these steps: > > > pkg refresh --full > > > pkg update -v > > i did that yesterday and noticed that pkg's "depend" option delivers no > > results anymore. e.g. i > > tried: > > pkg search -r depend::library/security/openssl > > > > returns nothing. did something change there? > > I can confirm the problem with pkg search. Most likely this is due to > one of the many python package updates. > At least someone else reported that pkg search in an older BE still > works. So our work on the repository cannot be the cause. Do we have more info about the older BE when it worked? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Heads-Up: Plan to obsolete application/cluster/pcs
Hi, We plan to obsolete the application/cluster/pcs package in OpenIndiana soon. There are at least following reasons for the obsoletion: - our current packaged version (0.10.1) is very old; this version was released upstream 5.5 years ago, - the pcs package is broken and does not work: https://openindiana.org/pipermail/oi-dev/2024-May/033632.html - it is hard to maintain pcs: https://openindiana.org/pipermail/oi-dev/2024-May/033633.html - there are no known pcs users If you believe the application/cluster/pcs package should not be obsoleted then please adopt the package and start to maintain it. Thanks for understanding. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Heads-Up: Motif obsoletion
Hi, I plan to obsolete the Motif library (together with the cde-incorporation) because it is: - very old - the package is more than 10 years old - not maintained - we have no knowledge how to build it (there is no build recipe for it in oi-userland) - not needed - nothing in OpenIndiana depends on it Namely, the following two packages will be obsoleted: pkg://openindiana.org/consolidation/cde/cde-incorporation@0.5.11-2013.0.0.0 pkg://openindiana.org/library/motif@0.5.11-2013.0.0.0 If you believe we should not obsolete Motif then please package it and contribute to oi-userland. It was open sourced and LGPLed more than 10 years ago. Thank you. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Old(er) GCC packages removal
On Thu, Feb 29, 2024 at 04:51:42PM +0100, Predrag Zečević via openindiana-discuss wrote: > currently I have these (OI updated today): > > :; pkg list | grep gcc > developer/gcc-10 10.5.0-2023.0.0.1 i-- > developer/gcc-12 12.3.0-2023.0.0.3 i-- > developer/gcc-13 13.2.0-2023.0.0.3 i-- > developer/gcc-7 7.5.0-2020.0.1.9 i-- > system/library/gcc-10-runtime 10.5.0-2023.0.0.1 i-- > system/library/gcc-12-runtime 12.3.0-2023.0.0.3 i-- > system/library/gcc-13-runtime 13.2.0-2023.0.0.3 i-- > system/library/gcc-7-runtime 7.5.0-2020.0.1.9 i-- > system/library/gccgo-10-runtime 10.5.0-2023.0.0.1 i-- > system/library/gccgo-12-runtime 12.3.0-2023.0.0.3 i-- > system/library/gccgo-13-runtime 13.2.0-2023.0.0.3 i-- > > So, wanted to get rid of old ones, because: ... snip ... > Is it too early for clean-up? Yes. Reasons why we cannot or should not obsolete varius gcc versions: illumos-gcc - at least one userland component is built using it gcc-3 - runtime dependency for one ancient package gcc-7 - shadow compiler for illumos-gate gcc-10 - primary compiler for illumos-gate; at least three userland components are still built using it gcc-11,12 - still supported versions, no need to obsolete them gcc-11 - at least one userland component is built using it gcc-12 - at least one userland component is built using it -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Sat, Feb 03, 2024 at 08:52:51PM +0100, Marcel Telka wrote: > On Thu, Jan 18, 2024 at 06:06:20PM +0100, Marcel Telka wrote: > > On Tue, Jan 09, 2024 at 04:24:42PM +0100, Marcel Telka wrote: > > > I propose obsoletion of following 39 OpenIndiana packages: > > > > I'm happy to let you know that the list now contains 38 entries only. > > Matthew R. Trower packaged text/dwdiff so the list is down to 37 entries > only. FYI: https://github.com/OpenIndiana/oi-userland/pull/16318 When anything from the list gets packaged, then it simply would need to be removed from the history file too. Thanks. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
Hi Matthew, On Wed, Jan 31, 2024 at 05:03:45AM -0600, Matthew R. Trower wrote: > Alright, I've submitted a PR for dwdiff: > https://github.com/OpenIndiana/oi-userland/pull/15866 > > While I've of course tested it on my end, as this is my first OI package, > I'd like to wait for it to be reviewed and merged by someone with experience > before continuing with packaging the others. Just as a sanity check, that > I've followed the process correctly. > > Hopefully I have enough kinks works out now that future packaging is > easier/quicker. Your dwdiff packaging effort was clear success. Do you plan to continue? It would be great if you do. Thank you. > > On 1/22/24 12:15, Marcel Telka wrote: > > > On Wed, Jan 10, 2024 at 05:26:22PM -0600, Matthew R. Trower wrote: > > > > I'll have a look at getting JEdit, dwdiff, ROXTerm and pen packaged up. > > > > iozone is not GPL, but I can look at it as well. > > > > > > Any progress in this area? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI hipster Text Install USB 2023.10 fails
On Tue, Feb 13, 2024 at 09:29:38PM +0100, Olaf Bohlen wrote: > File > "/usr/lib/python3.9/vendor-packages/osol_install/text_install/inner_window.py", > line 507, in translate_input > if curses.ascii.isdigit(input_key): > File "/usr/lib/python3.9/curses/ascii.py", line 59, in isdigit > def isdigit(c): return 48 <= _ctoi(c) <= 57 > TypeError: '<=' not supported between instances of 'int' and 'NoneType' https://www.illumos.org/issues/15248 -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On Tue, Feb 13, 2024 at 02:16:25PM +0100, Till Wegmüller wrote: > On 13.02.24 14:03, Marcel Telka wrote: > > On Tue, Feb 13, 2024 at 01:56:07PM +0100, Till Wegmüller wrote: > > > libdrm 109 is in the pipeline if somebody can get the builds to compile on > > > gcc13. It's a bit out of my depth unfortunetely. > > > > > > https://github.com/illumos/gfx-drm/pull/26 > > > > Unfortunately, the illumos/gfx-drm seems stale. We should probably dust > > off https://github.com/OpenIndiana/gfx-drm and switch oi-userland to use > > it instead of https://github.com/illumos/gfx-drm. > > > > Gordon Ross answered me within a day last thing I asked. I don't think that > is necessary. But we need somebody to freshen up the PR :) Yes, it is not necessary. The other option is this: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openindiana/gfx-drm/patches -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On Tue, Feb 13, 2024 at 01:56:07PM +0100, Till Wegmüller wrote: > libdrm 109 is in the pipeline if somebody can get the builds to compile on > gcc13. It's a bit out of my depth unfortunetely. > > https://github.com/illumos/gfx-drm/pull/26 Unfortunately, the illumos/gfx-drm seems stale. We should probably dust off https://github.com/OpenIndiana/gfx-drm and switch oi-userland to use it instead of https://github.com/illumos/gfx-drm. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] limited fqdn length on installation?
On Sun, Feb 11, 2024 at 12:53:28AM +0100, Rolf M. Dietze wrote: > Is that field length limitation there since the beginning? Likely. It is well known problem: https://www.illumos.org/issues/13742 -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Thu, Jan 18, 2024 at 06:06:20PM +0100, Marcel Telka wrote: > On Tue, Jan 09, 2024 at 04:24:42PM +0100, Marcel Telka wrote: > > I propose obsoletion of following 39 OpenIndiana packages: > > I'm happy to let you know that the list now contains 38 entries only. Matthew R. Trower packaged text/dwdiff so the list is down to 37 entries only. $ pkg list -afv text/dwdiff FMRI IFO pkg://openindiana.org/text/dwdiff@2.1.4-2024.0.0.0:20240201T182637Z i-- pkg://openindiana.org/text/dwdiff@1.5.2-2013.0.0.0:20151027T080702Z --- $ Thank you, Matthew. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-up: Python 3.7 reached EOL, please uninstall it
On Mon, Jan 29, 2024 at 06:53:39PM +, Apostolos Syropoulos via openindiana-discuss wrote: > I have entered the command mentioned in your message and here is what I get: > # pkg uninstall -v runtime/python-37 'library/python/*-37' > web/server/apache-24/module/apache-wsgi-37 > > pkg uninstall: 'web/server/apache-24/module/apache-wsgi-37' matches no > installed packages > # pkg uninstall -v runtime/python-37 'library/python/*-37' > Creating Plan (Solver setup): \ > pkg uninstall: Unable to remove 'runtime/python-37@3.7.16-2023.0.0.2' due to > the following packages that depend on it: > developer/dtrace/toolkit@0.99-2022.0.0.6 Your system is apparently not up-to-date. There is already developer/dtrace/toolkit@0.99-2023.0.0.7 that does not depend on runtime/python-37. So to solve, just update. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Heads-up: Python 3.7 reached EOL, please uninstall it
Hi, Python 3.7 reached end of life[1] in June 2023 (7 months ago). Currently there is no OpenIndiana package that depends on Python 3.7, except some Python modules that are otherwise unused. They are still sitting in the IPS package repository waiting for their obsoletion. We are slowly obsoleting them but since there are hundreds of such packages the process is slow. The slowness of the process does have some negative side effects for end users so here is the heads up and a suggestion how to solve such issues. The issue you could encounter is a failure when you try to install or upgrade some packages, for example: # pkg install library/python/rbtools Creating Plan (Running solver): - pkg install: No matching version of library/python/rbtools can be installed: Reject: pkg://openindiana.org/library/python/rbtools@4.1-2023.0.0.0:20230525T122724Z Reason: No version matching 'conditional' dependency library/python/rbtools-37@4.1-2023.0.0.0 can be installed Reject: pkg://openindiana.org/library/python/rbtools-37@4.1-2023.0.0.0:20230525T122701Z Reason: All acceptable versions of 'require' dependency on library/python/certifi-37 are obsolete # Please note that not only library/python/* packages are affected. Basically any package that depends on any Python-related package could be affected similarly. When you see similar failure stating that some package ending with '-37' cannot be installed, then you are affected by this. How to solve the issue? The solution is easy: Uninstall all Python 3.7 related packages from your system using command like: # pkg uninstall -v runtime/python-37 \ 'library/python/*-37' \ web/server/apache-24/module/apache-wsgi-37 The removal of Python 3.7 packages is recommended even if you currently do not see any issue related to Python 3.7. Please ask if you are experiencing any unforeseen issue related to this. Thank you. [1] see https://devguide.python.org/versions/#versions -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] mysql/mariadb secure installation script command not found
On Tue, Jan 23, 2024 at 12:38:46AM -0500, Christopher D. Bartels wrote: > I'm working on configuring a fresh install of mariadb & have tried several > ways to get the mysql_secure_installation script to run, including changing > it to mariadb-secure-installation, & changing these to use the full path > during execution. What exactly does not work? What happens when you run /usr/mariadb/10.6/bin/mariadb-secure-installation on an unmodified OI installation with the mariadb service up and running? -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mariadb always in maintenance mode
On Sun, Jan 21, 2024 at 08:56:15PM -0500, Christopher D. Bartels wrote: > I have the following repeated through the log: > > FATAL ERROR: Could not find /usr/mariadb/10.6/share/mysql_test_db.sql > > > So I've installed pkg:/database/mariadb-106/tests, which I thought had been > pulled in when I installed the base package, but apparently not. This is the > fix. Glad to see you managed it to work. I tried something similar and I see the same issue. The installation of database/mariadb-106/tests solves the problem but it is more a workaround than the real fix. I believe the problem is in the /lib/svc/method/mariadb_106 file where the test database is attempted to be created during initialization. This should be probably avoided. > Now I question whether I need this other package I see during search, > pkg:/database/mariadb-106/library. If you do not have anything that depends on it then you do not need it. There are currently 26 packages (only) that needs database/mariadb-106/library so it does not need to be installed everywhere. > Despite the service being online, will this give me a problem later by > chance? No. It is not needed to run the MariaDB server. > And shouldn't the tests package be a dependency if the service won't start > without it? How do things work here with regards to that? That's one possible option how to solve the problem, but I believe we can do better (see above). BTW, feel free to file a bug report so the issue is not forgotten. Thank you. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
Hi Matthew, On Wed, Jan 10, 2024 at 05:26:22PM -0600, Matthew R. Trower wrote: > I'll have a look at getting JEdit, dwdiff, ROXTerm and pen packaged up. > iozone is not GPL, but I can look at it as well. Any progress in this area? Thank you. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Flag-day: MATE switched from XScreenSaver to mate-screensaver
Hi, The default MATE Desktop Environment installation switched from XScreenSaver to mate-screensaver. This constitutes a flag day if your system is running with the mate_install package installed. If you do not have the mate_install package installed this is just heads-up for you. If you do not have the XScreenSaver installed then you can simply ignore this message. Please read below if you want to keep XScreenSaver. * How to SWITCH from XScreenSaver to mate-screensaver if you DO HAVE the mate_install package installed? Once you update to recent bits you'll end up with both XScreenSaver and mate-screensaver installed. You very likely do not want that and it is recommended to uninstall XScreenSaver using: sudo pkg uninstall -v 'desktop/xscreensaver*' * How to SWITCH from XScreenSaver to mate-screensaver if you DO NOT HAVE the mate_install package installed? In this case you should do the switch manually using: sudo pkg uninstall -v 'desktop/xscreensaver*' sudo pkg install -v desktop/mate/mate-screensaver * How to KEEP XScreenSaver (and do NOT SWITCH to mate-screensaver) if you DO HAVE the mate_install package installed? Since mate_install package constitutes the default MATE Desktop Environment installation it is not possible to avoid installation of mate-screensaver when there is mate_install installed. If you want to avoid mate-screensaver and keep XScreenSaver you need to uninstall the mate_install package. * How to KEEP XScreenSaver (and do NOT SWITCH to mate-screensaver) if you DO NOT HAVE the mate_install package installed? You do not need to do anything special :-). * Why we did the switch from XScreenSaver to mate-screensaver? Please read the rationale here: https://github.com/OpenIndiana/oi-userland/pull/15702 Regards. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Replace xscreensaver with mate-screensaver
On Sun, Jan 21, 2024 at 09:48:33AM -0600, Gary Mills wrote: > require in a screensaver. I'm going to keep it. The password box > does show the wrong time, six hours fast in my case, but I'm willing > to ignore that error. Yes, I see that too. It apparently uses UTC time instead of local time. Not sure it is MATE bug or OI bug. I do not see this on a Linux box with older MATE. So it is possibly OI issue. Fee free to file a bug report. Thank you. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Replace xscreensaver with mate-screensaver
Hi Gary, Thanks for the report. On Sun, Jan 21, 2024 at 09:48:33AM -0600, Gary Mills wrote: > install. I noticed the System menu now had an item called "Control > Center". In this country, we spell the second word "centre". This The above comes from desktop/mate/control-center package and is default in the C locale, so it seems okay for American English. Please see: https://github.com/mate-desktop/mate-control-center/blob/master/mate-control-center.pot#L4725 I assume you use the en_CA locale. For this locale the string in question is not "translated", see: https://github.com/mate-desktop/mate-control-center/blob/master/po/en_CA.po#L4717 so you see the default "untranslated" version of the string. If you want to see this fixed, then the best way would be either report this or maybe create a PR for the upstream mate-control-center project https://github.com/mate-desktop/mate-control-center or reach the en_CA translation team at https://www.transifex.com/mate/teams/13566/en_CA/ . The other possibility to have it fixed ASAP is to create a patch for our (OpenIndiana) desktop/mate/mate-control-center component at https://github.com/OpenIndiana/oi-userland and propose it as a PR. HTH. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mariadb always in maintenance mode
On Sun, Jan 21, 2024 at 03:09:15AM -0500, Christopher D. Bartels wrote: > I haven't found an error log in /var/log to peruse. Or any other clues > anywhere else for that matter. Either `svcs -x` or `svcs -L SERVICE` (where SERVICE is likely svc:/application/database/mariadb:version_106 in this case) will show you location of the service log. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] new be doesn't keep zfs settings
On Thu, Jan 18, 2024 at 01:22:42AM +0100, Goetz T. Fischer wrote: > On Wed, 17 Jan 2024 14:34:59 +0100, Marcel Telka wrote: > > On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote: > >> however, the catch was that the new be, that's created during a "pkg > >> update", doesn't keep the > >> compression setting. after the reboot i noticed that the new /var had > >> compression set to off again and > >> therefore was big again. is there something specific i have to do to make > >> the new be keep the zfs > >> settings? > > > > I'd expect this to work out of the box. Could you please share how > > exaclty this could be reproduced? > > sure, this is the pool of my test installation: > > rpool 5.63G 5.51G 124K /rpool > rpool/ROOT 5.03G 5.51G 96K legacy > rpool/ROOT/openindiana-2024:01:15 5.03G 5.51G 4.15G / > rpool/ROOT/openindiana-2024:01:15/var 905M 5.51G 905M /var > rpool/dump 64.1M 5.51G 64.1M - > rpool/export192K 5.51G 96K /export > rpool/export/home96K 5.51G 96K /export/home > rpool/swap 546M 6.03G 13.9M - > > then i run: > root@openindiana:~# zfs set compression=on > rpool/ROOT/openindiana-2024:01:15/var > root@openindiana:~# zfs get compression rpool/ROOT/openindiana-2024:01:15/var > NAME PROPERTY VALUE SOURCE > rpool/ROOT/openindiana-2024:01:15/var compression onlocal Even 'beadm create NEWBE' is enough to reproduce the issue (just tried). Feel free to file a bug report here: https://www.illumos.org/projects/illumos-gate/issues/new Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Tue, Jan 09, 2024 at 04:24:42PM +0100, Marcel Telka wrote: > I propose obsoletion of following 39 OpenIndiana packages: I'm happy to let you know that the list now contains 38 entries only. The media/mtx package is no longer on the list thanks to Carsten Grzemba and his work here: https://github.com/OpenIndiana/oi-userland/pull/15685 $ pkg list -afv media/mtx FMRI IFO pkg://openindiana.org/media/mtx@1.3.12-2024.0.0.0:20240118T153158Z i-- pkg://openindiana.org/media/mtx@1.3.11-2013.0.0.0:20151027T071736Z --- $ Thank you, Carsten. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] new be doesn't keep zfs settings
On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote: > however, the catch was that the new be, that's created during a "pkg update", > doesn't keep the > compression setting. after the reboot i noticed that the new /var had > compression set to off again and > therefore was big again. is there something specific i have to do to make the > new be keep the zfs > settings? I'd expect this to work out of the box. Could you please share how exaclty this could be reproduced? -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Question regarding: Obsolete perl/DBD-mysql
On Mon, Jan 15, 2024 at 05:08:59PM +0100, Predrag Zecevic via openindiana-discuss wrote: > why is this package (library/perl-5/dbd-mysql) obsoleted? > https://github.com/OpenIndiana/oi-userland/pull/14655 > > <https://github.com/OpenIndiana/oi-userland/pull/14655>There is no > explanation in description, so just wonder... I just added a comment there: https://github.com/OpenIndiana/oi-userland/pull/14655#issuecomment-1892473398 -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
On Fri, Jan 12, 2024 at 08:21:17AM -0600, Matthew R. Trower wrote: > > On 1/12/24 04:41, Marcel Telka wrote: > > On Fri, Jan 12, 2024 at 04:08:12AM -0600, Matthew R. Trower wrote: > > > /var/pkg/publisher is exactly what I thought it was. I am still not > > > clear as to whether the format is committed(stable) across different > > > versions of pkg5, and therefore safe to share across BEs. > > > > The man page says: Interface Stability: Uncommitted > > My understanding of the Interface Stability attribute is that it applies > to application programming interfaces (source and binary). I would not > expect it to necessarily apply to the data storage/caching layer of a > program, as I would not expect that to be considered an application Your expectation is wrong. Almost everything constitutes an interface. See also attributes(7). > interface layer. Furthermore, the Interface Stability attribute was > conceived back at Sun, and applied to their specific release strategy. > OI has diverged significantly from Sun's release schedules, > methodologies and motivations, so you'll have to forgive me if I don't > take the attribute as gospel these days. Sure, np. In that case you should consider everything as Volatile :-). See attributes(7). > I'm really just asking: how likely, these days, is /var/pkg/publisher to > change in breaking ways? I know from observation that it has changed at These days? Unlikely, because of the activity in the source repo at https://github.com/OpenIndiana/pkg5/commits/oi/ . > least once since OpenSolaris, but that could mean once ever, once a > year, once a month... it could be changing twice a week for all I really > know (okay, that's an exaggeration, but hopefully you get my point). > The people who actually do the bulk of the work on pkg5, are in a better > position to know this than I ever will be through trying to scour man > pages and source diffs. RTFM is fine and all, but sometimes it just > doesn't cut the mustard. > > Ultimately it's not that big of a deal, I guess. I was just hoping to > save some disk space instead of dragging around every package I've > downloaded since the beginning of time. But I've got new disks coming > in now anyway, so... meh. That really depeneds on your usage scenario. I run some systems almost always up-to-date with non-illumos-gate updates at least once a day and full updates (with reboot) every few days and here is an example: # du -sh /var/pkg/publisher/ 1.17G /var/pkg/publisher # and I do nothing special to keep it that way. This particular machine have almost all available packages installed. > > and no (because if such files have no relation to IPS then they > > won't appear there; but maybe you thinks about different kind of > > "relation" :-)) > > No relation as in "not under management". I doubt very much that pkg is > having those other kinds of relations :-) > > If I install my own /usr/bin/zsh, then later install pkg://shell/zsh > through pkg, pkg will take my old /usr/bin/zsh and chuck it in the > lost+found --- because that existing file has no relation to IPS (it was > not under its management). That is my interpretation of the man page, > anyway. Seems sensible. Yes. Sounds reasonable. > > I think yes (for example when you uninstall a package) > > If uninstalling a package places files in lost+found, then I'm well and > truly confused. To confuse you a bit more here is an example: # find /var/pkg/lost+found/ -type f # echo test > /usr/lib/python3.9/vendor-packages/pytest_randomly-3.15.0.dist-info/TEST # pkg uninstall pytest-randomly-39 pytest-randomly ... # find /var/pkg/lost+found/ -type f /var/pkg/lost+found/usr/lib/python3.9/vendor-packages/pytest_randomly-3.15.0.dist-info-20240112T154031Z/TEST # cat /var/pkg/lost+found/usr/lib/python3.9/vendor-packages/pytest_randomly-3.15.0.dist-info-20240112T154031Z/TEST test # -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
On Fri, Jan 12, 2024 at 04:08:12AM -0600, Matthew R. Trower wrote: > /var/pkg/publisher is exactly what I thought it was. I am still not clear > as to whether the format is committed(stable) across different versions of > pkg5, and therefore safe to share across BEs. The man page says: Interface Stability: Uncommitted > > /var/pkg/lost+found is... well, I still don't know. The language is... a > bit odd. I think it's saying that if I have files in my filesystem which > are not part of an IPS package, and pkg installs files in their place, those > original files will be moved here. However, are there other situations in > which files will be deposited here? Or will the files there only ever be my > files, which have no relation to IPS? It is exactly as it is stated in the man page. If I understand your questions properly then answers are: I think yes (for example when you uninstall a package); and no (because if such files have no relation to IPS then they won't appear there; but maybe you thinks about different kind of "relation" :-)). > In any event, I guess IPS doesn't care about them, and I should be free to > delete them if they are uninteresting to me. Yes, exactly. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
On Thu, Jan 11, 2024 at 11:16:21PM -0600, Matthew R. Trower wrote: > Is the format of /var/pkg/publisher committed at this point? It looks to > contain cached data and downloads from publishers, which ought not to be > tied to any particular BE. If I create a ZFS dataset to share that among > BEs, am I going to run into trouble? > > What exactly are the contents of /var/pkg/lost+found? Can any files I > discover in there be safely deleted? Please read the pkg(1) manpage to find some answers to your questions. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Wed, Jan 10, 2024 at 05:26:22PM -0600, Matthew R. Trower wrote: > On 1/10/24 03:33, Marcel Telka wrote: > > > Since nobody cared so far for many many years it looks obvious that > > these pacakges are abandoned, unused, rotted. > > That doesn't follow. I use vi daily, yet you could stop updating it for 20 > years and I wouldn't notice or care, so long as it was still distributed. > Great age does not necessarily mean a package is unused, or even necessarily > rotted. Another person has already said he uses mtx. Sure. You are right. This is understandable view of the situation from user's point of view. OTOH, developers see the situation a bit differently. This is exactly the reason why I posted the heads up to both openindiana-discuss@ (targetting users) and oi-dev@ (targetting developers). The aim was to let the users/developers know about the upcoming obsoletion and also to encourage somebody to do the real work and package the stuff they care about. It looks like the mission was successful :-). > I'll have a look at getting JEdit, dwdiff, ROXTerm and pen packaged up. > iozone is not GPL, but I can look at it as well. Great news! Thank you! -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Wed, Jan 10, 2024 at 12:05:08PM +0100, Carsten Grzemba via openindiana-discuss wrote: > Should we really remove all GPL licensed components? If we do not have build recipes in oi-userland and/or full sources (including possible patches) then very likely yes. But IANAL. > Sources and build recipes are public available. Upstream sources are available, but not sources (and build recipes) our packages were build from. > I use mtx and I would update the package. Please do so. Thank you. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
On Tue, Jan 09, 2024 at 04:08:13PM -0600, Matthew R. Trower wrote: > > All of them are: > > - very old - they are more than 10 years old > > - not maintained - we have no knowledge how to build them (there are > > no build recipes for them in oi-userland) > > - not needed - nothing in OpenIndiana depends on them > > I'm not very knowledgeable on how OI is packaged; how are they in the repos > currently if we can't build them? Did we inherit them in binary format in > the ON IPS repos or something? Without browsing to a lot of details the short answer is: yes. All these OpenIndiana packages (and also ca 60 more packages that are not on the list) are just binary blobs nobody knows for sure what exactly is there, what bugs they contain, what security vulnerabilities, or possibly malware, etc. If you or somebody else believe we should keep any of them then somebody needs to sit down and create build recipes for them. This needs labor and time somebody needs to invest. Since nobody cared so far for many many years it looks obvious that these pacakges are abandoned, unused, rotted. > I can say JEdit still works at a cursory glance. I don't use it very often > anymore, but I'm not sure why it should have to go if it isn't broken. Is > it causing you problems somehow? Our current jedit package is at version 4.3. This version was released upstream 14 years ago. Since 4.3 there were about 15 new releases upstream. The latest one is 5.6.0 released on September 2020. More info: https://sourceforge.net/projects/jedit The current jedit package is distributed (at least partly) under GPLv2. This means that OpenIndiana should provide sources and build recipes for the package. We do not have that, so it looks like we violate the license (IANAL). We should stop. > dwdiff appears to have source available > https://os.ghalkes.nl/dwdiff.html We are at 1.5.2 released upstream 15 years ago. The latest upstream is 2.1.4 released 3 years ago. License: GPLv3 (see above) > as does mtx > https://sourceforge.net/projects/mtx/ Our package is 1.3.11 released upstream 17 years ago. The latest is 1.3.12 released 15 years ago. License: GPLv2 (see above) > I wonder why we don't? Why we don't what? > For the CDE packages, we don't ship an entire CDE, right? So all they can do We do ship this: $ pkg list -a | grep '\' cde/calendar-manager-server 0.5.11-2013.0.0.0 --- cde/cde-runtime 0.5.11-2013.0.0.0 --- cde/cde-utilities 0.5.11-2013.0.0.0 --- cde/help-viewer 0.5.11-2013.0.0.0 --- consolidation/cde/cde-incorporation 0.5.11-2013.0.0.0 i-- $ I do not know how complete it is. > is support programs intended to run on/integrate with CDE, on machines that > don't actually have CDE installed... right? Furthermore, CDE is open source No idea. > these days. I don't know if current releases compile on OI, but it did at > least compile at one time (I use it as my DE, in fact), and at any rate If you are able to compile it, then you are welcome to contribute it to oi-userland. The git repo is here: https://github.com/OpenIndiana/oi-userland > ought to be able to be made to compile again. So, people ought to be able to > get a proper release of CDE if they desire one (though that may change if > enough of the wrong 32-bit libs disappear). Therefore, I would say CDE > packages probably constitute cruft and ought to be able to go. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] Heads-Up: Obsoletion of 39 old packages
On Tue, Jan 09, 2024 at 09:14:39AM -0800, Alan Coopersmith wrote: > https://lore.kernel.org/distributions/1ea25603-171c-062e-bc02-bcdfc3acd...@oracle.com/T/#u > is the advice I gave distros last year on unmaintained packages from X.Org. This is great info. It will allow us to start to work on obsoletion of few more packages, for example x11/library/libxevie. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] Heads-Up: Obsoletion of 39 old packages
On Tue, Jan 09, 2024 at 08:41:14AM -0800, Alan Coopersmith wrote: > On 1/9/24 07:24, Marcel Telka wrote: > > All of them are: > > - very old - they are more than 10 years old > > - not maintained - we have no knowledge how to build them (there are no > >build recipes for them in oi-userland) > > A fair number of them are actually impossible for you to maintain as we > never released the sources for them (things like the Solaris CDE & Motif > packages), and are likely just repackaging of the redistributable binaries > from OpenSolaris, complete with the bugs and security holes they had back > in 2010. > > A few are open source - for instance, I could point you to the sources for > x11/network/x11-network-proxies - but no one uses that in a world where > ssh X11-Forwarding is prevalent, which is why I removed that package from > Solaris and declared the upstream sources unmaintained and suggested that > distros remove them. Thanks for insights. This caused I looked closer at x11/network/rstart which is still required by mate_install and I noticed it is deprecated too, so I created https://github.com/OpenIndiana/oi-userland/pull/15571 . -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages
Hi, I propose obsoletion of following 39 OpenIndiana packages: pkg://openindiana.org/benchmark/iozone@3.323-2013.0.0.0 pkg://openindiana.org/cde/calendar-manager-server@0.5.11-2013.0.0.0 pkg://openindiana.org/cde/cde-runtime@0.5.11-2013.0.0.0 pkg://openindiana.org/cde/cde-utilities@0.5.11-2013.0.0.0 pkg://openindiana.org/cde/help-viewer@0.5.11-2013.0.0.0 pkg://openindiana.org/consolidation/dbtg/dbtg-incorporation@0.5.11-2013.0.0.0 pkg://openindiana.org/consolidation/jdmk/jdmk-incorporation@0.5.11-2013.0.0.0 pkg://openindiana.org/editor/jedit@4.3-2013.0.0.0 pkg://openindiana.org/library/java/activation@1.1.1-2013.0.0.0 pkg://openindiana.org/library/java/commons-collections@3.2.1-2013.0.0.0 pkg://openindiana.org/library/java/javadb@10.6.2.1-2013.0.0.0 pkg://openindiana.org/library/java/javamail@1.4.1-2013.0.0.0 pkg://openindiana.org/library/java/jdmk-runtime@0.5.11-2013.0.0.0 pkg://openindiana.org/library/java/jrexx@1.1.1-2013.0.0.0 pkg://openindiana.org/library/java/qdox@1.9-2013.0.0.0 pkg://openindiana.org/library/java/saaj@1.3.2-2013.0.0.0 pkg://openindiana.org/library/java/trove@2.0.4-2013.0.0.0 pkg://openindiana.org/library/libosip2@3.3.0-2013.0.0.0 pkg://openindiana.org/library/medialib@0.5.11-2013.0.0.0 pkg://openindiana.org/library/motif/libdpstkxm@0.5.11-2013.0.0.0 pkg://openindiana.org/library/tooltalk@0.5.11-2013.0.0.0 pkg://openindiana.org/media/mtx@1.3.11-2013.0.0.0 pkg://openindiana.org/service/network/load-balancer/pen@0.18.0-2013.0.0.0 pkg://openindiana.org/system/kernel/hardware-cursor@0.5.11-2013.0.0.0 pkg://openindiana.org/system/library/iconv/utf-8/manual@0.5.11-2013.0.0.0 pkg://openindiana.org/system/library/liblayout@0.5.11-2013.0.0.0 pkg://openindiana.org/system/locale/support/belarusian@0.1-2013.0.0.0 pkg://openindiana.org/system/locale/support/english@0.1-2013.0.0.0 pkg://openindiana.org/system/locale/support/sanskrit@0.1-2013.0.0.0 pkg://openindiana.org/system/storage/vdiskadm@0.5.11-2013.0.0.0 pkg://openindiana.org/system/test/sunvts@0.5.11-2013.0.0.0 pkg://openindiana.org/system/test/sunvts/manual@0.5.11-2013.0.0.0 pkg://openindiana.org/terminal/conman@0.2.4.1-2013.0.0.0 pkg://openindiana.org/terminal/roxterm@1.18.5-2013.0.0.0 pkg://openindiana.org/text/auto_ef@0.5.11-2013.0.0.0 pkg://openindiana.org/text/dwdiff@1.5.2-2013.0.0.0 pkg://openindiana.org/x11/library/dps@7.5-2013.0.0.0 pkg://openindiana.org/x11/library/libowconfig@0.5.11-2013.0.0.0 pkg://openindiana.org/x11/network/x11-network-proxies@7.5-2013.0.0.0 All of them are: - very old - they are more than 10 years old - not maintained - we have no knowledge how to build them (there are no build recipes for them in oi-userland) - not needed - nothing in OpenIndiana depends on them If you have a machine where any of them are installed I suggest to uninstall them ASAP to see if their absence affects you somehow. If I hear nothing in next few weeks I'll create a PR with obsoletion of these packages. Any questions? Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 12:13:48PM +0100, Goetz T. Fischer wrote: > sure, that's fine. if the package i selected for an update does require a > reboot then so be it. the idea > is just to avoid reboots for things i don't necessarily need to be up to date. > how much that would reduce reboots ... not sure, but maybe it would save some. Sure. It should somehow (and usually) work, modulo the userland-incorporation warning in my previous mail. So it is discouraged. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 11:52:25AM +0100, Goetz T. Fischer wrote: > no sorry, i wasn't clear. not one isolated package of course but whatever > "pkg update some_great_app" > triggers. No, you were clear. My "ssh only and nothing else" as an example was confusing. I meant ssh (and all tightly related pkgs that are needed to run ssh), as opposite to the full "pkg update" case. So my previous reply applies exactly to your case. For the ssh case (package network/ssh) you also need to account that the package depends on system/library and this means... see my other mail. In short if your system is older than 2023-12-22 then you cannot have latest network/ssh package. > the idea is to limit the updates to what i deem sensitive and whatever else > those updates drag in with > them is fine. reboots included because it would likely not be as often as > doing a full "pkg update" > everytime. > > On Mon, 8 Jan 2024 11:40:59 +0100, Marcel Telka wrote: > > e.g. update ssh only and nothing else -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:59:05AM +0100, Goetz T. Fischer wrote: > On Mon, 8 Jan 2024 10:49:37 +0100, Marcel Telka wrote: > > On Mon, Jan 08, 2024 at 10:27:32AM +0100, Goetz T. Fischer wrote: > >> which would mean pretty much every update needs a reboot. > > > > If you need to be always up-to-date. All the time and with all packages > > available then yes, you need to reboot once a day. > > hmm okay, i don't need that. if i would only use "pkg update" for specific > packages like for example > ssh, would pkg then fetch everything else that's required? yes, but ... see below > and would that way work permanently? Not sure what you mean by that. > or would i cripple the system after a while if i only update like that? Officially, there are incorporations to make sure your system is in known (and theoretically well tested) state. Mainly userland-incorporation. The userland-incorporation prevents you from most upgrades (or possibly downgrades) as you painted above. So if you want to do something like that (e.g. update ssh only and nothing else) then you need to deal with the userland-incorporation constraints somehow (for example by uninstalling the incorporation). But once you do that you could shot yourself in a foot if you really do not know what you are doing. So it is basically not recommended for general use. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:48:30AM +0100, Goetz T. Fischer wrote: > well, looking at their release notes > https://raw.githubusercontent.com/omniosorg/omnios-build/r151046/doc/ReleaseNotes.md > 1 reboot per month on average. that i can do with indiana as well. If you really need very long uptimes with being always up-to-date (reasonably, so without up-to-date illumos-gate bits) then you'll probably need to create your own fork of OpenIndiana (or OmnioOS, or whatever). Similarly as I do for our internal enterprise purposes. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:27:32AM +0100, Goetz T. Fischer wrote: > On Mon, 8 Jan 2024 10:03:47 +0100, Marcel Telka wrote: > > OTOH, system/library in OI (and also the rest of "kernel" - the > > illumos-gate) is rebuild once a day and almost all pacakges depends on > > them (either directly or indirectly). > > which would mean pretty much every update needs a reboot. If you need to be always up-to-date. All the time and with all packages available then yes, you need to reboot once a day. > how about --no-backup-be and/or --deny-new-be ? i can't try it right now > because i just updated my > system. That's orthogonal to the problem/question we are talking about here. In short, if you specify --deny-new-be you won't be able to upgrade any package that require reboot. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 08:56:30AM +0100, Goetz T. Fischer wrote: > of course but that raises the question why new libs would require a reboot. > the worst that could happen New libs does not require reboot on their own. The problem is with system/library only (and few other similar). The system/library package itself contains only few files that requires reboot (libc only). So with some effort we probably could make system/library usually upgradable without reboot (when libc is unchanged) but I think the bigger problem is that system/library depends on SUNWcs and SUNWcs contains 48 files that require reboot on update. And similar cascading dependencies makes the picture even more complex. > is that programs which depend on that lib would crash if they're restarted. > but if they're also updated, > then the next time they're restarted or just started it'll be fine. > let's say there's a new openssl so i simply copy the new one over the old > one, restart ssh and i'm good. > > similarly i can for example update rhel for months without a reboot and that > works. and i don't mean > live kernel patching. basically i only have to reboot for kernel stuff. but > for everything else i just > don't see a reason for all these reboots. To compare with rhel you should consider system/library similarly to their kernel-* packages. The main difference is that rhel's kernel packages are rebuild rarely AND almost no other package depends directly on them. OTOH, system/library in OI (and also the rest of "kernel" - the illumos-gate) is rebuild once a day and almost all pacakges depends on them (either directly or indirectly). So the current result is that if you want to stay up-to-date you need to reboot often. This is the fee we need to pay with the current way how OI Hipster is developed and built. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 06:21:31AM +0100, Andreas Wacknitz via openindiana-discuss wrote: > "pfexec pkg freeze osnet-incorporation" does mostly what you want. > It prohibits the update of packages that come from illumos-gate. > There are only few other packages (eg. NVIDIA drivers) from OI userland > that need a reboot. The only problem with this approach is that it will shortly prevent most updates since many newly built packages will require something from new illumos-gate (typically system/library[*]), but since you stay frozen at the older illumos-gate you won't be able to update affected packages. The above depends on frequency of the build server updates to new illumos-gate bits and reboots, which is currently often (roughly once a week, I think). [*] Currently ca 2000 packages out of 5200 require system/library and another ca 300 comes from illumos-gate (so you explicitly opted to not update them by frozing osnet-incorporation even they do not depend on system/library). So you have left only 2900 packages (or very likely even less because system/library is not the only package that comes from illumos-gate and is required by other packages) that you can safely update with frozen osnet-incorporation. Ca 1100 of them are Perl packages (library/perl-5/*) and ca 1300 are Python packages (library/python/*). So at the end of the day you can update only less than 500 non Perl, non Python packages when you run with frozen osnet-incorporation. This includes ca 60 packages with fonts, for example. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 32-bit libraries disappearing
On Sun, Jan 07, 2024 at 04:28:21PM -0600, Matthew R. Trower wrote: > > There are several types of software you can run on OpenIndiana: > > Respectfully, you seem to have misinterpreted my message. Ah, I'm sorry then. > I am not asking for support with my system; I can sort that out myself. I am > asking why these libraries have been removed, and why I see a general trend > of 32-bit library removal. The last I knew, the 32-bit kernel was dumped > and the userland binaries were being slowly migrated, but 32-bit libraries > were being preserved. What changed? Is it a simple matter of needing more > hands on deck (i.e. is this situation reversible with more help), or is > there some other factor? Is there previous discussion about this on the > mailing list that I can read? I'm not sure here. Somebody else should answer these your questions. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 32-bit libraries disappearing
On Sat, Jan 06, 2024 at 06:33:42PM -0600, Matthew R. Trower wrote: > mtrower@saturn:~$ conky > ld.so.1: conky: fatal: libcurl.so.4: open failed: No such file or directory > Killed There are several types of software you can run on OpenIndiana: 1. Software built by OpenIndiana maintainers and available via either openindiana.org or hipster-encumbered ips publishers. For such software OI maintainers aims to keep them fully working. If there is any issue with such software it could be considered as a bug. Any reports of issues here are welcome. Also help to solve such issues is welcome. 2. User compiled (either open source, or its own) software. For such software OI maintainers cannot provide any support because they simply do know nothing about such software. If such software works with OpenIndiana at one point in time, then user is just lucky, because _any_ change in OpenIndiana could break such software and OI maintainers have no way to notice. Such change could include: - library update (library name could change) - pacakge obsoletion - any file relocation or removal For such software there are only two viable ways to make sure the software works: - contribute it to oi-userland - maintain it yourself 3. 3rd party binary only software. For this software everything above in #2 applies, but there could be some exceptions for some special cases where OI maintainers decided to support such software with extra effort. Your 'conky' case falls under #2. There was recent discussion about support for SunRay software which would fall under #3. > root@saturn:/root# certutil -L -d /var/ldap > certutil: function failed: PR_LOAD_LIBRARY_ERROR: Failure to load dynamic > library > ld.so.1: certutil: fatal: relocation error: file > /usr/lib/mps/libsoftokn3.so: symbol sqlite3_temp_directory: referenced > symbol not found Thanks for the report. This falls under #1 above and _somebody_ needs to look at it and try to solve the problem. I think in this case just rebuild the system/mozilla-nss package 64-bit only should help. Is 64-bit certutil at /usr/sfw/bin/amd64/certutil working properly for you? HTH -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 32-bit libraries disappearing
On Sat, Jan 06, 2024 at 06:17:58AM -0600, Matthew R. Trower wrote: > Having updated my OI workstation after quite some time, I find myself with > quite a bit of breakage surrounding missing 32-bit libraries. For example, > libcurl and libcairo (among others) are shipping 64-bit libraries only, and > this breaks various third party software. For example? > More critically, libsqlite3 is > shipping 64-bit only, and this is breaking certutil(mozilla-nss), which > breaks ldapclient(!). Could you be more specific please how exactly is certutil broken? Thank you. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] argon2 missing
On Fri, Jan 05, 2024 at 07:04:39PM +0100, Goetz T. Fischer wrote: > # pkg verify argon2 > PACKAGE STATUS > pkg://openindiana.org/security/argon2ERROR > file: usr/bin/argon2 > ERROR: Missing: regular file does not exist > file: usr/lib/amd64/libargon2.so > ERROR: Missing: regular file does not exist > file: usr/include/argon2.h > ERROR: Missing: regular file does not exist > > a manual check confirmed that the files are indeed missing. This is problem on your local machine. To fix run `pkg fix argon2`. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] spam>Re: update ConsoleKit
On Fri, Dec 01, 2023 at 10:22:24AM +0100, Carsten Grzemba wrote: > It is also possible to check which packages comes from oi-userland and which > from illumos-gate? There are various ways how to find that info. For example: $ pkg contents -mr SUNWcs | grep ^set.*illumos-gate set name=illumos-gate.info.git-remote value=https://github.com/illumos/illumos-gate.git set name=illumos-gate.info.git-branch value=master set name=illumos-gate.info.git-rev value=d9e771569d5985de069c7db374affb027207ac43 $ pkg contents -mr runtime/perl-538 | grep ^set.*illumos-gate $ HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Fri, Dec 15, 2023 at 11:40:21AM +0100, Predrag Zečević via openindiana-discuss wrote: > Am I right when assuming that 'pkg update -vn' should NOT _download_ > packages? Those are not full packages, just their manifests. > > From 'man pkg': > -- >-n > >Perform a trial run of the operation with no package changes > made. > -- > > If answer is yes, then I will open ticket... > > Also I assume that I am allowed to remove any package manifest file under > /var/pkg/publisher/openindiana.org/pkg what is not installed? Likely, but I'm not sure. From what we know so far it looks like that /var/pkg/publisher/*/pkg is more like a cache... Then there is a question: What is difference between /var/pkg/cache/publisher/openindiana.org/pkg/ and /var/pkg/publisher/openindiana.org/pkg/ and what exactly is their purpose. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] /var/pkg/publisher (Was: Is it safe to remove /var/pkg/cache directory?)
On Thu, Dec 14, 2023 at 04:45:51PM +0100, Predrag Zečević via openindiana-discuss wrote: > Strange is this: > > :; pkg list | grep golang > developer/golang 1.21.1-2023.0.0.0 i-- > developer/golang-121 1.21.5-2023.0.0.0 i-- > > But: > :; ls -dlh /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang* > drwxr-xr-x 2 root root 9 Dec 13 19:36 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang > drwxr-xr-x 2 root root 4 Aug 23 2021 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang-115 > drwxr-xr-x 2 root root 4 Aug 25 2021 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang-116 > drwxr-xr-x 2 root root 3 Jun 19 15:21 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang-119 > drwxr-xr-x 2 root root 4 Oct 4 11:24 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang-120 > drwxr-xr-x 2 root root 5 Dec 14 12:47 > /var/pkg/publisher/openindiana.org/pkg/developer%2Fgolang-121 Apparently, in /var/pkg/publisher/* there are manifests stored. They are at various versions and even manifests for packages one do not have installed are stored there. I did a quick peek but I failed to find any documentation about /var/pkg/publisher/* content so it is unclear what manifests are expected to be there, but I'd expect only manifests for packages and versions that are installed on the system are there. In any case, somebody should try to find (either documentation or in pkg sources) what is supposed to be there. If it is clear there are some files leaking then we can start to look how to fix that. Any idea how it works on OmniOS? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Thu, Dec 14, 2023 at 11:37:52AM +0100, Aurélien Larcher wrote: > On Thu, Dec 14, 2023 at 10:38 AM Marcel Telka wrote: > > > On Thu, Dec 14, 2023 at 09:30:53AM +0100, Predrag Zečević wrote: > > > I understand network - there can be a lot of problems preventing fast > > > download, but *pkg* showing packages decreasing... > > > > Yes, it looks like a bug. Feel free to file a bugreport. > > > > > Also, is this OK (15GB of OI packages seems too much to me)? > > > > > > :; pfexec du -sh /var/pkg/publisher/* > > > 21M /var/pkg/publisher/hipster-encumbered > > > 15G /var/pkg/publisher/openindiana.org > > > > Not sure if it is okay or not. Here is mine: > > > > # du -sh /var/pkg/publisher/* > > 2.30M /var/pkg/publisher/hipster-encumbered > > 1019M /var/pkg/publisher/openindiana.org > > # > > > > I fully update usually at least once a week with a reboot (and new BE). > > This update includes bits from illumos-gate. I also update daily > > (without reboot) to have always up-to-date userland bits. I do have > > (almost) all packages installed. It is my oi and illumos build machine. > > > > I cannot remember which option it is but you can autopurge the cache after > successful install using a pkg property. It was already discussed. It is flush-content-cache-on-success. I'm not sure if /var/pkg/publisher/openindiana.org is considered as content-cache - see pkg(1) man page. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Thu, Dec 14, 2023 at 09:30:53AM +0100, Predrag Zečević wrote: > I understand network - there can be a lot of problems preventing fast > download, but *pkg* showing packages decreasing... Yes, it looks like a bug. Feel free to file a bugreport. > Also, is this OK (15GB of OI packages seems too much to me)? > > :; pfexec du -sh /var/pkg/publisher/* > 21M /var/pkg/publisher/hipster-encumbered > 15G /var/pkg/publisher/openindiana.org Not sure if it is okay or not. Here is mine: # du -sh /var/pkg/publisher/* 2.30M /var/pkg/publisher/hipster-encumbered 1019M /var/pkg/publisher/openindiana.org # I fully update usually at least once a week with a reboot (and new BE). This update includes bits from illumos-gate. I also update daily (without reboot) to have always up-to-date userland bits. I do have (almost) all packages installed. It is my oi and illumos build machine. HTH. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Wed, Dec 13, 2023 at 11:25:36PM +0100, Marcel Telka wrote: > On Wed, Dec 13, 2023 at 07:04:41PM +0100, Predrag Zečević wrote: > > :; pfexec du -sh /var/pkg/cache/publisher/* 4,0M > > /var/pkg/cache/publisher/hipster-encumbered 13G > > /var/pkg/cache/publisher/openindiana.org 1,0K > > /var/pkg/cache/publisher/userland > > I suggest to do: > > rm -rf /var/pkg/cache/publisher/hipster-encumbered Oops, 13G is apparently the size of openindiana.org, so it should read: rm -rf /var/pkg/cache/publisher/openindiana.org And the answer to the question in subject is: AFAIK, yes. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Python abstact socket and config printer applet.py
On Wed, Dec 13, 2023 at 06:24:17PM +0100, Carsten Grzemba via openindiana-discuss wrote: > I don't know when I have seen the last time the printer applet in mate-panel. The following link suggests that it does not work since version 1.5.16 of system-config-printer. https://github.com/OpenPrinting/system-config-printer/commit/0bec5b477b2e29dfa4b166ee12edcc065ddd8a7b -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Wed, Dec 13, 2023 at 07:04:41PM +0100, Predrag Zečević wrote: > :; pfexec du -sh /var/pkg/cache/publisher/* 4,0M > /var/pkg/cache/publisher/hipster-encumbered 13G > /var/pkg/cache/publisher/openindiana.org 1,0K > /var/pkg/cache/publisher/userland I suggest to do: rm -rf /var/pkg/cache/publisher/hipster-encumbered rm -rf /var/pkg/cache/publisher/userland and you are done. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Wed, Dec 13, 2023 at 04:39:51PM +0100, Predrag Zecevic wrote: > On 2023-12-13 16:33:28, Marcel Telka wrote: > > On Wed, Dec 13, 2023 at 04:30:27PM +0100, Predrag Zecevic wrote: > > > 13G /var/pkg/cache/publisher > > What is there? Does it match `pkg publisher` output? > > > > Yes, it matches: > :; pkg publisher > PUBLISHER TYPE STATUS P LOCATION > openindiana.org (non-sticky) origin online F > https://pkg.openindiana.org/hipster/ Just minor nit: unless you have some reason doing otherwise the above should not be non-sticky. > hipster-encumbered origin online F > https://pkg.openindiana.org/hipster-encumbered/ > > :; ls -dlh /var/pkg/publisher/* > drwxr-xr-x 7 root root 8 Dec 13 15:00 /var/pkg/publisher/hipster-encumbered > drwxr-xr-x 7 root root 8 Dec 13 15:00 /var/pkg/publisher/openindiana.org > drwxr-xr-x 3 root root 3 May 19 2021 /var/pkg/publisher/userland I was asking about /var/pkg/cache/publisher, not /var/pkg/publisher. Anyway, since you have no userland publisher you can remove the /var/pkg/publisher/userland directroy. I think the /var/pkg/cache directroy could be safely removed as a last resort. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Wed, Dec 13, 2023 at 04:30:27PM +0100, Predrag Zecevic wrote: > 13G /var/pkg/cache/publisher What is there? Does it match `pkg publisher` output? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
> > > On 13. Dec 2023, at 15:13, Predrag Zecevic > > > wrote: > > > :; du -sh /var/pkg/cache/ > > > 13G /var/pkg/cache/ How big is /var/pkg/cache/tmp ? -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] update ConsoleKit
On Thu, Nov 23, 2023 at 12:06:06PM +0100, Carsten Grzemba via openindiana-discuss wrote: > Does anyone knows which components really use this tools and would be > affected by this change (beside SunRay)? $ target/release/oi-pkg-checker check-fmri library/xdg/consolekit [INFO] fmri pkg:/library/xdg/consolekit is required by: [INFO] type: require, dependency: RUNTIME, package: pkg://openindiana.org/mate_install@1,5.11-2023.0.0.0:20231020T195142Z [INFO] type: incorporate, dependency: RUNTIME, package: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11,5.11-2023.0.0.2:20231119T212227Z [INFO] type: require, dependency: RUNTIME, package: pkg://openindiana.org/library/security/pam/module/pam-consolekit@0.4.1,5.11-2022.0.0.4:20220718T153347Z [INFO] type: require, dependency: RUNTIME, package: pkg://openindiana.org/system/display-manager/lightdm@1.30.0,5.11-2022.0.0.3:20220910T170257Z [INFO] component name: library/ConsoleKit $ PS: The tool is available here: https://github.com/aueam/oi-pkg-checker HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zone pkg broken
On Thu, Nov 16, 2023 at 09:18:39PM +0100, Goetz T. Fischer wrote: > more fun with zones. the zone's pkg seems broken: > > root@zone1:~# pkg publisher > Traceback (most recent call last): > File "/usr/bin/pkg", line 74, in > import six > ModuleNotFoundError: No module named 'six' > root@zone1:~# pkg search six > Traceback (most recent call last): > File "/usr/bin/pkg", line 74, in > import six > ModuleNotFoundError: No module named 'six' > > or the zone's python incomplete to be more precise. This is known problem. An attempt to solve the problem was made here: https://github.com/OpenIndiana/oi-userland/pull/14688 Technically the work there is no-op, so it didn't fix anything. Somebody should go and fix the problem in the pkg5 repo as noted here: https://github.com/OpenIndiana/oi-userland/pull/14688#issuecomment-1794555020 As a workaround you could try to install six into the zone. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] lost keyboard?
On Tue, Nov 14, 2023 at 07:25:00PM +0100, Quattro Porte via openindiana-discuss wrote: > Btw, I am running illumos-9fbdb45a98. If I pkg update it, OI cannot > see my USB keyboard any longer. There were some PCI related fixes and changes implemented in illumos-gate since 9fbdb45a98, but I found nothing specific that looks suspicious. You might try to update illumos bits only without rest of userland to see if the problem manifests that way to rule out userland bits. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] lost keyboard?
On Sat, Nov 11, 2023 at 10:29:10PM +0100, Quattro Porte via openindiana-discuss wrote: > just ran pkg update after a few weeks - it seems OI cannot recognise > my USB keyboard anymore. Tried different ports to no avail; no error > messages displayed either. Has anybody else had this issue? What the following command shows for you? pkg list | grep /nut/ -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Perl DBD::mysql will be obsoleted soon, use DBD::MariaDB
Hi all, After 10 years of DBD::mysql Perl module available in OpenIndiana we need to obsolete it. If you need similar functionality you should switch to DBD::MariaDB. The DBD::MariaDB Perl module is available in the library/perl-5/dbd-mariadb package. Starting with version 5.001 of DBD::mysql released on 2023-10-04 it is no longer possible to build it on OpenIndiana because MySQL 8.x is required for building. We do not have MySQL packaged for OpenIndiana. If DBD::mysql is a must for you and you cannot switch to DBD::MariaDB then you should contribute and package MySQL for OpenIndiana. Regards. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Scrub on single ZFS volume
On Mon, Oct 23, 2023 at 09:14:05AM +0100, Michelle wrote: > I'm having problems getting this question answered via the usual google > search, so I thought I'd ask here. I'm surprised google is unable to find the zpool man page available at https://illumos.org/man/8/zpool. Maybe you should try different search tool, or simply run `man zpool`? > The question is... how do I check the integrity of the data on the > single backup volume? zpool scrub > Does a scrub still make sense when there isn't any parity? Yes. >From the zpool man page: zpool scrub [-s | -p] pool... Begins a scrub or resumes a paused scrub. The scrub examines all data in the specified pools to verify that it checksums correctly. For replicated (mirror or raidz) devices, ZFS automatically repairs any damage discovered during the scrub. The zpool status command reports the progress of the scrub and summarizes the results of the scrub upon completion. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gccgo crashes
On Fri, Oct 20, 2023 at 09:19:11PM +0200, Goetz T. Fischer wrote: > i noticed another, minor issue along the way: > gccgo: fatal error: cannot execute > '/usr/gcc/12/lib/gcc/x86_64-pc-solaris2.11/12.3.0/go1': execv: > Permission denied Similar problem is with gcc-13 too. Both gcc-10 and gcc-11 look good. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gccgo crashes
On Fri, Oct 20, 2023 at 07:33:34PM +0200, Andreas Wacknitz wrote: > It's crashing for me, too. Hmm, strange. Is `env - /usr/gcc/10/bin/go env` crashing too? What `pmap core` shows? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gccgo crashes
On Fri, Oct 20, 2023 at 07:07:25PM +0200, Goetz T. Fischer wrote: > On Fri, 20 Oct 2023 15:41:06 +0200, Marcel Telka wrote: > > Could you please provide full repro steps? > > done already: > > On Fri, 20 Oct 2023 03:20:51 +0200, Goetz T. Fischer wrote: > > initial argv: /usr/gcc/10/bin/go env > ... > > even something as simple as "env" crashes Sorry, I'm unable to reproduce: $ /usr/gcc/10/bin/go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/marcel/.cache/go-build" GOENV="/home/marcel/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="solaris" GOINSECURE="" GONOPROXY="" GONOSUMDB="" GOOS="solaris" GOPATH="/home/marcel/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct; GOROOT="/usr/gcc/10" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0" GCCGO="/usr/gcc/10/bin/gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build677509705=/tmp/go-build -gno-record-gcc-switches -funwind-tables" $ echo $? 0 $ Is your system up-to-date? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gccgo crashes
On Fri, Oct 20, 2023 at 03:20:51AM +0200, Goetz T. Fischer wrote: > gccgo keeps crashing. following are the gcc10 results but the same > happened with gcc13. Could you please provide full repro steps? Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NVidia driver Lenovo P52
On Wed, Sep 06, 2023 at 12:55:53PM +0200, Olaf Bohlen wrote: > Aug 9 13:15:35 p52 nvidia_modeset: [ID 107833 kern.notice] Loading NVIDIA > Kernel Mode Setting Driver for UNIX platforms 470.182.03 Fri Feb 24 03:20:38 > UTC 2023 Try to update. The latest nvidia-470 driver in the repo is 470.199.02. HTH -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd has issues after upgraded to latest OI Hipster release today
On Sat, Jul 29, 2023 at 03:06:50PM +0100, russell wrote: > Jul 29 13:21:14 tesla ntpd[1283]: [ID 702911 ntp.error] > /jenkins/jobs/oi-userland/workspace/components/network/ntp/ntp-4.2.8p17/libntp/recvbuff.c:383: > REQUIRE(((void *)0) == pf->pptail || pptail == pf->pptail) failed This is an old and well known bug in ntp: https://bugs.ntp.org/show_bug.cgi?id=3552 -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On Thu, Jun 01, 2023 at 06:55:50AM +0200, Stephan Althaus wrote: > # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest > pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z > Retrieving packages for publisher openindiana.org ... > Retrieving and evaluating 1 package(s)... > pkgrecv: > pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z > Invalid content: manifest hash failure: fmri: > pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z > expected: e6571024d64e235a1ef19fd8557d028837118fec computed: > 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) > > I have tested the download on a different machine, same error. > > Maybe someone else can have a look at this? Confirmed. Same error here. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Ansible broken (after update to illumos-fcfad32eae)
On Thu, Apr 13, 2023 at 09:13:03AM +0200, Predrag Zečević via
openindiana-discuss wrote:
>
> On 4/13/23 08:12, Andreas Wacknitz wrote:
> > Am 13.04.23 um 07:47 schrieb Predrag Zečević via openindiana-discuss:
> > > After latest OI update:
> > >
> > > :; ansible --version
> > > ERROR: Ansible requires Jinja2 3.0 or newer on the controller. Current
> > > version: 2.11.3
> > >
> > > :; ls -la $(which ansible)
> > > lrwxrwxrwx 1 root root 11 Apr 12 23:10 /usr/bin/ansible -> ansible-3.9
> > >
> > > :; pkg list | grep -Ei "jinja|ansible"
> > > library/python/ansible 7.4.0-2023.0.0.0 i--
> > > library/python/ansible-core 2.14.4-2023.0.0.0 i--
> > > library/python/ansible-core-37 2.14.4-2023.0.0.0 i--
> > > library/python/ansible-core-39 2.14.4-2023.0.0.0 i--
> > > library/python/jinja2 3.1.2-2023.0.0.0 i--
> > > library/python/jinja2-37 3.1.2-2023.0.0.0 i--
> > > library/python/jinja2-39 3.1.2-2023.0.0.0 i--
> > > system/management/ansible 7.4.0-2023.0.0.0 i--
> > >
> > > Something is wrong, as my system provides Jinja2, version 3.1.2
> > >
> > > Any hints?
> > > Best regards
> > >
> > On my side everything is as expected, please create a new account an try
> > to use ansible with that. Maybe you have a broken configuration on your
> > account.
> >
> > Andreas
>
> Hi Andreas,
> thanks for hint, but it shows also same problem for new user account as
> well.
>
> I tried to truss ansible command, and then:
> :; grep -i jinja /tmp/ansible.truss
> 9937:
> open("/usr/lib/python3.9/site-packages/Jinja2-2.11.3.dist-info/METADATA",
> O_RDONLY|O_CLOEXEC) = 3
>
> Indeed:
> :; ls -hlad /usr/lib/python3.9/site-packages/{j,J}inja*
> drwxr-xr-x 3 root root 30 Feb 5 2021
> /usr/lib/python3.9/site-packages/jinja2
> drwxr-xr-x 2 root root 9 Feb 5 2021
> /usr/lib/python3.9/site-packages/Jinja2-2.11.3.dist-info
>
> :; pkg search -l
> /usr/lib/python3.9/site-packages/Jinja2-2.11.3.dist-info/METADATA
> [NO RESULT]
>
> There is also (not under site-packages, but vendor-packages):
> /usr/lib/python3.9/vendor-packages/Jinja2-3.1.2-py3.9.egg-info/PKG-INFO
>
> If I do this:
> :; pfexec mv /usr/lib/python3.9/site-packages/Jinja2-2.11.3.dist-info
> /var/tmp
>
> then it still shows wrong jinja2 version:
> :; ansible --version
> ansible [core 2.14.4]
> config file = None
> configured module search path =
> ['/export/home/predrag_zecevic/.ansible/plugins/modules',
> '/usr/share/ansible/plugins/modules']
> ansible python module location =
> /usr/lib/python3.9/vendor-packages/ansible
> ansible collection location =
> /export/home/predrag_zecevic/.ansible/collections:/usr/share/ansible/collections
> executable location = /usr/bin/ansible
> python version = 3.9.16 (main, Feb 19 2023, 15:42:40) [GCC 10.4.0]
> (/usr/bin/python3.9)
> jinja version = 2.11.3
> libyaml = True
>
> Seems that (due to many updates) I have some orphaned Jinja2 2.11.3
> settings. I am bit lost now.
The problem is that you installed Jinja2 via pip. This is not
recommended and should be avoided. Packages installed via pip takes
precedence over system packages. You should uninstall Jinja2 2.11.3
using pip.
In other words, your /usr/lib/python3.9/site-packages should contain
only files known to pkg. In ideal world the
/usr/lib/python3.9/site-packages directory should be (almost) empty, but
it is currently not (yet). If you need some Python package not provided
by OI pkg repo, please let me know and I'll try to package it.
Please also make sure that 'pip3.9 list --user' output is empty.
In short, running 'pip install' is unsupported and discouraged.
HTH.
--
+---+
| Marcel Telka e-mail: mar...@telka.sk |
|homepage: http://telka.sk/ |
+---+
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Proper invocation for zfs sharenfs
On Wed, Apr 12, 2023 at 03:19:04PM +0200, Till Wegmüller wrote: > I am currently trying to configure an NFS server but I seem to fail to > correctly invoke zfs sharenfs properly. > > zfs keeps complaining with 'cannot set property for 'rpool/data/oirepo': > 'sharenfs' cannot be set to invalid options' > > And a manual invokation of share keeps complaining with: 'Invalid protocol > specified: nfs' > > My command is: > ~# zfs set > sharenfs='rw=@10.1.0.70:@10.1.0.71:@10.1.0.72,ro=@10.1.0,root=@10.1.0.70:@10.1.0.71:@10.1.0.72,anon=abuild' > rpool/data/oirepo > > Does anybody know the correct invokation? Manpages etc. show that this > should be correct but I can't make it work. Do you have the service/file-system/nfs package installed? -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] update conflicts, what happened?
On Wed, Apr 12, 2023 at 10:05:38AM +0200, Udo Grabowski (IMK) wrote: > On 12/04/2023 07:16, Marcel Telka wrote: > > On Tue, Apr 11, 2023 at 07:33:32PM -0400, Richard L. Hamilton wrote: > > > root@openindiana:~# pkg update > > > Creating Plan (Checking for conflicting actions): / > > > pkg update: The following packages all deliver driver actions to nvidia: > > > > > > > > > pkg://openindiana.org/driver/graphics/nvidia@525.105.17,5.11-2023.0.0.0:20230331T112122Z > > > > > > pkg://openindiana.org/driver/graphics/nvidia-390@390.157,5.11-2022.0.0.0:20221123T085801Z > > > > > > These packages cannot be installed together. Any non-conflicting subset > > > of the above packages can be installed. > > > > We switched the default NVIDIA driver from nvidia-390 to nvidia > > recently. Since both nvidia-390 and nvidia packages cannot be installed > > together you need to manually uninstall nvidia-390 first (possibly with > > few other packages that depends on nvidia-390[*]) to get the system > > updated and then install nvidia package back (together with other > > packages you uninstalled previously). > > > > [*] I think the list includes these packages: mate_install, > > server_install, x11/server/xorg/driver/xorg-video. > > > > HTH. > > > > Since that is a real nuisance if you have an older graphics card that > depends on 390 availability: Is it possible to deliver the NVIDIA > package via a mediator ? > All of our cards are unsupported with 525.x. It is easy to stay with older nvidia driver (e.g. nvidia-390). Just uninstall mate_install and/or server_install and you should be able to upgrade your system while keeping older nvidia driver. Re mediator: no idea. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] update conflicts, what happened?
On Tue, Apr 11, 2023 at 07:33:32PM -0400, Richard L. Hamilton wrote: > root@openindiana:~# pkg update > Creating Plan (Checking for conflicting actions): / > pkg update: The following packages all deliver driver actions to nvidia: > > > pkg://openindiana.org/driver/graphics/nvidia@525.105.17,5.11-2023.0.0.0:20230331T112122Z > > pkg://openindiana.org/driver/graphics/nvidia-390@390.157,5.11-2022.0.0.0:20221123T085801Z > > These packages cannot be installed together. Any non-conflicting subset > of the above packages can be installed. We switched the default NVIDIA driver from nvidia-390 to nvidia recently. Since both nvidia-390 and nvidia packages cannot be installed together you need to manually uninstall nvidia-390 first (possibly with few other packages that depends on nvidia-390[*]) to get the system updated and then install nvidia package back (together with other packages you uninstalled previously). [*] I think the list includes these packages: mate_install, server_install, x11/server/xorg/driver/xorg-video. HTH. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Best way to install rsync
On Fri, Mar 31, 2023 at 03:43:10PM +0100, Michelle wrote: > I was wondering what would people recommend in order to get rsync onto > the installation please? pkg install rsync -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what do pkg install phases mean?
On Sun, Mar 05, 2023 at 09:59:05PM +0100, Till Wegmüller wrote:
> That will actually give you a different install result. Although as we are
The result would differ only in a case a new BE is needed (so usually only in a
case when you need to update packages from illumos-gate) and only in a case you
do the userland-incorporation incorrectly. Sorry, I forgot to mention that.
If you need to update userland components only (without a reboot) then both ways
will end with the same results.
To get as fast as possible userland update without reboot I do this (without
first and last steps, see below):
# pkg uninstall -v --deny-new-be --no-backup-be userland-incorporation entire
# pkg refresh
# ILLUMOS_VER="$(pkg list -H --no-refresh SUNWcs | awk '{print $2}' | sed -e
's/^.*-//g' -e 's/\./\\./g')"
# OUTPUT=$(pkg list -Hu --no-refresh | grep -v '^no packages have newer
versions available$' | grep -v "$ILLUMOS_VER")
# [[ -n "$OUTPUT" ]] && printf "Available updates (except
illumos-gate):\n%s\n\n" "$OUTPUT"
# [[ -n "$OUTPUT" ]] && printf "%s\n" "$OUTPUT" | awk '{print "/" $1}' | xargs
pkg update -v --no-refresh --deny-new-be --no-backup-be
# pkg install -v --no-refresh --deny-new-be --no-backup-be
userland-incorporation entire
Please note that if you always update all userland packages (everything except
illumos-gate packages, for example using above steps) then you can safely live
without the userland-incorporation installed.
OTOH, if you do the update using new BE, for example if you update everything
(including illumos-gate packages) or you simply force new BE creation using
--require-new-be, then I think the removal of the userland-incorporation prior
the update have not so visible impact (maybe no impact at all, I do not
remember).
HTH.
--
+---+
| Marcel Telka e-mail: mar...@telka.sk |
|homepage: http://telka.sk/ |
+---+
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what do pkg install phases mean?
On Sun, Mar 05, 2023 at 05:12:55PM +, Peter Tribble wrote: > It's unfortunate that the original aim of improving performance got lost > along the way. I found that with a slow machine and with a lot of packages installed it is usually faster (and requires less RAM) to uninstall userland-incorporation before the actual update, then do the update, and finally install userland-incorporation back. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] netbooting openindiana
On Sat, Mar 04, 2023 at 10:24:12PM +0100, Till Wegmüller wrote: > Due to limitations on how the install media are created at the this is not > possible. You would have to develop a media that can do that. Some work has > been done to allow supplying the media via NFS after booting the kernel but > it is undocumented and very beta. > > Contributions welcome. I can also help getting you started on that > development effort. The good news is that with this merged: https://github.com/OpenIndiana/slim_source/pull/72 the install image supports network booting OOTB. The only problem is that the latest available install image at https://www.openindiana.org/download/ was created before the above PR got merged. To make the netboot working you just need to mount the ISO image on your NFS server, share the mounted ISO via NFSv3 and configure your PXE server properly (see `man pxeboot`). Without the above PR merged you would additionally need to manually mount the install media once OpenIndiana boots over PXE using the following command: mount -o vers=3 NFSSERVER:ROOTPATH /.cdrom HTH. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] installing vlc
On Wed, Feb 15, 2023 at 09:26:54AM +, Apostolos Syropoulos via openindiana-discuss wrote: > root@emily:~# pkg set-publisher -P -g > http://pkg.openindiana.org/hipster-encumbered hipster-encumbered hipster-encumbered should be always searched after openindiana.org. The opposite order is not supported. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] how to re-install xorg-video and old nvidia driver after update?
On Thu, Jan 26, 2023 at 12:08:17AM -0600, Tim Mooney via openindiana-discuss wrote: > So, it looks like I need to somehow get back to the nvidia-390 driver. > Any suggestions on how to do that and still run a recent update? I could > go back to my April 2022 boot environment, but I would really like to get > my system up to date. pkg uninstall driver/graphics/nvidia pkg install driver/graphics/nvidia-390 HTH -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] cups does not work any more
On Thu, Jan 05, 2023 at 01:24:24PM +0100, Marc Lobelle wrote: > What should I do ? Load the core file into a debugger and try to root cause the problem. FYI, I'm running the same cups bits and it works okay here. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Automatic install
Hi, I would like to install OpenIndiana on few machines. To get the same (and easily reproducible) results I'd like to utilize some kind of automatic installation. Since AI (auto_install) was removed from OpenIndiana about 5 years back there seems to be no way to do the automatic OpenIndiana installation now. Any suggestion? Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] perl Term::ReadKey module question
Hi Predrag, On Thu, Dec 01, 2022 at 11:48:03AM +0100, Predrag Zečević via openindiana-discuss wrote: > We need update for our perl (add Term::ReadKey module) as suggested: > > :; /usr/mariadb/10.6/bin/mytop > Can't locate Term/ReadKey.pm in @INC (you may need to install the > Term::ReadKey module) (@INC contains: > /usr/perl5/site_perl/5.36/i86pc-solaris-thread-multi-64 > /usr/perl5/site_perl/5.36 > /usr/perl5/vendor_perl/5.36/i86pc-solaris-thread-multi-64 > /usr/perl5/vendor_perl/5.36 > /usr/perl5/5.36/lib/i86pc-solaris-thread-multi-64 /usr/perl5/5.36/lib) at > /usr/mariadb/10.6/bin/mytop line 203. Mmmmkay, I ran this for you: $ git checkout -b perl/TermReadKey $ WS_TOOLS=$(git rev-parse --show-toplevel)/tools $ $WS_TOOLS/perl-integrate-module Term::ReadKey WARNING: No license file found WARNING: No copyright notice found at standard locations WARNING: No copyright notice found $ git show $ git push $ ... and here is the result: https://github.com/OpenIndiana/oi-userland/pull/10094 Regards. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem updating openindiana
On Fri, Nov 18, 2022 at 12:43:56PM +0100, Marc Lobelle wrote: > The two nvidia packages are obviously conflicting. > > Can this be solved ? Yes, please read https://www.illumos.org/issues/15161#note-5 -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia 515 problem
On Wed, Nov 09, 2022 at 11:22:01AM +0100, Udo Grabowski (IMK) wrote: > > > On 09/11/2022 10:21, Stephan Althaus wrote: > > On 11/9/22 10:15, Marcel Telka wrote: > > > On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote: > > > > Hello! > > > > > > > > Yesterday i tried to use nvidia driver version 515 with my M1200M, > > > > but got an error in the Xorg.0.log: > > > > > > > > > > > > [ 234.097] (II) Loading sub module "glxserver_nvidia" > > > > [ 234.097] (II) LoadModule: "glxserver_nvidia" > > > > [ 234.098] (WW) Warning, couldn't open module glxserver_nvidia > > > > [ 234.098] (II) UnloadModule: "glxserver_nvidia" > > > > [ 234.098] (II) Unloading glxserver_nvidia > > > > [ 234.098] (EE) NVIDIA: Failed to load module > > > > "glxserver_nvidia" (module > > > > does not exist, 0) > > > > [ 234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please > > > > check in your X > > > > [ 234.098] (EE) NVIDIA(0): log file that the GLX module has been > > > > loaded in your X > > > > [ 234.098] (EE) NVIDIA(0): server, and that the module is > > > > the NVIDIA > > > > GLX module. If > > > > [ 234.098] (EE) NVIDIA(0): you continue to encounter > > > > problems, Please > > > > try > > > > [ 234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver. > > > > [ 234.098] (II) NVIDIA: The X server does not support PRIME Render > > > > Offload. > > > > [ 234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA > > > > graphics > > > > device! > > > > [ 234.098] (EE) NVIDIA(0): Failing initialization of X screen > > > > [ 234.098] (II) UnloadModule: "nvidia" > > > > > > > > i do not find glxserver_nvidia in the running version 470: > > > > > > > > $ grep -i glx /var/log/Xorg.0.log > > > > [ 90.930] (II) LoadModule: "glx" > > > > [ 90.932] (II) Loading > > > > /usr/lib/xorg/modules/extensions/amd64/libglx.so > > > > [ 90.986] (II) Module glx: vendor="NVIDIA Corporation" > > > > [ 90.986] (II) NVIDIA GLX Module 470.141.03 Thu Jun 30 18:38:53 UTC > > > > 2022 > > > > [ 93.742] (II) Initializing extension GLX > > > > [ 93.742] (II) Indirect GLX disabled. > > > > > > > > Does anyone has a hint on how to solve this? > > > There is no '*glxserver_nvidia*' file in the Solaris driver distribution > > > https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run > > > so I'm not sure why they expect such file (module) to exist. Maybe this > > > is a bug in their package? Either they forgot to add the module into > > > the package, or they mistakenly require it when they shouldn't? Maybe > > > you could try to contact NVIDIA. > > > > > > > > > Regards. > > > > > Hello! > > > > Looking a bit around i think its the GLX module that is not "NVIDIA" > > > > [ 234.053] (II) LoadModule: "glx" > > [ 234.055] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so > > [ 234.071] (II) Module glx: vendor="X.Org Foundation" > > [ 234.071] compiled for 1.19.7, module version = 1.0.0 > > [ 234.071] ABI class: X.Org Server Extension, version 10.0 > > > > and the glxserver is a method within that or something similar.. > > ... > > # nm -D > NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep > -i glx > > [6] |14550384| 24|OBJT |GLOB |0|22 > |glxserver_nvidiaModuleData > > That entrypoint is not present in , e.g., 295.40 . So probably a > packaging error by NVIDIA. I thought initially the same, but: $ /usr/bin/nm -D nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1: [55]|10124656| 35|FUNC |GLOB |0|12 |__glXNvHandShake [60] | 14546160| 24|OBJT |GLOB |0|22 |glxModuleData [7] |14546032| 24|OBJT |GLOB |0|22 |glxserver_nvidiaModuleData $ /usr/bin/nm -D nvidia/NVIDIA-Solari
Re: [OpenIndiana-discuss] Nvidia 515 problem
On Wed, Nov 09, 2022 at 10:36:52AM +0100, Marcel Telka wrote: > On Wed, Nov 09, 2022 at 10:21:16AM +0100, Stephan Althaus wrote: > > On 11/9/22 10:15, Marcel Telka wrote: > > > On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote: > > > > Yesterday i tried to use nvidia driver version 515 with my M1200M, > > > > but got an error in the Xorg.0.log: > > > > > > > > > > > > [ 234.097] (II) Loading sub module "glxserver_nvidia" > > > > [ 234.097] (II) LoadModule: "glxserver_nvidia" > > > > [ 234.098] (WW) Warning, couldn't open module glxserver_nvidia > > > > [ 234.098] (II) UnloadModule: "glxserver_nvidia" > > > > [ 234.098] (II) Unloading glxserver_nvidia > > > > [ 234.098] (EE) NVIDIA: Failed to load module "glxserver_nvidia" > > > > (module > > > > does not exist, 0) > > > > [ 234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please > > > > check in your X > > > > [ 234.098] (EE) NVIDIA(0): log file that the GLX module has been > > > > loaded in your X > > > > [ 234.098] (EE) NVIDIA(0): server, and that the module is the > > > > NVIDIA > > > > GLX module. If > > > > [ 234.098] (EE) NVIDIA(0): you continue to encounter problems, > > > > Please > > > > try > > > > [ 234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver. > > > > [ 234.098] (II) NVIDIA: The X server does not support PRIME Render > > > > Offload. > > > > [ 234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA > > > > graphics > > > > device! > > > > [ 234.098] (EE) NVIDIA(0): Failing initialization of X screen > > > > [ 234.098] (II) UnloadModule: "nvidia" > > > > > > > > i do not find glxserver_nvidia in the running version 470: > > > > > > > > $ grep -i glx /var/log/Xorg.0.log > > > > [ 90.930] (II) LoadModule: "glx" > > > > [ 90.932] (II) Loading > > > > /usr/lib/xorg/modules/extensions/amd64/libglx.so > > > > [ 90.986] (II) Module glx: vendor="NVIDIA Corporation" > > > > [ 90.986] (II) NVIDIA GLX Module 470.141.03 Thu Jun 30 18:38:53 UTC > > > > 2022 > > > > [ 93.742] (II) Initializing extension GLX > > > > [ 93.742] (II) Indirect GLX disabled. > > > > > > > > Does anyone has a hint on how to solve this? > > > There is no '*glxserver_nvidia*' file in the Solaris driver distribution > > > https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run > > > so I'm not sure why they expect such file (module) to exist. Maybe this > > > is a bug in their package? Either they forgot to add the module into > > > the package, or they mistakenly require it when they shouldn't? Maybe > > > you could try to contact NVIDIA. > > Looking a bit around i think its the GLX module that is not "NVIDIA" > > > > [ 234.053] (II) LoadModule: "glx" > > [ 234.055] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so > > [ 234.071] (II) Module glx: vendor="X.Org Foundation" > > [ 234.071] compiled for 1.19.7, module version = 1.0.0 > > [ 234.071] ABI class: X.Org Server Extension, version 10.0 > > Is the log with nvidia-470 (470.141.3) or nvidia (515.76)? > > If it is with nvidia-470, and if for nvidia 515.76 the > /usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so is loaded > instead, then that would explain why they need glxserver_nvidia. > > > and the glxserver is a method within that or something similar.. > > > > How to configure Xorg to use a different path for the GLX module is the next > > question to solve.. > > As a quick test you could try to remove > /usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so and see what > happens. If it solves the problem we could remove it from package. Ah, Udo is right. Please ignore what I said above. Almost all libglx.so are just symlinks, not real files. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia 515 problem
On Wed, Nov 09, 2022 at 10:21:16AM +0100, Stephan Althaus wrote: > On 11/9/22 10:15, Marcel Telka wrote: > > On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote: > > > Yesterday i tried to use nvidia driver version 515 with my M1200M, > > > but got an error in the Xorg.0.log: > > > > > > > > > [ 234.097] (II) Loading sub module "glxserver_nvidia" > > > [ 234.097] (II) LoadModule: "glxserver_nvidia" > > > [ 234.098] (WW) Warning, couldn't open module glxserver_nvidia > > > [ 234.098] (II) UnloadModule: "glxserver_nvidia" > > > [ 234.098] (II) Unloading glxserver_nvidia > > > [ 234.098] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module > > > does not exist, 0) > > > [ 234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please > > > check in your X > > > [ 234.098] (EE) NVIDIA(0): log file that the GLX module has been > > > loaded in your X > > > [ 234.098] (EE) NVIDIA(0): server, and that the module is the NVIDIA > > > GLX module. If > > > [ 234.098] (EE) NVIDIA(0): you continue to encounter problems, > > > Please > > > try > > > [ 234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver. > > > [ 234.098] (II) NVIDIA: The X server does not support PRIME Render > > > Offload. > > > [ 234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics > > > device! > > > [ 234.098] (EE) NVIDIA(0): Failing initialization of X screen > > > [ 234.098] (II) UnloadModule: "nvidia" > > > > > > i do not find glxserver_nvidia in the running version 470: > > > > > > $ grep -i glx /var/log/Xorg.0.log > > > [ 90.930] (II) LoadModule: "glx" > > > [ 90.932] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so > > > [ 90.986] (II) Module glx: vendor="NVIDIA Corporation" > > > [ 90.986] (II) NVIDIA GLX Module 470.141.03 Thu Jun 30 18:38:53 UTC > > > 2022 > > > [ 93.742] (II) Initializing extension GLX > > > [ 93.742] (II) Indirect GLX disabled. > > > > > > Does anyone has a hint on how to solve this? > > There is no '*glxserver_nvidia*' file in the Solaris driver distribution > > https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run > > so I'm not sure why they expect such file (module) to exist. Maybe this > > is a bug in their package? Either they forgot to add the module into > > the package, or they mistakenly require it when they shouldn't? Maybe > > you could try to contact NVIDIA. > Looking a bit around i think its the GLX module that is not "NVIDIA" > > [ 234.053] (II) LoadModule: "glx" > [ 234.055] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so > [ 234.071] (II) Module glx: vendor="X.Org Foundation" > [ 234.071] compiled for 1.19.7, module version = 1.0.0 > [ 234.071] ABI class: X.Org Server Extension, version 10.0 Is the log with nvidia-470 (470.141.3) or nvidia (515.76)? If it is with nvidia-470, and if for nvidia 515.76 the /usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so is loaded instead, then that would explain why they need glxserver_nvidia. > and the glxserver is a method within that or something similar.. > > How to configure Xorg to use a different path for the GLX module is the next > question to solve.. As a quick test you could try to remove /usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so and see what happens. If it solves the problem we could remove it from package. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia 515 problem
On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote: > Hello! > > Yesterday i tried to use nvidia driver version 515 with my M1200M, > but got an error in the Xorg.0.log: > > > [ 234.097] (II) Loading sub module "glxserver_nvidia" > [ 234.097] (II) LoadModule: "glxserver_nvidia" > [ 234.098] (WW) Warning, couldn't open module glxserver_nvidia > [ 234.098] (II) UnloadModule: "glxserver_nvidia" > [ 234.098] (II) Unloading glxserver_nvidia > [ 234.098] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module > does not exist, 0) > [ 234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please > check in your X > [ 234.098] (EE) NVIDIA(0): log file that the GLX module has been > loaded in your X > [ 234.098] (EE) NVIDIA(0): server, and that the module is the NVIDIA > GLX module. If > [ 234.098] (EE) NVIDIA(0): you continue to encounter problems, Please > try > [ 234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver. > [ 234.098] (II) NVIDIA: The X server does not support PRIME Render > Offload. > [ 234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics > device! > [ 234.098] (EE) NVIDIA(0): Failing initialization of X screen > [ 234.098] (II) UnloadModule: "nvidia" > > i do not find glxserver_nvidia in the running version 470: > > $ grep -i glx /var/log/Xorg.0.log > [ 90.930] (II) LoadModule: "glx" > [ 90.932] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so > [ 90.986] (II) Module glx: vendor="NVIDIA Corporation" > [ 90.986] (II) NVIDIA GLX Module 470.141.03 Thu Jun 30 18:38:53 UTC > 2022 > [ 93.742] (II) Initializing extension GLX > [ 93.742] (II) Indirect GLX disabled. > > Does anyone has a hint on how to solve this? There is no '*glxserver_nvidia*' file in the Solaris driver distribution https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run so I'm not sure why they expect such file (module) to exist. Maybe this is a bug in their package? Either they forgot to add the module into the package, or they mistakenly require it when they shouldn't? Maybe you could try to contact NVIDIA. Regards. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken
On Thu, Oct 06, 2022 at 11:43:29AM +0200, Stephan Althaus wrote: > On 10/6/22 11:36, Marcel Telka wrote: > > On Thu, Oct 06, 2022 at 10:20:45AM +0200, Predrag Zečević via > > openindiana-discuss wrote: > > > I would try: > > > > > > :; pfexec pkg refresh --full > > > :; pfexec pkg rebiuld-index > > Maybe rebuild-index would work better than rebiuld-index. :-) > > > You're right of course :-) > > pfexec pkg refresh --full > throws the problem. > Did you try it? Yes, pkg refresh does not work (hipster-encumbered publisher works okay): # pkg refresh openindiana.org pkg: 0/1 catalogs successfully updated: 1: Invalid contentpath /var/pkg/cache/incoming-23873/update.20221006T06Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-23873/update.20221006T06Z.C' catalog file is not valid.. (happened 4 times) 2: Invalid contentpath /var/pkg/cache/incoming-23873/update.20221006T07Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-23873/update.20221006T07Z.C' catalog file is not valid.. (happened 4 times) # Also these commands does not work: # pkg list -a pkg: 1/2 catalogs successfully updated: 1: Invalid contentpath /var/pkg/cache/incoming-24526/update.20221006T06Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-24526/update.20221006T06Z.C' catalog file is not valid.. (happened 4 times) 2: Invalid contentpath /var/pkg/cache/incoming-24526/update.20221006T07Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-24526/update.20221006T07Z.C' catalog file is not valid.. (happened 4 times) # pkg list -u pkg: 1/2 catalogs successfully updated: 1: Invalid contentpath /var/pkg/cache/incoming-24712/update.20221006T06Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-24712/update.20221006T06Z.C' catalog file is not valid.. (happened 4 times) 2: Invalid contentpath /var/pkg/cache/incoming-24712/update.20221006T07Z.C: CatalogPart failed validation: The signature data for the '/var/pkg/cache/incoming-24712/update.20221006T07Z.C' catalog file is not valid.. (happened 4 times) # It is anything that needs access to full packages list. Commands that does not need full package list works: # pkg list | head NAME (PUBLISHER) VERSIONIFO SUNWcs0.5.11-2022.0.0.21255 i-- SUNWcsd 0.5.11-2022.0.0.21255 i-- antivirus/c_icap 0.5.10-2022.0.0.0 i-- antivirus/c_icap_modules 0.5.5-2022.0.0.0 i-- antivirus/clamav 0.105.1-2022.0.0.1 i-- antivirus/clamav-clamdtop 0.105.1-2022.0.0.1 i-- antivirus/clamav-common 0.105.1-2022.0.0.1 i-- antivirus/clamav-core 0.105.1-2022.0.0.1 i-- antivirus/clamav-milter 0.105.1-2022.0.0.1 i-- # So apparently the openindiana.org repo/publisher is broken at pkg.openindiana.org. Regards. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken
On Thu, Oct 06, 2022 at 10:20:45AM +0200, Predrag Zečević via openindiana-discuss wrote: > I would try: > > :; pfexec pkg refresh --full > :; pfexec pkg rebiuld-index Maybe rebuild-index would work better than rebiuld-index. :-) -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
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. Regards. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] mkdocs 1.4 op OpenIndiana
On Sun, Oct 02, 2022 at 05:13:23PM +0200, Marcel Telka wrote:
> On Sun, Oct 02, 2022 at 05:04:36PM +0200, s...@pandora.be wrote:
> > but the theme error can be solved by:
> >
> > # pip install mkdocs-bootswatch
>
> ...
>
> > or somebody could try to package mkdocs for Python 3.9 in IPS oi-userland.
>
> I'm working on it:
> https://openindiana.org/pipermail/oi-dev/2022-September/033266.html
>
> I'll add both mkdocs and mkdocs-bootswatch. Both at latest versions.
All mkdocs packages are back and updated to their latest versions:
# pkg list library/python/mkdocs{,-bootstrap,-bootswatch}
NAME (PUBLISHER) VERSIONIFO
library/python/mkdocs 1.4.0-2022.0.0.1 i--
library/python/mkdocs-bootstrap 1.1-2022.0.0.0 i--
library/python/mkdocs-bootswatch 1.1-2022.0.0.0 i--
#
Please try and let me know if you find any problem.
Thanks.
--
+-------+
| Marcel Telka e-mail: mar...@telka.sk |
|homepage: http://telka.sk/ |
+---+
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] borg missing msgpack dependency?
On Fri, Sep 30, 2022 at 11:18:54PM +1000, Carl Brewer wrote: > I'd love to send a PR, where's how to do it documented? Just look at https://github.com/OpenIndiana/oi-userland and create usual github PR there. HTH. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] mkdocs 1.4 op OpenIndiana
On Sun, Oct 02, 2022 at 05:04:36PM +0200, s...@pandora.be wrote: > but the theme error can be solved by: > > # pip install mkdocs-bootswatch ... > or somebody could try to package mkdocs for Python 3.9 in IPS oi-userland. I'm working on it: https://openindiana.org/pipermail/oi-dev/2022-September/033266.html I'll add both mkdocs and mkdocs-bootswatch. Both at latest versions. Thanks. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 06:46:40PM +0200, s...@pandora.be wrote: > > > Based on the rule above we already obsoleted following packages > > recently: > > > ... > > library/python/mkdocs > ... > > see http://docs.openindiana.org/contrib/getting-started/ > > that page says for installing mkdocs: > > "For OpenIndiana Hipster, MKDocs and all of it's dependencies have been > packaged and are available in the OI Hipster repository. So, if you're > already running Hipster, installing MKDocs is as simple as: pkg install > mkdocs" Okay, I'll add mkdocs back. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 04:36:15PM +0200, Aurélien Larcher wrote: > On Thu, Sep 29, 2022 at 4:30 PM Marcel Telka wrote: > > > On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote: > > > We could define some rules or information depending on the nature of the > > > package to mark which dependencies are expected. > > > Some python modules have been added for the sake of resolving a > > dependency > > > while others have no consumer in userland but are expected to be > > installed > > > as "standalone" and consumed by users directly. > > > > > > Also I am not sure I understood which type of dependencies are considered > > > here: > > > - resolved within userland either directly or added explicitly in the > > > manifest > > > - build requirements > > > - dependencies detected by pipdeptree (which are a superset of what > > > pkg/userland detects) > > > > > > I just want to make sure that we do not miss some border effects. > > > > Okay, I'll stop to obsolete more python related packages and leave it as > > it is for now so everybody have a chance to add back packages that were > > obsoleted, but they are needed for any reason. > > > > I am not asking you to stop anything at all, I am just asking questions to > understand if this will not bite us back at some point. I won't obsolete any package from the list below until end of October 2022. If I see no PR trying to rebuild them to support python 3.7+ till end of October 2022, then I might propose to obsolete them. library/python/backport_abc library/python/backports.functools_lru_cache library/python/backports.ssl_match_hostname library/python/colorama library/python/decorator library/python/enum library/python/flamegraph library/python/funcsigs library/python/ipaddress library/python/ipython library/python/ipython_genutils library/python/notify2 library/python/pickleshare library/python/prompt-toolkit library/python/pyatspi2 library/python/pycups library/python/pygobject library/python/pygtk2 library/python/python-compizconfig library/python/python-xdg library/python/python-xlib library/python/rbtools library/python/simplegeneric library/python/traitlets Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 04:36:15PM +0200, Aurélien Larcher wrote: > At least maybe some indications on how to add the packages back and make > sure there is no mistake or loss of consistency with the location/naming > etc.. If anybody wants to re-add some obsoleted package back, or rebuild some package to support python 3.7/3.9 properly and have some questions, issues, problems, etc. feel free to ask me. I'll try to help. Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote: > We could define some rules or information depending on the nature of the > package to mark which dependencies are expected. > Some python modules have been added for the sake of resolving a dependency > while others have no consumer in userland but are expected to be installed > as "standalone" and consumed by users directly. > > Also I am not sure I understood which type of dependencies are considered > here: > - resolved within userland either directly or added explicitly in the > manifest > - build requirements > - dependencies detected by pipdeptree (which are a superset of what > pkg/userland detects) > > I just want to make sure that we do not miss some border effects. Okay, I'll stop to obsolete more python related packages and leave it as it is for now so everybody have a chance to add back packages that were obsoleted, but they are needed for any reason. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 03:18:29PM +0200, Aurélien Larcher wrote: > I do not understand the need for obsoleting the entire package and removing > all the files instead of updating on the go. > > Could you explain the motivation? There is no particular need. It is just simpler to obsolete than to update. And since there is no known consumer, then the obsoletion is the obvious option chosen. > To me this seems a bit of overhead, like removing the mkdocs, cython, numpy > packages completely from the tree instead of updating them. Feel free to create PRs to get them back. > We therefore lose track of what was in the tree and people may start from > scratch all over again. > > Maybe you intend to provide some level of automation later? Maybe. If I find it easy to do I'll do so, but I've no immediate plan to do so. > An earlier heads-up before starting to remove everything could have been > nice to have a chance to update a few components in advance and avoid the > mumbo-jumbo. Sorry. I try to do my best. Nothing is perfect. Anyway, an earlier update/rebuild of those packages for non-EOLed python would be nice from you before you left them fall out of support and be surprised that they are disappearing. Sorry, talking is easy. Thank you. -- +-------+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] FLAG-DAY: We started to obsolete python 2.7 and 3.5
Hi, Currently we provide Python versions 2.7, 3.5, 3.7, and 3.9 for OpenIndiana, while version 3.9 is the default version. Both Python 2.7 and 3.5 are no longer supported for two or almost three years now respectively - see https://devguide.python.org/versions/#versions for details, so we started to obsolete them. Since there are many related packages that needs to be rebuilt to get python 2.7 and 3.5 obsoleted, this transition is expected to take long time (probably weeks, maybe months). There are basically two sets of related packages: #1 software that uses python (e.g. gimp), and #2 packages that provide some enhancement to python; these are usually python modules, for example cherrypy. For #1 we just need to rebuild packages that require python 2.7 or 3.5 so they start to require either python 3.7, or python 3.9. Volunteers are welcome! For #2 the situation is a bit more complex. The name of all packages in this set is starting with 'library/python'. There is usually a basic package (e.g. library/python/cherrypy) and few version specific packages (e.g. library/python/cherrypy-35, library/python/cherrypy-37, library/python/cherrypy-39). Another example is library/python/pycups and its library/python/pycups-27 and library/python/pycups-35. For such packages we will slowly obsolete their -27 and -35 variants. In a case there is neither -37 nor -39 variant already available, nor it is needed for some other package, we will end up with all package variants obsoleted. If this happens, then in addition to obsolete of both -27 and -35 we will obsolete the base package too. For example, cherrypy. There are already -35, -37, and -39 variants. We will obsolete the -35 variant and both -37 and -39 will be kept, so we will keep the basic library/python/cherrypy too. When looking at pycups, we will obsolete both -27 and -35 variants. Let's assume there is currently no other package that needs pycups, so we would end with orphaned library/python/pycups, so we will obsolete the library/python/pycups package too. Based on the rule above we already obsoleted following packages recently: library/python/augeas library/python/backports.shutil_get_terminal_size library/python/backports.tempfile library/python/cheetah library/python/click library/python/cssutils library/python/cython library/python/dulwich library/python/geoip library/python/elixir library/python/import-profiler library/python/kafka-python library/python/livereload library/python/m2crypto library/python/mkdocs-bootstrap library/python/mkdocs-bootswatch library/python/mkdocs library/python/netaddr library/python/netifaces library/python/numpy library/python/pygtksourceview library/python/pymongo library/python/pyorbit library/python/pyrex library/python/pyro library/python/python-ldap library/python/python-memcached library/python/python-mysql library/python/python-notify library/python/python-sexy library/python/pywbem library/python/scientific-py library/python/sqlalchemy library/python/typing library/python/unittest2 Here is a list of packages that could get possibly obsoleted soon: library/python/backport_abc library/python/backports.functools_lru_cache library/python/backports.ssl_match_hostname library/python/colorama library/python/decorator library/python/enum library/python/flamegraph library/python/funcsigs library/python/ipaddress library/python/ipython library/python/ipython_genutils library/python/notify2 library/python/pickleshare library/python/prompt-toolkit library/python/pyatspi2 library/python/pycups library/python/pygobject library/python/pygtk2 library/python/python-compizconfig library/python/python-xdg library/python/python-xlib library/python/rbtools library/python/simplegeneric library/python/traitlets If you need any package from these lists then please create a pull request (see https://github.com/OpenIndiana/oi-userland/pulls) to get the package back and built for python 3.7 and/or 3.9 (in a case it is on the first list of already obsoleted packages), or either let us know or create a pull request to rebuild the package for python 3.7 and/or 3.9 (if it is on the second list of packages we could possibly obsolete). Any help with this task is very welcome (for example pull requests to get software in set #1 rebuilt). Please note that support for building python modules for python 2.7 and 3.5 was already dropped from oi-userland. Thank you. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] borg missing msgpack dependency?
On Tue, Sep 27, 2022 at 12:29:31AM +1000, Carl Brewer wrote: > I just bumped a ~12 month old OI Hipster that had Borg installed on it to > the current pkg contents. > > Ran borg, saw this : > > root@hog:/slow/backups# borg > Traceback (most recent call last): > File "/usr/lib/python3.9/vendor-packages/borg/archiver.py", line 38, in > > from . import helpers > File "/usr/lib/python3.9/vendor-packages/borg/helpers/__init__.py", line > 14, in > from .misc import * # NOQA > File "/usr/lib/python3.9/vendor-packages/borg/helpers/misc.py", line 16, > in > from . import msgpack > File "/usr/lib/python3.9/vendor-packages/borg/helpers/msgpack.py", line > 19, in > from msgpack import Packer as mp_Packer > ModuleNotFoundError: No module named 'msgpack' > > pkg install python/msgpack fixes it > > > Is this an artifact of recent changes to Python versions that didn't quite > make a dependency list? I do not think this is something recent because even backup/borg@1.2.0 built 5 months ago does not depend on msgpack. PRs are welcome. Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
