Re: [OpenIndiana-discuss] upgrading system
pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22348:20240919T032945Z Reason: No version matching 'require' dependency runtime/python-39@3.9.20-2024.0.0.0 can be installed Reject: pkg://openindiana.org/runtime/python-39@3.9.20-2024.0.0.0:20240908T085714Z Reason: No version matching 'require' dependency compress/xz@5.6.2-2024.0.0.0 can be installed Reason: This version is excluded by installed incorporation consolidation/userland/userland-incorporation@0.5.11-2024.0.0.23824 Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Reject: pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22350:20240920T223354Z to pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22362:20240923T223627Z Reason: No version matching 'require' dependency runtime/python-39@3.9.20-2024.0.0.0 can be installed Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Reject: pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22363:20240924T223940Z Reason: No version matching 'require' dependency system/library@0.5.11-2024.0.0.22363 can be installed Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Reject: pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22365:20240925T224319Z Reason: No version matching 'require' dependency runtime/python-39@3.9.20-2024.0.0.0 can be installed Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Reject: pkg://openindiana.org/system/library/python/solaris-39@0.5.11-2024.0.0.22382:20241004T010123Z Reason: No version matching 'require' dependency runtime/python-39@3.9.20-2024.0.0.0 can be installed Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Reject: pkg://openindiana.org/system/library@0.5.11-2024.0.0.22363:20240924T223438Z pkg://openindiana.org/system/library@0.5.11-2024.0.0.22365:20240925T223805Z Reason: [already rejected; see above] Reason: This version is excluded by installed incorporation consolidation/userland/userland-incorporation@0.5.11-2024.0.0.23824 Reason: This version is excluded by installed incorporation consolidation/userland/userland-incorporation@0.5.11-2024.0.0.23824 # --Apostolos Syropoulos Xanthi, Greece On Saturday, October 5, 2024 at 08:35:22 PM GMT+3, Andreas Wacknitz via openindiana-discuss wrote: Am 05.10.24 um 18:05 schrieb Apostolos Syropoulos via openindiana-discuss: Today I tried to upgrade my system and i got this: # pkg update -v Packages to update: 4 Estimated space available: 342.13 GB Estimated space to be consumed: 300.60 MB Create boot environment: No Create backup boot environment: Yes Rebuild boot archive: No Changed packages: openindiana.org consolidation/l10n/l10n-incorporation 0.5.11-2024.0.0.22303 -> 0.5.11-2024.0.0.22382 consolidation/sfw/sfw-incorporation 0.5.11-2015.0.2.0:20240822T101626Z -> 0.5.11-2015.0.2.0:20241004T191122Z consolidation/sunpro/sunpro-incorporation 0.5.11-2024.0.0.22303 -> 0.5.11-2024.0.0.22382 consolidation/xvm/xvm-incorporation 0.5.11-2015.0.2.0:20240822T101825Z -> 0.5.11-2015.0.2.0:20241004T191139Z PHASE ITEMS Updating modified actions 12/12 Updating package state database Done Updating package cache 4/4 Updating image state Done Creating fast lookup database Done --- NOTE: Please review release notes posted at: https://www.openindiana.org/ --- I had the following: # pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org (non-sticky) origin onlin
Re: [OpenIndiana-discuss] upgrading system
Am 05.10.24 um 18:05 schrieb Apostolos Syropoulos via openindiana-discuss: Today I tried to upgrade my system and i got this: # pkg update -v Packages to update: 4 Estimated space available: 342.13 GB Estimated space to be consumed: 300.60 MB Create boot environment: No Create backup boot environment: Yes Rebuild boot archive: No Changed packages: openindiana.org consolidation/l10n/l10n-incorporation 0.5.11-2024.0.0.22303 -> 0.5.11-2024.0.0.22382 consolidation/sfw/sfw-incorporation 0.5.11-2015.0.2.0:20240822T101626Z -> 0.5.11-2015.0.2.0:20241004T191122Z consolidation/sunpro/sunpro-incorporation 0.5.11-2024.0.0.22303 -> 0.5.11-2024.0.0.22382 consolidation/xvm/xvm-incorporation 0.5.11-2015.0.2.0:20240822T101825Z -> 0.5.11-2015.0.2.0:20241004T191139Z PHASE ITEMS Updating modified actions 12/12 Updating package state database Done Updating package cache 4/4 Updating image state Done Creating fast lookup database Done --- NOTE: Please review release notes posted at: https://www.openindiana.org/ --- I had the following: # pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org (non-sticky) origin online F http://pkg.openindiana.org/hipster/ hipster-encumbered origin online F http://pkg.openindiana.org/hipster-encumbered/ # pkg set-publisher --sticky openindiana.org # pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org origin online F http://pkg.openindiana.org/hipster/ hipster-encumbered origin online F http://pkg.openindiana.org/hipster-encumbered/ I think I had cleared the cache sometime and after that I got this. Whatshould I do to upgrade? Thank you in advance.Apostolos --Apostolos Syropoulos Xanthi, Greecehttp://asyropoulos.eu http://asyropoulos.wordpress.com http://hypercomputation.blogspot.com/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Something is blocking your update. Try to install the latest userland-incorporation, eg. with "pfexec pkg install userland-incorporation@0.5.11-2024.0.0.26304". This will give some ideas. Additionally you can try that with the osnet-incorporation: "pfexec pkg install osnet-incorporation@0.5.11-2024.0.0.22382" ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OpenIndiana version "OpenIndiana Hipster 2024.04 Version master-0-gaaceeb38b2-dirty 64-bit"
Am 08.09.24 um 13:54 schrieb russell: Good Morning I performed an update today and after a reboot I noticed the following message during boot, so copied the log entry from /var/adm/messages Sep 8 12:43:36 tesla genunix: [ID 107833 kern.notice] ^MOpenIndiana Hipster 2024.04 Version master-0-gaaceeb38b2-dirty 64-bit Is this the correct kernel version? Yes, this is due to changes in illumos-gate. We have a PR to fix this in the works: https://github.com/OpenIndiana/oi-userland/pull/18701 Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NVME bootable ?
Am 05.08.24 um 17:24 schrieb Udo Grabowski (IMK): Hi, is OI now bootable from a NVME device ? If so: In general, or does it still depend on specific controllers ? I have OI installed on two HP (Z4 G4 and Z6 G4) booting it from NVMe SSD's. The harder part was to get the install media booting on these machines. Our installation media doesn't work with activated SATA RAID. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gfxdrm/OpenGL error with latest update
Am 04.08.24 um 18:45 schrieb Ignacio Soriano Hernandez: That is true, the gfx stack on OI has been stuck for years and what is even worse, nowadays we have powerful mobile devices that could provide a very nice user experience. But as we know as well the nasty and really difficult bug that prevents leveraging the NVIDIA gfx is something that requires some really good kernel expert (just to get into). And we just do not have the people to do that. They are stuck with other topics. Btw, you mention postings in the PR‘s. Why not doing it like the Mesa mailing list where a broader range of people would get informed? And we do not have an unstable but just encumbered branch which is not being used for it but vlc, fs-uae etc. We have our mailing lists and Github already. Using more ways of communication only make it harder. It's simply that we don't have enough volunteers. Most people expect to get services like it is offered from paid products just without the payments. It is not about willing to help but the lack of expertise that at least applies to me. I know the BSD community is by far larger than the OI one and they solved a lot of the things OI has (if it survives as a desktop) to tackle. Surely illumos-gate (and its forks have a commercial motivitation) so I not concerned about the desktop. I have also started with little knowledge. The way to success is not to talk but to act. And as old as Solaris 11.4.42 CBE is, I prefer more and more its core (which can be extended via OSS) and run other OSes in the Virtualboxes of Solaris. Cheers Iggi ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gfxdrm/OpenGL error with latest update
Am 04.08.24 um 17:55 schrieb Aurélien Larcher: That's why I had not updated the stack, there were some notes in the tickets and some discussions with Klaus and Alan back then. There were a few patches parked in the gfx-drm branches. I merged the PR willingly and urged Till to produce it. The alternative is that OI would have been stuck with the outdated version probably forever. Now we have a newer package that has some defects but some people working on it. Obviously some suffer from its state but I ask them to be more actively help us. In my eyes this is better than to stay longer with an outdated version that only works with old Intel chips. If we cannot activate more people to help OI will be dead sooner or later. Now people tell us to test more thoroughly but in the past I had PR's with remarks asking people to test it without any responses for weeks if not months. So that way didn't work well either. Andreas Le vendredi 2 août 2024, Till Wegmueller a écrit : Hello All This is a known issue since the last Mesa update and seems to come from the changes Solaris did to it's platform Support by disabling Intel completely Upstream for Solaris and hardlinking the driver to Swrast. So yes We have effectively disabled intel acceleration due to the Mesa build system. It seems swrast is not up to the task though to handle modern GUI applications so I will have to bite the bullet and actually port that part of mesa back. This will take some time as the intel driver userland parts currently can't compile due to some C functions I will need to port. For some reason It did not install properly on my machine and I got a working OpenGL setup when I tested. I'll look into this in detail once I am back from Holidays. I think we will need to do the same thing we did with golang and split the OS detection so we can provide different configurations on illumos than Solaris. -Till On 31/07/2024 18.19, scavenger via openindiana-discuss wrote: Yes, I found all graphical applications to be sluggish. Firefox is the worse. Jul 31, 2024, 12:27 by stephan.alth...@duedinghausen.eu: On 7/31/24 01:57, scavenger via openindiana-discuss wrote: Originally posted by another people here: https://illumos.topicbox.com/groups/discuss/T6362d704c0be376b/gfxdrm-opengl-error-with-latest-update https://illumos.topicbox.com/groups/discuss/T024578a526b45d4d/aw-discuss-re-gfxdrm-opengl-error-with-latest-update I joined the discussion and posted further information. We are both affected by this bug. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thats not good. Do you feel slow handling in desktop apps (aside from games etc) ? On my system the error doesn't show up, i am using nvidia: $ glxinfo -B ... OpenGL version string: 4.5.0 NVIDIA 535.183.01 ... (as my builtin intel chipset was/is not supported) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] cups trouble
Am 26.07.24 um 21:47 schrieb Goetz T. Fischer: On Fri, 26 Jul 2024 21:33:57 +0200, Andreas Wacknitz via openindiana-discuss wrote: D [26/Jul/2024:20:35:37 -0100] [Job 252] ld.so.1: hal: fatal: libcups.so.2: open failed: No such file or directory D [26/Jul/2024:20:35:37 -0100] [Job 252] ld.so.1: hal: fatal: relocation error: file /usr/lib/cups/backend/hal: symbol cupsBackendDeviceURI: referenced symbol not found The problem is that hal is still 32 bit and we dropped 32 bit support for cups. The package hal-cups-utils needs to be rebuild for 64 bit (if it is possible at all). oh okay, i don't insist on hal if i can connect in some other way. i just used hal because that worked at the time. what's the "official" way of using usb printers? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have created a PR to switch hal-cups-utils to 64 bit and will integrate it soon. Can you check whether this works for you? Maybe hal_lpadmin needs to be updated for python 3. I haven't checked that. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] cups trouble
Am 26.07.24 um 21:11 schrieb Goetz T. Fischer: On Fri, 26 Jul 2024 11:39:14 +0200, Carsten Grzemba via openindiana-discuss wrote: Am 26.07.24 07:26 schrieb "Goetz T. Fischer" : hi all, yes i know it's a popular joke but in my case right now it really is true: my printer doesn't print anymore. i don't print much so i can't tell exactly when it stopped working. could be a couple of months give or take. i'm using cups and hal and the printer is connected via usb and so far it worked fine. right now however it still looks fine from the indiana side but the printer simply does nothing. the cups error log shows nothing, the printing job is listed without errors either and messages looks like this: Jul 25 21:20:24 oibox usba: [ID 912658 kern.info] USB 1.10 device (usb6bc,83) operating at full speed (USB 1.x) on USB 1.10 root hub: printer@2, usbprn3 at bus address 2 Jul 25 21:20:24 oibox usba: [ID 349649 kern.info] OKI DATA CORP USB Device Jul 25 21:20:24 oibox genunix: [ID 936769 kern.info] usbprn3 is /pci@0,0/pci1734,10fd@1d,1/printer@2 Jul 25 21:20:24 oibox genunix: [ID 408114 kern.info] /pci@0,0/pci1734,10fd@1d,1/printer@2 (usbprn3) online of course i tried to delete and add the printer again in cups, tried with foomatic instead of gutenprint, used a different usb port and so on but nothing helped. then just to make sure the hardware is okay, i booted that same box with knoppix and was able to print with that with cups right away. so apparently the problem seems to be on the indiana side. one thing i noticed is that in the cups webui the jobs are finished very quickly. that could indicate that the problem is the transmission i.e. nothing gets actually sent to the printer. for now i'm out of ideas. any hints are welcome! -- raise the LogLevel debug should list in /var/log/cups/error_log every step the print job is doing and hopefully what is failing. yep, debug logging is always nice and this caught my attention: D [26/Jul/2024:20:35:37 -0100] [Job 252] ld.so.1: hal: fatal: libcups.so.2: open failed: No such file or directory D [26/Jul/2024:20:35:37 -0100] [Job 252] ld.so.1: hal: fatal: relocation error: file /usr/lib/cups/backend/hal: symbol cupsBackendDeviceURI: referenced symbol not found however, libcups.so.2 does exist in /usr/lib/amd64 and has 803kb. later on: D [26/Jul/2024:20:35:37 -0100] [Job 252] Calling FindDeviceById(cups-OKI_DATA_CORP_B4350) D [26/Jul/2024:20:35:37 -0100] [Job 252] Failed to send: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files D [26/Jul/2024:20:35:37 -0100] [Job 252] Failed to get find device cups-OKI_DATA_CORP_B4350 D [26/Jul/2024:20:35:37 -0100] [Job 252] Calling FindDeviceById(cups-OKI_DATA_CORP_B4350) D [26/Jul/2024:20:35:37 -0100] [Job 252] Failed to send: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files D [26/Jul/2024:20:35:37 -0100] [Job 252] Failed to get device cups-OKI_DATA_CORP_B4350 not sure what to do about that and not sure why it doesn't find the lib either. anyway i attached the log. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi, The problem is that hal is still 32 bit and we dropped 32 bit support for cups. The package hal-cups-utils needs to be rebuild for 64 bit (if it is possible at all). Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Repository Cleanup
Am 09.07.24 um 14:36 schrieb Marcel Telka: 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? We found out that the real problem is the new infrastructure. A query returns HTTP code 204. The report that an older BE was still working wasn't correct. The user issued a local search and thus didn't use the server. Alas we haven't found a solution yet. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Repository Cleanup
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? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss 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. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Selecting wrong video driver
Am 08.05.24 um 02:42 schrieb Rainer Heilke: One more question as I head out the door... Groveling around the interwebs, I ran into a possibly related thread: Could I still run into problems because this is a UEFI-only system? No, on my HP Z4 G4 X11 (nvidia) doesn't work in legacy mode but UEFI only. I just had to turn off secure boot. Andreas ___ 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,
Hi, My main OI desktop system is a Fujitsu W530 workstation with an NVIDIA Quadro P600. Am 10.02.24 um 09:16 schrieb Carsten Grzemba via openindiana-discuss: For do some preliminary testing on update Pulseaudio I am interested in a small contribution. If anyone has more then one audio device, I am interested in the output of: $ ls -l /dev/audio* lrwxrwxrwx 1 root root 7 Apr. 1 2022 /dev/audio -> sound/0 lrwxrwxrwx 1 root root 10 Apr. 1 2022 /dev/audioctl -> sound/0ctl $ ls -l /dev/sound* total 12 lrwxrwxrwx 1 root root 9 Apr. 1 2022 0 -> audiohd:0 lrwxrwxrwx 1 root root 12 Apr. 1 2022 0ctl -> audiohd:0ctl lrwxrwxrwx 1 root root 9 Sep. 24 11:47 2 -> audiohd:2 lrwxrwxrwx 1 root root 12 Sep. 24 11:47 2ctl -> audiohd:2ctl lrwxrwxrwx 1 root root 50 Apr. 1 2022 audiohd:0 -> ../../devices/pci@0,0/pci1734,11eb@1b:sound,audio0 lrwxrwxrwx 1 root root 53 Apr. 1 2022 audiohd:0ctl -> ../../devices/pci@0,0/pci1734,11eb@1b:sound,audioctl0 lrwxrwxrwx 1 root root 48 Apr. 1 2022 audiohd:0dsp -> ../../devices/pci@0,0/pci1734,11eb@1b:sound,dsp0 lrwxrwxrwx 1 root root 50 Apr. 1 2022 audiohd:0mixer -> ../../devices/pci@0,0/pci1734,11eb@1b:sound,mixer0 lrwxrwxrwx 1 root root 69 Sep. 24 11:47 audiohd:2 -> ../../devices/pci@0,0/pci8086,8c18@1c,4/pci10de,11bd@0,1:sound,audio2 lrwxrwxrwx 1 root root 72 Sep. 24 11:47 audiohd:2ctl -> ../../devices/pci@0,0/pci8086,8c18@1c,4/pci10de,11bd@0,1:sound,audioctl2 lrwxrwxrwx 1 root root 67 Sep. 24 11:47 audiohd:2dsp -> ../../devices/pci@0,0/pci8086,8c18@1c,4/pci10de,11bd@0,1:sound,dsp2 lrwxrwxrwx 1 root root 69 Sep. 24 11:47 audiohd:2mixer -> ../../devices/pci@0,0/pci8086,8c18@1c,4/pci10de,11bd@0,1:sound,mixer2 $ ls -l /dev/dsp* lrwxrwxrwx 1 root root 4 Apr. 1 2022 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Apr. 1 2022 /dev/dsp0 -> sound/audiohd:0dsp lrwxrwxrwx 1 root root 18 Sep. 24 11:47 /dev/dsp2 -> sound/audiohd:2dsp Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 04.02.24 um 23:20 schrieb Goetz T. Fischer: On Sun, 4 Feb 2024 09:37:26 +0100, Andreas Wacknitz via openindiana-discuss wrote: You can only update individual packages when you uninstall both, userland-incorporation and entire. i did so and got the exact same reply as before. and using install instead fails with tons of consolidation/osnet/osnet-incorporation errors. You are unlucky that we had changes in illumos-gate recently that also needed changes in oi-userland. This is rare but can happen. So, in this case you'll need a full update. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 04.02.24 um 03:21 schrieb Goetz T. Fischer: well it might not be so good after all. for example just updating openssl: root@openindiana:~# pkg list library/security/openssl-31 NAME (PUBLISHER) VERSIONIFO library/security/openssl-31 3.1.4-2023.0.0.1 i-- root@openindiana:~# pkg update -nv library/security/openssl-31 No updates available for this image. looks fine. however, if i just use "pkg update -nv" i see: library/security/openssl-31 3.1.4-2023.0.0.1 -> 3.1.5-2024.0.0.0 so there is an update after all. apparently updating single packages doesn't work this way. Yes, this is by design. The metapackage userland-incorporation defines a baseline and thus fixes all package versions of packages coming from oi-userland. userland-incorporation will be updated automatically whenever an oi-userland jenkins job finishes successfully. You can only update individual packages when you uninstall both, userland-incorporation and entire. But that comes at additional costs as there are no guarantees that a newer version of a packages works with other packages. This is, by the way, usually a duty of a package maintainer. If a package maintainer updates a package he/she needs to check whether other packages need to be rebuild or even updated, too. This is a situation where problems can be introduced easily because some dependencies and changes are obvious and others are hiddenm especially the dependencies from illumos-gateway. Andreas On Mon, 8 Jan 2024 12:31:04 +0100, Goetz T. Fischer wrote: fair, that's good enough for me. much thanks for all the great info !! On Mon, 8 Jan 2024 12:22:20 +0100, Marcel Telka wrote: Sure. It should somehow (and usually) work, modulo the userland-incorporation warning in my previous mail. So it is discouraged. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
Am 14.01.24 um 00:36 schrieb Bill Sommerfeld via openindiana-discuss: On 1/13/24 15:20, Andreas Wacknitz via openindiana-discuss wrote: Am 14.01.24 um 00:13 schrieb Goetz T. Fischer: i'm afraid making ips fast needs more than just a cython module here and there. don't get me wrong, that's not indiana's fault but a genernal ips issue. maybe having a closer look at mr. Wegmueller's go version would be a good idea after all. If you want to make IPS fast you will probably need more than switching the implementation language. As Aurélien mentioned, IPS is using a SAT solver. So it might be necessary to also change the algorithms. Are you sure that you can devote enough time to achieve real advantages? Any such effort should start by profiling to see where the time actually goes - don't assume the SAT solver is eating it all. My casual pokes at it showed a lot of time going into manipulating the on-disk metadata, with a lot of short write() syscalls instead of using buffered I/O - but that may not have been a representative sampling of where the time goes. You are confirming what I wrote about the need to change algorithms. The SAT solver was just an example. Alas changing this doesn't seem to be so easy without changing IPS requirements. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
Am 14.01.24 um 00:13 schrieb Goetz T. Fischer: i'm afraid making ips fast needs more than just a cython module here and there. don't get me wrong, that's not indiana's fault but a genernal ips issue. maybe having a closer look at mr. Wegmueller's go version would be a good idea after all. If you want to make IPS fast you will probably need more than switching the implementation language. As Aurélien mentioned, IPS is using a SAT solver. So it might be necessary to also change the algorithms. Are you sure that you can devote enough time to achieve real advantages? On Sun, 14 Jan 2024 00:05:18 +0100, Andreas Wacknitz via openindiana-discuss wrote: Am 13.01.24 um 17:55 schrieb Alan Coopersmith: On 1/13/24 08:41, Goetz T. Fischer wrote: the first and foremost problem of ips is speed. Someone looking to improve that might want to check out the recent performance improving commits to https://github.com/oracle/solaris-ips/commits/master/ and see if they cherry-pick to OI's fork. -alan- So there is a low hanging fruit for people to not just talk but also do something with this link given by Alan. Please contribute to OI. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Questions about /var/pkg
Am 13.01.24 um 17:55 schrieb Alan Coopersmith: On 1/13/24 08:41, Goetz T. Fischer wrote: the first and foremost problem of ips is speed. Someone looking to improve that might want to check out the recent performance improving commits to https://github.com/oracle/solaris-ips/commits/master/ and see if they cherry-pick to OI's fork. -alan- So there is a low hanging fruit for people to not just talk but also do something with this link given by Alan. Please contribute to OI. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 08.01.24 um 04:07 schrieb Goetz T. Fischer: hi, a general question: i did a "pkg update" on the 2nd and another one just now. so just a few days later but again a new be was created and i had to reboot. of course i understand that for certain things a reboot is necessary but is there a way to somewhat filter the things that don't need a reboot ? for a desktop system that doesn't matter but i can't reboot a server once a week or maybe even more often. especially if i have several zones and/or vms. in other words, what's the "officially" recommended way of updating a server? thanks in advance for any info -- R-A-C Götz T. Fischer CertIT&Comp +49(0)7225/98 98 79 g.fisc...@r-a-c.de r-a-c.de ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss "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. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 32-bit libraries disappearing
Am 07.01.24 um 23:28 schrieb Matthew R. Trower: > 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. You can't do this. You will lose the ldap utils. Not just the userland binaries, but also the simple ability to say, log in to systems which authenticate over LDAP. > There are several types of software you can run on OpenIndiana: Respectfully, you seem to have misinterpreted my message. 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? Sorry, I was too fast pressing the send button in my earlier answer. Dropping 32 bit hasn't been discussed on the mailing list but only in personal mails and online meetings (we have a monthly maintainer meeting and try to establish weekly co-working sessions). The removal process started several weeks ago and until now only very few have noticed it. It is not our intention to break things but alas some dependencies aren't obvious. As already written, OI has very few active maintainers. For most parts of our infrastructure I am the only one caring. Do we need more? Certainly yes. Would more hands help keeping 32 bit? Only, if there will be enough people supporting it. Is the process revertable? Yes, but we have some cyclic dependencies where re-introducing 32 bit would be some extra work. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 32-bit libraries disappearing
Am 07.01.24 um 23:28 schrieb Matthew R. Trower: > 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. You can't do this. You will lose the ldap utils. Not just the userland binaries, but also the simple ability to say, log in to systems which authenticate over LDAP. > There are several types of software you can run on OpenIndiana: Respectfully, you seem to have misinterpreted my message. 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 am trying to determine what the goals and roadmap of this project have become, and whether they any longer align with my own. The reason 32 bit is being removed is simply because supporting 64 and 32 bit is more work than only 64 bit. Some package build receipes need A LOT of work in order to support both variants. So the intention is to reduce the amount of work for maintainers (we are just a few). Andreas -- Matthew R. Trower On 1/7/24 04:28, Marcel Telka wrote: 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 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg update this morning resulted in svc-dbus error 95
Am 25.11.23 um 07:14 schrieb russell: Good Morning Performed an update this morning to create a new BE. oihipster-20231103 - - 2.76G static 2023-11-25 06:00 Upon rebooting the svc-dbus service failed with code 95 which resulted in the GUI not being available as the nvidia module was unloaded. Did not investigate further as I have out of hours work to complete. Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I haven't tested my dbus changes thoroughly because they seemed harmless. Now we know that they weren't. Sorry for your inconveniences. When you update again the should be fixed as I have reverted my changes. Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Build Server is stuck (?)
Am 03.11.23 um 14:40 schrieb Stephan Althaus: Hello! As you might have noticed, the build server is stuck and does not build the recent PRs. Regards, Stephan It's not the build server that is stuck, it's the PR check build system that is having problems accessing github. We are working on a fix. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] audacity is erroring
Am 30.10.23 um 15:05 schrieb russell: Hi, Performed an update on Sunday 29th, when I attempted to run audacity I get the following error $ audacity ld.so.1: audacity: fatal: libwx_gtk3u_html-3.1.so.5: open failed: No such file or directory ld.so.1: audacity: fatal: relocation error: file /usr/bin/audacity: symbol _ZTV21wxHtmlFilterPlainText: referenced symbol not found Killed Uninstalled and then re-installed # pkg uninstall audacity Packages to remove: 1 Services to change: 3 Create boot environment: No Create backup boot environment: No PHASE ITEMS Removing old actions 187/187 Updating package state database Done Updating package cache 1/1 Updating image state Done Creating fast lookup database Done Updating package cache 2/2 root@tesla:~# pkg refresh --full root@tesla:~# pkg install audacity Packages to install: 1 Services to change: 3 Create boot environment: No Create backup boot environment: No DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 1/1 145/145 10.3/10.3 8.3M/s PHASE ITEMS Installing new actions 175/175 Updating package state database Done Updating package cache 0/0 Updating image state Done Creating fast lookup database Done Updating package cache 2/2 root@tesla:~# Same error as before $ audacity ld.so.1: audacity: fatal: libwx_gtk3u_html-3.1.so.5: open failed: No such file or directory ld.so.1: audacity: fatal: relocation error: file /usr/bin/audacity: symbol _ZTV21wxHtmlFilterPlainText: referenced symbol not found Killed An lld /usr/bin/audacity ldd audacity libexpat.so.1 => /usr/lib/64/libexpat.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libsndfile.so.1 => /usr/lib/64/libsndfile.so.1 libsoxr.so.0 => /usr/lib/64/libsoxr.so.0 libwx_gtk3u_html-3.1.so.5 => (file not found) libwx_gtk3u_qa-3.1.so.5 => (file not found) libwx_gtk3u_core-3.1.so.5 => (file not found) libwx_baseu_net-3.1.so.5 => (file not found) libwx_baseu-3.1.so.5 => (file not found) libFLAC++.so.6 => (file not found) libFLAC.so.8 => (file not found) libid3tag.so.0 => /usr/lib/64/libid3tag.so.0 libmad.so.0 => /usr/lib/64/libmad.so.0 libtwolame.so.0 => /usr/lib/64/libtwolame.so.0 libvorbisenc.so.2 => /usr/lib/64/libvorbisenc.so.2 libvorbisfile.so.3 => /usr/lib/64/libvorbisfile.so.3 libvorbis.so.0 => /usr/lib/64/libvorbis.so.0 libogg.so.0 => /usr/lib/64/libogg.so.0 libgtk-3.so.0 => /usr/lib/64/libgtk-3.so.0 libgdk-3.so.0 => /usr/lib/64/libgdk-3.so.0 libgdk_pixbuf-2.0.so.0 => /usr/lib/64/libgdk_pixbuf-2.0.so.0 libgobject-2.0.so.0 => /usr/lib/64/libgobject-2.0.so.0 libglib-2.0.so.0 => /usr/lib/64/libglib-2.0.so.0 libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1 libc.so.1 => /lib/64/libc.so.1 libFLAC.so.12 => /usr/lib/64/libFLAC.so.12 libopus.so.0 => /usr/lib/64/libopus.so.0 libmpg123.so.0 => /usr/lib/64/libmpg123.so.0 libmp3lame.so.0 => /usr/lib/64/libmp3lame.so.0 libgomp.so.1 => /usr/gcc/10/lib/amd64/libgomp.so.1 libz.so.1 => /usr/lib/64/libz.so.1 libXinerama.so.1 => /usr/lib/64/libXinerama.so.1 libXrandr.so.2 => /usr/lib/64/libXrandr.so.2 libXcursor.so.1 => /usr/lib/64/libXcursor.so.1 libXext.so.0 => /usr/lib/64/libXext.so.0 libgmodule-2.0.so.0 => /usr/lib/64/libgmodule-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/64/libpangocairo-1.0.so.0 libX11.so.4 => /usr/lib/64/libX11.so.4 libXi.so.5 => /usr/lib/64/libXi.so.5 libXcomposite.so.1 => /usr/lib/64/libXcomposite.so.1 libXdamage.so.1 => /usr/lib/64/libXdamage.so.1 libXfixes.so.1 => /usr/lib/64/libXfixes.so.1 libcairo-gobject.so.2 => /usr/lib/64/libcairo-gobject.so.2 libcairo.so.2 => /usr/lib/64/libcairo.so.2 libatk-1.0.so.0 => /usr/lib/64/libatk-1.0.so.0 libatk-bridge-2.0.so.0 => /usr/lib/64/libatk-bridge-2.0.so.0 libepoxy.so.0 => /usr/lib/64/libepoxy.so.0 libfribidi.so.0 => /usr/lib/64/libfribidi.so.0 libgio-2.0.so.0 => /usr/lib/64/libgio-2.0.s
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
Am 28.10.23 um 12:52 schrieb Stephan Althaus: On 6/1/23 22:28, Stephan Althaus wrote: I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Yes, the hash error is gone and the package can be downloaded now. Thanks!! Regards, Stephan Hello! I am hit by the same error today within a zone: Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z expected: cb02cbdaa6cda8a1ed1915185fe38015a6dce552 computed: a159de951797140d09295c42401e58092f2c8fd9. (happened 4 times) A pkg update in the global and an other local zone have been successful yesterday... A pkg refresh --full && pkg update an an other global zone got this: pkg refresh --full && pkg update && exit Creating Plan (Package planning: 64/614): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z expected: cefb854835a501b27a457630019ebc73cb3c099d computed: e3d9c336f4cb17b3e0a8ea59c8a2003c4eae6db1. (happened 4 times) I don't understand this. Maybe this is an error in my local network/transport ?? I will reset my network now and try again. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Please try again. We have rebuilt the affected packages. Regards, Andreas ___ 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
Am 28.10.23 um 13:08 schrieb Stephan Althaus: On 10/28/23 12:52, Stephan Althaus wrote: On 6/1/23 22:28, Stephan Althaus wrote: I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Yes, the hash error is gone and the package can be downloaded now. Thanks!! Regards, Stephan Hello! I am hit by the same error today within a zone: Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z expected: cb02cbdaa6cda8a1ed1915185fe38015a6dce552 computed: a159de951797140d09295c42401e58092f2c8fd9. (happened 4 times) A pkg update in the global and an other local zone have been successful yesterday... A pkg refresh --full && pkg update an an other global zone got this: pkg refresh --full && pkg update && exit Creating Plan (Package planning: 64/614): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z expected: cefb854835a501b27a457630019ebc73cb3c099d computed: e3d9c336f4cb17b3e0a8ea59c8a2003c4eae6db1. (happened 4 times) I don't understand this. Maybe this is an error in my local network/transport ?? I will reset my network now and try again. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Seems to be not network related on my side.. Anyone else seeing this ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi, I have released new install media yesterday (the 2023.10 release will be announced soonish). After that I have cleaned up the repositories. The problems you are experiencing seem to be related to that. I don't have an idea what causes this. It might that the underlying infrastructure has problems I am not aware of. The cleanup only takes the latest revisions of packages, it is done like this (repo is the old repository and repo.new the new one): pkgrecv -s repo --newest | tee pkg-list cat pkg-list | split -l 100 for i in $(ls x*); do pkgrecv -s repo -d repo.new $(cat $i); done It looks like the pkgrecv got some damaged packages. It happened before and the simplest solution was to rebuild the affected packages. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gccgo crashes
Am 20.10.23 um 19:38 schrieb Marcel Telka: 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? No, that works. What `pmap core` shows? ╰─➤ pmap /var/cores/core.go.2435 core '/var/cores/core.go.2435' of 2435: /usr/gcc/10/bin/go env 0040 3080K r-x-- /usr/gcc/10/bin/go 00711000 64K rw--- /usr/gcc/10/bin/go 00721000 168K rw--- [ heap ] 00C0 65536K rw--- [ anon ] 7FFF8080 32768K rw--- [ anon ] 7FFF82A0 263680K - [ anon ] 7FFF92B8 4K rw--- [ anon ] 7FFF92B81000 260604K - [ anon ] 7FFFA2B3 108K r-x-- /usr/gcc/10/lib/amd64/libgcc_s.so.1 7FFFA2B5A000 4K rw--- /usr/gcc/10/lib/amd64/libgcc_s.so.1 7FFFA2B6 19096K r-x-- /usr/gcc/10/lib/amd64/libgo.so.16.0.0 7FFFA3E15000 5412K rw--- /usr/gcc/10/lib/amd64/libgo.so.16.0.0 7FFFA435E000 236K rw--- /usr/gcc/10/lib/amd64/libgo.so.16.0.0 7FFFA6C0 4096K rw--- [ anon ] 7FFFA720 4096K rw--- [ anon ] 7FFFA780 4096K rw--- [ anon ] 7FFFA7CE 8K r-x-- /lib/amd64/libsendfile.so.1 7FFFA7CF2000 4K rw--- /lib/amd64/libsendfile.so.1 7FFFA840 4096K rw--- [ anon ] 7FFFA89FE000 8K rw--- [ stack tid=4 ] 7FFFA8BFE000 4K rw--- [ stack tid=3 ] 7FFFA8C0 4096K rw--- [ anon ] 7FFFA920 4096K rw--- [ stack tid=1 ] 7FFFA97BF000 256K rw--- [ anon ] 7FFFA980 2116K rw--- [ anon ] 7FFFA9A4 4K rw--- [ anon ] 7FFFA9A4F000 256K rw--- [ anon ] 7FFFA9A9 24K rw--- [ anon ] 7FFFA9AA 32K r [ anon ] 7FFFA9AC 32K rw--- [ altstack tid=4 ] 7FFFA9AD 32K rw--- [ altstack tid=3 ] 7FFFA9AE 4K rw--- [ anon ] 7FFFA9AF 4K rw--- [ anon ] 7FFFA9B0 4K rw--- [ anon ] 7FFFA9B1 4K rw--- [ anon ] 7FFFA9B2 4K rw--- [ anon ] 7FFFA9B3 4K rw--- [ anon ] 7FFFA9B4 4K rw--- [ anon ] 7FFFA9B5 4K rw--- [ anon ] 7FFFA9B6 4K rw--- [ anon ] 7FFFA9B7 4K rw--- [ anon ] 7FFFA9B8 4K rw--- [ anon ] 7FFFA9B9 4K rw--- [ anon ] 7FFFA9BA 4K rw--- [ anon ] 7FFFA9BB 4K rw--- [ anon ] 7FFFA9BC 4K rw--- [ anon ] 7FFFA9BD 4K rw--- [ anon ] 7FFFA9BE 4K rw--- [ anon ] 7FFFA9BF 4K rw--- [ anon ] 7FFFA9C0 32960K - [ anon ] 7FFFABC3 4K rw--- [ anon ] 7FFFABC31000 32572K - [ anon ] 7FFFADC1 4K rw--- [ anon ] 7FFFADC19000 1944K r [ anon ] 7FFFADE0 4120K - [ anon ] 7FFFAE206000 4K rw--- [ anon ] 7FFFAE207000 4068K - [ anon ] 7FFFAE61 4K rw--- [ anon ] 7FFFAE62 4K rw--- [ anon ] 7FFFAE63 4K rw--- [ anon ] 7FFFAE64 4K rw--- [ anon ] 7FFFAE65 4K rw--- [ anon ] 7FFFAE66 4K rw--- [ anon ] 7FFFAE67 4K rw--- [ anon ] 7FFFAE68 4K rw--- [ anon ] 7FFFAE69 4K rw--- [ anon ] 7FFFAE6A 4K rw--- [ anon ] 7FFFAE6B 4K rw--- [ anon ] 7FFFAE6C 4K rw--- [ anon ] 7FFFAE6CD000 12K r-x-- /lib/amd64/libpthread.so.1 7FFFAE6E 4K rw--- [ anon ] 7FFFAE6F 4K rw--- [ anon ] 7FFFAE70 4K rw--- [ anon ] 7FFFAE71 4K rw--- [ anon ] 7FFFAE72 4K rw--- [ anon ] 7FFFAE73 4K rw--- [ anon ] 7FFFAE74 4K rw--- [ anon ] 7FFFAE75 76K r-x-- /lib/amd64/libsocket.so.1 7FFFAE773000 4K rw--- /lib/amd64/libsocket.so.1 7FFFAE79 4K rw--- [ anon ] 7FFFAE7A 4K rw--- [ anon ] 7FFFAE7B 4K rw--- [ anon ] 7FFFAE7C 4K rw--- [ anon ] 7FFFAE7D 4K rw--- [ anon ] 7FFFAE7E 4K rw--- [ anon ] 7FFFAE7EA000 508K r [ anon ] 7FFFAE86A000 916K rw--- [ anon ] 7FFFAE96 4K rw--- [ anon ] 7FFFAE97 4K rw--- [ anon ] 7FFFAE98 4K rw--- [ anon ] 7FFFAE99 4K rw--- [ anon ] 7FFFAE9A 4K rw--- [ anon ] 7FFFAE9B 4K
Re: [OpenIndiana-discuss] gccgo crashes
Am 20.10.23 um 19:15 schrieb Marcel Telka: 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? It's crashing for me, too. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ruby-26 problem - don't update for now
Am 06.10.23 um 08:20 schrieb Andreas Wacknitz: We made a mistake when releasing the new ruby 3.2.2 version under the wrong ruby-26 fmri. This will create problems so please don't update your installations until we have a fixed this. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss The problem has been fixed and it should be ok to update again. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] ruby-26 problem - don't update for now
We made a mistake when releasing the new ruby 3.2.2 version under the wrong ruby-26 fmri. This will create problems so please don't update your installations until we have a fixed this. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] warning: new thunberbird crashes nvidia and nvidia-470 (works with nvidia-390)
Am 04.10.23 um 18:26 schrieb Alan Coopersmith: On 10/3/23 23:19, Andreas Wacknitz wrote: After updating thunderbird to the latest version 115.3.1 I have experienced instant crashes using either nvidia(-535) or nvidia-470 drivers. Going back to -390 makes thunderbird usable again. Thus, the problem seems to be located at the newer NVIDIA drivers. When our nvidia expert looked into it, he found the 115.x version of Firefox & Thunderbird were mixing OpenGL & EGL calls in a way that works with Mesa but not the Nvidia drivers, and applied a workaround to stop it from using EGL for now to avoid that: https://github.com/oracle/solaris-userland/blob/master/components/desktop/firefox/patches/firefox-115-glx-only.patch -alan- Alain, thanks again for this valuable information. It fixed the problems I had with the new thunderbird. Best regards, Andrea ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] warning: new thunberbird crashes nvidia and nvidia-470 (works with nvidia-390)
After updating thunderbird to the latest version 115.3.1 I have experienced instant crashes using either nvidia(-535) or nvidia-470 drivers. Going back to -390 makes thunderbird usable again. Thus, the problem seems to be located at the newer NVIDIA drivers. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Warning: icu upgrade immanent
Am 09.06.23 um 16:56 schrieb Andreas Wacknitz: I will start to merge an icu upgrade soon. That will make it necessary to rebuild a lot of other packages. Until everything has been rebuilt it is not safe to update your installation. A notice will be sent when the updates are through. Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss The upgrade of ICU is finished. All dependent packages have been rebuilt and it should now be safe again to update systems. Cheers Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Warning: icu upgrade immanent
I will start to merge an icu upgrade soon. That will make it necessary to rebuild a lot of other packages. Until everything has been rebuilt it is not safe to update your installation. A notice will be sent when the updates are through. Regards Andreas ___ 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
Am 01.06.23 um 06:55 schrieb Stephan Althaus: On 5/31/23 22:22, Stephan Althaus wrote: Hello! I have an old system running OI from November 2022: # pkg refresh --full && pkg update Creating Plan (Package planning: 661/1021): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: 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) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool1 444G 341G 103G - - 36% 76% 1.00x ONLINE - I will try again tomorrow, and i will try to remove some unused packages if this is related (this machine had various build bits like gcc-7, gcc-10 that are not needed anymore...) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! pkg update doesn't work, because of the 'old' pakcage readline may have some hash error. i tried to verify this with a single package download, which throws the same error: # 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? Does the package need a rebuild ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg folder size escalated
Am 18.05.23 um 11:39 schrieb Goetz T. Fischer: On Thu, 18 May 2023 11:59:52 +0300, Toomas Soome via openindiana-discuss wrote: those numbers are meaningless without checking what is inside of those files. sure, but only to some extend. it's both ips. unless of course illumos did a massive rewrite there and just kept the name for historical reasons. and the options and the messages and the package format and ... you get the idea :-) illumos (openindiana) is not solaris. The systems are different and we are not intending to be free clone of Solaris. i know what illumos is and where it came from and i didn't imply it had to be the same either. my question was about the size of the pkg folder and that i think it's too big. which then turned out to be right considering the solution with flush-content-cache-on-success and its result. the latter should be True by default if i may suggest that. as for the size, i think even the original solaris pkg folder is too big for that number of packages. looking at rhel for example i see 65mb for 485 packages. of course that depends on what packages they are but it does give a rough estimate. You are comparing apples to oranges. Nevertheless is openindiana a community project. So you are free to help us improving it. Stating shortfalls is a beginning but you have better chances to enhance oi if you provide changes in form of PR's. At the moment we have only roughly a handfull of people caring for oi-userland. As I have stated before you don't need to be a developer in order to help maintaining openindiana. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Cups problems
Am 16.05.23 um 18:58 schrieb Alan Coopersmith: On 5/16/23 09:37, Udo Grabowski (IMK) wrote: I've found a few problems with cups 1) it wants system/volatile/cups, but /system/volatile doesn't exist. Works if created manually and restart cups/in-lpd and /scheduler. Either system/volatile should be created somehow after boot before cups starts, or cups should be patched to put that into /var/run/cups; but... On Solaris, /etc/svc/volatile and /var/run were combined & renamed into /system/volatile and a symlink made from /var/run to /system/volatile for backwards compatibility, but I didn't think illumos/OI had made that change. (While Solaris made the change in the 11.0 release, it happened in snv_159, after the ON source releases ended.) The OI makefile seems to have copied the --with-rundir=/system/volatile/cups from the Solaris makefile though, which may be a mistake: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/print/cups/Makefile#L66 https://github.com/oracle/solaris-userland/blob/master/components/cups/Makefile#L59 Thanks Alan for the hint and the background. I have created a PR to fix this. Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Rebuild needed for wxwidgets-3 - consumers
Am 10.05.23 um 13:34 schrieb Stephan Althaus: Hello! i just found that codeblocks does not work anymore. Maybe a rebuild is needed because of the update of wxwidgets-3 Alas this is not so easy. Actually codeblocks doesn't compile with the latest wxwidgets-3. The project hasn't published a new release for three years. So from here it looks dead and we need to either find patches to make it work with wxwidgets-3 or need to obsolete it. Andreas $ codeblocks filelist2.cpp ld.so.1: codeblocks: fatal: libwx_gtk3u_aui-3.1.so.5: open failed: No such file or directory ld.so.1: codeblocks: fatal: relocation error: file /usr/bin/codeblocks: symbol wxEVT_AUINOTEBOOK_PAGE_CLOSE: referenced symbol not found Killed $ pkg search libwx_gtk3u_aui* INDEX ACTION VALUE PACKAGE basename link usr/lib/amd64/libwx_gtk3u_aui-3.2.so pkg:/library/graphics/wxwidgets-3@3.2.2.1-2023.0.0.0 basename file usr/lib/amd64/libwx_gtk3u_aui-3.2.so.0 pkg:/library/graphics/wxwidgets-3@3.2.2.1-2023.0.0.0 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate
Am 08.05.23 um 16:10 schrieb Udo Grabowski (IMK):
On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:
On 05/05/2023 09:14, Stephan Althaus wrote:
Hello!
The hint to use inotify support in glib was from you, can you please
shed a
light on this?
I am lacking all sorts of background on this stuff :-{
To test this, we would have to patch and build inotify support in
illumos-gate,
install it, then compile glib2 with a check if inotify was found and
install,
and then mate-system-monitor... to see if this approach does indeed
help.. Is
there some easier way?
Regards,
Stephan
Forwarded Message
Subject: Re: [OpenIndiana-discuss] Add inotify support to
illumos-gate
Date: Tue, 2 May 2023 20:25:49 +0200
From: Till Wegmüller
Reply-To: Discussion list for OpenIndiana
To: openindiana-discuss@openindiana.org
Hi Stephan
inotify has stubbed headers that work roughly decently. Any software
should use
FEN or the Native API. We add it to every programming language we
can and should
also add it to mate-system-monitor or rather make it use kstat if it
tries to
poll things under /proc which it should not for us.
What does mate-system-monitor use inotify for?
...
The parts that use Gio for monitoring in mate-system-monitor are located
in prettytable.cpp, where it monitors its apps-cache, and in
procman-app.cpp,
where it monitors mounts and somehow uses it to process a
commandline; that's
also the place it crashes (after complaining about the missing monitor
facility):
...
And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.
And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because
software that is still compiled with gcc 7 depends on them.
This mixup should be cleared first.
All libraries loaded from mate-system-monitor that depend on gcc:
/usr/lib/64/libgtkmm-3.0.so.1 ###
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libgdkmm-3.0.so.1 ###
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libxml2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/librsvg-2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libgiomm-2.4.so.1 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libglibmm-2.4.so.1 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libsigc-2.0.so.0 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/gcc/10/lib/amd64/libstdc++.so.6 ###
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libatkmm-1.6.so.1 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libpangomm-1.4.so.1 ###
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libcairomm-1.0.so.1 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libicuuc.so.68 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libcroco-0.6.so.3 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
I have upgraded pangomm and rebuilt its dependend packages gtkmm, gtkmm3
and gparted.
So all are using the correct libraries now.
Regards
Andreas
___
openindiana
Re: [OpenIndiana-discuss] gthumb libraw.so.20
Am 07.05.23 um 17:56 schrieb Stephan Althaus: On 4/12/23 09:32, Stephan Althaus wrote: Hello! On my BE of 2023-03-31 i have a failing link to LIBRAW on gthumb. Maybe the package has to be triggered to be rebuild on the build server? Regards, Stephan $ gthumb _DS33737.ARW ld.so.1: gthumb: fatal: libraw.so.20: open failed: No such file or directory ld.so.1: gthumb: fatal: relocation error: file /usr/lib/amd64/gthumb/extensions/libraw_files.so: symbol libraw_init: referenced symbol not found Killed $ pkg search libraw.so.20 $ pkg search libraw.so INDEX ACTION VALUE PACKAGE basename link usr/lib/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 basename link usr/lib/amd64/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 $ ls -l /usr/lib/libraw* lrwxrwxrwx 1 root root 18 Mar 20 21:57 /usr/lib/libraw_r.so -> libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 18 Mar 20 21:56 /usr/lib/libraw_r.so.23 -> libraw_r.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:57 /usr/lib/libraw.so -> libraw.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:56 /usr/lib/libraw.so.23 -> libraw.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw.so.23.0.0 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Something like ln -s libraw.so.23.0.0 libraw.so.20 does help, maybe this can easily be added in the gthumb package ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I fear that this might lead to strange errors because the library has a new .so version which typically indicates incompatible changes. Furthermore, it was needed to add some patches in order to build gthumb with the newer libraw. I have created a PR for it and it builds now. I hope that I was right in my believe that the missing attributes can be patched out without negative impacts on gthumb. Regards Andreas ___ 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)
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 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Best way to install rsync
Am 31.03.23 um 16:50 schrieb Michelle: No worries... pkg install rsync It was already in the library! I should have tried that first. You can always search for things in different ways, eg. pkg list -a|grep rsync Furthermore, I would like to remind that we have some documentation online, eg. https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips has a section named "Searching for packages". Plus, we have not only our ordinary package repository but also the encumbered one with packages that might have some restrictions (eg. ffmpeg and gstreamer plugins). Encumbered is not suited for servers but for desktop usage, that is, most (if not all) packages provide multimedia extensions. For me it's always irritating when people write about building their own software for their systems and don't consider contributing to the project. OpenIndiana is in desparate need for people helping packaging software and documenting the system. At the moment the burden of this is taken by just a few. By the way, you don't need to be a software developer to create or update packages. The most important thing you'll need is the will and dedication to learn the build system. Andreas Michelle. On Fri, 2023-03-31 at 15:43 +0100, Michelle wrote: I've got OI minimal install loaded and rsync isn't there. Some sources are suggesting downloading from Oracle. Others to compile it. I was wondering what would people recommend in order to get rsync onto the installation please? Michelle. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring, devices (last notice is of pseudo devices
Am 24.03.23 um 11:02 schrieb russell: On 24. Mar 2023, at 10:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not ?if? but ?when? - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? It is a bit premature to declare everything dead, but, the fact is, we can not rely on binary only drivers forever. As soon as Oracle will decide to stop distributing Solaris, nvidia will have no reason to distribute those binary drivers. Note, we *still* do rely on few closed binaries to distribute illumos itself. rgds, toomas There was a feature request #8069 for AMDGPU support which is the latest open source AMD driver for AMD graphics cards, given how AMD has improved their CPUs and Graphics Cards under Lisa Su, would now be the time to consider adding better support for AMD cards. Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss We need people to do the work. Alas we seem to lack companies interested in desktop usage and thus there is absolutely no interest in funding/supporting illumos driver development for graphics cards and other desktop related areas. I myself am missing support for Blutooth LE which is being used in newer mice and keyboards (eg. from Logitech). Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Libreoffice crashing on keyboard input
Am 20.02.23 um 14:44 schrieb russell: Good Afternoon On the 18th February I upgraded to the latest release of OI illumos-d227ea6805 (update performed 2023-02-18 18:19 UK time) and have found that I can start LibreOffice Writer or Calc but as soon as I just and enter any character into a document or spreadsheet it crashes. When I start Impress I can select a template and then it will crash. Is anyone else having the same problem? I can reproduce your problem. LibreOffice (and some other packages, too) need to be rebuild after the hunspell upgrade. I am working on it now and you can expect a fix within the next hours. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] warning - libtiif will be updated and will damage many packages until they have been rebuild - update process finished
The merge of libtiff and the necessary rebuilds of many packages are finished. Alas, during the process I found out that binutils-2.40 is broken for us. The problem was visible in a newly created qt5 version where all binaries were broken. The culprit seems to be gstrip. I have downgraded to binutils-2.39 with fake 2.40 version information (because our version numbers cannot decrease). After that it was needed to rebuild qt5 again to get working binaries. So, it should be safe again to update OI. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] warning - libtiif will be updated and will damage many packages until they have been rebuild
All, I will merge a libtiff upgrade to version 4.5.0 soon. Alas the .so major number has been changed for this version and as it is deeply integrated into userland you shouldn't update your OI installation (running pkg upgrade) until the dependend packages (qt5, qt6, ghostscript, gimp to name a few) have been rebuild. This will take some time and I will write another message when it is safe again. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gimp crash on JPG or PNG image export
Am 28.05.21 um 14:39 schrieb Carsten Grzemba via openindiana-discuss:
with the current gimp 2.10.22 I get a crash on export images as JPEG or PNG.
The export is done bz plugin:
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg
this is started via exec:
10533/1: 13.8110 execve("/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg",
0x7FFFBFFFE550, 0x02CD7A00) argc = 6
10533/1: argv: /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg
10533/1: -gimp 15 14 -run 0
10533/1: envp: _=*10224*/usr/bin/gimp AUDIODEV= COLORTERM=truecolor
10533/1: CORONA_TOKEN=pseudo.002128e65261
10533/1:
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-PPpzlt3UCi,guid=71a6c67bc283c28e74ca3aa760af6b42
10533/1: DESKTOP_SESSION=gnome DTDEVROOT=/tmp/SUNWut/sessions/12
10533/1: DTSCREENSAVERLIST=StartDtscreenBlank GDMSESSION=gnome
10533/1: GDM_KEYBOARD_LAYOUT=de GDM_LANG=de_DE.UTF-8
10533/1: GNOME_DESKTOP_SESSION_ID=this-is-deprecated
10533/1: HOME=/home/grzemba LANG=de_DE.UTF-8 LOGNAME=grzemba
10533/1: ORBIT_SOCKETDIR=/var/tmp/orbit-grzemba
10533/1: PAGER=/usr/bin/less -ins
10533/1:
PATH=/usr/bin:/usr/sbin:/sbin:/opt/SUNWut/bin:/opt/SUNWsamfs/bin:/opt/csw/bin
10533/1: PULSE_CONFIG=/etc/opt/SUNWut/pulse/daemon.conf
10533/1: PULSE_LOG_NO_RATE_LIMIT=1
10533/1: PULSE_SCRIPT=/etc/opt/SUNWut/pulse/default.pa
10533/1: PULSE_SINK=srout.12 PULSE_SOURCE=srin.12.monitor
10533/1: PWD=/home/grzemba
10533/1: SESSION_MANAGER=local/gnom:/tmp/.ICE-unix/3161
10533/1: SHELL=/usr/bin/ksh SHLVL=3 SSH_AGENT_PID=3273
10533/1: SSH_AUTH_SOCK=/tmp/ssh-XXwtailg/agent.3161
10533/1: SUN_SUNRAY_TOKEN=pseudo.002128e65261 TERM=xterm-256color
10533/1: USER=grzemba USERNAME=grzemba UTAUDIODEV=
10533/1: UTDEVROOT=/tmp/SUNWut/sessions/12/unit VTE_VERSION=5405
10533/1: WINDOWID=44040655
10533/1:
XAUTHORITY=/tmp/gdm-auth-cookies-avaqdf/auth-for-grzemba-evaqdf/database
10533/1: _AST_FEATURES=UNIVERSE - att A__z="*SHLVL
10533/1: PYTHONPATH=/usr/lib/amd64/gimp/2.0/python DISPLAY=:12
but crashed:
10533/1: 2 rB410 3 =BB10 4 R9610 51D9D10 6 2 x10 6FD7F10 81B9490 8DD a10
10533/1: 9FB v90 :BD C10 ;DB X90 86 A90 ?9B1C90 @ f #90
10533/1: A84 910 B F0590 C d1B10 D %E790 E CFD10 F05C990 G #DF10 GEEE610
10533/1: I03C110 ICEC810 JE3A310 KAEAA10 LCCBF90 M8E8C10 NACA190 O n n10
10533/1: P8C8390 Q W8A90 R l e90 S 7 l90 T L G90 U17 N90 V , )90 VF7 090
10533/1: X15 F10 XD71290 YF5 (10 ZB6F490 [D5\n10 \A01110 ]B4EC10 ^7FF310
10533/1: _94CE10 ` _D510 a }EA90 b ?B710 c ]CC90 d1F9910 e =AE90 f\bB590
10533/1: g1D9090 gE89790 hFD r90 iC8 y90 jDD T90 kA8 [90 lC6 q10 m88 =90
10533/1: nA6 S10 o h1F90 p86 510 q Q <10 r f1710 s 11E10 t EF910 u11\010
10533/1: v /1590 vF0E210 x0EF790 xD0C410 yEED990 zB0A610 {CEBB90 |99C290
10533/1: }AE9D90 ~ yA4907F8E7F90\001020302030203020302030204\00301020302
10533/1: 05\0030203020301060706070607060706070607060706070607060706070607
10533/1: 0607060706070607060706070607060706070607060706070607060706070607
10533/1: 0607060706070607060706070607060706070607060706070607060706070607
10533/1: 06070607060706070607060706070607060706070607060706070607\0\01C
10533/1: 01\0\0\00E10\005\0\01C 01\0\0\00E10\005\0\0 * 001\t\0\0 * 001\t
10533/1: \0\01C 01\0\0\00E10\005 C E S T\0 C E T\0 C E M T\0\0\00101\001
10533/1: 0101\0\0\0\0\0\00101
10533/1: 17.5854 close(11) = 0
10533/1: 17.5854 time() = 1622203035
10533/1: 17.5854 time() = 1622203035
10533/1: 17.5857 Incurred fault #6, FLTBOUNDS %pc = 0x7FFFAF3593D6
10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
10533/1: 17.5857 Received signal #11, SIGSEGV [caught]
10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
10533/1: 17.5857 lwp_sigmask(SIG_SETMASK, 0xFFBFFEFF, 0xFFF7, 0x01FF,
0x) = 0xFFBFFEFF [0x]
10533/1: 17.5858 write(2, " / u s r / l i b / a m d".., 86) = 86
10533/1: 17.5860 mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0x7FFFAC4F
10533/1: 17.5863 _exit(1)
unfortunately I cant find any core file. The good side the image was saved, so
I am guessing the crash is on plugin exit.
Has anzone seen similar problems?
Ok folks,
Woodstock located the root of the problem in the exiv2 sources. For
details you can read the bug report here:
https://www.illumos.org/issues/13824#change-40077
I have just created and merged a PR
(https://github.com/OpenIndiana/oi-userland/pull/10651) with a fix. So
the problem (and probably some others, too) should be gone soon.
Regards,
Andreas
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] GIMP issues loading jpg and png
Am 18.01.23 um 16:05 schrieb Udo Grabowski (IMK): On 17/01/2023 07:32, russell wrote: ... GIMP Message Plug-in crashed: "file-jpeg" (/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg) ... GIMP Message ... Plug-in crashed: "file-png" (/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png) ... Has anyone else noticed this? Yes, same problem here. Both plugins crash with a segfault, while a gif-file loads without problems: ts(~) gimp GIMP-Message: Some fonts failed to load: - /usr/share/gimp/2.0/fonts/ Plug-in "gtkam-gimp" (/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure "gtkam-capture" with a full menu path "/File/Acquire/Capture from Camera..." as menu label, this deprecated and will be an error in GIMP 3.0 Plug-in "gtkam-gimp" (/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure "gtkam-load" with a full menu path "/File/Acquire/Load from Camera..." as menu label, this deprecated and will be an error in GIMP 3.0 /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: Segmentation Fault gimp: GEGL-WARNING: (../../gegl-0.4.40/gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (&cache_queue)) eEeek! 14 GeglBuffers leaked ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I can confirm the problem but alas I don't get a core file which would be helpful to locate the problem. Can anybody provide a core dump? Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem with idle3.9
The file is there: ╰─➤ pkg search /usr/lib/python3.9/idlelib/util.py INDEX ACTION VALUE PACKAGE path file usr/lib/python3.9/idlelib/util.py pkg:/library/python/idle-39@3.9.15-2022.0.0.0 Maybe you need to update your installation? Are you sure that you have the latest bits? Andreas Am 30.11.22 um 17:32 schrieb Apostolos Syropoulos via openindiana-discuss: Hello, idle3.9 ( Python's Integrated Development and Learning Environment) is not working: $ idle3.9 Traceback (most recent call last): File "/usr/bin/idle3.9", line 3, in from idlelib.pyshell import main File "/usr/lib/python3.9/idlelib/pyshell.py", line 53, in from idlelib.editor import EditorWindow, fixwordbreaks File "/usr/lib/python3.9/idlelib/editor.py", line 30, in from idlelib.util import py_extensions ModuleNotFoundError: No module named 'idlelib.util' This means that the file /usr/lib/python3.9/idlelib/util.py is missing. I found this file in /tmp/XX/Python-3.9.13/Lib/idlelib/util.pyafter decompressing the python distribution to /tmp/ΧΧ I think thisfile must be included in the relevant package. Kind regards, Apostolos --Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia 515 problem
Hi Stephan,
Thanks to your efforts and the provided patch I have been able to create
a fix for own xorg-server version:
https://github.com/OpenIndiana/oi-userland/pull/9858
as our server is still on 1.19.7 while the patch is for a newer 1.21.1
version an adaption was needed.
My desktop is already running on a newer NVIDIA driver with this patched
xorg.
Regards,
Andreas
Am 11.11.22 um 09:38 schrieb Stephan Althaus:
Hello!
After a little bit of looking around, i think it could be relatated to
a bug that occured first with 495.
Solutions are
1) to disable the compositing-Manager withing mate
[org.mate.Marco.general]
compositing-manager=false
or
gsettings set org.mate.Marco.general compositing-manager false
2) a patch for xorg.server. The proposed patch to present_scmd.c could
be modified to match present.c in OI-userland...
--- a/present/present_scmd.c 2022-02-08 09:38:39.322128250 +0100
+++ b/present/present_scmd.c 2022-02-08 09:40:30.205857503 +0100
@@ -167,6 +167,9 @@
{
if (!screen_priv->info)
return NULL;
+
+ if (!screen_priv->info->get_crtc)
+ return NULL;
return (*screen_priv->info->get_crtc)(window);
}
@@ -205,6 +208,9 @@
if (!screen_priv->info)
return;
+
+ if (!screen_priv->info->flush)
+ return;
(*screen_priv->info->flush) (window);
}
i will check 1) when i have the time to reboot,
maybe 2) in the next days..
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia 515 problem
Hi, Your attachments have been discarded by the mailing list server. Am 10.11.22 um 21:19 schrieb Stephan Althaus: On 11/9/22 17:34, Stephan Althaus wrote: On 11/9/22 13:40, Udo Grabowski (IMK) wrote: On 09/11/2022 13:04, Stephan Althaus wrote: On 11/9/22 13:02, Udo Grabowski (IMK) wrote: On 09/11/2022 12:22, Udo Grabowski (IMK) wrote: On 09/11/2022 12:14, Udo Grabowski (IMK) wrote: On 09/11/2022 12:08, Stephan Althaus wrote: On 11/9/22 11:32, Marcel Telka wrote: 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-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1: [55] | 10128960| 35|FUNC |GLOB |0 |12 |__glXNvHandShake [61] | 14550512| 24|OBJT |GLOB |0 |22 |glxModuleData [6] | 14550384| 24|OBJT |GLOB |0 |22 |glxserver_nvidiaModuleData $ and 470.141.03 seems to work okay (at least this is my understanding from OP). 470 works. From the running machine with 470 i follow the GLX module from Xorg.0.log like this: $ 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. ,,, Which
Re: [OpenIndiana-discuss] Nvidia 515 problem
Am 09.11.22 um 17:34 schrieb Stephan Althaus: On 11/9/22 13:40, Udo Grabowski (IMK) wrote: On 09/11/2022 13:04, Stephan Althaus wrote: On 11/9/22 13:02, Udo Grabowski (IMK) wrote: On 09/11/2022 12:22, Udo Grabowski (IMK) wrote: On 09/11/2022 12:14, Udo Grabowski (IMK) wrote: On 09/11/2022 12:08, Stephan Althaus wrote: On 11/9/22 11:32, Marcel Telka wrote: 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-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1: [55] | 10128960| 35|FUNC |GLOB |0 |12 |__glXNvHandShake [61] | 14550512| 24|OBJT |GLOB |0 |22 |glxModuleData [6] | 14550384| 24|OBJT |GLOB |0 |22 |glxserver_nvidiaModuleData $ and 470.141.03 seems to work okay (at least this is my understanding from OP). 470 works. From the running machine with 470 i follow the GLX module from Xorg.0.log like this: $ 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. ,,, Which shows the correct vendor, while the non-working says Xorg. Just curious: Did you trigger a 'bootadm update-archiv
Re: [OpenIndiana-discuss] pkg update failed due to Service Unavailable for URL
Am 24.09.22 um 21:02 schrieb Bob Friesenhahn: Today I encountered this problem: weerd:~% pfexec pkg update -rnv Creating Plan (Download Manifests 530/717) | Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: http protocol error: Unknown error code: 503 reason: Service Unavailable URL: 'http://pkg.openindiana.org/hipster/openindiana.org/manifest/0/developer%2Fastdev@0.5.11%2C5.11-2022.0.0.21248%3A20220920T011010Z' Bob This typically happens while a repository is being updated. It should be back after a few minutes. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Old pull illumOS on OI, compared to up to date illumOS
Am 17.09.22 um 10:33 schrieb Handojo via openindiana-discuss: You are right this repository hasn't been updated for years. But that is not a problem as we don't use it at all. Our illumos-gate is being build nightly with the latest PRs. We have a separate jenkins job for this using our components/openindiana/illumos-gate package desription. This clones the original illumos-gate repository. Am i correct to notice that the illumOS in OI was the one that was pulled 8 years ago ? Branches · OpenIndiana/illumos-gate | | | | | | | | | | | Branches · OpenIndiana/illumos-gate Community developed and maintained version of the OS/Net consolidation - Branches · OpenIndiana/illumos-gate | | | The Last Updated illumOS was 2 years ago Branches · illumos/illumos-gate | | | | | | | | | | | Branches · illumos/illumos-gate An open-source Unix operating system. Contribute to illumos/illumos-gate development by creating an account on G... | | | ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Strange (?) error
The problem has been solved by erwinlem: https://github.com/OpenIndiana/oi-userland/pull/8605 Am 01.06.22 um 17:09 schrieb Aurélien Larcher: Your problem is that boost is compiler as 32 and 64 bits and your program expects to find 64-bit versions where we install the 32-bit. You should pass an environment variable to indicate where the cmake files for the 64-bit version live: /usr/lib/amd64. It is a similar recipe as for PKG_CONFIG_PATH probably. On Tue, May 31, 2022 at 7:21 PM Apostolos Syropoulos via openindiana-discuss wrote: The maintainer of apgnasm answered as follows to the same question: I'm afraid I can't offer much help with non-Linux OS's, but this right here: but it set boost_program_options_FOUND to FALSE so package "boost_program_options" is considered to be NOT FOUND Indicates to me that what's being found is basically a "dummy" configuration file which is intentionally setting that to false because either that functionality isn't available or it's intentionally being disabled. I'm not sure how package management is done on that system but you may want to try to either install the actual Boost program options package or if it is installed try reconfiguring it or re-installing it. So I am wondering if the person who actually compiles could help me to resolve this problem? Kind regards, Apostolos --Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Flag day: python mediator changed
Hi all, Today we have merged some changes regarding our pythons. Before these changes we had two python related mediators, named python and python3. As python version 2.x reached end-of-line some time ago and dealing with two mediators was error-prone we decided to get rid of one of them. With these changes the mediator named python3 has been completely removed. When you update your installation there will only be the meditor named python left for python related mediator settings. You may want to check its actual value: pkg mediator python Most probably its value will be 2.7. With this setting /usr/bin/python is a symlink to python2.7. Maybe you want to change this to a more modern python version, eg. pfexec pkg set-mediator -V3.9 python We intend to remove python2.7 in the near future. You need to be aware that setting the python mediator to 2.7 may not result in what you expect. Many mediated links have already been removed for python2.7 packages and changing the python mediator settings to 2.7 may leave your system without some symlinks. Thus, if you still rely on python2.7 you shouldn't change the mediator settings and keep it at 2.7. You won't be able to completely return to it. Most users may want to change it to one of our python3 versions, though. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] image-update fails with python mediator errors
Am 06.07.22 um 00:23 schrieb Philip Kime: pkg update -n -v userland-incorporation@0.5.11-2022.0.0.15875 Creating Plan (Solver setup): -pkg update: No matching version of consolidation/userland/userland-incorporation can be installed: Reject: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15875 Reason: No version matching 'incorporate' dependency mate_install@0.1-2022.0.0.49 can be installed Reject: pkg://openindiana.org/mate_install@0.1-2022.0.0.49 Reason: All acceptable versions of 'require' dependency on runtime/perl-522/module/sun-solaris are obsolete PK — Dr Philip Kime On Tue, Jul 5, 2022 at 22:05, Marcel Telka wrote: mate_install can safely be uninstalled. It is just a meta-package that forces the installation of all Mate related packages. After installation it's not needed anymore. On Tue, Jul 05, 2022 at 07:35:40PM +, Philip Kime wrote: Getting further now - after first reboot after pkg update, reboot, tried to run pkg update again and: -- pkg update -v Creating Plan (Running solver): | pkg update: No solution was found to satisfy constraints No solution found to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11,5.11-2022.0.0.15904:20220704T165022Z Dependency analysis is unable to determine the cause. Try specifying expected versions to obtain more detailed error messages. Try this: pkg update -n -v userland-incorporation@0.5.11-2022.0.0.15875 -- +---+ | 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 mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Latest update problems should be fixed now
Am 30.06.22 um 23:32 schrieb Marcel Telka: On Thu, Jun 30, 2022 at 11:25:05PM +0200, Andreas Wacknitz wrote: I get enough recommendations for things that should be improved. But with too few helping hands it's hard keep the status quo let alone to improve things. Thank you for your work, Andreas. You are welcome. It was never intended by me to become "the" OpenIndiana maintainer. My world was almost perfect when Michal, Alexander and Aurélien were still active. I was like most of my actual helpers are now: I updated or added a package every once in a while. Aurélien and Alexander taught me what I needed at that time. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Latest update problems should be fixed now
Am 30.06.22 um 23:00 schrieb Joshua M. Clulow via openindiana-discuss: On Thu, 30 Jun 2022 at 12:32, Andreas Wacknitz wrote: Am 30.06.22 um 20:56 schrieb Joshua M. Clulow via openindiana-discuss: Is there some way that we can gate future publishing to the public repository on a successful test install/update? We need more volunteers as I already stated several times in the past. I am doing most of everything with only very few helpers. I try to test all PR's but my time and test environment is limited. Besides me it is quite seldom that anybody is testing anything. The situation is similar in all areas of the project you can imagine. In the past I have been waiting for others to do tests but that happened only very rarely and typically with days to weeks of delays. So, to be clear, my question is not about looking for more manual testing. I know we're all limited in time and resources. I was more trying to ask about automated testing we could have done. Presumably there's already automation (Jenkins?) that does the build, and then publishes the packages. Agnar and toasterson are working in that area for some time already. But it already took months to get where we are now and will probably take some more months to be usable. The first results you can already find in the PR process - there is an automated integration test. Alas the results are not yet helpful because of too many limitations. The test builds already take place in zones but there is no notion of dependencies yet so only single packages will be build. And there are no automatic updates like they happen on the official build system as part of each jenkins job (with osnet-incorporation frozen to avoid problems). It seems like it would be good if it was also able to create an ephemeral VM, then log in and use pkg to install the built bits (to make sure they can be installed), then reboot and make sure the machine at least comes up (as a basic smoke test). If that all succeeds, _then_ push the packages to the public repository. The problem of testing is more complex for some packages, eg. we have dependencies to consider when we update Mate packages. This is one of the areas where we need improvements for the already available automatic integration tests. The python eco system is a nightmare with baselining almost impossible because some packages have contradicting requirements, everything is in constant flux, ... Hopefully having that automated would not then require a bunch of extra hands-on manual work for each PR? As I wrote before: we are lacking volunteers who help. With only one active admin it is hard to keep everything in a working condition. With only one active tester it's hard (almost impossible) to test thoroughly. I get enough recommendations for things that should be improved. But with too few helping hands it's hard keep the status quo let alone to improve things. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Latest update problems should be fixed now
Am 30.06.22 um 20:56 schrieb Joshua M. Clulow via openindiana-discuss: On Thu, 30 Jun 2022 at 10:46, Andreas Wacknitz wrote: The problems you probably had during the last days should be fixed now. That includes the default perl problem (and the resulting non-working intrd service) and the update python problems due to contradicting mediator settings. Sorry for the inconveniences. Thanks for fixing it up! Is there some way that we can gate future publishing to the public repository on a successful test install/update? We need more volunteers as I already stated several times in the past. I am doing most of everything with only very few helpers. I try to test all PR's but my time and test environment is limited. Besides me it is quite seldom that anybody is testing anything. The situation is similar in all areas of the project you can imagine. In the past I have been waiting for others to do tests but that happened only very rarely and typically with days to weeks of delays. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Latest update problems should be fixed now
Hi all, The problems you probably had during the last days should be fixed now. That includes the default perl problem (and the resulting non-working intrd service) and the update python problems due to contradicting mediator settings. Sorry for the inconveniences. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] idle3.9 not working
Am 25.06.22 um 22:52 schrieb Andreas Wacknitz: Am 24.06.22 um 12:31 schrieb Apostolos Syropoulos via openindiana-discuss: Hello, I have just updated a computer of mine and idle3.9 does not work: apostolo@nadya:~$ idle3.9 Traceback (most recent call last): File "/usr/bin/idle3.9", line 3, in from idlelib.pyshell import main File "/usr/lib/python3.9/idlelib/pyshell.py", line 53, in from idlelib.editor import EditorWindow, fixwordbreaks File "/usr/lib/python3.9/idlelib/editor.py", line 30, in from idlelib.util import py_extensions ModuleNotFoundError: No module named 'idlelib.util' I think this is a packaging problem (the maintainer of the packageprobably forgot to include the missing file). Could someone havea look at it? Kind regards, Apostolos --Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have created a new package revision with a fix. You should be able to run it after another pkg update. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] idle3.9 not working
Am 24.06.22 um 12:31 schrieb Apostolos Syropoulos via openindiana-discuss: Hello, I have just updated a computer of mine and idle3.9 does not work: apostolo@nadya:~$ idle3.9 Traceback (most recent call last): File "/usr/bin/idle3.9", line 3, in from idlelib.pyshell import main File "/usr/lib/python3.9/idlelib/pyshell.py", line 53, in from idlelib.editor import EditorWindow, fixwordbreaks File "/usr/lib/python3.9/idlelib/editor.py", line 30, in from idlelib.util import py_extensions ModuleNotFoundError: No module named 'idlelib.util' I think this is a packaging problem (the maintainer of the packageprobably forgot to include the missing file). Could someone havea look at it? Kind regards, Apostolos --Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I can confirm the problem. I will have a look at it as time permits. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Bad package in hipster repo: pkg://openindiana.org/security/softhsm
Am 16.06.22 um 10:37 schrieb Predrag Zečević via openindiana-discuss: On 6/16/22 00:36, Bill Sommerfeld wrote: On 6/15/22 3:32 PM, Till Wegmueller wrote: Is this happening everytime or just once? It's happened every time I've tried today. The error can happen during a package builde from jenkins if you are very unlucky. illumos-gate is built during 24:00 GMT so that could be a bigger upload that triggers this. Does it happen always with the same package? Always the same package. Can you try once more in an hour or so? Will do.. Still wrong (this morning): :; pkg contents -r softhsm Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/security/softhsm@2.6.1,5.11-2022.0.0.0:20220424T205931Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/security/softhsm@2.6.1,5.11-2022.0.0.0:20220424T205931Z expected: 92cf41000efc6a55b2488aee9df9fd6700ffb913 computed: 86a6c734f14799f21fd3438e655af8874eb55414. (happened 4 times) Regards ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have released a new package revision. So that issue should be fixed now. Thanks for the hint. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem updating
Am 11.06.22 um 23:40 schrieb Apostolos Syropoulos via openindiana-discuss: Hello, Today I tried to update OI to see whether automount wotks. However, when the system booted Igot many errors related to svc services and it was saying something about cycling. I have not deletedthe new BE but it is not functional. Can anybody let me know if he/she encountered the same problem? Regards, Apostolos --Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss We had a discussion about service dependency cycles before. The introduction of varpd gave problems in some situations. You system may have an outdated service that now creates this cycle. In the past it was metainit, which has been removed long ago. You should check the root cause of your dependency cycle and disable or remove it. Regarding metainit we have some release notes from a former release: http://docs.openindiana.org/release-notes/2017.04-release-notes/ Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libtclsqlite3 error
Am 08.05.22 um 20:37 schrieb Stefan:
Hello Andreas,
thanks for the 64bit library.
Unfortunately it doesn't still work. Now I get the following error
messages:
Error in startup script: couldn't load file
"/usr/lib/amd64/sqlite3/libtclsqlite3.so": ld.so.1: wish8.6: fatal:
relocation error: file /usr/lib/amd64/sqlite3/libtclsqlite3.so: symbol
sqlite3_prepare_v3: referenced symbol not found
while executing
"load /usr/lib/amd64/sqlite3/libtclsqlite3.so sqlite3"
("package ifneeded sqlite3 3.38.5" script)
invoked from within
"package require sqlite3"
Hm, there also seems to be another package delivering the 64-bit library:
pkg update: The following packages all deliver file actions to
usr/lib/amd64/sqlite3/libtclsqlite3.so:
pkg://openindiana.org/runtime/tcl-8/tcl-sqlite-3@3.38.5,5.11-2022.0.0.1:20220508T182405Z
pkg://openindiana.org/database/sqlcipher@4.5.1,5.11-2022.0.0.0:20220309T191835Z
These packages cannot be installed together. Any non-conflicting subset
of the above packages can be installed.
I need to investigate further. So we have two problems to solve. Can you
provide a minimal tcl file that uses the library so I can test it?
I don't have any tcl experience yet.
Andreas
Best regards
Stefan
Betreff: Re: [OpenIndiana-discuss] libtclsqlite3 error
Datum: Sun, 8 May 2022 19:22:27 +0200
Von: Andreas Wacknitz
Antwort an: Discussion list for OpenIndiana
An: openindiana-discuss@openindiana.org
Am 08.05.22 um 18:35 schrieb Stefan:
Hello,
my financial accounting software is written in Tcl/Tk and needs
libtclsqlite3.so.
I usually use this software on a linux box but I try to get it run on
openindiana.
I tried it a few months ago and it worked.
Now I did a fresh install with the 202110 iso image in virtualbox and it
doesn't
work anymore. When I start the software I get the following error
messages:
Error in startup script: couldn't load file
"/usr/lib/tcl8.6/sqlite3/libtclsqlite3.so": ld.so.1: wish8.6: fatal:
/usr/lib/tcl8.6/sqlite3/libtclsqlite3.so: wrong ELF class: ELFCLASS32
while executing
"load /usr/lib/tcl8.6/sqlite3/libtclsqlite3.so sqlite3"
("package ifneeded sqlite3 3.38.5" script)
invoked from within
"package require sqlite3"
Seems that the 64bit package is missing. There is no amd64 directory
under
/usr/lib/tcl8.6/sqlite3
What can I do to get the 64bit libtclsqlite3.so?
I made a mistake when I updated the sqlite-3 packages some time ago. I
have created a fix and it's building now.
It should be available in about 30 minutes. When you update then the
64-bit libraries should be back.
Regards,
Andreas
Thanks a lot
Stefan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libtclsqlite3 error
Am 08.05.22 um 18:35 schrieb Stefan:
Hello,
my financial accounting software is written in Tcl/Tk and needs
libtclsqlite3.so.
I usually use this software on a linux box but I try to get it run on
openindiana.
I tried it a few months ago and it worked.
Now I did a fresh install with the 202110 iso image in virtualbox and it
doesn't
work anymore. When I start the software I get the following error
messages:
Error in startup script: couldn't load file
"/usr/lib/tcl8.6/sqlite3/libtclsqlite3.so": ld.so.1: wish8.6: fatal:
/usr/lib/tcl8.6/sqlite3/libtclsqlite3.so: wrong ELF class: ELFCLASS32
while executing
"load /usr/lib/tcl8.6/sqlite3/libtclsqlite3.so sqlite3"
("package ifneeded sqlite3 3.38.5" script)
invoked from within
"package require sqlite3"
Seems that the 64bit package is missing. There is no amd64 directory
under
/usr/lib/tcl8.6/sqlite3
What can I do to get the 64bit libtclsqlite3.so?
I made a mistake when I updated the sqlite-3 packages some time ago. I
have created a fix and it's building now.
It should be available in about 30 minutes. When you update then the
64-bit libraries should be back.
Regards,
Andreas
Thanks a lot
Stefan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nvidia driver causes immediate kernel panic with NVS 510
Am 01.05.22 um 18:24 schrieb James Madgwick: Hi, I have a problem with Nvidia. I don't think there's much that can be done about it, but I thought it would be worth mentioning in case anyone else has experienced this before and in case anyone is looking for a workaround in future. I did a fresh installation of 2021.10 on an Z77 system which has an Nvidia Quadro NVS 510 GPU. I initially tried the GUI version but fell back to the text version because the GUI rebooted straight after the language selection (this was the panic). After installation, I realised the problem was with the Nvidia driver. A few seconds after X is launched, there's a kernel panic. It gets as far as a showing a white square in the top left of the screen. Xorg.0.log is empty. The version of the Nvidia driver installed by default apparently support this GPU (Kepler). I worked around the issue by creating an xorg.conf which specifies the 'vesa' driver and not 'nvidia' (as used by default). This works and MATE starts and works as expected (although with 800x600) - the problem seems to be with the nvidia module. I imagine the way forward would be to report the problem to Nvidia seeing as the driver is closed source. I doubt they would be interested though due to the age of this GPU (Kepler consumer GeForce is now unsupported). James Madgwick ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Maybe https://www.nvidia.com/en-us/drivers/unix/solaris-display-archive/ will help you. Looking at what we have now as alternative NVIDIA drivers, both -460 and -470 should support your graphics card. You may want to experiment with the alternatives. There is some documentation on how to switch to a different NVIDIA driver on OI. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ssh -X mate-terminal error
Am 25.04.22 um 19:51 schrieb Stephan Althaus: Hello! This does not work anymore: ssh -X mate-terminal .. from an OI box to another OI box. It works between a Linux vm (ubuntu impish) and the OI boxes in both directions. I successfully tried this. Make sure it's not caused by your user's configuration. I recommend to try it with newly created accounts. Andreas Error Message is: $ ssh 192.168.2.52 -X mate-terminal (mate-terminal:4778): Gdk-ERROR **: 19:47:32.619: The program 'mate-terminal' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 178 error_code 16 request_code 72 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) It does not work on localhost either. I did not manage to place the variable GDK_SYNCHRONIZE=1 at the right place it seems :-/ Any hints ? Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1
Am 10.04.22 um 20:53 schrieb Gary Mills: On Sun, Apr 10, 2022 at 08:10:56PM +0200, Andreas Wacknitz wrote: As the subject says, I have recently integrated a new version of openssh. You may need to reboot your machine in order to make the update work. Isn't there something in the P5M file that says that the svc:/network/ssh:default service needs to be restarted after the update? No, not yet. Feel free to add something. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1
As the subject says, I have recently integrated a new version of openssh. You may need to reboot your machine in order to make the update work. Otherwise connection attempts may end in messages like this: kex_exchange_identification: Connection closed by remote host Connection closed by port 22 Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 10.04.22 um 14:57 schrieb Stephan Althaus: On 4/10/22 14:29, Andreas Wacknitz wrote: Am 10.04.22 um 11:46 schrieb Andreas Wacknitz: Am 10.04.22 um 11:23 schrieb Stephan Althaus: On 4/10/22 11:12, Stephan Althaus wrote: On 4/10/22 10:52, Andreas Wacknitz wrote: Am 10.04.22 um 10:47 schrieb Stephan Althaus: On 4/10/22 09:56, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio I have investigated further and found out that we have some actual problems with old packages that have been replaced in the past. The problems became imminent after illumos-gate has merged #14583 developer/opensolaris/osnet requirements cleanup and after shrinking the repository. So far I have identified three: file/slocate runtime/java service/network/ftp and replaced the fmri's with their replacements mlocate, openjdk8 and proftpd. There might be more outdated fmri's left that need to be fixed, though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! There are some packages mentioned that are not in "2022": This should not be a problem. They just haven't been build this year yet. But you need to make sure that they are still in the repository, though. Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0 and are in the userland-incorporation meta package. # zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022 Reject: pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z Reject: pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z Reject: pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z Reject: pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z Reject: pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z Reject: pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z Reject: pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z Reject: pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z Reject: pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z Reject: pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z Reject: pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z Reject: pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z Reject: pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z Reject: pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z Thank you for having a look at it! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hmm... gnu-tar is a pkg from 2020 $ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip' pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z From the manifest of gnu.tar: (source: pkg.openindiana.org/) dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0 type=require Maybe this type of dependency is the reason why the zone install fails, as that required old gzip package is no more available... ??? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.or
Re: [OpenIndiana-discuss] can't install a new zone
Am 10.04.22 um 11:46 schrieb Andreas Wacknitz: Am 10.04.22 um 11:23 schrieb Stephan Althaus: On 4/10/22 11:12, Stephan Althaus wrote: On 4/10/22 10:52, Andreas Wacknitz wrote: Am 10.04.22 um 10:47 schrieb Stephan Althaus: On 4/10/22 09:56, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio I have investigated further and found out that we have some actual problems with old packages that have been replaced in the past. The problems became imminent after illumos-gate has merged #14583 developer/opensolaris/osnet requirements cleanup and after shrinking the repository. So far I have identified three: file/slocate runtime/java service/network/ftp and replaced the fmri's with their replacements mlocate, openjdk8 and proftpd. There might be more outdated fmri's left that need to be fixed, though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! There are some packages mentioned that are not in "2022": This should not be a problem. They just haven't been build this year yet. But you need to make sure that they are still in the repository, though. Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0 and are in the userland-incorporation meta package. # zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022 Reject: pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z Reject: pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z Reject: pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z Reject: pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z Reject: pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z Reject: pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z Reject: pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z Reject: pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z Reject: pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z Reject: pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z Reject: pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z Reject: pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z Reject: pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z Reject: pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z Thank you for having a look at it! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hmm... gnu-tar is a pkg from 2020 $ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip' pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z From the manifest of gnu.tar: (source: pkg.openindiana.org/) dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0 type=require Maybe this type of dependency is the reason why the zone install fails, as that required old gzip package is no more available... ??? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Ah! The dependency in gnu-tar is not correct
Re: [OpenIndiana-discuss] can't install a new zone
Am 10.04.22 um 11:23 schrieb Stephan Althaus: On 4/10/22 11:12, Stephan Althaus wrote: On 4/10/22 10:52, Andreas Wacknitz wrote: Am 10.04.22 um 10:47 schrieb Stephan Althaus: On 4/10/22 09:56, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio I have investigated further and found out that we have some actual problems with old packages that have been replaced in the past. The problems became imminent after illumos-gate has merged #14583 developer/opensolaris/osnet requirements cleanup and after shrinking the repository. So far I have identified three: file/slocate runtime/java service/network/ftp and replaced the fmri's with their replacements mlocate, openjdk8 and proftpd. There might be more outdated fmri's left that need to be fixed, though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! There are some packages mentioned that are not in "2022": This should not be a problem. They just haven't been build this year yet. But you need to make sure that they are still in the repository, though. Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0 and are in the userland-incorporation meta package. # zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022 Reject: pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z Reject: pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z Reject: pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z Reject: pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z Reject: pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z Reject: pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z Reject: pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z Reject: pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z Reject: pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z Reject: pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z Reject: pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z Reject: pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z Reject: pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z Reject: pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z Thank you for having a look at it! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hmm... gnu-tar is a pkg from 2020 $ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip' pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z From the manifest of gnu.tar: (source: pkg.openindiana.org/) dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0 type=require Maybe this type of dependency is the reason why the zone install fails, as that required old gzip package is no more available... ??? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Ah! The dependency in gnu-tar is not correct, because the version of gzip is mentioned:
Re: [OpenIndiana-discuss] can't install a new zone
Am 10.04.22 um 10:47 schrieb Stephan Althaus: On 4/10/22 09:56, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio I have investigated further and found out that we have some actual problems with old packages that have been replaced in the past. The problems became imminent after illumos-gate has merged #14583 developer/opensolaris/osnet requirements cleanup and after shrinking the repository. So far I have identified three: file/slocate runtime/java service/network/ftp and replaced the fmri's with their replacements mlocate, openjdk8 and proftpd. There might be more outdated fmri's left that need to be fixed, though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! There are some packages mentioned that are not in "2022": This should not be a problem. They just haven't been build this year yet. But you need to make sure that they are still in the repository, though. Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0 and are in the userland-incorporation meta package. # zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022 Reject: pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z Reject: pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z Reject: pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z Reject: pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z Reject: pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z Reject: pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z Reject: pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z Reject: pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z Reject: pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z Reject: pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z Reject: pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z Reject: pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z Reject: pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z Reject: pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z Thank you for having a look at it! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio I have investigated further and found out that we have some actual problems with old packages that have been replaced in the past. The problems became imminent after illumos-gate has merged #14583 developer/opensolaris/osnet requirements cleanup and after shrinking the repository. So far I have identified three: file/slocate runtime/java service/network/ftp and replaced the fmri's with their replacements mlocate, openjdk8 and proftpd. There might be more outdated fmri's left that need to be fixed, though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 20:19 schrieb Andreas Wacknitz: Am 09.04.22 um 20:07 schrieb Stephan Althaus: On 4/9/22 19:33, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio So, your system is really updated but your zoneadm tries to use fairly outdated packages. Sorry, I won't be a big help here as I don't use ipkg branded zones. I can only recommend to check whether system-repository is enabled and working (svcs system-repository) and to check your actual publishers (pkg publisher). Andreas Il 09/04/2022 18:34 Andreas Wacknitz ha scritto: Sorry, I made a mistake. Please use pkg info userland-incorporation (without "-r" which means remote) in order to get information about your local userland-incorporation. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! I tried to use the oi-userland scripts to set up a build zone, and i am facing the same issue, even with zone brand ipkg. I checked entire and userland-incorporation. Entire seems old: $ pkg info entire Name: entire Summary: incorporation to lock all system packages to same build (empty package) Description: incorporation to lock all system packages to same build (empty package) State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2020.0.1.0 * Packaging Date: March 30, 2020 at 03:17:13 PM** **Last Install Time: April 10, 2020 at 07:22:18 PM* Size: 0.00 B FMRI: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z The entire package is more than one year old. This looks wrong. It is correct. entire is just a meta package that requires userland-incorporation. $ pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org origin online F http://pkg.openindiana.org/hipster/ hipster-encumbered (non-sticky) origin online F https://pkg.openindiana.org/hipster-encumbered/ # zonecfg -z bz-template export create -b set zonepath=/zones/bz-template set brand=ipkg set autoboot=false set ip-type=shared Greetings, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 20:07 schrieb Stephan Althaus: On 4/9/22 19:33, Andreas Wacknitz wrote: Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio So, your system is really updated but your zoneadm tries to use fairly outdated packages. Sorry, I won't be a big help here as I don't use ipkg branded zones. I can only recommend to check whether system-repository is enabled and working (svcs system-repository) and to check your actual publishers (pkg publisher). Andreas Il 09/04/2022 18:34 Andreas Wacknitz ha scritto: Sorry, I made a mistake. Please use pkg info userland-incorporation (without "-r" which means remote) in order to get information about your local userland-incorporation. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! I tried to use the oi-userland scripts to set up a build zone, and i am facing the same issue, even with zone brand ipkg. I checked entire and userland-incorporation. Entire seems old: $ pkg info entire Name: entire Summary: incorporation to lock all system packages to same build (empty package) Description: incorporation to lock all system packages to same build (empty package) State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2020.0.1.0 * Packaging Date: March 30, 2020 at 03:17:13 PM** **Last Install Time: April 10, 2020 at 07:22:18 PM* Size: 0.00 B FMRI: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z The entire package is more than one year old. This looks wrong. $ pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org origin online F http://pkg.openindiana.org/hipster/ hipster-encumbered (non-sticky) origin online F https://pkg.openindiana.org/hipster-encumbered/ # zonecfg -z bz-template export create -b set zonepath=/zones/bz-template set brand=ipkg set autoboot=false set ip-type=shared Greetings, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss: No problem Andreas, it is at 15370 $ pkg info userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Last Install Time: Sun Oct 31 19:39:21 2021 Last Update Time: Sat Apr 9 12:01:18 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Regards. Maurilio So, your system is really updated but your zoneadm tries to use fairly outdated packages. Sorry, I won't be a big help here as I don't use ipkg branded zones. I can only recommend to check whether system-repository is enabled and working (svcs system-repository) and to check your actual publishers (pkg publisher). Andreas Il 09/04/2022 18:34 Andreas Wacknitz ha scritto: Sorry, I made a mistake. Please use pkg info userland-incorporation (without "-r" which means remote) in order to get information about your local userland-incorporation. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 18:30 schrieb Maurilio Longo via openindiana-discuss: Hi Andreas, mine is reported as newer than 15370. $ pkg info -r userland-incorporation Sorry, I made a mistake. Please use pkg info userland-incorporation (without "-r" which means remote) in order to get information about your local userland-incorporation. Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Not installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15372 Packaging Date: Sat Apr 9 13:24:12 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15372:20220409T132412Z Regards Maurilio Il 09/04/2022 18:16 Andreas Wacknitz ha scritto: Something prohibits to update to the latest bits. What does "pkg info userland-incorporation" output? Here it is ─➤ pkg info -r userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Not installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Make sure your userland-incorporation is at this version or newer. If it is older try to install it explicitly and see what prevents its update: pfexec pkg install userland-incorporation@0.5.11-2022.0.0.15370 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't install a new zone
Am 09.04.22 um 18:10 schrieb Maurilio Longo via openindiana-discuss: Hi, I've just updated an Openindiana 2021.10 system with a # pkg refresh --full # pkg update $ uname -a SunOS st-ar-01 5.11 illumos-041297c2d6 i86pc i386 i86pc illumos because, after a few years from the last time I did install one, I could not install a new zone due to missing dependencies, but the problem stays the same. $ pfexec zoneadm -z ztc install A ZFS file system has been created for this zone. Sanity Check: Looking for 'entire' incorporation. Image: Preparing at /nas/zones/ztc/root. Publisher: Using openindiana.org (http://pkg.openindiana.org/hipster/). Cache: Using /var/pkg/publisher. Installing: Packages (output follows) Creating Plan (Running solver): - pkg install: No matching version of compress/zip can be installed: Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122ZReason: No version matching 'require' dependency compress/bzip2@1.0.8-2020.0.1.0 can be installedReject: pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433ZReason: No version matching 'require' dependency SUNWcs@0.5.11-2020.0.1.19548 can be installed ... an so on and so forth for tens of different packages ?!? The zone config is as bare I can get it $ zonecfg -z ztc info zonename: ztc zonepath: /nas/zones/ztc brand: ipkg autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: exclusive hostid: fs-allowed: net: address not specified allowed-address not specified physical: vnztc0 defrouter not specified Is it still possibile to run zones on current Openindiana or am I doing something wrong? Regards. Maurilio ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Something prohibits to update to the latest bits. What does "pkg info userland-incorporation" output? Here it is ─➤ pkg info -r userland-incorporation Name: consolidation/userland/userland-incorporation Summary: userland consolidation incorporation (consolidation/userland/userland-incorporation) Description: This incorporation constrains packages from the userland consolidation Category: Meta Packages/Incorporations State: Not installed Publisher: openindiana.org Version: 0.5.11 Branch: 2022.0.0.15370 Packaging Date: Sat Apr 9 09:53:00 2022 Size: 0.00 B FMRI: pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z Make sure your userland-incorporation is at this version or newer. If it is older try to install it explicitly and see what prevents its update: pfexec pkg install userland-incorporation@0.5.11-2022.0.0.15370 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] geany editor?
Am 28.03.22 um 02:02 schrieb Jason Martin: Just a heads up. I was using this package before my disk space problem. I uninstalled and then re-installed but I still get this error. agrellum@openindiana:~$ geany ld.so.1: geany: fatal: relocation error: file /usr/lib/libgeany.so.0: symbol g_get_os_info: referenced symbol not found Killed ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Folks, I have created a PR for glib-2.70.0: https://github.com/OpenIndiana/oi-userland/pull/7958 Please build it for yourself and test it. It works for me (I have successfully tried to hot-plug a keyboard, a mouse, and an USB data stick). With this geany also works again. If it doesn't work for you, then we'll also need two simple patches for our hal which have been introduced for Solaris. I have a local illumos-gate build with them. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] geany editor?
Am 28.03.22 um 15:34 schrieb Peter Tribble: On Mon, Mar 28, 2022 at 2:06 PM Andreas Wacknitz wrote: Am 28.03.22 um 02:02 schrieb Jason Martin: agrellum@openindiana:~$ geany ld.so.1: geany: fatal: relocation error: file /usr/lib/libgeany.so.0: symbol g_get_os_info: referenced symbol not found Killed It looks like geany needs a rebuild after our necessary downgrade of glib to 2.62.6. Yes, it picked up g_get_os_info which came in with 2.64 Alas, geany doesn't compile with this old glib version. Hm. Builds and runs for me (on Tribblix) against glib 2.56.4 and geany itself only claims to want glib 2.32.0, so it ought to be OK. Then we are missing a patch: In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /export/home/andreas/oi-userland/components/editor/geany/geany-1.38/scintilla/gtk/ScintillaGTK.cxx:22: /usr/include/glib-2.0/glib/gtypes.h: In function 'gboolean _GLIB_CHECKED_ADD_U64(guint64*, guint64, guint64)': /usr/include/glib-2.0/glib/gmacros.h:738:31: error: '_Static_assert' was not declared in this scope #define G_STATIC_ASSERT(expr) _Static_assert (expr, "Expression evaluates to false") ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] geany editor?
Am 28.03.22 um 02:02 schrieb Jason Martin: Just a heads up. I was using this package before my disk space problem. I uninstalled and then re-installed but I still get this error. agrellum@openindiana:~$ geany ld.so.1: geany: fatal: relocation error: file /usr/lib/libgeany.so.0: symbol g_get_os_info: referenced symbol not found Killed It looks like geany needs a rebuild after our necessary downgrade of glib to 2.62.6. Alas, geany doesn't compile with this old glib version. Thus, we need to fix our problems with newer glib versions before geany will be working again. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Need to update but not enough disk space
Am 26.03.22 um 18:20 schrieb Jason Martin: Disk does not appear to be full from my data in my $HOME When I run: zfs list -t all -r rpool What are the items with name@datestamp? These are snapshots belonging to boot environment. "beadm list" will show your boot environments. You can delete older boot environments with "pfexec beadm destroy ". With that the corresponding snapshot should also vanish. Alas there is at least one bug that prevents from the deletion of the corresponding snapshot sometimes. Then you can delete a snapshot with "pfexec zfs destroy rpool/ROOT/openindiana-2022:03:18@datestamp" BTW: openindiana-2022:03:18 is you active boot environment. How do I safely clean them up? NAME USED AVAIL REFER MOUNTPOINT rpool 42.4G 698M 33K /rpool rpool/ROOT 38.2G 698M 24K legacy rpool/ROOT/openindiana 14.7M 698M 7.25G / rpool/ROOT/openindiana-2022:03:17 18.0M 698M 11.1G / rpool/ROOT/openindiana-2022:03:18 38.2G 698M 11.2G / rpool/ROOT/openindiana-2022:03:18@install 208M - 5.95G - rpool/ROOT/openindiana-2022:03:18@2022-02-12-12:30:52 298K - 6.42G - rpool/ROOT/openindiana-2022:03:18@2022-02-12-12:58:04 6.60M - 7.25G - rpool/ROOT/openindiana-2022:03:18@2022-02-14-02:27:04 1018M - 10.5G - rpool/ROOT/openindiana-2022:03:18@2022-02-16-12:09:24 1005M - 10.6G - rpool/ROOT/openindiana-2022:03:18@2022-02-17-08:43:56 992M - 10.7G - rpool/ROOT/openindiana-2022:03:18@2022-02-18-10:55:47 995M - 10.8G - rpool/ROOT/openindiana-2022:03:18@2022-02-21-01:36:39 1019M - 10.9G - rpool/ROOT/openindiana-2022:03:18@2022-02-22-12:15:16 1.00G - 11.5G - rpool/ROOT/openindiana-2022:03:18@2022-02-24-11:12:32 1.00G - 11.6G - rpool/ROOT/openindiana-2022:03:18@2022-02-25-12:35:55 1.02G - 11.7G - rpool/ROOT/openindiana-2022:03:18@2022-02-27-03:20:18 1.03G - 11.8G - rpool/ROOT/openindiana-2022:03:18@2022-03-01-12:56:25 1.03G - 11.9G - rpool/ROOT/openindiana-2022:03:18@2022-03-03-02:46:01 1.03G - 12.0G - rpool/ROOT/openindiana-2022:03:18@2022-03-07-13:25:01 1.04G - 12.2G - rpool/ROOT/openindiana-2022:03:18@2022-03-09-02:09:08 1.64G - 12.6G - rpool/ROOT/openindiana-2022:03:18@2022-03-17-12:35:34 1.12G - 15.5G - rpool/ROOT/openindiana-2022:03:18@2022-03-18-11:57:12 15.7M - 15.6G - rpool/ROOT/openindiana-2022:03:18@2022-03-18-12:06:41 295M - 15.9G - rpool/dump 1.75G 698M 1.75G - rpool/export 565M 698M 24K /export rpool/export/home 565M 698M 24K /export/home rpool/export/home/agrellum 565M 698M 565M /export/home/agrellum rpool/swap 1.86G 2.29G 261M - ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] samba package needs a maintainer
Hi all, our samba package doesn't build at the moment. It fails in the 64-bit part probably because of a missing flag. Alas this prevents for fixing man page collisions that have been introduced by an update of illumogs-gate (IPD4). I have stopped our nightly illumos-gate builds at rhe moment because of this but we need to find a solution for it soon. When the jenkins job will be ra-activated before we have a solution either everybody needs to uninstall samba or we need to obsolete the samba package. Short: We need to find a maintainer for the samba package otherwise it's doomed for OI. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Future of PostgreSQL on OpenIndiana
Hi all, at the moment PostgreSQL 9.6 is our version that is being used for all packages that need PostgreSQL. This version is not supported upstream for some months now. The oldest supported version is 10 and this would be the obvious new version to use for us. Alas, obsoleting a PostgreSQL version in OpenIndiana means some work to be done and it looks like nobody is interested enough to do this work regularly. So, my question is how we should proceed with PostgreSQL. Obsoleting 9.6 and using 10 as our default would mean that in less than 9 months according to https://www.postgresql.org/support/versioning/ we will need to touch PostgreSQL again. We will need a volunteer to do this or we might think about skipping some versions of PostgreSQL now. What is your opinion? Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Don't update now
Am 20.02.22 um 16:35 schrieb Andreas Wacknitz: Hi all, we have a bigger problem with our last openldap update which renders pkg unusable! So, please don't update until we have found a solution for this! It looks as if we have added all missing compatibility links for libraries. It should be safe to update again. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Don't update now
Hi all, we have a bigger problem with our last openldap update which renders pkg unusable! So, please don't update until we have found a solution for this! Sorry for the inconveniences, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] nodejs (npm) problem
Am 07.02.22 um 11:11 schrieb Predrag Zecevic via openindiana-discuss: Hi all, does this happens only to me? :; pkg list | grep nodejs runtime/nodejs-16 16.13.2-2022.0.0.0 i-- :; npm version Error: Cannot find module 'make-fetch-happen' Require stack: - /usr/node/16/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js - /usr/node/16/lib/node_modules/npm/node_modules/pacote/lib/remote.js - /usr/node/16/lib/node_modules/npm/node_modules/pacote/lib/git.js - /usr/node/16/lib/node_modules/npm/node_modules/pacote/lib/fetcher.js - /usr/node/16/lib/node_modules/npm/node_modules/pacote/lib/index.js - /usr/node/16/lib/node_modules/npm/lib/utils/update-notifier.js - /usr/node/16/lib/node_modules/npm/lib/cli.js - /usr/node/16/lib/node_modules/npm/bin/npm-cli.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at Object. (/usr/node/16/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js:6:15) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Module.require (node:internal/modules/cjs/loader:1005:19) Regards. Sorry, that was my fault. The package manifest is missing some files. I will merge a fix soon. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] missing deadkeys in be keyboard
Am 18.01.22 um 17:50 schrieb Marc Lobelle:
Hello Andreas,
Thanks for your answer,
Indeed, in the meantime, I found that the problem was that libreoffice
did not use the selected keyboard but worked through ibus whose daemon
is not running by default. To solve the problem, I had to go through
the mate menus: System>Control center>IBus preferences
then I was prompted t start the daemon, which I accepted
then I started libreoffice and the dead keys worked as in other
applications such as the terminal window or pluma (where they always
worked).
To start this daemon automatically rather than manually as above. I
tried to add /usr/bin/ibus-daemon -d or /usr /usr/bin/ibus-daemon -dr
to the programs to start at start-up in the control center. ibus is
then running but the dead keys do not work in libreoffice. Then I read
on the web that it should be started */usr/bin/ibus-daemon --xim* and
indeed, this way, it works, but xim is reputed to be obsolete*...
*
I have checked "Enable Input Method Framework" in one of the system
settings and selected the only available one: "IBus - Intelligent Input
Bus".
Andreas
**
Best regards
Marc
On 18/01/2022 14:11, Andreas Wacknitz wrote:
Hi,
Mate comes with a keyboard selection tool. You can choose there from
different layouts for Belgian keyboards as I checked now.
As far as I can tell you'll need to start the ibus service to make
the deadkey functionality working. There is also a Mate tool for it.
Andreas
Am 18.01.22 um 11:51 schrieb Marc Lobelle:
Hello everybody,
Apparently, the BE keyboard is decribed in
/usr/share/X11/xkb/symbols/be.
However, the deadkeys are present in this file, as shown below
// based on a keyboard map from an 'xkb/symbols/be' file
default partial alphanumeric_keys
xkb_symbols "basic" {
include "latin"
name[Group1]="Belgian";
key { [ ampersand, 1, bar,
exclamdown ] };
key { [ eacute, 2, at, oneeighth ] };
key { [ quotedbl, 3, numbersign,
sterling ] };
key { [apostrophe, 4, onequarter,
dollar ] };
key { [ parenleft, 5, onehalf,
threeeighths ] };
key { [ section, 6, asciicircum,
fiveeighths ] };
key { [ egrave, 7, braceleft,
seveneighths ] };
key { [ exclam, 8, bracketleft,
trademark ] };
key { [ ccedilla, 9, braceleft,
plusminus ] };
key { [ agrave, 0, braceright,
degree ] };
key { [parenright, degree, backslash,
questiondown ] };
key { [ minus, underscore, dead_cedilla,
dead_ogonek ] };
key { [ a, A, at,
Greek_OMEGA ] };
key { [ z, Z, lstroke, Lstroke
] };
key { [ e, E, EuroSign, cent
] };
key { [ o, O, oe, OE ] }; //
o O œ Œ
key { [dead_circumflex, dead_diaeresis, bracketleft,
dead_abovering ] };
key { [ dollar, asterisk, bracketright,
dead_macron ] };
key { [ q, Q, ae, AE
] };
key { [ m, M, dead_acute,
dead_doubleacute ] };
Thus apparently, the BE keyboard is not the be keyboard described in
/usr/share/X11/xkb/symbols/be.
Does anyone know where the keyboards tha are effectively used are
located and/or how to use the good one, described in
/usr/share/X11/xkb/symbols/be ?
Thanks,
Marc
On 18/01/2022 00:24, Marc Lobelle wrote:
Hello
Apparently there are no dead keys in the BE keyboard. Is there a
way to activate them in order to easily type â in libreoffice for
instance ?
Thanks
Marc
--
Marc Lobelle
professeur émérite
ICTEAM
UCLouvain / SST / ICTEAM / INGI
Place Ste Barbe, 2, bte L5.02.01 - 1348 Louvain-la-Neuve
marc.lobe...@uclouvain.be <mailto:prenom@uclouvain.be>
Tél.+32 (0) 475 494 616
Fax +32 (0) 10 47 51 20
www.uclouvain.be <https://uclouvain.be>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
--
Marc Lobelle
professeur émérite
ICTEAM
UCLouvain / SST / ICTEAM / INGI
Place Ste Barbe, 2, bte L5.02.01 - 1348 Louvain-la-Neuve
marc.lobe...@uclouvain.be <mailto:prenom@uclouvain.be>
Tél.+32 (0) 475 494 616
Fax +32 (0) 10 47 51 20
www.uclouvain.be <https://uclouvain.be>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] missing deadkeys in be keyboard
Hi,
Mate comes with a keyboard selection tool. You can choose there from
different layouts for Belgian keyboards as I checked now.
As far as I can tell you'll need to start the ibus service to make the
deadkey functionality working. There is also a Mate tool for it.
Andreas
Am 18.01.22 um 11:51 schrieb Marc Lobelle:
Hello everybody,
Apparently, the BE keyboard is decribed in /usr/share/X11/xkb/symbols/be.
However, the deadkeys are present in this file, as shown below
// based on a keyboard map from an 'xkb/symbols/be' file
default partial alphanumeric_keys
xkb_symbols "basic" {
include "latin"
name[Group1]="Belgian";
key { [ ampersand, 1, bar,
exclamdown ] };
key { [ eacute, 2, at, oneeighth ] };
key { [ quotedbl, 3, numbersign,
sterling ] };
key { [apostrophe, 4, onequarter,
dollar ] };
key { [ parenleft, 5, onehalf,
threeeighths ] };
key { [ section, 6, asciicircum,
fiveeighths ] };
key { [ egrave, 7, braceleft,
seveneighths ] };
key { [ exclam, 8, bracketleft,
trademark ] };
key { [ ccedilla, 9, braceleft,
plusminus ] };
key { [ agrave, 0, braceright,
degree ] };
key { [parenright, degree, backslash,
questiondown ] };
key { [ minus, underscore, dead_cedilla,
dead_ogonek ] };
key { [ a, A, at,
Greek_OMEGA ] };
key { [ z, Z, lstroke, Lstroke
] };
key { [ e, E, EuroSign, cent
] };
key { [ o, O, oe, OE ] }; //
o O œ Œ
key { [dead_circumflex, dead_diaeresis, bracketleft,
dead_abovering ] };
key { [ dollar, asterisk, bracketright,
dead_macron ] };
key { [ q, Q, ae, AE ] };
key { [ m, M, dead_acute,
dead_doubleacute ] };
Thus apparently, the BE keyboard is not the be keyboard described in
/usr/share/X11/xkb/symbols/be.
Does anyone know where the keyboards tha are effectively used are
located and/or how to use the good one, described in
/usr/share/X11/xkb/symbols/be ?
Thanks,
Marc
On 18/01/2022 00:24, Marc Lobelle wrote:
Hello
Apparently there are no dead keys in the BE keyboard. Is there a way
to activate them in order to easily type â in libreoffice for
instance ?
Thanks
Marc
--
Marc Lobelle
professeur émérite
ICTEAM
UCLouvain / SST / ICTEAM / INGI
Place Ste Barbe, 2, bte L5.02.01 - 1348 Louvain-la-Neuve
marc.lobe...@uclouvain.be
Tél.+32 (0) 475 494 616
Fax +32 (0) 10 47 51 20
www.uclouvain.be
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] Proposal to change documentation structure for some pages
Am 16.01.22 um 11:02 schrieb benn: Hi, I have included the openindiana mailing list in this discussion as I hope it will reach more interested people. At the moment James is the only actual member of the documentation team and thus naturally its head. I would like to invite everybody to chime in with ideas and opinions here, and of course after discussion formulate a plan and act upon. Everybody is invited to enhance our documentation by creating pull requests against our oi-docs repository at https://github.com/OpenIndiana/oi-docs Please keep in mind that James as the team lead of the documentation team will have the final decision about what will be merged and what not. Best regards, Andreas Hi James, Yes. I've noticed some of the pages becoming unwieldy too so your suggestion is an inevitability. Having such collosal themes such as ZFS, Dtrace, virtualisatiion, services, ... and more, hopefully, much more to come and placing this all in one file makes it cumbersome for the document writer. Moreover, when I'm reading up on something, I ususally end up exporting just that section to its own file and using the -f option to produce an epub of that one section. However, it might be wise to keep related sections somehow together in a kind of namespace. For example, if you split up a file, all new files deriving from the original file share the same name prefix; or you place all files into the same sub-directory. It might be possible to keep the same number of pages and instead investigate changes to the layout/theme in MkDocs; so it is easier to find subsections. Some content could maybe move between the sections where appropriate. Most certainly. Furthermore, when we begin to add an index, we'll see more duplication of material and repitions can be replaced by a reference to elsewhere. Benn On Sat, 2022-01-15 at 11:05 +, James Madgwick wrote: Hi, I've added an issue (https://github.com/OpenIndiana/oi-docs/issues/211) which proposes splitting some of the docs content into separate pages. In particular I noticed it when formatting some content from the old Wiki for transfer. There's quite a bit covering ZFS to migrate, putting it all into an existing page would increase the length significantly. My concern is there's a lot of content packed into a single page in some cases and this is not the easiest to navigate. It is not entirely clear which topics are covered by which page in the handbook - there is some overlap. It might be possible to keep the same number of pages and instead investigate changes to the layout/theme in MkDocs; so it is easier to find subsections. Some content could maybe move between the sections where appropriate. Thanks, James ___ oi-dev mailing list oi-...@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-...@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] About Publisher
Am 01.01.22 um 18:58 schrieb hput via openindiana-discuss: For a newly installed hipster OS 21.10 (in vbox vm) I see 'publish' set as so: PUBLISHER TYPESTATUS P LOCATION openindiana.org origin onlinehttp:/pkg.openindiana.org/hipster/ Is there more to be set... I notice when I ran: pkg install emacs I'm told it is not permitted on my image. I haven't done a full We don't have any package named "emacs" in our repositories, but searching for it is possible and reveals some package names: ╰─➤ pkg list -a|grep emacs SUNWgnu-emacs 23.1-0.133 --r SUNWgnu-emacs-el 23.1-0.133 --r SUNWgnu-emacs-gtk 23.1-0.133 --r SUNWgnu-emacs-nox 23.1-0.133 --r SUNWgnu-emacs-x 23.1-0.133 --r editor/gnu-emacs 27.2-2021.0.0.1 i-- editor/gnu-emacs/gnu-emacs-gtk 27.2-2021.0.0.1 i-- editor/gnu-emacs/gnu-emacs-lisp 27.2-2021.0.0.1 --- editor/gnu-emacs/gnu-emacs-no-x11 27.2-2021.0.0.1 i-- editor/gnu-emacs/gnu-emacs-x11 27.2-2021.0.0.1 --- So, you might want to run "pfexec pkg install gnu-emacs" or something similar depending on your needs. You can ask for details about a (probably not yet installed package) with eg. "pkg info -r gnu-emacs-gtk". Regards, Andreas update yet. Don't know if that will change anything regarding emacs. I did some installs, including build-essential with a range of compiling and etc tools I wanted whatever other publishers experienced users have if any. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] WARNING: Don't update now!
Am 17.12.21 um 14:32 schrieb Andreas Wacknitz: Hi all, we got the runtime dependencies wrong. So please don't update your OI Hipster for now or you'll end with a non-working pkg! Background: We updated some python packages and introduct pyrsistent but this package is not installed automatically. Sorry for the inconvenience. Andreas Ok, the problems have been fixed and it should be safe to update again! Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] WARNING: Don't update now!
Hi all, we got the runtime dependencies wrong. So please don't update your OI Hipster for now or you'll end with a non-working pkg! Background: We updated some python packages and introduct pyrsistent but this package is not installed automatically. Sorry for the inconvenience. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] firefox/thunderbird mediators and upgrade
Am 12/7/21 um 21:52 schrieb Bob Friesenhahn: I have not updated OpenIndian for some time (/etc/release says 2020.10). Using 'pkg update -rnv' I see reasonable output except for this output (simplified) which causes concern: Changed mediators: mediator firefox: version: 60 (system default) -> None mediator thunderbird: version: 52 (system default) -> None I am worried that the above means that after an upgrade, there will be no firefox or thunderbird available. Presumably I could then manually install them. My assumption regarding the meaning of 'Changed mediators' may be totally incorrect. Using 'pkg mediator' I see this relevant output: MEDIATOR VER. SRC. VERSION IMPL. SRC. IMPLEMENTATION firefox system 60 system thunderbird system 52 system Will everything just be ok or is there a way to influence the mediators in advance such that firefox and thunderbird will be installed with the latest version? Bob Don't worry. We have removed both mediators as we only have one version of both packages for some time now and don't plan to support multiple packages for the foreseeable future. Thus, the mediators were useless. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI snapshot release?
Hi, I have created the snapshot images on October 31st, and put them on the download server but haven't found enough time to write an announcement and the release notes. You can find them here: https://dlc.openindiana.org/isos/hipster/latest/ Regards, Andreas Am 11/21/21 um 20:37 schrieb Carl Brewer: G'day, I may have missed it, and there's nothing on https://www.openindiana.org/category/news/ - has there been a snapshot release of OI? A 2021.10? I know I needed a specially brewed snapshot earlier this year to work with a modern motherboard and CPU combo, thanks to Andreas I got one. Is there a formal one coming? Thank you, Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] wiki.openindiana.org needs to be re/started and fixed
Am 03.11.21 um 04:58 schrieb Nikola M.: On 10/18/21 23:11, James Madgwick wrote: Indeed, the contents of the Wiki have also been backed up to GitHub. However the repo it is in has not been made public because the Wiki also contained other information which is sensitive and can't be public. Wiki raw data can be used for Wiki service to restart and by the Wiki service itself then. Wiki raw data stays on Wiki side as always, and when Wiki is restarted and on the new hosting, everything that is supposed made public is served as for years before, including having an integrated discussion space for articles. Everything everyone ever published on Wiki is there to be publicly available by their authors and there is not much sensitive on it, except maybe connection between mail addresses , usernames and wiki account passwords and that Wiki manages itself internally. I've now removed the images (~70MB) and put it here: https://gist.github.com/JMadgwick/8a488ca4430aa0f50b7d5c5e31f60361/raw/390ff69310bf3756086ff90dfa156a6ce2fcab89/oi%2520Confluence-space-export.tar.xz Maybe that article archive can be useful and include images, too, is size constrain is a problem, it can be hosted outside of Github with images. Andreas Wacknitz helped James Madgewick in the past to do an export. So James Madgewick has an export of the wiki and is working on further migrating the contents to oi-docs. Everything about Wiki and it's freedom to be easy to contribute, publish and discuss, (Without the need to jhave every single change, or talk, being "approved" from someone else over GIT). Wiki is self-hosted and is independent from external resources availability as opposed to external service as Github. Wiki functionality is not be replaced and it is not the solution avoiding the issue of restarting working wiki. Issue is that Wiki needs to be restarted as a service and not keeping it closed under various pretenses. Wikis themselves do not have security problems when put up on new infrastructure with new and supported software, so security problems are not a real issue when maintained, as is not the lack of manpower for maintaining Wiki infrastructure. Wikis do not need "appointed censor" to decide only by itself without any discussion or process what is to stay on Wiki and what is not, but it is there by merit, usefulness and collaboration. With wiki, every article author is included in changes and re-engaged. Wiki is very important tool for new users to start contributing, it is form of free space that, on one place promotes the project name. Wikis serve as a proof of the project openness for new people, closing them down serves only to closing down communities. Closing community spaces and turning them in tightly-controlled and appointed ones, without actual wider community influx , leads to OI brand name bad reputation in a wider sense, for proprietary handling things on closed source mailing lists, not available to the public and available only to selected people. You omitted a central point: We need people to care for things. Telling people what should be done doesn't solve problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] a MP4 media player which works on openindiana ?
Am 10/24/21 um 7:14 PM schrieb Mario Marietto: Hello. thanks. Can you explain how to compile the newest mpeg version and (s) mplayer ? I'm new to OpenIndiana. Life is hard for the newbies of a new operating system. Il giorno dom 24 ott 2021 alle ore 19:06 Apostolos Syropoulos via openindiana-discuss ha scritto: We have documentation: http://docs.openindiana.org/dev/userland/ Using our build machinery brings another level of burden and you'll need to learn a lot of new things additionally but when using it you can participate in the project. If we don't find enough volunteers the project will end sooner or later. At the moment there are very few people working regularly on updates or fixes. We have many areas where nobody despite me is doing anything. Multimedia support is one example. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] a MP4 media player which works on openindiana ?
Am 10/24/21 um 7:05 PM schrieb Apostolos Syropoulos via openindiana-discuss: On my system I have two versions of ffmpeg: /usr/bin/ffmpeg -version ffmpeg version 3.2.14 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7.5.0 (OpenIndiana 7.5.0-il-0) configuration: --prefix=/usr --mandir=/usr/share/man --bindir=/usr/bin --libdir=/usr/lib/amd64 --cc=/usr/gcc/7/bin/gcc --enable-runtime-cpudetect --enable-mmx --enable-sse --enable-ssse3 --disable-debug --enable-nonfree --enable-gpl --enable-postproc --enable-avfilter --enable-swscale --enable-libgsm --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-x11grab --enable-libspeex --enable-pthreads --enable-libass --enable-openssl --enable-openal --enable-avresample --enable-libschroedinger --enable-libopenjpeg --enable-librtmp --enable-vdpau --enable-shared --disable-static libavutil 55. 34.101 / 55. 34.101 libavcodec 57. 64.101 / 57. 64.101 libavformat 57. 56.101 / 57. 56.101 libavdevice 57. 1.100 / 57. 1.100 libavfilter 6. 65.100 / 6. 65.100 libavresample 3. 1. 0 / 3. 1. 0 libswscale 4. 2.100 / 4. 2.100 libswresample 2. 3.100 / 2. 3.100 libpostproc 54. 1.100 / 54. 1.100 aposyro@adalind>> /opt/gnu/bin/ffmpeg -version ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 6.5.0 (OpenIndiana 6.5.0-oi-2) configuration: --enable-gpl --enable-nonfree --enable-libfdk-aac --enable-libx264 --enable-libmp3lame --enable-libass --prefix=/opt/gnu libavutil 55. 78.100 / 55. 78.100 libavcodec 57.107.100 / 57.107.100 libavformat 57. 83.100 / 57. 83.100 libavdevice 57. 10.100 / 57. 10.100 libavfilter 6.107.100 / 6.107.100 libswscale 4. 8.100 / 4. 8.100 libswresample 2. 9.100 / 2. 9.100 libpostproc 54. 7.100 / 54. 7.100 I have built the second one and I think it is not difficult to do it. Also, I have mplayer: mplayer -v MPlayer 1.3.0-4.8.5 (C) 2000-2016 MPlayer Team CPU vendor name: AuthenticAMD max cpuid level: 13 CPU: AMD FX(tm)-6300 Six-Core Processor (Family: 21, Model: 2, Stepping: 0) extended cpuid-level: 30 extended cache-info: 134250816 Detected cache-line size is 64 bytes CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNowExt: 0 SSE: 1 SSE2: 1 SSE3: 1 SSSE3: 1 SSE4: 1 SSE4.2: 1 AVX: 1 Compiled for x86 CPU with extensions And obviously I can play any video file. I could make an old style package for mplayer if you like. A.S. --Apostolos Syropoulos It would be nice to participate in the OpenIndiana project by using our build system and providing patches and updates (by means of PR's). We have only very few people involved in the development and it's a shame that some prefer to build their own packages. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
