Re: [oi-dev] [OpenIndiana-discuss] warning - don't update OI
Thanks, guys, for the hard work and the quick remediation.
Lou Picciano
> On Jul 24, 2021, at 4:09 PM, Judah Richardson
> wrote:
>
> Thanks very much for the update!
>
> Judah
>
> On Sat, Jul 24, 2021 at 3:08 PM Andreas Wacknitz wrote:
>
>> Hi all,
>>
>> It is now safe again to update.
>>
>> I had to revert the binutils-2.37 update and instead created a fake 2.37
>> package version that delivers the older 2.36.1 version.
>> With that I have re-published the latest illumos-gate packages and
>> successfully installed them on my machines.
>> Thanks to Toomas Soome for helping me and analyzing the problem.
>>
>> Andreas
>>
>> Am 7/24/21 um 9:55 AM schrieb Andreas Wacknitz:
>>> Hi all,
>>>
>>> something bad has happened with the last updates and rendered two of my
>>> build servers unbootable. They are both stuck in the boot loader ("start
>>> not found") such that
>>> booting with an old BE won't fix that!
>>>
>>> SO DON'T UPDATE YOUR SYSTEMS FOR NOW!
>>>
>>> I fear that my update of binutils-2.37 may be the culprit.
>>>
>>> Regards
>>> Andreas
>>>
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-disc...@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-disc...@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
> ___
> openindiana-discuss mailing list
> openindiana-disc...@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [OpenIndiana-discuss] Moving on with postgresql
I myself should be getting (again, more) re-engaged in the build/update process for PostgreSQL… I’ll wake up shortly. Lou > On Apr 18, 2021, at 6:07 AM, Andreas Wacknitz wrote: > > Am 18.04.21 um 02:37 schrieb Austin Kim: >> On Apr 17, 2021, at 7:22 PM, Till Wegmueller wrote: >>> Hi Gary >>> >>> I use Postgres and extensions for all Applications I develop professionally >>> and privately. >>> >>> We use mostly 12 and upwards 13 being the standard and I am waiting for 14 >>> to hit. The last Bugfix release for 9.5 was on 2021-02-11 so quite recently. >>> >>> I would love to have 13 and modern 12 packaged, especially as we have a >>> build server for them sponsored by the Oi community. So we know it builds >>> even on current develop. >>> >>> My preference for the record is to have 13, 12 and 11. Older ones should >>> only be used for people still needing them. AWS only offers those in their >>> offerings as well, so not many people will want 10 or older. >>> >>> -Till >>> >>> On 17.04.21 18:46, Gary Mills wrote: OI currently has postgresql versions: 95 96 10 11 12 . The OI default, in shared-macros.mk, is 95 . However, the postgresql developers report that 95 is unsupported, but 13 is available and supported. Something has to change in OI to move forward with postgresql. Here are some actions that could be taken with OI. We could change the default version to 10. I, myself, would prefer 11. We could obsolete 95. I'd prefer obsoleting 95 and 96. We could add version 13, but only after 96 is obsoleted. We should limit the number of postgresql versions in OI, after all. Finally, we could make no obsoletions or additions, retaining even the unsupported 95. Which would you prefer? I have not investigated two questions. Perhaps you can tell me? What are the consequences of obsoleting 95? What are the consequences of the default change? >> Hi, >> >> Sorry for posting to this list as I’m only an OpenIndiana user, not a >> developer, but PostgreSQL is the DB I use most. > This is perfectly fine. > I just want to chime in here and say: You don't need to be a developer > in order to get involved in OpenIndiana! > Of course it is helpful to know some programming languages and build > systems. But many for aspects you don't need to be a professional > programmer. > > At the moment we lack volunteers in almost all areas, even those not > related to updating packages. Eg. we need people to enhance or update > our documentation, > we need testers and of course people who care for some packages. > > Nobody started as an expert in any of these areas. I am willing to help > people to get involved, eg. we can have video conferences where I can > demonstrate and teach how to update packages. > > Of course you need to devote some resources (time, build or test > environment, ...). I can assure you that you will learn a lot about > OpenIndiana, Solaris and other operating systems. > And you will see some insanity related to software development, > especially open source software development where projects make heavy > changes (like change the build system) in minor or even micro releases. > > Andreas > > ___ > openindiana-discuss mailing list > openindiana-disc...@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] I'm taking a break
Alexander, Your contribution to OpenIndiana has been _huge_! And I’m sure I’m not alone in wishing to thank you for it. Best of luck in your new endeavor - but we are encouraged to think you are just ’taking a break’ (!) Regards, Lou Picciano > On Sep 8, 2020, at 11:36 AM, Alexander Pyhalov via oi-dev > wrote: > > Hi, guys. > > I wasn't sure if this should be a public message, but when I understood that > CC list reached > 5 persons, decided to send it here. > > Briefly, I'm taking a break. > This doesn't mean that I'll not be able to answer your questions or that I > will not commit anything to OI repos - I don't know. But for now I'm changing > my job and likely will relocate to Moscow in near future. Given that's new > position is a new area for me, I'll just have no time for such > time-consuming hobby as OI. > > I'm still excited about OI and illumos. It was a wonderful experience, but > for now our ways parted. > Good luck. You can always reach me via my gmail account. > > Best regards, > Alexander Pyhalov, > (still) system administrator of Southern Federal University IT department > > ___ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [OpenIndiana-discuss] GCC6 build zone status
Aurélien, You Da Man! (Yes, I am still here…) Lou Picciano > On Dec 4, 2017, at 4:45 AM, Aurelien Larcher <aurelien.larc...@gmail.com> > wrote: > > Only ocaml remains :) > So aside from openjdk-8 I'll have 100% gcc-6 compiled userland repository by > the end of the day :) > > Le Samedi 2 décembre 2017, Aurelien Larcher a écrit : >> It seems that only ocaml and open-vm-tools remain since Andreas fixed >> spidermonkey. >> Thanks :) >> >> Le Samedi 2 décembre 2017, Aurélien Larcher a écrit : >>> With some more help from Ken, remaining packages follow: >>> >>>> >>>>> runtime/ocaml >>>> >>>> Needs update. >>>> >>>>> sysutils/open-vm-tools >>>> >>>> Needs update >>>> >>>>> library/ spidermonkey >>>> >>>> Needs gcc6 patches. >>> >>> >>> Updated page here https://wiki.openindiana.org/oi/GCC+6 and still openjdk-8 >>> to be considered at some point. >>> >>> That leaves 4 packages out of 1390. >>> >>> Thanks >>> >>> Aurélien >>> >>>> >>>>> >>>>> If someone knows about Lua, there are issues with hexchat and libpeas >>>>> regarding luajit and LGI support. >>>>> >>>>> Kind regards >>>>> >>>>> Aurelien >>>>> >>>>> -- >>>>> --- >>>>> Praise the Caffeine embeddings >>>>> >>>> >>>> -- >>>> Envoyé depuis mon Jolla >>> >>> >>> >>> >>> -- >>> --- >>> Praise the Caffeine embeddings >>> >> >> -- >> Envoyé depuis mon Joll > > -- > Envoyé depuis mon Jolla > ___ > openindiana-discuss mailing list > openindiana-disc...@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Update IPS from https://github.com/everycity/pkg5/tree/ec-py27-ec-zones
Super work, Alexander. Thanks for this. (goes off to try...) Lou Picciano - Original Message - From: Alexander Pyhalov a...@rsu.ru To: OpenIndiana Developer mailing list oi-dev@openindiana.org, Dan McDonald dan...@omniti.com Sent: Thursday, June 4, 2015 12:35:19 PM Subject: [oi-dev] Update IPS from https://github.com/everycity/pkg5/tree/ec-py27-ec-zones Hello. I'm working on IPS update now. I used https://github.com/everycity/pkg5/tree/ec-py27-ec-zones for reference to leverage great Igor work on updating IPS for EveryCity. Branch with new IPS is here: https://github.com/pyhalov/pkg5/tree/oi-updates Note, that you'll need python2.6 IPS modules for now to compile illumos-gate or oi-userland, and python 2.6 IPS bits are mostly working, however pkg.depotd suggests using rather fresh Python2.7 (=2.7.9). Routine operations works for both python2.6 and 2.7. You will have to compile libbe with python2.7 to be able to use boot environments with Python (we provide library/python-2/libbe-27 in oi-userland). As executables don't meniton explicit python version, pkgdepend can't generate correct IPS dependencies for them and it should be done manually (included in update). Test resulsts are the following. All usual operations, as installing/updating packages work. ipkg zones work. IPS now knows about linked images and using -r switch you can make recursive operations on base system and zones. # Ran 1045 tests in 10496.098s - skipped 8 tests. Skipped tests: cli.t_pkgdep.py TestPkgdepBasics.test_bug_12697: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_bug_15843: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_bug_17808: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_elf_dependency_tags: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_elf_warning: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_output: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkgdep.py TestPkgdepBasics.test_relative_run_path: Test Skipped: No suitable Sun Studio compiler found. Tried: ['/usr/bin/cc', 'cc', '$CC']. Try setting $CC to a validcompiler. cli.t_pkg_help.py TestPkgHelp.test_help_character_encoding: Test Skipped: The test system must have the ja_JP.eucJP locale installed to run this test. FAILED (successes=1036, failures=8, errors=1, mismatches=9) == BASELINE MISMATCH: The following results didn't match the baseline. -- api.t_pkg_api_install.py TestPkgApiInstall.test_ipkg_out_of_date: fail cli.t_pkgdep.py TestPkgdepBasics.test_PEP_3149: fail cli.t_pkgdep.py TestPkgdepBasics.test_bug_13059: fail cli.t_pkgdep.py TestPkgdepBasics.test_multiple_run_paths: fail cli.t_pkgdep.py TestPkgdepBasics.test_python_combinations: error cli.t_pkg_install.py TestPkgInstallUpgrade.test_upgrade1: fail cli.t_pkgrecv.py TestPkgrecvMulti.test_2_recv_compare: fail cli.t_pkg_info.py TestPkgInfoBasics.test_ranked: fail cli.t_fix.py TestFix.test_06_download: fail cli.t_pkg_linked.py TestPkgLinkedScale.test_li_scale: fail -- Mismatches are related to the following. 1) api.t_pkg_api_install.py TestPkgApiInstall.test_ipkg_out_of_date This one also fails on our current IPS. MISMATCH FAIL (expected: pass)# # .---Failure Information--- # | ___ # | Start: api.t_pkg_api_install.py TestPkgApiInstall.test_ipkg_out_of_date # | Make sure that packaging system out-of-date testing works. # | ___ # | $ echo '#!/usr/bin/python [+5 lines...]' \ # | /tmp/ips.test.4335/0/smf_cmds/usr/bin/svcprop # | image 0 selected: /tmp/ips.test.4335/0/image0 # | setup: api.t_pkg_api_install.TestPkgApiInstall.test_ipkg_out_of_date # | creating 1 repo(s) # | publishers: ['test'] # | debug_features: [] # | prep_depot: set depot port 12001 # | prep_depot: set depot repository /tmp/ips.test.4335/0/repo_contents1 # | prep_depot: set depot log to /tmp/ips.test.4335/0/depot_logfile1 # | created repository /tmp/ips.test.4335/0/repo_contents1 # | $ echo 'tmp/baz
Re: [oi-dev] Review for new package - abook
Matt, I'll check it out. And thanks for contributing! Lou Picciano - Original Message - From: Matt Samudio m...@samudio.net To: oi-dev@openindiana.org Sent: Tuesday, May 26, 2015 4:35:44 PM Subject: [oi-dev] Review for new package - abook Hi all, This is my first attempt at contributing, so I selected something fairly easy - introducing a new package for a simple piece of software called abook, which is a console-based program for address books, used frequently with the mutt email client. Would someone like to review what I've done, to make sure its ready for me to make a pull request ? My github login is rk4n3, and I checked my work into my fork of hipster oi-userland on a branch named rk4n3dev_abook. I tested my work by performing the build in a build zone, publishing the package to a publisher running in my build zone, installing in a clean test zone by pointing the test zone at the build zone's publisher, and running the program from a normal (non-root) login, trying basic functionality that I know about from using the program. There is no test suite delivered with the software. Please advise me if I've made any mistakes, or not completed everything I should ... Thanks, Matt Samudio ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] build-essential package review
Adam, Nice! I especially like the gcc-4.7 bits... On Studio 12u1: I (Personally) wouldn't see much value in its being included in a build-essentials package. 12.3 might be another matter, of course, but thought we had a barrier to redistribution on the Studio line? Regards All, Lou - Original Message - From: Adam Števko To: OpenIndiana Developer mailing list Sent: Thu, 11 Jul 2013 01:14:17 - (UTC) Subject: [oi-dev] build-essential package review Hi guys, I created build-essential package and I would like you to review and tell me what else should be included. Changeset URL: https://github.com/xen0l/oi-userland/commit/7026fe8373c2e15a7d1d88595a8d34214e8d1ed8 Packages, which are commented out are either not found in /hipster and need porting from ec-userland or are duplicate (pkg-config vs gnome/gettext). i started with manifest from ec-userland and I added all things from make-rules/build-zone.mk. Next important step is to modify build-zone.mk, so setting up development environment is not complicated and newcomers have easy way to start contributing. I plan on documenting that process as well. And one last thing, do you guys think that Is there a point in including sunstudio12u1 and clang-3.3 as well in this package? Cheers, Adam ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Hipster zone update: command_substitute: cannot duplicate pipe as fd 1: Bad file number
Have recently updated many of our zones to a8 Hipster - working great! And thanks for your hard work, Andrzej and others... Having just updated yet another zone - using the repo as of late yesterday( 06 July), we see the following on zlogin. Never get near the OpenIndiana banner: The Illumos ProjectSunOS 5.11 illumos-b49b27dcJuly 2013 -bash: command_substitute: cannot duplicate pipe as fd 1: Bad file number I'll have to dig through the various .profiles and scripts which may be(?) on this container, but does above ring any bells? Lou Picciano___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Broadcom wireless drivers for OpenIndiana
Merci, Jean-Pierre, You realize this one feat addresses any number of questions we've gotten on the lists - with people being limited by the lack of this one driver? Thanks again, Lou Picciano - Original Message - From: Jean-Pierre jean-pierre.an...@wanadoo.fr To: oi-dev@openindiana.org Sent: Thu, 25 Apr 2013 13:21:28 - (UTC) Subject: [oi-dev] Broadcom wireless drivers for OpenIndiana I have uploaded to http://jp-andre.pagesperso-orange.fr/ndis.1.3.0.rc2.tar.gz a release candidate for an ndis emulator which can emulate the NDIS5 interface in 64-bit mode for Broadcom wireless drivers designed for Windows. This is a source tarball for which completing a Makefile really usable on OpenIndiana is left as an exercice for the user. Please read the included bcm4312.htm files for the procedure to compile and install. I have tested the emulator with my wireless device (vendor 14E4 device 4315) and the three versions of the Broadcom driver described below. Jim Klimov has sucessfully tested the latest version with his own device (vendor 14E4 device 4727). Only WEP encryption is available so far (WPA is not supported). Supported devices by driver 4.170.25.12, September 21, 2007 (from Dell R174291.exe) : Vendor 14E4 device 4311 Vendor 14E4 device 4312 Vendor 14E4 device 4315 Vendor 14E4 device 4318 Vendor 14E4 device 4319 Vendor 14E4 device 4320 rev 03 Vendor 14E4 device 4324 rev 03 Vendor 14E4 device 4328 Supported devices by driver 4.170.77.3, March 22, 2008 (from HP sp39912.exe), same as above, plus : Vendor 14E4 device 4307 Vendor 14E4 device 432B Supported devices by driver 5.60.350.6, March 23, 2010 (from HP sp48616.exe), same as above, plus : Vendor 14E4 device 4353 Vendor 14E4 device 4357 Vendor 14E4 device 4727 Enjoy, Jean-Pierre ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] OpenSSL 1.0.1e building quite nicely on OpenIndiana
Well, there is some good news - with OpenSSL 1.0.1e released earlier today, I wanted to do some testing. I can report it's building beautifully, and passing all tests, using our gcc-4.4.4. Will start integrating it into oi-build shortly. Those of you following the OpenSSL saga will have seen a couple of challenges in the recent release(s?) 1.0.1e seems to have addressed these. Lou Picciano___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Compiler migration #2
Adam, Tks for your hard work here. Have not yet had an oppty to review specifics, but... During our last threaten-to-publish-a-repo episode, I'd put some work into these build tools as well. Specifically, was in extensive dialog with the authors to remediate various errors from automake test suites. Believe I put up the submission - on our issues list(?) - which included patches. In addition, in another email/submission to the list, I'd referenced results of these tests - for virtually everything in oi-build at that point. I think we should be trying to use at least the best parts(?) of our earlier attempts at process in order to ease the way forward - are we using the issues list any more? Specifically, I'd done a lot of work on patching and packaging automake - these were virtually ready-to-go at that point; may be due a version bump by now. I'd like that work to not be lost now. I also feel that we should be sticking with Rich Lowe's Illumos-specific bump to gcc; we have to get through the growing pains of figuring out how best to make it all 'hang together'. From there, the version bump to newer gccs should be much easier. (Glad to see there is a core group of us here still quite interested in OI's future...) Regards, Lou Picciano - Original Message - From: adam stevko adam.ste...@gmail.com To: OpenIndiana Developer mailing list oi-dev@openindiana.org Sent: Sat, 26 Jan 2013 19:03:46 - (UTC) Subject: Re: [oi-dev] Compiler migration #2 Bumping for reviews. AdamOn Saturday, 26 January 2013 at 17:14, Gordon Ross wrote:I'm pretty sure some distros would like the consistency ofusing the same gcc version the OS uses. (Just for theconvenience. I know they don't need to be the same.) Gordon On Sat, Jan 26, 2013 at 7:59 AM, Adam Števko adam.ste...@gmail.com wrote:Hi Peter, On Jan 26, 2013, at 1:01 PM, Peter Tribble peter.trib...@gmail.com wrote: Adam, Just one question - why gcc44? In other words, why not jump straightto gcc 4.7?Getting new compiler into oi-build would be nice, but it doesn't solve the problem with migrating stuff away from Sun Studio. Once, we are sure, that everything is buildable by GCC 4.4 (which we have already packaged), I have no doubt that transitioning to newer GCC painless. Correct me if I am wrong. Yes, I know that Illumos has 4.4.4, but that's a custom versionspecific to building Illumos. I think SmartOS has gone to 4.7,and for Tribblix I went straight to 4.7.2.As I said, I am using GCC 4.4 because it is available. Cheers, Adam ---Peter Tribblehttp://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___oi-dev mailing listoi-dev@openindiana.orghttp://openindiana.org/mailman/listinfo/oi-dev ___oi-dev mailing listoi-dev@openindiana.orghttp://openindiana.org/mailman/listinfo/oi-dev -- Gordon Ross g...@nexenta.comNexenta Systems, Inc. www.nexenta.comEnterprise class storage for everyone ___oi-dev mailing listoi-dev@openindiana.orghttp://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build: Studio - GCC migration changeset #1
Adam, Fabulous work! Thank You for it. It's heartening to realize there's still a core cadre of us who want to see OpenIndiana realize its potential. Lou Picciano - Original Message - From: Adam Števko adam.ste...@gmail.com To: OpenIndiana Developer mailing list oi-dev@openindiana.org Sent: Saturday, November 10, 2012 8:32:00 AM Subject: [oi-dev] oi-build: Studio - GCC migration changeset #1 Hi, in the past few weeks I was working on importing Bayard's gcc44 (the one used in oi-experimental) into current oi-build. Huge amount of packages can be build without any problems. I worked on problematic one and I have covered almost half of them. I'm posting first changeset for review. I plan to post the next changeset in the second half of the november, so it is easier to review. Changeset URL: https://hg.openindiana.org/users/xenol/oi-build/rev/1f4b245e177d Current status of every component (contains my notes): https://hg.openindiana.org/users/xenol/oi-build/file/a91d248a1df9/status I also published the output from gmake publish in every component did. (txt files can be used directly by browsers) Build logs: http://xenol.eu/~xenol/logs/oi-build/ Cheers, Adam ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [OpenIndiana-discuss] Calibre doc converter to ebooks formats for OpenIndiana??
From: Jan Owoc jso...@gmail.com To: Discussion list for OpenIndiana openindiana-disc...@openindiana.org Sent: Thursday, August 9, 2012 9:37:32 AM Subject: Re: [OpenIndiana-discuss] Calibre doc converter to ebooks formats for OpenIndiana?? On Thu, Aug 9, 2012 at 7:03 AM, Milan Jurik milan.ju...@xylab.cz wrote: Sooner or later Python 3.2 will be provided in OI SFE but I am not sure how much it can coexists with 2.6 blockquote Many GNU/Linux distributions have both a Python2 and a Python3 in their repositories. I happen to have both installed on one of my systems. /blockquote blockquote /blockquote blockquote /blockquote We do quite a bit of 'experimentation' with various versions of Python, so have several versions installed at a given moment. The Python 'altinstall' option is your friend here through all v2s of python. In fact - if memory serves, since v3.0(?), I believe 'make install' is now an alias for 'make altinstall'. The 'make fullinstall' option now exists for when you're ready to make the jump to v3-as-default. Really, the developer has fully granular control over which binary to use in a given environment; they coexist quite nicely in separate trees. (Some crazy developer might well have 2.4, 2.6, 2.7 and 3.2, all in harmonious cohabitation.) Of course, the only big gotcha is that the binary named 'python' is called, by default, by many things - and so should be agreed upon. We can make the determination of which version is to be so blessed as 'The OS Version' as necessary bits and pieces make it into versions. Fwiw, I've suggested we use these binary naming conventions within our own userland builds; they seem to accommodate most developer use cases (we have many), and allow for rapid transition in the future; for example, for all the system-level uses of python. (OK, I had to look it up: see release notes for 3.0a5: http://www.python.org/getit/releases/3.0.1/NEWS.txt ) blockquote The way it works is similar to how it's frequently done with gcc, where there is a series of symbolic links, with the plain python command pointing toward the version that is considered most universal: ~$ ls -l /usr/bin/pyth* lrwxrwxrwx 1 root root 9 Apr 23 10:06 /usr/bin/python - python2.7 lrwxrwxrwx 1 root root 9 Apr 23 10:06 /usr/bin/python2 - python2.7 -rwxr-xr-x 1 root root 2989480 Jul 31 23:40 /usr/bin/python2.7 -rwxr-xr-x 1 root root 1652 Jul 31 23:40 /usr/bin/python2.7-config lrwxrwxrwx 1 root root 16 Apr 17 11:20 /usr/bin/python2-config - python2.7-config lrwxrwxrwx 1 root root 9 Apr 14 23:13 /usr/bin/python3 - python3.2 lrwxrwxrwx 1 root root 11 May 3 09:52 /usr/bin/python3.2 - python3.2mu -rwxr-xr-x 1 root root 2954048 May 3 09:52 /usr/bin/python3.2mu lrwxrwxrwx 1 root root 11 Apr 14 23:13 /usr/bin/python3mu - python3.2mu lrwxrwxrwx 1 root root 16 Apr 17 11:20 /usr/bin/python-config - python2.7-config When I have a program that *requires* Python 3.2, it usually knows (or can be configured) to call python3. Cheers, Jan ___ OpenIndiana-discuss mailing list openindiana-disc...@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss /blockquote ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] HeartBeat+Pacemaker ready to be included into OI repository
Tao, I'll gladly help get the underlying packages into illumos-userland (and I'm sure many others would be interested); interest in the cluster capability comes up quite a bit... Many thanks for this work. Lou Picciano - Original Message - From: Tao Shen themoron1...@yahoo.com To: oi-dev@openindiana.org Cc: alka a...@hfg-gmuend.de, Mike Rowell m...@scuba.org.uk Sent: Friday, May 4, 2012 2:16:16 AM Subject: [oi-dev] HeartBeat+Pacemaker ready to be included into OI repository Hi, oi-dev list: I am writing you this email to request that the heartbeat + pacemaker package to be included into the OI repository. Ever since Oracle closed source OpenSolaris, they took away the free Solaris Cluster as well. Right now, the clustering package for Illumos is missing. There are solutions like RSF-1, but if you believe in open source, you realize that you need an open source solution to the clustering problem for Illumos. This is the work based on Mike Rowell's blog and the script is based on Patterson's work on Heartbeat 3.0.4 posted here: http://www.scuba.org.uk/toptech/openindiana-ha-cluster-howto/ http://www.scuba.org.uk/toptech/openindiana-ha-cluster-new-versions/ http://www.scuba.org.uk/toptech/openindiana-ha-package/ Now there are two ways to skin this cat: the script way or Mike Rowell's already packaged way: 1. Mike's packaged bzip2 file: http://www.scuba.org.uk/?wpdmact=processdid=NC5ob3RsaW5r 2. Modified script to build everything from source: http://booki.cc/howto-setup-openindiana-ha-clusters-in-esxi/_draft/_v/2.4/static/clusterbuilder-1.1.sh The script way shows you all the steps necessary to arrive at Mike's package. It also includes Illumian 1.0 support, which I intend to ask Illumian mailing list to accept into the Illumian repository as well. Whichever way the OI-dev goes, the final goal is to let users do this command and have it installed onto their OI system: pkg install pacemaker-heartbeat Please let Gea, Mike or I know when this package is integrated into OI repository. Thanks, ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] New prestable release - oi_151a2 0.151.1.2
Jon, This (people) person is happy with that. And thanks for your work! Things are coming together! Lou Picciano - Original Message - From: Jon Tibble me...@btinternet.com To: Developer list for OpenIndiana oi-dev@openindiana.org Sent: Monday, February 13, 2012 6:13:37 PM Subject: [oi-dev] New prestable release - oi_151a2 0.151.1.2 Hi all, Repos and tarball download locations have been updated for the next prestable release of OpenIndiana. After feedback this includes pushing both prestable releases to the /dev repo for wider testing and seemed to be what the majority wanted. This will probably see the prestable repo go away soon so when ISOs are produced they will have /dev as the configured openindiana.org publisher. Please feedback if people are happy with that. Full release notes can be found here: http://wiki.openindiana.org/oi/oi_151a_prestable1+Release+Notes Again, no ISOs but there will be for the next one. Please test and feedback on the mailing lists, in IRC or in the comments on the wiki. Enjoy, JT ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] error in pkg5 - from oi-prestable
Bayard: That pkg is from /experimental: pkg:/package/pkg@0.5.11-0.151.1.1 Aside, should it now be considered 'good practice' to do an rebuild-index after all updates? Getting the performance degraded message - and generally inconsistent search results when rebuild is not done. - Original Message - From: Bayard Bell buffer.g.overf...@gmail.com To: OpenIndiana Developer mailing list oi-dev@openindiana.org Sent: Saturday, February 11, 2012 6:05:34 AM Subject: Re: [oi-dev] error in pkg5 - from oi-prestable I saw that bit, but I was hoping to get the publisher and package version, as well as the hg fingerprint. On Sat, Feb 11, 2012 at 10:06 AM, Jeppe Toustrup openindi...@tenzer.dk wrote: On Sat, Feb 11, 2012 at 10:12, Bayard Bell buffer.g.overf...@gmail.com wrote: I don't get this error with the version I'm using. What version do you have? It's mentioned in the last line of the output :) The version of pkg(5) is '4d886e93dafc' -- Venlig hilsen / Kind regards Jeppe Toustrup (aka. Tenzer) ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] error in pkg5 - from oi-prestable
Unsure where we'd want this reported - so... (thanks to those of you working hard on pkg5, btw!) # pkg image-update -n --help Usage: Traceback (most recent call last): File /usr/bin/pkg, line 4233, in handle_errors __ret = func(*args, **kwargs) File /usr/bin/pkg, line 4150, in main_func usage(retcode=0, full=False, cmd=subcommand) File /usr/bin/pkg, line 248, in usage print_cmds([cmd], combined) File /usr/bin/pkg, line 235, in print_cmds cmd) ValueError: Unable to find usage str for image-update pkg: This is an internal error. Please let the developers know about this problem by filing a bug at http://defect.opensolaris.org and including the above traceback and this message. The version of pkg(5) is '4d886e93dafc'. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] illumos-userland
Igor, Super news - and thanks for your efforts. Starting to feel like we may actually now be approximating the goal; that of a unified, harmonized Oi-build system. Yay! Regards All, Lou Picciano - Original Message - From: Igor Kozhukhov ikozhuk...@gmail.com To: OpenIndiana Developer mailing list oi-dev@openindiana.org Cc: develo...@lists.illumos.org Sent: Thursday, February 9, 2012 8:58:37 AM Subject: [oi-dev] illumos-userland Hello All, I have pushed my changes from dilos-userland - illumos-userland - have agreement with Alasdair. We can start to use it and integrate changes after review. Welcome with contributing! --- Best regards, Igor Kozhukhov Skype# igor.kozhukhov | IRC# igork ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
