From bonivart at opencsw.org Sat Jul 1 10:54:52 2017 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 1 Jul 2017 10:54:52 +0200 Subject: pkgutil failing to install specific version of a package dependency In-Reply-To: <20170630152851.GA27656@blizinski-linux.roam.corp.google.com> References: <20170630152851.GA27656@blizinski-linux.roam.corp.google.com> Message-ID: I only remember us using "latest is greatest" as principle. If I remember correctly GAR produces depend files without version and it's probably because of Antoine including version that pkgutil sees two versions, it was never intended to end up with that. If it's a standard Solaris thing it should handle it without fault at least but I'm not sure of the benefit of complete support of it. First time in 10 years (?) it has surfaced. I'm on the road so I can't take a look at this for at least a week. On Fri, Jun 30, 2017 at 5:28 PM, Maciej Blizi?ski wrote: > Hi Anotine, > > On Fri, Jun 30, 2017 at 01:41:31PM +0000, ALLARD Antoine via users wrote: >> The depend documentation says that the version should be specified on a new line starting with some whitespace but it did not work in my case (it ended taking the latest revision). >> What is the correct way to specify the revision of a package dependency? > > The ability to depend on a specific version of a package is news to me. All of > the OpenCSW packages are built with the assumption that this is not possible. > > I tried to determine when was this introduced. I found the previous version of > this document for Solaris 8 and 9: > > Solaris 8 > http://docs.oracle.com/cd/E19455-01/806-0633/6j9vn6q35/index.html > > Solaris 9 > http://docs.oracle.com/cd/E19683-01/816-0219/6m6njqb78/index.html > > Both documents refer to the same file format, which includes the package > version. > > Perhaps it's just the OpenCSW tooling that doesn't allow for that? In any case, > it's likely that pkgutil wasn't designed or tested for this feature. > > I don't know how much effort would it take to make it work. Maybe Peter > Bonivart can write more about this? > > Maciej From George.Wyche at pw.utc.com Sun Jul 2 00:12:54 2017 From: George.Wyche at pw.utc.com (Wyche, George PW) Date: Sat, 1 Jul 2017 22:12:54 +0000 Subject: updating CSW pkgs when last was 2012. Message-ID: <040fa64d3af34ae0b4887787ae901d26@UUSALE0L.utcmail.com> Need advice about updating an old setup. This system is isolated from the internet. Been content with CSW software (333 packages) since late 2012. Reading, I see that big reason for lots of changes was being caught just when all the SO's were separated out. Pkgutil -C says I have 198 of 333 have changed. And 39 of the 198 are "not in catalog". The "not in catalog" means I don't know what those CSW is now named. So if I want to do "pkgutil -in" I will have to guess (and be wrong). I want to be able to compile some simple c++ programs and aim to get CSWgcc4g++. I remember 5 years ago being bothered by copying this & that .gz from the mirror, attempting installation, then finding I needed yet more files from the mirror. I also worry that after 5 years, SOME program I use which was dropped from the catalog, will /break/ after I do all the updating. This did happen to me with emacs on one workstation that was/Is stuck on Solaris 10u5, when the openCSW policy came to drawing the line at 10u8 (I think). Being without an editor after *that* update was unpleasant. Since I cannot reasonably QA all the programs using openCSW support that I have, what alternatives do I have when after a few weeks post updating I find a program "I MUST HAVE" doesn't work (well enough) because some library change is incompatible? Throw away all the work I did updating (and giving up CSWgcc4g++)? Find exactly which programs use the offending library (assuming I can figure that out) and uninstall all of them so I can revert just that SO library so my "MUST HAVE" can work again? [[I feel like my system is unchangeable! I should pick up another workstation, do the updating on it, and stuff the former workstation in the closet as a backup.]] George Wyche From maciej at opencsw.org Mon Jul 3 01:31:02 2017 From: maciej at opencsw.org (Maciej =?utf-8?Q?Blizi=C5=84ski?=) Date: Mon, 3 Jul 2017 00:31:02 +0100 Subject: updating CSW pkgs when last was 2012. In-Reply-To: <040fa64d3af34ae0b4887787ae901d26@UUSALE0L.utcmail.com> References: <040fa64d3af34ae0b4887787ae901d26@UUSALE0L.utcmail.com> Message-ID: <20170702233102.3au2nqhhrnaczgmu@gmail.com> Hi George, It feels like you've administered yourself into a corner, but I think there are ways to get out of it. I won't provide you with the whole procedure but hopefully I'll leave enough hints so you can figure out the rest. On Sat, Jul 01, 2017 at 10:12:54PM +0000, Wyche, George PW via users wrote: > Need advice about updating an old setup. > > This system is isolated from the internet. We have a procedure for that: https://www.opencsw.org/community/questions/92/installing-without-direct-internet-access But it doesn't apply to your setup in a straightforward way. In your case, I would recommend making a local mirror of the catalog: https://www.opencsw.org/manual/for-administrators/mirror-setup.html > Been content with CSW software (333 packages) since late 2012. > > Reading, I see that big reason for lots of changes was being caught just when all the SO's were separated out. > Pkgutil -C says I have 198 of 333 have changed. And 39 of the 198 are "not in catalog". > The "not in catalog" means I don't know what those CSW is now named. So if I want to do "pkgutil -in" I will have to guess (and be wrong). I guess the problem is that you skipped intermediate releases. You need to upgrade to each consecutive catalog release. They have been released in a way that when you go from catalog N to N+1, you don't get these errors. But if you go from catalog N to N+2, you'll get these errors. Browse the "releases" subdirectory on the mirror to find the ordering of catalog names. > Since I cannot reasonably QA all the programs using openCSW support that I have, what alternatives do I have when after a few weeks post updating I find a program "I MUST HAVE" doesn't work (well enough) because some library change is incompatible? Throw away all the work I did updating (and giving up CSWgcc4g++)? Find exactly which programs use the offending library (assuming I can figure that out) and uninstall all of them so I can revert just that SO library so my "MUST HAVE" can work again? Try using Live Upgrade for that. If something goes wrong, you can go back to the previous state. > [[I feel like my system is unchangeable! I should pick up another workstation, do the updating on it, and stuff the former workstation in the closet as a backup.]] Sounds like a good idea! Maciej From JACKSON at encompasserve.org Wed Jul 12 23:43:01 2017 From: JACKSON at encompasserve.org (noskcaJ leahciM) Date: Wed, 12 Jul 2017 17:43:01 -0400 (EDT) Subject: Pkg database hungover - How best to fix? Message-ID: <01QGMNNRAWC20022H7@Encompasserve.org> Hi Guys, CSWcurl, which for years had been installed and regularly updated on a S10 branded zone on S11.3, complained on an update attempt last year, that there was a dependency with the global zone and wouldn't update. I've been left with no cURL on that S10 zone ever since. Recently P2V'd that global zone into a native S11.3 guest zone on upgraded h/w (and cloned the S10 branded zone over to the upgraded server). Point being that, in relation to the S10 branded zone, what was its parent global zone is now just another sibling non-global zone. (Hope you're with me so far). I've just tried, again, to update CSWcurl on the S10 branded zone, and, as before it complains thus:- ----->o------ # pkgutil -i CSWcurl Solving needed dependencies ... Solving dependency order ... 13 CURRENT packages: CSWcacertificates-20160830,REV=2016.08.30 CSWcas-migrateconf-1.50,REV=2015.01.17 CSWcas-preserveconf-1.50,REV=2015.01.17 CSWcommon-1.5,REV=2010.12.11 CSWlibexpat1-2.1.0,REV=2013.01.01 CSWlibgcc-s1-5.2.0,REV=2015.07.31 CSWlibiconv2-1.14,REV=2011.08.07 CSWlibicudata57-57.1,REV=2016.04.04 CSWlibicuuc57-57.1,REV=2016.04.04 CSWlibmetalink3-0.1.3,REV=2015.06.27 CSWlibssl1-0-0-1.0.2l,REV=2017.06.01 CSWlibz1-1.2.8,REV=2013.09.23 CSWpublic-suffix-list-20160819,REV=2016.08.19 Install 6 NEW packages: CSWcurl-7.54.1,REV=2017.06.14 (opencsw/unstable) CSWggettext-data-0.19.8,REV=2016.09.08 (opencsw/unstable) CSWlibcurl4-7.54.1,REV=2017.06.14 (opencsw/unstable) CSWlibidn2-0-0.10,REV=2016.11.07 (opencsw/unstable) CSWlibintl9-0.19.8,REV=2016.09.08 (opencsw/unstable) CSWlibpsl5-0.14.0,REV=2016.08.21 (opencsw/unstable) Total size: 1.9 MB 6 packages to fetch. Do you want to continue? ([y],n,auto) auto Turning on automatic mode as if --yes was passed. => Fetching CSWggettext-data-0.19.8,REV=2016.09.08 (1/6) ... A local copy of CSWlibidn2-0-0.10,REV=2016.11.07 exists and is of matching size. A local copy of CSWlibpsl5-0.14.0,REV=2016.08.21 exists and is of matching size. A local copy of CSWlibintl9-0.19.8,REV=2016.09.08 exists and is of matching size. => Fetching CSWlibcurl4-7.54.1,REV=2017.06.14 (5/6) ... => Fetching CSWcurl-7.54.1,REV=2017.06.14 (6/6) ... => Installing CSWggettext-data-0.19.8,REV=2016.09.08 (1/6) ... pkgadd: ERROR: The package is currently installed on the system in the global zone. To install the new instance of this package in the global zone only, you must specify the -G option. To install the new instance of this package in all zones you must first remove the existing instance of this package from the global zone first (via pkgrm) and then install the new instance of this package in all zones. pkgadd: ERROR: package cannot be installed on this system/zone Exiting pkgutil due to pkgadd error: 1 -----o<----- On the contrary, the package isn't installed in the global zone (there aren't any CSW packages installed in the global zone). OTOH, it is installed in a non-global zone; the non-global zone (NGZ) that was formerly this zone's parent global zone. I appreciate that this isn't actually a pkgutil issue, but how should I go about fixing this? I'm a bit worried about un-installing all of the CSW packages in either/both of the S10 branded zone or the S11 NGZ and then re-installing as some of my packages aren't in the catalogue and I can't remember from where I obtained them. TL;DR's forgiven. Michael. From dam at opencsw.org Thu Jul 13 08:07:34 2017 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Jul 2017 08:07:34 +0200 Subject: Pkg database hungover - How best to fix? In-Reply-To: <01QGMNNRAWC20022H7@Encompasserve.org> References: <01QGMNNRAWC20022H7@Encompasserve.org> Message-ID: <8F93381B-5321-4D20-AE40-A2E3FDB02951@opencsw.org> Hi Michael, Am 12.07.2017 um 23:43 schrieb noskcaJ leahciM via users : > CSWcurl, which for years had been installed and regularly updated > on a S10 branded zone on S11.3, complained on an update attempt > last year, that there was a dependency with the global zone and > wouldn't update. I've been left with no cURL on that S10 zone > ever since. > > Recently P2V'd that global zone into a native S11.3 guest zone > on upgraded h/w (and cloned the S10 branded zone over to the > upgraded server). Point being that, in relation to the S10 > branded zone, what was its parent global zone is now just > another sibling non-global zone. (Hope you're with me so far). > > I've just tried, again, to update CSWcurl on the S10 branded > zone, and, as before it complains thus:- > > ----->o------ > # pkgutil -i CSWcurl > Solving needed dependencies ... > Solving dependency order ... > 13 CURRENT packages: > CSWcacertificates-20160830,REV=2016.08.30 > CSWcas-migrateconf-1.50,REV=2015.01.17 > CSWcas-preserveconf-1.50,REV=2015.01.17 > CSWcommon-1.5,REV=2010.12.11 > CSWlibexpat1-2.1.0,REV=2013.01.01 > CSWlibgcc-s1-5.2.0,REV=2015.07.31 > CSWlibiconv2-1.14,REV=2011.08.07 > CSWlibicudata57-57.1,REV=2016.04.04 > CSWlibicuuc57-57.1,REV=2016.04.04 > CSWlibmetalink3-0.1.3,REV=2015.06.27 > CSWlibssl1-0-0-1.0.2l,REV=2017.06.01 > CSWlibz1-1.2.8,REV=2013.09.23 > CSWpublic-suffix-list-20160819,REV=2016.08.19 > Install 6 NEW packages: > CSWcurl-7.54.1,REV=2017.06.14 (opencsw/unstable) > CSWggettext-data-0.19.8,REV=2016.09.08 (opencsw/unstable) > CSWlibcurl4-7.54.1,REV=2017.06.14 (opencsw/unstable) > CSWlibidn2-0-0.10,REV=2016.11.07 (opencsw/unstable) > CSWlibintl9-0.19.8,REV=2016.09.08 (opencsw/unstable) > CSWlibpsl5-0.14.0,REV=2016.08.21 (opencsw/unstable) > Total size: 1.9 MB > 6 packages to fetch. Do you want to continue? ([y],n,auto) auto > Turning on automatic mode as if --yes was passed. > => Fetching CSWggettext-data-0.19.8,REV=2016.09.08 (1/6) ... > A local copy of CSWlibidn2-0-0.10,REV=2016.11.07 exists and is of matching size. > A local copy of CSWlibpsl5-0.14.0,REV=2016.08.21 exists and is of matching size. > A local copy of CSWlibintl9-0.19.8,REV=2016.09.08 exists and is of matching size. > => Fetching CSWlibcurl4-7.54.1,REV=2017.06.14 (5/6) ... > => Fetching CSWcurl-7.54.1,REV=2017.06.14 (6/6) ... > > => Installing CSWggettext-data-0.19.8,REV=2016.09.08 (1/6) ... > pkgadd: ERROR: The package is currently installed on the system in the > global zone. To install the new instance of this package in the global > zone only, you must specify the -G option. To install the new instance > of this package in all zones you must first remove the existing instance > of this package from the global zone first (via pkgrm) and then install > the new instance of this package in all zones. > pkgadd: ERROR: package cannot be installed on this system/zone > Exiting pkgutil due to pkgadd error: 1 > -----o<----- > > On the contrary, the package isn't installed in the > global zone (there aren't any CSW packages installed in the global zone). > OTOH, it is installed in a non-global zone; the non-global zone (NGZ) > that was formerly this zone's parent global zone. > > I appreciate that this isn't actually a pkgutil issue, but how should I > go about fixing this? I'm a bit worried about un-installing all of the > CSW packages in either/both of the S10 branded zone or the S11 NGZ and > then re-installing as some of my packages aren't in the catalogue and > I can't remember from where I obtained them. Ugly, ugly, ugly, there is no documented way out of this AFAIK. I guess the only workaround is to manually ?fix" the issue by editing out the stuff from the previous global zone from the package database in /var/sadm/pkg and /var/sadm/install/contents. Make sure to make a snopshot upfront to be on the safe side. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP URL: From mikeowens at gmail.com Fri Jul 14 00:29:44 2017 From: mikeowens at gmail.com (Mike Owens) Date: Thu, 13 Jul 2017 17:29:44 -0500 Subject: Link error with git Message-ID: First off, thanks for all you do. This project is a great help. I ran into a problem with git/libcurl on Solaris 10 Sparc. I got the following error when trying to use git: git-remote-http: fatal: libssl.so.1.0.0: version 'OPENSSL_1.0.2' not found (required by file /opt/csw/lib/libcurl-feature.so.4) It seems like the current libcurl package links to a newer openssl library than was is installed. So I mucked around and figured out how to build the latest openssl lts using gar. When I built and installed from source the problem went away. I tried to file a bug but I could not get the back tracker to send me a confirmation email when I signed up for an account. Regards, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From JACKSON at encompasserve.org Fri Jul 14 19:08:40 2017 From: JACKSON at encompasserve.org (noskcaJ leahciM) Date: Fri, 14 Jul 2017 13:08:40 -0400 (EDT) Subject: Pkg database hungover - How best to fix? Message-ID: <01QGP6ON8XQS0020XU@Encompasserve.org> > Hi Michael, Hiya Dago, Am 12.07.2017 um 23:43 schrieb noskcaJ leahciM via users : >> [ ... ] >> I've just tried, again, to update CSWcurl on the S10 branded >> zone, and, as before it complains thus:- >> [ ... ] >> ----->o------ >> # pkgutil -i CSWcurl >> => Installing CSWggettext-data-0.19.8,REV=2016.09.08 (1/6) ... >> pkgadd: ERROR: Package is currently installed >> on the system in the global zone. To install the new instance of >> this package in global zone only you must specify the -G option. >> To install the new instance of this package in all zones you must >> first remove the existing instance of this package from global >> zone first (via pkgrm) and then install the new instance of this >> package in all zones. pkgadd: ERROR: package >> cannot be installed on this system/zone >> Exiting pkgutil due to pkgadd error: 1 >> -----o<----- >> >> On the contrary, isn't installed in the global >> zone (there aren't any CSW packages installed in the global zone). >> OTOH, it is installed in a non-global zone; the non-global zone >> that was formerly this zone's parent global zone. >> >> I appreciate that this isn't actually a pkgutil issue, but how >> should I go about fixing this? > > > Ugly, ugly, ugly, there is no documented way out of this AFAIK. > I guess the only workaround is to manually "fix" the issue by > editing out the stuff from the previous global zone from the > package database /var/sadm/pkg and /var/sadm/install/contents. On the s10s_u10wos_17b zone, /var/sadm/install/contents looks big and hairy enough to decide to leave well alone. > Make sure to make a snapshot upfront to be on the safe side. Now there's a thought. I've got a recovery archive of global and all the subordinate zones, but that's Last Chance Saloon territory. If in global I do a beadm create, boot into that new snapshot then uninstall all of the CSW packages in the S11.3 zone that the problem S10 zone thinks is still the GZ, then return to that problem S10 zone and re-try that failed installation of CSWcurl, shouldn't it "just work"? Then, if it does, surely all I need to is reinstall in the S11.3 zone all(*) the CSW packages I removed earlier. If it doesn't work (meaning I've still got a broken S10 zone and now, on top of that, a S11.3 zone emptied of all CSW packages), surely all I have to do is drop back to the previous BE and delete my trial BE and be no worse-off? > Best regards > > Dago Thank you Michael (*)I too must have skipped consecutive updates as I've got a number of packages not in-catalogue. Presumably, providing I backup the package directories /var/sadm/pkg, they can just be reinstalled again using the old Companion CD approach; cd to /var/sadm/pkg and do a pkg install -d . CSWx2x for example? They'll be installed, I'll still get "not in catalog" messages and won't be any worse-off than I am now. From uwppp at flash.net Mon Jul 17 20:40:26 2017 From: uwppp at flash.net (Robert A. Schmied) Date: Mon, 17 Jul 2017 11:40:26 -0700 Subject: qt4 ver 4.8.5 libqt4-qt3support Message-ID: <596D049A.8050108@flash.net> opencsw / peter felecan sure would be nice to have package that supplies the bits and pieces needed for libqt4-qt3support for qt4 ver 4.8.5 if at all possible. while trying to build qucs-0.0.19 the missing libqt4-qt3support and all the qt3support include files are halting further progress. thanks aloha ras From csardi.gabor at gmail.com Wed Jul 19 10:55:50 2017 From: csardi.gabor at gmail.com (=?UTF-8?B?R8OhYm9yIENzw6FyZGk=?=) Date: Wed, 19 Jul 2017 09:55:50 +0100 Subject: libssl1_0_0 version on 5.10 Message-ID: Hi All, I am trying to install libcurl4 on Solaris 10, and it seems to depend on the openssl library, version 1.0.2. Which is fine, but this version of libssl1_0_0 is somehow not available to pkgutil. I update the package list using pkgutil -U and then pkgutil -a libssl still gives me libssl1_0_0 1.0.1u. Unfortunately this version has a different soname and it is not ABI compatible with the newer version of libssl. Interestingly, if I go to the package list at http://mirror.opencsw.org/opencsw/allpkgs/ I can see the 1.0.2 version, it is at http://mirror.opencsw.org/opencsw/allpkgs/libssl1_0_0-1.0.2l%2cREV%3d2017.06.01-SunOS5.10-i386-CSW.pkg.gz Btw. is it possible to download this pkg file and install it manually? Thanks for any tips, GAbor From dam at opencsw.org Wed Jul 19 12:14:11 2017 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 19 Jul 2017 12:14:11 +0200 Subject: libssl1_0_0 version on 5.10 In-Reply-To: References: Message-ID: <3AC30AD6-2B0A-4A59-A7CC-BADFD1B2A701@opencsw.org> Hi Gabor, Am 19.07.2017 um 10:55 schrieb G?bor Cs?rdi via users : > I am trying to install libcurl4 on Solaris 10, and it seems to depend > on the openssl library, version 1.0.2. Which is fine, but this version > of libssl1_0_0 is somehow not available to pkgutil. > > I update the package list using > pkgutil -U > and then > pkgutil -a libssl > still gives me libssl1_0_0 1.0.1u. > > Unfortunately this version has a different soname and it is not ABI > compatible with the newer version of libssl. > > Interestingly, if I go to the package list at > http://mirror.opencsw.org/opencsw/allpkgs/ I can see the 1.0.2 > version, it is at > http://mirror.opencsw.org/opencsw/allpkgs/libssl1_0_0-1.0.2l%2cREV%3d2017.06.01-SunOS5.10-i386-CSW.pkg.gz > > Btw. is it possible to download this pkg file and install it manually? The problem is that there was a blocking bug preventing propagation from unstable/ to testing/. You probably have subscribed to the testing/ catalog. As workaround I would suggest to switch to unstable by changing the mirror suffix in /etc/opt/csw/pkgutil.conf. I also closed the error so the package should be in testing tomorrow, so you could also just wait a day and update again and everything should work. Thanks to bring this issue up! Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP URL: From dam at opencsw.org Wed Jul 19 12:15:54 2017 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 19 Jul 2017 12:15:54 +0200 Subject: qt4 ver 4.8.5 libqt4-qt3support In-Reply-To: <596D049A.8050108@flash.net> References: <596D049A.8050108@flash.net> Message-ID: Hi Robert, Am 17.07.2017 um 20:40 schrieb Robert A. Schmied via users : > opencsw / peter felecan > > sure would be nice to have package that supplies the bits and pieces > needed for libqt4-qt3support for qt4 ver 4.8.5 if at all possible. > > while trying to build qucs-0.0.19 the missing libqt4-qt3support > and all the qt3support include files are halting further progress. Just to get this right: you just need an additional configure option for the existing package so a respin should be sufficient? Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP URL: From uwppp at flash.net Wed Jul 19 18:53:16 2017 From: uwppp at flash.net (Robert A. Schmied) Date: Wed, 19 Jul 2017 09:53:16 -0700 Subject: qt4 ver 4.8.5 libqt4-qt3support In-Reply-To: References: <596D049A.8050108@flash.net> Message-ID: <596F8E7C.9040105@flash.net> Dagobert Michelsen wrote: > Hi Robert, > > Am 17.07.2017 um 20:40 schrieb Robert A. Schmied via users : > >>opencsw / peter felecan >> >>sure would be nice to have package that supplies the bits and pieces >>needed for libqt4-qt3support for qt4 ver 4.8.5 if at all possible. >> >>while trying to build qucs-0.0.19 the missing libqt4-qt3support >>and all the qt3support include files are halting further progress. > > > Just to get this right: you just need an additional configure option for the > existing package so a respin should be sufficient? > aloha Dago well now i'm a bit confused. i was(am) trying to compile locally, not on or for opencsw, qucs-0.0.19 (Quite Universal Circuit Simulator) and while it is mostly qt4 there are some dependencies still on the qt4-q3support library (-lQt3Support) and the associated include files (-I$QT4_PATH/Qt3Support). oh dago after re-re-re-reading the message i think the message is partly directed at me and also partly at peter or (current) qt4 maintainer. with respect to qt4, i've looked at trying to build it (qt4) here locally, a daunting task it seems especially on my antique hardware. and i've never attempted to get gar installed and functional so it would be a configure build in any case with opencsw gcc/g++ 4.9.0. with respect to a 'respin' i'm thinking the changed configure option for the existing package is either a) deleting the -no-qt3support as the default is -qt3support or b) explicitly adding -qt3support. whether this will be a trivial respin without headache is doubtful, as there must have been a valid reason to override the -qt3support default. in addition there will probably be a bit of additional gar configuration needed to package up the Qt3Support library, include files and anything else that implement the qt3 support stuff. thanks for you help aloha ras > > Best regards > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > From pfelecan at opencsw.org Sat Jul 22 10:19:10 2017 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 22 Jul 2017 10:19:10 +0200 Subject: qt4 ver 4.8.5 libqt4-qt3support In-Reply-To: <596F8E7C.9040105@flash.net> (Robert A. Schmied's message of "Wed, 19 Jul 2017 09:53:16 -0700") References: <596D049A.8050108@flash.net> <596F8E7C.9040105@flash.net> Message-ID: "Robert A. Schmied" writes: > with respect to a 'respin' i'm thinking the changed configure option for the > existing package is either a) deleting the -no-qt3support as the default is > -qt3support or b) explicitly adding -qt3support. > > whether this will be a trivial respin without headache is doubtful, as there > must have been a valid reason to override the -qt3support default. in addition > there will probably be a bit of additional gar configuration needed to package > up the Qt3Support library, include files and anything else that implement > the qt3 support stuff. I'm not the initial maintainer of thess packages and I do not know the reason behind having inhibited the qt3 support capability. Nothing is trivial in building such a massive package set as Qt but I'll try to see if it's not a low hanging fruit and a respin will make it fall. -- Peter From uwppp at flash.net Sat Jul 22 19:10:59 2017 From: uwppp at flash.net (Robert A. Schmied) Date: Sat, 22 Jul 2017 10:10:59 -0700 Subject: qt4 ver 4.8.5 libqt4-qt3support In-Reply-To: References: <596D049A.8050108@flash.net> <596F8E7C.9040105@flash.net> Message-ID: <59738723.8070606@flash.net> Peter FELECAN wrote: > "Robert A. Schmied" writes: > > >>with respect to a 'respin' i'm thinking the changed configure option for the >>existing package is either a) deleting the -no-qt3support as the default is >>-qt3support or b) explicitly adding -qt3support. >> >>whether this will be a trivial respin without headache is doubtful, as there >>must have been a valid reason to override the -qt3support default. in addition >>there will probably be a bit of additional gar configuration needed to package >>up the Qt3Support library, include files and anything else that implement >>the qt3 support stuff. > > > I'm not the initial maintainer of thess packages and I do not > know the reason behind having inhibited the qt3 support capability. > > Nothing is trivial in building such a massive package set as Qt but I'll > try to see if it's not a low hanging fruit and a respin will make it fall. aloha peter i fully recognize that this effort might be for naught, but do appreciate the attempt. after looking at the instructions to configure/build qt4 on my unsupported solaris-10-sparc-gcc and the source/config changes made in the past by those sharing the effort i decided it might better to ask opencsw to give it a go and thereby giving more of us solarians the benefit of a package but mostly to save me a bunch of eyestrain and headache. if there is anything i can do to help you with this effort please give me a shout. thanks aloha ras From bourke.aubrey at gmail.com Sun Jul 23 18:49:57 2017 From: bourke.aubrey at gmail.com (Aubrey Bourke) Date: Sun, 23 Jul 2017 17:49:57 +0100 Subject: Murrine gtk2 Theme engine 64bit Message-ID: Hi Im runninng Solaris 11.3 and I compiled the murrine theme engine from here: https://github.com/GNOME/murrine But it only compiles a 32bit version. I need both 32bit and 64bit versions. Can anyone help me out here? Regards, Aubrey Bourke -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Mon Jul 24 11:10:24 2017 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Jul 2017 11:10:24 +0200 Subject: OpenCSW HDF5 support In-Reply-To: References: Message-ID: Hi Mike, Am 17.07.2017 um 11:58 schrieb Dagobert Michelsen : > Am 14.07.2017 um 15:32 schrieb Mike Schmidt : >> Do you have any thoughts you can share on why OpenCSW HDF5 support is dated? I know the HDFgroup officially stop supporting Solaris x86 as of Feb 2001, but your builds kept going well past that time. Did it get to the point where it was difficult or impossible to build? For what its worth, I can't even get the last version you built for OpenCSW to build on my system. > > No particular reason, just busy with other stuff :-) > > I?ll have a look if I can bump the version. Feel free to ping me in a week if the package > is not there until then :-) I don?t quite get how the shared library naming works for this library: the existing HDF5 1.8.7 has the shared libraries libhdf5.so.7.0.1 libhdf5_hl.so.7.0.1 The latest version from the 1.8 branch is 1.8.19 and that one produces libhdf5.so.10.3.0 libhdf5_hl.so.10.2.0 The latest version 1.10.1 produces libhdf5.so.101.0.0 libhdf5_hl.so.100.0.1 These libraries are built regardless whet API version I specify with --with-default-api-version=(v16|v18|v110) If you can tell me what the best for packaging would be I can provide the packages. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP URL: From dam at opencsw.org Mon Jul 24 11:21:53 2017 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Jul 2017 11:21:53 +0200 Subject: Murrine gtk2 Theme engine 64bit In-Reply-To: References: Message-ID: Hi Aubrey, Am 23.07.2017 um 18:49 schrieb Aubrey Bourke via users : > Im runninng Solaris 11.3 and I compiled the murrine theme engine from here: > https://github.com/GNOME/murrine > > But it only compiles a 32bit version. > > I need both 32bit and 64bit versions. > > Can anyone help me out here? What do you mean by ?it only compiles a 32bit version?? I suspect ?it? is actually you and if you want an additional 64 bit version you need to build that in addition to the 32 bit build you already did by setting the flags appropriately as described here: https://www.opencsw.org/manual/for-developers/index.html Please also make sure to include an exact output of what you did and what you expect from your commands. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP URL: