From phil at bolthole.com Thu Jan 1 07:40:34 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 31 Dec 2008 22:40:34 -0800 Subject: [csw-maintainers] back from vac Message-ID: <20090101064034.GD70757@bolthole.com> fyi: back from vacation, and have processed some pending packages. will put in more tomorrow; it's late. happy new year and all that :-) order was semi-random for the curious From dlaigle at opencsw.org Thu Jan 1 18:38:57 2009 From: dlaigle at opencsw.org (dlaigle) Date: Thu, 01 Jan 2009 18:38:57 +0100 Subject: [csw-maintainers] =?utf-8?q?qt=5Fgcc_3=2E3=2E8b_in_/testing?= Message-ID: <938923f84f2c55a7361b1c77ee18502c@localhost> Hi ! Happy new year and feel free to test the new build of Qt_gcc 3.3.8: http://mirror.opencsw.org/testing/qt_gcc-3.3.8,REV=2009.01.01-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/qt_gcc-3.3.8,REV=2009.01.01-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/qt_gcc_common-3.3.8,REV=2009.01.01-SunOS5.8-all-CSW.pkg.gz Using this new one in replacement of the current (old) 3.3.4 version should give all "kde-gcc" applications anti-aliased fonts and OpenGL support for nuts. Cheers - Dominique From dam at opencsw.org Thu Jan 1 18:49:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 1 Jan 2009 18:49:54 +0100 Subject: [csw-maintainers] New members Message-ID: Hi, the association welcomes the newly accepted members - Ken Mays - Jonathan Wheeler - Mike Arnold - Oliver Kiddle All of you have already contributed to the project in the past. Ken did a lot of desktop packages, Jonathan put considerable effort in media player software and contributed fixes upstream, Mike also maintained quite a bunch of packages and Oliver took over some orphaned packages like lzma. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! If you have applied for membership and don't see your name listed here please stay calm. There is a backlog and I don't have mails on every applicant from every board member yet. Please allow some more days as it is still vacation time. Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Best regards -- Dago From dam at opencsw.org Thu Jan 1 22:52:15 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 1 Jan 2009 22:52:15 +0100 Subject: [csw-maintainers] libidn 1.9 in testing/ Message-ID: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> Hi, I updated our stoneged-version of libidn to 1.9 in testing: libidn-1.9,REV=2009.01.01-SunOS5.8-i386-CSW.pkg.gz libidn-1.9,REV=2009.01.01-SunOS5.8-sparc-CSW.pkg.gz However, the old package contained some (really-) legacy versions of the library: /opt/csw/lib/sparcv9/libidn.so.11.5.2 /opt/csw/lib/sparcv9/libidn.so.11.5.12 /opt/csw/lib/sparcv9/libidn.so.11.5.10 /opt/csw/lib/libidn.so.11.5.2 /opt/csw/lib/libidn.so.11.5.12 /opt/csw/lib/libidn.so.11.5.10 /opt/csw/lib/libidn.so.11.4.5 There is quite a number of packages depending on this one (see ). Is there a simpler way to find stuff depending on these old libs apart from installing all dependend packages and use ldd? It would be really useful to be able to search for this in addition to the regular file searches. The packages in testing/ *do not* include any old versions right now. Best regards -- Dago From phil at bolthole.com Fri Jan 2 00:40:59 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 1 Jan 2009 15:40:59 -0800 Subject: [csw-maintainers] libidn 1.9 in testing/ In-Reply-To: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> References: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> Message-ID: <20090101234059.GA70048@bolthole.com> On Thu, Jan 01, 2009 at 10:52:15PM +0100, Dagobert Michelsen wrote: > Hi, > There is quite a number of packages depending on this one > (see ). Is there a simpler > way to find stuff depending on these old libs apart from installing > all dependend packages and use ldd? It would be really useful to > be able to search for this in addition to the regular file searches. This is mentioned on the search page. put each of the actual numbered versions in. for example, exact match on libidn.so.11.5.2 pulls up nothing. Hmm.... perhaps this feature is broken though :-( nothing is showing up now on any of the revs. WAIT! everything seems to actually be looking for the simpler, libidn.so.11 so you should be able to dump the older revs i think. This is not surprising, since presumably, the newest lib, has an SONAME of libidn.so.11 also hurray for competant developers for once! From dam at opencsw.org Fri Jan 2 18:25:45 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 2 Jan 2009 18:25:45 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 Message-ID: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Hi, I finally managed to make a current ncurses 5.7 with full 64 bit for Sparc and x86. The legacy versions of the shared libraries which used to be in the previous package doesn't seemed to be used, so I dropped them. Feel free to give it a try, after release we can go on adding amd64 support to all the dependencies. Best regards -- Dago From phil at bolthole.com Fri Jan 2 19:55:25 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 2 Jan 2009 10:55:25 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Message-ID: <20090102185525.GA7106@bolthole.com> On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: > Hi, > > I finally managed to make a current ncurses 5.7 with full > 64 bit for Sparc and x86. The legacy versions of the shared > libraries which used to be in the previous package doesn't > seemed to be used, so I dropped them. Feel free to give it > a try, after release we can go on adding amd64 support to > all the dependencies. please test/fix the xterm issues on.. x86, i think it was? From phil at bolthole.com Sun Jan 4 08:25:22 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 3 Jan 2009 23:25:22 -0800 Subject: [csw-maintainers] new version of cswutils/checkpkg Message-ID: <20090104072522.GA15859@bolthole.com> hi folks, please note, that I have updated o the cswutils package, for a new version of checkpkg. Folks will be happy to learn that it is a good deal more intelligent, about NOT double-reporting gcc3rt vs gcc3core dependancies. also, it will not double report SUNW dependancies when CSW ones already cover it. There are still a few vague edge cases where it wont be perfect... but it should be a whole lot better than the older version. enjoy :) (PS to build farmadmins: please update the packageon the build machines ;-) From dlaigle at opencsw.org Sun Jan 4 17:55:22 2009 From: dlaigle at opencsw.org (dlaigle) Date: Sun, 04 Jan 2009 17:55:22 +0100 Subject: [csw-maintainers] =?utf-8?q?samba=5Flib=5Fdev_on_build_farm_missi?= =?utf-8?b?bmcuLi4=?= Message-ID: <1bc9b6a011c2618e625fe93d37477d80@localhost> Hi, Please install the package CSWsambalibdev on build machines, I have dependencies on it from KDE... Many thanks. - Dominique From dlaigle at opencsw.org Sun Jan 4 20:27:54 2009 From: dlaigle at opencsw.org (dlaigle) Date: Sun, 04 Jan 2009 20:27:54 +0100 Subject: [csw-maintainers] =?utf-8?q?/testing_=3A_arts=5Fgcc-1=2E5=2E10_an?= =?utf-8?q?d_kdelibs=5Fgcc-3=2E5=2E10?= Message-ID: <6d375a76a36f1762477729f4f79c5f95@localhost> Hello, Fundamental packages for kde 3.5.10 are ready for testing: http://mirror.opencsw.org/testing/arts_gcc-1.5.10,REV=2009.01.03-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/arts_gcc-1.5.10,REV=2009.01.03-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/kdelibs_gcc-3.5.10,REV=2009.01.03-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/kdelibs_gcc-3.5.10,REV=2009.01.03-SunOS5.8-sparc-CSW.pkg.gz Cheers - Dominique From bwalton at opencsw.org Mon Jan 5 16:41:10 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 05 Jan 2009 10:41:10 -0500 Subject: [csw-maintainers] avoid cswutils Message-ID: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> Hi All, Avoid the updated cswutils. It puts files in the wrong locations. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Mon Jan 5 17:44:32 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 5 Jan 2009 08:44:32 -0800 Subject: [csw-maintainers] avoid cswutils In-Reply-To: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> References: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> Message-ID: <20090105164431.GA71088@bolthole.com> On Mon, Jan 05, 2009 at 10:41:10AM -0500, Ben Walton wrote: > > Hi All, > > Avoid the updated cswutils. It puts files in the wrong locations. what the heck... I went back to look at where I genereated the package... and the files I rememebered editing, arent the way I edited them :-( stuff i put into MULTIPLE files is lost somehow. what a mess :-( new update going out now. seems to pkgadd just fine From bwalton at opencsw.org Tue Jan 6 01:50:20 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 05 Jan 2009 19:50:20 -0500 Subject: [csw-maintainers] avoid cswutils In-Reply-To: <20090105164431.GA71088@bolthole.com> References: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> <20090105164431.GA71088@bolthole.com> Message-ID: <1231202800-sup-7771@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Mon Jan 05 11:44:32 -0500 2009: > new update going out now. > seems to pkgadd just fine Following up on this, it seems that the this is a PEBKAC. I called `pkg-get -i cswutils` instead of `pkg-get -u cswutils.` [Holiday mode still? Debian mode?] The BASEDIR had changed from / to /opt/csw and the default admin file sets instance=overwrite. In short, I shot myself in the foot. Apologies to Phil and to the list. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Tue Jan 6 14:45:27 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 06 Jan 2009 14:45:27 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Message-ID: <49636077.10804@opencsw.org> Hi Dago, Dagobert Michelsen wrote: > I finally managed to make a current ncurses 5.7 with full > 64 bit for Sparc and x86. which machine do you use to build 64 bit packages? When i try to build mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( [===== NOW BUILDING: mbuffer-20081207 MODULATION isa-amd64: ISA=amd64 =====] ==> Extracting download/mbuffer-20081207.tgz ==> Copying download/CSWpackage.gspec [extract-modulated] complete for mbuffer. gmake[1]: Leaving directory `/home/skayser/mgar/pkg/mbuffer/trunk' [extract] complete for mbuffer. gmake[1]: Entering directory `/home/skayser/mgar/pkg/mbuffer/trunk' gar/gar.conf.mk:321: *** The ISA 'amd64' can not be build on this kernel with the arch 'i386'. Stop. However, your ncurses PSTAMP makes me believe that you used build8x to build the 64 bit ncurses libs. What am i missing? Sebastian From phil at bolthole.com Tue Jan 6 18:03:19 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 6 Jan 2009 09:03:19 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49636077.10804@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <49636077.10804@opencsw.org> Message-ID: <20090106170319.GC42258@bolthole.com> On Tue, Jan 06, 2009 at 02:45:27PM +0100, Sebastian Kayser wrote: > Hi Dago, > > Dagobert Michelsen wrote: > > I finally managed to make a current ncurses 5.7 with full > > 64 bit for Sparc and x86. > > which machine do you use to build 64 bit packages? When i try to build > mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( yup. cant build amd64 on sol8. sadly. HHmmmm... well, actually, it should be theoretically possible. we should be able to set up a gcc cross-compiler, for non-kernel software builds. (i'm not volunteering for it though ;-) but you can use build10x for generating the binaries. > However, your ncurses PSTAMP makes me believe that you used build8x to > build the 64 bit ncurses libs. What am i missing? PSTAMP says where you created the packages. for combined sol8/10 packages, standard proceedure is to build the "regular" stuff on build8x, then build aux binaries on build10x and copy them over. From dam at opencsw.org Tue Jan 6 22:53:10 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 6 Jan 2009 22:53:10 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49636077.10804@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <49636077.10804@opencsw.org> Message-ID: Hi Sebastian, Am 06.01.2009 um 14:45 schrieb Sebastian Kayser: > Dagobert Michelsen wrote: >> I finally managed to make a current ncurses 5.7 with full >> 64 bit for Sparc and x86. > > which machine do you use to build 64 bit packages? When i try to build > mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( > > [===== NOW BUILDING: mbuffer-20081207 MODULATION isa-amd64: > ISA=amd64 =====] > ==> Extracting download/mbuffer-20081207.tgz > ==> Copying download/CSWpackage.gspec > [extract-modulated] complete for mbuffer. > gmake[1]: Leaving directory `/home/skayser/mgar/pkg/mbuffer/trunk' > [extract] complete for mbuffer. > gmake[1]: Entering directory `/home/skayser/mgar/pkg/mbuffer/trunk' > gar/gar.conf.mk:321: *** The ISA 'amd64' can not be build on this > kernel > with the arch 'i386'. Stop. > > However, your ncurses PSTAMP makes me believe that you used build8x to > build the 64 bit ncurses libs. What am i missing? The trick is to do the 64 bit compilation on build10x and the package assembly on build8x. You do - build8x: gmake - build10x: gmake merge - build8x: gmake package And you end up with a nicely assembled package. This is only possible with an NFS-mounted directory between Solaris 8 and 10. I may add some feature which sshs over to the right machine for each ISA. Best regards -- Dago From dam at opencsw.org Tue Jan 6 23:33:05 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 6 Jan 2009 23:33:05 +0100 Subject: [csw-maintainers] New members and current member acceptance status Message-ID: <3D0F723B-6FCE-4019-ACF9-FB39F29D1352@opencsw.org> Hi, the association welcomes the newly accepted members - Ian Dickinson - Gilberto Persico - Chad Harp Ian and Gilberto have already contributed to the project in the past. Ian maintains some network-related packages, Gilberto also maintains network and terminal-related packages. Chad is a new maintainer who contributed lots of changes to SVN for several packages like vim, meanwhile, libgadu and others. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Currently there are three more applicants is the queue for which I either don't have votes from all board members or where the status is currently under discussion: - Juergen Arndt - Jake Goerzen - Eric Korpela If you have applied for membership and don't see your name anywhere above please let me know. There has been a lot of mail traffic for me to be processed in the past weeks and I cannot guarantee that I didn't missed one. Best regards -- Dago _______________________________________________ board mailing list board at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/board From dam at opencsw.org Wed Jan 7 22:59:11 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 7 Jan 2009 22:59:11 +0100 Subject: [csw-maintainers] Please take care: prototype generation on mGAR v2 Message-ID: Hi, it turns out the prototype generation of mGAR v2 had some issues generating packages containing hardlinks to files in other directories from the same package. Commit r2753 should have fixed this, however this path rewriting from cswproto is not straight-forward. Please be extra careful with the auto-generated prototypes and let me know if you encounter other issues. This does not affect mGAR v1. Thanks! -- Dago From dam at baltic-online.de Wed Jan 7 22:57:51 2009 From: dam at baltic-online.de (Dagobert Michelsen) Date: Wed, 7 Jan 2009 22:57:51 +0100 Subject: [csw-maintainers] Please take care: prototype generation on mGAR v2 Message-ID: <2A2E6840-CA05-4148-B192-FD29213D0CA9@baltic-online.de> Hi, it turns out the prototype generation of mGAR v2 had some issues generating packages containing hardlinks to files in other directories from the same package. Commit r2753 should have fixed this, however this path rewriting from cswproto is not straight-forward. Please be extra careful with the auto-generated prototypes and let me know if you encounter other issues. This does not affect mGAR v1. Thanks! -- Dago From william at wbonnet.net Wed Jan 7 22:05:52 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 07 Jan 2009 22:05:52 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media Message-ID: <49651930.2070506@wbonnet.net> Hi, I am looking the installation media of the latest (if possible) version of Solaris 7 for the x86 platform. Anyone has an idea of how to find it ? thanksin advance for your help cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 7 22:19:22 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 07 Jan 2009 22:19:22 +0100 Subject: [csw-maintainers] LinkedIn group Message-ID: <49651C5A.4090800@wbonnet.net> Hi For people using LinkedIn i have created an OpenCSW group. http://www.linkedin.com/groups?home=&gid=1693847 feel free to join cheers, W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 7 23:47:06 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 7 Jan 2009 23:47:06 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <20090102185525.GA7106@bolthole.com> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> Message-ID: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Hi Phil, Am 02.01.2009 um 19:55 schrieb Philip Brown: > On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: >> I finally managed to make a current ncurses 5.7 with full >> 64 bit for Sparc and x86. The legacy versions of the shared >> libraries which used to be in the previous package doesn't >> seemed to be used, so I dropped them. Feel free to give it >> a try, after release we can go on adding amd64 support to >> all the dependencies. > > please test/fix the xterm issues on.. x86, i think it was? After reading the bug report I get the impression that the Solaris implementation of xterm is missing the necessary control character support. Modifying the xterm spec would be bad, as http://opencsw.org/packages/xterm supports the sequence. Otherwise the package looks good now for me. Best regards -- Dago From phil at bolthole.com Thu Jan 8 01:22:54 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 7 Jan 2009 16:22:54 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Message-ID: <20090108002254.GA31120@bolthole.com> On Wed, Jan 07, 2009 at 11:47:06PM +0100, Dagobert Michelsen wrote: > > please test/fix the xterm issues on.. x86, i think it was? > > After reading the bug report I get the impression that the > Solaris implementation of xterm is missing the necessary > control character support. Modifying the xterm spec would > be bad, as http://opencsw.org/packages/xterm supports the > sequence. > I think that's inappropriate. it does not work on x86 as well as it does on sparc. unless you can say "x86 xterm needs to install this patch to work right", i think you should either remove the "broken" feature code from the x86 side, or possibly standardize both sparc and x86 to have lesser capabilities that basically always work. From skayser at opencsw.org Thu Jan 8 14:06:50 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 14:06:50 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Message-ID: <4965FA6A.1010908@opencsw.org> Dagobert Michelsen wrote: > Am 02.01.2009 um 19:55 schrieb Philip Brown: >> On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: >>> I finally managed to make a current ncurses 5.7 with full >>> 64 bit for Sparc and x86. The legacy versions of the shared >>> libraries which used to be in the previous package doesn't >>> seemed to be used, so I dropped them. Feel free to give it >>> a try, after release we can go on adding amd64 support to >>> all the dependencies. >> please test/fix the xterm issues on.. x86, i think it was? > > After reading the bug report I get the impression that the > Solaris implementation of xterm is missing the necessary > control character support. Modifying the xterm spec would > be bad, as http://opencsw.org/packages/xterm supports the > sequence. Mhh, how then would you prevent issues as the one being described in the bug report? If you leave the capabilities in the xterm terminfo file provided with CSWncurses, applications linked against CSWncurses running in a Solaris xterm are prone to mess up the display. We could pull in CSWxterm as a dependency for applications linked against CSWncurses, but even this wouldn't totally cut it as it is not granted that a user then actually uses /opt/csw/bin/xterm. You would need to make users aware of the fact that CSWxterm should be used with CSWncurses applications ... unless they fancy a garbled display of course. ;) On the other hand: From what i have seen when i deleted the two capabilities from the terminfo file, it doesn't matter to ncurses applications whether the two affected capabilities are present or not. ncurses just falls back to other capabilities for cursor positioning. So why not just drop the capabilities? Sebastian From a.cervellin at acm.org Thu Jan 8 14:58:03 2009 From: a.cervellin at acm.org (Alessio) Date: Thu, 08 Jan 2009 14:58:03 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4965FA6A.1010908@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> Message-ID: <4966066B.4060804@acm.org> xterm 238 is now available on /testing From phil at bolthole.com Thu Jan 8 18:01:10 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 8 Jan 2009 09:01:10 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <4965FA6A.1010908@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> Message-ID: <20090108170110.GE42437@bolthole.com> On Thu, Jan 08, 2009 at 02:06:50PM +0100, Sebastian Kayser wrote: > > After reading the bug report I get the impression that the > > Solaris implementation of xterm is missing the necessary > > control character support. Modifying the xterm spec would > > be bad, as http://opencsw.org/packages/xterm supports the > > sequence. > > Mhh, how then would you prevent issues as the one being described in the > bug report? If you leave the capabilities in the xterm terminfo file > provided with CSWncurses, applications linked against CSWncurses running > in a Solaris xterm are prone to mess up the display. take the extra capabilities out, from the ncurses terminfo file. > On the other hand: From what i have seen when i deleted the two > capabilities from the terminfo file, it doesn't matter to ncurses > applications whether the two affected capabilities are present or not. > ncurses just falls back to other capabilities for cursor positioning. > > So why not just drop the capabilities? and sounds like you agree also. Perhaps you could specify which ones you dropped to fix things, for the benefit of the current (in progress) ncurses maintainer From skayser at opencsw.org Thu Jan 8 18:17:23 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 18:17:23 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <20090108170110.GE42437@bolthole.com> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> Message-ID: <49663523.2090603@opencsw.org> Philip Brown wrote: > On Thu, Jan 08, 2009 at 02:06:50PM +0100, Sebastian Kayser wrote: >>> After reading the bug report I get the impression that the >>> Solaris implementation of xterm is missing the necessary >>> control character support. Modifying the xterm spec would >>> be bad, as http://opencsw.org/packages/xterm supports the >>> sequence. >> Mhh, how then would you prevent issues as the one being described in the >> bug report? If you leave the capabilities in the xterm terminfo file >> provided with CSWncurses, applications linked against CSWncurses running >> in a Solaris xterm are prone to mess up the display. > > take the extra capabilities out, from the ncurses terminfo file. > > >> On the other hand: From what i have seen when i deleted the two >> capabilities from the terminfo file, it doesn't matter to ncurses >> applications whether the two affected capabilities are present or not. >> ncurses just falls back to other capabilities for cursor positioning. >> >> So why not just drop the capabilities? > > and sounds like you agree also. Yep, I see no harm in doing so. > Perhaps you could specify which ones you dropped to fix things, for the > benefit of the current (in progress) ncurses maintainer The capabilities were HPA and VPA (horizontal and vertical absolute positioning). $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep '[hv]pa' hpa=\E[%i%p1%dG, vpa=\E[%i%p1%dd, Details and ncurses behaviour after i deleted vpa are documented in the bug that i had filed against mutt [1]. Sebastian [1] http://opencsw.org/bugtrack/view.php?id=2942. From skayser at opencsw.org Thu Jan 8 18:57:39 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 18:57:39 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4966066B.4060804@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> Message-ID: <49663E93.1040000@opencsw.org> Alessio wrote: > xterm 238 is now available on /testing Works fine here, thanks. Could you ./configure with --enable-wide-chars so that CSWxterm can deal with UTF-8 ... p l e a s e :) Just give the following python snippet a try. python -c 'print u"\u00E4"' Right now CSWxterm gives ?? whereas the Solaris xterm properly displays the character ? (LATIN SMALL LETTER A WITH DIAERESIS). Sebastian From a.cervellin at acm.org Thu Jan 8 19:12:24 2009 From: a.cervellin at acm.org (Alessio) Date: Thu, 08 Jan 2009 19:12:24 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <49663E93.1040000@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> <49663E93.1040000@opencsw.org> Message-ID: <49664208.60808@acm.org> done, can you grab it again from /testing? Sebastian Kayser wrote: > Alessio wrote: > >> xterm 238 is now available on /testing >> > > Works fine here, thanks. Could you ./configure with --enable-wide-chars > so that CSWxterm can deal with UTF-8 ... p l e a s e :) > > Just give the following python snippet a try. > > python -c 'print u"\u00E4"' > > Right now CSWxterm gives ?? whereas the Solaris xterm properly displays > the character ? (LATIN SMALL LETTER A WITH DIAERESIS). > > Sebastian > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > > From skayser at opencsw.org Thu Jan 8 19:20:15 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 19:20:15 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <49664208.60808@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> <49663E93.1040000@opencsw.org> <49664208.60808@acm.org> Message-ID: <496643DF.9010903@opencsw.org> Alessio wrote: > done, can you grab it again from /testing? Tested the i386 version and it works like a charm :) Thanks very much. > Sebastian Kayser wrote: >> Alessio wrote: >> >>> xterm 238 is now available on /testing >>> >> Works fine here, thanks. Could you ./configure with --enable-wide-chars >> so that CSWxterm can deal with UTF-8 ... p l e a s e :) >> >> Just give the following python snippet a try. >> >> python -c 'print u"\u00E4"' >> >> Right now CSWxterm gives ?? whereas the Solaris xterm properly displays >> the character ? (LATIN SMALL LETTER A WITH DIAERESIS). Sebastian From skayser at opencsw.org Thu Jan 8 19:38:24 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 19:38:24 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media In-Reply-To: <49651930.2070506@wbonnet.net> References: <49651930.2070506@wbonnet.net> Message-ID: <49664820.5040205@opencsw.org> Hi William, William Bonnet wrote: > I am looking the installation media of the latest (if possible) version > of Solaris 7 for the x86 platform. Anyone has an idea of how to find it ? yep, there is huge closet with ancient Solaris release right next door to me. So in case you haven't already found the installation media somewhere, just let me know. I will have to charge you a premium for fighting through piles of dust, though ... *g*. What are you up to with Solaris 7? Sebastian From william at wbonnet.net Thu Jan 8 19:28:30 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 08 Jan 2009 19:28:30 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media In-Reply-To: <49664820.5040205@opencsw.org> References: <49651930.2070506@wbonnet.net> <49664820.5040205@opencsw.org> Message-ID: <496645CE.2040804@wbonnet.net> Hi Sebastian > yep, there is huge closet with ancient Solaris release right next door > to me. So in case you haven't already found the installation media > somewhere, just let me know. > I would appreciate to have some iso to download please > I will have to charge you a premium for fighting through piles of dust, > though ... *g*. What about a beer next time we meet ? ;) > What are you up to with Solaris 7? > In Zurich we talk about the possibility to build packages for versions older than solaris 8. I have next to me a netra T1/105 waiting to become a build7s machine. I was looking for media to try to install a build7x computer. I have a couple of old pentium III based server waiting for a second life. Maybe i'll be able to install one of these boxes. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From yann at pleiades.fr.eu.org Fri Jan 9 00:03:32 2009 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Fri, 09 Jan 2009 00:03:32 +0100 Subject: [csw-maintainers] /testing openssl 0.9.8j Message-ID: <49668644.10903@pleiades.fr.eu.org> Hello all, I just build last openssl version, 0.9.8j, and in addition I created a ca_certificates providing common CA as discussed in a recent thread [1] The openssl_rt package now depends from this ca_certificates package for comptability purpose, as previous openssl distribution used to provide some CA. I put them into testing so I can have some feedbacks before pushing them into unstable: ca_certificates-20090108,REV=2009.01.08-SunOS5.8-all-CSW.pkg.gz openssl-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-all-CSW.pkg.gz openssl_devel-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_devel-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz openssl_rt-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_rt-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz openssl_utils-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_utils-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz As explained in the testing page [2], to test just type: pkg-get -s http://mirror.opencsw.org/opencsw/testing -U -u openssl or pkgutil -t http://mirror.opencsw.org/opencsw/testing/`uname -p`/`uname -r` -i openssl The /opt/csw/share/doc/ca-certificates/README.CSW contains some information about how to add custom CA certificates. Yann [1] http://lists.opencsw.org/pipermail/maintainers/2008-December/000409.html [2] http://buildfarm.opencsw.org/testing.html From bwalton at opencsw.org Fri Jan 9 02:49:47 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 08 Jan 2009 20:49:47 -0500 Subject: [csw-maintainers] /testing openssl 0.9.8j In-Reply-To: <49668644.10903@pleiades.fr.eu.org> References: <49668644.10903@pleiades.fr.eu.org> Message-ID: <1231465715-sup-4855@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Jan 08 18:03:32 -0500 2009: Hi Yann, > I just build last openssl version, 0.9.8j, and in addition I created a > ca_certificates providing common CA as discussed in a recent thread > [1] I'll try and get this installed on a few machines tomorrow. > The openssl_rt package now depends from this ca_certificates package for > comptability purpose, as previous openssl distribution used to provide > some CA. > The /opt/csw/share/doc/ca-certificates/README.CSW contains some > information about how to add custom CA certificates. A nice touch! :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Fri Jan 9 13:10:52 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 09 Jan 2009 13:10:52 +0100 Subject: [csw-maintainers] garv2 and multi-ISA build (i386/amd64) problems (target skipped) Message-ID: <49673ECC.1080300@opencsw.org> Hi all, i am having an issue with a multi-ISA build. To build and package mbuffer for i386 & amd64 i am using the three step approach suggested by Dago. build8x: gmake build-isa-i386 build10x: gmake merge build8x: gmake package When doing this, the post-configure-isa-amd64 target is _not_ run. When i substitute the step on build10x with build10x: gmake configure build10x: gmake merge then the post-configure-isa-amd64 target is run. So if someone with experience in garv2 and multi-ISA builds could have a quick look at my build description for mbuffer [1] i would appreciate it. Should i do things differently or is this a garv2 issue? Sebastian [1] https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/mbuffer/trunk/Makefile From phil at bolthole.com Fri Jan 9 17:38:42 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 9 Jan 2009 08:38:42 -0800 Subject: [csw-maintainers] note on "pure php" and similar packages Message-ID: <20090109163842.GG72675@bolthole.com> hi folks, just a heads-up; I have "put in writing", what maintainers have been moving towards, informally, for the last year or two: pure php or other arch neutral, web facing stuff, now officially belongs in /opt/csw/share/www rather than /opt/csw/[apacheX]/htdocs This brings us more in line with other common distributions, and I think also just makes more sense, given that we support multiple webservers. http://www.opencsw.org/standards/layout is where this is now mentioned. From dam at opencsw.org Fri Jan 9 18:19:15 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:19:15 +0100 Subject: [csw-maintainers] Updating all CSW packages now Message-ID: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> Hi, I am now updating all CSW packages installed on the buildfarm to current. As packages get removed and installed it may result in temporary build errors in case you are compiling right now. Best regards -- Dago From dam at opencsw.org Fri Jan 9 18:45:07 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:45:07 +0100 Subject: [csw-maintainers] garv2 and multi-ISA build (i386/amd64) problems (target skipped) In-Reply-To: <49673ECC.1080300@opencsw.org> References: <49673ECC.1080300@opencsw.org> Message-ID: <7A4EE425-1F5E-4327-B34C-67DD7FCB2012@opencsw.org> Hi Sebastian, Am 09.01.2009 um 13:10 schrieb Sebastian Kayser: > i am having an issue with a multi-ISA build. To build and package > mbuffer > for i386 & amd64 i am using the three step approach suggested by Dago. > > build8x: gmake build-isa-i386 > build10x: gmake merge > build8x: gmake package > > When doing this, the post-configure-isa-amd64 target is _not_ run. > When > i substitute the step on build10x with > > build10x: gmake configure > build10x: gmake merge > > then the post-configure-isa-amd64 target is run. > > So if someone with experience in garv2 and multi-ISA builds could > have a > quick look at my build description for mbuffer [1] i would appreciate > it. Should i do things differently or is this a garv2 issue? That was a bug. The target was not called due to the dependency chain automatically generated for the modulations. It is now fixed in r2772: One more thing: What you are trying to do here > # Solaris 10 on build10x has libm.so which points to libm.so.2. > libm.so.2 > # is however not available on Solaris 8. So we have to explicitly use > # libm.so.1 during linking and get rid of the -lm reference. Otherwise > # the package check on build8x when running "gmake package" fails. is also a flaw of checkpkg: When a package is build on Solaris 8 and Solaris 10 the complete package may fail when checkpkg'ed on Solaris 8 with the reason above. You were able to link to a specific version, but this may not always be possible. I have no idea on how this could be fixed in checkpkg apart from not making mixed packages or checking only on Solaris 10. Best regards -- Dago From dam at opencsw.org Fri Jan 9 18:59:57 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:59:57 +0100 Subject: [csw-maintainers] [csw-buildfarm] Updating all CSW packages now: DONE In-Reply-To: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> References: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> Message-ID: Hi, Am 09.01.2009 um 18:19 schrieb Dagobert Michelsen: > I am now updating all CSW packages installed on the buildfarm to > current. The update is finished, please resume your important work :-) Best regards -- Dago From bwalton at opencsw.org Fri Jan 9 20:14:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 09 Jan 2009 14:14:28 -0500 Subject: [csw-maintainers] /testing openssl 0.9.8j In-Reply-To: <49668644.10903@pleiades.fr.eu.org> References: <49668644.10903@pleiades.fr.eu.org> Message-ID: <1231528110-sup-5884@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Jan 08 18:03:32 -0500 2009: Hi Yann, > I put them into testing so I can have some feedbacks before pushing them > into unstable: I just updated a box here and then used GAR to fetch the package hosted from an https site (after removing custom wget options). It pulled the package down without any problems. So, it looks good to me! [That's pretty circumstantial evidence though.] Thanks for putting this together! :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From dam at opencsw.org Fri Jan 9 23:25:13 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 23:25:13 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49663523.2090603@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> Message-ID: <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> Hi, Am 08.01.2009 um 18:17 schrieb Sebastian Kayser: > Philip Brown wrote: >> Perhaps you could specify which ones you dropped to fix things, for >> the >> benefit of the current (in progress) ncurses maintainer > > The capabilities were HPA and VPA (horizontal and vertical absolute > positioning). > > $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep > '[hv]pa' > hpa=\E[%i%p1%dG, > vpa=\E[%i%p1%dd, > > Details and ncurses behaviour after i deleted vpa are documented in > the > bug that i had filed against mutt [1]. > > Sebastian > > [1] http://opencsw.org/bugtrack/view.php?id=2942. There is an updated ncurses for sparc/x86 with 32 and 64 bit in testing. Please verify that this solves your problem. Mutt has been recompiled to not use ncurses any more, so I can't exactly reproduce your testcase. The capabilities have been taken out from the description of 'xterm'. Best regards -- Dago From owigger at opencsw.org Sat Jan 10 20:34:43 2009 From: owigger at opencsw.org (Othmar Wigger) Date: Sat, 10 Jan 2009 20:34:43 +0100 Subject: [csw-maintainers] /testing xmgrace Message-ID: <4968F853.5020603@opencsw.org> I packaged grace (xmgrace) and put it on /testing. http://mirror.opencsw.org/testing/grace-5.1.22,REV=2009.01.10-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/grace-5.1.22,REV=2009.01.10-SunOS5.8-sparc-CSW.pkg.gz Grace stands for "GRaphing, Advanced Computation and Exploration of data." It is a WYSIWYG 2D plotting tool for the X Window System and Motif. Grace creates publication-quality output. It can be used from a point-and-click interface or scripted (either from the built-in programming language or through a number of language bindings). It performs both linear and nonlinear least-squares fitting to arbitrarily-complex user-defined functions, with or without constraints. Other analysis tools include FFT, integration and differentiation, splines, interpolation and smoothing. Please have a look at it and check for silly mistakes, as this is the first time I submit a package to openCSW. Othmar From dam at opencsw.org Sun Jan 11 00:02:42 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 11 Jan 2009 00:02:42 +0100 Subject: [csw-maintainers] /testing xmgrace In-Reply-To: <4968F853.5020603@opencsw.org> References: <4968F853.5020603@opencsw.org> Message-ID: <97294C48-5014-47C1-A9F7-133C9E27D9F0@opencsw.org> Hi Othmar, Am 10.01.2009 um 20:34 schrieb Othmar Wigger: > I packaged grace (xmgrace) and put it on /testing. Yes, and "samefile". Works like charm on x86 :-) Thanks! -- Dago From glaw at opencsw.org Sun Jan 11 11:21:16 2009 From: glaw at opencsw.org (Gary Law) Date: Sun, 11 Jan 2009 10:21:16 +0000 Subject: [csw-maintainers] CSWfacter released into testing Message-ID: Hi all There's a new CSWfacter in /home/testing ...feedback appreciated... Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sun Jan 11 11:23:01 2009 From: garylaw at garylaw.net (Gary Law) Date: Sun, 11 Jan 2009 10:23:01 +0000 Subject: [csw-maintainers] CSWpuppet released into testing Message-ID: Hi all There's a new CSWpuppet in /home/testing ...feedback appreciated... Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From skayser at opencsw.org Sun Jan 11 23:36:19 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 11 Jan 2009 23:36:19 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> Message-ID: <496A7463.5080805@opencsw.org> Dagobert Michelsen wrote: > Am 08.01.2009 um 18:17 schrieb Sebastian Kayser: >> Philip Brown wrote: >>> Perhaps you could specify which ones you dropped to fix things, for >>> the >>> benefit of the current (in progress) ncurses maintainer >> The capabilities were HPA and VPA (horizontal and vertical absolute >> positioning). >> >> $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep >> '[hv]pa' >> hpa=\E[%i%p1%dG, >> vpa=\E[%i%p1%dd, >> >> Details and ncurses behaviour after i deleted vpa are documented in >> the >> bug that i had filed against mutt [1]. >> >> Sebastian >> >> [1] http://opencsw.org/bugtrack/view.php?id=2942. > > There is an updated ncurses for sparc/x86 with 32 and 64 bit in > testing. Please verify that this solves your problem. Mutt has > been recompiled to not use ncurses any more, so I can't exactly > reproduce your testcase. The capabilities have been taken out > from the description of 'xterm'. Thanks, Dago. Tested the updated ncurses version with the CSWmutt version that the bug was filed against [1]. Solves the problem. Sebastian [1] http://csw.informatik.uni-erlangen.de/oldpkgs/current/i386/5.10/mutt-1.5.18,REV=2008.11.03-SunOS5.8-i386-CSW.pkg.gz From dam at opencsw.org Mon Jan 12 16:46:10 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 16:46:10 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <496A7463.5080805@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> <496A7463.5080805@opencsw.org> Message-ID: <38C29507-A04F-468C-BDB4-23737586C838@opencsw.org> Hi, Am 11.01.2009 um 23:36 schrieb Sebastian Kayser: > Thanks, Dago. Tested the updated ncurses version with the CSWmutt > version that the bug was filed against [1]. Solves the problem. I replaced now the modified terminal description with the option recommended by the ncurses maintainer Thomas Dickey --without-xterm-new This has the advantage to be more predictable than my feature hacking. Please give it a try so this can be released to current soon. Thanks! -- Dago From harpchad at opencsw.org Mon Jan 12 20:23:48 2009 From: harpchad at opencsw.org (Chad Harp) Date: Mon, 12 Jan 2009 13:23:48 -0600 Subject: [csw-maintainers] New version on libxslt in testing Message-ID: <496B98C4.7000606@opencsw.org> I've built a new version of libxslt (1.1.24). In addition to the version refresh it now exclude .la files which appears to be compatible with all existing packages EXCEPT libscrollkeeper (who's own .la refers to libxslt.la). I'm doing some testing, but package owners who depend on libxslt and/or libscrollkeeper may want to test compatibility. Thanks, Chad From dam at opencsw.org Mon Jan 12 20:44:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 20:44:02 +0100 Subject: [csw-maintainers] New version on libxslt in testing In-Reply-To: <496B98C4.7000606@opencsw.org> References: <496B98C4.7000606@opencsw.org> Message-ID: Hi Chad, Am 12.01.2009 um 20:23 schrieb Chad Harp: > I've built a new version of libxslt (1.1.24). In addition to the > version refresh it now exclude .la files which appears to be > compatible > with all existing packages EXCEPT libscrollkeeper (who's own .la > refers > to libxslt.la). > > I'm doing some testing, but package owners who depend on libxslt and/ > or > libscrollkeeper may want to test compatibility. Looks good with xmlstarlet. Best regards -- Dago From glaw at opencsw.org Mon Jan 12 20:56:04 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 19:56:04 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: New version released, with working man pages. Enjoy. -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Mon Jan 12 21:00:31 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 21:00:31 +0100 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: Hi Gary, Am 12.01.2009 um 20:56 schrieb Gary Law: > New version released, with working man pages. Enjoy. Nice touch to see you also working on upstream documentation :-) I haven't used puppet yet, are you using it in your environment? If yes, I would like to know how your typical deployment setup looks like. Thanks! -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Mon Jan 12 21:03:01 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 12 Jan 2009 15:03:01 -0500 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Mon Jan 12 15:00:31 -0500 2009: Hi Gary, > used puppet yet, are you using it in your environment? If yes, I would > like > to know how your typical deployment setup looks like. ...and does it work better under solaris than it did in the past? I'm running cfengine here (warts and all) but have been intrigued by puppet in the past. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Mon Jan 12 21:13:38 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 20:13:38 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: 2009/1/12 Dagobert Michelsen > Hi Gary, > Am 12.01.2009 um 20:56 schrieb Gary Law: > > New version released, with working man pages. Enjoy. > > > Nice touch to see you also working on upstream documentation :-) I haven't > used puppet yet, are you using it in your environment? If yes, I would like > to know how your typical deployment setup looks like. > I'm working on a new infrastructure build out at my current client. It remains to be seen if puppet is used, it seems to fit the bill and gets my recommendation, but the team here need to be comfortable with it, so we're still at proof of concept phase. In previous places I've worked with it in production, and whilst it has some idiosyncrasies, and out-and-out bugs, but beats maintaining by hand -- or alternatives like cfengine -- hands down IMHO. If you are interested I would recommend the book, Pulling Strings With Puppet, and the #puppet channel on IRC (where you can often find me too). -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From glaw at opencsw.org Mon Jan 12 21:21:31 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 20:21:31 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Message-ID: 2009/1/12 Ben Walton > ...and does it work better under solaris than it did in the past? > ...depends what issues you had. Ruby on Solaris used to be very hit and miss, which made puppet flaky. That's a solved problem. There's good support for some solaris specific features, like zones, see here for a quick example: http://www.madstop.com/managing-solaris-zones.html However, there is also at least a 10:1 ratio of Linux:Solaris users with puppet, so the community, documentation, support and so on is very Linux focussed. HTH Gary -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at wbonnet.net Mon Jan 12 20:50:21 2009 From: william at wbonnet.net (William Bonnet) Date: Mon, 12 Jan 2009 20:50:21 +0100 Subject: [csw-maintainers] Press release Message-ID: <496B9EFD.4090008@wbonnet.net> Hi In Zurich we talked about releasing a press communicate to announce the creation of the association. Wednesday in Paris there is meeting with Simon Pheeps. I don't know what is the current statut of the communication, but it would be certainly good to release tomorrow. So it will be only 24 hours old for the meeting (maybe he will have heard of it, and not yet forgotten ;) ). Sorry for the short delay, i forgot to send this email. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 12 22:06:35 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 12 Jan 2009 13:06:35 -0800 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Message-ID: <20090112210635.GH94353@bolthole.com> On Mon, Jan 12, 2009 at 08:21:31PM +0000, Gary Law wrote: > 2009/1/12 Ben Walton > > ...and does it work better under solaris than it did in the past? > > ...depends what issues you had. Ruby on Solaris used to be very hit and > miss, which made puppet flaky. That's a solved problem. well.. mostly solved. there are still apparently some "quirks" in x86 vs sparc, which is what has delayed our ruby release. Ben Walton took ruby on, but got discouraged when he and I examined some discrepancies between the arches. I think he's sorta trying to ignore it right now :-) would any other ruby enthusiast be willing to take a look? From bwalton at opencsw.org Mon Jan 12 22:14:24 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 12 Jan 2009 16:14:24 -0500 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <20090112210635.GH94353@bolthole.com> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> <20090112210635.GH94353@bolthole.com> Message-ID: <1231794738-sup-8690@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Mon Jan 12 16:06:35 -0500 2009: > Ben Walton took ruby on, but got discouraged when he and I examined some > discrepancies between the arches. > I think he's sorta trying to ignore it right now :-) > would any other ruby enthusiast be willing to take a look? Not discouraged, just distracted. This is actually still on my todo list. I've simply not had time to work on it since git became a priority here and the actual ruby packages I put together work (they've been running a rails site since late in the summer without issue). ...Hoping to get back to it shortly though, since git is going to be out shortly. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Mon Jan 12 22:18:03 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 21:18:03 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <20090112210635.GH94353@bolthole.com> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> <20090112210635.GH94353@bolthole.com> Message-ID: 2009/1/12 Philip Brown > well.. mostly solved. > The CSW stable Ruby works well for puppet. As for later versions, I cannot comment... -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihsan at opencsw.org Tue Jan 13 12:56:49 2009 From: ihsan at opencsw.org (Ihsan Dogan) Date: Tue, 13 Jan 2009 12:56:49 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <496B9EFD.4090008@wbonnet.net> References: <496B9EFD.4090008@wbonnet.net> Message-ID: <496C8181.3000907@opencsw.org> Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: > In Zurich we talked about releasing a press communicate to announce the > creation of the association. > > Wednesday in Paris there is meeting with Simon Pheeps. I don't know what > is the current statut of the communication, but it would be certainly > good to release tomorrow. So it will be only 24 hours old for the > meeting (maybe he will have heard of it, and not yet forgotten ;) ). > > Sorry for the short delay, i forgot to send this email. Othmar Wigger made a press release. Dago, do yo still have the press release? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Tue Jan 13 13:17:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 13:17:02 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <496C8181.3000907@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> Message-ID: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Hi Ihsan, Am 13.01.2009 um 12:56 schrieb Ihsan Dogan: > Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: >> In Zurich we talked about releasing a press communicate to announce >> the >> creation of the association. >> >> Wednesday in Paris there is meeting with Simon Pheeps. I don't know >> what >> is the current statut of the communication, but it would be certainly >> good to release tomorrow. So it will be only 24 hours old for the >> meeting (maybe he will have heard of it, and not yet forgotten ;) ). >> >> Sorry for the short delay, i forgot to send this email. > > Othmar Wigger made a press release. > Dago, do yo still have the press release? Yes, but unfortunately it is in German and I am on training right now :-( Anyway, here it is, maybe someone can translate today: > Effretikon, 6.12.2008 > > Teilnehmer der OpenCSW-Community trafen sich am Wochenende vom 6. > Dezember in Effretikon bei Z?rich zum ersten Mal in der 7-j?hrigen > Geschichte der Bewegung zu einer Konferenz. Anwesend war unter > anderem auch Philip Brown, der Initiator und Vaterfigur des > Projekts. Zweck des Treffens war die Neukonstituierung der Bewegung, > nachdem es letzten Sommer zu einer Spaltung gekommen war, die das > Projekt w?hrend Monaten gel?hmt hatte. > > Zweck von Blastwave/CSW war seit jeher das Bereitstellen von freier > Software f?r das Solaris Betriebssystem auf benutzerfreundliche Art. > CSW soll f?r Solaris ?hnliche Anwenderfreundlichkeit bieten wie > Ubuntu f?r Linux. > > Das OpenCSW-Projekt umfasst heute ?ber 1600 Softwarepakete und z?hlt > 2 Millionen Benutzer. Die Bereitstellung erfolgt ausschliesslich > durch Freiwillige und die Benutzung ist kostenlos. > > Das "Open Community Software"-Projekt (OpenCSW) ist dabei als Verein > nach schweizerischem Recht gegr?ndet worden. Die bisherigen > Teilnehmer desProjektes sind als Vereinsmitglieder herzlich > willkommen, neue Paket-Maintainer (mit entsprechendem Know-How) sind > stets erw?nscht. Der Verein arbeitet unentgeltlich und strebt keinen > Gewinn an. Sein Hauptzweck ist die Bereitstellung von > Softwarepaketen f?r das Solaris Operating Environment und die > Sicherung des Weiterbestehens als freie, community-basierte Software- > Distribution. > > Die Gr?ndungsversammlung w?hlte Philip Brown, Ihsan Dogan und > Dagobert Michelsen in den Vorstand des neu gegr?ndeten Vereins. Ein Bild gibt es unter Best regards -- Dago From bwalton at opencsw.org Tue Jan 13 15:53:32 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 09:53:32 -0500 Subject: [csw-maintainers] New version on libxslt in testing In-Reply-To: <496B98C4.7000606@opencsw.org> References: <496B98C4.7000606@opencsw.org> Message-ID: <1231858329-sup-7368@ntdws12.chass.utoronto.ca> Excerpts from Chad Harp's message of Mon Jan 12 14:23:48 -0500 2009: Hi Chad, > I'm doing some testing, but package owners who depend on libxslt and/or > libscrollkeeper may want to test compatibility. I just ran the xmlto build using the updated libxslt package and it looks good. xmlto only drives xsltproc though and doesn't actually link against any provided libraries. HTH. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From owigger at opencsw.org Tue Jan 13 16:54:11 2009 From: owigger at opencsw.org (Othmar Wigger) Date: Tue, 13 Jan 2009 16:54:11 +0100 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Message-ID: <496CB923.6050704@opencsw.org> Dagobert Michelsen wrote: >> Othmar Wigger made a press release. >> Dago, do yo still have the press release? > > Yes, but unfortunately it is in German and I am on training right > now :-( > Anyway, here it is, maybe someone can translate today: This is my translation. A native English speaker should proofread it before release! Effretikon/Zurich Members of the OpenCSW community met for the first time in the 7 year history of the movement at a conference in Switzerland during the week-end of December 6th. Also present was Philip Brown, the founding father of the project. One important point on the agenda was OpenCSW's legal reconstitution, because of last summer's breakup, which had paralyzed the project during several months. OpenCSW aims to provide ready-to-use free software for the Solaris platform. It is renown for its ease of use and its consistent end-to-end user experience. OpenCSW wants to be for Solaris what Ubuntu is for Linux. To date it counts around 1600 software packages and two million users worldwide. The packaging effort is carried out entirely by volunteers. Usage is free. The newly founded "Open Community Software" project (OpenCSW) is an association under Swiss law. All previous contributors are welcome as members. New package maintainers with the relevant skills are always welcome, too. All members of this not-for-profit association work without financial compensation. Its purpose is the continued provisioning of the Solaris Operating Environment with packaged software as a free, community based distribution. The founding members elected Philip Brown, Ihsan Dogan, and Dagobert Michelsen as members of the board. links: http://www.opencsw.org pictures: the OpenCSW board: http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277160178482290594 the founding association: http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277081573030645330 http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277081589838559890 (I suggest somebody please copy these pictures to www.opencsw.org and give them nicer URLs! Copyright for unlimited distribution is hereby granted.) Othmar From skayser at opencsw.org Tue Jan 13 16:59:47 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 13 Jan 2009 16:59:47 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Message-ID: <496CBA73.1030404@opencsw.org> Dagobert Michelsen wrote: > Am 13.01.2009 um 12:56 schrieb Ihsan Dogan: >> Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: >>> In Zurich we talked about releasing a press communicate to announce >>> the >>> creation of the association. >>> >>> Wednesday in Paris there is meeting with Simon Pheeps. I don't know >>> what >>> is the current statut of the communication, but it would be certainly >>> good to release tomorrow. So it will be only 24 hours old for the >>> meeting (maybe he will have heard of it, and not yet forgotten ;) ). >>> >>> Sorry for the short delay, i forgot to send this email. >> Othmar Wigger made a press release. >> Dago, do yo still have the press release? > > Yes, but unfortunately it is in German and I am on training right > now :-( > Anyway, here it is, maybe someone can translate today: > > [...] I just saw Othmars translation come in. As i was just finished with mine, i might as well send it also. Maybe makes it easier for the one fitting the pieces together. Translation: For the first time in its 7 year history, members of the OpenCSW community gathered for a miniconf in Effretikon, Zurich (Switzerland) on December 6th 2008. Attendees were happy to welcome Phil Brown, founder of the Community Software effort, as well as fellow maintainers from different parts of Europe. With the Blastwave/OpenCSW split in mind, which had put packaging efforts on hold over months, the main purpose of the meeting was to work out ways to avoid such situations in the future and settle on the direction the project should be heading to in the future. Since its beginning the intention of Blastwave/CSW was to provide free software for the Solaris Operating Environment in a user-friendly way. Today the OpenCSW project has 1600 software packages in its catalogs and counts close to 2 million users worldwide. The project is run by volunteers and provides its packages free of charge to everyone. As a result of the miniconf the "Open Community Software (OpenCSW) Project" was founded as an official association according to Swiss jurisdiction. The purpose of the association is to ensure the availability of the free, community-based software distribution known as OpenCSW. Its bylaws embody the core principles. Contributors are welcome to join the association, as are new package maintainers. The association works free of charge and is not geared towards making profit. Philip Brown, Ihsan Dogan, and Dagobert Michelsen were voted on the board of the found association by the founding association members. Sebastian From bwalton at opencsw.org Tue Jan 13 17:08:20 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 11:08:20 -0500 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <496CB923.6050704@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> <496CB923.6050704@opencsw.org> Message-ID: <1231862873-sup-1144@ntdws12.chass.utoronto.ca> Excerpts from Othmar Wigger's message of Tue Jan 13 10:54:11 -0500 2009: Hi Othmar, I'd offer only a small correction. :) Paragraph 1: > legal reconstitution, because of last summer's breakup, which had > paralyzed the project during several months. legal reconstitution, due to last summer's breakup, which saw the project paralyzed for several months. [I also suggest clarifying that the breakup was with blastwave or rewording this to something like: due to last summers internal turmoil, which had paralyzed... Others should maybe comment on this change though.] HTH, -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Tue Jan 13 17:16:50 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 08:16:50 -0800 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <496CB923.6050704@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> <496CB923.6050704@opencsw.org> Message-ID: <20090113161650.GC84975@bolthole.com> Minor correction which has nothing to do with translation :-) > To date it counts around 1600 software packages and two million users > worldwide. ls *pkg*|wc -l 1847 so, "over 1800 software packages" From harpchad at opencsw.org Tue Jan 13 18:34:30 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:34:30 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> Message-ID: <496CD0A6.1060105@opencsw.org> This latest libgpg_error build created some problems for my pidgin build. /opt/csw/lib/libgpg-error.la is still referenced by: /opt/csw/lib/libexslt.la /opt/csw/lib/libgcrypt.la /opt/csw/lib/libgnutls-extra.la /opt/csw/lib/libgnutls-openssl.la /opt/csw/lib/libgnutls.la /opt/csw/lib/libgnutlsxx.la /opt/csw/lib/libgpgme-pth.la /opt/csw/lib/libgpgme-pthread.la /opt/csw/lib/libgpgme.la This isn't restricted to libgpg_error, I've been running into this with other packages as well (the new libxml for example). I agree that we should be getting rid of the libtool files where possible, I'm just not sure how to address all of the dependencies. I've been using my own .la files in order to do some test builds, but that's just a temporary hack. Are there suggestion on how to deal with the legacy libtool files? Also, is there a mechanism in gar to filter them? I've been using custom prototypes to exclude them, but it would be better if I could let gar generate the prototype and filter the libtool files. Thanks, Chad Dagobert Michelsen wrote: > Hi, > > I am updating libgpg_error on all machines now. > > Best regards > > -- Dago > _______________________________________________ > buildfarm mailing list > buildfarm at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/buildfarm From phil at bolthole.com Tue Jan 13 18:41:24 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 09:41:24 -0800 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD0A6.1060105@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> Message-ID: <20090113174124.GA48829@bolthole.com> On Tue, Jan 13, 2009 at 11:34:30AM -0600, Chad Harp wrote: > This latest libgpg_error build created some problems for my pidgin build. > > /opt/csw/lib/libgpg-error.la is still referenced by: > > /opt/csw/lib/libexslt.la > /opt/csw/lib/libgcrypt.la > /opt/csw/lib/libgnutls-extra.la > /opt/csw/lib/libgnutls-openssl.la > /opt/csw/lib/libgnutls.la > /opt/csw/lib/libgnutlsxx.la > /opt/csw/lib/libgpgme-pth.la > /opt/csw/lib/libgpgme-pthread.la > /opt/csw/lib/libgpgme.la > all of the libgXXX stuff is going away as part of repackaging this week. dunno about libexslt. what package is that in? i guess lib xstl. rebuild, anyone? > sure how to address all of the dependencies. I've been using my own .la > files in order to do some test builds, but that's just a temporary hack. > > Are there suggestion on how to deal with the legacy libtool files? the temp hack sounds like a plan, until we can eradicate them more fully. filtering them out in gar would be nice too From bwalton at opencsw.org Tue Jan 13 18:45:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 12:45:28 -0500 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <20090113174124.GA48829@bolthole.com> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> Message-ID: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 2009: > filtering them out in gar would be nice too This is already happening, unless there was a regression. Dago implemented it a while back. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From harpchad at opencsw.org Tue Jan 13 18:45:37 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:45:37 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <20090113174124.GA48829@bolthole.com> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> Message-ID: <496CD341.2070104@opencsw.org> Philip Brown wrote: > dunno about libexslt. > > what package is that in? i guess lib xstl. > > rebuild, anyone? I've got a new xslt build in testing, its had good feedback so I'll go ahead and move it to newpkgs. From harpchad at opencsw.org Tue Jan 13 18:50:42 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:50:42 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Message-ID: <496CD472.7080907@opencsw.org> Probably my fault for using gar v1. Is gar v2 ready for regular use? If so maybe we should change the newpkg- target to make v2 the default. Ben Walton wrote: > Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 2009: > >> filtering them out in gar would be nice too > > This is already happening, unless there was a regression. Dago > implemented it a while back. > > -Ben > > > > ------------------------------------------------------------------------ > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bwalton at opencsw.org Tue Jan 13 18:55:35 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 12:55:35 -0500 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD472.7080907@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> <496CD472.7080907@opencsw.org> Message-ID: <1231869256-sup-3518@ntdws12.chass.utoronto.ca> Excerpts from Chad Harp's message of Tue Jan 13 12:50:42 -0500 2009: > Probably my fault for using gar v1. Is gar v2 ready for regular use? > If so maybe we should change the newpkg- target to make v2 the default. I'm not sure what Dago's thoughts on this are. For my purposes, all of my packages are working fine under v2. That being said, my packages are at worst annoying to build...not overly complicated. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Tue Jan 13 18:55:41 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 18:55:41 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Message-ID: <503C7C8F-B48B-4D40-807B-AA53633133F9@opencsw.org> Hi, Am 13.01.2009 um 18:45 schrieb Ben Walton: > Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 > 2009: > >> filtering them out in gar would be nice too > > This is already happening, unless there was a regression. Dago > implemented it a while back. Yes, if you use mGAR v2 .la-files are excluded by default. Best regards -- Dago From phil at bolthole.com Tue Jan 13 18:57:23 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 09:57:23 -0800 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD341.2070104@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> Message-ID: <20090113175723.GA76298@bolthole.com> On Tue, Jan 13, 2009 at 11:45:37AM -0600, Chad Harp wrote: > Philip Brown wrote: > > dunno about libexslt. > > > > what package is that in? i guess lib xstl. > > > > rebuild, anyone? > > I've got a new xslt build in testing, its had good feedback so I'll go > ahead and move it to newpkgs. ok, thanks. From dam at opencsw.org Tue Jan 13 18:57:42 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 18:57:42 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231869256-sup-3518@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> <496CD472.7080907@opencsw.org> <1231869256-sup-3518@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 13.01.2009 um 18:55 schrieb Ben Walton: > Excerpts from Chad Harp's message of Tue Jan 13 12:50:42 -0500 2009: >> Probably my fault for using gar v1. Is gar v2 ready for regular use? >> If so maybe we should change the newpkg- target to make v2 the >> default. > > I'm not sure what Dago's thoughts on this are. For my purposes, all > of my packages are working fine under v2. That being said, my > packages are at worst annoying to build...not overly complicated. From time to time a bug comes to the surface in mGAR v2, but I guess the best thing is to move forward, use it as default and fix bugs as they occur. I am making v2 now default. Best regards -- Dago From dam at opencsw.org Tue Jan 13 19:23:36 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 19:23:36 +0100 Subject: [csw-maintainers] Call for testers Message-ID: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Hi, there are packages piling up in testing/ and there seem to be only very little feedback. How about a "call for testers" on the main page? Having professional testers would both help maintainers and improve quality. Best regargs -- Dago From phil at bolthole.com Tue Jan 13 19:42:51 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 10:42:51 -0800 Subject: [csw-maintainers] Call for testers In-Reply-To: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Message-ID: <20090113184251.GA34848@bolthole.com> On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: > Hi, > > there are packages piling up in testing/ and there seem to be > only very little feedback. How about a "call for testers" on > the main page? Having professional testers would both help > maintainers and improve quality. Another suggestion: since we have a "special, custom" testing page rather than just a raw inventory thingie.. it might be nice to allow some kind of "click here to say you tested it" button. Not sure how or where it would store the info though. Also note that if you decide to do this, it should track both the filename, AND THE CHECKSUM, since in theory, maintainers could put a newer version of a package, with the exact same filename, in testing. Also, since the page is "public", it should allow feedback from non-maintainers. From dam at opencsw.org Tue Jan 13 19:53:09 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 19:53:09 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090113184251.GA34848@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> Message-ID: <0D70CADA-4838-41CE-B68F-8278399E80A0@opencsw.org> Hi Phil, Am 13.01.2009 um 19:42 schrieb Philip Brown: > On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: >> there are packages piling up in testing/ and there seem to be >> only very little feedback. How about a "call for testers" on >> the main page? Having professional testers would both help >> maintainers and improve quality. > > Another suggestion: since we have a "special, custom" testing page > rather > than just a raw inventory thingie.. it might be nice to allow some > kind of > "click here to say you tested it" button. > Not sure how or where it would store the info though. > > Also note that if you decide to do this, it should track both the > filename, > AND THE CHECKSUM, since in theory, maintainers could put a newer > version of > a package, with the exact same filename, in testing. > > Also, since the page is "public", it should allow feedback from > non-maintainers. Nice idea, but I am swamped with work and the GAR docs need to be written too. It would be very cool if someone else could jump on this one. Best regards -- Dago From trygvel at opencsw.org Wed Jan 14 01:32:35 2009 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 14 Jan 2009 01:32:35 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Message-ID: <496D32A3.6040402@opencsw.org> Dagobert Michelsen wrote: > Hi, > > there are packages piling up in testing/ and there seem to be > only very little feedback. How about a "call for testers" on > the main page? Having professional testers would both help > maintainers and improve quality. One thing that might help with getting non-maintainers (maintainer of the specific package, not all maintainers) to test stuff might be to have a page describing test cases to run etc. This will vary wildly between packages, but for some packages it might be very useful. I'm planning to add a jetty6-dev page on the wiki [1] the next time I'm rebuilding the Jetty package just to serve as a reminder for myself on how to verify that the package work. [1]: http://wiki.opencsw.org/packages -- Trygve From skayser at opencsw.org Wed Jan 14 01:51:46 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 14 Jan 2009 01:51:46 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090113184251.GA34848@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> Message-ID: <496D3722.7020004@opencsw.org> Philip Brown wrote: > On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: >> there are packages piling up in testing/ and there seem to be >> only very little feedback. No feedback may sometimes be a good sign. Is there any way to track the number of downloads for a particular package from testing/? >> How about a "call for testers" on the main page? Do you mean testers as in people who specifically test packages inside out? Or just a call to get more people to install packages from testing/ and provide feedback in case they notice something strange? Is testing/ mentioned on the website at all? How about a small paragraph about it on the user guide page [1] under the section "Release Program"? That way users could also be made aware of it and i suppose there are always people out there who are interested in testing out the latest "stuff". >> Having professional testers would both help >> maintainers and improve quality. What about doing it like Debian does it? They have three branches: stable, testing, unstable. Development happens in unstable and packages move to testing after a non-bug-encountered grace period has passed. Developers (maintainers) usually subscribe to unstable and update frequently. Thus, the chance that someone hits a hidden bug is increased. Experimental users can also subscribe to unstable (which would be testing/ in our case) if they like bleeding edge. Does pkg-get/pkgutil offer an easy way to blend in the testing/ tree so that testing/ wouldn't need to be a full release? I imagine something like implicitly using the pkgutil -t option set to the testing tree all the time. >> Another suggestion: since we have a "special, custom" testing page >> rather than just a raw inventory thingie.. Do you mean this one [2]? Hadn't heard of it before. Is it linked from anywhere else on the page? Could you have a look at the package feed on the page. From what i see the last package in the feed is from Dec 12, but there are already more recent packages in testing/. > Also note that if you decide to do this, it should track both the filename, > AND THE CHECKSUM, since in theory, maintainers could put a newer version of > a package, with the exact same filename, in testing. This would not only be interesting for the feedback, but also for pkg-get / pkgutil. Can they be forced to install a package from testing when the filename and version remain identical (which is per default the case for GAR builds done on the same day)? So far i pkgrm'ed the affected package and then installed the new version. But maybe there is something like a --reinstall option? Sebastian [1] http://opencsw.org/userguide [2] http://mirror.opencsw.org/testing.html From bonivart at opencsw.org Wed Jan 14 10:08:22 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 14 Jan 2009 10:08:22 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <496D3722.7020004@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> Message-ID: <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> On Wed, Jan 14, 2009 at 1:51 AM, Sebastian Kayser wrote: > Does pkg-get/pkgutil offer an easy way to blend in the testing/ tree so > that testing/ wouldn't need to be a full release? I imagine something > like implicitly using the pkgutil -t option set to the testing tree all > the time. No, using -t adds the specified location to what you already have set as mirror in pkgutil.conf. So, yes, pkgutil can blend in the testing tree without it needing to be a full release. I wanted it to work for those who produce a few packages of their own that depend on the CSW stack. That way they don't have to mirror the whole stack locally. > This would not only be interesting for the feedback, but also for > pkg-get / pkgutil. Can they be forced to install a package from testing > when the filename and version remain identical (which is per default the > case for GAR builds done on the same day)? There's no --reinstall option in pkgutil but if you remove the package you want to reinstall first, you will always get the latest one at the next install if you don't have a caching problem in your proxy for example. -- /peter From pfelecan at opencsw.org Wed Jan 14 10:30:47 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 14 Jan 2009 10:30:47 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> (Peter Bonivart's message of "Wed\, 14 Jan 2009 10\:08\:22 +0100") References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> Message-ID: Peter Bonivart writes: > On Wed, Jan 14, 2009 at 1:51 AM, Sebastian Kayser wrote: >> This would not only be interesting for the feedback, but also for >> pkg-get / pkgutil. Can they be forced to install a package from testing >> when the filename and version remain identical (which is per default the >> case for GAR builds done on the same day)? > > There's no --reinstall option in pkgutil but if you remove the package > you want to reinstall first, you will always get the latest one at the > next install if you don't have a caching problem in your proxy for > example. This could be helped with a build sequence number, as used in rpm and deb packages; this can be enforced in a build system such as gar, consequently two successive builds have different signatures --- btw, the package's md5 sum of the package offers such a thing. -- Peter From dam at opencsw.org Wed Jan 14 14:57:44 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 14 Jan 2009 14:57:44 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD341.2070104@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> Message-ID: <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> Hi Chad, Am 13.01.2009 um 18:45 schrieb Chad Harp: > Philip Brown wrote: >> dunno about libexslt. >> >> what package is that in? i guess lib xstl. >> >> rebuild, anyone? > > I've got a new xslt build in testing, its had good feedback so I'll go > ahead and move it to newpkgs. We should make libxslt and libxml2 look similar in terms of splitting _devel, python bindings and 64 bit support. I would recommend copying over the necessary descriptions from the libxml2 Makefile for package splitting etc. Please let me know if I can be of any help here. Best regards -- Dago From phil at bolthole.com Wed Jan 14 15:48:28 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 14 Jan 2009 06:48:28 -0800 Subject: [csw-maintainers] Call for testers In-Reply-To: References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> Message-ID: <20090114144828.GA91550@bolthole.com> On Wed, Jan 14, 2009 at 10:30:47AM +0100, Peter FELECAN wrote: > This could be helped with a build sequence number, as used in rpm and > deb packages; this can be enforced in a build system such as gar, > consequently two successive builds have different signatures --- btw, > the package's md5 sum of the package offers such a thing. or, gar could keep a record of built packages somewhere per-user, and do the yyyy.mm.dd.1, .2, .2 thing automatically From skayser at opencsw.org Wed Jan 14 17:33:38 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 14 Jan 2009 17:33:38 +0100 Subject: [csw-maintainers] New pkg in testing/: mbuffer 20090106 Message-ID: <496E13E2.7070601@opencsw.org> Hi all, i just uploaded a new package (simple binary + some docs) to testing/. If anyone would like to give it a try, feel free to do so. Feedback appreciated. http://mirror.opencsw.org/testing/mbuffer-20090106,REV=2009.01.14-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/mbuffer-20090106,REV=2009.01.14-SunOS5.8-sparc-CSW.pkg.gz mbuffer comes in handy when you do zfs send / recv over a network. You can put it in between the send and recv processes and it will provide a buffer that makes up for pauses in network or disk IO. Description from the mbuffer website: mbuffer is a tool to buffer data streams. Its special feature is to show the I/O rate and summary to the user. This was firstly the main reason I developed it. It is especially useful, if you are writing backups to fast tape drives or libraries. Those drives tend to stop and rewind if they have a buffer underrun. This so called tape screwing reduces the lifetime of the motors. mbuffer can prevent buffer underruns, if used correctly and speed up the whole backup process. Sebastian From trygvel at opencsw.org Wed Jan 14 19:38:53 2009 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 14 Jan 2009 19:38:53 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090114144828.GA91550@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> <20090114144828.GA91550@bolthole.com> Message-ID: <496E313D.5090903@opencsw.org> Philip Brown wrote: > On Wed, Jan 14, 2009 at 10:30:47AM +0100, Peter FELECAN wrote: >> This could be helped with a build sequence number, as used in rpm and >> deb packages; this can be enforced in a build system such as gar, >> consequently two successive builds have different signatures --- btw, >> the package's md5 sum of the package offers such a thing. > > or, gar could keep a record of built packages somewhere per-user, and > do the yyyy.mm.dd.1, .2, .2 thing automatically This really don't belong in the build tool IMO, but rather as a part of the submission process to a package queue (the testing queue in this case). Having a tool like Debian's dput [1]. [1]: http://www.digipedia.pl/man/dput.1.html -- Trygve From harpchad at opencsw.org Wed Jan 14 21:31:31 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 14 Jan 2009 14:31:31 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> Message-ID: <496E4BA3.9050507@opencsw.org> Sounds like a good idea, I'll get the packages split up. Dagobert Michelsen wrote: > Hi Chad, > > Am 13.01.2009 um 18:45 schrieb Chad Harp: >> Philip Brown wrote: >>> dunno about libexslt. >>> >>> what package is that in? i guess lib xstl. >>> >>> rebuild, anyone? >> I've got a new xslt build in testing, its had good feedback so I'll go >> ahead and move it to newpkgs. > > We should make libxslt and libxml2 look similar in terms > of splitting _devel, python bindings and 64 bit support. > I would recommend copying over the necessary descriptions > from the libxml2 Makefile for package splitting etc. > Please let me know if I can be of any help here. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Wed Jan 14 21:46:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 14 Jan 2009 21:46:02 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496E4BA3.9050507@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> <496E4BA3.9050507@opencsw.org> Message-ID: <06AE6DC8-BE0B-4CB6-AE58-41AAA88158CF@opencsw.org> Hi Chad, Am 14.01.2009 um 21:31 schrieb Chad Harp: > Dagobert Michelsen wrote: >> Am 13.01.2009 um 18:45 schrieb Chad Harp: >>> Philip Brown wrote: >>>> dunno about libexslt. >>>> >>>> what package is that in? i guess lib xstl. >>>> >>>> rebuild, anyone? >>> I've got a new xslt build in testing, its had good feedback so >>> I'll go >>> ahead and move it to newpkgs. >> >> We should make libxslt and libxml2 look similar in terms >> of splitting _devel, python bindings and 64 bit support. >> I would recommend copying over the necessary descriptions >> from the libxml2 Makefile for package splitting etc. >> Please let me know if I can be of any help here. > > Sounds like a good idea, I'll get the packages split up. Fine, and please file bug reports on the packages depending on libxslt to depend on libxslt_rt after release. Thanks and best regards -- Dago PS: Please avoid top-posting if possible :-) From william at wbonnet.net Thu Jan 15 21:04:39 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 21:04:39 +0100 Subject: [csw-maintainers] svn tags use and naming convention Message-ID: <496F96D7.3060703@wbonnet.net> Hi Do we have a standard for the use of tags, branches and associated naming ? If not i can propose one cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bwalton at opencsw.org Thu Jan 15 22:18:08 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 15 Jan 2009 16:18:08 -0500 Subject: [csw-maintainers] git on buildfarm Message-ID: <1232054103-sup-9301@ntdws12.chass.utoronto.ca> Hi All, Just a heads up that if you're interested in Git as an SCM tool, it's now on the build machines. I've also installed the emacs VCS module (M-x load-file RET /opt/csw/share/emacs/site-lisp/git.el; M-x git-status) and the svn gateway. I haven't played with the svn gateway yet (I plan to), so I won't tell you it's good or bad. If anyone is interested, I'll let you know of my experiences after trying it out with a GAR package description. Cheers, -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From william at wbonnet.net Thu Jan 15 22:32:39 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 22:32:39 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <496FAB77.8000208@wbonnet.net> Hi, Since OpenCSW is a pretty young project, if we consider the point of view of the new organization, website, tools, buildfarm, etc. there are a lot of things to do, to improve or to update. We will have to work of this different things, and we need some minimum coordination of effort. I was wondering about a way to make things happen and happen faster and to optimize effort. What about creating thematic months ? The proposal is to focus for a given month on a specific subject. Of course it does not mean that other subject cannot be processed or should not. It does not mean that it has to be mandatory. But it could help to define a roadmap, and create some motivation to work on given subject. For instance themes could be (just an example...) February : communication goal is to improve web site, add content, write presentation of the project and tools (, slides, etc. to produce all the material we will need to make presentation, improve google rank, communicate with Sun and other corporates, create links and relation with other open source project etc.) March : move package to GAR Kind of hacking session. Goal is to add to gar as much as possible of existing packages. This will go through maintainer training on how to use gar, to write and produce howto and tutorials (if needed because Dago already did a lot to create documentation) April : Package update Goal is to move to up to date version of as much as possible of existing packages May : Bug hunting Goal is to fix and close as many as possible of bugs and entries in mantis June : Continus integration Goal is to add to continuus integration as much as possible of existing package July : Build world Goal is to setup a procedure that will be used to rebuild every packages from an blank environment. August : Summer camp September : Mass porting and package creation Goal is to create as much as possible new packages. This include creating and processing requested package list, etc. October : To be defined November : To be defined December : General meeting ! Once we will have a frozen theme list and roadmap, this should be of course published on the web site and made publicly available. What about the idea ? Feedback welcomed ! cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From harpchad at opencsw.org Thu Jan 15 23:53:58 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 15 Jan 2009 16:53:58 -0600 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FAB77.8000208@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> Message-ID: <496FBE86.3030403@opencsw.org> I like the idea and I've got another theme for you (or perhaps and extension of the April theme): Clean up remaining libtool (*.la) files (even if it's just repackaging old builds). Somewhere in here should fit a release schedule for the stable branch. William Bonnet wrote: > Hi, > > Since OpenCSW is a pretty young project, if we consider the point of > view of the new organization, website, tools, buildfarm, etc. there are > a lot of things to do, to improve or to update. > > We will have to work of this different things, and we need some minimum > coordination of effort. I was wondering about a way to make things > happen and happen faster and to optimize effort. What about creating > thematic months ? > > The proposal is to focus for a given month on a specific subject. Of > course it does not mean that other subject cannot be processed or should > not. It does not mean that it has to be mandatory. But it could help to > define a roadmap, and create some motivation to work on given subject. > > > For instance themes could be (just an example...) > > February : communication > > goal is to improve web site, add content, write presentation of the > project and tools (, slides, etc. to produce all the material we will > need to make presentation, improve google rank, communicate with Sun and > other corporates, create links and relation with other open source > project etc.) > > March : move package to GAR > > Kind of hacking session. Goal is to add to gar as much as possible of > existing packages. This will go through maintainer training on how to > use gar, to write and produce howto and tutorials (if needed because > Dago already did a lot to create documentation) > > April : Package update > > Goal is to move to up to date version of as much as possible of > existing packages > > May : Bug hunting > > Goal is to fix and close as many as possible of bugs and entries in > mantis > > June : Continus integration > > Goal is to add to continuus integration as much as possible of > existing package > > July : Build world > > Goal is to setup a procedure that will be used to rebuild every > packages from an blank environment. > > August : Summer camp > > September : Mass porting and package creation > > Goal is to create as much as possible new packages. This include > creating and processing requested package list, etc. > > October : To be defined > > November : To be defined > > December : General meeting ! > > > Once we will have a frozen theme list and roadmap, this should be of > course published on the web site and made publicly available. > > What about the idea ? > > Feedback welcomed ! > > cheers > From william at wbonnet.net Thu Jan 15 23:01:05 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 23:01:05 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FBE86.3030403@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <496FBE86.3030403@opencsw.org> Message-ID: <496FB221.4010702@wbonnet.net> Hi > Somewhere in here should fit a release schedule for the stable branch. > Yes it is just a proposal, a first work version >> February : communication >> According to me it looks like the highest priority. We have to use the momentum we created and even increase it. It will also help to attract new members and maintainers. >> March : move package to GAR >> Looks to me better to have everything in GAR before starting to update and fix things. >> April : Package update >> I think it has to be done before bug hunting campaign. Update will fix some bug and create new one. So no need to spend to much time on fixing something we are going to update. Better test it and fix it after :) >> May : Bug hunting >> A prerequisite to next stable release ? >> June : Continus integration >> >> Should it be done before bug hunting and update ? Trygve any suggestion on the best way to use Hudson ? Cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From skayser at opencsw.org Fri Jan 16 00:16:21 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 16 Jan 2009 00:16:21 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496F96D7.3060703@wbonnet.net> References: <496F96D7.3060703@wbonnet.net> Message-ID: <496FC3C5.7060709@opencsw.org> William Bonnet wrote: > Do we have a standard for the use of tags, branches and associated naming ? > > If not i can propose one Me too :) I would love to see a tag for each package version that has been pushed to current/. Something along the way of: tags/4.4.20,REV=2009.01.13 This way one could know whether a GAR build description is just a stub or actually has been used to build a released package. Sebastian From william at wbonnet.net Thu Jan 15 23:29:23 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 23:29:23 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <496FB8C3.2020508@wbonnet.net> Hi Sebastian > William Bonnet wrote: > >> Do we have a standard for the use of tags, branches and associated naming ? >> >> If not i can propose one >> > > Me too :) Cool. So i guess you are the taker ;) I have more than enough things in my todo list. > I would love to see a tag for each package version that has > been pushed to current/. Something along the way of: > > tags/4.4.20,REV=2009.01.13 > > This way one could know whether a GAR build description is just a stub > or actually has been used to build a released package. > I had quite the same idea. We have to think about the way it could be use in dependencies (from a make world point of view), and write some documentation to propose a standard. cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 01:08:18 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 15 Jan 2009 16:08:18 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FBE86.3030403@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <496FBE86.3030403@opencsw.org> Message-ID: <20090116000818.GA10797@bolthole.com> On Thu, Jan 15, 2009 at 04:53:58PM -0600, Chad Harp wrote: > I like the idea and I've got another theme for you (or perhaps and > extension of the April theme): Clean up remaining libtool (*.la) files > (even if it's just repackaging old builds). > > Somewhere in here should fit a release schedule for the stable branch. that is larger than a "theme for a month". it is a very large effort, that takes more than a month. and the first step, is someone volunteering to actually put it together. From bwalton at opencsw.org Fri Jan 16 01:22:40 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 15 Jan 2009 19:22:40 -0500 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <1232065192-sup-6659@ntdws12.chass.utoronto.ca> Excerpts from Sebastian Kayser's message of Thu Jan 15 18:16:21 -0500 2009: > tags/4.4.20,REV=2009.01.13 GAR is sticking the svn rev id into the PSTAMP portion of the pkginfo files, so for anything released as of Dago's implementation of this feature, the relevant info could be retrieved to start this off... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bonivart at opencsw.org Fri Jan 16 10:20:03 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 16 Jan 2009 10:20:03 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FAB77.8000208@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> Message-ID: <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> On Thu, Jan 15, 2009 at 10:32 PM, William Bonnet wrote: > Hi, > > Since OpenCSW is a pretty young project, if we consider the point of > view of the new organization, website, tools, buildfarm, etc. there are > a lot of things to do, to improve or to update. > > We will have to work of this different things, and we need some minimum > coordination of effort. I was wondering about a way to make things > happen and happen faster and to optimize effort. What about creating > thematic months ? > > The proposal is to focus for a given month on a specific subject. Of > course it does not mean that other subject cannot be processed or should > not. It does not mean that it has to be mandatory. But it could help to > define a roadmap, and create some motivation to work on given subject. Great idea! But how about starting with all the stuff in the agenda for the IRL meeting? If I'm correct, almost all of it was skipped due to time constraints but it's important and it's very quiet about it now. http://wiki.opencsw.org/irl-meeting -- /peter From dam at opencsw.org Fri Jan 16 12:03:48 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 16 Jan 2009 12:03:48 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> Hi, Am 16.01.2009 um 00:16 schrieb Sebastian Kayser: > William Bonnet wrote: >> Do we have a standard for the use of tags, branches and associated >> naming ? >> >> If not i can propose one > > Me too :) I would love to see a tag for each package version that has > been pushed to current/. Something along the way of: > > tags/4.4.20,REV=2009.01.13 > > This way one could know whether a GAR build description is just a stub > or actually has been used to build a released package. I would recommend using tags/-4.4.20,REV=2009.01.13 That way you get a decent directory name when you only check out that tag. I added a new target to make for making this as easy as possible: > dam at login [login]:/home/dam/mgar/pkg/libtasn1/trunk > gmake scm-tag- > release > /opt/csw/bin/svn cp ../trunk ../tags/libtasn1-1.7,REV=2009.01.16 > A ../tags/libtasn1-1.7,REV=2009.01.16 > dam at login [login]:/home/dam/mgar/pkg/libtasn1/trunk > You must still commit this, of course. Best regards -- Dago From dam at opencsw.org Fri Jan 16 12:20:09 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 16 Jan 2009 12:20:09 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> Message-ID: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> Hi Peter, Am 16.01.2009 um 10:20 schrieb Peter Bonivart: > Great idea! But how about starting with all the stuff in the agenda > for the IRL meeting? If I'm correct, almost all of it was skipped due > to time constraints but it's important and it's very quiet about it > now. > > http://wiki.opencsw.org/irl-meeting Yes, that was skipped, but as I browse the list a lot of it is already in progress. However, Williams' propositions go more into the direction of enhancing the quality of packages directly instead of tuning the process (which also should lead to better quality btw). Do you have a specific point which you want to have addressed or inserted into Williams agenda? Best regards -- Dago From william at wbonnet.net Fri Jan 16 12:20:14 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 12:20:14 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> Message-ID: <49706D6E.5000106@wbonnet.net> Hi > I would recommend using > tags/-4.4.20,REV=2009.01.13 > > That way you get a decent directory name when you only check out that > tag. > Right I am wondering if we should not even need something more precise and complex. It would be useful to be able to make a distinction in tags between version used in testing, unstable and stable. For instance i can imagine a process including steps from the following list (not now but in a few weeks or months). The maintainer create its package, tags it and release it to testing Then the "unstable catalog maker (aka Phil)" or whatever automatic procedure provided by continuus integation, build it (optional ?), tags it whith an "unstable" tag, and release it Then the stable release manager tags include a given version of the package in the stable release, and tags it. Even if contents are sometime the same (by content i mean packge creation scripts, etc.), the tags will have to be the same. So what about tags/-4.4.20,REV=2009.01.13-- source will be testing, unstable, or stable release version will be a "version number of the release" we can image that for stable it coulb be like REV=09/05 for stableversion release in May 2009, for unstable it could just be an incremental number in the year (ie week number), and for testing it can be up to he maintainer (sequential number, or beta1, beta2, etc. or default to 'sid' (still in development). This may need different targets ? just to make it simple to use and prevent argument errors creating a wrong tag > You must still commit this, of course. > Thanks :) cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Fri Jan 16 12:27:10 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 12:27:10 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> Message-ID: <49706F0E.2080004@wbonnet.net> Dagobert Michelsen a ?crit : > Hi Peter, > > Am 16.01.2009 um 10:20 schrieb Peter Bonivart: > >> Great idea! But how about starting with all the stuff in the agenda >> for the IRL meeting? If I'm correct, almost all of it was skipped due >> to time constraints but it's important and it's very quiet about it >> now. >> >> http://wiki.opencsw.org/irl-meeting >> > > Yes, that was skipped, but as I browse the list a lot of it > is already in progress. However, Williams' propositions go more > into the direction of enhancing the quality of packages > directly instead of tuning the process (which also should lead > to better quality btw). > Peter is right, this point have to be processed. But i think improving the process should be a background task. It is easier to gather some people to work on a specific more technical point, like moving packages to GAR or creating new packages, than to focus effort on the process improvement. Moreover, doing this, will make things easier for people having less time to contribute. But ... process is not forgotten :) If we want to setup this thematics agenda, some people will have to work on advance on the process. Each coming theme will raise discussion about the process improvement (what is missing, out dated, which documentation is missing etc.). This will have certainly to be done during the month before the theme (that's also why i propose to start by commnication, there is no process prerequisite). Running a "thematic event" can go through simple steps like : . week one we talk about what has to be done, . week 2 and 3 people work on different task, according to their free time, . week 4 everyone work is integrated, commited, tested and published That's just a general process. It will have to be tuned to fit the real life and may chance according to the subjects cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 15:48:04 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 16 Jan 2009 06:48:04 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49706F0E.2080004@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> Message-ID: <20090116144804.GB2576@bolthole.com> On Fri, Jan 16, 2009 at 12:27:10PM +0100, William Bonnet wrote: > > If we want to setup this thematics agenda, some people will have to work > on advance on the process. Each coming theme will raise discussion about > the process improvement (what is missing, out dated, which documentation > is missing etc.). This will have certainly to be done during the month > before the theme (that's also why i propose to start by commnication, > there is no process prerequisite). one of the biggest "challenges" about a volunteer organisation, is that you cant just write up a project agenda, and then assign people to do it. You need... volunteers! So, I would suggest that you first start with a wiki page on "here are themes I propose", then see if there are any extra ones proposed, and then see who signs up to handle/drive each of them. Finally, based on who is doing each bit, work out schedules for each. From william at wbonnet.net Fri Jan 16 22:13:13 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 22:13:13 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090116144804.GB2576@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> Message-ID: <4970F869.7060601@wbonnet.net> Hi Phil > one of the biggest "challenges" about a volunteer > organisation, is that you cant just write up a project agenda, and then > assign people to do it. You need... volunteers! > That's right ! I fully agree . In order to recruit volunteers we first have to set up the project. As you wrote below it comes through writing wiki page, and documentation and many thing else. Gathering volunteers also requires to be attractive. Being attractive often means to start the work on the project and to communicate about this until you reach a kind of "critical mass". It's not gonna be a easy thing, but i believe it is worth to try :) It will help to create the buzz around, it will help focusing some effort on mutual goal, and ... many things :) It is important to me that this project or themes or whatever you call it, must *not be* a mandatory thing or an exclusive thing. It has to be a kind of roadmap to highlight important task, to try to improve the quality of the packages and service we deliver. It should not prevent people to work on other things. > So, I would suggest that you first start with a wiki page on > "here are themes I propose", > then see if there are any extra ones proposed, > and then see who signs up to handle/drive each of them. > Finally, based on who is doing each bit, work out schedules for each. > For sure. It's a good advice. First of all i sent this email to see how people are feeling about this idea. I already had a few positive feedback, i will start to work on the wiki page in the next days. I can setup a couple things, but i'll need help :) and i'll ask for... Don't hesitate to comment more or give your opinion about this. And don't hesitate to submit your ideas for the agenda and discuss about subjects. Sometimes it is easier to discuss about this by email rather by editing wiki pages. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 23:22:36 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 16 Jan 2009 14:22:36 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4970F869.7060601@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> Message-ID: <20090116222236.GH70788@bolthole.com> On Fri, Jan 16, 2009 at 10:13:13PM +0100, William Bonnet wrote: >.. > don't hesitate to submit your ideas for the agenda and discuss about > subjects. Sometimes it is easier to discuss about this by email rather > by editing wiki pages. definately. email can be good for discussion; wikis are good for condensing what was actually agreed to in the discussion From william at wbonnet.net Fri Jan 16 22:26:12 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 22:26:12 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090116222236.GH70788@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <20090116222236.GH70788@bolthole.com> Message-ID: <4970FB74.1030804@wbonnet.net> Hi Phil > definately. email can be good for discussion; > wikis are good for condensing what was actually agreed to in the discussion > We do share the same point of view. I'll initialize the wiki about this in the next days. It should be this week end. I wait until saturday night (CET) for comments, then i start to write a sum up. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Sat Jan 17 11:09:47 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 17 Jan 2009 11:09:47 +0100 Subject: [csw-maintainers] Mantis e-mail working? Message-ID: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> I recently filed this bug, http://www.opencsw.org/mantis/view.php?id=2981, but didn't get a notification via e-mail. Now I wonder if James got one? I have also noted before (via Dago's buglist) that I had bugs filed against my packages that I had not received a notification for and so didn't know about. -- /peter From james at opencsw.org Sat Jan 17 11:37:55 2009 From: james at opencsw.org (James Lee) Date: Sat, 17 Jan 2009 10:37:55 GMT Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> Message-ID: <20090117.10375500.3265564087@gyor.oxdrove.co.uk> On 17/01/09, 10:09:47, Peter Bonivart wrote regarding [csw-maintainers] Mantis e-mail working?: > I recently filed this bug, > http://www.opencsw.org/mantis/view.php?id=2981, but didn't get a > notification via e-mail. Now I wonder if James got one? Nothing received - hence my lack of action. (Sorry about the typo in the bug. I'll fix it.) James. From bonivart at opencsw.org Sat Jan 17 12:07:56 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 17 Jan 2009 12:07:56 +0100 Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <20090117.10375500.3265564087@gyor.oxdrove.co.uk> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> <20090117.10375500.3265564087@gyor.oxdrove.co.uk> Message-ID: <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> On Sat, Jan 17, 2009 at 11:37 AM, James Lee wrote: > Nothing received - hence my lack of action. > > (Sorry about the typo in the bug. I'll fix it.) Your bug is tiny, Mantis not sending notifications (again?) is a much larger issue. :-) -- /peter From james at opencsw.org Sat Jan 17 12:35:18 2009 From: james at opencsw.org (James Lee) Date: Sat, 17 Jan 2009 11:35:18 GMT Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> <20090117.10375500.3265564087@gyor.oxdrove.co.uk> <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> Message-ID: <20090117.11351800.2247806400@gyor.oxdrove.co.uk> On 17/01/09, 11:07:56, Peter Bonivart wrote regarding Re: [csw-maintainers] Mantis e-mail working?: > > (Sorry about the typo in the bug. I'll fix it.) > Your bug is tiny, Indeed, but unlike mantis it's within my power to fix and I have fixed it. > Mantis not sending notifications (again?) is a much > larger issue. :-) Indeed... From dam at opencsw.org Sun Jan 18 13:23:53 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 13:23:53 +0100 Subject: [csw-maintainers] New maintainer for Mantis installation Message-ID: Hi, Sebastian volunteered to maintain the Mantis installation, update it, tune it and make sure emails are sent properly. He already maintained other mantis installation in the past, so I have no doubt he does a great job. Ihsan, Phil: Please make sure he gets the proper access rights to do the job. Thanks! -- Dago From skayser at opencsw.org Sun Jan 18 13:48:43 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 13:48:43 +0100 Subject: [csw-maintainers] New maintainer for Mantis installation In-Reply-To: References: Message-ID: <4973252B.1080203@opencsw.org> Hi Dago, Dagobert Michelsen wrote: > Sebastian volunteered to maintain the Mantis installation, update it, > tune it and make sure emails are sent properly. He already maintained > other mantis installation in the past, so I have no doubt he does a > great job. just some small amendments: * Will do so, given that the people who took care of Mantis up to now, are ok with it. * Priority list (from my point of view): Make sure emails are sent out properly, update it, tune it. Has been about two years since i had a Mantis installation in my hands, so don't expect magical things to happen right away. Will have to dig into my documentation, distant memories, and the Mantis manual first. Sebastian From skayser at opencsw.org Sun Jan 18 14:15:20 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 14:15:20 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4970F869.7060601@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> Message-ID: <49732B68.4090105@opencsw.org> William Bonnet wrote: >> one of the biggest "challenges" about a volunteer >> organisation, is that you cant just write up a project agenda, and then >> assign people to do it. You need... volunteers! >> > That's right ! I fully agree > . > In order to recruit volunteers we first have to set up the project. As > you wrote below it comes through writing wiki page, and documentation > and many thing else. Gathering volunteers also requires to be > attractive. Being attractive often means to start the work on the > project and to communicate about this until you reach a kind of > "critical mass". It's not gonna be a easy thing, but i believe it is > worth to try :) > > It will help to create the buzz around, it will help focusing some > effort on mutual goal, and ... many things :) I like Williams ideas very much, especially the mutual goal part. Right now people are moving the project forward by producing bugfixed and updated packages. That's great, but not the whole story. Williams ideas try to capture all the other areas where work can be done to move the project forward. Given that these ideas are communicated, discussed, and packaged in doable "let's first do this and then move on to the next one" items, the right people can get together to make things happen in a joint effort. IMHO it's worth giving it a go. Sebastian From bonivart at opencsw.org Sun Jan 18 15:40:46 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 15:40:46 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49732B68.4090105@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> Message-ID: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> On Sun, Jan 18, 2009 at 2:15 PM, Sebastian Kayser wrote: > I like Williams ideas very much, especially the mutual goal part. Right > now people are moving the project forward by producing bugfixed and > updated packages. That's great, but not the whole story. Williams ideas > try to capture all the other areas where work can be done to move the > project forward. I also like William's ideas and you're right about us only updating packages now. However, I don't think this new theme idea captures "all" areas where we need improvement. There's fundamental things in the community that needs to open up if we're going to attract more people to join (or come back). It's my belief that those issues are avoided. There's only so much you can do with ten people. -- /peter From dam at opencsw.org Sun Jan 18 15:56:23 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 15:56:23 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49706F0E.2080004@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> Message-ID: Hi William, Am 16.01.2009 um 12:27 schrieb William Bonnet: > If we want to setup this thematics agenda, some people will have to > work > on advance on the process. Each coming theme will raise discussion > about > the process improvement (what is missing, out dated, which > documentation > is missing etc.). This will have certainly to be done during the month > before the theme (that's also why i propose to start by commnication, > there is no process prerequisite). > > Running a "thematic event" can go through simple steps like : > . week one we talk about what has to be done, > . week 2 and 3 people work on different task, according to their > free time, > . week 4 everyone work is integrated, commited, tested and published > > That's just a general process. It will have to be tuned to fit the > real > life and may chance according to the subjects I think that the thematics month proposal is a great and truly useful idea. You have my full support for taking the stake on these things. The order makes sense, removing libtools files can be done at the "removing bugs" month. Having the new website first would be good as the progress could be generally visible blogged on the front page. Do you think you can do that first? Best regards -- Dago From dam at opencsw.org Sun Jan 18 15:59:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 15:59:27 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: Hi Peter, Am 18.01.2009 um 15:40 schrieb Peter Bonivart: > I also like William's ideas and you're right about us only updating > packages now. However, I don't think this new theme idea captures > "all" areas where we need improvement. > > There's fundamental things in the community that needs to open up if > we're going to attract more people to join (or come back). It's my > belief that those issues are avoided. Are you talking about this or this? We already have addressed some of the points. If you have issues that you really want to have done please name them so we can try do resolve these fast-tracked if possible. Best regards -- Dago From bonivart at opencsw.org Sun Jan 18 16:15:35 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 16:15:35 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <625385e30901180715g65b23d34s2d6f871b533c46fd@mail.gmail.com> On Sun, Jan 18, 2009 at 3:59 PM, Dagobert Michelsen wrote: > Are you talking about this > > or this? > > > We already have addressed some of the points. If you have > issues that you really want to have done please name them > so we can try do resolve these fast-tracked if possible. If I could take a pick I would choose the Release Process and the Maintainers sections from the Suggestion-page on the wiki. Those are single point of failures today so to speak. -- /peter From phil at bolthole.com Sun Jan 18 17:47:18 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 08:47:18 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <20090118164717.GC81262@bolthole.com> On Sun, Jan 18, 2009 at 03:40:46PM +0100, Peter Bonivart wrote: > > There's fundamental things in the community that needs to open up if > we're going to attract more people to join (or come back). It's my > belief that those issues are avoided. Actually, we've been having new people join already. Two more are pending. The main thing holding up the new people, is just trying to put together a new "add new accounts" procedure between Ihsan, Dago, and myself. btw: to my recollection, at the meeting in switzerland, we looked briefly at every issue on the wiki flagged for discussion. Many of them were judged to be "handled already" From pfelecan at opencsw.org Sun Jan 18 20:23:11 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 18 Jan 2009 20:23:11 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: (Dagobert Michelsen's message of "Sun\, 18 Jan 2009 15\:59\:27 +0100") References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: Dagobert Michelsen writes: > Are you talking about this > > or this? > > > We already have addressed some of the points. If you have > issues that you really want to have done please name them > so we can try do resolve these fast-tracked if possible. Sorry to jump on this but, in my opinion, both referenced documents are of interest. If you addressed the issues why don't you publish an answer to each one, on the same page, this way we can see what's still undecided and can add to William topics; we can even discuss them here. my 7x10^13 cents -- Peter From phil at bolthole.com Sun Jan 18 20:48:10 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 11:48:10 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <20090118194810.GE81262@bolthole.com> On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: > If you addressed the issues why don't you publish an answer to each > one, on the same page, this way we can see what's still undecided and > can add to William topics; we can even discuss them here. > I'll let the secretary do that ;-) From dam at opencsw.org Sun Jan 18 21:17:29 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 21:17:29 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118194810.GE81262@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> Message-ID: Fellow maintainers, Am 18.01.2009 um 20:48 schrieb Philip Brown: > On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: >> If you addressed the issues why don't you publish an answer to each >> one, on the same page, this way we can see what's still undecided and >> can add to William topics; we can even discuss them here. Good point Peter. > I'll let the secretary do that ;-) I'll take care of that. Best regards -- Dago From dam at opencsw.org Sun Jan 18 21:19:35 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 21:19:35 +0100 Subject: [csw-maintainers] Perl module handling changed in mGAR v2 Message-ID: Hi, with r2853 the handling of files in Perl modules (category "cpan") has changed. Now the files .*/perllocal\.pod .*/\.packlist are excluded by default during merge in mGAR v2. The behaviour in mGAR v1 is unchanged as there is no merge-phase. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 21:32:37 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 21:32:37 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118164717.GC81262@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> Message-ID: <497391E5.1070700@opencsw.org> Philip Brown wrote: > On Sun, Jan 18, 2009 at 03:40:46PM +0100, Peter Bonivart wrote: >> There's fundamental things in the community that needs to open up if >> we're going to attract more people to join (or come back). It's my >> belief that those issues are avoided. > > Actually, we've been having new people join already. Two more are pending. > The main thing holding up the new people, is just trying to put together a > new "add new accounts" procedure between Ihsan, Dago, and myself. > > btw: to my recollection, at the meeting in switzerland, we looked briefly > at every issue on the wiki flagged for discussion. Many of them were judged > to be "handled already" I recall the same. A few was "handled already", other where "almost done" (like lots of the GAR stuff). Some of the matters are internal stuff (like the exact details of the release process), but most of them are public and should probably be moved to William's page (with a status note if applicable). -- Trygve From bonivart at opencsw.org Sun Jan 18 22:07:19 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 22:07:19 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497391E5.1070700@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> Message-ID: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: > I recall the same. A few was "handled already", other where "almost > done" (like lots of the GAR stuff). Some of the matters are internal > stuff (like the exact details of the release process), but most of them > are public and should probably be moved to William's page (with a status > note if applicable). The technical stuff is not the problem, I'm not worried about that. What worries me, even more after your post, is that there seems to be some unexplainable need for secrecy. Why does the release process need to be handled internally? And what does that mean? The board? Are you involved? Why aren't the rest of us worthy of knowing what goes on? I hear that it's being handled but I simply don't believe it until I see it. -- /peter From dam at opencsw.org Sun Jan 18 22:34:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 22:34:27 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <1DB4522F-B6DD-44D3-8DF1-1D50315ED5A0@opencsw.org> Hi Peter, Am 18.01.2009 um 22:07 schrieb Peter Bonivart: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l > wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of >> them >> are public and should probably be moved to William's page (with a >> status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? There is no need for it to be handled internally. Explanations are given in www.opencsw.org:/home/newpkgs/README in addition to individual emails to the maintainers. I'll write all that up during the week. > And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? Well, I of course feel myself well informed. We could enhance the process with email-pings to maintainers@ or anything else that makes it more visible any time if the members feel that this is needed. That it is not done is not rooted in that we don't want it - it is not that easy to just post the right amount of data. If you feel the need please post, kick the board, kick me, kick Ihsan, kick Phil. It's our obligation to do this decently. But making everyone happy is not an easy task ;-) > I hear that it's being handled but I simply don't believe it until I > see it. Ok. Point taken. Please: Kick again if this is not implemented with your full satisfaction. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 22:34:38 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 22:34:38 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <4973A06E.6040906@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of them >> are public and should probably be moved to William's page (with a status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? Come one, there is no secrecy. I meant internally as on the maintainers@ list, not publicly on devel at . > I hear that it's being handled but I simply don't believe it until I see it. I'm not sure of any specific stuff going on with the release process, but if you have specific issues that need to be handled please note those down on the page that you've already started. From what I can tell the major point WRT to the release process is getting every rule written down or put into code as a part of chkpkg. -- Trygve From phil at bolthole.com Sun Jan 18 22:56:02 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 13:56:02 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A06E.6040906@opencsw.org> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> Message-ID: <20090118215602.GB56431@bolthole.com> On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: > From what I can tell the major point WRT to the release process is > getting every rule written down or put into code as a part of chkpkg. And that is intrinsically impossible. It is impossible to write down EVERYTHING, just as it is impossible to write a computer program to automatically write any new computer program you want. It's impossible to code checkpkg to cover "everything". It's a little easier to write down descriptions of what things not covered by checkpkg should look like. But there will always be exceptoins. At some point, there always comes a need for a human being to make a decision of "yes this is acceptible/no this is not". Peter seems to want to completely eliminate any human inspection of packages. I say that this is not possible. Given that I have been inspecting packages for 6 years now, I hope that the majority of people will trust my experience on this. I'll agree there is some room for improvement, though. m From dam at opencsw.org Sun Jan 18 22:59:25 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 22:59:25 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> Hi, Am 18.01.2009 um 22:56 schrieb Philip Brown: > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: >> From what I can tell the major point WRT to the release process is >> getting every rule written down or put into code as a part of chkpkg. > > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will > trust > my experience on this. That's why Trygve said "written down" *or* "put into code" :-) The rules just shouldn't be arbitrary. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 22:59:53 2009 From: trygvis at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Sun, 18 Jan 2009 22:59:53 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <4973A659.8060506@opencsw.org> Philip Brown wrote: > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: >> From what I can tell the major point WRT to the release process is >> getting every rule written down or put into code as a part of chkpkg. > > And that is intrinsically impossible. It is impossible to write down > EVERYTHING, just as it is impossible to write a computer program to > automatically write any new computer program you want. > It's impossible to code checkpkg to cover "everything". > It's a little easier to write down descriptions of what > things not covered by checkpkg should look like. But there will always > be exceptoins. > At some point, there always comes a need for a human being to make a > decision of "yes this is acceptible/no this is not". > Peter seems to want to completely eliminate any human inspection of > packages. Peter's point is that he want more than one person to decide. > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will trust > my experience on this. > > I'll agree there is some room for improvement, though. Continuous improvement is important and all I'm asking for. In particular for a volunteer-based project like OpenCSW it is important to keep the changes small so that they can be realized, but at the same time never stop to improve and become better. -- Trygve From phil at bolthole.com Sun Jan 18 23:03:53 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 14:03:53 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> Message-ID: <20090118220353.GE56431@bolthole.com> On Sun, Jan 18, 2009 at 10:59:25PM +0100, Dagobert Michelsen wrote: > Hi, > > Am 18.01.2009 um 22:56 schrieb Philip Brown: > > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: > >> From what I can tell the major point WRT to the release process is > >> getting every rule written down or put into code as a part of chkpkg. > > > > I say that this is not possible. Given that I have been inspecting > > packages for 6 years now, I hope that the majority of people will > > trust > > my experience on this. > > That's why Trygve said "written down" *or* "put into code" :-) > The rules just shouldn't be arbitrary. you trimmed too much :-) I tried to convey that we can reasonably cover, lets say, 80% of cases through checkpkg, and 95% of cases via "written down", but there's always going to be a grey area left. Either that, or our "standards documentation" will become so ludicrously large, that it will become effectively USELESS. There *is* such a thing as "too much information", sometimes :-} Once a doc reaches a certain size, people stop reading it entirely. It's at that point already for some people. From bonivart at opencsw.org Sun Jan 18 23:03:32 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:03:32 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A06E.6040906@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> Message-ID: <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> On Sun, Jan 18, 2009 at 10:34 PM, Trygve Laugst?l wrote: > Come one, there is no secrecy. Yes, there is. I don't know how the release process works (from submission to hitting the mirrors) or how maintainers are selected. I would like to have full disclosure on that, only then can we have input from the community on how to improve stuff. If we don't invite the community to take part we can't expect the community to grow. -- /peter From bonivart at opencsw.org Sun Jan 18 23:12:17 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:12:17 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <625385e30901181412g8ff433fo99de7557cd46e31a@mail.gmail.com> On Sun, Jan 18, 2009 at 10:56 PM, Philip Brown wrote: > Peter seems to want to completely eliminate any human inspection of > packages. You don't have to guess (wrongly) what I want. I have written it down here: http://wiki.opencsw.org/suggestions > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will trust > my experience on this. Computers are not good at handling new problems but they don't let old ones slip by. > I'll agree there is some room for improvement, though. Yes, there is but what are you going to do about but keep stalling? Disclosing the process and inviting more people to check packages would be a good start. I'm sure we would get a lot more ideas from there. -- /peter From phil at bolthole.com Sun Jan 18 23:14:28 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 14:14:28 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A659.8060506@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> Message-ID: <20090118221428.GF56431@bolthole.com> On Sun, Jan 18, 2009 at 10:59:53PM +0100, Trygve Laugst??l wrote: > > Peter's point is that he want more than one person to decide. Decide what? More than one person to decide what actually gets written down as standards? More than one person, in case the primary person is on vacation or ill? Or to play a game of "well, mom said I cant, so I'll go ask dad instead"? I dont think that playing games like that is beneficial to the quality of CSW packages. But that seems to be what Peter is aiming for, since the other cases are Already Handled. In my opinion, it would be a bad thing, to have one set of packages that are put into "current" via one person, that have strict consistency to them, and then have another set of packages, allowed to go into current by a different person, that did not have consistency to them. That is my opinion. Now that we have a whole definition of "membership" in the "OpenCSW association", perhaps we can have a format vote to see how many people share my opinion, and settle this issue. From skayser at opencsw.org Sun Jan 18 23:18:54 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 23:18:54 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <4973AACE.3080309@opencsw.org> Hi Peter, Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of them >> are public and should probably be moved to William's page (with a status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? good that you bring the secrecy concern up. It might be of concern to others as well. Maybe more detailed communication about how exactly the meeting was taking place and what all of us took away from it could have been helpful to avoid that assumption. So here we go, from my humble point of view: First of all, there is no hidden agenda, no secrecy, no Pinky and Brain world domination theories, no nothing. Maybe Othmar could jump in, who as a then-OpenCSW-user attended the meeting and volunteered to take the "protocol" during the meeting. It should have been pretty obvious from his point of view (as a bystander), what was going on. Take about 10 engineers, throw them into a room and let them talk about organizational stuff like the bylaws and you will realize very soon, that it will take a lot of (partly painful) time to figure out things. Put on top that people are all very excited about how to improve certain aspects of the project and you will find yourself in very interesting discussions, with _lots_ of different aspects. However, it's not until close to the end of the day and heaps of cups of coffee later that you realize that on the one hand the bylaws are finalized (*whopee*), but a lot of other things could have used a more stringent dealing with and you wish you had Sunday to talk everything over again. > I hear that it's being handled but I simply don't believe it until I see it. So when others say that they remember your suggestions being handled during the Saturday i think it is because some of them were touched, but less in a "now take two hours to deal with Peter's suggestions" way than in a "part of the whole discussion" way. This goes for most of the technical stuff also by the way. When Alexander Maier and i went to the meeting, one of the major reasons was to hear the technical GAR session from Dago. We didn't even get as far as that (and GAR had been scheduled for 14:00). Needless to say that tangible results besides the written bylaws were blurred in the fuss of all that has been discussed. At least from my point of view. Someone correct me please in case they feel otherwise. Still it was very nice to meet the other people and to realize that maybe next time a better organized and less packed schedule, attendees with less exhaustion from traveling, and maybe a moderator could be useful. :) With William setting up thematic months and the activeness we have on the maintainers list right now i think it should not be a problem to bring up certain points up again (especially any concerns about secrecy), get them discussed and formalized in a way. Sebastian From trygvis at opencsw.org Sun Jan 18 23:36:23 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 23:36:23 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> Message-ID: <4973AEE7.1020905@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 10:34 PM, Trygve Laugst?l wrote: >> Come one, there is no secrecy. > > Yes, there is. I don't know how the release process works (from > submission to hitting the mirrors) or how maintainers are selected. I > would like to have full disclosure on that, only then can we have > input from the community on how to improve stuff. If we don't invite > the community to take part we can't expect the community to grow. Thanks for getting very specific! Phil: would you mind noting down an overview of how the process is? If it already is noted down, I'm sure Peter can point out what he feel that is missing and then those points can be fixed. Dagobert: could you publish the notes on the site describing the rules and requirements for membership? That would be very useful for newcomers to know -- Trygve From bonivart at opencsw.org Sun Jan 18 23:39:39 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:39:39 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118221428.GF56431@bolthole.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> Message-ID: <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> On Sun, Jan 18, 2009 at 11:14 PM, Philip Brown wrote: > I dont think that playing games like that is beneficial to the quality of > CSW packages. But that seems to be what Peter is aiming for, since the > other cases are Already Handled. I wouldn't call disclosing the process and sharing the load playing games but it's nice to hear your view of it. > In my opinion, it would be a bad thing, to have one set of packages that > are put into "current" via one person, that have strict consistency to them, > and then have another set of packages, allowed to go into current > by a different person, that did not have consistency to them. There's really no defence to your single of point of failure strategy. You're just getting desperate and now you're insulting anyone wanting to help even before they get a chance. Do you really think that no one can do what you do? Blastwave does fine without your help, I have made an alternative to pkg-get and Dago basically does what you when it comes to the current versus testing repos. You're defending your position with secrecy and discrediting. > That is my opinion. Now that we have a whole definition of "membership" > in the "OpenCSW association", perhaps we can have a format vote to > see how many people share my opinion, and settle this issue. Sysadmins tend to go for redundancy and load balancing when given a choice. Let's hope most of us are sysadmins and not pointy-haired-bosses. -- /peter From skayser at opencsw.org Mon Jan 19 00:42:17 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 19 Jan 2009 00:42:17 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> Message-ID: <4973BE59.6040102@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 11:14 PM, Philip Brown wrote: >> I dont think that playing games like that is beneficial to the quality of >> CSW packages. But that seems to be what Peter is aiming for, since the >> other cases are Already Handled. > > I wouldn't call disclosing the process and sharing the load playing > games but it's nice to hear your view of it. > >> In my opinion, it would be a bad thing, to have one set of packages that >> are put into "current" via one person, that have strict consistency to them, >> and then have another set of packages, allowed to go into current >> by a different person, that did not have consistency to them. > > There's really no defence to your single of point of failure strategy. > You're just getting desperate and now you're insulting anyone wanting > to help even before they get a chance. Do you really think that no one > can do what you do? Blastwave does fine without your help, I have made > an alternative to pkg-get and Dago basically does what you when it > comes to the current versus testing repos. You're defending your > position with secrecy and discrediting. Just some questions, because i have never been in the position and i would like to understand the discussion: Has the release process with Phil as the single point of getting packages into current shown a major bottleneck so far? Or is it the manual nature (effort on the maintainers side) of the release process? Did packages get rejected out of uncertain or non-understandable reasons? Do we have a truck factor issue with Phil as the only path to current at the moment? What's the exact pain that is trying to be cured? Sebastian From phil at bolthole.com Mon Jan 19 00:52:07 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 15:52:07 -0800 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: <4973AEE7.1020905@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> Message-ID: <20090118235207.GA79582@bolthole.com> On Sun, Jan 18, 2009 at 11:36:23PM +0100, Trygve Laugst?l wrote: > ... > Phil: would you mind noting down an overview of how the process is? If > it already is noted down, I'm sure Peter can point out what he feel that > is missing and then those points can be fixed. Reguarding the release process: there's really very little to it that isnt already documented. Here's a description for you right now. again. I seem to recall I wrote this up for the maintainers list, but it's easier for me to write it here again than seach for it. But I'll change the subject line so it's easier to search in the future. Once a package is put in newpkgs by the maintainer, I look it over to see if there's any "gotchas" to it, and run checkpkg on it. If everything looks good, then I run a silly little "registerpkg" script to add it to a trivial mysql table. I also add an area to mantis for it if there isnt one already. This script is sitting easily accessible to Ihsan in my home directory on www.opencsw.org Beyond that, I run a catalog update script and sign it. Peter is already INTIMATELY familiar with this step, since he decided to write his own utility to do exactly the same thing for blastwave. Then, its a simple matter of "rsync to our master site, and we're done". ...... There's no "big hidden mystery". Its all pretty obvious. As I noted above, Peter is already very familar with one of the more complicated bits, since he replicated it himself for blastwave, after the split!! So his big complaints about "I dont understand what's going on" seem rather disengenuous to me. Peter wrote in his own email, > There's really no defence to your single of point of failure strategy. There is no single point of failure through me; this has been addressed already. If I got run over by a bus tomorrow, opencsw could continue to release packages, without any noticable impact to users. No need to change keys, everything would look the same to them: James has the signing key; Ihsan and Dago have access to the databases, and the "registerpkg" script, which is just sitting there in my directory on www. Peter knows this already. It seems like this fuss is really all about him not liking to get MY approval for HIS packages, and he wants to go through someone else, or better yet, not have to go through anyone to double-check his work. He keeps claiming it's about "single point of failure", but as I have pointed out, on here, and at the in-person meeting, That Has Been Handled Already. And everyone at the meeting agreed, so we moved on. Doesnt that match your recollection, Trygve? From bonivart at opencsw.org Mon Jan 19 01:11:55 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 19 Jan 2009 01:11:55 +0100 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: <20090118235207.GA79582@bolthole.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> Message-ID: <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> On Mon, Jan 19, 2009 at 12:52 AM, Philip Brown wrote: > Beyond that, I run a catalog update script and sign it. > Peter is already INTIMATELY familiar with this step, since he decided to > write his own utility to do exactly the same thing for blastwave. That's just not true. I wrote a simple catalog building script which everyone can use. Dennis tried it but I have no idea if he's going to use it regularly or not, he hasn't so far. It has nothing to do with signing and creating mirror content. Dennis was doing fine before I did my script which was meant for local users. > Peter knows this already. It seems like this fuss is really all about > him not liking to get MY approval for HIS packages, and he wants to go > through someone else, or better yet, not have to go through anyone > to double-check his work. Actually I didn't know most of that already but thanks for sharing it. Maybe you would be so kind as to write it on the wiki or on the main site? What I have suggested, not that you seem to care what I actually say when replying, is that I want a group of people handling the release process. We shouldn't e-mail your personal address and be kept in the dark until you decide to reply. What you have against a web app for tracking the testing/release process baffles me. We could create a ticket there, mark our testing already done, others can check in their testing of the package, the release group can assign the packet to one of them and the rest will know that. Not only will maintainers know better what is and is not happening with their packages, I think it will encourage testing as well. -- /peter From Murray.Jensen at csiro.au Mon Jan 19 12:36:51 2009 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Mon, 19 Jan 2009 22:36:51 +1100 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: Your message of "Mon, 19 Jan 2009 11:11:55 +1100" <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> Message-ID: <25061.1232365011@gerd> On Mon, 19 Jan 2009 11:11:55 +1100, Peter Bonivart writes: >What I have suggested, not that you seem to care what I actually say >when replying, is that I want a group of people handling the release >process. We shouldn't e-mail your personal address and be kept in the >dark until you decide to reply. > >What you have against a web app for tracking the testing/release >process baffles me. We could create a ticket there, mark our testing >already done, others can check in their testing of the package, the >release group can assign the packet to one of them and the rest will >know that. Not only will maintainers know better what is and is not >happening with their packages, I think it will encourage testing as >well. While I am uncomfortable with the antagonistic way that Peter expresses himself towards you all the time Phil, this approach seems reasonable to me. I have a vague recollection of suggesting something similar myself in the past during the "split". I don't see it as a burning issue though, just something that should be worked towards. We should at least talk about it, and maybe see if anyone can put the time in to develop this "web app". Shouldn't be too difficult with modern technology :-) Cheers! Murray... From glaw at opencsw.org Tue Jan 20 00:32:08 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 19 Jan 2009 23:32:08 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <4973BE59.6040102@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: Dago wrote: > There is no need for it to be handled internally. > Explanations are given in www.opencsw.org:/home/newpkgs/README Not sure what you mean there, but http://opencsw.org/home/newpkgs/READMEdoesn't exist, nor does [/export]/home/newpkgs/README on login.bo.opencsw.org. Trygve wrote: > From what I can tell the major point WRT to the release process is getting > every rule written down or put into code as a part of chkpkg. +1 Peter wrote: > It's impossible to code checkpkg to cover "everything". This is not an argument against automated testing. Well, it is actually an /argument/ against automated testing, but a really bad one. The whole world of software development these days seems to have accepted that automated testing is good, and should be used to the maximum extent possible. We should try and code tests for every possible reason to reject a package (and document this too). >But there will always be exceptoins. > At some point, there always comes a need for a human being to make a decision > of "yes this is acceptible/no this is not". I disagree. If something passes all the testing, why not release it? The project board might want to retain a long-stop power to pull software that was defective in some previously unheard of, and therefore untested for, way. Other than that maintainers should be able to say "this is good to go", provided it meets the published standard. Personally, I would also restrict this to automated builds that run off a gar or similar system, so hudson (or similar) does the build on the basis of a published make/spec file, and the testing/approval is fully automated. > Peter seems to want to completely eliminate any human inspection of packages. There is an interesting parallel with a discussion at my workplace just this week. Some admins want to retain manual builds for much of the software stack. I want to see everything that can be automated. The tools are there, and I feel the benefits are clear. It seems OpenCSW is now having the same conversation. > I say that this is not possible. It is definitely possible. Do the benefits outweigh the disadvantages? I'd say yes. Peter then wrote: > I tried to convey that we can reasonably cover, lets say, 80% of cases through > checkpkg, and 95% of cases via "written down", but there's always going to be > a grey area left. Either that, or our "standards documentation" will become so > ludicrously large, that it will become effectively USELESS Reasons for rejecting packages need to be documented and agreed upon, not subject to arbitary decisions. If the documentation gets too large... let's cross that bridge then. I don't see excessive documentation weighing down MacPorts or Fedora Packages or whatever. The "grey area" is just the exercise of individual discretion, and we should be looking to eliminate that from the quality control process. Peter wrote some more: > Decide what? > More than one person to decide what actually gets written down as standards? > More than one person, in case the primary person is on vacation or ill? > Or to play a game of "well, mom said I cant, so I'll go ask dad instead"? The standards should be agreed on by the board at the minimum, maybe the whole membership should vote on it. > In my opinion, it would be a bad thing, to have one set of packages that > are put into "current" via one person, that have strict consistency to them, > and then have another set of packages, allowed to go into current > by a different person, that did not have consistency to them. Of course, we should strive for consistency. However, in my country, there are many judges, juries and magistrates called upon to make legal judgements in different courts every day. They strive to be consistent with one another (we have Common Law system here). They may not actually be 100% consistent but that is the aim. No one suggests that in order to maintain perfect consistency we can only have one judge. Sebastian wrote: > Has the release process with Phil as the single point of getting packages > into current shown a major bottleneck so far? Well, depends what you call 'major'. Certainly a bottleneck. > Or is it the manual nature (effort on the maintainers side) of the release > process? I don't like a manual process either. I like automation. I want to SVN check in a fresh file to GAR, and do basically nothing else if there are no problems... build it, test it, release to testing, wait, release to newpkgs, maybe email me and some others a status update as it moves through the system... > Did packages get rejected out of uncertain or non-understandable reasons? Yes > Do we have a truck factor issue with Phil as the only path to current at the moment? We call it the 'hit by a bus' factor here, and yes. Again, personally, I don't think packages should have a single mainainer either, it should be minimum two. For release gatekeepers/GPG keyholders, I'd like half a dozen. Just my 2p... Gary -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Tue Jan 20 09:25:48 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 20 Jan 2009 09:25:48 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090116144804.GB2576@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> On Tue, Jan 20, 2009 at 12:32 AM, Gary Law wrote: > Peter wrote: > Peter then wrote: > Peter wrote some more: Phil wrote all those quotes, not me. :-) Besides that... +1 To me it comes down to basic technical design, you always go for load balancing and redundancy if you can. One recent example is Dago administering the build farm just as well as Phil releases packages, still there were requests for adding people to that process. Dago, being a reasonable man, agreed and now we have more build farm admins. Why is this different? -- /peter From glaw at opencsw.org Tue Jan 20 10:54:59 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 09:54:59 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> References: <20090116144804.GB2576@bolthole.com> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> Message-ID: 2009/1/20 Peter Bonivart > On Tue, Jan 20, 2009 at 12:32 AM, Gary Law wrote: > > Peter wrote: > > Peter then wrote: > > Peter wrote some more: > > Phil wrote all those quotes, not me. :-) > > Besides that... +1 > Err, yes, i was trying to summarise lots of points in a long thread and lost the plot there. Sorry Phil, sorry Peter. -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Tue Jan 20 18:05:49 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 09:05:49 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: <20090120170549.GB54457@bolthole.com> On Mon, Jan 19, 2009 at 11:32:08PM +0000, Gary Law wrote: > Dago wrote: > > There is no need for it to be handled internally. > > Explanations are given in www.opencsw.org:/home/newpkgs/README > > Not sure what you mean there, but http://opencsw.org/home/newpkgs/README > doesn't exist The initial reference is a file reference, scp style, not a URL > ..., nor does [/export]/home/newpkgs/README on > login.bo.opencsw.org. /home/newpkgs should not exist on login.bo.opencsw.org in the first place. It's only supposed to exist on www.opencsw.org > > It's impossible to code checkpkg to cover "everything". > > This is not an argument against automated testing. Well, it is actually an > /argument/ against automated testing, but a really bad one. no, it isnt an argument against automated testing. It's saying what it is saying. no more, no less. And it is reinforced by what you quoted from me, lower down: >> I tried to convey that we can reasonably cover, lets say, 80% of cases >> through checkpkg, and 95% of cases via "written down", but there's always > going to be a grey area left. that is to say, automated testing is nice, but it cannot cover everything that needs to be covered. >>But there will always be exceptoins. >> At some point, there always comes a need for a human being to make a >> decision of "yes this is acceptible/no this is not". > > I disagree. If something passes all the testing, why not release it? What is your basis for disagreement? convenience on your part? I will tell you what my basis for disagreeing with your statement right there: checkpkg was a lot simpler 4 years ago, and so were the written standards. Lets say that we had gone with your exact premise 4 years ago. We would not have gotten the improvements! The primary way they have improved, is because I took the time to personally take a glance at the packages, and sometimes noticed things that werent being caught. Then checkpkg, and/or the standards, got improved, when appropriate. There is a similar process in general AUTOMATED manufacturing of goods. Things are for the most part, fully automated. Yet there are still QA checks *by a human*, to see if any defects are slipping through still. > There is an interesting parallel with a discussion at my workplace just > this week. Some admins want to retain manual builds for much of the > software stack. I want to see everything that can be automated. This is a different case. You may feel it is the same, because there is an issue of "manual vs automated". But there are different core issues at stake. This is a matter of QA process, not build process. From glaw at opencsw.org Tue Jan 20 23:23:33 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 22:23:33 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090120170549.GB54457@bolthole.com> References: <20090118164717.GC81262@bolthole.com> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> Message-ID: 2009/1/20 Philip Brown > On Mon, Jan 19, 2009 at 11:32:08PM +0000, Gary Law wrote: > > Dago wrote: > > > There is no need for it to be handled internally. > > > Explanations are given in www.opencsw.org:/home/newpkgs/README > > > > Not sure what you mean there, but > http://opencsw.org/home/newpkgs/README > > doesn't exist > > The initial reference is a file reference, scp style, not a URL > > > > ..., nor does [/export]/home/newpkgs/README on > > login.bo.opencsw.org. > > /home/newpkgs should not exist on login.bo.opencsw.org in the first place. > It's only supposed to exist on www.opencsw.org OK, I have to say it hadn't occurred to me that I could ssh in... but I can! However, as far as I can tell the file isn't there: $ scp www.opencsw.org:/home/newpkgs/README . scp: /home/newpkgs/README: No such file or directory > > > It's impossible to code checkpkg to cover "everything". > > > > This is not an argument against automated testing. Well, it is > actually an > > /argument/ against automated testing, but a really bad one. > > no, it isnt an argument against automated testing. It's saying what it is > saying. no more, no less. And it is reinforced by what you quoted from me, > lower down: > > >> I tried to convey that we can reasonably cover, lets say, 80% of cases > >> through checkpkg, and 95% of cases via "written down", but there's > always > > going to be a grey area left. > > that is to say, automated testing is nice, but it cannot cover everything > that needs to be covered. Perhaps I'd have a better idea if you could explain what needs to be covered that's not automatable? > >>But there will always be exceptoins. > >> At some point, there always comes a need for a human being to make a > >> decision of "yes this is acceptible/no this is not". > > > > I disagree. If something passes all the testing, why not release it? > > What is your basis for disagreement? convenience on your part? convenience? perhaps a little, there's nothing wrong with that. But much more importantly consistency and transparency. > I will tell you what my basis for disagreeing with your statement right > there: > checkpkg was a lot simpler 4 years ago, and so were the written standards. > Lets say that we had gone with your exact premise 4 years ago. > We would not have gotten the improvements! > > The primary way they have improved, is because I took the time to > personally take a glance at the packages, and sometimes noticed things that > werent being caught. > Then checkpkg, and/or the standards, got improved, when > appropriate. > > There is a similar process in general AUTOMATED manufacturing of goods. > Things are for the most part, fully automated. Yet there are still QA > checks *by a human*, to see if any defects are slipping through still. > what we do is much more analogous to software development than manufacturing. And in software development automating QA is at the heart of most processes that seek to be support frequent, consistent, high quality releases. Manual QA is seen as a necessary evil for those things that haven't /yet/ been automated. We still need human beings -- users and maintainers -- to feed back problems that aren't caught in the automated tests, so we can improve them. > > There is an interesting parallel with a discussion at my workplace > just > > this week. Some admins want to retain manual builds for much of the > > software stack. I want to see everything that can be automated. > > This is a different case. You may feel it is the same, because there is an > issue of "manual vs automated". But there are different core issues at > stake. > > This is a matter of QA process, not build process. > Yes. But at the moment both build and QA are very manual, I'd like to see them be automated. You don't address the points concerning only having one gatekeeper on releases or on the use of individual discretion in this reply. I hope this means you're having second thoughts. Regards Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Tue Jan 20 23:37:24 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 14:37:24 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> Message-ID: <20090120223724.GF54457@bolthole.com> On Tue, Jan 20, 2009 at 10:23:33PM +0000, Gary Law wrote: > OK, I have to say it hadn't occurred to me that I could ssh in... but I > can! However, as far as I can tell the file isn't there: > $ scp www.opencsw.org:/home/newpkgs/README . > scp: /home/newpkgs/README: No such file or directory The original emailer, who wasnt me AFAIK, mistyped. If you actually log in and look in that directory, you will see that the actual file name is 00-README or something like that. Bottom line is, though, most people wont care about the file anyway. They will probably email me "why isnt my package released yet", and then *I* will go look at the file, to remind myself and them, the reasons why their package is still sitting in newpkgs. I put the reminder file there (instead of my home dir) , as an effort to be transparent to everyone about what is going on with things. Go read it, if you're curious. > that is to say, automated testing is nice, but it cannot cover > everything that needs to be covered. > > Perhaps I'd have a better idea if you could explain what needs to be > covered that's not automatable? Are you familiar with "the halting problem" in software design? Some things are fundamentally not solvable by fully automated methods. This is one of them. If i could explain "everything that needs to be covered" before ever seeing it, then not only would i be capable of designing a perfect AI, but i would also be clairvoyant. In which case, i'd be playing the stock market, and relaxing on a beach in the Bahamas instead of doing this :-) > You don't address the points concerning only having one gatekeeper on > releases or on the use of individual discretion in this reply. You havent given specifics why it is a bad thing. You have basically stated "it is bad", without saying what is actually bad about it. In constrast, I have given explicit reasons why it is a GOOD thing (consistency), and I have also given specific reasons why the "phil gets run over by a bus" claim to be concerned, is invalid. It has already been handled. Let's not waste people's time rehashing things that have already been solved, please? From glaw at opencsw.org Wed Jan 21 00:58:35 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 23:58:35 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090120223724.GF54457@bolthole.com> References: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> Message-ID: 2009/1/20 Philip Brown > On Tue, Jan 20, 2009 at 10:23:33PM +0000, Gary Law wrote: > > OK, I have to say it hadn't occurred to me that I could ssh in... but > I > > can! However, as far as I can tell the file isn't there: > > $ scp www.opencsw.org:/home/newpkgs/README . > > scp: /home/newpkgs/README: No such file or directory > > The original emailer, who wasnt me AFAIK, mistyped. If you actually log in > and > look in that directory, you will see that the actual file name is > 00-README or something like that. Indeed, that's it. > Bottom line is, though, most people wont care about the file anyway. They > will probably email me "why isnt my package released yet", and then *I* > will go look at the file, to remind myself and them, the reasons why their > package is still sitting in newpkgs. I put the reminder file there > (instead of my home dir) , as an effort to be transparent to everyone about > what is going on with things. Go read it, if you're curious. Thanks. That is a pointer to how things work. It is also a clear indication of how much of this process is currently handled by one person. > > that is to say, automated testing is nice, but it cannot cover > > everything that needs to be covered. > > > > Perhaps I'd have a better idea if you could explain what needs to be > > covered that's not automatable? > > Are you familiar with "the halting problem" in software design? Err, I wasn't aware that checkpkg was actually trying to solve that problem. > Some things are fundamentally not solvable by fully automated methods. > This is one of them. *What* is one of them? What are these nebulous criteria that cannot be tested in an automated fashion -- or indeed in a consistent way by anyone other than you personally -- but packages must comply with before release? > If i could explain "everything that needs to be covered" before ever seeing > it, then not only would i be capable of designing a perfect AI, but i would > also be clairvoyant. In which case, i'd be playing the stock market, and > relaxing on a beach in the Bahamas instead of doing this :-) Legislators face this problem every day. So do company managers. So so software designers. You make rules based on what you know, and what you anticipate. You don't expect it to be perfect, do you aim for 'good enough'. You accept that future revisions might require better rules/tests. That 'good enough' standard will be different if writing software for a content only website, or a bank teller system, or a fly-by-wire aircraft control system. I'm not asking you to explain everything you might find wrong in packages that don't yet exist; but I am suggesting we need to dispassionately look at proposed releases, against published criteria, and ideally automate the enforcement of the standard by failing to release things that fail a test. (I'm also not of the view that submission to one human being for arbitrary rubber stamp based on unpublished criteria should be the key determinant of the release process). > > You don't address the points concerning only having one gatekeeper on > > releases or on the use of individual discretion in this reply. > > You havent given specifics why it is a bad thing. You have basically > stated "it is bad", without saying what is actually bad about it. > In constrast, I have given explicit reasons why it is a GOOD thing > (consistency), and I have also given specific reasons why the > "phil gets run over by a bus" claim to be concerned, is invalid. > It has already been handled. Consistency is much more likely to be provided by automated tests, and well understood and broadly agreed standards. One person signing things off is more fallible IMHO. Even if you manage to be perfectly consistent with yourself this is not a scalable, or transparent, or open way of doing this. It does not encourage community participation. It's not a process I can explain to a potential new maintainer. It's also not consistent when you're not around for any reason, as the process just stops, which isn't consistent either. My last employer had a Change Advisory Board to decide on software releases. We tried to keep membership consistent from meeting to meeting, to maintain consistent decision making, but this never entirely possible. And it didn't matter much. The fact is good (automated) QA and agreed, published standards were more useful in the long term to raising standards in software than trying to keep the same bunch of people in a room, week in, week out. Companies signing off software with the potential to cost/make millions of $CURRENCY can do so on the basis of a inconsistent process like a CAB -- so why can't a volunteer effort release a couple of Solaris packages? > Let's not waste people's time rehashing things that have already been > solved, please? > This isn't rehashing, it's the first time I've seen it properly discussed since OpenCSW was formed, and, from where I'm standing, this is so /not/ solved. I think you suggested putting it to a vote... something I'll be entirely in favour of as soon as my membership application is approved..... :) Gary -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Wed Jan 21 02:21:09 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 17:21:09 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> Message-ID: <20090121012109.GA48238@bolthole.com> On Tue, Jan 20, 2009 at 11:58:35PM +0000, Gary Law wrote: > Let's not waste people's time rehashing things that have already been > solved, please? > > This isn't rehashing, it's the first time I've seen it properly discussed > since OpenCSW was formed, and, from where I'm standing, this is so /not/ > solved. > ... You are mixing "it"s by unfairly distancing what I wrote there, from what was directly before it. What was directly before it, was mention of the fallacious "what if phil got run over by a bus" argument. Which has been solved. You did not acknowlege that. That's all I have to say for now. From phil at bolthole.com Wed Jan 21 02:50:54 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 17:50:54 -0800 Subject: [csw-maintainers] testing team for packages In-Reply-To: <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> Message-ID: <20090121015054.GA61849@bolthole.com> On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: >... > Not only will maintainers know better what is and is not > happening with their packages, I think it will encourage testing as > well. a side note: maintainers already tend to "know what is happening" with their packages already. Often within a few hours; usually within a day. As far as testing goes: Across-the-board testing doesnt happen because people write a fancy interface. Testing happens only when people *commit* to spending a WHOOLE bunch of their own time to do so. I think it makes sense that when, and IF, people step up to doing testing, that *those* people should get to design the interface they are going to use. Contrariwise, if no-one is willing to commit to doing testing, it makes no sense to spend a bunch of time designing an interface that no-one is going to use. If someone does decide to volunteer to test in the future, they may well toss it out the window and write their own. So it's waste of time and effort to write one now, before someone commits to doing testing. I would LOVE for us to have an official testing team, to test every package before release. [something which completely torpedoes any idea of "fully automated release" out the door, btw] As a frame of reference, I spend somewhere between 1-5 hours a week, EVERY WEEK, just looking at, and releasing packages. Testing, is going to take probably more time than that. Anyone want to commit to that kind of time, every week? From bonivart at opencsw.org Wed Jan 21 09:36:33 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 09:36:33 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090121012109.GA48238@bolthole.com> References: <20090118215602.GB56431@bolthole.com> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> <20090121012109.GA48238@bolthole.com> Message-ID: <625385e30901210036u48bdf127v63767a8bcefc328d@mail.gmail.com> On Wed, Jan 21, 2009 at 2:21 AM, Philip Brown wrote: > What was directly before it, was mention of the fallacious > "what if phil got run over by a bus" argument. Which has been solved. Solved in a bad way. It's like running a server with one PSU, no UPS and a single disk but stating that everything is perfect because you have a spare server on the shelf. In the real world those passive standby systems are rarely up to the task but needs tinkering to say the least to do the job when tested. Active standby systems don't only share the load when everything works, they also immediately pick up the slack when one server goes down. That's how you design systems. Or processes in our case. -- /peter From bonivart at opencsw.org Wed Jan 21 09:45:14 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 09:45:14 +0100 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: <625385e30901210045q19f979fbv3e79285f10528a71@mail.gmail.com> On Wed, Jan 21, 2009 at 2:50 AM, Philip Brown wrote: > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a day. I wasn't talking about only the maintainer who owns the package, having a closed release process is part of our testing problem. By having a system that is easily available more people may see the need for testing and be willing to commit to a missing part. But as usual you paint a black and white scenario where it's no point in even trying to improve stuff. > As a frame of reference, I spend somewhere between 1-5 hours a week, EVERY > WEEK, just looking at, and releasing packages. > > Testing, is going to take probably more time than that. > Anyone want to commit to that kind of time, every week? My main reason for this is not some kind of personal gain as you have tried to convince others, but to make the community grow and be ready for that. It would mean even more packages that would need to be handled by you alone. You will not be able to keep reasonable times and quality. By sharing, the load would be less on all, including you, and times would be kept even if one is on vacation for example. That is, if you're ready to use your six years of experience doing this to teach others. That would be a good thing for all. -- /peter From bonivart at opencsw.org Wed Jan 21 14:44:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 14:44:42 +0100 Subject: [csw-maintainers] pkgutil 1.4 released Message-ID: <625385e30901210544y6b95ad51u56e4150a3370dd31@mail.gmail.com> I have released version 1.4 of pkgutil and the main news is that it's much faster at calculating dependencies than before. You who had tried to install complex packages with lots of dependencies had to wait for many minutes to get results, now it should be down to seconds. In my tests it's been more than 100x faster in some cases. Release history for v1.4: * Dependency calculations are now much faster * Support for local file repositories (Dennis Clarke) * Keyword "same" when using -c replaced with "SAME" (Dennis Clarke) * Bldcat now skips SUNW packages as dependencies The reason for such a short list (when I have a huge wishlist) is that I'm working with another developer on a large patch and I underestimated the time it takes to implement and test so I decided to release v1.4 with this important speed increase and then continue with the patch. More info about pkgutil here: http://pkgutil.wikidot.com -- /peter From glaw at opencsw.org Wed Jan 21 17:34:45 2009 From: glaw at opencsw.org (Gary Law) Date: Wed, 21 Jan 2009 16:34:45 +0000 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: 2009/1/21 Philip Brown > On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: > >... > > Not only will maintainers know better what is and is not > > happening with their packages, I think it will encourage testing as > > well. > > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a day. > > As far as testing goes: > Across-the-board testing doesnt happen because people write a fancy > interface. > Testing happens only when people *commit* to spending a WHOOLE bunch of > their own time to do so. > > I think it makes sense that when, and IF, people step up to doing testing, > that *those* people should get to design the interface they are going to > use. > > Contrariwise, if no-one is willing to commit to doing testing, it makes no > sense to spend a bunch of time designing an interface that no-one is going > to use. > If someone does decide to volunteer to test in the future, they may well > toss it out the window and write their own. So it's waste of time and > effort to write one now, before someone commits to doing testing. > People test my packages before release. I get feedback and I've made plenty of changes in response to this. Most of this came from you Phil, but I got a lot from other people too, including one report only last week from the package I rolled up a week before. An entirely or largely automated test regime would reduce or eliminate the load on volunteers of course. Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Wed Jan 21 19:10:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 19:10:32 +0100 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> Hi, Am 21.01.2009 um 02:50 schrieb Philip Brown: > On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: >> ... >> Not only will maintainers know better what is and is not >> happening with their packages, I think it will encourage testing as >> well. > > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a > day. That is okay. If someone is willing to work on the next-generation package tracking web interface: even better. > As far as testing goes: > Across-the-board testing doesnt happen because people write a fancy > interface. Only if it is hard. We already have a testing catalog. If we had a full catalog (instead of an "add-on") people could subscribe to testing/ directly. If we then had some easy-to-use feedback mechanism (Mantis with prior registration is not!) that may help. > I would LOVE for us to have an official testing team, to test every > package > before release. > [something which completely torpedoes any idea of "fully automated > release" > out the door, btw] Fully automated testing is what checkpkg already does. What Phil does is looking for things like consistent naming, decent package splitting, putting files in the correct locations, all things that you simply can not automate - and these things are important too. However, the operational guidelines for this can and should be written down in addition to the formal guidelines in checkpkg. Best regards -- Dago From dam at opencsw.org Wed Jan 21 19:12:33 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 19:12:33 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> Message-ID: <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> Hi, Am 18.01.2009 um 21:17 schrieb Dagobert Michelsen: > Am 18.01.2009 um 20:48 schrieb Philip Brown: > >> On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: >>> If you addressed the issues why don't you publish an answer to each >>> one, on the same page, this way we can see what's still undecided >>> and >>> can add to William topics; we can even discuss them here. > > Good point Peter. > >> I'll let the secretary do that ;-) > > I'll take care of that. I added the current status to http://wiki.opencsw.org/suggestions Feel free to comment on the status or to request improvements ;-) Best regards -- Dago From phil at bolthole.com Wed Jan 21 19:22:07 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 21 Jan 2009 10:22:07 -0800 Subject: [csw-maintainers] testing team for packages In-Reply-To: <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> References: <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> Message-ID: <20090121182207.GC27028@bolthole.com> On Wed, Jan 21, 2009 at 07:10:32PM +0100, Dagobert Michelsen wrote: > ... > Fully automated testing is what checkpkg already does. What Phil does is > looking for things like consistent naming, decent package splitting, > putting files in the correct locations, all things that you simply > can not automate - and these things are important too. However, the > operational guidelines for this can and should be written down in > addition to the formal guidelines in checkpkg. and, as far as is reasonable to do so in a uniform fashion, [once again] This Is Already Handled. That is what the "filesystem layout" page is for, under the standards area, for example. From harpchad at opencsw.org Wed Jan 21 19:58:52 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 21 Jan 2009 12:58:52 -0600 Subject: [csw-maintainers] testing: libxslt and curl Message-ID: <4977706C.7020700@opencsw.org> New versions of libxslt and curl are now in testing. These are some of my first builds using gar v2, so please test if you have a dependency. libxslt is now distributed as three packages: CSWlibxslt libxslt CSWlibxsltdevel libxslt_devel CSWpylibxslt pylibxslt curl is like wise distrubuted as three packages: CSWcurl curl CSWcurldevel curldevel CSWcurlrt curlrt From bonivart at opencsw.org Wed Jan 21 20:12:08 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 20:12:08 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> Message-ID: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen wrote: > I added the current status to > http://wiki.opencsw.org/suggestions > > Feel free to comment on the status or to request improvements ;-) The maintainer suggestion status is "done", referring to a blank page. It will be interesting to read its future content. ;-) Another thing is the done status for "equal status between install tools". You refer to your testing page but that is the only page that even mentions pkgutil. Everywhere on the main site (home, packages, mirror and so on) it's only pkg-get and on the mirror roots only pkg-get is available for new users, the README file there also only mention pkg-get. -- /peter From dam at opencsw.org Wed Jan 21 21:00:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 21:00:32 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <92EE88DA-5AB1-4556-BA6B-18DEE9057A99@opencsw.org> Hi Peter, Am 21.01.2009 um 20:12 schrieb Peter Bonivart: > On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen > wrote: >> I added the current status to >> http://wiki.opencsw.org/suggestions >> >> Feel free to comment on the status or to request improvements ;-) > > The maintainer suggestion status is "done", referring to a blank page. > It will be interesting to read its future content. ;-) Grrr... mistyped link now corrected ;-) > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. I see. That should be addressed. Phil, the presentation of tools on the webpage should be adjusted to allow equal use. It is a good thing you wrote pkg-get and that it runs everywhere due to the implementation language. But it is equally good to have the choice of another tool with slightly different goals. A good point to fully address this issue would be IMHO the new website from William, which hopefully come very soon. Best regards -- Dago From dam at opencsw.org Wed Jan 21 21:02:28 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 21:02:28 +0100 Subject: [csw-maintainers] testing: libxslt and curl In-Reply-To: <4977706C.7020700@opencsw.org> References: <4977706C.7020700@opencsw.org> Message-ID: <7AD57E29-EC47-4F1C-93BC-C6FEE0D05F0D@opencsw.org> Hi Chad, Am 21.01.2009 um 19:58 schrieb Chad Harp: > New versions of libxslt and curl are now in testing. These are some > of > my first builds using gar v2 This is very brave of you :-) > so please test if you have a dependency. > > libxslt is now distributed as three packages: > > CSWlibxslt libxslt > CSWlibxsltdevel libxslt_devel > CSWpylibxslt pylibxslt You may want to have a look at the REQUIRED_PKGS_ to get rid of the .depend-files and use SPKG_DESC_ for individual description strings. A good reference is the Makefile from 'bind' which uses most of the new features. > curl is like wise distrubuted as three packages: > > CSWcurl curl > CSWcurldevel curldevel > CSWcurlrt curlrt Thanks for your constant contribution and enhancements! Best regards -- Dago From william at wbonnet.net Wed Jan 21 21:01:35 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 21 Jan 2009 21:01:35 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <49777F1F.6050202@wbonnet.net> Hi Peter > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. > It will be documented on the next version of the web site. Blog engine is already online, if you agree we can work together on the description for your tools. Especially the "quickstart" page has to be created and filled for both tools cheers W. /me back after four days of blackout... -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Wed Jan 21 22:26:15 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 22:26:15 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <49777F1F.6050202@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <49777F1F.6050202@wbonnet.net> Message-ID: <625385e30901211326v7e3ad652m32351e2c48819d37@mail.gmail.com> On Wed, Jan 21, 2009 at 9:01 PM, William Bonnet wrote: > Hi Peter >> Another thing is the done status for "equal status between install >> tools". You refer to your testing page but that is the only page that >> even mentions pkgutil. Everywhere on the main site (home, packages, >> mirror and so on) it's only pkg-get and on the mirror roots only >> pkg-get is available for new users, the README file there also only >> mention pkg-get. >> > It will be documented on the next version of the web site. Blog engine > is already online, if you agree we can work together on the description > for your tools. Especially the "quickstart" page has to be created and > filled for both tools I would very much like that. :-) I will do my best to help. -- /peter From bonivart at opencsw.org Thu Jan 22 15:26:16 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 15:26:16 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122050944.GA31372@keevey> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> Message-ID: <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> Forwarded from the users list... Was this a deliberate change implemented in GAR or did I screw up somehow? :-/ ---------- Forwarded message ---------- From: Rob Stampfli Date: Thu, Jan 22, 2009 at 6:09 AM Subject: Re: [csw-users] Warning: Latest Clamav does not work on old Sparcs To: questions and discussions On Wed, Jan 21, 2009 at 10:36:13PM -0500, Rob Stampfli wrote: > Just a head's up: The latest clamav build (0.94.2,REV=2008.12.18) > is built for the SPARC32PLUS / V8+, and will not run on the older > Sparc V7 architecture. Beware of this gotcha if you are planning > to upgrade from the 0.92.1,REV=2008.02.11 load on an older Sparc. > > And as long as I have your attention, I notice that the most recent > version of libtool and libtool_rt is older than the prior version: > The version I am running is 2.2.4,REV=2008.05.16, whereas the version > currently being offered is 1.5.26,REV=2008.12.22. What is recommended? > Backing back to 1.5.26 or waiting to see what happens? I see the new Python load is also V8+ now, so apparently there has been a change. I realize there has been some sort of split between Blastwave CSW and Opencsw, probably revolving around this very issue from what I've been able to discern. I suppose this means I need to go over to Opencsw for my old systems. Sorry to bother you all. Rob _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users -- /peter From dam at opencsw.org Thu Jan 22 17:00:16 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:00:16 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> Message-ID: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Hi Peter, Am 22.01.2009 um 15:26 schrieb Peter Bonivart: > Forwarded from the users list... > > Was this a deliberate change implemented in GAR or did I screw up > somehow? :-/ Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. You should have better just reset OPT_FLAGS_SOS11_sparc and the equivalent flags. Being least-invasive here is quite important. Phil, this would be nice to catch in checkpkg. Best regards -- Dago > ---------- Forwarded message ---------- > From: Rob Stampfli > Date: Thu, Jan 22, 2009 at 6:09 AM > Subject: Re: [csw-users] Warning: Latest Clamav does not work on old > Sparcs > To: questions and discussions > > > On Wed, Jan 21, 2009 at 10:36:13PM -0500, Rob Stampfli wrote: >> Just a head's up: The latest clamav build (0.94.2,REV=2008.12.18) >> is built for the SPARC32PLUS / V8+, and will not run on the older >> Sparc V7 architecture. Beware of this gotcha if you are planning >> to upgrade from the 0.92.1,REV=2008.02.11 load on an older Sparc. >> >> And as long as I have your attention, I notice that the most recent >> version of libtool and libtool_rt is older than the prior version: >> The version I am running is 2.2.4,REV=2008.05.16, whereas the version >> currently being offered is 1.5.26,REV=2008.12.22. What is >> recommended? >> Backing back to 1.5.26 or waiting to see what happens? > > I see the new Python load is also V8+ now, so apparently there has > been a change. I realize there has been some sort of split between > Blastwave CSW and Opencsw, probably revolving around this very issue > from what I've been able to discern. I suppose this means I need > to go over to Opencsw for my old systems. Sorry to bother you all. > > Rob > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > > > > -- > /peter > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Thu Jan 22 17:09:41 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:09:41 +0100 Subject: [csw-maintainers] Best-practice on texinfo - cswclassutils? Message-ID: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> Hi, I noticed that some legacy packages have an integration of regenerating the texinfo index when files are added in a package. We don't have anything in GAR for this yet. I guess it would be nice to have that in cswclassutils. Thoughts? Best regards -- Dago From bonivart at opencsw.org Thu Jan 22 17:12:53 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 17:12:53 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Message-ID: <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> On Thu, Jan 22, 2009 at 5:00 PM, Dagobert Michelsen wrote: > Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile > of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. > You should have better just reset OPT_FLAGS_SOS11_sparc and > the equivalent flags. Being least-invasive here is quite important. I remember us discussing optimization and that x03 didn't work but x02 did. By changing to x02 I accidentally removed all other options then..? Could you be more specific on how I should change my Makefile? How about that Python package he mentions then? -- /peter From dam at opencsw.org Thu Jan 22 17:18:30 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:18:30 +0100 Subject: [csw-maintainers] FYI: Temporarily deactivation .la-files Message-ID: Hi, I have currently serious trouble with .la-files and have therefore temporarily renamed all files from /opt/csw/lib/*.la to /opt/csw/lib/*.la.moved on build8s only (!). I'll undo the changes after my tests. Please be aware and let me know if you encounter anything. Best regards -- Dago From dam at opencsw.org Thu Jan 22 17:43:24 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:43:24 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> Message-ID: Hi Peter, Am 22.01.2009 um 17:12 schrieb Peter Bonivart: > On Thu, Jan 22, 2009 at 5:00 PM, Dagobert Michelsen > wrote: >> Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile >> of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. >> You should have better just reset OPT_FLAGS_SOS11_sparc and >> the equivalent flags. Being least-invasive here is quite important. > > I remember us discussing optimization and that x03 didn't work but x02 > did. I had a similar problem with SE Toolkit some time ago. The problem was produced by using jumps to codereferences without declaring the proper variables volatile. See for details. This may help identifying the problem upstream so you can compile the next versions with -xO3 again :-) > By changing to x02 I accidentally removed all other options > then..? More specifically by setting CFLAGS directly. > Could you be more specific on how I should change my Makefile? Nice and easy after my enhancement in r2875 with OPT_FLAGS_SOS = -xO2 As this is quite new please let me know if it worked. > How about that Python package he mentions then? That package was done by Ken Mays and the description is not in GAR: I don't know what happened there. The package at OpenCSW looks ok, but is old. Best regards -- Dago From dam at opencsw.org Thu Jan 22 17:45:19 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:45:19 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <4978A12E.8090407@opencsw.org> References: <4978A12E.8090407@opencsw.org> Message-ID: <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Hi Chad, Am 22.01.2009 um 17:39 schrieb Chad Harp: > Dagobert Michelsen wrote: >> I have currently serious trouble with .la-files and have therefore >> temporarily renamed all files from >> /opt/csw/lib/*.la >> to >> /opt/csw/lib/*.la.moved >> on build8s only (!). I'll undo the changes after my tests. >> >> Please be aware and let me know if you encounter anything. >> > > Is there a reason we shouldn't leave it that way (and replicate the > change on the rest of the build env)? > > I've been having a similar problem and have been delaying some updates > until the .la problem gets resolved. I understand that in some cases > the .la files are required, but we could deal with those on an > exception > basis. I guess that would be best. That way we don't pollute new packages. Best regards -- Dago From bonivart at opencsw.org Thu Jan 22 18:04:54 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 18:04:54 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> Message-ID: <625385e30901220904q2063546cy668ef7bd5cc022be@mail.gmail.com> On Thu, Jan 22, 2009 at 5:43 PM, Dagobert Michelsen wrote: > Nice and easy after my enhancement in r2875 with > OPT_FLAGS_SOS = -xO2 > > As this is quite new please let me know if it worked. Before: clamscan: ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, dynamically linked, stripped After: clamscan: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped :-) -- /peter From korpela at opencsw.org Thu Jan 22 18:13:06 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 22 Jan 2009 09:13:06 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: In some cases I'm having the opposite problem because of missing dependencies that were supposed to be in the .la files of packages where the .la files were not installed. Shouldn't problems in .la files be reported as bugs to the package maintainers? If a package includes them it's up the the maintainers to see that they are correct, no? Eric On Thu, Jan 22, 2009 at 8:45 AM, Dagobert Michelsen wrote: > Hi Chad, > > Am 22.01.2009 um 17:39 schrieb Chad Harp: >> Dagobert Michelsen wrote: >>> I have currently serious trouble with .la-files and have therefore >>> temporarily renamed all files from >>> /opt/csw/lib/*.la >>> to >>> /opt/csw/lib/*.la.moved >>> on build8s only (!). I'll undo the changes after my tests. >>> >>> Please be aware and let me know if you encounter anything. >>> >> >> Is there a reason we shouldn't leave it that way (and replicate the >> change on the rest of the build env)? >> >> I've been having a similar problem and have been delaying some updates >> until the .la problem gets resolved. I understand that in some cases >> the .la files are required, but we could deal with those on an >> exception >> basis. > > I guess that would be best. That way we don't pollute new packages. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From pfelecan at opencsw.org Thu Jan 22 18:30:26 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 18:30:26 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: (Eric J. Korpela's message of "Thu\, 22 Jan 2009 09\:13\:06 -0800") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: Eric J Korpela writes: > In some cases I'm having the opposite problem because of missing > dependencies that were supposed to be in the .la files of packages > where the .la files were not installed. > > Shouldn't problems in .la files be reported as bugs to the package > maintainers? If a package includes them it's up the the maintainers > to see that they are correct, no? Indeed, the .la files *are* useful and not having them is a pain... If the paths in the .la files are incorrect it *is* a bug and *must* be corrected. BTW, moving the .la files as you have done can be disruptive for activities of other maintainers and, IMHO should be done on a test system. my 8.5*10^12 cents --- and growing -- Peter From dam at opencsw.org Thu Jan 22 18:47:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 18:47:32 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Hi Peter, Am 22.01.2009 um 18:30 schrieb Peter FELECAN: > Eric J Korpela writes: >> In some cases I'm having the opposite problem because of missing >> dependencies that were supposed to be in the .la files of packages >> where the .la files were not installed. >> >> Shouldn't problems in .la files be reported as bugs to the package >> maintainers? If a package includes them it's up the the maintainers >> to see that they are correct, no? > > Indeed, the .la files *are* useful and not having them is a pain... If > the paths in the .la files are incorrect it *is* a bug and *must* be > corrected. The reason for officially banning .la-files in new packages is that you can get in a situation where you cannot build a software when an old version is installed because libtool picks up the old files and links against the old libs. > BTW, moving the .la files as you have done can be disruptive for > activities of other maintainers and, IMHO should be done on a test > system. I am really sorry for that. I'll undo my changes in an hour and promise to keep away from using misusing my root powers again *-) Best regards -- Dago From pfelecan at opencsw.org Thu Jan 22 18:54:37 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 18:54:37 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> (Dagobert Michelsen's message of "Thu\, 22 Jan 2009 18\:47\:32 +0100") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: Dagobert Michelsen writes: > Hi Peter, > > Am 22.01.2009 um 18:30 schrieb Peter FELECAN: >> Eric J Korpela writes: >>> In some cases I'm having the opposite problem because of missing >>> dependencies that were supposed to be in the .la files of packages >>> where the .la files were not installed. >>> >>> Shouldn't problems in .la files be reported as bugs to the package >>> maintainers? If a package includes them it's up the the maintainers >>> to see that they are correct, no? >> >> Indeed, the .la files *are* useful and not having them is a pain... If >> the paths in the .la files are incorrect it *is* a bug and *must* be >> corrected. > > The reason for officially banning .la-files in new packages is that > you can get in a situation where you cannot build a software when > an old version is installed because libtool picks up the old files > and links against the old libs. There is no way to prohibit the usage of the old, installed .la files when building the new package? It seems to me a less brutal approach. >> BTW, moving the .la files as you have done can be disruptive for >> activities of other maintainers and, IMHO should be done on a test >> system. > > I am really sorry for that. I'll undo my changes in an hour and promise > to keep away from using misusing my root powers again *-) It's alright, my observation was just a question of principle. -- Peter From dam at opencsw.org Thu Jan 22 18:57:29 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 18:57:29 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: <48D4AED4-53F7-4BA8-98CB-63E18740276F@opencsw.org> Hi, Am 22.01.2009 um 18:47 schrieb Dagobert Michelsen: >> BTW, moving the .la files as you have done can be disruptive for >> activities of other maintainers and, IMHO should be done on a test >> system. > > I am really sorry for that. I'll undo my changes in an hour and > promise > to keep away from using misusing my root powers again *-) Changes undone on build8s. Everything should be fine again. Sorry for the inconvenience -- Dago From dam at opencsw.org Thu Jan 22 19:07:25 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 19:07:25 +0100 Subject: [csw-maintainers] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: Hi Peter, Am 22.01.2009 um 18:54 schrieb Peter FELECAN: > Dagobert Michelsen writes: >> The reason for officially banning .la-files in new packages is that >> you can get in a situation where you cannot build a software when >> an old version is installed because libtool picks up the old files >> and links against the old libs. > > There is no way to prohibit the usage of the old, installed .la > files when building the new package? It seems to me a less brutal > approach. If you know one than I would be really interested to hear it. This is the answer I got from Bruno Haible, a GNU maintainer for libiconv and a dozen other packages when I asked him about the problem: Am 11.04.2008 um 13:13 schrieb Bruno Haible: > This is a known problem with libtool and DESTDIR installations. > On some systems you simply cannot create an executable that should > link to /opt/csw/lib/libiconv.so if the library is not yet there. > On the other systems, libtool could do a bit better when you ask > to link with /tmp/pkgdir/opt/csw/lib/libiconv.la (it could use > /tmp/pkgdir/opt/csw/lib/libiconv.so). > > So, in general, I recommend to do first the "make install" and then > only > "make install DESTDIR=..." Using /tmp for temp linking spoils other config files like pkgconfig, so I figured removing .la-files at all will help here. Best regards -- Dago From phil at bolthole.com Thu Jan 22 19:32:12 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:32:12 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Message-ID: <20090122183210.GA23122@bolthole.com> On Thu, Jan 22, 2009 at 05:00:16PM +0100, Dagobert Michelsen wrote: > > Phil, this [sparc executables not v8] would be nice to catch in checkpkg. yes, it would :) but it's tricky, which is why I havent implemented it previously. The problems being that 1. not all executables HAVE to be in /opt/csw/bin 2. some executables are LEGITIMATELY non vanilla v8. Best I could do, would be to look at executables in /opt/csw/bin only. Which would still potentially miss somethings, but would at least catch more than is being done now. yes/no? From dam at opencsw.org Thu Jan 22 19:35:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 19:35:54 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122183210.GA23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> Message-ID: <5C8A5524-D69E-43F5-AD3D-06A32EA3B922@opencsw.org> Hi Phil, Am 22.01.2009 um 19:32 schrieb Philip Brown: > On Thu, Jan 22, 2009 at 05:00:16PM +0100, Dagobert Michelsen wrote: >> >> Phil, this [sparc executables not v8] would be nice to catch in >> checkpkg. > > yes, it would :) but it's tricky, which is why I havent implemented it > previously. > > The problems being that > > 1. not all executables HAVE to be in /opt/csw/bin > 2. some executables are LEGITIMATELY non vanilla v8. > > Best I could do, would be to look at executables in /opt/csw/bin only. > Which would still potentially miss somethings, but would at least > catch > more than is being done now. You could search for all binaries. Every binary must conform to v8/i386 with the exception of binaries residing in directories named after the ISA, e. h. sparcv9/ may contain a binary with sparcv9. That is at least true for all GAR builds as far as I know of. Best regards -- Dago From harpchad at opencsw.org Thu Jan 22 19:37:14 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 22 Jan 2009 12:37:14 -0600 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: <4978BCDA.9070508@opencsw.org> Several of those packages don't have maintainers. By leaving them there we're deciding not to build new packages that have a broken libtool dependencies. i.e. Old package that no longer has a maintainer has an [a.la] file that references another [b.la] file. But b.la is gone now because the maintainer of that package is stripping .la files when he packages. Now packages that depend on a.so will not build because libtool wants to see b.la. We need a global policy on libtool files. We should either remove them all allowing them only by exception or chose to keep them. Right now the build farm is in a state where I cannot build most of my packages because old .la files reference .la files that have been removed in newer builds by package maintainers. Cleaning this up is probably going to be painful, maybe someone has some libtool magic to make it build around these situations? Eric J Korpela wrote: > In some cases I'm having the opposite problem because of missing > dependencies that were supposed to be in the .la files of packages > where the .la files were not installed. > > Shouldn't problems in .la files be reported as bugs to the package > maintainers? If a package includes them it's up the the maintainers > to see that they are correct, no? > > Eric > > On Thu, Jan 22, 2009 at 8:45 AM, Dagobert Michelsen wrote: >> Hi Chad, >> >> Am 22.01.2009 um 17:39 schrieb Chad Harp: >>> Dagobert Michelsen wrote: >>>> I have currently serious trouble with .la-files and have therefore >>>> temporarily renamed all files from >>>> /opt/csw/lib/*.la >>>> to >>>> /opt/csw/lib/*.la.moved >>>> on build8s only (!). I'll undo the changes after my tests. >>>> >>>> Please be aware and let me know if you encounter anything. >>>> >>> Is there a reason we shouldn't leave it that way (and replicate the >>> change on the rest of the build env)? >>> >>> I've been having a similar problem and have been delaying some updates >>> until the .la problem gets resolved. I understand that in some cases >>> the .la files are required, but we could deal with those on an >>> exception >>> basis. >> I guess that would be best. That way we don't pollute new packages. >> >> >> Best regards >> >> -- Dago >> _______________________________________________ >> maintainers mailing list >> maintainers at lists.opencsw.org >> https://lists.opencsw.org/mailman/listinfo/maintainers >> From bwalton at opencsw.org Thu Jan 22 19:39:02 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 22 Jan 2009 13:39:02 -0500 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122183210.GA23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> Message-ID: <1232649483-sup-19@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Jan 22 13:32:12 -0500 2009: > Best I could do, would be to look at executables in /opt/csw/bin only. > Which would still potentially miss somethings, but would at least catch > more than is being done now. ...but checkpkg is already doing a `find ...` and discovering anything with an ELF header. Couldn't this list be overloaded to help in this situation? -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Jan 22 19:47:49 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:47:49 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <1232649483-sup-19@ntdws12.chass.utoronto.ca> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> Message-ID: <20090122184748.GB23122@bolthole.com> On Thu, Jan 22, 2009 at 01:39:02PM -0500, Ben Walton wrote: > Excerpts from Philip Brown's message of Thu Jan 22 13:32:12 -0500 2009: > > Best I could do, would be to look at executables in /opt/csw/bin only. > > Which would still potentially miss somethings, but would at least catch > > more than is being done now. > > ...but checkpkg is already doing a `find ...` and discovering anything > with an ELF header. Couldn't this list be overloaded to help in this > situation? The issue is not "finding where all ELF files are located". The issue is, "Which ones should we legitimately complain about?" As I have mentioned, the rule is NOT that *all* sparc binaries be v8. The rule is that *default* binaries be v8. One package i know of that would run afoul of a blind checkpkg check, would be mysql. which has 32bit and 64bit binaries in the same directory. but they are not /opt/csw/bin From bwalton at opencsw.org Thu Jan 22 19:51:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 22 Jan 2009 13:51:28 -0500 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122184748.GB23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> Message-ID: <1232650271-sup-5226@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Jan 22 13:47:49 -0500 2009: > The issue is not "finding where all ELF files are located". > The issue is, "Which ones should we legitimately complain about?" > As I have mentioned, the rule is NOT that *all* sparc binaries be > v8. The rule is that *default* binaries be v8. Roger that. I missed the nuance. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Jan 22 19:51:49 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:51:49 -0800 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files Message-ID: <20090122185149.GF23122@bolthole.com> oops. replied to "buildfarm" list in error. forwarding to maintainers list instead... On Thu, Jan 22, 2009 at 12:33:36PM -0600, Chad Harp wrote: > ... > We need a global policy on libtool files. We HAVE a global policy. We just unfortunately have not had people who have volunteered to repackage old orphaned packages to bring them in line with the policy. Would you like to volunteer? From dam at opencsw.org Thu Jan 22 20:01:24 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:01:24 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122184748.GB23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> Message-ID: <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> Hi Phil, Am 22.01.2009 um 19:47 schrieb Philip Brown: > One package i know of that would run afoul of a blind checkpkg > check, would > be mysql. which has 32bit and 64bit binaries in the same directory. > but they are not /opt/csw/bin This doesn't sound right. Having a legacy package not passing checkpkg shouldn't keep us from enforcing a decent up-to-date policy on new packages: /opt/csw/mysql5/libexec/mysqld64 /opt/csw/mysql5/libexec/mysqld32+ /opt/csw/mysql5/libexec/mysqld32 /opt/csw/mysql5/libexec/mysqld This could be very well the standardized /opt/csw/mysql5/libexec/sparcv8/mysqld /opt/csw/mysql5/libexec/sparcv8plus/mysqld /opt/csw/mysql5/libexec/sparcv9/mysqld Best regards -- Dago From pfelecan at opencsw.org Thu Jan 22 20:10:49 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 20:10:49 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <4978BCDA.9070508@opencsw.org> (Chad Harp's message of "Thu\, 22 Jan 2009 12\:37\:14 -0600") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BCDA.9070508@opencsw.org> Message-ID: Chad Harp writes: > Cleaning this up is probably going to be painful, maybe someone has some > libtool magic to make it build around these situations? I understand your issue. Maybe a temporary solution is to modify the .la files on the build farm to correct the issues and, when there is no more soiled .la files we can revert to a normal operation. Isn't this a good candidate for a February topic for William's list? i.e., "get rid of cruft in .la files" -- Peter From phil at bolthole.com Thu Jan 22 20:11:56 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:11:56 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> Message-ID: <20090122191155.GH23122@bolthole.com> On Thu, Jan 22, 2009 at 08:01:24PM +0100, Dagobert Michelsen wrote: > > This could be very well the standardized > /opt/csw/mysql5/libexec/sparcv8/mysqld > /opt/csw/mysql5/libexec/sparcv8plus/mysqld > /opt/csw/mysql5/libexec/sparcv9/mysqld > Please note that the usual standard is based upon the concept of having [..]/bin/isaexec which will then automatically use the "most advanced" version of the binary supported on the system, based on those subdirs. This will automatically prefer 64-bit binaries, if they can run, I believe. This is NOT the desired default behaviour for mysql, however. From pfelecan at opencsw.org Thu Jan 22 20:12:45 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 20:12:45 +0100 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files In-Reply-To: <20090122185149.GF23122@bolthole.com> (Philip Brown's message of "Thu\, 22 Jan 2009 10\:51\:49 -0800") References: <20090122185149.GF23122@bolthole.com> Message-ID: Philip Brown writes: > oops. replied to "buildfarm" list in error. forwarding to maintainers > list instead... > > > On Thu, Jan 22, 2009 at 12:33:36PM -0600, Chad Harp wrote: >> ... >> We need a global policy on libtool files. > > We HAVE a global policy. Which is?... -- Peter From phil at bolthole.com Thu Jan 22 20:40:47 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:40:47 -0800 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files In-Reply-To: References: <20090122185149.GF23122@bolthole.com> Message-ID: <20090122194047.GI23122@bolthole.com> On Thu, Jan 22, 2009 at 08:12:45PM +0100, Peter FELECAN wrote: > Philip Brown writes: > > > > We HAVE a global policy. > > Which is?... http://www.opencsw.org/standards/build "New packages should take care to EXCLUDE libtool .la files. [...] Unfortunately, existing packages may need to preserve them, until all dependant packages have their own configs adjusted to not use .la files." And this global policy, has been "implemented" in GAR already, for many months. From phil at bolthole.com Thu Jan 22 20:44:06 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:44:06 -0800 Subject: [csw-maintainers] note: our 'search' page does actually work Message-ID: <20090122194406.GJ23122@bolthole.com> FYI, to people who may not be aware: our "search" page does actually work fairly well. If you go to http://www.opencsw.org/search and drop into the Site Search box, "libtool .la files" the first hit, is the standards page referencing, "New packages should take care to EXCLUDE libtool .la files. " From dam at opencsw.org Thu Jan 22 20:46:36 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:46:36 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122191155.GH23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> <20090122191155.GH23122@bolthole.com> Message-ID: Hi Phil, Am 22.01.2009 um 20:11 schrieb Philip Brown: > On Thu, Jan 22, 2009 at 08:01:24PM +0100, Dagobert Michelsen wrote: >> >> This could be very well the standardized >> /opt/csw/mysql5/libexec/sparcv8/mysqld >> /opt/csw/mysql5/libexec/sparcv8plus/mysqld >> /opt/csw/mysql5/libexec/sparcv9/mysqld >> > > Please note that the usual standard is based upon the concept of > having > [..]/bin/isaexec > > which will then automatically use the "most advanced" version of the > binary > supported on the system, based on those subdirs. > This will automatically prefer 64-bit binaries, if they can run, I > believe. > > This is NOT the desired default behaviour for mysql, however. This is the standard for isaexec, yes. If no isaexec is used the standard is to have sparcv8 in bin/ and the 64 bit in sparcv9/ or amd64/. IIRC there is currently no standard for isaexec which lets you choose manually between 32 and 64 bit. It may look like bin/ 32 bit isaexec bin/sparcv8/ 32 bit v8 binary bin/sparcv8plus/ 32 bit v8+ binary bin/64 64 bit isaexec bin/64/sparcv9/ 64 bit v9 bin/64/sparcv9b 64 bit v9b etc. Thoughts? Best regards -- Dago From dam at opencsw.org Thu Jan 22 20:48:34 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:48:34 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BCDA.9070508@opencsw.org> Message-ID: <48BE844F-1B9D-4AEF-85FF-1CF97BEF1127@opencsw.org> Hi Peter, Am 22.01.2009 um 20:10 schrieb Peter FELECAN: > Chad Harp writes: > >> Cleaning this up is probably going to be painful, maybe someone has >> some >> libtool magic to make it build around these situations? > > I understand your issue. Maybe a temporary solution is to modify the > .la files on the build farm to correct the issues and, when there is > no more soiled .la files we can revert to a normal operation. Unfortunately this is not sufficient. The old packages itself either need to be updated or modified. We could repackage the old packages without .la-files if necessary. > Isn't this a good candidate for a February topic for William's list? > i.e., "get rid of cruft in .la files" Yes. This can be done under "bug squashing". Best regards -- Dago From dam at opencsw.org Thu Jan 22 21:08:00 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 21:08:00 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: Hi Eric, Am 22.01.2009 um 19:39 schrieb Eric J Korpela: > Yeah, a consistent policy is necessary. Maybe remove any for packages > without maintainers? Remove those that are reported broken? Or have > an enforced no libtool .la libraries policy? All of them could be > hard on the maintainers. Mass-remove .la-files from all packages has IMHO the least pain. After that we only must make sure that all new packages don't have them. Phil, are you in on this? Best regards -- Dago From trygvis at opencsw.org Thu Jan 22 21:40:34 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 22 Jan 2009 21:40:34 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <4978D9C2.2070904@opencsw.org> Peter Bonivart wrote: > On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen wrote: >> I added the current status to >> http://wiki.opencsw.org/suggestions >> >> Feel free to comment on the status or to request improvements ;-) > > The maintainer suggestion status is "done", referring to a blank page. > It will be interesting to read its future content. ;-) > > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. To be honest I don't see why we need two tools that does the same job. It will only be confuing to users as they won't know which tool to know, in particular if they have the same set of features. As it is now pkgutil can't replace pkg-get (try running pkgutil update on a box with more than one outdated dependency). When pkgutil is generally useful in *all* cases, I wouldn't mind a discussion. -- Trygve From bonivart at opencsw.org Thu Jan 22 22:08:22 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 22:08:22 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <4978D9C2.2070904@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> Message-ID: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> On Thu, Jan 22, 2009 at 9:40 PM, Trygve Laugst?l wrote: > To be honest I don't see why we need two tools that does the same job. > It will only be confuing to users as they won't know which tool to know, > in particular if they have the same set of features. Same basic features maybe but pkgutil already has more advanced features and a lot more is coming. Lots of people choose to install apt/yum on rpm systems even if you can argue that they do the same job as what was on the system in the first place. Choice is good. > As it is now pkgutil can't replace pkg-get (try running pkgutil update > on a box with more than one outdated dependency). When pkgutil is > generally useful in *all* cases, I wouldn't mind a discussion. Are you talking about pre-1.4 now? Version 1.4 is lots faster. If you still have performance issues with 1.4 or other issues I wouldn't mind a discussion about that either. Or you could just keep using pkg-get if you like that one better. Choice is good. :-) -- /peter From phil at bolthole.com Thu Jan 22 22:48:05 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 13:48:05 -0800 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> Message-ID: <20090122214805.GQ23122@bolthole.com> On Thu, Jan 22, 2009 at 10:08:22PM +0100, Peter Bonivart wrote: > Same basic features maybe but pkgutil already has more advanced > features and a lot more is coming. the same can be said of pkg-get. your "comparison page" is very out of date. From trygvis at opencsw.org Thu Jan 22 23:51:13 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 22 Jan 2009 23:51:13 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> Message-ID: <4978F861.2040301@opencsw.org> Peter Bonivart wrote: > On Thu, Jan 22, 2009 at 9:40 PM, Trygve Laugst?l wrote: >> To be honest I don't see why we need two tools that does the same job. >> It will only be confuing to users as they won't know which tool to know, >> in particular if they have the same set of features. > > Same basic features maybe but pkgutil already has more advanced > features and a lot more is coming. Lots of people choose to install > apt/yum on rpm systems even if you can argue that they do the same job > as what was on the system in the first place. Choice is good. As a project I don't think choice is necessarily a good thing if it increases the burden on us as a team as we would have to support two tools which can (and most likely will) fail in different ways. Having all tool available in the catalog is to me obviously a good thing. Do not take this personal or as critique of pkgutil or pkg-get. It is too bad that you couldn't work together on the same code base. Choice is good in the way that you took the ideas of pkg-get and added more, useful features. pkg-get has caught up (at least to a certain extent, I haven't checked out the new features of either tool), good for that tool. >> As it is now pkgutil can't replace pkg-get (try running pkgutil update >> on a box with more than one outdated dependency). When pkgutil is >> generally useful in *all* cases, I wouldn't mind a discussion. > > Are you talking about pre-1.4 now? Version 1.4 is lots faster. If you > still have performance issues with 1.4 or other issues I wouldn't mind > a discussion about that either. Or you could just keep using pkg-get > if you like that one better. Choice is good. :-) I'm not saying anything about what version I like or not, it is not relevant. You know I've already given you several feature requests. -- Trygve From korpela at opencsw.org Fri Jan 23 00:31:17 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 22 Jan 2009 15:31:17 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: That should probably work. Some packages may need some fixes to their build scripts to bring them in line. Some stuff developed on Linux assumes that they are there, or that a library isn't there if the .la file isn't, but IMHO, that's a bug anyway. It also can make static linking a pain, but that's rarely required when using a package manager. Eric From bonivart at opencsw.org Fri Jan 23 00:43:39 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 23 Jan 2009 00:43:39 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <4978F861.2040301@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> <4978F861.2040301@opencsw.org> Message-ID: <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> On Thu, Jan 22, 2009 at 11:51 PM, Trygve Laugst?l wrote: > You know I've already given you several feature requests. ...and I'm working on that... :-) -- /peter From skayser at opencsw.org Fri Jan 23 01:13:41 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 23 Jan 2009 01:13:41 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4966066B.4060804@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> Message-ID: <49790BB5.6030201@opencsw.org> Alessio wrote: > xterm 238 is now available on /testing Any chance that this can be pushed to current? I have been using it quite happily over the last two weeks and xterm 235 which we currently carry in the catalog has known security issues. http://opencsw.org/bugtrack/view.php?id=2978 Sebastian From harpchad at opencsw.org Fri Jan 23 03:45:46 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 22 Jan 2009 20:45:46 -0600 Subject: [csw-maintainers] Library dependency search Message-ID: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> Prior to the last release or curl I did a search on http:// www.opencsw.org/search (exact match) for libcurl.so.3 to see if any packages still depended on the older version. I didn't find any so I didn't include them in the new release. It turns out there is at least 1 package that does depend on it (grip). So is the search engine broken, or am I just using it wrong (or not understanding what it searches on)? --chad From phil at bolthole.com Fri Jan 23 04:59:19 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 19:59:19 -0800 Subject: [csw-maintainers] Library dependency search In-Reply-To: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> References: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> Message-ID: <20090123035919.GA59756@bolthole.com> On Thu, Jan 22, 2009 at 08:45:46PM -0600, Chad Harp wrote: > Prior to the last release or curl I did a search on http:// > www.opencsw.org/search (exact match) for libcurl.so.3 to see if any > packages still depended on the older version. I didn't find any so I > didn't include them in the new release. > > It turns out there is at least 1 package that does depend on it (grip). > > So is the search engine broken, or am I just using it wrong (or not > understanding what it searches on)? Hmm.. that's odd. I see "libcurl.so.3" in the dependancy database. but it doesnt come up on the search page. I'll look into it. From phil at bolthole.com Fri Jan 23 05:10:26 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 20:10:26 -0800 Subject: [csw-maintainers] Library dependency search In-Reply-To: <20090123035919.GA59756@bolthole.com> References: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> <20090123035919.GA59756@bolthole.com> Message-ID: <20090123041026.GB59756@bolthole.com> On Thu, Jan 22, 2009 at 07:59:19PM -0800, Philip Brown wrote: > I see "libcurl.so.3" in the dependancy database. but it doesnt come up on > the search page. I'll look into it. Aha.. you hit an edge case; you queried it, after "libcurl.so.3" did not exist in any active package. The search page made an invalid assumption, that if a shared lib did not exist in any existing package, there was no point in doing a dependancy search for that lib. now fixed. From phil at bolthole.com Fri Jan 23 06:35:25 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 21:35:25 -0800 Subject: [csw-maintainers] Best-practice on texinfo - cswclassutils? In-Reply-To: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> References: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> Message-ID: <20090123053525.GL71834@bolthole.com> On Thu, Jan 22, 2009 at 05:09:41PM +0100, Dagobert Michelsen wrote: > Hi, > > I noticed that some legacy packages have an integration of > regenerating the texinfo index when files are added in a > package. We don't have anything in GAR for this yet. I guess > it would be nice to have that in cswclassutils. Thoughts? yes, precisely. that is on my waay-too-long todo list. would be nice if someone else did that class script. [ so XXX.info files, can be of class cswtexinfo, and the info 'dir' file can be automatically regenerated when needed ] From trygvis at opencsw.org Fri Jan 23 11:45:31 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 23 Jan 2009 11:45:31 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> <4978F861.2040301@opencsw.org> <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> Message-ID: <49799FCB.3070509@opencsw.org> Peter Bonivart wrote: > On Thu, Jan 22, 2009 at 11:51 PM, Trygve Laugst?l wrote: >> You know I've already given you several feature requests. > > ...and I'm working on that... :-) Excellent! I'm looking forward to trying out 1.4. -- Trygve From dam at opencsw.org Fri Jan 23 16:18:11 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:18:11 +0100 Subject: [csw-maintainers] [csw-users] lsof In-Reply-To: <4978E284.CC54.005D.3@emporia.edu> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220929q3251d481ye4cf0ddbe57314e8@mail.gmail.com> <20090122223502.GA2836@keevey> <4978E284.CC54.005D.3@emporia.edu> Message-ID: <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> Hi Glen, Am 23.01.2009 um 04:17 schrieb Glen Gunselman: > Are there any plans to update lsof? > > It looks like an update has been requested several times in the past. Plans, yes. We don't currently have Solaris 9 build machines in the farm. I look into it. BTW: If I recall correctly you offered to help in november. We are desperately needing testers who try out stuff in testing at and give feedback. It would be a great help if you used the new packages on some of your machines. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Jan 23 16:24:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:24:54 +0100 Subject: [csw-maintainers] Updating CSW packages on the buildfarm now Message-ID: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> Hi, I am updating all installed CSW packages form the buildfarms to the most recent versions in current/ now. I'll let you know when I'm finished. Sorry for inconvenience -- Dago From dam at opencsw.org Fri Jan 23 16:47:43 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:47:43 +0100 Subject: [csw-maintainers] [csw-buildfarm] Updating CSW packages on the buildfarm now In-Reply-To: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> References: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> Message-ID: <67F910E3-2C1F-4EEA-8043-3311A0068684@opencsw.org> Hi, Am 23.01.2009 um 16:24 schrieb Dagobert Michelsen: > I am updating all installed CSW packages form the buildfarms to the > most recent versions in current/ now. I'll let you know when I'm > finished. All buildfarm servers now run current. Best regards -- Dago From harpchad at opencsw.org Fri Jan 23 20:04:56 2009 From: harpchad at opencsw.org (Chad Harp) Date: Fri, 23 Jan 2009 13:04:56 -0600 Subject: [csw-maintainers] Mantis issue Message-ID: <497A14D8.9090406@opencsw.org> I was opening bugs against several packages today. I opened four tabs in my browser, one for each project, and submitted the reports. But all four reports were filed against the last tab I opened. Apparently Mantis uses cookies to track the active project rather than fields in the post data? Is that fixed in a later revision? Can one of the Mantis admins remove bugs 3039, 3040 and 3041 from bzflag? Sorry, Chad From dam at opencsw.org Fri Jan 23 20:14:05 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 20:14:05 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Hi, I put the monthly thematics proposal in the Wiki at for further reference. If you feel your points in the discussion should be reflected on the page please reply with the updates. Thanks! -- Dago From dam at opencsw.org Fri Jan 23 22:21:39 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 22:21:39 +0100 Subject: [csw-maintainers] Now available: build9s Message-ID: Fellow maintainers, an OpenCSW-user has recently requested an updated version from top. top needs to be compiled on each Solaris version separately, so it is necessary to have a Solaris 9 build infrastructure. The Sparc server is available now: build9s Let me know if you encounter anything strange. The x86 version build9x will follow soon. Thanks! -- Dago From phil at bolthole.com Sat Jan 24 00:32:21 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 23 Jan 2009 15:32:21 -0800 Subject: [csw-maintainers] /testing: new gd package Message-ID: <20090123233221.GJ57355@bolthole.com> i just made a new gd package and dropped it in testing. i hope folks will give it a spin and verify that it fixes the issues with the current one. From dam at opencsw.org Sat Jan 24 22:37:37 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 24 Jan 2009 22:37:37 +0100 Subject: [csw-maintainers] Design decision: NFS-Sharing against OS-specific branches Message-ID: <62A15A05-A76C-4A51-8AC5-720AD7B8C86B@opencsw.org> Hi, I am currently inspecting some packages to be renewed and some like lsof have binaries for all os releases in it: As this is of course necessary for NFS-sharing it makes different directories in the mirror like redundant. What is the way to go here? Include all in one package if feasible and keep directories for the difficult ones? Best regards -- Dago From william at wbonnet.net Sun Jan 25 11:09:49 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 11:09:49 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <497C3A6D.9040403@wbonnet.net> Hi Dagobert > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > Thanks :) I would like to put online the text i've written about events, but i cannot modify the page. I have the following permission error : Oooops! Sorry, you can not edit this page. Only members of this site, site administrators and perhaps selected moderators are allowed to. Anyone knows what can i do ? thanks in advance cheers ps: i used a wrong email address to send this email, i resend it, you can delete it from moderation queue. Sorry ... :) -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Sun Jan 25 11:15:35 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 25 Jan 2009 11:15:35 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497C3A6D.9040403@wbonnet.net> References: <497C3A6D.9040403@wbonnet.net> Message-ID: <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> On Sun, Jan 25, 2009 at 11:09 AM, William Bonnet wrote: > I would like to put online the text i've written about events, but i > cannot modify the page. I have the following permission error : > > > Oooops! > > Sorry, you can not edit this page. Only members of this site, site > administrators and perhaps selected moderators are allowed to. > > > Anyone knows what can i do ? To edit the wiki you need a wikidot.com account and then join the OpenCSW wiki. I can send you an invite to ease things for you. -- /peter From korpela at ssl.berkeley.edu Fri Jan 23 00:27:53 2009 From: korpela at ssl.berkeley.edu (Eric J Korpela) Date: Thu, 22 Jan 2009 15:27:53 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: That should probably work. Some packages may need some fixes to their build scripts to bring them in line. Some stuff developed on Linux assumes that they are there, or that a library isn't there if the .la file isn't, but IMHO, that's a bug anyway. It also can make static linking a pain, but that's rarely required when using a package manager. Eric From ggunselm at emporia.edu Sat Jan 24 02:46:36 2009 From: ggunselm at emporia.edu (Glen Gunselman) Date: Fri, 23 Jan 2009 19:46:36 -0600 Subject: [csw-maintainers] [csw-users] lsof In-Reply-To: <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220929q3251d481ye4cf0ddbe57314e8@mail.gmail.com> <20090122223502.GA2836@keevey> <4978E284.CC54.005D.3@emporia.edu> <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> Message-ID: <497A1E9C.CC54.005D.3@emporia.edu> I looked over the current stuff available for testing and I'm not currently using any of it in a Solaris environment. I'm looking for a current lsof for a Solaris 10 system (update 5). Thanks and have a good weekend, Glen Gunselman Systems Software Specialist TCS Emporia State University >>> Dagobert Michelsen 1/23/2009 9:18 AM >>> Hi Glen, Am 23.01.2009 um 04:17 schrieb Glen Gunselman: Are there any plans to update lsof? It looks like an update has been requested several times in the past. Plans, yes. We don't currently have Solaris 9 build machines in the farm. I look into it. BTW: If I recall correctly you offered to help in november. We are desperately needing testers who try out stuff in testing at and give feedback. It would be a great help if you used the new packages on some of your machines. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From wbonnet at opencsw.org Sun Jan 25 00:27:17 2009 From: wbonnet at opencsw.org (William Bonnet) Date: Sun, 25 Jan 2009 00:27:17 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Message-ID: <497BA3D5.8060306@opencsw.org> Hi Dagobert > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > Thanks :) I would like to put online the text i've written about events, but i cannot modify the page. I have the following permission error : Oooops! Sorry, you can not edit this page. Only members of this site, site administrators and perhaps selected moderators are allowed to. Anyone knows what can i do ? thanks in advance cheers -- William Bonnet http://www.wbonnet.net http://www.opencsw.org Community SoftWare for Solaris From william at wbonnet.net Sun Jan 25 12:29:10 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 12:29:10 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> References: <497C3A6D.9040403@wbonnet.net> <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> Message-ID: <497C4D06.3060102@wbonnet.net> Hi Peter > To edit the wiki you need a wikidot.com account and then join the > OpenCSW wiki. I can send you an invite to ease things for you. > It works thanks :) I forgot one step. I only had an account. Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Sun Jan 25 19:44:21 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 19:44:21 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Message-ID: <497CB305.8050807@wbonnet.net> Hi > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > I have added some details to this page. Comments feedback are welcome. Does anyone disagree with the fact that first theme should be communication ? Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 26 04:17:40 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 25 Jan 2009 19:17:40 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497CB305.8050807@wbonnet.net> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> Message-ID: <20090126031740.GE22989@bolthole.com> On Sun, Jan 25, 2009 at 07:44:21PM +0100, William Bonnet wrote: > I have added some details to this page. Comments feedback are welcome. > > Does anyone disagree with the fact that first theme should be > communication ? I think it is not focused enough. I think that the way you have currently worded it, includes both "better communication with existing users", and also "better ADVERTISING". I think that each deserves its own full month of focus. From dam at opencsw.org Mon Jan 26 11:06:53 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 26 Jan 2009 11:06:53 +0100 Subject: [csw-maintainers] New server build9x Message-ID: Hi, I finally managed to add the missing Solaris 9 x86 build server: build9x We have now a full set of Solaris 8, 9 and 10 for both sparc and x86. Ben: This time I remembered to add all buildfarm-admins from the start :-) Have fun! -- Dago From william at wbonnet.net Mon Jan 26 12:59:33 2009 From: william at wbonnet.net (William Bonnet) Date: Mon, 26 Jan 2009 12:59:33 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090126031740.GE22989@bolthole.com> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> Message-ID: <497DA5A5.1000407@wbonnet.net> Hi > I think it is not focused enough. > > I think that the way you have currently worded it, includes both > "better communication with existing users", and also > "better ADVERTISING". > That's right My question was "Are you ok that first theme is communication ? If no, please let us know, if yes let's start writing detailled content before 1st of Feb". I'll start to work and write on this tomorrow night. > I think that each deserves its own full month of focus. > Surely. It is a large area to be covered for both subject. What i target for first month is to do as much as we can on both subjects. We won't cover everything, and we will have to work on this again. Now we first we have to create the foundation of our communication and advertising, refresh and update some documentation, put content into the new web site, and setup a communication strategy with users. I'll create a wiki page about this tomorrow (today it's a long long day at office...) Cheers, W. > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 26 16:59:35 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 26 Jan 2009 07:59:35 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497DA5A5.1000407@wbonnet.net> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> Message-ID: <20090126155935.GF84666@bolthole.com> On Mon, Jan 26, 2009 at 12:59:33PM +0100, William Bonnet wrote: > Hi *wave* > > I think that each deserves its own full month of focus. > > > Surely. It is a large area to be covered for both subject. What i target > for first month is to do as much as we can on both subjects. We won't > cover everything, and we will have to work on this again. Now we first > we have to create the foundation of our communication and advertising, > refresh and update some documentation, .... I think that once we have an advertising blitz, it would be best for the new people to see our site, etc. at its best. So it would be the most strategic, to first improve our "user communication", *before* doing all the advertising. So I would like to propose the first month be "communication", possibly overlapping with *planning* advertising, and then the month after that be when we actually do the advertising. From pfelecan at opencsw.org Mon Jan 26 17:54:45 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Mon, 26 Jan 2009 17:54:45 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090126155935.GF84666@bolthole.com> (Philip Brown's message of "Mon\, 26 Jan 2009 07\:59\:35 -0800") References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> <20090126155935.GF84666@bolthole.com> Message-ID: Philip Brown writes: > On Mon, Jan 26, 2009 at 12:59:33PM +0100, William Bonnet wrote: >> > I think that each deserves its own full month of focus. >> > >> Surely. It is a large area to be covered for both subject. What i target >> for first month is to do as much as we can on both subjects. We won't >> cover everything, and we will have to work on this again. Now we first >> we have to create the foundation of our communication and advertising, >> refresh and update some documentation, .... > > I think that once we have an advertising blitz, it would be best for the > new people to see our site, etc. at its best. So it would be the most > strategic, to first improve our "user communication", *before* doing all > the advertising. So I would like to propose the first month be > "communication", possibly overlapping with *planning* advertising, and then > the month after that be when we actually do the advertising. It seems to me most reasonable to do it in that order, i.e., user communication and then advertising. But don't forget to update the thematics page accordingly. -- Peter From william at wbonnet.net Tue Jan 27 09:55:32 2009 From: william at wbonnet.net (William Bonnet) Date: Tue, 27 Jan 2009 09:55:32 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> <20090126155935.GF84666@bolthole.com> Message-ID: <497ECC04.2090603@wbonnet.net> Hi guys >> I think that once we have an advertising blitz, it would be best for the >> new people to see our site, etc. at its best. So it would be the most >> strategic, to first improve our "user communication", *before* doing all >> the advertising. So I would like to propose the first month be >> "communication", possibly overlapping with *planning* advertising, and then >> the month after that be when we actually do the advertising. >> > > It seems to me most reasonable to do it in that order, i.e., user > communication and then advertising. But don't forget to update the > thematics page accordingly. > That's the good way to do it for sure :) I'll create a new page linked from thematics events for detailed description of the first event. What i had in my mind was to work on materials we need during this month, then at the end of month start massive communication. Well it's time for my first meeting of the day ;) more to come later. cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From pfelecan at opencsw.org Tue Jan 27 17:51:16 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 27 Jan 2009 17:51:16 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues Message-ID: Here is a story which shows an additional reason to have a better "communication": I'm a CSW maintainer since a few years. Not really active since some time but considering to submit some updated packages. In the "old world" I copied the packages to /export/newpkgs and sent a mail to Phil. In the "new world", on the only relevant page of our site, http://www.opencsw.org/standards/pkg-walkthrough, I read that I must "copy your finished packages to /home/newpkgs on www.opencsw.org". Being connected on login.opencsw.org I try to scp the package but I'm asked for a password. What password? I supplied many time my public key and I'm expecting to be authorized to release a package. I searched also the maintainers mailing list. Phil explains how to submit a package. But there is not a word about authorization. The only reference is a request by another maintainer in the same situation as mine. Again, no reference to an authorization procedure. Is there a kind soul who can explain the whole process, with an example, please? Maybe that before addressing the issue of communication toward the users we should enhance the one destined to the maintainers. -- Peter From phil at bolthole.com Tue Jan 27 20:20:34 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 27 Jan 2009 11:20:34 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: Message-ID: <20090127192034.GA54002@bolthole.com> On Tue, Jan 27, 2009 at 05:51:16PM +0100, Peter FELECAN wrote: >... > ... In the "new world", on the only relevant page of our site, > http://www.opencsw.org/standards/pkg-walkthrough, I read that I must > "copy your finished packages to /home/newpkgs on www.opencsw.org". > > Being connected on login.opencsw.org I try to scp the package but I'm > asked for a password. What password? I supplied many time my public key > and I'm expecting to be authorized to release a package. > ... > Is there a kind soul who can explain the whole process, with an example, > please? > It seems that the only "piece of the puzzle" you are missing from the process, is an easy way to copy a package from build machines, to www. Unfortunately, older maintainer accounts, do not have the scp set up to be seamless by default. But, since you have full login access to both machines already, you yourself have the power to "fix" this, as on any other unix machine that you scp to and from. if you scp the .ssh/id_dsa.pub from login, back to your normal (desktop?) machine, then copy it from there, over to www, and then append it to the authorized_keys file there, then you will have just given yourself access to scp directly between login.bo.opencsw.org, and www.opencsw.org I have also updated the web page with this information. From pfelecan at opencsw.org Tue Jan 27 21:41:57 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 27 Jan 2009 21:41:57 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090127192034.GA54002@bolthole.com> (Philip Brown's message of "Tue\, 27 Jan 2009 11\:20\:34 -0800") References: <20090127192034.GA54002@bolthole.com> Message-ID: Philip Brown writes: > On Tue, Jan 27, 2009 at 05:51:16PM +0100, Peter FELECAN wrote: >>... >> ... In the "new world", on the only relevant page of our site, >> http://www.opencsw.org/standards/pkg-walkthrough, I read that I must >> "copy your finished packages to /home/newpkgs on www.opencsw.org". >> >> Being connected on login.opencsw.org I try to scp the package but I'm >> asked for a password. What password? I supplied many time my public key >> and I'm expecting to be authorized to release a package. >> ... >> Is there a kind soul who can explain the whole process, with an example, >> please? >> > > It seems that the only "piece of the puzzle" you are missing from the > process, is an easy way to copy a package from build machines, to www. Indeed. > Unfortunately, older maintainer accounts, do not have the scp set up to be > seamless by default. Older? What defines "older"? > But, since you have full login access to both machines already, you > yourself have the power to "fix" this, as on any other unix machine that > you scp to and from. > > if you scp the .ssh/id_dsa.pub from login, back to your normal > (desktop?) machine, then copy it from there, over to www, and then > append it to the authorized_keys file there, then you will have just given > yourself access to scp directly between login.bo.opencsw.org, and > www.opencsw.org Trying to connect to pfelecan at www.opencsw.org requires a password that I have not. Consequently, I cannot fix it myself. BTW, I cannot see the changes to the documentation? Can you give me a reference URI? -- Peter From phil at bolthole.com Tue Jan 27 22:37:48 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 27 Jan 2009 13:37:48 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: <20090127192034.GA54002@bolthole.com> Message-ID: <20090127213748.GA13932@bolthole.com> On Tue, Jan 27, 2009 at 09:41:57PM +0100, Peter FELECAN wrote: > > > Unfortunately, older maintainer accounts, do not have the scp set up to be > > seamless by default. > > Older? What defines "older"? older than two weeks ago. so, "accounts created before jan 2009" > > if you scp the .ssh/id_dsa.pub from login, back to your normal > > (desktop?) machine, then copy it from there, over to www, and then > > append it to the authorized_keys file there, then you will have just given > > yourself access to scp directly between login.bo.opencsw.org, and > > www.opencsw.org > > Trying to connect to pfelecan at www.opencsw.org requires a password that I > have not. Consequently, I cannot fix it myself. Hmmm...... i tried tweaking one thing on www. please try again. also, please note that it is expecting ssh access from the host that has your public key on it which ends in: 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan From harpchad at opencsw.org Tue Jan 27 22:44:44 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 27 Jan 2009 15:44:44 -0600 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) Message-ID: <497F804C.7080503@opencsw.org> I want to propose and get feedback on the following patch to gar. I'd like to add a configuration variable called ISAEXEC_EXCLUDE_FILES. The purpose of this variable would be to define items that should not be moved to a bin/$(ISA) directory and wrapped with isaexec. Examples of executables that you may not want to wrap: shell & other interpreted language scripts symbolic links (i.e. view->vim, no need to wrap the view symlink) executables that wouldn't benefit from 64bit support I've implemented this in the attached patch by adding another flag to pathfilter (-n) and calling it with the excluded files from gar.pkg.mk I've done some testing and it works as I need it to. Hopefully I haven't missed a simpler way to do this. --chad -------------- next part -------------- A non-text attachment was scrubbed... Name: isaexec_exclude.patch Type: text/x-patch Size: 2290 bytes Desc: not available URL: From dam at opencsw.org Tue Jan 27 22:57:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 27 Jan 2009 22:57:27 +0100 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <497F804C.7080503@opencsw.org> References: <497F804C.7080503@opencsw.org> Message-ID: <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> Hi Chad, Am 27.01.2009 um 22:44 schrieb Chad Harp: > I want to propose and get feedback on the following patch to gar. > > I'd like to add a configuration variable called > ISAEXEC_EXCLUDE_FILES. The purpose of this variable would be to > define items that should not be moved to a bin/$(ISA) directory and > wrapped with isaexec. > > Examples of executables that you may not want to wrap: > shell & other interpreted language scripts > symbolic links (i.e. view->vim, no need to wrap the view symlink) > executables that wouldn't benefit from 64bit support This sounds reasonable. > I've implemented this in the attached patch by adding another flag > to pathfilter (-n) and calling it with the excluded files from > gar.pkg.mk > I've done some testing and it works as I need it to. Hopefully I > haven't missed a simpler way to do this. Well, it should work but I think you have missed a simpler way to do this ;-) The list of files to be isaexec'ed is defined in ISAEXEC_FILES in gar.mk, which adds one option per isaexec-file to pathfilter. Taking them out at pathfilter after explicitly passing them to pathfilter looks wrong to me. It is easier to add something like ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. I'll take a look tomorrow. Best regards -- Dago From harpchad at opencsw.org Tue Jan 27 23:03:13 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 27 Jan 2009 16:03:13 -0600 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> References: <497F804C.7080503@opencsw.org> <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> Message-ID: <497F84A1.9@opencsw.org> Dagobert Michelsen wrote: > > Well, it should work but I think you have missed a simpler way to do > this ;-) > The list of files to be isaexec'ed is defined in ISAEXEC_FILES in > gar.mk, which > adds one option per isaexec-file to pathfilter. Taking them out at > pathfilter > after explicitly passing them to pathfilter looks wrong to me. It is > easier > to add something like > ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) > where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. > I'll take a look tomorrow. That does sound simpler, I based it on the existing -x functionality for PKGFILES_EXCLUDE, but I think stripping it prior to calling pathfilter would have the same result. From pfelecan at opencsw.org Wed Jan 28 09:37:21 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 28 Jan 2009 09:37:21 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090127213748.GA13932@bolthole.com> (Philip Brown's message of "Tue\, 27 Jan 2009 13\:37\:48 -0800") References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> Message-ID: Philip Brown writes: > On Tue, Jan 27, 2009 at 09:41:57PM +0100, Peter FELECAN wrote: >> >> > Unfortunately, older maintainer accounts, do not have the scp set up to be >> > seamless by default. >> >> Older? What defines "older"? > > older than two weeks ago. so, "accounts created before jan 2009" Never saw a discussion about this kind of stuff on the maintainers mailing list. BTW, it means that almost everybody has this issue. >> > if you scp the .ssh/id_dsa.pub from login, back to your normal >> > (desktop?) machine, then copy it from there, over to www, and then >> > append it to the authorized_keys file there, then you will have just given >> > yourself access to scp directly between login.bo.opencsw.org, and >> > www.opencsw.org >> >> Trying to connect to pfelecan at www.opencsw.org requires a password that I >> have not. Consequently, I cannot fix it myself. > > Hmmm...... > i tried tweaking one thing on www. please try again. ssh pfelecan at www.opencsw.org Password: Received disconnect from 147.87.98.73: 2: Too many authentication failures for pfelecan > also, please note that it is expecting ssh access from the host that has > your public key on it which ends in: > > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan That's the case. -- Peter From bonivart at opencsw.org Wed Jan 28 09:47:27 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 28 Jan 2009 09:47:27 +0100 Subject: [csw-maintainers] /testing dhcp 4.1.0 Message-ID: <625385e30901280047j5823f0dfkc289fe0997ce3310@mail.gmail.com> I would like some help testing the new ISC DHCP 4.1.0 packages. They use cswclassutils for configuration file handling and SMF support. http://mirror.opencsw.org/testing.html dhcp-4.1.0,REV=2009.01.27-SunOS5.8-sparc-CSW.pkg.gz dhcp-4.1.0,REV=2009.01.27-SunOS5.8-i386-CSW.pkg.gz dhcp_devel-4.1.0,REV=2009.01.27-SunOS5.8-sparc-CSW.pkg.gz dhcp_devel-4.1.0,REV=2009.01.27-SunOS5.8-i386-CSW.pkg.gz -- /peter From dam at opencsw.org Wed Jan 28 11:35:00 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 11:35:00 +0100 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <497F84A1.9@opencsw.org> References: <497F804C.7080503@opencsw.org> <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> <497F84A1.9@opencsw.org> Message-ID: <8C85C443-6D93-43A6-9CF9-5534E9B7C71B@opencsw.org> Hi Chad, Am 27.01.2009 um 23:03 schrieb Chad Harp: > Dagobert Michelsen wrote: >> Well, it should work but I think you have missed a simpler way to do >> this ;-) >> The list of files to be isaexec'ed is defined in ISAEXEC_FILES in >> gar.mk, which >> adds one option per isaexec-file to pathfilter. Taking them out at >> pathfilter >> after explicitly passing them to pathfilter looks wrong to me. It is >> easier >> to add something like >> ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) >> where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. >> I'll take a look tomorrow. > > That does sound simpler, I based it on the existing -x functionality > for > PKGFILES_EXCLUDE, but I think stripping it prior to calling pathfilter > would have the same result. I implemented this in r2918. Please test it and see if this fixes your request :-) Best regards -- Dago From dam at opencsw.org Wed Jan 28 13:44:12 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 13:44:12 +0100 Subject: [csw-maintainers] Fwd: [csw-users] HELP - non functioning openssl References: <49805295.6030602@ericsson.com> Message-ID: <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> Hi, FYI on users@ Best regards -- Dago Anfang der weitergeleiteten E-Mail: > Von: Mats Larsson > Datum: 28. Januar 2009 13:41:57 MEZ > An: users at lists.opencsw.org > Kopie: Ove Lundell > Betreff: [csw-users] HELP - non functioning openssl > Antwort an: questions and discussions > > Hi all, > > Latest 'pkg-get -uU' gave me a amongst others a non functioning > openssl. > I'm not even able to do a 'pkg-get -uU' any more: > > # pg -uU > Getting catalog... > ld.so.1: wget: fatal: libssl.so.0.9.8: open failed: No such file or > directory > /usr/bin/pkg-get[34]: 20393 Killed > > So I went to > http://www.ibiblio.org/pub/packages/solaris/opencsw/unstable/sparc/ > 5.8/ > and downloaded > openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg.gz since > libssl.so.0.9.8 live there and did try to pkgadd it instead > > pkgadd -d > ~/downloads/openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc- > CSW.pkg > > # pkgadd -d openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc- > CSW.pkg > ... > > ## Executing checkinstall script. > /var/tmp/dstreAAAIpaW1N/CSWosslrt/install/checkinstall: test: argument > expected > pkgadd: ERROR: checkinstall script did not complete successfully > > Installation of failed. > No changes were made to the system. > > I'm lost. Any help appreciated. > > BR MOL > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users From yann at pleiades.fr.eu.org Wed Jan 28 14:31:28 2009 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Wed, 28 Jan 2009 14:31:28 +0100 Subject: [csw-maintainers] Fwd: [csw-users] HELP - non functioning openssl In-Reply-To: <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> References: <49805295.6030602@ericsson.com> <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> Message-ID: <49805E30.9000006@pleiades.fr.eu.org> For the "test argument expected", I am currently producing a new package fixing this bug. I already received an email about it today: http://www.opencsw.org/mantis/view.php?id=3050 BTW, I didn't catch this bug because I have only a solaris 10 server. Would it be possible to have root access on some solaris 8 server ? It would even nicer to have some automatic script to test package installation (like piuparts on Debian), but that might be not so easy on Solaris. Yann Dagobert Michelsen a ?crit : > Hi, > > FYI on users@ > > Best regards > > -- Dago > > Anfang der weitergeleiteten E-Mail: > >> Von: Mats Larsson >> Datum: 28. Januar 2009 13:41:57 MEZ >> An: users at lists.opencsw.org >> Kopie: Ove Lundell >> Betreff: [csw-users] HELP - non functioning openssl >> Antwort an: questions and discussions >> >> Hi all, >> >> Latest 'pkg-get -uU' gave me a amongst others a non functioning openssl. >> I'm not even able to do a 'pkg-get -uU' any more: >> >> # pg -uU >> Getting catalog... >> ld.so.1: wget: fatal: libssl.so.0.9.8: open failed: No such file or >> directory >> /usr/bin/pkg-get[34]: 20393 Killed >> >> So I went to >> http://www.ibiblio.org/pub/packages/solaris/opencsw/unstable/sparc/5.8/ >> and downloaded >> openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg.gz since >> libssl.so.0.9.8 live there and did try to pkgadd it instead >> >> pkgadd -d >> ~/downloads/openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg >> >> # pkgadd -d openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg >> ... >> >> ## Executing checkinstall script. >> /var/tmp/dstreAAAIpaW1N/CSWosslrt/install/checkinstall: test: argument >> expected >> pkgadd: ERROR: checkinstall script did not complete successfully >> >> Installation of failed. >> No changes were made to the system. >> >> I'm lost. Any help appreciated. >> >> BR MOL >> _______________________________________________ >> users mailing list >> users at lists.opencsw.org >> https://lists.opencsw.org/mailman/listinfo/users > From harpchad at opencsw.org Wed Jan 28 17:27:22 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 10:27:22 -0600 Subject: [csw-maintainers] .la discussion Message-ID: <4980876A.8070806@opencsw.org> There's been discussion, but I'm not sure there's a consensus yet. I've got some .la files that are causing issues. I've seen some requests to have them deleted (on a single file basis) from the build farm, is that how we should handle them for now? Should that e-mail go to the buildfarm list? I suspect there will be less work is we mass relocate them and add them as needed (i.e. there will be fewer requests for adds than deletes). --chad From phil at bolthole.com Wed Jan 28 18:02:51 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:02:51 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <4980876A.8070806@opencsw.org> References: <4980876A.8070806@opencsw.org> Message-ID: <20090128170250.GZ23122@bolthole.com> On Wed, Jan 28, 2009 at 10:27:22AM -0600, Chad Harp wrote: > There's been discussion, but I'm not sure there's a consensus yet. > > I've got some .la files that are causing issues. I've seen some > requests to have them deleted (on a single file basis) from the build > farm, is that how we should handle them for now? Should that e-mail go > to the buildfarm list? you should both email/contact the maintainer, and also the build farm, if you are in a hurry. if you are not in a hurry, then just contact the maintainer. > I suspect there will be less work is we mass relocate them and add them > as needed (i.e. there will be fewer requests for adds than deletes). there are "only" 10 packages with .la files on the build farm. So, it's not THAT much work, I would think. ones that are probably the easiest to fix, are: libsqlite3.la (Michael libgdbm.la (Me) libsasl2.la (Damjan) the notsoseay, are for libiconv and ggettext (both me, unfortunately) From phil at bolthole.com Wed Jan 28 18:05:39 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:05:39 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170250.GZ23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> Message-ID: <20090128170539.GB23122@bolthole.com> On Wed, Jan 28, 2009 at 09:02:51AM -0800, Philip Brown wrote: > libgdbm.la (Me) > ... > the notsoseay, are for libiconv and ggettext (both me, unfortunately) i should mention, that if anyone would LIKE to take over these packages, please speak up! ;-) From phil at bolthole.com Wed Jan 28 18:10:16 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:10:16 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> Message-ID: <20090128171016.GC23122@bolthole.com> On Wed, Jan 28, 2009 at 09:37:21AM +0100, Peter FELECAN wrote: > > also, please note that it is expecting ssh access from the host that has > > your public key on it which ends in: > > > > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan > > That's the case. Errr... it would appear that you have a different public key for external access, on login.bo.opencsw.org, than on www.opencsw.org I'm guessing the www one was a "legacy" one, that is no longer valid for you. Soooo.. i just copied over your login one, to www. you should now be able to access www from outside, AND from login. i think. From harpchad at opencsw.org Wed Jan 28 18:10:47 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:10:47 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170250.GZ23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> Message-ID: <49809197.8050801@opencsw.org> Philip Brown wrote: > you should both email/contact the maintainer, and also the build farm, if > you are in a hurry. > if you are not in a hurry, then just contact the maintainer. The packages are unmaintained. I'll send in buildfarm requests from the ones that are causing me issues. > there are "only" 10 packages with .la files on the build farm. > So, it's not THAT much work, I would think. harpchad at build8s (CSW)$ ls -1 /opt/csw/lib/*.la | wc -l 231 231 .la requests to buildfarm might result in no buildfarm maintainers :) From phil at bolthole.com Wed Jan 28 18:22:25 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:22:25 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <49809197.8050801@opencsw.org> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> Message-ID: <20090128172225.GF23122@bolthole.com> On Wed, Jan 28, 2009 at 11:10:47AM -0600, Chad Harp wrote: > > there are "only" 10 packages with .la files on the build farm. > > So, it's not THAT much work, I would think. > > harpchad at build8s (CSW)$ ls -1 /opt/csw/lib/*.la | wc -l > 231 oh. nuts. I did it on "login", not on "buildxxx" :-} Well, I'd say there are two "clean" ways to handle this. One is less work, and less clean to outside, but clean to US. Other is a lot more work, but clean to everyone. "clean to us": ssh buildX && rm /opt/csw/lib/lib*.la "clean to outside": make a list of all packages that have .la files, and graph em as dependancies, and then start prodding the appropriate people to repackage them starting at "leaf nodes" in the graph. Note: It's no good just doing a one-time repackage. we need to make sure that the maintainers build it "the next time" without .la files too. From harpchad at opencsw.org Wed Jan 28 18:25:46 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:25:46 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128172225.GF23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> Message-ID: <4980951A.2050003@opencsw.org> Philip Brown wrote: > Well, I'd say there are two "clean" ways to handle this. > One is less work, and less clean to outside, but clean to US. > Other is a lot more work, but clean to everyone. > > "clean to us": ssh buildX && rm /opt/csw/lib/lib*.la > > > "clean to outside": > make a list of all packages that have .la files, and graph em as > dependancies, and then start prodding the appropriate people > to repackage them starting at "leaf nodes" in the graph. > > Note: It's no good just doing a one-time repackage. we need to make sure > that the maintainers build it "the next time" without .la files too. Why not do both? The "clean to us" would allow our maintainers to continue building their packages while we take care of the "clean to outside". From phil at bolthole.com Wed Jan 28 18:43:01 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:43:01 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <4980951A.2050003@opencsw.org> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> <4980951A.2050003@opencsw.org> Message-ID: <20090128174301.GG23122@bolthole.com> On Wed, Jan 28, 2009 at 11:25:46AM -0600, Chad Harp wrote: > Philip Brown wrote: > > "clean to outside": > > make a list of all packages that have .la files, and graph em as > > dependancies, and then start prodding the appropriate people > > to repackage them starting at "leaf nodes" in the graph. > > > > Note: It's no good just doing a one-time repackage. we need to make sure > > that the maintainers build it "the next time" without .la files too. > > Why not do both? The "clean to us" would allow our maintainers to > continue building their packages while we take care of the "clean to > outside". you kinda missed the point of "clean to outside". If we are trying to remain "clean to outside", that means that "outside" people will be able to build easily on top of our published packages, without getting TOO messed up with .la missing linkages. The only way that can happen, is if we rebuild packages in a deterministic manner, working from the "leaf nodes" inward. If we just rm all the .la files, then we will effectively be clearing things for random package rebuilds, which will break the "clean to outside" paradigm". From harpchad at opencsw.org Wed Jan 28 18:58:35 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:58:35 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128174301.GG23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> <4980951A.2050003@opencsw.org> <20090128174301.GG23122@bolthole.com> Message-ID: <49809CCB.60600@opencsw.org> Philip Brown wrote: > you kinda missed the point of "clean to outside". > > If we are trying to remain "clean to outside", that means that "outside" > people will be able to build easily on top of our published packages, > without getting TOO messed up with .la missing linkages. > > The only way that can happen, is if we rebuild packages in a deterministic > manner, working from the "leaf nodes" inward. > > If we just rm all the .la files, then we will effectively be clearing > things for random package rebuilds, which will break the "clean to outside" > paradigm". I understand the concept, but it will likely take some time to get all of the packages cleaned up (and find maintainers for the ones that need them). We don't have a clean build environment in either place today. I'm proposing we go ahead with "clean to inside" because it will facilitate "clean to outside". While it won't make it immediately possible to have a clean build environment on the outside, it will allow the active maintainers to update their packages where they otherwise might not be able to because of .la dependencies (at the same time removing .la files from their packages). While that's going on we try to push for updates on the remaining packages (starting with the leaf nodes), eventually cleaning the "outside" as well. From pfelecan at opencsw.org Wed Jan 28 19:26:23 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 28 Jan 2009 19:26:23 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090128171016.GC23122@bolthole.com> (Philip Brown's message of "Wed\, 28 Jan 2009 09\:10\:16 -0800") References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> <20090128171016.GC23122@bolthole.com> Message-ID: Philip Brown writes: > On Wed, Jan 28, 2009 at 09:37:21AM +0100, Peter FELECAN wrote: >> > also, please note that it is expecting ssh access from the host that has >> > your public key on it which ends in: >> > >> > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan >> >> That's the case. > > Errr... it would appear that you have a different public key for external > access, on login.bo.opencsw.org, than on www.opencsw.org > > I'm guessing the www one was a "legacy" one, that is no longer valid for > you. > > Soooo.. i just copied over your login one, to www. > you should now be able to access www from outside, AND from login. > i think. Now it works. Thank you. -- Peter From dam at opencsw.org Wed Jan 28 21:39:45 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 21:39:45 +0100 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170539.GB23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <20090128170539.GB23122@bolthole.com> Message-ID: <56E111E6-A022-4839-90A2-57D275FBA4DB@opencsw.org> Hi Phil, Am 28.01.2009 um 18:05 schrieb Philip Brown: > On Wed, Jan 28, 2009 at 09:02:51AM -0800, Philip Brown wrote: >> libgdbm.la (Me) >> ... >> the notsoseay, are for libiconv and ggettext (both me, unfortunately) > > i should mention, that if anyone would LIKE to take over these > packages, > please speak up! ;-) Please send me your buildscripts so I can add them to the GAR for reference if volunteers pop up. For libiconv I have a 95% build recipe in GAR. Best regards -- Dago From dam at opencsw.org Wed Jan 28 22:18:49 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:18:49 +0100 Subject: [csw-maintainers] More thematics topics Message-ID: Hi, I have some proposals for thematics: (1) Tiering: Identify tier 1/2/3 packages and find people who adopt them (2) File bugs for packages containing .la-files (3) Go 64: Make sure libraries are always 32/64 bit for sparc / x86 (4) CPAN Coverage: Compare the OpenCSW offered modules against CPAN availability Timing: (1) April, with priority on tier 1 packages (2) Should be before Bug Hunting in May (3) Should also be before Bug Hunting as missing 64 bit libs could be considered a bug ;-) (4) Quite optional, end of year? Sounds reasonable? Best regards -- Dago From william at wbonnet.net Wed Jan 28 22:24:27 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:24:27 +0100 Subject: [csw-maintainers] Package creation problem Message-ID: <4980CD0B.3000609@wbonnet.net> Hi all I am currently facing a problem that goes far beyond my GAR knowledge... I started to move my old java libs package, and update them by the way, but i have a problem at package creation. In the Makefile i use a custom install step in which i create symlinks to jar files and licence. This links do exists in my install dir, and they do exists in the prototype files that are generated automatically. BUT they are not in the package once build. Anyone ( looking towards Dago direction... ) has an idea of what i did wrong ? Here is my custom-install steps. Everything is commited to gar in the beanutils folder. Thanks in advance cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:27:48 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:27:48 +0100 Subject: [csw-maintainers] Use of java folder Message-ID: <4980CDD4.5080106@wbonnet.net> Hi, Still talking about the beanutils package... but different subject. Beautils package is Apache Jakarta Commons Beanutils. A java lib. I have several libs to add to gar, and i was planning to add them to GAR under the java folder (just like there is xfce, x11 and cpan folders). A few weeks ago, Dago, you told me you were planning to put jdk packages under *java* , but i noticed they are the root of pkg. Do you still plan to do it or can i use it ? I you use it, is it a problem if i call my folder *javalibs* instead ? cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:30:30 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:30:30 +0100 Subject: [csw-maintainers] More thematics topics In-Reply-To: References: Message-ID: <4980CE76.3010601@wbonnet.net> Hi Dagobert > Sounds reasonable? > Sounds good to me. If we have enough volunteers it is not a problem to work on several theme at a time. Cheers, W. /me working on first theme... i'll publish some notes this friday or early in the week end -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 28 22:33:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:33:02 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <4980CD0B.3000609@wbonnet.net> References: <4980CD0B.3000609@wbonnet.net> Message-ID: Hi William, Am 28.01.2009 um 22:24 schrieb William Bonnet: > Here is my custom-install steps. Everything is commited to gar in the > beanutils folder. Please also commit gar/categories/java/category.mk ;-) Thanks! -- Dago From dam at opencsw.org Wed Jan 28 22:37:28 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:37:28 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <4980CDD4.5080106@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> Message-ID: <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> Hi William, Am 28.01.2009 um 22:27 schrieb William Bonnet: > Still talking about the beanutils package... but different subject. > > Beautils package is Apache Jakarta Commons Beanutils. A java lib. I > have > several libs to add to gar, and i was planning to add them to GAR > under > the java folder (just like there is xfce, x11 and cpan folders). A few > weeks ago, Dago, you told me you were planning to put jdk packages > under > *java* , but i noticed they are the root of pkg. Do you still plan > to do > it or can i use it ? I am still negatioating with Suns legal department. For reference I installed jdk6 / jre6 on build8s / build8x. I am very well aware that this is against the release-first policy, but as it does not have any side-effects on any other software I hope you'll forgive me ;-) > I you use it, is it a problem if i call my folder > *javalibs* instead ? javalibs/ or java/, both ok for me. Are you planning to do GAR magic in the category? If no, it is just a grouping. Best regards -- Dago From dam at opencsw.org Wed Jan 28 22:55:58 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:55:58 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: References: <4980CD0B.3000609@wbonnet.net> Message-ID: <8D4A6033-DAE1-477A-B486-A17B6DC7D0C3@opencsw.org> Hi William, Am 28.01.2009 um 22:33 schrieb Dagobert Michelsen: > Am 28.01.2009 um 22:24 schrieb William Bonnet: >> Here is my custom-install steps. Everything is commited to gar in the >> beanutils folder. > > Please also commit gar/categories/java/category.mk ;-) files/CSWajcbeanutils.gspec is missing also... Best regards -- Dago From william at wbonnet.net Wed Jan 28 22:56:14 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:56:14 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: References: <4980CD0B.3000609@wbonnet.net> Message-ID: <4980D47E.4050008@wbonnet.net> Hi Dago > Please also commit gar/categories/java/category.mk ;-) > > ooops :) done -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:59:06 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:59:06 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> References: <4980CDD4.5080106@wbonnet.net> <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> Message-ID: <4980D52A.3070206@wbonnet.net> Hi Dago > javalibs/ or java/, both ok for me. Are you planning to do GAR magic > in the > category? If no, it is just a grouping. > It is just a grouping. Category will be used to defines frequently used URL and regexp for uwatch (apache.org stuff etc.) I propose to use java so far, i think there is yet no special need to create too much extra dir. I'll can move libs to another later when we will have more packages. are you ok guys ? cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 28 23:08:49 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 23:08:49 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <4980CD0B.3000609@wbonnet.net> References: <4980CD0B.3000609@wbonnet.net> Message-ID: <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> Hi William, Am 28.01.2009 um 22:24 schrieb William Bonnet: > In the Makefile i use a custom install step in which i create symlinks > to jar files and licence. This links do exists in my install dir, and > they do exists in the prototype files that are generated > automatically. > BUT they are not in the package once build. You mean in root/? That is normal, as links are generated during pkgadd. Have you tried adding the package? I guess the link is there :-) Best regards -- Dago From william at wbonnet.net Wed Jan 28 23:18:29 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 23:18:29 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> References: <4980CD0B.3000609@wbonnet.net> <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> Message-ID: <4980D9B5.2040109@wbonnet.net> Dagobert Michelsen wrote: > Hi William, > > Am 28.01.2009 um 22:24 schrieb William Bonnet: > >> In the Makefile i use a custom install step in which i create symlinks >> to jar files and licence. This links do exists in my install dir, and >> they do exists in the prototype files that are generated >> automatically. >> BUT they are not in the package once build. >> > > You mean in root/? That is normal, as links are generated during pkgadd. > Have you tried adding the package? I guess the link is there :-) > That's right :) Stupid me... i did not installed it but used pkgtrans to extract its content and i was expecting it to create the symlinks :( It's time to go to bed :D Thanks Dago, sorry for the noise cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Thu Jan 29 00:22:11 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 29 Jan 2009 00:22:11 +0100 Subject: [csw-maintainers] Licence file handling proposal Message-ID: <4980E8A3.1090305@wbonnet.net> Hi Tonight i talk about licenses with Trygve, and a need for a shared folder is here. After gathering our ideas, here is a first proposal for discussion. 1/ Creation of a "License package". This package will contains a list of files, each file is a licence text. In both full version, and short version (for pkgadd). Like the ca-certificate package, it is a reference datapackage that will be updated upon need. The files are stored under /opt/csw/share/licences. So as an example we will have the following layout : |-- opt `-- csw `-- share `-- licences |-- Apache_License_2.0_full_text.txt |-- Apache_License_2.0_desc.txt |-- GPL_2.0_full_text.txt |-- GPL_2.0_desc.txt |-- GPL_3.0_full_text.txt `-- GPL_3.0_desc.txt 2/ Use reference to theses files from installed packages (when applicable), and create and entry under /opt/csw/share/licences for each package For instance package foo which is released under GPL v2 will create the following entry |-- opt `-- csw `-- share `-- licences `-- foo `-- GPL_V2.0.txt -> /opt/csw/share/licenses/GPL_2.0_full_text.txt I think it is better to use the license name instead of license.txt for the symlink. So the user know immediately which license it is. Most of software are released under a single license, but for some packages it will be possible to create several link under the /opt/csw/share/license/ directory. If need a small readme.txt can explain that the software is released under several licenses. 3/ In the gspec file use a reference to the short "descriptive version" of the license. Doing this will reduce the output /garbage/ when installing a list of software under gpl. We do have a constraint to distribute the license with the package. If linking it to a license text is not enough (which is my guess). This will still be done as actually. Just keep the license.txt where they are actually, and for convenience use the symlinks and the short description. The short description can be like this : This software is distributed under the GNU General Public Licence V2 as published by the Free Software Foundation. See the file /opt/csw/share/licences/foo/GPL_V2.0.txt for the conditions under which this software is made available. What about this ? Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From korpela at opencsw.org Thu Jan 29 04:26:22 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Wed, 28 Jan 2009 19:26:22 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem Message-ID: I'm trying to install packages to test a build on my local machine (sparc Solaris 10) I installed pkg-get 4.0 2008.12.15 For example, one package dependency is mesalibs. Attempting to install it tells me that CSWcommon is not up to date. Attempting to update CSWcommon tells me that I have the current version installed. Updating the catalogs with -U doesn't help I've tried uninstalling all CSW packages and reinstalling pkg-get to no avail. -bash-3.00# pkg-get -i mesalibs No existing install of CSWmesa found. Installing... Pre-existing local file mesalibs-7.2,REV=2008.10.19-SunOS5.8-sparc-CSW.pkg.gz matches checksum Keeping existing file Analysing special files... Error: dependancy common (CSWcommon) not up to date Call pkg-get again in 'upgrade all' mode eg: '/opt/csw/bin/pkg-get upgrade' This will then upgrade all packages cleanly ERROR: could not install required dependancies for CSWmesa Once dependancies are up to date, call /opt/csw/bin/pkg-get -i mesalibs to (re)install -bash-3.00# pkg-get -u common No worries... you already have version 1.4.6,REV=2008.04.28 of common If you doubt this message, run 'pkg-get -U', then run 'pkg-get upgrade common' From Murray.Jensen at csiro.au Thu Jan 29 05:32:12 2009 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Thu, 29 Jan 2009 15:32:12 +1100 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: Your message of "Thu, 29 Jan 2009 14:26:22 +1100" Message-ID: <3226.1233203532@gerd> On Thu, 29 Jan 2009 14:26:22 +1100, Eric J Korpela writes: >... >Analysing special files... >Error: dependancy common (CSWcommon) not up to date >Call pkg-get again in 'upgrade all' mode >eg: '/opt/csw/bin/pkg-get upgrade' >This will then upgrade all packages cleanly >... So did you try running '/opt/csw/bin/pkg-get upgrade' ?? Cheers! Murray... -- Murray Jensen, CSIRO Materials Science and Engineering Phone: +61 3 9545 2075 Private Bag 33, Clayton South 3169, Australia Fax: +61 3 9544 1128 Internet: Murray.Jensen at csiro.au To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference. The information contained in this e-mail may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this e-mail in error, please delete it immediately and notify Murray Jensen on +61 3 9545 2075. Thank you. From phil at bolthole.com Thu Jan 29 13:18:02 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 04:18:02 -0800 Subject: [csw-maintainers] Licence file handling proposal In-Reply-To: <4980E8A3.1090305@wbonnet.net> References: <4980E8A3.1090305@wbonnet.net> Message-ID: <20090129121802.GC67198@bolthole.com> On Thu, Jan 29, 2009 at 12:22:11AM +0100, William Bonnet wrote: > |-- opt > `-- csw > `-- share > `-- licences > |-- Apache_License_2.0_full_text.txt > |-- Apache_License_2.0_desc.txt > |-- GPL_2.0_full_text.txt > |-- GPL_2.0_desc.txt > |-- GPL_3.0_full_text.txt > `-- GPL_3.0_desc.txt > > 2/ Use reference to theses files from installed packages (when > applicable), and create and entry under /opt/csw/share/licences for each > package for MOST of our packages, this is NOT applicable. the license file MUST be shipped with the package, for GPL'd packages, i believe. > Doing this will reduce the output /garbage/ when installing a list of > software under gpl. well, a common location for this stuff is not what fixes that issue. In contrast, the following bit does: > The short description can be like this : > > This software is distributed under the GNU General Public Licence V2 as published > by the Free Software Foundation. See the file /opt/csw/share/licences/foo/GPL_V2.0.txt > for the conditions under which this software is made available. This was already agreed upon (having the "i copyright" file say "go read this file here") and there are already packages that do this. From phil at bolthole.com Thu Jan 29 13:21:21 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 04:21:21 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: References: Message-ID: <20090129122121.GD67198@bolthole.com> Please send me, in private, output from pkg-get -c From bonivart at opencsw.org Thu Jan 29 17:49:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 29 Jan 2009 17:49:42 +0100 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site Message-ID: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> I was thinking about updating phpMyAdmin and happened to notice a bug in the display script for files: http://www.opencsw.org/search/phpmyadmin. Note that the true BASEDIR used is not included in the paths shown there, it's instead replaced by /opt/csw. I'm pretty sure I have reported this back in the Blastwave days and they show it correctly but somehow it's still wrong here. The other thing is that I vaguely remember that files shouldn't be dumped into /opt/csw/apache2/share/htdocs any more to be more web server neutral. But what was the new location? /var/opt/csw/www? -- /peter From skayser at opencsw.org Thu Jan 29 18:04:12 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 29 Jan 2009 18:04:12 +0100 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site In-Reply-To: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> References: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> Message-ID: <4981E18C.5040509@opencsw.org> Peter Bonivart wrote: > The other thing is that I vaguely remember that files shouldn't be > dumped into /opt/csw/apache2/share/htdocs any more to be more web > server neutral. But what was the new location? /var/opt/csw/www? According to http://opencsw.org/standards/layout: /opt/csw/share/www "pure php" and other arch-neutral web packages should deploy to here, for similar reasons to the java location. (One reason being that we dont want to limit the users' choice of web server if we dont have to). If there is a particular reason why the app doesnt belong under "share", though, perhaps /var/opt/csw/share/www or similar would be appropriate. Sebastian From korpela at opencsw.org Thu Jan 29 18:27:55 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 29 Jan 2009 09:27:55 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: <3226.1233203532@gerd> References: <3226.1233203532@gerd> Message-ID: > So did you try running '/opt/csw/bin/pkg-get upgrade' ?? Cheers! Yep. The upgrade fails on every package, because CSWcommon is supposedly out of date. Eric From phil at bolthole.com Thu Jan 29 19:50:31 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 10:50:31 -0800 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site In-Reply-To: <4981E18C.5040509@opencsw.org> References: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> <4981E18C.5040509@opencsw.org> Message-ID: <20090129185030.GA42131@bolthole.com> On Thu, Jan 29, 2009 at 06:04:12PM +0100, Sebastian Kayser wrote: > According to http://opencsw.org/standards/layout: > > /opt/csw/share/www "pure php" and other arch-neutral web packages should > deploy to here, for similar reasons to the java location. (One reason > being that we dont want to limit the users' choice of web server if we > dont have to). If there is a particular reason why the app doesnt belong > under "share", though "a particular reason" being, "if the app writes to its directories", since /opt/csw/share should be read-only. From harpchad at opencsw.org Thu Jan 29 23:22:08 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 29 Jan 2009 16:22:08 -0600 Subject: [csw-maintainers] vim/gvim 7.2.93 available in testing Message-ID: <49822C10.3090009@opencsw.org> Changes: - Update to patch level 093 - vim now has 64-bit binaries (gvim won't until gtk2 does) From dam at opencsw.org Fri Jan 30 17:04:55 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:04:55 +0100 Subject: [csw-maintainers] General package update on the buildfarm Message-ID: Hi, there has been a request for package installation where I must update all dependencies. Please be patient while I run a full upgrade of CSW packages on all build servers. Thanks! -- Dago From phil at bolthole.com Fri Jan 30 17:19:18 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 08:19:18 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: <4980CDD4.5080106@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> Message-ID: <20090130161918.GB72531@bolthole.com> On Wed, Jan 28, 2009 at 10:27:48PM +0100, William Bonnet wrote: > Hi, > > Still talking about the beanutils package... but different subject. > > Beautils package is Apache Jakarta Commons Beanutils. A java lib. I have > several libs to add to gar, and i was planning to add them to GAR under > the java folder (just like there is xfce, x11 and cpan folders). A few > weeks ago, Dago, you told me you were planning to put jdk packages under > *java* , but i noticed they are the root of pkg. Do you still plan to do > it or can i use it ? I you use it, is it a problem if i call my folder > *javalibs* instead ? I think it's best to use full path names when you're talking about this stuff From dam at opencsw.org Fri Jan 30 17:27:34 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:27:34 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <20090130161918.GB72531@bolthole.com> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> Message-ID: Hi, Am 30.01.2009 um 17:19 schrieb Philip Brown: > On Wed, Jan 28, 2009 at 10:27:48PM +0100, William Bonnet wrote: >> Still talking about the beanutils package... but different subject. >> >> Beautils package is Apache Jakarta Commons Beanutils. A java lib. I >> have >> several libs to add to gar, and i was planning to add them to GAR >> under >> the java folder (just like there is xfce, x11 and cpan folders). A >> few >> weeks ago, Dago, you told me you were planning to put jdk packages >> under >> *java* , but i noticed they are the root of pkg. Do you still plan >> to do >> it or can i use it ? I you use it, is it a problem if i call my >> folder >> *javalibs* instead ? > > I think it's best to use full path names when you're talking about > this > stuff The directory layout of the Java stuff is now exactly as we have discussed: /opt/csw/java jdk/ jdk1.6.0_52/ (CSWjdk6) jdk6 -> jdk1.6.0_52 (CSWjdk6) latest -> jdk6 (CSWjdk) jre/ jre1.6.0_52 -> jdk1.6.0_52/jre/ (CSWjre6) jre6 -> jre1.6.0_52 (CSWjre6) latest -> jre6 (CSWjre) javalibs/ (New one??) The packages have been installed on build8s and build8x for inspection. Best regards -- Dago From dam at opencsw.org Fri Jan 30 17:28:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:28:54 +0100 Subject: [csw-maintainers] General package update on the buildfarm In-Reply-To: References: Message-ID: <6C85BFA5-B667-45CE-950D-E538280AAF5E@opencsw.org> Hi, Am 30.01.2009 um 17:04 schrieb Dagobert Michelsen: > there has been a request for package installation where I must update > all dependencies. Please be patient while I run a full upgrade of > CSW packages on all build servers. All packages have been upgraded. Sorry for the inconvenience. -- Dago From phil at bolthole.com Fri Jan 30 17:41:48 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 08:41:48 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> Message-ID: <20090130164148.GC72531@bolthole.com> On Fri, Jan 30, 2009 at 05:27:34PM +0100, Dagobert Michelsen wrote: > Hi, > ... > The directory layout of the Java stuff is now exactly as we have > discussed: > > /opt/csw/java > .... > javalibs/ (New one??) > I dont remember discussing /opt/csw/java/javalibs before. what should its statement of purpose be? and why would it be different form the preexisting /opt/csw/share/java/ ? (whose current purpose is primarily for .jar files, but given the name, could be most other "java related libraries" also ?) From harpchad at opencsw.org Fri Jan 30 20:05:10 2009 From: harpchad at opencsw.org (Chad Harp) Date: Fri, 30 Jan 2009 13:05:10 -0600 Subject: [csw-maintainers] pidgin 2.5.4 in testing Message-ID: <49834F66.6000901@opencsw.org> Changes: update from 2.5.3 -> 2.5.4 From bonivart at opencsw.org Sat Jan 31 03:38:32 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 03:38:32 +0100 Subject: [csw-maintainers] Package page broken Message-ID: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> I reported about the file display being wrong for phpMyAdmin the other day. I remember reporting the same thing to Blastwave sometime before the split and it was fixed but we still have the broken code that doesn't use the BASEDIR setting. I also noted that my new package, botnet, can't be displayed at all. According to the page there is no such package. A third problem is that bzip2 doesn't show isaexec as a dependency on the main site but in the catalog it's there. All three of these problems do not exist with James Lee's more informative package page: http://www.canoedissent.org.uk/packages/ Overall the web site is pretty shaky with broken stuff that has been broken for a long time and new stuff being "out of sync" like above. I hope the new web site will use more stable tools for us, like James page which has always worked fine for me. -- /peter From phil at bolthole.com Sat Jan 31 04:25:05 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:25:05 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131032505.GF2538@bolthole.com> On Sat, Jan 31, 2009 at 03:38:32AM +0100, Peter Bonivart wrote: > ... > All three of these problems do not exist with James Lee's more > informative package page: http://www.canoedissent.org.uk/packages/ > > Overall the web site is pretty shaky with broken stuff that has been > broken for a long time and new stuff being "out of sync" like above. I > hope the new web site will use more stable tools for us, like James > page which has always worked fine for me. james page has always worked for what you use it for, i understand that. but does james's page, have ALL the features of the existing page? I'm not aware that it does. for example, you cannot search for shared libs nor does it link to the mantis section, for an individual package. I am not averse to replacing the existing page. I'd just like to make sure that it is an UPgrade, rather than a sidegrade. Features should be added, not traded one for another. From phil at bolthole.com Sat Jan 31 04:37:18 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:37:18 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131033718.GG2538@bolthole.com> btw; the reason that sometimes there is a lag for "new" packages to be displayed as packages, is two fold: 1. a package doesnt display as "officially" a package on www.opencsw.org/packages until it has an official mantis section for it. 2. there is a separate "checkmantis" script, that i run from time to time, to do this. The reason #2 is separate, is because creating the mantis space is kinda messy to back out from, so it's nice to avoid adding something by mistake, or in error. SO, at the moment, we're erroring on the side of not updating frequently enough, as opposed to updating mantis all the time. james' stuff doesnt try to integrate/update anything else, so it's a little simpler on his end. From phil at bolthole.com Sat Jan 31 04:40:21 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:40:21 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131034021.GH2538@bolthole.com> btw: thank you for reminding me about the package search page, not having proper paths, when basedir != "/opt/csw". i have now fixed that bug, and reregistered phpmyadmin. please let me know if there are other packages that need similar reregistering. From bonivart at opencsw.org Sat Jan 31 10:59:43 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 10:59:43 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> On Sat, Jan 31, 2009 at 4:25 AM, Philip Brown wrote: > but does james's page, have ALL the features of the existing page? > I'm not aware that it does. > > for example, you cannot search for shared libs > nor does it link to the mantis section, for an individual package. > > I am not averse to replacing the existing page. I'd just like to make sure > that it is an UPgrade, rather than a sidegrade. Features should be added, > not traded one for another. History tells me that your reasoning here means that things will remain the way they are so I won't waste my time arguing with you. But I would like to show another useful thing James page has, it shows symlinks properly. Look at the difference for a package like gnulinks: http://www.opencsw.org/search/gnulinks http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/files/ I also want to remind you that bzip2 still lacks the isaexec dependency. -- /peter From phil at bolthole.com Sat Jan 31 13:27:02 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:27:02 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> Message-ID: <20090131122702.GA12692@bolthole.com> On Sat, Jan 31, 2009 at 10:59:43AM +0100, Peter Bonivart wrote: > But I would like to show another useful thing James page has, it shows > symlinks properly. Look at the difference for a package like gnulinks: > > http://www.opencsw.org/search/gnulinks > http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/files/ That was actually a deliberate design decision on my part. Unfortunately, given that it was 6 years ago, i dont remember off the top of my head WHY i made that decision at the time :-/ I'll try to ponder on that . > I also want to remind you that bzip2 still lacks the isaexec dependency. not the fault of the registration script. bzip2 doesnt actually have a declared dependancy on isaexec. bender$ cat /tmp/CSWbzip2/install/depend P CSWcommon common - common files and dirs for CSW packages From james at opencsw.org Sat Jan 31 13:36:02 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:36:02 GMT Subject: [csw-maintainers] .la discussion In-Reply-To: <4980876A.8070806@opencsw.org> References: <4980876A.8070806@opencsw.org> Message-ID: <20090131.12360200.3638938294@gyor.oxdrove.co.uk> On 28/01/09, 16:27:22, Chad Harp wrote regarding [csw-maintainers] .la discussion: > I've got some .la files that are causing issues. I've seen some > requests to have them deleted (on a single file basis) from the build > farm, is that how we should handle them for now? I was criticised the the last time I offered my workaround but here goes again because it actually works. It is not so much the la files that are a problem but libtool's use of them. My strategy is one of living with libtool rather than avoiding or fighting it. Write a shell script (or whatever you like) and name it cc and/or CC. Place it on the path in front of real compiler. Make the script dismantle the compiler args, reassemble in a sane order, exclude and add anything you want and call the real compiler with your own new arg list. James. From bonivart at opencsw.org Sat Jan 31 13:38:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 13:38:42 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131122702.GA12692@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> Message-ID: <625385e30901310438l1e52bf5ay331468ae7bdadd85@mail.gmail.com> On Sat, Jan 31, 2009 at 1:27 PM, Philip Brown wrote: >> I also want to remind you that bzip2 still lacks the isaexec dependency. > > not the fault of the registration script. bzip2 doesnt actually have a > declared dependancy on isaexec. > > bender$ cat /tmp/CSWbzip2/install/depend > P CSWcommon common - common files and dirs for CSW packages Then we have broken catalogs which are much worse. http://ftp.math.purdue.edu/mirrors/opencsw.org/current/i386/5.10/catalog bzip2 1.0.5,REV=2009.01.17 CSWbzip2 bzip2-1.0.5,REV=2009.01.17-SunOS5.8-i386-CSW.pkg.gz bfd482c82ec78e5d4ae974679e890ddd 404667 CSWcommon|CSWisaexec none Sparc looks ok. -- /peter From james at opencsw.org Sat Jan 31 13:39:57 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:39:57 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> Message-ID: <20090131.12395700.2202691244@gyor.oxdrove.co.uk> On 31/01/09, 09:59:43, Peter Bonivart wrote regarding Re: [csw-maintainers] Package page broken: > But I would like to show another useful thing James page has, it shows > symlinks properly. Look at the difference for a package like gnulinks: > http://www.opencsw.org/search/gnulinks > http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/fi les/ I not sure mine is right, if one runs "ls" on a sym link it just shows the file name, so perhaps this simple file list should show only the file names. An "ls -l" style long output too would be useful showing the size, date, owners and perms of all files, then we could add checksum... no, I wanted to keep it simple. From james at opencsw.org Sat Jan 31 13:39:58 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:39:58 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <20090131.12395800.4260684360@gyor.oxdrove.co.uk> On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > but does james's page, have ALL the features of the existing page? > I'm not aware that it does. > for example, you cannot search for shared libs True. I only read the top part of the package file to extract the info parts (as a stream from a remote URL). This mean only a small amount needs to be downloaded. To read the ELF headers and extract the shared lib usage the whole package has to be read and I chose not to. > nor does it link to the mantis section, for an individual package. It don't know the mapping from package name to mantis number, (no access to the mantis data). Mantis would be better if it used package name itself not an arbitrary id number. Of course if someone could set up a forwarder... From james at opencsw.org Sat Jan 31 13:40:39 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:40:39 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <20090131.12403900.475170348@gyor.oxdrove.co.uk> On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > I am not averse to replacing the existing page. I'd just like to make > sure that it is an UPgrade, rather than a sidegrade. Features should > be added, not traded one for another. Ahh.. so this is how software turns into bloatware. From james at opencsw.org Sat Jan 31 13:41:50 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:41:50 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131122702.GA12692@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> Message-ID: <20090131.12415000.3743127150@gyor.oxdrove.co.uk> On 31/01/09, 12:27:02, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > > I also want to remind you that bzip2 still lacks the isaexec dependency. > not the fault of the registration script. bzip2 doesnt actually have a > declared dependancy on isaexec. Compare: http://www.canoedissent.org.uk/packages/unstable/i386/5.10/CSWbzip2/ http://www.canoedissent.org.uk/packages/unstable/sparc/5.10/CSWbzip2/ The problem is Phil's single listing. James. From bonivart at opencsw.org Sat Jan 31 13:48:12 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 13:48:12 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12415000.3743127150@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> <20090131.12415000.3743127150@gyor.oxdrove.co.uk> Message-ID: <625385e30901310448p28c61b8alddef73bdaf5b53af@mail.gmail.com> On Sat, Jan 31, 2009 at 1:41 PM, James Lee wrote: > On 31/01/09, 12:27:02, Philip Brown wrote regarding Re: > [csw-maintainers] Package page broken: > >> > I also want to remind you that bzip2 still lacks the isaexec dependency. > >> not the fault of the registration script. bzip2 doesnt actually have a >> declared dependancy on isaexec. > > Compare: > http://www.canoedissent.org.uk/packages/unstable/i386/5.10/CSWbzip2/ > http://www.canoedissent.org.uk/packages/unstable/sparc/5.10/CSWbzip2/ > > > The problem is Phil's single listing. Ah...that explains it. Thank you James. -- /peter From phil at bolthole.com Sat Jan 31 13:49:31 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:49:31 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12403900.475170348@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <20090131.12403900.475170348@gyor.oxdrove.co.uk> Message-ID: <20090131124931.GB12692@bolthole.com> On Sat, Jan 31, 2009 at 12:40:39PM +0000, James Lee wrote: > On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: > [csw-maintainers] Package page broken: > > > I am not averse to replacing the existing page. I'd just like to make > > sure that it is an UPgrade, rather than a sidegrade. Features should > > be added, not traded one for another. > > Ahh.. so this is how software turns into bloatware. haha :-) well, I dont think something should be considered "bloat", if it is a feature that is both useful, and relevant. From phil at bolthole.com Sat Jan 31 13:56:05 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:56:05 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12395800.4260684360@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <20090131.12395800.4260684360@gyor.oxdrove.co.uk> Message-ID: <20090131125605.GC12692@bolthole.com> On Sat, Jan 31, 2009 at 12:39:58PM +0000, James Lee wrote: > > nor does it link to the mantis section, for an individual package. > > It don't know the mapping from package name to mantis number, (no access > to the mantis data). Mantis would be better if it used package name > itself not an arbitrary id number. Of course if someone could set up a > forwarder... thats an idea... it would be nice if some motivated person could code up an add-on, that we could drop into the mantis area, that would maybe look something like [http://....mantis/]showproject.php/softwarenamehere This could potentially benefit both us, and mantis itself. It could be contributed to "upstream", if written nicely. From william at wbonnet.net Sat Jan 31 18:43:36 2009 From: william at wbonnet.net (William Bonnet) Date: Sat, 31 Jan 2009 18:43:36 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <20090130164148.GC72531@bolthole.com> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> <20090130164148.GC72531@bolthole.com> Message-ID: <49848DC8.8070705@wbonnet.net> Hi guys > I dont remember discussing /opt/csw/java/javalibs before. what should its > statement of purpose be? > It has never been discussed > and why would it be different form the preexisting > /opt/csw/share/java/ ? > I don't think it has to be In fat the problem is that my original email was /not clear/. I was talking about adding files to GAR, so it was about the java (or javalibs) directory in svn not under /opt/csw :) cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Sat Jan 31 21:06:29 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 12:06:29 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: <49848DC8.8070705@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> <20090130164148.GC72531@bolthole.com> <49848DC8.8070705@wbonnet.net> Message-ID: <20090131200629.GD12692@bolthole.com> On Sat, Jan 31, 2009 at 06:43:36PM +0100, William Bonnet wrote: > ... > In fat the problem is that my original email was /not clear/. I was > talking about adding files to GAR, so it was about the java (or > javalibs) directory in svn not under /opt/csw :) ahaha.. good to know now :-) From phil at bolthole.com Thu Jan 1 07:40:34 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 31 Dec 2008 22:40:34 -0800 Subject: [csw-maintainers] back from vac Message-ID: <20090101064034.GD70757@bolthole.com> fyi: back from vacation, and have processed some pending packages. will put in more tomorrow; it's late. happy new year and all that :-) order was semi-random for the curious From dlaigle at opencsw.org Thu Jan 1 18:38:57 2009 From: dlaigle at opencsw.org (dlaigle) Date: Thu, 01 Jan 2009 18:38:57 +0100 Subject: [csw-maintainers] =?utf-8?q?qt=5Fgcc_3=2E3=2E8b_in_/testing?= Message-ID: <938923f84f2c55a7361b1c77ee18502c@localhost> Hi ! Happy new year and feel free to test the new build of Qt_gcc 3.3.8: http://mirror.opencsw.org/testing/qt_gcc-3.3.8,REV=2009.01.01-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/qt_gcc-3.3.8,REV=2009.01.01-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/qt_gcc_common-3.3.8,REV=2009.01.01-SunOS5.8-all-CSW.pkg.gz Using this new one in replacement of the current (old) 3.3.4 version should give all "kde-gcc" applications anti-aliased fonts and OpenGL support for nuts. Cheers - Dominique From dam at opencsw.org Thu Jan 1 18:49:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 1 Jan 2009 18:49:54 +0100 Subject: [csw-maintainers] New members Message-ID: Hi, the association welcomes the newly accepted members - Ken Mays - Jonathan Wheeler - Mike Arnold - Oliver Kiddle All of you have already contributed to the project in the past. Ken did a lot of desktop packages, Jonathan put considerable effort in media player software and contributed fixes upstream, Mike also maintained quite a bunch of packages and Oliver took over some orphaned packages like lzma. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! If you have applied for membership and don't see your name listed here please stay calm. There is a backlog and I don't have mails on every applicant from every board member yet. Please allow some more days as it is still vacation time. Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Best regards -- Dago From dam at opencsw.org Thu Jan 1 22:52:15 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 1 Jan 2009 22:52:15 +0100 Subject: [csw-maintainers] libidn 1.9 in testing/ Message-ID: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> Hi, I updated our stoneged-version of libidn to 1.9 in testing: libidn-1.9,REV=2009.01.01-SunOS5.8-i386-CSW.pkg.gz libidn-1.9,REV=2009.01.01-SunOS5.8-sparc-CSW.pkg.gz However, the old package contained some (really-) legacy versions of the library: /opt/csw/lib/sparcv9/libidn.so.11.5.2 /opt/csw/lib/sparcv9/libidn.so.11.5.12 /opt/csw/lib/sparcv9/libidn.so.11.5.10 /opt/csw/lib/libidn.so.11.5.2 /opt/csw/lib/libidn.so.11.5.12 /opt/csw/lib/libidn.so.11.5.10 /opt/csw/lib/libidn.so.11.4.5 There is quite a number of packages depending on this one (see ). Is there a simpler way to find stuff depending on these old libs apart from installing all dependend packages and use ldd? It would be really useful to be able to search for this in addition to the regular file searches. The packages in testing/ *do not* include any old versions right now. Best regards -- Dago From phil at bolthole.com Fri Jan 2 00:40:59 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 1 Jan 2009 15:40:59 -0800 Subject: [csw-maintainers] libidn 1.9 in testing/ In-Reply-To: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> References: <91D9C864-0797-4655-BF9B-83F62E7D1435@opencsw.org> Message-ID: <20090101234059.GA70048@bolthole.com> On Thu, Jan 01, 2009 at 10:52:15PM +0100, Dagobert Michelsen wrote: > Hi, > There is quite a number of packages depending on this one > (see ). Is there a simpler > way to find stuff depending on these old libs apart from installing > all dependend packages and use ldd? It would be really useful to > be able to search for this in addition to the regular file searches. This is mentioned on the search page. put each of the actual numbered versions in. for example, exact match on libidn.so.11.5.2 pulls up nothing. Hmm.... perhaps this feature is broken though :-( nothing is showing up now on any of the revs. WAIT! everything seems to actually be looking for the simpler, libidn.so.11 so you should be able to dump the older revs i think. This is not surprising, since presumably, the newest lib, has an SONAME of libidn.so.11 also hurray for competant developers for once! From dam at opencsw.org Fri Jan 2 18:25:45 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 2 Jan 2009 18:25:45 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 Message-ID: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Hi, I finally managed to make a current ncurses 5.7 with full 64 bit for Sparc and x86. The legacy versions of the shared libraries which used to be in the previous package doesn't seemed to be used, so I dropped them. Feel free to give it a try, after release we can go on adding amd64 support to all the dependencies. Best regards -- Dago From phil at bolthole.com Fri Jan 2 19:55:25 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 2 Jan 2009 10:55:25 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Message-ID: <20090102185525.GA7106@bolthole.com> On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: > Hi, > > I finally managed to make a current ncurses 5.7 with full > 64 bit for Sparc and x86. The legacy versions of the shared > libraries which used to be in the previous package doesn't > seemed to be used, so I dropped them. Feel free to give it > a try, after release we can go on adding amd64 support to > all the dependencies. please test/fix the xterm issues on.. x86, i think it was? From phil at bolthole.com Sun Jan 4 08:25:22 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 3 Jan 2009 23:25:22 -0800 Subject: [csw-maintainers] new version of cswutils/checkpkg Message-ID: <20090104072522.GA15859@bolthole.com> hi folks, please note, that I have updated o the cswutils package, for a new version of checkpkg. Folks will be happy to learn that it is a good deal more intelligent, about NOT double-reporting gcc3rt vs gcc3core dependancies. also, it will not double report SUNW dependancies when CSW ones already cover it. There are still a few vague edge cases where it wont be perfect... but it should be a whole lot better than the older version. enjoy :) (PS to build farmadmins: please update the packageon the build machines ;-) From dlaigle at opencsw.org Sun Jan 4 17:55:22 2009 From: dlaigle at opencsw.org (dlaigle) Date: Sun, 04 Jan 2009 17:55:22 +0100 Subject: [csw-maintainers] =?utf-8?q?samba=5Flib=5Fdev_on_build_farm_missi?= =?utf-8?b?bmcuLi4=?= Message-ID: <1bc9b6a011c2618e625fe93d37477d80@localhost> Hi, Please install the package CSWsambalibdev on build machines, I have dependencies on it from KDE... Many thanks. - Dominique From dlaigle at opencsw.org Sun Jan 4 20:27:54 2009 From: dlaigle at opencsw.org (dlaigle) Date: Sun, 04 Jan 2009 20:27:54 +0100 Subject: [csw-maintainers] =?utf-8?q?/testing_=3A_arts=5Fgcc-1=2E5=2E10_an?= =?utf-8?q?d_kdelibs=5Fgcc-3=2E5=2E10?= Message-ID: <6d375a76a36f1762477729f4f79c5f95@localhost> Hello, Fundamental packages for kde 3.5.10 are ready for testing: http://mirror.opencsw.org/testing/arts_gcc-1.5.10,REV=2009.01.03-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/arts_gcc-1.5.10,REV=2009.01.03-SunOS5.8-sparc-CSW.pkg.gz http://mirror.opencsw.org/testing/kdelibs_gcc-3.5.10,REV=2009.01.03-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/kdelibs_gcc-3.5.10,REV=2009.01.03-SunOS5.8-sparc-CSW.pkg.gz Cheers - Dominique From bwalton at opencsw.org Mon Jan 5 16:41:10 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 05 Jan 2009 10:41:10 -0500 Subject: [csw-maintainers] avoid cswutils Message-ID: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> Hi All, Avoid the updated cswutils. It puts files in the wrong locations. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Mon Jan 5 17:44:32 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 5 Jan 2009 08:44:32 -0800 Subject: [csw-maintainers] avoid cswutils In-Reply-To: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> References: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> Message-ID: <20090105164431.GA71088@bolthole.com> On Mon, Jan 05, 2009 at 10:41:10AM -0500, Ben Walton wrote: > > Hi All, > > Avoid the updated cswutils. It puts files in the wrong locations. what the heck... I went back to look at where I genereated the package... and the files I rememebered editing, arent the way I edited them :-( stuff i put into MULTIPLE files is lost somehow. what a mess :-( new update going out now. seems to pkgadd just fine From bwalton at opencsw.org Tue Jan 6 01:50:20 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 05 Jan 2009 19:50:20 -0500 Subject: [csw-maintainers] avoid cswutils In-Reply-To: <20090105164431.GA71088@bolthole.com> References: <1231169989-sup-3070@ntdws12.chass.utoronto.ca> <20090105164431.GA71088@bolthole.com> Message-ID: <1231202800-sup-7771@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Mon Jan 05 11:44:32 -0500 2009: > new update going out now. > seems to pkgadd just fine Following up on this, it seems that the this is a PEBKAC. I called `pkg-get -i cswutils` instead of `pkg-get -u cswutils.` [Holiday mode still? Debian mode?] The BASEDIR had changed from / to /opt/csw and the default admin file sets instance=overwrite. In short, I shot myself in the foot. Apologies to Phil and to the list. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Tue Jan 6 14:45:27 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 06 Jan 2009 14:45:27 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> Message-ID: <49636077.10804@opencsw.org> Hi Dago, Dagobert Michelsen wrote: > I finally managed to make a current ncurses 5.7 with full > 64 bit for Sparc and x86. which machine do you use to build 64 bit packages? When i try to build mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( [===== NOW BUILDING: mbuffer-20081207 MODULATION isa-amd64: ISA=amd64 =====] ==> Extracting download/mbuffer-20081207.tgz ==> Copying download/CSWpackage.gspec [extract-modulated] complete for mbuffer. gmake[1]: Leaving directory `/home/skayser/mgar/pkg/mbuffer/trunk' [extract] complete for mbuffer. gmake[1]: Entering directory `/home/skayser/mgar/pkg/mbuffer/trunk' gar/gar.conf.mk:321: *** The ISA 'amd64' can not be build on this kernel with the arch 'i386'. Stop. However, your ncurses PSTAMP makes me believe that you used build8x to build the 64 bit ncurses libs. What am i missing? Sebastian From phil at bolthole.com Tue Jan 6 18:03:19 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 6 Jan 2009 09:03:19 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49636077.10804@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <49636077.10804@opencsw.org> Message-ID: <20090106170319.GC42258@bolthole.com> On Tue, Jan 06, 2009 at 02:45:27PM +0100, Sebastian Kayser wrote: > Hi Dago, > > Dagobert Michelsen wrote: > > I finally managed to make a current ncurses 5.7 with full > > 64 bit for Sparc and x86. > > which machine do you use to build 64 bit packages? When i try to build > mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( yup. cant build amd64 on sol8. sadly. HHmmmm... well, actually, it should be theoretically possible. we should be able to set up a gcc cross-compiler, for non-kernel software builds. (i'm not volunteering for it though ;-) but you can use build10x for generating the binaries. > However, your ncurses PSTAMP makes me believe that you used build8x to > build the 64 bit ncurses libs. What am i missing? PSTAMP says where you created the packages. for combined sol8/10 packages, standard proceedure is to build the "regular" stuff on build8x, then build aux binaries on build10x and copy them over. From dam at opencsw.org Tue Jan 6 22:53:10 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 6 Jan 2009 22:53:10 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49636077.10804@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <49636077.10804@opencsw.org> Message-ID: Hi Sebastian, Am 06.01.2009 um 14:45 schrieb Sebastian Kayser: > Dagobert Michelsen wrote: >> I finally managed to make a current ncurses 5.7 with full >> 64 bit for Sparc and x86. > > which machine do you use to build 64 bit packages? When i try to build > mbuffer with GAR v2 and BUILD64=1 on build8x GAR won't let me. :( > > [===== NOW BUILDING: mbuffer-20081207 MODULATION isa-amd64: > ISA=amd64 =====] > ==> Extracting download/mbuffer-20081207.tgz > ==> Copying download/CSWpackage.gspec > [extract-modulated] complete for mbuffer. > gmake[1]: Leaving directory `/home/skayser/mgar/pkg/mbuffer/trunk' > [extract] complete for mbuffer. > gmake[1]: Entering directory `/home/skayser/mgar/pkg/mbuffer/trunk' > gar/gar.conf.mk:321: *** The ISA 'amd64' can not be build on this > kernel > with the arch 'i386'. Stop. > > However, your ncurses PSTAMP makes me believe that you used build8x to > build the 64 bit ncurses libs. What am i missing? The trick is to do the 64 bit compilation on build10x and the package assembly on build8x. You do - build8x: gmake - build10x: gmake merge - build8x: gmake package And you end up with a nicely assembled package. This is only possible with an NFS-mounted directory between Solaris 8 and 10. I may add some feature which sshs over to the right machine for each ISA. Best regards -- Dago From dam at opencsw.org Tue Jan 6 23:33:05 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 6 Jan 2009 23:33:05 +0100 Subject: [csw-maintainers] New members and current member acceptance status Message-ID: <3D0F723B-6FCE-4019-ACF9-FB39F29D1352@opencsw.org> Hi, the association welcomes the newly accepted members - Ian Dickinson - Gilberto Persico - Chad Harp Ian and Gilberto have already contributed to the project in the past. Ian maintains some network-related packages, Gilberto also maintains network and terminal-related packages. Chad is a new maintainer who contributed lots of changes to SVN for several packages like vim, meanwhile, libgadu and others. Please keep in mind that being a maintainer is not only about fame and glory, but also about tedious work to make the packages as good as possible and remove bugs timely when discovered. Please check regularly at the bottom of your maintainer page if there are any open issues. If you have spare cycles please adopt an orphaned package and help bring the complete software stack to a 100% current state. But enough of morality: A very warm welcome! Your membership is tracked at There is now a new column with your dedication in the project. Please let me know on what are you working or are planning to work like "webpage", "maintainer", etc. Currently there are three more applicants is the queue for which I either don't have votes from all board members or where the status is currently under discussion: - Juergen Arndt - Jake Goerzen - Eric Korpela If you have applied for membership and don't see your name anywhere above please let me know. There has been a lot of mail traffic for me to be processed in the past weeks and I cannot guarantee that I didn't missed one. Best regards -- Dago _______________________________________________ board mailing list board at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/board From dam at opencsw.org Wed Jan 7 22:59:11 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 7 Jan 2009 22:59:11 +0100 Subject: [csw-maintainers] Please take care: prototype generation on mGAR v2 Message-ID: Hi, it turns out the prototype generation of mGAR v2 had some issues generating packages containing hardlinks to files in other directories from the same package. Commit r2753 should have fixed this, however this path rewriting from cswproto is not straight-forward. Please be extra careful with the auto-generated prototypes and let me know if you encounter other issues. This does not affect mGAR v1. Thanks! -- Dago From dam at baltic-online.de Wed Jan 7 22:57:51 2009 From: dam at baltic-online.de (Dagobert Michelsen) Date: Wed, 7 Jan 2009 22:57:51 +0100 Subject: [csw-maintainers] Please take care: prototype generation on mGAR v2 Message-ID: <2A2E6840-CA05-4148-B192-FD29213D0CA9@baltic-online.de> Hi, it turns out the prototype generation of mGAR v2 had some issues generating packages containing hardlinks to files in other directories from the same package. Commit r2753 should have fixed this, however this path rewriting from cswproto is not straight-forward. Please be extra careful with the auto-generated prototypes and let me know if you encounter other issues. This does not affect mGAR v1. Thanks! -- Dago From william at wbonnet.net Wed Jan 7 22:05:52 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 07 Jan 2009 22:05:52 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media Message-ID: <49651930.2070506@wbonnet.net> Hi, I am looking the installation media of the latest (if possible) version of Solaris 7 for the x86 platform. Anyone has an idea of how to find it ? thanksin advance for your help cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 7 22:19:22 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 07 Jan 2009 22:19:22 +0100 Subject: [csw-maintainers] LinkedIn group Message-ID: <49651C5A.4090800@wbonnet.net> Hi For people using LinkedIn i have created an OpenCSW group. http://www.linkedin.com/groups?home=&gid=1693847 feel free to join cheers, W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 7 23:47:06 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 7 Jan 2009 23:47:06 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <20090102185525.GA7106@bolthole.com> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> Message-ID: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Hi Phil, Am 02.01.2009 um 19:55 schrieb Philip Brown: > On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: >> I finally managed to make a current ncurses 5.7 with full >> 64 bit for Sparc and x86. The legacy versions of the shared >> libraries which used to be in the previous package doesn't >> seemed to be used, so I dropped them. Feel free to give it >> a try, after release we can go on adding amd64 support to >> all the dependencies. > > please test/fix the xterm issues on.. x86, i think it was? After reading the bug report I get the impression that the Solaris implementation of xterm is missing the necessary control character support. Modifying the xterm spec would be bad, as http://opencsw.org/packages/xterm supports the sequence. Otherwise the package looks good now for me. Best regards -- Dago From phil at bolthole.com Thu Jan 8 01:22:54 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 7 Jan 2009 16:22:54 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Message-ID: <20090108002254.GA31120@bolthole.com> On Wed, Jan 07, 2009 at 11:47:06PM +0100, Dagobert Michelsen wrote: > > please test/fix the xterm issues on.. x86, i think it was? > > After reading the bug report I get the impression that the > Solaris implementation of xterm is missing the necessary > control character support. Modifying the xterm spec would > be bad, as http://opencsw.org/packages/xterm supports the > sequence. > I think that's inappropriate. it does not work on x86 as well as it does on sparc. unless you can say "x86 xterm needs to install this patch to work right", i think you should either remove the "broken" feature code from the x86 side, or possibly standardize both sparc and x86 to have lesser capabilities that basically always work. From skayser at opencsw.org Thu Jan 8 14:06:50 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 14:06:50 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> Message-ID: <4965FA6A.1010908@opencsw.org> Dagobert Michelsen wrote: > Am 02.01.2009 um 19:55 schrieb Philip Brown: >> On Fri, Jan 02, 2009 at 06:25:45PM +0100, Dagobert Michelsen wrote: >>> I finally managed to make a current ncurses 5.7 with full >>> 64 bit for Sparc and x86. The legacy versions of the shared >>> libraries which used to be in the previous package doesn't >>> seemed to be used, so I dropped them. Feel free to give it >>> a try, after release we can go on adding amd64 support to >>> all the dependencies. >> please test/fix the xterm issues on.. x86, i think it was? > > After reading the bug report I get the impression that the > Solaris implementation of xterm is missing the necessary > control character support. Modifying the xterm spec would > be bad, as http://opencsw.org/packages/xterm supports the > sequence. Mhh, how then would you prevent issues as the one being described in the bug report? If you leave the capabilities in the xterm terminfo file provided with CSWncurses, applications linked against CSWncurses running in a Solaris xterm are prone to mess up the display. We could pull in CSWxterm as a dependency for applications linked against CSWncurses, but even this wouldn't totally cut it as it is not granted that a user then actually uses /opt/csw/bin/xterm. You would need to make users aware of the fact that CSWxterm should be used with CSWncurses applications ... unless they fancy a garbled display of course. ;) On the other hand: From what i have seen when i deleted the two capabilities from the terminfo file, it doesn't matter to ncurses applications whether the two affected capabilities are present or not. ncurses just falls back to other capabilities for cursor positioning. So why not just drop the capabilities? Sebastian From a.cervellin at acm.org Thu Jan 8 14:58:03 2009 From: a.cervellin at acm.org (Alessio) Date: Thu, 08 Jan 2009 14:58:03 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4965FA6A.1010908@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> Message-ID: <4966066B.4060804@acm.org> xterm 238 is now available on /testing From phil at bolthole.com Thu Jan 8 18:01:10 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 8 Jan 2009 09:01:10 -0800 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <4965FA6A.1010908@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> Message-ID: <20090108170110.GE42437@bolthole.com> On Thu, Jan 08, 2009 at 02:06:50PM +0100, Sebastian Kayser wrote: > > After reading the bug report I get the impression that the > > Solaris implementation of xterm is missing the necessary > > control character support. Modifying the xterm spec would > > be bad, as http://opencsw.org/packages/xterm supports the > > sequence. > > Mhh, how then would you prevent issues as the one being described in the > bug report? If you leave the capabilities in the xterm terminfo file > provided with CSWncurses, applications linked against CSWncurses running > in a Solaris xterm are prone to mess up the display. take the extra capabilities out, from the ncurses terminfo file. > On the other hand: From what i have seen when i deleted the two > capabilities from the terminfo file, it doesn't matter to ncurses > applications whether the two affected capabilities are present or not. > ncurses just falls back to other capabilities for cursor positioning. > > So why not just drop the capabilities? and sounds like you agree also. Perhaps you could specify which ones you dropped to fix things, for the benefit of the current (in progress) ncurses maintainer From skayser at opencsw.org Thu Jan 8 18:17:23 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 18:17:23 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <20090108170110.GE42437@bolthole.com> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> Message-ID: <49663523.2090603@opencsw.org> Philip Brown wrote: > On Thu, Jan 08, 2009 at 02:06:50PM +0100, Sebastian Kayser wrote: >>> After reading the bug report I get the impression that the >>> Solaris implementation of xterm is missing the necessary >>> control character support. Modifying the xterm spec would >>> be bad, as http://opencsw.org/packages/xterm supports the >>> sequence. >> Mhh, how then would you prevent issues as the one being described in the >> bug report? If you leave the capabilities in the xterm terminfo file >> provided with CSWncurses, applications linked against CSWncurses running >> in a Solaris xterm are prone to mess up the display. > > take the extra capabilities out, from the ncurses terminfo file. > > >> On the other hand: From what i have seen when i deleted the two >> capabilities from the terminfo file, it doesn't matter to ncurses >> applications whether the two affected capabilities are present or not. >> ncurses just falls back to other capabilities for cursor positioning. >> >> So why not just drop the capabilities? > > and sounds like you agree also. Yep, I see no harm in doing so. > Perhaps you could specify which ones you dropped to fix things, for the > benefit of the current (in progress) ncurses maintainer The capabilities were HPA and VPA (horizontal and vertical absolute positioning). $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep '[hv]pa' hpa=\E[%i%p1%dG, vpa=\E[%i%p1%dd, Details and ncurses behaviour after i deleted vpa are documented in the bug that i had filed against mutt [1]. Sebastian [1] http://opencsw.org/bugtrack/view.php?id=2942. From skayser at opencsw.org Thu Jan 8 18:57:39 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 18:57:39 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4966066B.4060804@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> Message-ID: <49663E93.1040000@opencsw.org> Alessio wrote: > xterm 238 is now available on /testing Works fine here, thanks. Could you ./configure with --enable-wide-chars so that CSWxterm can deal with UTF-8 ... p l e a s e :) Just give the following python snippet a try. python -c 'print u"\u00E4"' Right now CSWxterm gives ?? whereas the Solaris xterm properly displays the character ? (LATIN SMALL LETTER A WITH DIAERESIS). Sebastian From a.cervellin at acm.org Thu Jan 8 19:12:24 2009 From: a.cervellin at acm.org (Alessio) Date: Thu, 08 Jan 2009 19:12:24 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <49663E93.1040000@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> <49663E93.1040000@opencsw.org> Message-ID: <49664208.60808@acm.org> done, can you grab it again from /testing? Sebastian Kayser wrote: > Alessio wrote: > >> xterm 238 is now available on /testing >> > > Works fine here, thanks. Could you ./configure with --enable-wide-chars > so that CSWxterm can deal with UTF-8 ... p l e a s e :) > > Just give the following python snippet a try. > > python -c 'print u"\u00E4"' > > Right now CSWxterm gives ?? whereas the Solaris xterm properly displays > the character ? (LATIN SMALL LETTER A WITH DIAERESIS). > > Sebastian > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > > From skayser at opencsw.org Thu Jan 8 19:20:15 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 19:20:15 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <49664208.60808@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> <49663E93.1040000@opencsw.org> <49664208.60808@acm.org> Message-ID: <496643DF.9010903@opencsw.org> Alessio wrote: > done, can you grab it again from /testing? Tested the i386 version and it works like a charm :) Thanks very much. > Sebastian Kayser wrote: >> Alessio wrote: >> >>> xterm 238 is now available on /testing >>> >> Works fine here, thanks. Could you ./configure with --enable-wide-chars >> so that CSWxterm can deal with UTF-8 ... p l e a s e :) >> >> Just give the following python snippet a try. >> >> python -c 'print u"\u00E4"' >> >> Right now CSWxterm gives ?? whereas the Solaris xterm properly displays >> the character ? (LATIN SMALL LETTER A WITH DIAERESIS). Sebastian From skayser at opencsw.org Thu Jan 8 19:38:24 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 08 Jan 2009 19:38:24 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media In-Reply-To: <49651930.2070506@wbonnet.net> References: <49651930.2070506@wbonnet.net> Message-ID: <49664820.5040205@opencsw.org> Hi William, William Bonnet wrote: > I am looking the installation media of the latest (if possible) version > of Solaris 7 for the x86 platform. Anyone has an idea of how to find it ? yep, there is huge closet with ancient Solaris release right next door to me. So in case you haven't already found the installation media somewhere, just let me know. I will have to charge you a premium for fighting through piles of dust, though ... *g*. What are you up to with Solaris 7? Sebastian From william at wbonnet.net Thu Jan 8 19:28:30 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 08 Jan 2009 19:28:30 +0100 Subject: [csw-maintainers] Looking for Solaris 7 media In-Reply-To: <49664820.5040205@opencsw.org> References: <49651930.2070506@wbonnet.net> <49664820.5040205@opencsw.org> Message-ID: <496645CE.2040804@wbonnet.net> Hi Sebastian > yep, there is huge closet with ancient Solaris release right next door > to me. So in case you haven't already found the installation media > somewhere, just let me know. > I would appreciate to have some iso to download please > I will have to charge you a premium for fighting through piles of dust, > though ... *g*. What about a beer next time we meet ? ;) > What are you up to with Solaris 7? > In Zurich we talk about the possibility to build packages for versions older than solaris 8. I have next to me a netra T1/105 waiting to become a build7s machine. I was looking for media to try to install a build7x computer. I have a couple of old pentium III based server waiting for a second life. Maybe i'll be able to install one of these boxes. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From yann at pleiades.fr.eu.org Fri Jan 9 00:03:32 2009 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Fri, 09 Jan 2009 00:03:32 +0100 Subject: [csw-maintainers] /testing openssl 0.9.8j Message-ID: <49668644.10903@pleiades.fr.eu.org> Hello all, I just build last openssl version, 0.9.8j, and in addition I created a ca_certificates providing common CA as discussed in a recent thread [1] The openssl_rt package now depends from this ca_certificates package for comptability purpose, as previous openssl distribution used to provide some CA. I put them into testing so I can have some feedbacks before pushing them into unstable: ca_certificates-20090108,REV=2009.01.08-SunOS5.8-all-CSW.pkg.gz openssl-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-all-CSW.pkg.gz openssl_devel-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_devel-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz openssl_rt-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_rt-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz openssl_utils-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-i386-CSW.pkg.gz openssl_utils-0.9.8,REV=2009.01.07_rev=j-SunOS5.8-sparc-CSW.pkg.gz As explained in the testing page [2], to test just type: pkg-get -s http://mirror.opencsw.org/opencsw/testing -U -u openssl or pkgutil -t http://mirror.opencsw.org/opencsw/testing/`uname -p`/`uname -r` -i openssl The /opt/csw/share/doc/ca-certificates/README.CSW contains some information about how to add custom CA certificates. Yann [1] http://lists.opencsw.org/pipermail/maintainers/2008-December/000409.html [2] http://buildfarm.opencsw.org/testing.html From bwalton at opencsw.org Fri Jan 9 02:49:47 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 08 Jan 2009 20:49:47 -0500 Subject: [csw-maintainers] /testing openssl 0.9.8j In-Reply-To: <49668644.10903@pleiades.fr.eu.org> References: <49668644.10903@pleiades.fr.eu.org> Message-ID: <1231465715-sup-4855@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Jan 08 18:03:32 -0500 2009: Hi Yann, > I just build last openssl version, 0.9.8j, and in addition I created a > ca_certificates providing common CA as discussed in a recent thread > [1] I'll try and get this installed on a few machines tomorrow. > The openssl_rt package now depends from this ca_certificates package for > comptability purpose, as previous openssl distribution used to provide > some CA. > The /opt/csw/share/doc/ca-certificates/README.CSW contains some > information about how to add custom CA certificates. A nice touch! :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skayser at opencsw.org Fri Jan 9 13:10:52 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 09 Jan 2009 13:10:52 +0100 Subject: [csw-maintainers] garv2 and multi-ISA build (i386/amd64) problems (target skipped) Message-ID: <49673ECC.1080300@opencsw.org> Hi all, i am having an issue with a multi-ISA build. To build and package mbuffer for i386 & amd64 i am using the three step approach suggested by Dago. build8x: gmake build-isa-i386 build10x: gmake merge build8x: gmake package When doing this, the post-configure-isa-amd64 target is _not_ run. When i substitute the step on build10x with build10x: gmake configure build10x: gmake merge then the post-configure-isa-amd64 target is run. So if someone with experience in garv2 and multi-ISA builds could have a quick look at my build description for mbuffer [1] i would appreciate it. Should i do things differently or is this a garv2 issue? Sebastian [1] https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/mbuffer/trunk/Makefile From phil at bolthole.com Fri Jan 9 17:38:42 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 9 Jan 2009 08:38:42 -0800 Subject: [csw-maintainers] note on "pure php" and similar packages Message-ID: <20090109163842.GG72675@bolthole.com> hi folks, just a heads-up; I have "put in writing", what maintainers have been moving towards, informally, for the last year or two: pure php or other arch neutral, web facing stuff, now officially belongs in /opt/csw/share/www rather than /opt/csw/[apacheX]/htdocs This brings us more in line with other common distributions, and I think also just makes more sense, given that we support multiple webservers. http://www.opencsw.org/standards/layout is where this is now mentioned. From dam at opencsw.org Fri Jan 9 18:19:15 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:19:15 +0100 Subject: [csw-maintainers] Updating all CSW packages now Message-ID: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> Hi, I am now updating all CSW packages installed on the buildfarm to current. As packages get removed and installed it may result in temporary build errors in case you are compiling right now. Best regards -- Dago From dam at opencsw.org Fri Jan 9 18:45:07 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:45:07 +0100 Subject: [csw-maintainers] garv2 and multi-ISA build (i386/amd64) problems (target skipped) In-Reply-To: <49673ECC.1080300@opencsw.org> References: <49673ECC.1080300@opencsw.org> Message-ID: <7A4EE425-1F5E-4327-B34C-67DD7FCB2012@opencsw.org> Hi Sebastian, Am 09.01.2009 um 13:10 schrieb Sebastian Kayser: > i am having an issue with a multi-ISA build. To build and package > mbuffer > for i386 & amd64 i am using the three step approach suggested by Dago. > > build8x: gmake build-isa-i386 > build10x: gmake merge > build8x: gmake package > > When doing this, the post-configure-isa-amd64 target is _not_ run. > When > i substitute the step on build10x with > > build10x: gmake configure > build10x: gmake merge > > then the post-configure-isa-amd64 target is run. > > So if someone with experience in garv2 and multi-ISA builds could > have a > quick look at my build description for mbuffer [1] i would appreciate > it. Should i do things differently or is this a garv2 issue? That was a bug. The target was not called due to the dependency chain automatically generated for the modulations. It is now fixed in r2772: One more thing: What you are trying to do here > # Solaris 10 on build10x has libm.so which points to libm.so.2. > libm.so.2 > # is however not available on Solaris 8. So we have to explicitly use > # libm.so.1 during linking and get rid of the -lm reference. Otherwise > # the package check on build8x when running "gmake package" fails. is also a flaw of checkpkg: When a package is build on Solaris 8 and Solaris 10 the complete package may fail when checkpkg'ed on Solaris 8 with the reason above. You were able to link to a specific version, but this may not always be possible. I have no idea on how this could be fixed in checkpkg apart from not making mixed packages or checking only on Solaris 10. Best regards -- Dago From dam at opencsw.org Fri Jan 9 18:59:57 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 18:59:57 +0100 Subject: [csw-maintainers] [csw-buildfarm] Updating all CSW packages now: DONE In-Reply-To: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> References: <3662FEBF-0148-4B23-9F0A-3EAC1FC48094@opencsw.org> Message-ID: Hi, Am 09.01.2009 um 18:19 schrieb Dagobert Michelsen: > I am now updating all CSW packages installed on the buildfarm to > current. The update is finished, please resume your important work :-) Best regards -- Dago From bwalton at opencsw.org Fri Jan 9 20:14:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 09 Jan 2009 14:14:28 -0500 Subject: [csw-maintainers] /testing openssl 0.9.8j In-Reply-To: <49668644.10903@pleiades.fr.eu.org> References: <49668644.10903@pleiades.fr.eu.org> Message-ID: <1231528110-sup-5884@ntdws12.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Thu Jan 08 18:03:32 -0500 2009: Hi Yann, > I put them into testing so I can have some feedbacks before pushing them > into unstable: I just updated a box here and then used GAR to fetch the package hosted from an https site (after removing custom wget options). It pulled the package down without any problems. So, it looks good to me! [That's pretty circumstantial evidence though.] Thanks for putting this together! :) -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. From dam at opencsw.org Fri Jan 9 23:25:13 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 9 Jan 2009 23:25:13 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <49663523.2090603@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> Message-ID: <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> Hi, Am 08.01.2009 um 18:17 schrieb Sebastian Kayser: > Philip Brown wrote: >> Perhaps you could specify which ones you dropped to fix things, for >> the >> benefit of the current (in progress) ncurses maintainer > > The capabilities were HPA and VPA (horizontal and vertical absolute > positioning). > > $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep > '[hv]pa' > hpa=\E[%i%p1%dG, > vpa=\E[%i%p1%dd, > > Details and ncurses behaviour after i deleted vpa are documented in > the > bug that i had filed against mutt [1]. > > Sebastian > > [1] http://opencsw.org/bugtrack/view.php?id=2942. There is an updated ncurses for sparc/x86 with 32 and 64 bit in testing. Please verify that this solves your problem. Mutt has been recompiled to not use ncurses any more, so I can't exactly reproduce your testcase. The capabilities have been taken out from the description of 'xterm'. Best regards -- Dago From owigger at opencsw.org Sat Jan 10 20:34:43 2009 From: owigger at opencsw.org (Othmar Wigger) Date: Sat, 10 Jan 2009 20:34:43 +0100 Subject: [csw-maintainers] /testing xmgrace Message-ID: <4968F853.5020603@opencsw.org> I packaged grace (xmgrace) and put it on /testing. http://mirror.opencsw.org/testing/grace-5.1.22,REV=2009.01.10-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/grace-5.1.22,REV=2009.01.10-SunOS5.8-sparc-CSW.pkg.gz Grace stands for "GRaphing, Advanced Computation and Exploration of data." It is a WYSIWYG 2D plotting tool for the X Window System and Motif. Grace creates publication-quality output. It can be used from a point-and-click interface or scripted (either from the built-in programming language or through a number of language bindings). It performs both linear and nonlinear least-squares fitting to arbitrarily-complex user-defined functions, with or without constraints. Other analysis tools include FFT, integration and differentiation, splines, interpolation and smoothing. Please have a look at it and check for silly mistakes, as this is the first time I submit a package to openCSW. Othmar From dam at opencsw.org Sun Jan 11 00:02:42 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 11 Jan 2009 00:02:42 +0100 Subject: [csw-maintainers] /testing xmgrace In-Reply-To: <4968F853.5020603@opencsw.org> References: <4968F853.5020603@opencsw.org> Message-ID: <97294C48-5014-47C1-A9F7-133C9E27D9F0@opencsw.org> Hi Othmar, Am 10.01.2009 um 20:34 schrieb Othmar Wigger: > I packaged grace (xmgrace) and put it on /testing. Yes, and "samefile". Works like charm on x86 :-) Thanks! -- Dago From glaw at opencsw.org Sun Jan 11 11:21:16 2009 From: glaw at opencsw.org (Gary Law) Date: Sun, 11 Jan 2009 10:21:16 +0000 Subject: [csw-maintainers] CSWfacter released into testing Message-ID: Hi all There's a new CSWfacter in /home/testing ...feedback appreciated... Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sun Jan 11 11:23:01 2009 From: garylaw at garylaw.net (Gary Law) Date: Sun, 11 Jan 2009 10:23:01 +0000 Subject: [csw-maintainers] CSWpuppet released into testing Message-ID: Hi all There's a new CSWpuppet in /home/testing ...feedback appreciated... Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From skayser at opencsw.org Sun Jan 11 23:36:19 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 11 Jan 2009 23:36:19 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> Message-ID: <496A7463.5080805@opencsw.org> Dagobert Michelsen wrote: > Am 08.01.2009 um 18:17 schrieb Sebastian Kayser: >> Philip Brown wrote: >>> Perhaps you could specify which ones you dropped to fix things, for >>> the >>> benefit of the current (in progress) ncurses maintainer >> The capabilities were HPA and VPA (horizontal and vertical absolute >> positioning). >> >> $ TERM=xterm TERMINFO=/opt/csw/share/terminfo infocmp -1 | ggrep >> '[hv]pa' >> hpa=\E[%i%p1%dG, >> vpa=\E[%i%p1%dd, >> >> Details and ncurses behaviour after i deleted vpa are documented in >> the >> bug that i had filed against mutt [1]. >> >> Sebastian >> >> [1] http://opencsw.org/bugtrack/view.php?id=2942. > > There is an updated ncurses for sparc/x86 with 32 and 64 bit in > testing. Please verify that this solves your problem. Mutt has > been recompiled to not use ncurses any more, so I can't exactly > reproduce your testcase. The capabilities have been taken out > from the description of 'xterm'. Thanks, Dago. Tested the updated ncurses version with the CSWmutt version that the bug was filed against [1]. Solves the problem. Sebastian [1] http://csw.informatik.uni-erlangen.de/oldpkgs/current/i386/5.10/mutt-1.5.18,REV=2008.11.03-SunOS5.8-i386-CSW.pkg.gz From dam at opencsw.org Mon Jan 12 16:46:10 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 16:46:10 +0100 Subject: [csw-maintainers] New in testing/: ncurses 5.7 In-Reply-To: <496A7463.5080805@opencsw.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <20090108170110.GE42437@bolthole.com> <49663523.2090603@opencsw.org> <264E7969-8586-4FA2-A38C-80BCA76FC2D7@opencsw.org> <496A7463.5080805@opencsw.org> Message-ID: <38C29507-A04F-468C-BDB4-23737586C838@opencsw.org> Hi, Am 11.01.2009 um 23:36 schrieb Sebastian Kayser: > Thanks, Dago. Tested the updated ncurses version with the CSWmutt > version that the bug was filed against [1]. Solves the problem. I replaced now the modified terminal description with the option recommended by the ncurses maintainer Thomas Dickey --without-xterm-new This has the advantage to be more predictable than my feature hacking. Please give it a try so this can be released to current soon. Thanks! -- Dago From harpchad at opencsw.org Mon Jan 12 20:23:48 2009 From: harpchad at opencsw.org (Chad Harp) Date: Mon, 12 Jan 2009 13:23:48 -0600 Subject: [csw-maintainers] New version on libxslt in testing Message-ID: <496B98C4.7000606@opencsw.org> I've built a new version of libxslt (1.1.24). In addition to the version refresh it now exclude .la files which appears to be compatible with all existing packages EXCEPT libscrollkeeper (who's own .la refers to libxslt.la). I'm doing some testing, but package owners who depend on libxslt and/or libscrollkeeper may want to test compatibility. Thanks, Chad From dam at opencsw.org Mon Jan 12 20:44:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 20:44:02 +0100 Subject: [csw-maintainers] New version on libxslt in testing In-Reply-To: <496B98C4.7000606@opencsw.org> References: <496B98C4.7000606@opencsw.org> Message-ID: Hi Chad, Am 12.01.2009 um 20:23 schrieb Chad Harp: > I've built a new version of libxslt (1.1.24). In addition to the > version refresh it now exclude .la files which appears to be > compatible > with all existing packages EXCEPT libscrollkeeper (who's own .la > refers > to libxslt.la). > > I'm doing some testing, but package owners who depend on libxslt and/ > or > libscrollkeeper may want to test compatibility. Looks good with xmlstarlet. Best regards -- Dago From glaw at opencsw.org Mon Jan 12 20:56:04 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 19:56:04 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: New version released, with working man pages. Enjoy. -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Mon Jan 12 21:00:31 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 12 Jan 2009 21:00:31 +0100 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: Hi Gary, Am 12.01.2009 um 20:56 schrieb Gary Law: > New version released, with working man pages. Enjoy. Nice touch to see you also working on upstream documentation :-) I haven't used puppet yet, are you using it in your environment? If yes, I would like to know how your typical deployment setup looks like. Thanks! -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Mon Jan 12 21:03:01 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 12 Jan 2009 15:03:01 -0500 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Mon Jan 12 15:00:31 -0500 2009: Hi Gary, > used puppet yet, are you using it in your environment? If yes, I would > like > to know how your typical deployment setup looks like. ...and does it work better under solaris than it did in the past? I'm running cfengine here (warts and all) but have been intrigued by puppet in the past. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Mon Jan 12 21:13:38 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 20:13:38 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: Message-ID: 2009/1/12 Dagobert Michelsen > Hi Gary, > Am 12.01.2009 um 20:56 schrieb Gary Law: > > New version released, with working man pages. Enjoy. > > > Nice touch to see you also working on upstream documentation :-) I haven't > used puppet yet, are you using it in your environment? If yes, I would like > to know how your typical deployment setup looks like. > I'm working on a new infrastructure build out at my current client. It remains to be seen if puppet is used, it seems to fit the bill and gets my recommendation, but the team here need to be comfortable with it, so we're still at proof of concept phase. In previous places I've worked with it in production, and whilst it has some idiosyncrasies, and out-and-out bugs, but beats maintaining by hand -- or alternatives like cfengine -- hands down IMHO. If you are interested I would recommend the book, Pulling Strings With Puppet, and the #puppet channel on IRC (where you can often find me too). -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From glaw at opencsw.org Mon Jan 12 21:21:31 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 20:21:31 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Message-ID: 2009/1/12 Ben Walton > ...and does it work better under solaris than it did in the past? > ...depends what issues you had. Ruby on Solaris used to be very hit and miss, which made puppet flaky. That's a solved problem. There's good support for some solaris specific features, like zones, see here for a quick example: http://www.madstop.com/managing-solaris-zones.html However, there is also at least a 10:1 ratio of Linux:Solaris users with puppet, so the community, documentation, support and so on is very Linux focussed. HTH Gary -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at wbonnet.net Mon Jan 12 20:50:21 2009 From: william at wbonnet.net (William Bonnet) Date: Mon, 12 Jan 2009 20:50:21 +0100 Subject: [csw-maintainers] Press release Message-ID: <496B9EFD.4090008@wbonnet.net> Hi In Zurich we talked about releasing a press communicate to announce the creation of the association. Wednesday in Paris there is meeting with Simon Pheeps. I don't know what is the current statut of the communication, but it would be certainly good to release tomorrow. So it will be only 24 hours old for the meeting (maybe he will have heard of it, and not yet forgotten ;) ). Sorry for the short delay, i forgot to send this email. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.blastwave.org An OpenSolaris Community Site http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 12 22:06:35 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 12 Jan 2009 13:06:35 -0800 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> Message-ID: <20090112210635.GH94353@bolthole.com> On Mon, Jan 12, 2009 at 08:21:31PM +0000, Gary Law wrote: > 2009/1/12 Ben Walton > > ...and does it work better under solaris than it did in the past? > > ...depends what issues you had. Ruby on Solaris used to be very hit and > miss, which made puppet flaky. That's a solved problem. well.. mostly solved. there are still apparently some "quirks" in x86 vs sparc, which is what has delayed our ruby release. Ben Walton took ruby on, but got discouraged when he and I examined some discrepancies between the arches. I think he's sorta trying to ignore it right now :-) would any other ruby enthusiast be willing to take a look? From bwalton at opencsw.org Mon Jan 12 22:14:24 2009 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 12 Jan 2009 16:14:24 -0500 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <20090112210635.GH94353@bolthole.com> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> <20090112210635.GH94353@bolthole.com> Message-ID: <1231794738-sup-8690@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Mon Jan 12 16:06:35 -0500 2009: > Ben Walton took ruby on, but got discouraged when he and I examined some > discrepancies between the arches. > I think he's sorta trying to ignore it right now :-) > would any other ruby enthusiast be willing to take a look? Not discouraged, just distracted. This is actually still on my todo list. I've simply not had time to work on it since git became a priority here and the actual ruby packages I put together work (they've been running a rails site since late in the summer without issue). ...Hoping to get back to it shortly though, since git is going to be out shortly. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From glaw at opencsw.org Mon Jan 12 22:18:03 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 12 Jan 2009 21:18:03 +0000 Subject: [csw-maintainers] CSWpuppet released into testing In-Reply-To: <20090112210635.GH94353@bolthole.com> References: <1231790517-sup-1447@ntdws12.chass.utoronto.ca> <20090112210635.GH94353@bolthole.com> Message-ID: 2009/1/12 Philip Brown > well.. mostly solved. > The CSW stable Ruby works well for puppet. As for later versions, I cannot comment... -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihsan at opencsw.org Tue Jan 13 12:56:49 2009 From: ihsan at opencsw.org (Ihsan Dogan) Date: Tue, 13 Jan 2009 12:56:49 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <496B9EFD.4090008@wbonnet.net> References: <496B9EFD.4090008@wbonnet.net> Message-ID: <496C8181.3000907@opencsw.org> Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: > In Zurich we talked about releasing a press communicate to announce the > creation of the association. > > Wednesday in Paris there is meeting with Simon Pheeps. I don't know what > is the current statut of the communication, but it would be certainly > good to release tomorrow. So it will be only 24 hours old for the > meeting (maybe he will have heard of it, and not yet forgotten ;) ). > > Sorry for the short delay, i forgot to send this email. Othmar Wigger made a press release. Dago, do yo still have the press release? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Tue Jan 13 13:17:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 13:17:02 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <496C8181.3000907@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> Message-ID: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Hi Ihsan, Am 13.01.2009 um 12:56 schrieb Ihsan Dogan: > Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: >> In Zurich we talked about releasing a press communicate to announce >> the >> creation of the association. >> >> Wednesday in Paris there is meeting with Simon Pheeps. I don't know >> what >> is the current statut of the communication, but it would be certainly >> good to release tomorrow. So it will be only 24 hours old for the >> meeting (maybe he will have heard of it, and not yet forgotten ;) ). >> >> Sorry for the short delay, i forgot to send this email. > > Othmar Wigger made a press release. > Dago, do yo still have the press release? Yes, but unfortunately it is in German and I am on training right now :-( Anyway, here it is, maybe someone can translate today: > Effretikon, 6.12.2008 > > Teilnehmer der OpenCSW-Community trafen sich am Wochenende vom 6. > Dezember in Effretikon bei Z?rich zum ersten Mal in der 7-j?hrigen > Geschichte der Bewegung zu einer Konferenz. Anwesend war unter > anderem auch Philip Brown, der Initiator und Vaterfigur des > Projekts. Zweck des Treffens war die Neukonstituierung der Bewegung, > nachdem es letzten Sommer zu einer Spaltung gekommen war, die das > Projekt w?hrend Monaten gel?hmt hatte. > > Zweck von Blastwave/CSW war seit jeher das Bereitstellen von freier > Software f?r das Solaris Betriebssystem auf benutzerfreundliche Art. > CSW soll f?r Solaris ?hnliche Anwenderfreundlichkeit bieten wie > Ubuntu f?r Linux. > > Das OpenCSW-Projekt umfasst heute ?ber 1600 Softwarepakete und z?hlt > 2 Millionen Benutzer. Die Bereitstellung erfolgt ausschliesslich > durch Freiwillige und die Benutzung ist kostenlos. > > Das "Open Community Software"-Projekt (OpenCSW) ist dabei als Verein > nach schweizerischem Recht gegr?ndet worden. Die bisherigen > Teilnehmer desProjektes sind als Vereinsmitglieder herzlich > willkommen, neue Paket-Maintainer (mit entsprechendem Know-How) sind > stets erw?nscht. Der Verein arbeitet unentgeltlich und strebt keinen > Gewinn an. Sein Hauptzweck ist die Bereitstellung von > Softwarepaketen f?r das Solaris Operating Environment und die > Sicherung des Weiterbestehens als freie, community-basierte Software- > Distribution. > > Die Gr?ndungsversammlung w?hlte Philip Brown, Ihsan Dogan und > Dagobert Michelsen in den Vorstand des neu gegr?ndeten Vereins. Ein Bild gibt es unter Best regards -- Dago From bwalton at opencsw.org Tue Jan 13 15:53:32 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 09:53:32 -0500 Subject: [csw-maintainers] New version on libxslt in testing In-Reply-To: <496B98C4.7000606@opencsw.org> References: <496B98C4.7000606@opencsw.org> Message-ID: <1231858329-sup-7368@ntdws12.chass.utoronto.ca> Excerpts from Chad Harp's message of Mon Jan 12 14:23:48 -0500 2009: Hi Chad, > I'm doing some testing, but package owners who depend on libxslt and/or > libscrollkeeper may want to test compatibility. I just ran the xmlto build using the updated libxslt package and it looks good. xmlto only drives xsltproc though and doesn't actually link against any provided libraries. HTH. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From owigger at opencsw.org Tue Jan 13 16:54:11 2009 From: owigger at opencsw.org (Othmar Wigger) Date: Tue, 13 Jan 2009 16:54:11 +0100 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Message-ID: <496CB923.6050704@opencsw.org> Dagobert Michelsen wrote: >> Othmar Wigger made a press release. >> Dago, do yo still have the press release? > > Yes, but unfortunately it is in German and I am on training right > now :-( > Anyway, here it is, maybe someone can translate today: This is my translation. A native English speaker should proofread it before release! Effretikon/Zurich Members of the OpenCSW community met for the first time in the 7 year history of the movement at a conference in Switzerland during the week-end of December 6th. Also present was Philip Brown, the founding father of the project. One important point on the agenda was OpenCSW's legal reconstitution, because of last summer's breakup, which had paralyzed the project during several months. OpenCSW aims to provide ready-to-use free software for the Solaris platform. It is renown for its ease of use and its consistent end-to-end user experience. OpenCSW wants to be for Solaris what Ubuntu is for Linux. To date it counts around 1600 software packages and two million users worldwide. The packaging effort is carried out entirely by volunteers. Usage is free. The newly founded "Open Community Software" project (OpenCSW) is an association under Swiss law. All previous contributors are welcome as members. New package maintainers with the relevant skills are always welcome, too. All members of this not-for-profit association work without financial compensation. Its purpose is the continued provisioning of the Solaris Operating Environment with packaged software as a free, community based distribution. The founding members elected Philip Brown, Ihsan Dogan, and Dagobert Michelsen as members of the board. links: http://www.opencsw.org pictures: the OpenCSW board: http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277160178482290594 the founding association: http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277081573030645330 http://picasaweb.google.de/Othmar.Wigger/OpenCSW?feat=directlink#5277081589838559890 (I suggest somebody please copy these pictures to www.opencsw.org and give them nicer URLs! Copyright for unlimited distribution is hereby granted.) Othmar From skayser at opencsw.org Tue Jan 13 16:59:47 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Tue, 13 Jan 2009 16:59:47 +0100 Subject: [csw-maintainers] Press release In-Reply-To: <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> Message-ID: <496CBA73.1030404@opencsw.org> Dagobert Michelsen wrote: > Am 13.01.2009 um 12:56 schrieb Ihsan Dogan: >> Am 12.1.2009 20:50 Uhr, William Bonnet schrieb: >>> In Zurich we talked about releasing a press communicate to announce >>> the >>> creation of the association. >>> >>> Wednesday in Paris there is meeting with Simon Pheeps. I don't know >>> what >>> is the current statut of the communication, but it would be certainly >>> good to release tomorrow. So it will be only 24 hours old for the >>> meeting (maybe he will have heard of it, and not yet forgotten ;) ). >>> >>> Sorry for the short delay, i forgot to send this email. >> Othmar Wigger made a press release. >> Dago, do yo still have the press release? > > Yes, but unfortunately it is in German and I am on training right > now :-( > Anyway, here it is, maybe someone can translate today: > > [...] I just saw Othmars translation come in. As i was just finished with mine, i might as well send it also. Maybe makes it easier for the one fitting the pieces together. Translation: For the first time in its 7 year history, members of the OpenCSW community gathered for a miniconf in Effretikon, Zurich (Switzerland) on December 6th 2008. Attendees were happy to welcome Phil Brown, founder of the Community Software effort, as well as fellow maintainers from different parts of Europe. With the Blastwave/OpenCSW split in mind, which had put packaging efforts on hold over months, the main purpose of the meeting was to work out ways to avoid such situations in the future and settle on the direction the project should be heading to in the future. Since its beginning the intention of Blastwave/CSW was to provide free software for the Solaris Operating Environment in a user-friendly way. Today the OpenCSW project has 1600 software packages in its catalogs and counts close to 2 million users worldwide. The project is run by volunteers and provides its packages free of charge to everyone. As a result of the miniconf the "Open Community Software (OpenCSW) Project" was founded as an official association according to Swiss jurisdiction. The purpose of the association is to ensure the availability of the free, community-based software distribution known as OpenCSW. Its bylaws embody the core principles. Contributors are welcome to join the association, as are new package maintainers. The association works free of charge and is not geared towards making profit. Philip Brown, Ihsan Dogan, and Dagobert Michelsen were voted on the board of the found association by the founding association members. Sebastian From bwalton at opencsw.org Tue Jan 13 17:08:20 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 11:08:20 -0500 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <496CB923.6050704@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> <496CB923.6050704@opencsw.org> Message-ID: <1231862873-sup-1144@ntdws12.chass.utoronto.ca> Excerpts from Othmar Wigger's message of Tue Jan 13 10:54:11 -0500 2009: Hi Othmar, I'd offer only a small correction. :) Paragraph 1: > legal reconstitution, because of last summer's breakup, which had > paralyzed the project during several months. legal reconstitution, due to last summer's breakup, which saw the project paralyzed for several months. [I also suggest clarifying that the breakup was with blastwave or rewording this to something like: due to last summers internal turmoil, which had paralyzed... Others should maybe comment on this change though.] HTH, -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Tue Jan 13 17:16:50 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 08:16:50 -0800 Subject: [csw-maintainers] Press release, English translation In-Reply-To: <496CB923.6050704@opencsw.org> References: <496B9EFD.4090008@wbonnet.net> <496C8181.3000907@opencsw.org> <8CA9D780-825E-4878-BCAD-31001F586422@opencsw.org> <496CB923.6050704@opencsw.org> Message-ID: <20090113161650.GC84975@bolthole.com> Minor correction which has nothing to do with translation :-) > To date it counts around 1600 software packages and two million users > worldwide. ls *pkg*|wc -l 1847 so, "over 1800 software packages" From harpchad at opencsw.org Tue Jan 13 18:34:30 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:34:30 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> Message-ID: <496CD0A6.1060105@opencsw.org> This latest libgpg_error build created some problems for my pidgin build. /opt/csw/lib/libgpg-error.la is still referenced by: /opt/csw/lib/libexslt.la /opt/csw/lib/libgcrypt.la /opt/csw/lib/libgnutls-extra.la /opt/csw/lib/libgnutls-openssl.la /opt/csw/lib/libgnutls.la /opt/csw/lib/libgnutlsxx.la /opt/csw/lib/libgpgme-pth.la /opt/csw/lib/libgpgme-pthread.la /opt/csw/lib/libgpgme.la This isn't restricted to libgpg_error, I've been running into this with other packages as well (the new libxml for example). I agree that we should be getting rid of the libtool files where possible, I'm just not sure how to address all of the dependencies. I've been using my own .la files in order to do some test builds, but that's just a temporary hack. Are there suggestion on how to deal with the legacy libtool files? Also, is there a mechanism in gar to filter them? I've been using custom prototypes to exclude them, but it would be better if I could let gar generate the prototype and filter the libtool files. Thanks, Chad Dagobert Michelsen wrote: > Hi, > > I am updating libgpg_error on all machines now. > > Best regards > > -- Dago > _______________________________________________ > buildfarm mailing list > buildfarm at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/buildfarm From phil at bolthole.com Tue Jan 13 18:41:24 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 09:41:24 -0800 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD0A6.1060105@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> Message-ID: <20090113174124.GA48829@bolthole.com> On Tue, Jan 13, 2009 at 11:34:30AM -0600, Chad Harp wrote: > This latest libgpg_error build created some problems for my pidgin build. > > /opt/csw/lib/libgpg-error.la is still referenced by: > > /opt/csw/lib/libexslt.la > /opt/csw/lib/libgcrypt.la > /opt/csw/lib/libgnutls-extra.la > /opt/csw/lib/libgnutls-openssl.la > /opt/csw/lib/libgnutls.la > /opt/csw/lib/libgnutlsxx.la > /opt/csw/lib/libgpgme-pth.la > /opt/csw/lib/libgpgme-pthread.la > /opt/csw/lib/libgpgme.la > all of the libgXXX stuff is going away as part of repackaging this week. dunno about libexslt. what package is that in? i guess lib xstl. rebuild, anyone? > sure how to address all of the dependencies. I've been using my own .la > files in order to do some test builds, but that's just a temporary hack. > > Are there suggestion on how to deal with the legacy libtool files? the temp hack sounds like a plan, until we can eradicate them more fully. filtering them out in gar would be nice too From bwalton at opencsw.org Tue Jan 13 18:45:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 12:45:28 -0500 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <20090113174124.GA48829@bolthole.com> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> Message-ID: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 2009: > filtering them out in gar would be nice too This is already happening, unless there was a regression. Dago implemented it a while back. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From harpchad at opencsw.org Tue Jan 13 18:45:37 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:45:37 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <20090113174124.GA48829@bolthole.com> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> Message-ID: <496CD341.2070104@opencsw.org> Philip Brown wrote: > dunno about libexslt. > > what package is that in? i guess lib xstl. > > rebuild, anyone? I've got a new xslt build in testing, its had good feedback so I'll go ahead and move it to newpkgs. From harpchad at opencsw.org Tue Jan 13 18:50:42 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 13 Jan 2009 11:50:42 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Message-ID: <496CD472.7080907@opencsw.org> Probably my fault for using gar v1. Is gar v2 ready for regular use? If so maybe we should change the newpkg- target to make v2 the default. Ben Walton wrote: > Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 2009: > >> filtering them out in gar would be nice too > > This is already happening, unless there was a regression. Dago > implemented it a while back. > > -Ben > > > > ------------------------------------------------------------------------ > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bwalton at opencsw.org Tue Jan 13 18:55:35 2009 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 13 Jan 2009 12:55:35 -0500 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD472.7080907@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> <496CD472.7080907@opencsw.org> Message-ID: <1231869256-sup-3518@ntdws12.chass.utoronto.ca> Excerpts from Chad Harp's message of Tue Jan 13 12:50:42 -0500 2009: > Probably my fault for using gar v1. Is gar v2 ready for regular use? > If so maybe we should change the newpkg- target to make v2 the default. I'm not sure what Dago's thoughts on this are. For my purposes, all of my packages are working fine under v2. That being said, my packages are at worst annoying to build...not overly complicated. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dam at opencsw.org Tue Jan 13 18:55:41 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 18:55:41 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231868669-sup-8689@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> Message-ID: <503C7C8F-B48B-4D40-807B-AA53633133F9@opencsw.org> Hi, Am 13.01.2009 um 18:45 schrieb Ben Walton: > Excerpts from Philip Brown's message of Tue Jan 13 12:41:24 -0500 > 2009: > >> filtering them out in gar would be nice too > > This is already happening, unless there was a regression. Dago > implemented it a while back. Yes, if you use mGAR v2 .la-files are excluded by default. Best regards -- Dago From phil at bolthole.com Tue Jan 13 18:57:23 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 09:57:23 -0800 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD341.2070104@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> Message-ID: <20090113175723.GA76298@bolthole.com> On Tue, Jan 13, 2009 at 11:45:37AM -0600, Chad Harp wrote: > Philip Brown wrote: > > dunno about libexslt. > > > > what package is that in? i guess lib xstl. > > > > rebuild, anyone? > > I've got a new xslt build in testing, its had good feedback so I'll go > ahead and move it to newpkgs. ok, thanks. From dam at opencsw.org Tue Jan 13 18:57:42 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 18:57:42 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <1231869256-sup-3518@ntdws12.chass.utoronto.ca> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <1231868669-sup-8689@ntdws12.chass.utoronto.ca> <496CD472.7080907@opencsw.org> <1231869256-sup-3518@ntdws12.chass.utoronto.ca> Message-ID: Hi Ben, Am 13.01.2009 um 18:55 schrieb Ben Walton: > Excerpts from Chad Harp's message of Tue Jan 13 12:50:42 -0500 2009: >> Probably my fault for using gar v1. Is gar v2 ready for regular use? >> If so maybe we should change the newpkg- target to make v2 the >> default. > > I'm not sure what Dago's thoughts on this are. For my purposes, all > of my packages are working fine under v2. That being said, my > packages are at worst annoying to build...not overly complicated. From time to time a bug comes to the surface in mGAR v2, but I guess the best thing is to move forward, use it as default and fix bugs as they occur. I am making v2 now default. Best regards -- Dago From dam at opencsw.org Tue Jan 13 19:23:36 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 19:23:36 +0100 Subject: [csw-maintainers] Call for testers Message-ID: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Hi, there are packages piling up in testing/ and there seem to be only very little feedback. How about a "call for testers" on the main page? Having professional testers would both help maintainers and improve quality. Best regargs -- Dago From phil at bolthole.com Tue Jan 13 19:42:51 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 13 Jan 2009 10:42:51 -0800 Subject: [csw-maintainers] Call for testers In-Reply-To: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Message-ID: <20090113184251.GA34848@bolthole.com> On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: > Hi, > > there are packages piling up in testing/ and there seem to be > only very little feedback. How about a "call for testers" on > the main page? Having professional testers would both help > maintainers and improve quality. Another suggestion: since we have a "special, custom" testing page rather than just a raw inventory thingie.. it might be nice to allow some kind of "click here to say you tested it" button. Not sure how or where it would store the info though. Also note that if you decide to do this, it should track both the filename, AND THE CHECKSUM, since in theory, maintainers could put a newer version of a package, with the exact same filename, in testing. Also, since the page is "public", it should allow feedback from non-maintainers. From dam at opencsw.org Tue Jan 13 19:53:09 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 13 Jan 2009 19:53:09 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090113184251.GA34848@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> Message-ID: <0D70CADA-4838-41CE-B68F-8278399E80A0@opencsw.org> Hi Phil, Am 13.01.2009 um 19:42 schrieb Philip Brown: > On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: >> there are packages piling up in testing/ and there seem to be >> only very little feedback. How about a "call for testers" on >> the main page? Having professional testers would both help >> maintainers and improve quality. > > Another suggestion: since we have a "special, custom" testing page > rather > than just a raw inventory thingie.. it might be nice to allow some > kind of > "click here to say you tested it" button. > Not sure how or where it would store the info though. > > Also note that if you decide to do this, it should track both the > filename, > AND THE CHECKSUM, since in theory, maintainers could put a newer > version of > a package, with the exact same filename, in testing. > > Also, since the page is "public", it should allow feedback from > non-maintainers. Nice idea, but I am swamped with work and the GAR docs need to be written too. It would be very cool if someone else could jump on this one. Best regards -- Dago From trygvel at opencsw.org Wed Jan 14 01:32:35 2009 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 14 Jan 2009 01:32:35 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> Message-ID: <496D32A3.6040402@opencsw.org> Dagobert Michelsen wrote: > Hi, > > there are packages piling up in testing/ and there seem to be > only very little feedback. How about a "call for testers" on > the main page? Having professional testers would both help > maintainers and improve quality. One thing that might help with getting non-maintainers (maintainer of the specific package, not all maintainers) to test stuff might be to have a page describing test cases to run etc. This will vary wildly between packages, but for some packages it might be very useful. I'm planning to add a jetty6-dev page on the wiki [1] the next time I'm rebuilding the Jetty package just to serve as a reminder for myself on how to verify that the package work. [1]: http://wiki.opencsw.org/packages -- Trygve From skayser at opencsw.org Wed Jan 14 01:51:46 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 14 Jan 2009 01:51:46 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090113184251.GA34848@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> Message-ID: <496D3722.7020004@opencsw.org> Philip Brown wrote: > On Tue, Jan 13, 2009 at 07:23:36PM +0100, Dagobert Michelsen wrote: >> there are packages piling up in testing/ and there seem to be >> only very little feedback. No feedback may sometimes be a good sign. Is there any way to track the number of downloads for a particular package from testing/? >> How about a "call for testers" on the main page? Do you mean testers as in people who specifically test packages inside out? Or just a call to get more people to install packages from testing/ and provide feedback in case they notice something strange? Is testing/ mentioned on the website at all? How about a small paragraph about it on the user guide page [1] under the section "Release Program"? That way users could also be made aware of it and i suppose there are always people out there who are interested in testing out the latest "stuff". >> Having professional testers would both help >> maintainers and improve quality. What about doing it like Debian does it? They have three branches: stable, testing, unstable. Development happens in unstable and packages move to testing after a non-bug-encountered grace period has passed. Developers (maintainers) usually subscribe to unstable and update frequently. Thus, the chance that someone hits a hidden bug is increased. Experimental users can also subscribe to unstable (which would be testing/ in our case) if they like bleeding edge. Does pkg-get/pkgutil offer an easy way to blend in the testing/ tree so that testing/ wouldn't need to be a full release? I imagine something like implicitly using the pkgutil -t option set to the testing tree all the time. >> Another suggestion: since we have a "special, custom" testing page >> rather than just a raw inventory thingie.. Do you mean this one [2]? Hadn't heard of it before. Is it linked from anywhere else on the page? Could you have a look at the package feed on the page. From what i see the last package in the feed is from Dec 12, but there are already more recent packages in testing/. > Also note that if you decide to do this, it should track both the filename, > AND THE CHECKSUM, since in theory, maintainers could put a newer version of > a package, with the exact same filename, in testing. This would not only be interesting for the feedback, but also for pkg-get / pkgutil. Can they be forced to install a package from testing when the filename and version remain identical (which is per default the case for GAR builds done on the same day)? So far i pkgrm'ed the affected package and then installed the new version. But maybe there is something like a --reinstall option? Sebastian [1] http://opencsw.org/userguide [2] http://mirror.opencsw.org/testing.html From bonivart at opencsw.org Wed Jan 14 10:08:22 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 14 Jan 2009 10:08:22 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <496D3722.7020004@opencsw.org> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> Message-ID: <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> On Wed, Jan 14, 2009 at 1:51 AM, Sebastian Kayser wrote: > Does pkg-get/pkgutil offer an easy way to blend in the testing/ tree so > that testing/ wouldn't need to be a full release? I imagine something > like implicitly using the pkgutil -t option set to the testing tree all > the time. No, using -t adds the specified location to what you already have set as mirror in pkgutil.conf. So, yes, pkgutil can blend in the testing tree without it needing to be a full release. I wanted it to work for those who produce a few packages of their own that depend on the CSW stack. That way they don't have to mirror the whole stack locally. > This would not only be interesting for the feedback, but also for > pkg-get / pkgutil. Can they be forced to install a package from testing > when the filename and version remain identical (which is per default the > case for GAR builds done on the same day)? There's no --reinstall option in pkgutil but if you remove the package you want to reinstall first, you will always get the latest one at the next install if you don't have a caching problem in your proxy for example. -- /peter From pfelecan at opencsw.org Wed Jan 14 10:30:47 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 14 Jan 2009 10:30:47 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> (Peter Bonivart's message of "Wed\, 14 Jan 2009 10\:08\:22 +0100") References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> Message-ID: Peter Bonivart writes: > On Wed, Jan 14, 2009 at 1:51 AM, Sebastian Kayser wrote: >> This would not only be interesting for the feedback, but also for >> pkg-get / pkgutil. Can they be forced to install a package from testing >> when the filename and version remain identical (which is per default the >> case for GAR builds done on the same day)? > > There's no --reinstall option in pkgutil but if you remove the package > you want to reinstall first, you will always get the latest one at the > next install if you don't have a caching problem in your proxy for > example. This could be helped with a build sequence number, as used in rpm and deb packages; this can be enforced in a build system such as gar, consequently two successive builds have different signatures --- btw, the package's md5 sum of the package offers such a thing. -- Peter From dam at opencsw.org Wed Jan 14 14:57:44 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 14 Jan 2009 14:57:44 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496CD341.2070104@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> Message-ID: <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> Hi Chad, Am 13.01.2009 um 18:45 schrieb Chad Harp: > Philip Brown wrote: >> dunno about libexslt. >> >> what package is that in? i guess lib xstl. >> >> rebuild, anyone? > > I've got a new xslt build in testing, its had good feedback so I'll go > ahead and move it to newpkgs. We should make libxslt and libxml2 look similar in terms of splitting _devel, python bindings and 64 bit support. I would recommend copying over the necessary descriptions from the libxml2 Makefile for package splitting etc. Please let me know if I can be of any help here. Best regards -- Dago From phil at bolthole.com Wed Jan 14 15:48:28 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 14 Jan 2009 06:48:28 -0800 Subject: [csw-maintainers] Call for testers In-Reply-To: References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> Message-ID: <20090114144828.GA91550@bolthole.com> On Wed, Jan 14, 2009 at 10:30:47AM +0100, Peter FELECAN wrote: > This could be helped with a build sequence number, as used in rpm and > deb packages; this can be enforced in a build system such as gar, > consequently two successive builds have different signatures --- btw, > the package's md5 sum of the package offers such a thing. or, gar could keep a record of built packages somewhere per-user, and do the yyyy.mm.dd.1, .2, .2 thing automatically From skayser at opencsw.org Wed Jan 14 17:33:38 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Wed, 14 Jan 2009 17:33:38 +0100 Subject: [csw-maintainers] New pkg in testing/: mbuffer 20090106 Message-ID: <496E13E2.7070601@opencsw.org> Hi all, i just uploaded a new package (simple binary + some docs) to testing/. If anyone would like to give it a try, feel free to do so. Feedback appreciated. http://mirror.opencsw.org/testing/mbuffer-20090106,REV=2009.01.14-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/mbuffer-20090106,REV=2009.01.14-SunOS5.8-sparc-CSW.pkg.gz mbuffer comes in handy when you do zfs send / recv over a network. You can put it in between the send and recv processes and it will provide a buffer that makes up for pauses in network or disk IO. Description from the mbuffer website: mbuffer is a tool to buffer data streams. Its special feature is to show the I/O rate and summary to the user. This was firstly the main reason I developed it. It is especially useful, if you are writing backups to fast tape drives or libraries. Those drives tend to stop and rewind if they have a buffer underrun. This so called tape screwing reduces the lifetime of the motors. mbuffer can prevent buffer underruns, if used correctly and speed up the whole backup process. Sebastian From trygvel at opencsw.org Wed Jan 14 19:38:53 2009 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 14 Jan 2009 19:38:53 +0100 Subject: [csw-maintainers] Call for testers In-Reply-To: <20090114144828.GA91550@bolthole.com> References: <89F15946-3C1F-460D-A032-BE78120E304D@opencsw.org> <20090113184251.GA34848@bolthole.com> <496D3722.7020004@opencsw.org> <625385e30901140108g5b5b16d2w4bbc52154817170c@mail.gmail.com> <20090114144828.GA91550@bolthole.com> Message-ID: <496E313D.5090903@opencsw.org> Philip Brown wrote: > On Wed, Jan 14, 2009 at 10:30:47AM +0100, Peter FELECAN wrote: >> This could be helped with a build sequence number, as used in rpm and >> deb packages; this can be enforced in a build system such as gar, >> consequently two successive builds have different signatures --- btw, >> the package's md5 sum of the package offers such a thing. > > or, gar could keep a record of built packages somewhere per-user, and > do the yyyy.mm.dd.1, .2, .2 thing automatically This really don't belong in the build tool IMO, but rather as a part of the submission process to a package queue (the testing queue in this case). Having a tool like Debian's dput [1]. [1]: http://www.digipedia.pl/man/dput.1.html -- Trygve From harpchad at opencsw.org Wed Jan 14 21:31:31 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 14 Jan 2009 14:31:31 -0600 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> Message-ID: <496E4BA3.9050507@opencsw.org> Sounds like a good idea, I'll get the packages split up. Dagobert Michelsen wrote: > Hi Chad, > > Am 13.01.2009 um 18:45 schrieb Chad Harp: >> Philip Brown wrote: >>> dunno about libexslt. >>> >>> what package is that in? i guess lib xstl. >>> >>> rebuild, anyone? >> I've got a new xslt build in testing, its had good feedback so I'll go >> ahead and move it to newpkgs. > > We should make libxslt and libxml2 look similar in terms > of splitting _devel, python bindings and 64 bit support. > I would recommend copying over the necessary descriptions > from the libxml2 Makefile for package splitting etc. > Please let me know if I can be of any help here. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Wed Jan 14 21:46:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 14 Jan 2009 21:46:02 +0100 Subject: [csw-maintainers] libtool files (Subject changed from: [csw-buildfarm] Updating libgpg_error to 1.7 now) In-Reply-To: <496E4BA3.9050507@opencsw.org> References: <324DBC51-FF01-480B-8FB4-D6129263C529@opencsw.org> <496CD0A6.1060105@opencsw.org> <20090113174124.GA48829@bolthole.com> <496CD341.2070104@opencsw.org> <238FA37D-B267-4A2E-B324-4679D4F51135@opencsw.org> <496E4BA3.9050507@opencsw.org> Message-ID: <06AE6DC8-BE0B-4CB6-AE58-41AAA88158CF@opencsw.org> Hi Chad, Am 14.01.2009 um 21:31 schrieb Chad Harp: > Dagobert Michelsen wrote: >> Am 13.01.2009 um 18:45 schrieb Chad Harp: >>> Philip Brown wrote: >>>> dunno about libexslt. >>>> >>>> what package is that in? i guess lib xstl. >>>> >>>> rebuild, anyone? >>> I've got a new xslt build in testing, its had good feedback so >>> I'll go >>> ahead and move it to newpkgs. >> >> We should make libxslt and libxml2 look similar in terms >> of splitting _devel, python bindings and 64 bit support. >> I would recommend copying over the necessary descriptions >> from the libxml2 Makefile for package splitting etc. >> Please let me know if I can be of any help here. > > Sounds like a good idea, I'll get the packages split up. Fine, and please file bug reports on the packages depending on libxslt to depend on libxslt_rt after release. Thanks and best regards -- Dago PS: Please avoid top-posting if possible :-) From william at wbonnet.net Thu Jan 15 21:04:39 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 21:04:39 +0100 Subject: [csw-maintainers] svn tags use and naming convention Message-ID: <496F96D7.3060703@wbonnet.net> Hi Do we have a standard for the use of tags, branches and associated naming ? If not i can propose one cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bwalton at opencsw.org Thu Jan 15 22:18:08 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 15 Jan 2009 16:18:08 -0500 Subject: [csw-maintainers] git on buildfarm Message-ID: <1232054103-sup-9301@ntdws12.chass.utoronto.ca> Hi All, Just a heads up that if you're interested in Git as an SCM tool, it's now on the build machines. I've also installed the emacs VCS module (M-x load-file RET /opt/csw/share/emacs/site-lisp/git.el; M-x git-status) and the svn gateway. I haven't played with the svn gateway yet (I plan to), so I won't tell you it's good or bad. If anyone is interested, I'll let you know of my experiences after trying it out with a GAR package description. Cheers, -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From william at wbonnet.net Thu Jan 15 22:32:39 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 22:32:39 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <496FAB77.8000208@wbonnet.net> Hi, Since OpenCSW is a pretty young project, if we consider the point of view of the new organization, website, tools, buildfarm, etc. there are a lot of things to do, to improve or to update. We will have to work of this different things, and we need some minimum coordination of effort. I was wondering about a way to make things happen and happen faster and to optimize effort. What about creating thematic months ? The proposal is to focus for a given month on a specific subject. Of course it does not mean that other subject cannot be processed or should not. It does not mean that it has to be mandatory. But it could help to define a roadmap, and create some motivation to work on given subject. For instance themes could be (just an example...) February : communication goal is to improve web site, add content, write presentation of the project and tools (, slides, etc. to produce all the material we will need to make presentation, improve google rank, communicate with Sun and other corporates, create links and relation with other open source project etc.) March : move package to GAR Kind of hacking session. Goal is to add to gar as much as possible of existing packages. This will go through maintainer training on how to use gar, to write and produce howto and tutorials (if needed because Dago already did a lot to create documentation) April : Package update Goal is to move to up to date version of as much as possible of existing packages May : Bug hunting Goal is to fix and close as many as possible of bugs and entries in mantis June : Continus integration Goal is to add to continuus integration as much as possible of existing package July : Build world Goal is to setup a procedure that will be used to rebuild every packages from an blank environment. August : Summer camp September : Mass porting and package creation Goal is to create as much as possible new packages. This include creating and processing requested package list, etc. October : To be defined November : To be defined December : General meeting ! Once we will have a frozen theme list and roadmap, this should be of course published on the web site and made publicly available. What about the idea ? Feedback welcomed ! cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From harpchad at opencsw.org Thu Jan 15 23:53:58 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 15 Jan 2009 16:53:58 -0600 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FAB77.8000208@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> Message-ID: <496FBE86.3030403@opencsw.org> I like the idea and I've got another theme for you (or perhaps and extension of the April theme): Clean up remaining libtool (*.la) files (even if it's just repackaging old builds). Somewhere in here should fit a release schedule for the stable branch. William Bonnet wrote: > Hi, > > Since OpenCSW is a pretty young project, if we consider the point of > view of the new organization, website, tools, buildfarm, etc. there are > a lot of things to do, to improve or to update. > > We will have to work of this different things, and we need some minimum > coordination of effort. I was wondering about a way to make things > happen and happen faster and to optimize effort. What about creating > thematic months ? > > The proposal is to focus for a given month on a specific subject. Of > course it does not mean that other subject cannot be processed or should > not. It does not mean that it has to be mandatory. But it could help to > define a roadmap, and create some motivation to work on given subject. > > > For instance themes could be (just an example...) > > February : communication > > goal is to improve web site, add content, write presentation of the > project and tools (, slides, etc. to produce all the material we will > need to make presentation, improve google rank, communicate with Sun and > other corporates, create links and relation with other open source > project etc.) > > March : move package to GAR > > Kind of hacking session. Goal is to add to gar as much as possible of > existing packages. This will go through maintainer training on how to > use gar, to write and produce howto and tutorials (if needed because > Dago already did a lot to create documentation) > > April : Package update > > Goal is to move to up to date version of as much as possible of > existing packages > > May : Bug hunting > > Goal is to fix and close as many as possible of bugs and entries in > mantis > > June : Continus integration > > Goal is to add to continuus integration as much as possible of > existing package > > July : Build world > > Goal is to setup a procedure that will be used to rebuild every > packages from an blank environment. > > August : Summer camp > > September : Mass porting and package creation > > Goal is to create as much as possible new packages. This include > creating and processing requested package list, etc. > > October : To be defined > > November : To be defined > > December : General meeting ! > > > Once we will have a frozen theme list and roadmap, this should be of > course published on the web site and made publicly available. > > What about the idea ? > > Feedback welcomed ! > > cheers > From william at wbonnet.net Thu Jan 15 23:01:05 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 23:01:05 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FBE86.3030403@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <496FBE86.3030403@opencsw.org> Message-ID: <496FB221.4010702@wbonnet.net> Hi > Somewhere in here should fit a release schedule for the stable branch. > Yes it is just a proposal, a first work version >> February : communication >> According to me it looks like the highest priority. We have to use the momentum we created and even increase it. It will also help to attract new members and maintainers. >> March : move package to GAR >> Looks to me better to have everything in GAR before starting to update and fix things. >> April : Package update >> I think it has to be done before bug hunting campaign. Update will fix some bug and create new one. So no need to spend to much time on fixing something we are going to update. Better test it and fix it after :) >> May : Bug hunting >> A prerequisite to next stable release ? >> June : Continus integration >> >> Should it be done before bug hunting and update ? Trygve any suggestion on the best way to use Hudson ? Cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From skayser at opencsw.org Fri Jan 16 00:16:21 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 16 Jan 2009 00:16:21 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496F96D7.3060703@wbonnet.net> References: <496F96D7.3060703@wbonnet.net> Message-ID: <496FC3C5.7060709@opencsw.org> William Bonnet wrote: > Do we have a standard for the use of tags, branches and associated naming ? > > If not i can propose one Me too :) I would love to see a tag for each package version that has been pushed to current/. Something along the way of: tags/4.4.20,REV=2009.01.13 This way one could know whether a GAR build description is just a stub or actually has been used to build a released package. Sebastian From william at wbonnet.net Thu Jan 15 23:29:23 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 15 Jan 2009 23:29:23 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <496FB8C3.2020508@wbonnet.net> Hi Sebastian > William Bonnet wrote: > >> Do we have a standard for the use of tags, branches and associated naming ? >> >> If not i can propose one >> > > Me too :) Cool. So i guess you are the taker ;) I have more than enough things in my todo list. > I would love to see a tag for each package version that has > been pushed to current/. Something along the way of: > > tags/4.4.20,REV=2009.01.13 > > This way one could know whether a GAR build description is just a stub > or actually has been used to build a released package. > I had quite the same idea. We have to think about the way it could be use in dependencies (from a make world point of view), and write some documentation to propose a standard. cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 01:08:18 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 15 Jan 2009 16:08:18 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FBE86.3030403@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <496FBE86.3030403@opencsw.org> Message-ID: <20090116000818.GA10797@bolthole.com> On Thu, Jan 15, 2009 at 04:53:58PM -0600, Chad Harp wrote: > I like the idea and I've got another theme for you (or perhaps and > extension of the April theme): Clean up remaining libtool (*.la) files > (even if it's just repackaging old builds). > > Somewhere in here should fit a release schedule for the stable branch. that is larger than a "theme for a month". it is a very large effort, that takes more than a month. and the first step, is someone volunteering to actually put it together. From bwalton at opencsw.org Fri Jan 16 01:22:40 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 15 Jan 2009 19:22:40 -0500 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <1232065192-sup-6659@ntdws12.chass.utoronto.ca> Excerpts from Sebastian Kayser's message of Thu Jan 15 18:16:21 -0500 2009: > tags/4.4.20,REV=2009.01.13 GAR is sticking the svn rev id into the PSTAMP portion of the pkginfo files, so for anything released as of Dago's implementation of this feature, the relevant info could be retrieved to start this off... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bonivart at opencsw.org Fri Jan 16 10:20:03 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 16 Jan 2009 10:20:03 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <496FAB77.8000208@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> Message-ID: <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> On Thu, Jan 15, 2009 at 10:32 PM, William Bonnet wrote: > Hi, > > Since OpenCSW is a pretty young project, if we consider the point of > view of the new organization, website, tools, buildfarm, etc. there are > a lot of things to do, to improve or to update. > > We will have to work of this different things, and we need some minimum > coordination of effort. I was wondering about a way to make things > happen and happen faster and to optimize effort. What about creating > thematic months ? > > The proposal is to focus for a given month on a specific subject. Of > course it does not mean that other subject cannot be processed or should > not. It does not mean that it has to be mandatory. But it could help to > define a roadmap, and create some motivation to work on given subject. Great idea! But how about starting with all the stuff in the agenda for the IRL meeting? If I'm correct, almost all of it was skipped due to time constraints but it's important and it's very quiet about it now. http://wiki.opencsw.org/irl-meeting -- /peter From dam at opencsw.org Fri Jan 16 12:03:48 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 16 Jan 2009 12:03:48 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <496FC3C5.7060709@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> Message-ID: <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> Hi, Am 16.01.2009 um 00:16 schrieb Sebastian Kayser: > William Bonnet wrote: >> Do we have a standard for the use of tags, branches and associated >> naming ? >> >> If not i can propose one > > Me too :) I would love to see a tag for each package version that has > been pushed to current/. Something along the way of: > > tags/4.4.20,REV=2009.01.13 > > This way one could know whether a GAR build description is just a stub > or actually has been used to build a released package. I would recommend using tags/-4.4.20,REV=2009.01.13 That way you get a decent directory name when you only check out that tag. I added a new target to make for making this as easy as possible: > dam at login [login]:/home/dam/mgar/pkg/libtasn1/trunk > gmake scm-tag- > release > /opt/csw/bin/svn cp ../trunk ../tags/libtasn1-1.7,REV=2009.01.16 > A ../tags/libtasn1-1.7,REV=2009.01.16 > dam at login [login]:/home/dam/mgar/pkg/libtasn1/trunk > You must still commit this, of course. Best regards -- Dago From dam at opencsw.org Fri Jan 16 12:20:09 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 16 Jan 2009 12:20:09 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> Message-ID: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> Hi Peter, Am 16.01.2009 um 10:20 schrieb Peter Bonivart: > Great idea! But how about starting with all the stuff in the agenda > for the IRL meeting? If I'm correct, almost all of it was skipped due > to time constraints but it's important and it's very quiet about it > now. > > http://wiki.opencsw.org/irl-meeting Yes, that was skipped, but as I browse the list a lot of it is already in progress. However, Williams' propositions go more into the direction of enhancing the quality of packages directly instead of tuning the process (which also should lead to better quality btw). Do you have a specific point which you want to have addressed or inserted into Williams agenda? Best regards -- Dago From william at wbonnet.net Fri Jan 16 12:20:14 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 12:20:14 +0100 Subject: [csw-maintainers] svn tags use and naming convention In-Reply-To: <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> References: <496F96D7.3060703@wbonnet.net> <496FC3C5.7060709@opencsw.org> <45D93A76-8CD6-4872-92B4-4A5342DA65AA@opencsw.org> Message-ID: <49706D6E.5000106@wbonnet.net> Hi > I would recommend using > tags/-4.4.20,REV=2009.01.13 > > That way you get a decent directory name when you only check out that > tag. > Right I am wondering if we should not even need something more precise and complex. It would be useful to be able to make a distinction in tags between version used in testing, unstable and stable. For instance i can imagine a process including steps from the following list (not now but in a few weeks or months). The maintainer create its package, tags it and release it to testing Then the "unstable catalog maker (aka Phil)" or whatever automatic procedure provided by continuus integation, build it (optional ?), tags it whith an "unstable" tag, and release it Then the stable release manager tags include a given version of the package in the stable release, and tags it. Even if contents are sometime the same (by content i mean packge creation scripts, etc.), the tags will have to be the same. So what about tags/-4.4.20,REV=2009.01.13-- source will be testing, unstable, or stable release version will be a "version number of the release" we can image that for stable it coulb be like REV=09/05 for stableversion release in May 2009, for unstable it could just be an incremental number in the year (ie week number), and for testing it can be up to he maintainer (sequential number, or beta1, beta2, etc. or default to 'sid' (still in development). This may need different targets ? just to make it simple to use and prevent argument errors creating a wrong tag > You must still commit this, of course. > Thanks :) cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Fri Jan 16 12:27:10 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 12:27:10 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> Message-ID: <49706F0E.2080004@wbonnet.net> Dagobert Michelsen a ?crit : > Hi Peter, > > Am 16.01.2009 um 10:20 schrieb Peter Bonivart: > >> Great idea! But how about starting with all the stuff in the agenda >> for the IRL meeting? If I'm correct, almost all of it was skipped due >> to time constraints but it's important and it's very quiet about it >> now. >> >> http://wiki.opencsw.org/irl-meeting >> > > Yes, that was skipped, but as I browse the list a lot of it > is already in progress. However, Williams' propositions go more > into the direction of enhancing the quality of packages > directly instead of tuning the process (which also should lead > to better quality btw). > Peter is right, this point have to be processed. But i think improving the process should be a background task. It is easier to gather some people to work on a specific more technical point, like moving packages to GAR or creating new packages, than to focus effort on the process improvement. Moreover, doing this, will make things easier for people having less time to contribute. But ... process is not forgotten :) If we want to setup this thematics agenda, some people will have to work on advance on the process. Each coming theme will raise discussion about the process improvement (what is missing, out dated, which documentation is missing etc.). This will have certainly to be done during the month before the theme (that's also why i propose to start by commnication, there is no process prerequisite). Running a "thematic event" can go through simple steps like : . week one we talk about what has to be done, . week 2 and 3 people work on different task, according to their free time, . week 4 everyone work is integrated, commited, tested and published That's just a general process. It will have to be tuned to fit the real life and may chance according to the subjects cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 15:48:04 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 16 Jan 2009 06:48:04 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49706F0E.2080004@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> Message-ID: <20090116144804.GB2576@bolthole.com> On Fri, Jan 16, 2009 at 12:27:10PM +0100, William Bonnet wrote: > > If we want to setup this thematics agenda, some people will have to work > on advance on the process. Each coming theme will raise discussion about > the process improvement (what is missing, out dated, which documentation > is missing etc.). This will have certainly to be done during the month > before the theme (that's also why i propose to start by commnication, > there is no process prerequisite). one of the biggest "challenges" about a volunteer organisation, is that you cant just write up a project agenda, and then assign people to do it. You need... volunteers! So, I would suggest that you first start with a wiki page on "here are themes I propose", then see if there are any extra ones proposed, and then see who signs up to handle/drive each of them. Finally, based on who is doing each bit, work out schedules for each. From william at wbonnet.net Fri Jan 16 22:13:13 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 22:13:13 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090116144804.GB2576@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> Message-ID: <4970F869.7060601@wbonnet.net> Hi Phil > one of the biggest "challenges" about a volunteer > organisation, is that you cant just write up a project agenda, and then > assign people to do it. You need... volunteers! > That's right ! I fully agree . In order to recruit volunteers we first have to set up the project. As you wrote below it comes through writing wiki page, and documentation and many thing else. Gathering volunteers also requires to be attractive. Being attractive often means to start the work on the project and to communicate about this until you reach a kind of "critical mass". It's not gonna be a easy thing, but i believe it is worth to try :) It will help to create the buzz around, it will help focusing some effort on mutual goal, and ... many things :) It is important to me that this project or themes or whatever you call it, must *not be* a mandatory thing or an exclusive thing. It has to be a kind of roadmap to highlight important task, to try to improve the quality of the packages and service we deliver. It should not prevent people to work on other things. > So, I would suggest that you first start with a wiki page on > "here are themes I propose", > then see if there are any extra ones proposed, > and then see who signs up to handle/drive each of them. > Finally, based on who is doing each bit, work out schedules for each. > For sure. It's a good advice. First of all i sent this email to see how people are feeling about this idea. I already had a few positive feedback, i will start to work on the wiki page in the next days. I can setup a couple things, but i'll need help :) and i'll ask for... Don't hesitate to comment more or give your opinion about this. And don't hesitate to submit your ideas for the agenda and discuss about subjects. Sometimes it is easier to discuss about this by email rather by editing wiki pages. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Fri Jan 16 23:22:36 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 16 Jan 2009 14:22:36 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4970F869.7060601@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> Message-ID: <20090116222236.GH70788@bolthole.com> On Fri, Jan 16, 2009 at 10:13:13PM +0100, William Bonnet wrote: >.. > don't hesitate to submit your ideas for the agenda and discuss about > subjects. Sometimes it is easier to discuss about this by email rather > by editing wiki pages. definately. email can be good for discussion; wikis are good for condensing what was actually agreed to in the discussion From william at wbonnet.net Fri Jan 16 22:26:12 2009 From: william at wbonnet.net (William Bonnet) Date: Fri, 16 Jan 2009 22:26:12 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090116222236.GH70788@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <20090116222236.GH70788@bolthole.com> Message-ID: <4970FB74.1030804@wbonnet.net> Hi Phil > definately. email can be good for discussion; > wikis are good for condensing what was actually agreed to in the discussion > We do share the same point of view. I'll initialize the wiki about this in the next days. It should be this week end. I wait until saturday night (CET) for comments, then i start to write a sum up. cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Sat Jan 17 11:09:47 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 17 Jan 2009 11:09:47 +0100 Subject: [csw-maintainers] Mantis e-mail working? Message-ID: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> I recently filed this bug, http://www.opencsw.org/mantis/view.php?id=2981, but didn't get a notification via e-mail. Now I wonder if James got one? I have also noted before (via Dago's buglist) that I had bugs filed against my packages that I had not received a notification for and so didn't know about. -- /peter From james at opencsw.org Sat Jan 17 11:37:55 2009 From: james at opencsw.org (James Lee) Date: Sat, 17 Jan 2009 10:37:55 GMT Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> Message-ID: <20090117.10375500.3265564087@gyor.oxdrove.co.uk> On 17/01/09, 10:09:47, Peter Bonivart wrote regarding [csw-maintainers] Mantis e-mail working?: > I recently filed this bug, > http://www.opencsw.org/mantis/view.php?id=2981, but didn't get a > notification via e-mail. Now I wonder if James got one? Nothing received - hence my lack of action. (Sorry about the typo in the bug. I'll fix it.) James. From bonivart at opencsw.org Sat Jan 17 12:07:56 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 17 Jan 2009 12:07:56 +0100 Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <20090117.10375500.3265564087@gyor.oxdrove.co.uk> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> <20090117.10375500.3265564087@gyor.oxdrove.co.uk> Message-ID: <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> On Sat, Jan 17, 2009 at 11:37 AM, James Lee wrote: > Nothing received - hence my lack of action. > > (Sorry about the typo in the bug. I'll fix it.) Your bug is tiny, Mantis not sending notifications (again?) is a much larger issue. :-) -- /peter From james at opencsw.org Sat Jan 17 12:35:18 2009 From: james at opencsw.org (James Lee) Date: Sat, 17 Jan 2009 11:35:18 GMT Subject: [csw-maintainers] Mantis e-mail working? In-Reply-To: <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> References: <625385e30901170209o12d812c7r10aaebcebd2cbdc7@mail.gmail.com> <20090117.10375500.3265564087@gyor.oxdrove.co.uk> <625385e30901170307n2337685bgb4c937ade968ccd7@mail.gmail.com> Message-ID: <20090117.11351800.2247806400@gyor.oxdrove.co.uk> On 17/01/09, 11:07:56, Peter Bonivart wrote regarding Re: [csw-maintainers] Mantis e-mail working?: > > (Sorry about the typo in the bug. I'll fix it.) > Your bug is tiny, Indeed, but unlike mantis it's within my power to fix and I have fixed it. > Mantis not sending notifications (again?) is a much > larger issue. :-) Indeed... From dam at opencsw.org Sun Jan 18 13:23:53 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 13:23:53 +0100 Subject: [csw-maintainers] New maintainer for Mantis installation Message-ID: Hi, Sebastian volunteered to maintain the Mantis installation, update it, tune it and make sure emails are sent properly. He already maintained other mantis installation in the past, so I have no doubt he does a great job. Ihsan, Phil: Please make sure he gets the proper access rights to do the job. Thanks! -- Dago From skayser at opencsw.org Sun Jan 18 13:48:43 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 13:48:43 +0100 Subject: [csw-maintainers] New maintainer for Mantis installation In-Reply-To: References: Message-ID: <4973252B.1080203@opencsw.org> Hi Dago, Dagobert Michelsen wrote: > Sebastian volunteered to maintain the Mantis installation, update it, > tune it and make sure emails are sent properly. He already maintained > other mantis installation in the past, so I have no doubt he does a > great job. just some small amendments: * Will do so, given that the people who took care of Mantis up to now, are ok with it. * Priority list (from my point of view): Make sure emails are sent out properly, update it, tune it. Has been about two years since i had a Mantis installation in my hands, so don't expect magical things to happen right away. Will have to dig into my documentation, distant memories, and the Mantis manual first. Sebastian From skayser at opencsw.org Sun Jan 18 14:15:20 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 14:15:20 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4970F869.7060601@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> Message-ID: <49732B68.4090105@opencsw.org> William Bonnet wrote: >> one of the biggest "challenges" about a volunteer >> organisation, is that you cant just write up a project agenda, and then >> assign people to do it. You need... volunteers! >> > That's right ! I fully agree > . > In order to recruit volunteers we first have to set up the project. As > you wrote below it comes through writing wiki page, and documentation > and many thing else. Gathering volunteers also requires to be > attractive. Being attractive often means to start the work on the > project and to communicate about this until you reach a kind of > "critical mass". It's not gonna be a easy thing, but i believe it is > worth to try :) > > It will help to create the buzz around, it will help focusing some > effort on mutual goal, and ... many things :) I like Williams ideas very much, especially the mutual goal part. Right now people are moving the project forward by producing bugfixed and updated packages. That's great, but not the whole story. Williams ideas try to capture all the other areas where work can be done to move the project forward. Given that these ideas are communicated, discussed, and packaged in doable "let's first do this and then move on to the next one" items, the right people can get together to make things happen in a joint effort. IMHO it's worth giving it a go. Sebastian From bonivart at opencsw.org Sun Jan 18 15:40:46 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 15:40:46 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49732B68.4090105@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> Message-ID: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> On Sun, Jan 18, 2009 at 2:15 PM, Sebastian Kayser wrote: > I like Williams ideas very much, especially the mutual goal part. Right > now people are moving the project forward by producing bugfixed and > updated packages. That's great, but not the whole story. Williams ideas > try to capture all the other areas where work can be done to move the > project forward. I also like William's ideas and you're right about us only updating packages now. However, I don't think this new theme idea captures "all" areas where we need improvement. There's fundamental things in the community that needs to open up if we're going to attract more people to join (or come back). It's my belief that those issues are avoided. There's only so much you can do with ten people. -- /peter From dam at opencsw.org Sun Jan 18 15:56:23 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 15:56:23 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <49706F0E.2080004@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> Message-ID: Hi William, Am 16.01.2009 um 12:27 schrieb William Bonnet: > If we want to setup this thematics agenda, some people will have to > work > on advance on the process. Each coming theme will raise discussion > about > the process improvement (what is missing, out dated, which > documentation > is missing etc.). This will have certainly to be done during the month > before the theme (that's also why i propose to start by commnication, > there is no process prerequisite). > > Running a "thematic event" can go through simple steps like : > . week one we talk about what has to be done, > . week 2 and 3 people work on different task, according to their > free time, > . week 4 everyone work is integrated, commited, tested and published > > That's just a general process. It will have to be tuned to fit the > real > life and may chance according to the subjects I think that the thematics month proposal is a great and truly useful idea. You have my full support for taking the stake on these things. The order makes sense, removing libtools files can be done at the "removing bugs" month. Having the new website first would be good as the progress could be generally visible blogged on the front page. Do you think you can do that first? Best regards -- Dago From dam at opencsw.org Sun Jan 18 15:59:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 15:59:27 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: Hi Peter, Am 18.01.2009 um 15:40 schrieb Peter Bonivart: > I also like William's ideas and you're right about us only updating > packages now. However, I don't think this new theme idea captures > "all" areas where we need improvement. > > There's fundamental things in the community that needs to open up if > we're going to attract more people to join (or come back). It's my > belief that those issues are avoided. Are you talking about this or this? We already have addressed some of the points. If you have issues that you really want to have done please name them so we can try do resolve these fast-tracked if possible. Best regards -- Dago From bonivart at opencsw.org Sun Jan 18 16:15:35 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 16:15:35 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <625385e30901180715g65b23d34s2d6f871b533c46fd@mail.gmail.com> On Sun, Jan 18, 2009 at 3:59 PM, Dagobert Michelsen wrote: > Are you talking about this > > or this? > > > We already have addressed some of the points. If you have > issues that you really want to have done please name them > so we can try do resolve these fast-tracked if possible. If I could take a pick I would choose the Release Process and the Maintainers sections from the Suggestion-page on the wiki. Those are single point of failures today so to speak. -- /peter From phil at bolthole.com Sun Jan 18 17:47:18 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 08:47:18 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <20090118164717.GC81262@bolthole.com> On Sun, Jan 18, 2009 at 03:40:46PM +0100, Peter Bonivart wrote: > > There's fundamental things in the community that needs to open up if > we're going to attract more people to join (or come back). It's my > belief that those issues are avoided. Actually, we've been having new people join already. Two more are pending. The main thing holding up the new people, is just trying to put together a new "add new accounts" procedure between Ihsan, Dago, and myself. btw: to my recollection, at the meeting in switzerland, we looked briefly at every issue on the wiki flagged for discussion. Many of them were judged to be "handled already" From pfelecan at opencsw.org Sun Jan 18 20:23:11 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 18 Jan 2009 20:23:11 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: (Dagobert Michelsen's message of "Sun\, 18 Jan 2009 15\:59\:27 +0100") References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: Dagobert Michelsen writes: > Are you talking about this > > or this? > > > We already have addressed some of the points. If you have > issues that you really want to have done please name them > so we can try do resolve these fast-tracked if possible. Sorry to jump on this but, in my opinion, both referenced documents are of interest. If you addressed the issues why don't you publish an answer to each one, on the same page, this way we can see what's still undecided and can add to William topics; we can even discuss them here. my 7x10^13 cents -- Peter From phil at bolthole.com Sun Jan 18 20:48:10 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 11:48:10 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> Message-ID: <20090118194810.GE81262@bolthole.com> On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: > If you addressed the issues why don't you publish an answer to each > one, on the same page, this way we can see what's still undecided and > can add to William topics; we can even discuss them here. > I'll let the secretary do that ;-) From dam at opencsw.org Sun Jan 18 21:17:29 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 21:17:29 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118194810.GE81262@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> Message-ID: Fellow maintainers, Am 18.01.2009 um 20:48 schrieb Philip Brown: > On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: >> If you addressed the issues why don't you publish an answer to each >> one, on the same page, this way we can see what's still undecided and >> can add to William topics; we can even discuss them here. Good point Peter. > I'll let the secretary do that ;-) I'll take care of that. Best regards -- Dago From dam at opencsw.org Sun Jan 18 21:19:35 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 21:19:35 +0100 Subject: [csw-maintainers] Perl module handling changed in mGAR v2 Message-ID: Hi, with r2853 the handling of files in Perl modules (category "cpan") has changed. Now the files .*/perllocal\.pod .*/\.packlist are excluded by default during merge in mGAR v2. The behaviour in mGAR v1 is unchanged as there is no merge-phase. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 21:32:37 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 21:32:37 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118164717.GC81262@bolthole.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> Message-ID: <497391E5.1070700@opencsw.org> Philip Brown wrote: > On Sun, Jan 18, 2009 at 03:40:46PM +0100, Peter Bonivart wrote: >> There's fundamental things in the community that needs to open up if >> we're going to attract more people to join (or come back). It's my >> belief that those issues are avoided. > > Actually, we've been having new people join already. Two more are pending. > The main thing holding up the new people, is just trying to put together a > new "add new accounts" procedure between Ihsan, Dago, and myself. > > btw: to my recollection, at the meeting in switzerland, we looked briefly > at every issue on the wiki flagged for discussion. Many of them were judged > to be "handled already" I recall the same. A few was "handled already", other where "almost done" (like lots of the GAR stuff). Some of the matters are internal stuff (like the exact details of the release process), but most of them are public and should probably be moved to William's page (with a status note if applicable). -- Trygve From bonivart at opencsw.org Sun Jan 18 22:07:19 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 22:07:19 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497391E5.1070700@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> Message-ID: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: > I recall the same. A few was "handled already", other where "almost > done" (like lots of the GAR stuff). Some of the matters are internal > stuff (like the exact details of the release process), but most of them > are public and should probably be moved to William's page (with a status > note if applicable). The technical stuff is not the problem, I'm not worried about that. What worries me, even more after your post, is that there seems to be some unexplainable need for secrecy. Why does the release process need to be handled internally? And what does that mean? The board? Are you involved? Why aren't the rest of us worthy of knowing what goes on? I hear that it's being handled but I simply don't believe it until I see it. -- /peter From dam at opencsw.org Sun Jan 18 22:34:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 22:34:27 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <1DB4522F-B6DD-44D3-8DF1-1D50315ED5A0@opencsw.org> Hi Peter, Am 18.01.2009 um 22:07 schrieb Peter Bonivart: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l > wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of >> them >> are public and should probably be moved to William's page (with a >> status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? There is no need for it to be handled internally. Explanations are given in www.opencsw.org:/home/newpkgs/README in addition to individual emails to the maintainers. I'll write all that up during the week. > And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? Well, I of course feel myself well informed. We could enhance the process with email-pings to maintainers@ or anything else that makes it more visible any time if the members feel that this is needed. That it is not done is not rooted in that we don't want it - it is not that easy to just post the right amount of data. If you feel the need please post, kick the board, kick me, kick Ihsan, kick Phil. It's our obligation to do this decently. But making everyone happy is not an easy task ;-) > I hear that it's being handled but I simply don't believe it until I > see it. Ok. Point taken. Please: Kick again if this is not implemented with your full satisfaction. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 22:34:38 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 22:34:38 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <4973A06E.6040906@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of them >> are public and should probably be moved to William's page (with a status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? Come one, there is no secrecy. I meant internally as on the maintainers@ list, not publicly on devel at . > I hear that it's being handled but I simply don't believe it until I see it. I'm not sure of any specific stuff going on with the release process, but if you have specific issues that need to be handled please note those down on the page that you've already started. From what I can tell the major point WRT to the release process is getting every rule written down or put into code as a part of chkpkg. -- Trygve From phil at bolthole.com Sun Jan 18 22:56:02 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 13:56:02 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A06E.6040906@opencsw.org> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> Message-ID: <20090118215602.GB56431@bolthole.com> On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: > From what I can tell the major point WRT to the release process is > getting every rule written down or put into code as a part of chkpkg. And that is intrinsically impossible. It is impossible to write down EVERYTHING, just as it is impossible to write a computer program to automatically write any new computer program you want. It's impossible to code checkpkg to cover "everything". It's a little easier to write down descriptions of what things not covered by checkpkg should look like. But there will always be exceptoins. At some point, there always comes a need for a human being to make a decision of "yes this is acceptible/no this is not". Peter seems to want to completely eliminate any human inspection of packages. I say that this is not possible. Given that I have been inspecting packages for 6 years now, I hope that the majority of people will trust my experience on this. I'll agree there is some room for improvement, though. m From dam at opencsw.org Sun Jan 18 22:59:25 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 18 Jan 2009 22:59:25 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> Hi, Am 18.01.2009 um 22:56 schrieb Philip Brown: > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: >> From what I can tell the major point WRT to the release process is >> getting every rule written down or put into code as a part of chkpkg. > > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will > trust > my experience on this. That's why Trygve said "written down" *or* "put into code" :-) The rules just shouldn't be arbitrary. Best regards -- Dago From trygvis at opencsw.org Sun Jan 18 22:59:53 2009 From: trygvis at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Sun, 18 Jan 2009 22:59:53 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <4973A659.8060506@opencsw.org> Philip Brown wrote: > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: >> From what I can tell the major point WRT to the release process is >> getting every rule written down or put into code as a part of chkpkg. > > And that is intrinsically impossible. It is impossible to write down > EVERYTHING, just as it is impossible to write a computer program to > automatically write any new computer program you want. > It's impossible to code checkpkg to cover "everything". > It's a little easier to write down descriptions of what > things not covered by checkpkg should look like. But there will always > be exceptoins. > At some point, there always comes a need for a human being to make a > decision of "yes this is acceptible/no this is not". > Peter seems to want to completely eliminate any human inspection of > packages. Peter's point is that he want more than one person to decide. > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will trust > my experience on this. > > I'll agree there is some room for improvement, though. Continuous improvement is important and all I'm asking for. In particular for a volunteer-based project like OpenCSW it is important to keep the changes small so that they can be realized, but at the same time never stop to improve and become better. -- Trygve From phil at bolthole.com Sun Jan 18 23:03:53 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 14:03:53 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <5C2CD8C0-EA4F-409E-94A5-9F65529D4C1B@opencsw.org> Message-ID: <20090118220353.GE56431@bolthole.com> On Sun, Jan 18, 2009 at 10:59:25PM +0100, Dagobert Michelsen wrote: > Hi, > > Am 18.01.2009 um 22:56 schrieb Philip Brown: > > On Sun, Jan 18, 2009 at 10:34:38PM +0100, Trygve Laugst?l wrote: > >> From what I can tell the major point WRT to the release process is > >> getting every rule written down or put into code as a part of chkpkg. > > > > I say that this is not possible. Given that I have been inspecting > > packages for 6 years now, I hope that the majority of people will > > trust > > my experience on this. > > That's why Trygve said "written down" *or* "put into code" :-) > The rules just shouldn't be arbitrary. you trimmed too much :-) I tried to convey that we can reasonably cover, lets say, 80% of cases through checkpkg, and 95% of cases via "written down", but there's always going to be a grey area left. Either that, or our "standards documentation" will become so ludicrously large, that it will become effectively USELESS. There *is* such a thing as "too much information", sometimes :-} Once a doc reaches a certain size, people stop reading it entirely. It's at that point already for some people. From bonivart at opencsw.org Sun Jan 18 23:03:32 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:03:32 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A06E.6040906@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> Message-ID: <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> On Sun, Jan 18, 2009 at 10:34 PM, Trygve Laugst?l wrote: > Come one, there is no secrecy. Yes, there is. I don't know how the release process works (from submission to hitting the mirrors) or how maintainers are selected. I would like to have full disclosure on that, only then can we have input from the community on how to improve stuff. If we don't invite the community to take part we can't expect the community to grow. -- /peter From bonivart at opencsw.org Sun Jan 18 23:12:17 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:12:17 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118215602.GB56431@bolthole.com> References: <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> Message-ID: <625385e30901181412g8ff433fo99de7557cd46e31a@mail.gmail.com> On Sun, Jan 18, 2009 at 10:56 PM, Philip Brown wrote: > Peter seems to want to completely eliminate any human inspection of > packages. You don't have to guess (wrongly) what I want. I have written it down here: http://wiki.opencsw.org/suggestions > I say that this is not possible. Given that I have been inspecting > packages for 6 years now, I hope that the majority of people will trust > my experience on this. Computers are not good at handling new problems but they don't let old ones slip by. > I'll agree there is some room for improvement, though. Yes, there is but what are you going to do about but keep stalling? Disclosing the process and inviting more people to check packages would be a good start. I'm sure we would get a lot more ideas from there. -- /peter From phil at bolthole.com Sun Jan 18 23:14:28 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 14:14:28 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <4973A659.8060506@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> Message-ID: <20090118221428.GF56431@bolthole.com> On Sun, Jan 18, 2009 at 10:59:53PM +0100, Trygve Laugst??l wrote: > > Peter's point is that he want more than one person to decide. Decide what? More than one person to decide what actually gets written down as standards? More than one person, in case the primary person is on vacation or ill? Or to play a game of "well, mom said I cant, so I'll go ask dad instead"? I dont think that playing games like that is beneficial to the quality of CSW packages. But that seems to be what Peter is aiming for, since the other cases are Already Handled. In my opinion, it would be a bad thing, to have one set of packages that are put into "current" via one person, that have strict consistency to them, and then have another set of packages, allowed to go into current by a different person, that did not have consistency to them. That is my opinion. Now that we have a whole definition of "membership" in the "OpenCSW association", perhaps we can have a format vote to see how many people share my opinion, and settle this issue. From skayser at opencsw.org Sun Jan 18 23:18:54 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Sun, 18 Jan 2009 23:18:54 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> Message-ID: <4973AACE.3080309@opencsw.org> Hi Peter, Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 9:32 PM, Trygve Laugst?l wrote: >> I recall the same. A few was "handled already", other where "almost >> done" (like lots of the GAR stuff). Some of the matters are internal >> stuff (like the exact details of the release process), but most of them >> are public and should probably be moved to William's page (with a status >> note if applicable). > > The technical stuff is not the problem, I'm not worried about that. > What worries me, even more after your post, is that there seems to be > some unexplainable need for secrecy. Why does the release process need > to be handled internally? And what does that mean? The board? Are you > involved? Why aren't the rest of us worthy of knowing what goes on? good that you bring the secrecy concern up. It might be of concern to others as well. Maybe more detailed communication about how exactly the meeting was taking place and what all of us took away from it could have been helpful to avoid that assumption. So here we go, from my humble point of view: First of all, there is no hidden agenda, no secrecy, no Pinky and Brain world domination theories, no nothing. Maybe Othmar could jump in, who as a then-OpenCSW-user attended the meeting and volunteered to take the "protocol" during the meeting. It should have been pretty obvious from his point of view (as a bystander), what was going on. Take about 10 engineers, throw them into a room and let them talk about organizational stuff like the bylaws and you will realize very soon, that it will take a lot of (partly painful) time to figure out things. Put on top that people are all very excited about how to improve certain aspects of the project and you will find yourself in very interesting discussions, with _lots_ of different aspects. However, it's not until close to the end of the day and heaps of cups of coffee later that you realize that on the one hand the bylaws are finalized (*whopee*), but a lot of other things could have used a more stringent dealing with and you wish you had Sunday to talk everything over again. > I hear that it's being handled but I simply don't believe it until I see it. So when others say that they remember your suggestions being handled during the Saturday i think it is because some of them were touched, but less in a "now take two hours to deal with Peter's suggestions" way than in a "part of the whole discussion" way. This goes for most of the technical stuff also by the way. When Alexander Maier and i went to the meeting, one of the major reasons was to hear the technical GAR session from Dago. We didn't even get as far as that (and GAR had been scheduled for 14:00). Needless to say that tangible results besides the written bylaws were blurred in the fuss of all that has been discussed. At least from my point of view. Someone correct me please in case they feel otherwise. Still it was very nice to meet the other people and to realize that maybe next time a better organized and less packed schedule, attendees with less exhaustion from traveling, and maybe a moderator could be useful. :) With William setting up thematic months and the activeness we have on the maintainers list right now i think it should not be a problem to bring up certain points up again (especially any concerns about secrecy), get them discussed and formalized in a way. Sebastian From trygvis at opencsw.org Sun Jan 18 23:36:23 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 18 Jan 2009 23:36:23 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> Message-ID: <4973AEE7.1020905@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 10:34 PM, Trygve Laugst?l wrote: >> Come one, there is no secrecy. > > Yes, there is. I don't know how the release process works (from > submission to hitting the mirrors) or how maintainers are selected. I > would like to have full disclosure on that, only then can we have > input from the community on how to improve stuff. If we don't invite > the community to take part we can't expect the community to grow. Thanks for getting very specific! Phil: would you mind noting down an overview of how the process is? If it already is noted down, I'm sure Peter can point out what he feel that is missing and then those points can be fixed. Dagobert: could you publish the notes on the site describing the rules and requirements for membership? That would be very useful for newcomers to know -- Trygve From bonivart at opencsw.org Sun Jan 18 23:39:39 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 18 Jan 2009 23:39:39 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090118221428.GF56431@bolthole.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> Message-ID: <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> On Sun, Jan 18, 2009 at 11:14 PM, Philip Brown wrote: > I dont think that playing games like that is beneficial to the quality of > CSW packages. But that seems to be what Peter is aiming for, since the > other cases are Already Handled. I wouldn't call disclosing the process and sharing the load playing games but it's nice to hear your view of it. > In my opinion, it would be a bad thing, to have one set of packages that > are put into "current" via one person, that have strict consistency to them, > and then have another set of packages, allowed to go into current > by a different person, that did not have consistency to them. There's really no defence to your single of point of failure strategy. You're just getting desperate and now you're insulting anyone wanting to help even before they get a chance. Do you really think that no one can do what you do? Blastwave does fine without your help, I have made an alternative to pkg-get and Dago basically does what you when it comes to the current versus testing repos. You're defending your position with secrecy and discrediting. > That is my opinion. Now that we have a whole definition of "membership" > in the "OpenCSW association", perhaps we can have a format vote to > see how many people share my opinion, and settle this issue. Sysadmins tend to go for redundancy and load balancing when given a choice. Let's hope most of us are sysadmins and not pointy-haired-bosses. -- /peter From skayser at opencsw.org Mon Jan 19 00:42:17 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Mon, 19 Jan 2009 00:42:17 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> Message-ID: <4973BE59.6040102@opencsw.org> Peter Bonivart wrote: > On Sun, Jan 18, 2009 at 11:14 PM, Philip Brown wrote: >> I dont think that playing games like that is beneficial to the quality of >> CSW packages. But that seems to be what Peter is aiming for, since the >> other cases are Already Handled. > > I wouldn't call disclosing the process and sharing the load playing > games but it's nice to hear your view of it. > >> In my opinion, it would be a bad thing, to have one set of packages that >> are put into "current" via one person, that have strict consistency to them, >> and then have another set of packages, allowed to go into current >> by a different person, that did not have consistency to them. > > There's really no defence to your single of point of failure strategy. > You're just getting desperate and now you're insulting anyone wanting > to help even before they get a chance. Do you really think that no one > can do what you do? Blastwave does fine without your help, I have made > an alternative to pkg-get and Dago basically does what you when it > comes to the current versus testing repos. You're defending your > position with secrecy and discrediting. Just some questions, because i have never been in the position and i would like to understand the discussion: Has the release process with Phil as the single point of getting packages into current shown a major bottleneck so far? Or is it the manual nature (effort on the maintainers side) of the release process? Did packages get rejected out of uncertain or non-understandable reasons? Do we have a truck factor issue with Phil as the only path to current at the moment? What's the exact pain that is trying to be cured? Sebastian From phil at bolthole.com Mon Jan 19 00:52:07 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 18 Jan 2009 15:52:07 -0800 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: <4973AEE7.1020905@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> Message-ID: <20090118235207.GA79582@bolthole.com> On Sun, Jan 18, 2009 at 11:36:23PM +0100, Trygve Laugst?l wrote: > ... > Phil: would you mind noting down an overview of how the process is? If > it already is noted down, I'm sure Peter can point out what he feel that > is missing and then those points can be fixed. Reguarding the release process: there's really very little to it that isnt already documented. Here's a description for you right now. again. I seem to recall I wrote this up for the maintainers list, but it's easier for me to write it here again than seach for it. But I'll change the subject line so it's easier to search in the future. Once a package is put in newpkgs by the maintainer, I look it over to see if there's any "gotchas" to it, and run checkpkg on it. If everything looks good, then I run a silly little "registerpkg" script to add it to a trivial mysql table. I also add an area to mantis for it if there isnt one already. This script is sitting easily accessible to Ihsan in my home directory on www.opencsw.org Beyond that, I run a catalog update script and sign it. Peter is already INTIMATELY familiar with this step, since he decided to write his own utility to do exactly the same thing for blastwave. Then, its a simple matter of "rsync to our master site, and we're done". ...... There's no "big hidden mystery". Its all pretty obvious. As I noted above, Peter is already very familar with one of the more complicated bits, since he replicated it himself for blastwave, after the split!! So his big complaints about "I dont understand what's going on" seem rather disengenuous to me. Peter wrote in his own email, > There's really no defence to your single of point of failure strategy. There is no single point of failure through me; this has been addressed already. If I got run over by a bus tomorrow, opencsw could continue to release packages, without any noticable impact to users. No need to change keys, everything would look the same to them: James has the signing key; Ihsan and Dago have access to the databases, and the "registerpkg" script, which is just sitting there in my directory on www. Peter knows this already. It seems like this fuss is really all about him not liking to get MY approval for HIS packages, and he wants to go through someone else, or better yet, not have to go through anyone to double-check his work. He keeps claiming it's about "single point of failure", but as I have pointed out, on here, and at the in-person meeting, That Has Been Handled Already. And everyone at the meeting agreed, so we moved on. Doesnt that match your recollection, Trygve? From bonivart at opencsw.org Mon Jan 19 01:11:55 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 19 Jan 2009 01:11:55 +0100 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: <20090118235207.GA79582@bolthole.com> References: <20090116144804.GB2576@bolthole.com> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> Message-ID: <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> On Mon, Jan 19, 2009 at 12:52 AM, Philip Brown wrote: > Beyond that, I run a catalog update script and sign it. > Peter is already INTIMATELY familiar with this step, since he decided to > write his own utility to do exactly the same thing for blastwave. That's just not true. I wrote a simple catalog building script which everyone can use. Dennis tried it but I have no idea if he's going to use it regularly or not, he hasn't so far. It has nothing to do with signing and creating mirror content. Dennis was doing fine before I did my script which was meant for local users. > Peter knows this already. It seems like this fuss is really all about > him not liking to get MY approval for HIS packages, and he wants to go > through someone else, or better yet, not have to go through anyone > to double-check his work. Actually I didn't know most of that already but thanks for sharing it. Maybe you would be so kind as to write it on the wiki or on the main site? What I have suggested, not that you seem to care what I actually say when replying, is that I want a group of people handling the release process. We shouldn't e-mail your personal address and be kept in the dark until you decide to reply. What you have against a web app for tracking the testing/release process baffles me. We could create a ticket there, mark our testing already done, others can check in their testing of the package, the release group can assign the packet to one of them and the rest will know that. Not only will maintainers know better what is and is not happening with their packages, I think it will encourage testing as well. -- /peter From Murray.Jensen at csiro.au Mon Jan 19 12:36:51 2009 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Mon, 19 Jan 2009 22:36:51 +1100 Subject: [csw-maintainers] The release process: a write-up In-Reply-To: Your message of "Mon, 19 Jan 2009 11:11:55 +1100" <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> Message-ID: <25061.1232365011@gerd> On Mon, 19 Jan 2009 11:11:55 +1100, Peter Bonivart writes: >What I have suggested, not that you seem to care what I actually say >when replying, is that I want a group of people handling the release >process. We shouldn't e-mail your personal address and be kept in the >dark until you decide to reply. > >What you have against a web app for tracking the testing/release >process baffles me. We could create a ticket there, mark our testing >already done, others can check in their testing of the package, the >release group can assign the packet to one of them and the rest will >know that. Not only will maintainers know better what is and is not >happening with their packages, I think it will encourage testing as >well. While I am uncomfortable with the antagonistic way that Peter expresses himself towards you all the time Phil, this approach seems reasonable to me. I have a vague recollection of suggesting something similar myself in the past during the "split". I don't see it as a burning issue though, just something that should be worked towards. We should at least talk about it, and maybe see if anyone can put the time in to develop this "web app". Shouldn't be too difficult with modern technology :-) Cheers! Murray... From glaw at opencsw.org Tue Jan 20 00:32:08 2009 From: glaw at opencsw.org (Gary Law) Date: Mon, 19 Jan 2009 23:32:08 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <4973BE59.6040102@opencsw.org> References: <20090116144804.GB2576@bolthole.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: Dago wrote: > There is no need for it to be handled internally. > Explanations are given in www.opencsw.org:/home/newpkgs/README Not sure what you mean there, but http://opencsw.org/home/newpkgs/READMEdoesn't exist, nor does [/export]/home/newpkgs/README on login.bo.opencsw.org. Trygve wrote: > From what I can tell the major point WRT to the release process is getting > every rule written down or put into code as a part of chkpkg. +1 Peter wrote: > It's impossible to code checkpkg to cover "everything". This is not an argument against automated testing. Well, it is actually an /argument/ against automated testing, but a really bad one. The whole world of software development these days seems to have accepted that automated testing is good, and should be used to the maximum extent possible. We should try and code tests for every possible reason to reject a package (and document this too). >But there will always be exceptoins. > At some point, there always comes a need for a human being to make a decision > of "yes this is acceptible/no this is not". I disagree. If something passes all the testing, why not release it? The project board might want to retain a long-stop power to pull software that was defective in some previously unheard of, and therefore untested for, way. Other than that maintainers should be able to say "this is good to go", provided it meets the published standard. Personally, I would also restrict this to automated builds that run off a gar or similar system, so hudson (or similar) does the build on the basis of a published make/spec file, and the testing/approval is fully automated. > Peter seems to want to completely eliminate any human inspection of packages. There is an interesting parallel with a discussion at my workplace just this week. Some admins want to retain manual builds for much of the software stack. I want to see everything that can be automated. The tools are there, and I feel the benefits are clear. It seems OpenCSW is now having the same conversation. > I say that this is not possible. It is definitely possible. Do the benefits outweigh the disadvantages? I'd say yes. Peter then wrote: > I tried to convey that we can reasonably cover, lets say, 80% of cases through > checkpkg, and 95% of cases via "written down", but there's always going to be > a grey area left. Either that, or our "standards documentation" will become so > ludicrously large, that it will become effectively USELESS Reasons for rejecting packages need to be documented and agreed upon, not subject to arbitary decisions. If the documentation gets too large... let's cross that bridge then. I don't see excessive documentation weighing down MacPorts or Fedora Packages or whatever. The "grey area" is just the exercise of individual discretion, and we should be looking to eliminate that from the quality control process. Peter wrote some more: > Decide what? > More than one person to decide what actually gets written down as standards? > More than one person, in case the primary person is on vacation or ill? > Or to play a game of "well, mom said I cant, so I'll go ask dad instead"? The standards should be agreed on by the board at the minimum, maybe the whole membership should vote on it. > In my opinion, it would be a bad thing, to have one set of packages that > are put into "current" via one person, that have strict consistency to them, > and then have another set of packages, allowed to go into current > by a different person, that did not have consistency to them. Of course, we should strive for consistency. However, in my country, there are many judges, juries and magistrates called upon to make legal judgements in different courts every day. They strive to be consistent with one another (we have Common Law system here). They may not actually be 100% consistent but that is the aim. No one suggests that in order to maintain perfect consistency we can only have one judge. Sebastian wrote: > Has the release process with Phil as the single point of getting packages > into current shown a major bottleneck so far? Well, depends what you call 'major'. Certainly a bottleneck. > Or is it the manual nature (effort on the maintainers side) of the release > process? I don't like a manual process either. I like automation. I want to SVN check in a fresh file to GAR, and do basically nothing else if there are no problems... build it, test it, release to testing, wait, release to newpkgs, maybe email me and some others a status update as it moves through the system... > Did packages get rejected out of uncertain or non-understandable reasons? Yes > Do we have a truck factor issue with Phil as the only path to current at the moment? We call it the 'hit by a bus' factor here, and yes. Again, personally, I don't think packages should have a single mainainer either, it should be minimum two. For release gatekeepers/GPG keyholders, I'd like half a dozen. Just my 2p... Gary -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Tue Jan 20 09:25:48 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 20 Jan 2009 09:25:48 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090116144804.GB2576@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> On Tue, Jan 20, 2009 at 12:32 AM, Gary Law wrote: > Peter wrote: > Peter then wrote: > Peter wrote some more: Phil wrote all those quotes, not me. :-) Besides that... +1 To me it comes down to basic technical design, you always go for load balancing and redundancy if you can. One recent example is Dago administering the build farm just as well as Phil releases packages, still there were requests for adding people to that process. Dago, being a reasonable man, agreed and now we have more build farm admins. Why is this different? -- /peter From glaw at opencsw.org Tue Jan 20 10:54:59 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 09:54:59 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> References: <20090116144804.GB2576@bolthole.com> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <625385e30901200025s41f6f68agef5333a9a146b86b@mail.gmail.com> Message-ID: 2009/1/20 Peter Bonivart > On Tue, Jan 20, 2009 at 12:32 AM, Gary Law wrote: > > Peter wrote: > > Peter then wrote: > > Peter wrote some more: > > Phil wrote all those quotes, not me. :-) > > Besides that... +1 > Err, yes, i was trying to summarise lots of points in a long thread and lost the plot there. Sorry Phil, sorry Peter. -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Tue Jan 20 18:05:49 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 09:05:49 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> Message-ID: <20090120170549.GB54457@bolthole.com> On Mon, Jan 19, 2009 at 11:32:08PM +0000, Gary Law wrote: > Dago wrote: > > There is no need for it to be handled internally. > > Explanations are given in www.opencsw.org:/home/newpkgs/README > > Not sure what you mean there, but http://opencsw.org/home/newpkgs/README > doesn't exist The initial reference is a file reference, scp style, not a URL > ..., nor does [/export]/home/newpkgs/README on > login.bo.opencsw.org. /home/newpkgs should not exist on login.bo.opencsw.org in the first place. It's only supposed to exist on www.opencsw.org > > It's impossible to code checkpkg to cover "everything". > > This is not an argument against automated testing. Well, it is actually an > /argument/ against automated testing, but a really bad one. no, it isnt an argument against automated testing. It's saying what it is saying. no more, no less. And it is reinforced by what you quoted from me, lower down: >> I tried to convey that we can reasonably cover, lets say, 80% of cases >> through checkpkg, and 95% of cases via "written down", but there's always > going to be a grey area left. that is to say, automated testing is nice, but it cannot cover everything that needs to be covered. >>But there will always be exceptoins. >> At some point, there always comes a need for a human being to make a >> decision of "yes this is acceptible/no this is not". > > I disagree. If something passes all the testing, why not release it? What is your basis for disagreement? convenience on your part? I will tell you what my basis for disagreeing with your statement right there: checkpkg was a lot simpler 4 years ago, and so were the written standards. Lets say that we had gone with your exact premise 4 years ago. We would not have gotten the improvements! The primary way they have improved, is because I took the time to personally take a glance at the packages, and sometimes noticed things that werent being caught. Then checkpkg, and/or the standards, got improved, when appropriate. There is a similar process in general AUTOMATED manufacturing of goods. Things are for the most part, fully automated. Yet there are still QA checks *by a human*, to see if any defects are slipping through still. > There is an interesting parallel with a discussion at my workplace just > this week. Some admins want to retain manual builds for much of the > software stack. I want to see everything that can be automated. This is a different case. You may feel it is the same, because there is an issue of "manual vs automated". But there are different core issues at stake. This is a matter of QA process, not build process. From glaw at opencsw.org Tue Jan 20 23:23:33 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 22:23:33 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090120170549.GB54457@bolthole.com> References: <20090118164717.GC81262@bolthole.com> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> Message-ID: 2009/1/20 Philip Brown > On Mon, Jan 19, 2009 at 11:32:08PM +0000, Gary Law wrote: > > Dago wrote: > > > There is no need for it to be handled internally. > > > Explanations are given in www.opencsw.org:/home/newpkgs/README > > > > Not sure what you mean there, but > http://opencsw.org/home/newpkgs/README > > doesn't exist > > The initial reference is a file reference, scp style, not a URL > > > > ..., nor does [/export]/home/newpkgs/README on > > login.bo.opencsw.org. > > /home/newpkgs should not exist on login.bo.opencsw.org in the first place. > It's only supposed to exist on www.opencsw.org OK, I have to say it hadn't occurred to me that I could ssh in... but I can! However, as far as I can tell the file isn't there: $ scp www.opencsw.org:/home/newpkgs/README . scp: /home/newpkgs/README: No such file or directory > > > It's impossible to code checkpkg to cover "everything". > > > > This is not an argument against automated testing. Well, it is > actually an > > /argument/ against automated testing, but a really bad one. > > no, it isnt an argument against automated testing. It's saying what it is > saying. no more, no less. And it is reinforced by what you quoted from me, > lower down: > > >> I tried to convey that we can reasonably cover, lets say, 80% of cases > >> through checkpkg, and 95% of cases via "written down", but there's > always > > going to be a grey area left. > > that is to say, automated testing is nice, but it cannot cover everything > that needs to be covered. Perhaps I'd have a better idea if you could explain what needs to be covered that's not automatable? > >>But there will always be exceptoins. > >> At some point, there always comes a need for a human being to make a > >> decision of "yes this is acceptible/no this is not". > > > > I disagree. If something passes all the testing, why not release it? > > What is your basis for disagreement? convenience on your part? convenience? perhaps a little, there's nothing wrong with that. But much more importantly consistency and transparency. > I will tell you what my basis for disagreeing with your statement right > there: > checkpkg was a lot simpler 4 years ago, and so were the written standards. > Lets say that we had gone with your exact premise 4 years ago. > We would not have gotten the improvements! > > The primary way they have improved, is because I took the time to > personally take a glance at the packages, and sometimes noticed things that > werent being caught. > Then checkpkg, and/or the standards, got improved, when > appropriate. > > There is a similar process in general AUTOMATED manufacturing of goods. > Things are for the most part, fully automated. Yet there are still QA > checks *by a human*, to see if any defects are slipping through still. > what we do is much more analogous to software development than manufacturing. And in software development automating QA is at the heart of most processes that seek to be support frequent, consistent, high quality releases. Manual QA is seen as a necessary evil for those things that haven't /yet/ been automated. We still need human beings -- users and maintainers -- to feed back problems that aren't caught in the automated tests, so we can improve them. > > There is an interesting parallel with a discussion at my workplace > just > > this week. Some admins want to retain manual builds for much of the > > software stack. I want to see everything that can be automated. > > This is a different case. You may feel it is the same, because there is an > issue of "manual vs automated". But there are different core issues at > stake. > > This is a matter of QA process, not build process. > Yes. But at the moment both build and QA are very manual, I'd like to see them be automated. You don't address the points concerning only having one gatekeeper on releases or on the use of individual discretion in this reply. I hope this means you're having second thoughts. Regards Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Tue Jan 20 23:37:24 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 14:37:24 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> Message-ID: <20090120223724.GF54457@bolthole.com> On Tue, Jan 20, 2009 at 10:23:33PM +0000, Gary Law wrote: > OK, I have to say it hadn't occurred to me that I could ssh in... but I > can! However, as far as I can tell the file isn't there: > $ scp www.opencsw.org:/home/newpkgs/README . > scp: /home/newpkgs/README: No such file or directory The original emailer, who wasnt me AFAIK, mistyped. If you actually log in and look in that directory, you will see that the actual file name is 00-README or something like that. Bottom line is, though, most people wont care about the file anyway. They will probably email me "why isnt my package released yet", and then *I* will go look at the file, to remind myself and them, the reasons why their package is still sitting in newpkgs. I put the reminder file there (instead of my home dir) , as an effort to be transparent to everyone about what is going on with things. Go read it, if you're curious. > that is to say, automated testing is nice, but it cannot cover > everything that needs to be covered. > > Perhaps I'd have a better idea if you could explain what needs to be > covered that's not automatable? Are you familiar with "the halting problem" in software design? Some things are fundamentally not solvable by fully automated methods. This is one of them. If i could explain "everything that needs to be covered" before ever seeing it, then not only would i be capable of designing a perfect AI, but i would also be clairvoyant. In which case, i'd be playing the stock market, and relaxing on a beach in the Bahamas instead of doing this :-) > You don't address the points concerning only having one gatekeeper on > releases or on the use of individual discretion in this reply. You havent given specifics why it is a bad thing. You have basically stated "it is bad", without saying what is actually bad about it. In constrast, I have given explicit reasons why it is a GOOD thing (consistency), and I have also given specific reasons why the "phil gets run over by a bus" claim to be concerned, is invalid. It has already been handled. Let's not waste people's time rehashing things that have already been solved, please? From glaw at opencsw.org Wed Jan 21 00:58:35 2009 From: glaw at opencsw.org (Gary Law) Date: Tue, 20 Jan 2009 23:58:35 +0000 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090120223724.GF54457@bolthole.com> References: <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> Message-ID: 2009/1/20 Philip Brown > On Tue, Jan 20, 2009 at 10:23:33PM +0000, Gary Law wrote: > > OK, I have to say it hadn't occurred to me that I could ssh in... but > I > > can! However, as far as I can tell the file isn't there: > > $ scp www.opencsw.org:/home/newpkgs/README . > > scp: /home/newpkgs/README: No such file or directory > > The original emailer, who wasnt me AFAIK, mistyped. If you actually log in > and > look in that directory, you will see that the actual file name is > 00-README or something like that. Indeed, that's it. > Bottom line is, though, most people wont care about the file anyway. They > will probably email me "why isnt my package released yet", and then *I* > will go look at the file, to remind myself and them, the reasons why their > package is still sitting in newpkgs. I put the reminder file there > (instead of my home dir) , as an effort to be transparent to everyone about > what is going on with things. Go read it, if you're curious. Thanks. That is a pointer to how things work. It is also a clear indication of how much of this process is currently handled by one person. > > that is to say, automated testing is nice, but it cannot cover > > everything that needs to be covered. > > > > Perhaps I'd have a better idea if you could explain what needs to be > > covered that's not automatable? > > Are you familiar with "the halting problem" in software design? Err, I wasn't aware that checkpkg was actually trying to solve that problem. > Some things are fundamentally not solvable by fully automated methods. > This is one of them. *What* is one of them? What are these nebulous criteria that cannot be tested in an automated fashion -- or indeed in a consistent way by anyone other than you personally -- but packages must comply with before release? > If i could explain "everything that needs to be covered" before ever seeing > it, then not only would i be capable of designing a perfect AI, but i would > also be clairvoyant. In which case, i'd be playing the stock market, and > relaxing on a beach in the Bahamas instead of doing this :-) Legislators face this problem every day. So do company managers. So so software designers. You make rules based on what you know, and what you anticipate. You don't expect it to be perfect, do you aim for 'good enough'. You accept that future revisions might require better rules/tests. That 'good enough' standard will be different if writing software for a content only website, or a bank teller system, or a fly-by-wire aircraft control system. I'm not asking you to explain everything you might find wrong in packages that don't yet exist; but I am suggesting we need to dispassionately look at proposed releases, against published criteria, and ideally automate the enforcement of the standard by failing to release things that fail a test. (I'm also not of the view that submission to one human being for arbitrary rubber stamp based on unpublished criteria should be the key determinant of the release process). > > You don't address the points concerning only having one gatekeeper on > > releases or on the use of individual discretion in this reply. > > You havent given specifics why it is a bad thing. You have basically > stated "it is bad", without saying what is actually bad about it. > In constrast, I have given explicit reasons why it is a GOOD thing > (consistency), and I have also given specific reasons why the > "phil gets run over by a bus" claim to be concerned, is invalid. > It has already been handled. Consistency is much more likely to be provided by automated tests, and well understood and broadly agreed standards. One person signing things off is more fallible IMHO. Even if you manage to be perfectly consistent with yourself this is not a scalable, or transparent, or open way of doing this. It does not encourage community participation. It's not a process I can explain to a potential new maintainer. It's also not consistent when you're not around for any reason, as the process just stops, which isn't consistent either. My last employer had a Change Advisory Board to decide on software releases. We tried to keep membership consistent from meeting to meeting, to maintain consistent decision making, but this never entirely possible. And it didn't matter much. The fact is good (automated) QA and agreed, published standards were more useful in the long term to raising standards in software than trying to keep the same bunch of people in a room, week in, week out. Companies signing off software with the potential to cost/make millions of $CURRENCY can do so on the basis of a inconsistent process like a CAB -- so why can't a volunteer effort release a couple of Solaris packages? > Let's not waste people's time rehashing things that have already been > solved, please? > This isn't rehashing, it's the first time I've seen it properly discussed since OpenCSW was formed, and, from where I'm standing, this is so /not/ solved. I think you suggested putting it to a vote... something I'll be entirely in favour of as soon as my membership application is approved..... :) Gary -- Gary Law Email: glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Wed Jan 21 02:21:09 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 17:21:09 -0800 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: References: <20090118215602.GB56431@bolthole.com> <4973A659.8060506@opencsw.org> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> Message-ID: <20090121012109.GA48238@bolthole.com> On Tue, Jan 20, 2009 at 11:58:35PM +0000, Gary Law wrote: > Let's not waste people's time rehashing things that have already been > solved, please? > > This isn't rehashing, it's the first time I've seen it properly discussed > since OpenCSW was formed, and, from where I'm standing, this is so /not/ > solved. > ... You are mixing "it"s by unfairly distancing what I wrote there, from what was directly before it. What was directly before it, was mention of the fallacious "what if phil got run over by a bus" argument. Which has been solved. You did not acknowlege that. That's all I have to say for now. From phil at bolthole.com Wed Jan 21 02:50:54 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 20 Jan 2009 17:50:54 -0800 Subject: [csw-maintainers] testing team for packages In-Reply-To: <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> Message-ID: <20090121015054.GA61849@bolthole.com> On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: >... > Not only will maintainers know better what is and is not > happening with their packages, I think it will encourage testing as > well. a side note: maintainers already tend to "know what is happening" with their packages already. Often within a few hours; usually within a day. As far as testing goes: Across-the-board testing doesnt happen because people write a fancy interface. Testing happens only when people *commit* to spending a WHOOLE bunch of their own time to do so. I think it makes sense that when, and IF, people step up to doing testing, that *those* people should get to design the interface they are going to use. Contrariwise, if no-one is willing to commit to doing testing, it makes no sense to spend a bunch of time designing an interface that no-one is going to use. If someone does decide to volunteer to test in the future, they may well toss it out the window and write their own. So it's waste of time and effort to write one now, before someone commits to doing testing. I would LOVE for us to have an official testing team, to test every package before release. [something which completely torpedoes any idea of "fully automated release" out the door, btw] As a frame of reference, I spend somewhere between 1-5 hours a week, EVERY WEEK, just looking at, and releasing packages. Testing, is going to take probably more time than that. Anyone want to commit to that kind of time, every week? From bonivart at opencsw.org Wed Jan 21 09:36:33 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 09:36:33 +0100 Subject: [csw-maintainers] Release process for current (was: Re: Thematics month proposal) In-Reply-To: <20090121012109.GA48238@bolthole.com> References: <20090118215602.GB56431@bolthole.com> <20090118221428.GF56431@bolthole.com> <625385e30901181439uaa16183t565ec49ab894cefe@mail.gmail.com> <4973BE59.6040102@opencsw.org> <20090120170549.GB54457@bolthole.com> <20090120223724.GF54457@bolthole.com> <20090121012109.GA48238@bolthole.com> Message-ID: <625385e30901210036u48bdf127v63767a8bcefc328d@mail.gmail.com> On Wed, Jan 21, 2009 at 2:21 AM, Philip Brown wrote: > What was directly before it, was mention of the fallacious > "what if phil got run over by a bus" argument. Which has been solved. Solved in a bad way. It's like running a server with one PSU, no UPS and a single disk but stating that everything is perfect because you have a spare server on the shelf. In the real world those passive standby systems are rarely up to the task but needs tinkering to say the least to do the job when tested. Active standby systems don't only share the load when everything works, they also immediately pick up the slack when one server goes down. That's how you design systems. Or processes in our case. -- /peter From bonivart at opencsw.org Wed Jan 21 09:45:14 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 09:45:14 +0100 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: <625385e30901210045q19f979fbv3e79285f10528a71@mail.gmail.com> On Wed, Jan 21, 2009 at 2:50 AM, Philip Brown wrote: > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a day. I wasn't talking about only the maintainer who owns the package, having a closed release process is part of our testing problem. By having a system that is easily available more people may see the need for testing and be willing to commit to a missing part. But as usual you paint a black and white scenario where it's no point in even trying to improve stuff. > As a frame of reference, I spend somewhere between 1-5 hours a week, EVERY > WEEK, just looking at, and releasing packages. > > Testing, is going to take probably more time than that. > Anyone want to commit to that kind of time, every week? My main reason for this is not some kind of personal gain as you have tried to convince others, but to make the community grow and be ready for that. It would mean even more packages that would need to be handled by you alone. You will not be able to keep reasonable times and quality. By sharing, the load would be less on all, including you, and times would be kept even if one is on vacation for example. That is, if you're ready to use your six years of experience doing this to teach others. That would be a good thing for all. -- /peter From bonivart at opencsw.org Wed Jan 21 14:44:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 14:44:42 +0100 Subject: [csw-maintainers] pkgutil 1.4 released Message-ID: <625385e30901210544y6b95ad51u56e4150a3370dd31@mail.gmail.com> I have released version 1.4 of pkgutil and the main news is that it's much faster at calculating dependencies than before. You who had tried to install complex packages with lots of dependencies had to wait for many minutes to get results, now it should be down to seconds. In my tests it's been more than 100x faster in some cases. Release history for v1.4: * Dependency calculations are now much faster * Support for local file repositories (Dennis Clarke) * Keyword "same" when using -c replaced with "SAME" (Dennis Clarke) * Bldcat now skips SUNW packages as dependencies The reason for such a short list (when I have a huge wishlist) is that I'm working with another developer on a large patch and I underestimated the time it takes to implement and test so I decided to release v1.4 with this important speed increase and then continue with the patch. More info about pkgutil here: http://pkgutil.wikidot.com -- /peter From glaw at opencsw.org Wed Jan 21 17:34:45 2009 From: glaw at opencsw.org (Gary Law) Date: Wed, 21 Jan 2009 16:34:45 +0000 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: 2009/1/21 Philip Brown > On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: > >... > > Not only will maintainers know better what is and is not > > happening with their packages, I think it will encourage testing as > > well. > > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a day. > > As far as testing goes: > Across-the-board testing doesnt happen because people write a fancy > interface. > Testing happens only when people *commit* to spending a WHOOLE bunch of > their own time to do so. > > I think it makes sense that when, and IF, people step up to doing testing, > that *those* people should get to design the interface they are going to > use. > > Contrariwise, if no-one is willing to commit to doing testing, it makes no > sense to spend a bunch of time designing an interface that no-one is going > to use. > If someone does decide to volunteer to test in the future, they may well > toss it out the window and write their own. So it's waste of time and > effort to write one now, before someone commits to doing testing. > People test my packages before release. I get feedback and I've made plenty of changes in response to this. Most of this came from you Phil, but I got a lot from other people too, including one report only last week from the package I rolled up a week before. An entirely or largely automated test regime would reduce or eliminate the load on volunteers of course. Gary -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Wed Jan 21 19:10:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 19:10:32 +0100 Subject: [csw-maintainers] testing team for packages In-Reply-To: <20090121015054.GA61849@bolthole.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> Message-ID: <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> Hi, Am 21.01.2009 um 02:50 schrieb Philip Brown: > On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote: >> ... >> Not only will maintainers know better what is and is not >> happening with their packages, I think it will encourage testing as >> well. > > a side note: maintainers already tend to "know what is happening" with > their packages already. Often within a few hours; usually within a > day. That is okay. If someone is willing to work on the next-generation package tracking web interface: even better. > As far as testing goes: > Across-the-board testing doesnt happen because people write a fancy > interface. Only if it is hard. We already have a testing catalog. If we had a full catalog (instead of an "add-on") people could subscribe to testing/ directly. If we then had some easy-to-use feedback mechanism (Mantis with prior registration is not!) that may help. > I would LOVE for us to have an official testing team, to test every > package > before release. > [something which completely torpedoes any idea of "fully automated > release" > out the door, btw] Fully automated testing is what checkpkg already does. What Phil does is looking for things like consistent naming, decent package splitting, putting files in the correct locations, all things that you simply can not automate - and these things are important too. However, the operational guidelines for this can and should be written down in addition to the formal guidelines in checkpkg. Best regards -- Dago From dam at opencsw.org Wed Jan 21 19:12:33 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 19:12:33 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: References: <496FAB77.8000208@wbonnet.net> <625385e30901160120y74a24fccm300f549fed5b9cfa@mail.gmail.com> <345D1671-EC4B-4D3A-8A59-B0C98B0440D9@opencsw.org> <49706F0E.2080004@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> Message-ID: <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> Hi, Am 18.01.2009 um 21:17 schrieb Dagobert Michelsen: > Am 18.01.2009 um 20:48 schrieb Philip Brown: > >> On Sun, Jan 18, 2009 at 08:23:11PM +0100, Peter FELECAN wrote: >>> If you addressed the issues why don't you publish an answer to each >>> one, on the same page, this way we can see what's still undecided >>> and >>> can add to William topics; we can even discuss them here. > > Good point Peter. > >> I'll let the secretary do that ;-) > > I'll take care of that. I added the current status to http://wiki.opencsw.org/suggestions Feel free to comment on the status or to request improvements ;-) Best regards -- Dago From phil at bolthole.com Wed Jan 21 19:22:07 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 21 Jan 2009 10:22:07 -0800 Subject: [csw-maintainers] testing team for packages In-Reply-To: <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> References: <20090118164717.GC81262@bolthole.com> <497391E5.1070700@opencsw.org> <625385e30901181307p393352f1pc112e9ded314ec68@mail.gmail.com> <4973A06E.6040906@opencsw.org> <625385e30901181403g2255f8c4ife320fcf2e8e4e10@mail.gmail.com> <4973AEE7.1020905@opencsw.org> <20090118235207.GA79582@bolthole.com> <625385e30901181611q4ae01dedj24df342dbaf429dc@mail.gmail.com> <20090121015054.GA61849@bolthole.com> <2B446B38-4B91-49E1-B541-C793AC4A8524@opencsw.org> Message-ID: <20090121182207.GC27028@bolthole.com> On Wed, Jan 21, 2009 at 07:10:32PM +0100, Dagobert Michelsen wrote: > ... > Fully automated testing is what checkpkg already does. What Phil does is > looking for things like consistent naming, decent package splitting, > putting files in the correct locations, all things that you simply > can not automate - and these things are important too. However, the > operational guidelines for this can and should be written down in > addition to the formal guidelines in checkpkg. and, as far as is reasonable to do so in a uniform fashion, [once again] This Is Already Handled. That is what the "filesystem layout" page is for, under the standards area, for example. From harpchad at opencsw.org Wed Jan 21 19:58:52 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 21 Jan 2009 12:58:52 -0600 Subject: [csw-maintainers] testing: libxslt and curl Message-ID: <4977706C.7020700@opencsw.org> New versions of libxslt and curl are now in testing. These are some of my first builds using gar v2, so please test if you have a dependency. libxslt is now distributed as three packages: CSWlibxslt libxslt CSWlibxsltdevel libxslt_devel CSWpylibxslt pylibxslt curl is like wise distrubuted as three packages: CSWcurl curl CSWcurldevel curldevel CSWcurlrt curlrt From bonivart at opencsw.org Wed Jan 21 20:12:08 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 20:12:08 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> Message-ID: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen wrote: > I added the current status to > http://wiki.opencsw.org/suggestions > > Feel free to comment on the status or to request improvements ;-) The maintainer suggestion status is "done", referring to a blank page. It will be interesting to read its future content. ;-) Another thing is the done status for "equal status between install tools". You refer to your testing page but that is the only page that even mentions pkgutil. Everywhere on the main site (home, packages, mirror and so on) it's only pkg-get and on the mirror roots only pkg-get is available for new users, the README file there also only mention pkg-get. -- /peter From dam at opencsw.org Wed Jan 21 21:00:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 21:00:32 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <92EE88DA-5AB1-4556-BA6B-18DEE9057A99@opencsw.org> Hi Peter, Am 21.01.2009 um 20:12 schrieb Peter Bonivart: > On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen > wrote: >> I added the current status to >> http://wiki.opencsw.org/suggestions >> >> Feel free to comment on the status or to request improvements ;-) > > The maintainer suggestion status is "done", referring to a blank page. > It will be interesting to read its future content. ;-) Grrr... mistyped link now corrected ;-) > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. I see. That should be addressed. Phil, the presentation of tools on the webpage should be adjusted to allow equal use. It is a good thing you wrote pkg-get and that it runs everywhere due to the implementation language. But it is equally good to have the choice of another tool with slightly different goals. A good point to fully address this issue would be IMHO the new website from William, which hopefully come very soon. Best regards -- Dago From dam at opencsw.org Wed Jan 21 21:02:28 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 21 Jan 2009 21:02:28 +0100 Subject: [csw-maintainers] testing: libxslt and curl In-Reply-To: <4977706C.7020700@opencsw.org> References: <4977706C.7020700@opencsw.org> Message-ID: <7AD57E29-EC47-4F1C-93BC-C6FEE0D05F0D@opencsw.org> Hi Chad, Am 21.01.2009 um 19:58 schrieb Chad Harp: > New versions of libxslt and curl are now in testing. These are some > of > my first builds using gar v2 This is very brave of you :-) > so please test if you have a dependency. > > libxslt is now distributed as three packages: > > CSWlibxslt libxslt > CSWlibxsltdevel libxslt_devel > CSWpylibxslt pylibxslt You may want to have a look at the REQUIRED_PKGS_ to get rid of the .depend-files and use SPKG_DESC_ for individual description strings. A good reference is the Makefile from 'bind' which uses most of the new features. > curl is like wise distrubuted as three packages: > > CSWcurl curl > CSWcurldevel curldevel > CSWcurlrt curlrt Thanks for your constant contribution and enhancements! Best regards -- Dago From william at wbonnet.net Wed Jan 21 21:01:35 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 21 Jan 2009 21:01:35 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <49777F1F.6050202@wbonnet.net> Hi Peter > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. > It will be documented on the next version of the web site. Blog engine is already online, if you agree we can work together on the description for your tools. Especially the "quickstart" page has to be created and filled for both tools cheers W. /me back after four days of blackout... -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Wed Jan 21 22:26:15 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 21 Jan 2009 22:26:15 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <49777F1F.6050202@wbonnet.net> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <49777F1F.6050202@wbonnet.net> Message-ID: <625385e30901211326v7e3ad652m32351e2c48819d37@mail.gmail.com> On Wed, Jan 21, 2009 at 9:01 PM, William Bonnet wrote: > Hi Peter >> Another thing is the done status for "equal status between install >> tools". You refer to your testing page but that is the only page that >> even mentions pkgutil. Everywhere on the main site (home, packages, >> mirror and so on) it's only pkg-get and on the mirror roots only >> pkg-get is available for new users, the README file there also only >> mention pkg-get. >> > It will be documented on the next version of the web site. Blog engine > is already online, if you agree we can work together on the description > for your tools. Especially the "quickstart" page has to be created and > filled for both tools I would very much like that. :-) I will do my best to help. -- /peter From bonivart at opencsw.org Thu Jan 22 15:26:16 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 15:26:16 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122050944.GA31372@keevey> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> Message-ID: <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> Forwarded from the users list... Was this a deliberate change implemented in GAR or did I screw up somehow? :-/ ---------- Forwarded message ---------- From: Rob Stampfli Date: Thu, Jan 22, 2009 at 6:09 AM Subject: Re: [csw-users] Warning: Latest Clamav does not work on old Sparcs To: questions and discussions On Wed, Jan 21, 2009 at 10:36:13PM -0500, Rob Stampfli wrote: > Just a head's up: The latest clamav build (0.94.2,REV=2008.12.18) > is built for the SPARC32PLUS / V8+, and will not run on the older > Sparc V7 architecture. Beware of this gotcha if you are planning > to upgrade from the 0.92.1,REV=2008.02.11 load on an older Sparc. > > And as long as I have your attention, I notice that the most recent > version of libtool and libtool_rt is older than the prior version: > The version I am running is 2.2.4,REV=2008.05.16, whereas the version > currently being offered is 1.5.26,REV=2008.12.22. What is recommended? > Backing back to 1.5.26 or waiting to see what happens? I see the new Python load is also V8+ now, so apparently there has been a change. I realize there has been some sort of split between Blastwave CSW and Opencsw, probably revolving around this very issue from what I've been able to discern. I suppose this means I need to go over to Opencsw for my old systems. Sorry to bother you all. Rob _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users -- /peter From dam at opencsw.org Thu Jan 22 17:00:16 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:00:16 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> Message-ID: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Hi Peter, Am 22.01.2009 um 15:26 schrieb Peter Bonivart: > Forwarded from the users list... > > Was this a deliberate change implemented in GAR or did I screw up > somehow? :-/ Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. You should have better just reset OPT_FLAGS_SOS11_sparc and the equivalent flags. Being least-invasive here is quite important. Phil, this would be nice to catch in checkpkg. Best regards -- Dago > ---------- Forwarded message ---------- > From: Rob Stampfli > Date: Thu, Jan 22, 2009 at 6:09 AM > Subject: Re: [csw-users] Warning: Latest Clamav does not work on old > Sparcs > To: questions and discussions > > > On Wed, Jan 21, 2009 at 10:36:13PM -0500, Rob Stampfli wrote: >> Just a head's up: The latest clamav build (0.94.2,REV=2008.12.18) >> is built for the SPARC32PLUS / V8+, and will not run on the older >> Sparc V7 architecture. Beware of this gotcha if you are planning >> to upgrade from the 0.92.1,REV=2008.02.11 load on an older Sparc. >> >> And as long as I have your attention, I notice that the most recent >> version of libtool and libtool_rt is older than the prior version: >> The version I am running is 2.2.4,REV=2008.05.16, whereas the version >> currently being offered is 1.5.26,REV=2008.12.22. What is >> recommended? >> Backing back to 1.5.26 or waiting to see what happens? > > I see the new Python load is also V8+ now, so apparently there has > been a change. I realize there has been some sort of split between > Blastwave CSW and Opencsw, probably revolving around this very issue > from what I've been able to discern. I suppose this means I need > to go over to Opencsw for my old systems. Sorry to bother you all. > > Rob > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > > > > -- > /peter > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Thu Jan 22 17:09:41 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:09:41 +0100 Subject: [csw-maintainers] Best-practice on texinfo - cswclassutils? Message-ID: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> Hi, I noticed that some legacy packages have an integration of regenerating the texinfo index when files are added in a package. We don't have anything in GAR for this yet. I guess it would be nice to have that in cswclassutils. Thoughts? Best regards -- Dago From bonivart at opencsw.org Thu Jan 22 17:12:53 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 17:12:53 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Message-ID: <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> On Thu, Jan 22, 2009 at 5:00 PM, Dagobert Michelsen wrote: > Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile > of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. > You should have better just reset OPT_FLAGS_SOS11_sparc and > the equivalent flags. Being least-invasive here is quite important. I remember us discussing optimization and that x03 didn't work but x02 did. By changing to x02 I accidentally removed all other options then..? Could you be more specific on how I should change my Makefile? How about that Python package he mentions then? -- /peter From dam at opencsw.org Thu Jan 22 17:18:30 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:18:30 +0100 Subject: [csw-maintainers] FYI: Temporarily deactivation .la-files Message-ID: Hi, I have currently serious trouble with .la-files and have therefore temporarily renamed all files from /opt/csw/lib/*.la to /opt/csw/lib/*.la.moved on build8s only (!). I'll undo the changes after my tests. Please be aware and let me know if you encounter anything. Best regards -- Dago From dam at opencsw.org Thu Jan 22 17:43:24 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:43:24 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> Message-ID: Hi Peter, Am 22.01.2009 um 17:12 schrieb Peter Bonivart: > On Thu, Jan 22, 2009 at 5:00 PM, Dagobert Michelsen > wrote: >> Sorry Peter, you screwed it up. You reset CFLAGS in your Makefile >> of clamav. The default is v8+ and the CFLAGS are set in GAR to v8. >> You should have better just reset OPT_FLAGS_SOS11_sparc and >> the equivalent flags. Being least-invasive here is quite important. > > I remember us discussing optimization and that x03 didn't work but x02 > did. I had a similar problem with SE Toolkit some time ago. The problem was produced by using jumps to codereferences without declaring the proper variables volatile. See for details. This may help identifying the problem upstream so you can compile the next versions with -xO3 again :-) > By changing to x02 I accidentally removed all other options > then..? More specifically by setting CFLAGS directly. > Could you be more specific on how I should change my Makefile? Nice and easy after my enhancement in r2875 with OPT_FLAGS_SOS = -xO2 As this is quite new please let me know if it worked. > How about that Python package he mentions then? That package was done by Ken Mays and the description is not in GAR: I don't know what happened there. The package at OpenCSW looks ok, but is old. Best regards -- Dago From dam at opencsw.org Thu Jan 22 17:45:19 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 17:45:19 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <4978A12E.8090407@opencsw.org> References: <4978A12E.8090407@opencsw.org> Message-ID: <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Hi Chad, Am 22.01.2009 um 17:39 schrieb Chad Harp: > Dagobert Michelsen wrote: >> I have currently serious trouble with .la-files and have therefore >> temporarily renamed all files from >> /opt/csw/lib/*.la >> to >> /opt/csw/lib/*.la.moved >> on build8s only (!). I'll undo the changes after my tests. >> >> Please be aware and let me know if you encounter anything. >> > > Is there a reason we shouldn't leave it that way (and replicate the > change on the rest of the build env)? > > I've been having a similar problem and have been delaying some updates > until the .la problem gets resolved. I understand that in some cases > the .la files are required, but we could deal with those on an > exception > basis. I guess that would be best. That way we don't pollute new packages. Best regards -- Dago From bonivart at opencsw.org Thu Jan 22 18:04:54 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 18:04:54 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <625385e30901220812r3fa467b7kabd862da41f7143b@mail.gmail.com> Message-ID: <625385e30901220904q2063546cy668ef7bd5cc022be@mail.gmail.com> On Thu, Jan 22, 2009 at 5:43 PM, Dagobert Michelsen wrote: > Nice and easy after my enhancement in r2875 with > OPT_FLAGS_SOS = -xO2 > > As this is quite new please let me know if it worked. Before: clamscan: ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, dynamically linked, stripped After: clamscan: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped :-) -- /peter From korpela at opencsw.org Thu Jan 22 18:13:06 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 22 Jan 2009 09:13:06 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: In some cases I'm having the opposite problem because of missing dependencies that were supposed to be in the .la files of packages where the .la files were not installed. Shouldn't problems in .la files be reported as bugs to the package maintainers? If a package includes them it's up the the maintainers to see that they are correct, no? Eric On Thu, Jan 22, 2009 at 8:45 AM, Dagobert Michelsen wrote: > Hi Chad, > > Am 22.01.2009 um 17:39 schrieb Chad Harp: >> Dagobert Michelsen wrote: >>> I have currently serious trouble with .la-files and have therefore >>> temporarily renamed all files from >>> /opt/csw/lib/*.la >>> to >>> /opt/csw/lib/*.la.moved >>> on build8s only (!). I'll undo the changes after my tests. >>> >>> Please be aware and let me know if you encounter anything. >>> >> >> Is there a reason we shouldn't leave it that way (and replicate the >> change on the rest of the build env)? >> >> I've been having a similar problem and have been delaying some updates >> until the .la problem gets resolved. I understand that in some cases >> the .la files are required, but we could deal with those on an >> exception >> basis. > > I guess that would be best. That way we don't pollute new packages. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > From pfelecan at opencsw.org Thu Jan 22 18:30:26 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 18:30:26 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: (Eric J. Korpela's message of "Thu\, 22 Jan 2009 09\:13\:06 -0800") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: Eric J Korpela writes: > In some cases I'm having the opposite problem because of missing > dependencies that were supposed to be in the .la files of packages > where the .la files were not installed. > > Shouldn't problems in .la files be reported as bugs to the package > maintainers? If a package includes them it's up the the maintainers > to see that they are correct, no? Indeed, the .la files *are* useful and not having them is a pain... If the paths in the .la files are incorrect it *is* a bug and *must* be corrected. BTW, moving the .la files as you have done can be disruptive for activities of other maintainers and, IMHO should be done on a test system. my 8.5*10^12 cents --- and growing -- Peter From dam at opencsw.org Thu Jan 22 18:47:32 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 18:47:32 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Hi Peter, Am 22.01.2009 um 18:30 schrieb Peter FELECAN: > Eric J Korpela writes: >> In some cases I'm having the opposite problem because of missing >> dependencies that were supposed to be in the .la files of packages >> where the .la files were not installed. >> >> Shouldn't problems in .la files be reported as bugs to the package >> maintainers? If a package includes them it's up the the maintainers >> to see that they are correct, no? > > Indeed, the .la files *are* useful and not having them is a pain... If > the paths in the .la files are incorrect it *is* a bug and *must* be > corrected. The reason for officially banning .la-files in new packages is that you can get in a situation where you cannot build a software when an old version is installed because libtool picks up the old files and links against the old libs. > BTW, moving the .la files as you have done can be disruptive for > activities of other maintainers and, IMHO should be done on a test > system. I am really sorry for that. I'll undo my changes in an hour and promise to keep away from using misusing my root powers again *-) Best regards -- Dago From pfelecan at opencsw.org Thu Jan 22 18:54:37 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 18:54:37 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> (Dagobert Michelsen's message of "Thu\, 22 Jan 2009 18\:47\:32 +0100") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: Dagobert Michelsen writes: > Hi Peter, > > Am 22.01.2009 um 18:30 schrieb Peter FELECAN: >> Eric J Korpela writes: >>> In some cases I'm having the opposite problem because of missing >>> dependencies that were supposed to be in the .la files of packages >>> where the .la files were not installed. >>> >>> Shouldn't problems in .la files be reported as bugs to the package >>> maintainers? If a package includes them it's up the the maintainers >>> to see that they are correct, no? >> >> Indeed, the .la files *are* useful and not having them is a pain... If >> the paths in the .la files are incorrect it *is* a bug and *must* be >> corrected. > > The reason for officially banning .la-files in new packages is that > you can get in a situation where you cannot build a software when > an old version is installed because libtool picks up the old files > and links against the old libs. There is no way to prohibit the usage of the old, installed .la files when building the new package? It seems to me a less brutal approach. >> BTW, moving the .la files as you have done can be disruptive for >> activities of other maintainers and, IMHO should be done on a test >> system. > > I am really sorry for that. I'll undo my changes in an hour and promise > to keep away from using misusing my root powers again *-) It's alright, my observation was just a question of principle. -- Peter From dam at opencsw.org Thu Jan 22 18:57:29 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 18:57:29 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: <48D4AED4-53F7-4BA8-98CB-63E18740276F@opencsw.org> Hi, Am 22.01.2009 um 18:47 schrieb Dagobert Michelsen: >> BTW, moving the .la files as you have done can be disruptive for >> activities of other maintainers and, IMHO should be done on a test >> system. > > I am really sorry for that. I'll undo my changes in an hour and > promise > to keep away from using misusing my root powers again *-) Changes undone on build8s. Everything should be fine again. Sorry for the inconvenience -- Dago From dam at opencsw.org Thu Jan 22 19:07:25 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 19:07:25 +0100 Subject: [csw-maintainers] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <1E88D310-A165-4EA3-8316-36261E1FB21F@opencsw.org> Message-ID: Hi Peter, Am 22.01.2009 um 18:54 schrieb Peter FELECAN: > Dagobert Michelsen writes: >> The reason for officially banning .la-files in new packages is that >> you can get in a situation where you cannot build a software when >> an old version is installed because libtool picks up the old files >> and links against the old libs. > > There is no way to prohibit the usage of the old, installed .la > files when building the new package? It seems to me a less brutal > approach. If you know one than I would be really interested to hear it. This is the answer I got from Bruno Haible, a GNU maintainer for libiconv and a dozen other packages when I asked him about the problem: Am 11.04.2008 um 13:13 schrieb Bruno Haible: > This is a known problem with libtool and DESTDIR installations. > On some systems you simply cannot create an executable that should > link to /opt/csw/lib/libiconv.so if the library is not yet there. > On the other systems, libtool could do a bit better when you ask > to link with /tmp/pkgdir/opt/csw/lib/libiconv.la (it could use > /tmp/pkgdir/opt/csw/lib/libiconv.so). > > So, in general, I recommend to do first the "make install" and then > only > "make install DESTDIR=..." Using /tmp for temp linking spoils other config files like pkgconfig, so I figured removing .la-files at all will help here. Best regards -- Dago From phil at bolthole.com Thu Jan 22 19:32:12 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:32:12 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> Message-ID: <20090122183210.GA23122@bolthole.com> On Thu, Jan 22, 2009 at 05:00:16PM +0100, Dagobert Michelsen wrote: > > Phil, this [sparc executables not v8] would be nice to catch in checkpkg. yes, it would :) but it's tricky, which is why I havent implemented it previously. The problems being that 1. not all executables HAVE to be in /opt/csw/bin 2. some executables are LEGITIMATELY non vanilla v8. Best I could do, would be to look at executables in /opt/csw/bin only. Which would still potentially miss somethings, but would at least catch more than is being done now. yes/no? From dam at opencsw.org Thu Jan 22 19:35:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 19:35:54 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122183210.GA23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> Message-ID: <5C8A5524-D69E-43F5-AD3D-06A32EA3B922@opencsw.org> Hi Phil, Am 22.01.2009 um 19:32 schrieb Philip Brown: > On Thu, Jan 22, 2009 at 05:00:16PM +0100, Dagobert Michelsen wrote: >> >> Phil, this [sparc executables not v8] would be nice to catch in >> checkpkg. > > yes, it would :) but it's tricky, which is why I havent implemented it > previously. > > The problems being that > > 1. not all executables HAVE to be in /opt/csw/bin > 2. some executables are LEGITIMATELY non vanilla v8. > > Best I could do, would be to look at executables in /opt/csw/bin only. > Which would still potentially miss somethings, but would at least > catch > more than is being done now. You could search for all binaries. Every binary must conform to v8/i386 with the exception of binaries residing in directories named after the ISA, e. h. sparcv9/ may contain a binary with sparcv9. That is at least true for all GAR builds as far as I know of. Best regards -- Dago From harpchad at opencsw.org Thu Jan 22 19:37:14 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 22 Jan 2009 12:37:14 -0600 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> Message-ID: <4978BCDA.9070508@opencsw.org> Several of those packages don't have maintainers. By leaving them there we're deciding not to build new packages that have a broken libtool dependencies. i.e. Old package that no longer has a maintainer has an [a.la] file that references another [b.la] file. But b.la is gone now because the maintainer of that package is stripping .la files when he packages. Now packages that depend on a.so will not build because libtool wants to see b.la. We need a global policy on libtool files. We should either remove them all allowing them only by exception or chose to keep them. Right now the build farm is in a state where I cannot build most of my packages because old .la files reference .la files that have been removed in newer builds by package maintainers. Cleaning this up is probably going to be painful, maybe someone has some libtool magic to make it build around these situations? Eric J Korpela wrote: > In some cases I'm having the opposite problem because of missing > dependencies that were supposed to be in the .la files of packages > where the .la files were not installed. > > Shouldn't problems in .la files be reported as bugs to the package > maintainers? If a package includes them it's up the the maintainers > to see that they are correct, no? > > Eric > > On Thu, Jan 22, 2009 at 8:45 AM, Dagobert Michelsen wrote: >> Hi Chad, >> >> Am 22.01.2009 um 17:39 schrieb Chad Harp: >>> Dagobert Michelsen wrote: >>>> I have currently serious trouble with .la-files and have therefore >>>> temporarily renamed all files from >>>> /opt/csw/lib/*.la >>>> to >>>> /opt/csw/lib/*.la.moved >>>> on build8s only (!). I'll undo the changes after my tests. >>>> >>>> Please be aware and let me know if you encounter anything. >>>> >>> Is there a reason we shouldn't leave it that way (and replicate the >>> change on the rest of the build env)? >>> >>> I've been having a similar problem and have been delaying some updates >>> until the .la problem gets resolved. I understand that in some cases >>> the .la files are required, but we could deal with those on an >>> exception >>> basis. >> I guess that would be best. That way we don't pollute new packages. >> >> >> Best regards >> >> -- Dago >> _______________________________________________ >> maintainers mailing list >> maintainers at lists.opencsw.org >> https://lists.opencsw.org/mailman/listinfo/maintainers >> From bwalton at opencsw.org Thu Jan 22 19:39:02 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 22 Jan 2009 13:39:02 -0500 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122183210.GA23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> Message-ID: <1232649483-sup-19@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Jan 22 13:32:12 -0500 2009: > Best I could do, would be to look at executables in /opt/csw/bin only. > Which would still potentially miss somethings, but would at least catch > more than is being done now. ...but checkpkg is already doing a `find ...` and discovering anything with an ELF header. Couldn't this list be overloaded to help in this situation? -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Jan 22 19:47:49 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:47:49 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <1232649483-sup-19@ntdws12.chass.utoronto.ca> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> Message-ID: <20090122184748.GB23122@bolthole.com> On Thu, Jan 22, 2009 at 01:39:02PM -0500, Ben Walton wrote: > Excerpts from Philip Brown's message of Thu Jan 22 13:32:12 -0500 2009: > > Best I could do, would be to look at executables in /opt/csw/bin only. > > Which would still potentially miss somethings, but would at least catch > > more than is being done now. > > ...but checkpkg is already doing a `find ...` and discovering anything > with an ELF header. Couldn't this list be overloaded to help in this > situation? The issue is not "finding where all ELF files are located". The issue is, "Which ones should we legitimately complain about?" As I have mentioned, the rule is NOT that *all* sparc binaries be v8. The rule is that *default* binaries be v8. One package i know of that would run afoul of a blind checkpkg check, would be mysql. which has 32bit and 64bit binaries in the same directory. but they are not /opt/csw/bin From bwalton at opencsw.org Thu Jan 22 19:51:28 2009 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 22 Jan 2009 13:51:28 -0500 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122184748.GB23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> Message-ID: <1232650271-sup-5226@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Thu Jan 22 13:47:49 -0500 2009: > The issue is not "finding where all ELF files are located". > The issue is, "Which ones should we legitimately complain about?" > As I have mentioned, the rule is NOT that *all* sparc binaries be > v8. The rule is that *default* binaries be v8. Roger that. I missed the nuance. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From phil at bolthole.com Thu Jan 22 19:51:49 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 10:51:49 -0800 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files Message-ID: <20090122185149.GF23122@bolthole.com> oops. replied to "buildfarm" list in error. forwarding to maintainers list instead... On Thu, Jan 22, 2009 at 12:33:36PM -0600, Chad Harp wrote: > ... > We need a global policy on libtool files. We HAVE a global policy. We just unfortunately have not had people who have volunteered to repackage old orphaned packages to bring them in line with the policy. Would you like to volunteer? From dam at opencsw.org Thu Jan 22 20:01:24 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:01:24 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122184748.GB23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> Message-ID: <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> Hi Phil, Am 22.01.2009 um 19:47 schrieb Philip Brown: > One package i know of that would run afoul of a blind checkpkg > check, would > be mysql. which has 32bit and 64bit binaries in the same directory. > but they are not /opt/csw/bin This doesn't sound right. Having a legacy package not passing checkpkg shouldn't keep us from enforcing a decent up-to-date policy on new packages: /opt/csw/mysql5/libexec/mysqld64 /opt/csw/mysql5/libexec/mysqld32+ /opt/csw/mysql5/libexec/mysqld32 /opt/csw/mysql5/libexec/mysqld This could be very well the standardized /opt/csw/mysql5/libexec/sparcv8/mysqld /opt/csw/mysql5/libexec/sparcv8plus/mysqld /opt/csw/mysql5/libexec/sparcv9/mysqld Best regards -- Dago From pfelecan at opencsw.org Thu Jan 22 20:10:49 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 20:10:49 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: <4978BCDA.9070508@opencsw.org> (Chad Harp's message of "Thu\, 22 Jan 2009 12\:37\:14 -0600") References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BCDA.9070508@opencsw.org> Message-ID: Chad Harp writes: > Cleaning this up is probably going to be painful, maybe someone has some > libtool magic to make it build around these situations? I understand your issue. Maybe a temporary solution is to modify the .la files on the build farm to correct the issues and, when there is no more soiled .la files we can revert to a normal operation. Isn't this a good candidate for a February topic for William's list? i.e., "get rid of cruft in .la files" -- Peter From phil at bolthole.com Thu Jan 22 20:11:56 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:11:56 -0800 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> Message-ID: <20090122191155.GH23122@bolthole.com> On Thu, Jan 22, 2009 at 08:01:24PM +0100, Dagobert Michelsen wrote: > > This could be very well the standardized > /opt/csw/mysql5/libexec/sparcv8/mysqld > /opt/csw/mysql5/libexec/sparcv8plus/mysqld > /opt/csw/mysql5/libexec/sparcv9/mysqld > Please note that the usual standard is based upon the concept of having [..]/bin/isaexec which will then automatically use the "most advanced" version of the binary supported on the system, based on those subdirs. This will automatically prefer 64-bit binaries, if they can run, I believe. This is NOT the desired default behaviour for mysql, however. From pfelecan at opencsw.org Thu Jan 22 20:12:45 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Thu, 22 Jan 2009 20:12:45 +0100 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files In-Reply-To: <20090122185149.GF23122@bolthole.com> (Philip Brown's message of "Thu\, 22 Jan 2009 10\:51\:49 -0800") References: <20090122185149.GF23122@bolthole.com> Message-ID: Philip Brown writes: > oops. replied to "buildfarm" list in error. forwarding to maintainers > list instead... > > > On Thu, Jan 22, 2009 at 12:33:36PM -0600, Chad Harp wrote: >> ... >> We need a global policy on libtool files. > > We HAVE a global policy. Which is?... -- Peter From phil at bolthole.com Thu Jan 22 20:40:47 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:40:47 -0800 Subject: [csw-maintainers] FYI: Temporarily?deactivation .la-files In-Reply-To: References: <20090122185149.GF23122@bolthole.com> Message-ID: <20090122194047.GI23122@bolthole.com> On Thu, Jan 22, 2009 at 08:12:45PM +0100, Peter FELECAN wrote: > Philip Brown writes: > > > > We HAVE a global policy. > > Which is?... http://www.opencsw.org/standards/build "New packages should take care to EXCLUDE libtool .la files. [...] Unfortunately, existing packages may need to preserve them, until all dependant packages have their own configs adjusted to not use .la files." And this global policy, has been "implemented" in GAR already, for many months. From phil at bolthole.com Thu Jan 22 20:44:06 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 11:44:06 -0800 Subject: [csw-maintainers] note: our 'search' page does actually work Message-ID: <20090122194406.GJ23122@bolthole.com> FYI, to people who may not be aware: our "search" page does actually work fairly well. If you go to http://www.opencsw.org/search and drop into the Site Search box, "libtool .la files" the first hit, is the standards page referencing, "New packages should take care to EXCLUDE libtool .la files. " From dam at opencsw.org Thu Jan 22 20:46:36 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:46:36 +0100 Subject: [csw-maintainers] Fwd: [csw-users] Warning: Latest Clamav does not work on old Sparcs In-Reply-To: <20090122191155.GH23122@bolthole.com> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220626u46d62c0by4d54bd870f860d21@mail.gmail.com> <34E9FC68-D6AD-4B95-A395-C4A0EF31D1AB@opencsw.org> <20090122183210.GA23122@bolthole.com> <1232649483-sup-19@ntdws12.chass.utoronto.ca> <20090122184748.GB23122@bolthole.com> <79D6C092-9F18-440B-8710-4A8F1293111F@opencsw.org> <20090122191155.GH23122@bolthole.com> Message-ID: Hi Phil, Am 22.01.2009 um 20:11 schrieb Philip Brown: > On Thu, Jan 22, 2009 at 08:01:24PM +0100, Dagobert Michelsen wrote: >> >> This could be very well the standardized >> /opt/csw/mysql5/libexec/sparcv8/mysqld >> /opt/csw/mysql5/libexec/sparcv8plus/mysqld >> /opt/csw/mysql5/libexec/sparcv9/mysqld >> > > Please note that the usual standard is based upon the concept of > having > [..]/bin/isaexec > > which will then automatically use the "most advanced" version of the > binary > supported on the system, based on those subdirs. > This will automatically prefer 64-bit binaries, if they can run, I > believe. > > This is NOT the desired default behaviour for mysql, however. This is the standard for isaexec, yes. If no isaexec is used the standard is to have sparcv8 in bin/ and the 64 bit in sparcv9/ or amd64/. IIRC there is currently no standard for isaexec which lets you choose manually between 32 and 64 bit. It may look like bin/ 32 bit isaexec bin/sparcv8/ 32 bit v8 binary bin/sparcv8plus/ 32 bit v8+ binary bin/64 64 bit isaexec bin/64/sparcv9/ 64 bit v9 bin/64/sparcv9b 64 bit v9b etc. Thoughts? Best regards -- Dago From dam at opencsw.org Thu Jan 22 20:48:34 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 20:48:34 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BCDA.9070508@opencsw.org> Message-ID: <48BE844F-1B9D-4AEF-85FF-1CF97BEF1127@opencsw.org> Hi Peter, Am 22.01.2009 um 20:10 schrieb Peter FELECAN: > Chad Harp writes: > >> Cleaning this up is probably going to be painful, maybe someone has >> some >> libtool magic to make it build around these situations? > > I understand your issue. Maybe a temporary solution is to modify the > .la files on the build farm to correct the issues and, when there is > no more soiled .la files we can revert to a normal operation. Unfortunately this is not sufficient. The old packages itself either need to be updated or modified. We could repackage the old packages without .la-files if necessary. > Isn't this a good candidate for a February topic for William's list? > i.e., "get rid of cruft in .la files" Yes. This can be done under "bug squashing". Best regards -- Dago From dam at opencsw.org Thu Jan 22 21:08:00 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 22 Jan 2009 21:08:00 +0100 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: Hi Eric, Am 22.01.2009 um 19:39 schrieb Eric J Korpela: > Yeah, a consistent policy is necessary. Maybe remove any for packages > without maintainers? Remove those that are reported broken? Or have > an enforced no libtool .la libraries policy? All of them could be > hard on the maintainers. Mass-remove .la-files from all packages has IMHO the least pain. After that we only must make sure that all new packages don't have them. Phil, are you in on this? Best regards -- Dago From trygvis at opencsw.org Thu Jan 22 21:40:34 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 22 Jan 2009 21:40:34 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090116144804.GB2576@bolthole.com> <4970F869.7060601@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> Message-ID: <4978D9C2.2070904@opencsw.org> Peter Bonivart wrote: > On Wed, Jan 21, 2009 at 7:12 PM, Dagobert Michelsen wrote: >> I added the current status to >> http://wiki.opencsw.org/suggestions >> >> Feel free to comment on the status or to request improvements ;-) > > The maintainer suggestion status is "done", referring to a blank page. > It will be interesting to read its future content. ;-) > > Another thing is the done status for "equal status between install > tools". You refer to your testing page but that is the only page that > even mentions pkgutil. Everywhere on the main site (home, packages, > mirror and so on) it's only pkg-get and on the mirror roots only > pkg-get is available for new users, the README file there also only > mention pkg-get. To be honest I don't see why we need two tools that does the same job. It will only be confuing to users as they won't know which tool to know, in particular if they have the same set of features. As it is now pkgutil can't replace pkg-get (try running pkgutil update on a box with more than one outdated dependency). When pkgutil is generally useful in *all* cases, I wouldn't mind a discussion. -- Trygve From bonivart at opencsw.org Thu Jan 22 22:08:22 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 22 Jan 2009 22:08:22 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <4978D9C2.2070904@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> Message-ID: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> On Thu, Jan 22, 2009 at 9:40 PM, Trygve Laugst?l wrote: > To be honest I don't see why we need two tools that does the same job. > It will only be confuing to users as they won't know which tool to know, > in particular if they have the same set of features. Same basic features maybe but pkgutil already has more advanced features and a lot more is coming. Lots of people choose to install apt/yum on rpm systems even if you can argue that they do the same job as what was on the system in the first place. Choice is good. > As it is now pkgutil can't replace pkg-get (try running pkgutil update > on a box with more than one outdated dependency). When pkgutil is > generally useful in *all* cases, I wouldn't mind a discussion. Are you talking about pre-1.4 now? Version 1.4 is lots faster. If you still have performance issues with 1.4 or other issues I wouldn't mind a discussion about that either. Or you could just keep using pkg-get if you like that one better. Choice is good. :-) -- /peter From phil at bolthole.com Thu Jan 22 22:48:05 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 13:48:05 -0800 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> References: <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> Message-ID: <20090122214805.GQ23122@bolthole.com> On Thu, Jan 22, 2009 at 10:08:22PM +0100, Peter Bonivart wrote: > Same basic features maybe but pkgutil already has more advanced > features and a lot more is coming. the same can be said of pkg-get. your "comparison page" is very out of date. From trygvis at opencsw.org Thu Jan 22 23:51:13 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Thu, 22 Jan 2009 23:51:13 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <49732B68.4090105@opencsw.org> <625385e30901180640t75772629h75eb64d98ca978a9@mail.gmail.com> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> Message-ID: <4978F861.2040301@opencsw.org> Peter Bonivart wrote: > On Thu, Jan 22, 2009 at 9:40 PM, Trygve Laugst?l wrote: >> To be honest I don't see why we need two tools that does the same job. >> It will only be confuing to users as they won't know which tool to know, >> in particular if they have the same set of features. > > Same basic features maybe but pkgutil already has more advanced > features and a lot more is coming. Lots of people choose to install > apt/yum on rpm systems even if you can argue that they do the same job > as what was on the system in the first place. Choice is good. As a project I don't think choice is necessarily a good thing if it increases the burden on us as a team as we would have to support two tools which can (and most likely will) fail in different ways. Having all tool available in the catalog is to me obviously a good thing. Do not take this personal or as critique of pkgutil or pkg-get. It is too bad that you couldn't work together on the same code base. Choice is good in the way that you took the ideas of pkg-get and added more, useful features. pkg-get has caught up (at least to a certain extent, I haven't checked out the new features of either tool), good for that tool. >> As it is now pkgutil can't replace pkg-get (try running pkgutil update >> on a box with more than one outdated dependency). When pkgutil is >> generally useful in *all* cases, I wouldn't mind a discussion. > > Are you talking about pre-1.4 now? Version 1.4 is lots faster. If you > still have performance issues with 1.4 or other issues I wouldn't mind > a discussion about that either. Or you could just keep using pkg-get > if you like that one better. Choice is good. :-) I'm not saying anything about what version I like or not, it is not relevant. You know I've already given you several feature requests. -- Trygve From korpela at opencsw.org Fri Jan 23 00:31:17 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 22 Jan 2009 15:31:17 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: That should probably work. Some packages may need some fixes to their build scripts to bring them in line. Some stuff developed on Linux assumes that they are there, or that a library isn't there if the .la file isn't, but IMHO, that's a bug anyway. It also can make static linking a pain, but that's rarely required when using a package manager. Eric From bonivart at opencsw.org Fri Jan 23 00:43:39 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 23 Jan 2009 00:43:39 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <4978F861.2040301@opencsw.org> References: <496FAB77.8000208@wbonnet.net> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> <4978F861.2040301@opencsw.org> Message-ID: <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> On Thu, Jan 22, 2009 at 11:51 PM, Trygve Laugst?l wrote: > You know I've already given you several feature requests. ...and I'm working on that... :-) -- /peter From skayser at opencsw.org Fri Jan 23 01:13:41 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 23 Jan 2009 01:13:41 +0100 Subject: [csw-maintainers] xterm 238 available for testing In-Reply-To: <4966066B.4060804@acm.org> References: <8C0A7198-726E-4961-AEA1-C71996B0E83A@opencsw.org> <20090102185525.GA7106@bolthole.com> <5BDC55EF-D466-42E1-88D5-6BEC2A20198B@opencsw.org> <4965FA6A.1010908@opencsw.org> <4966066B.4060804@acm.org> Message-ID: <49790BB5.6030201@opencsw.org> Alessio wrote: > xterm 238 is now available on /testing Any chance that this can be pushed to current? I have been using it quite happily over the last two weeks and xterm 235 which we currently carry in the catalog has known security issues. http://opencsw.org/bugtrack/view.php?id=2978 Sebastian From harpchad at opencsw.org Fri Jan 23 03:45:46 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 22 Jan 2009 20:45:46 -0600 Subject: [csw-maintainers] Library dependency search Message-ID: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> Prior to the last release or curl I did a search on http:// www.opencsw.org/search (exact match) for libcurl.so.3 to see if any packages still depended on the older version. I didn't find any so I didn't include them in the new release. It turns out there is at least 1 package that does depend on it (grip). So is the search engine broken, or am I just using it wrong (or not understanding what it searches on)? --chad From phil at bolthole.com Fri Jan 23 04:59:19 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 19:59:19 -0800 Subject: [csw-maintainers] Library dependency search In-Reply-To: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> References: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> Message-ID: <20090123035919.GA59756@bolthole.com> On Thu, Jan 22, 2009 at 08:45:46PM -0600, Chad Harp wrote: > Prior to the last release or curl I did a search on http:// > www.opencsw.org/search (exact match) for libcurl.so.3 to see if any > packages still depended on the older version. I didn't find any so I > didn't include them in the new release. > > It turns out there is at least 1 package that does depend on it (grip). > > So is the search engine broken, or am I just using it wrong (or not > understanding what it searches on)? Hmm.. that's odd. I see "libcurl.so.3" in the dependancy database. but it doesnt come up on the search page. I'll look into it. From phil at bolthole.com Fri Jan 23 05:10:26 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 20:10:26 -0800 Subject: [csw-maintainers] Library dependency search In-Reply-To: <20090123035919.GA59756@bolthole.com> References: <510025D1-63A3-4C75-8881-724A124218CC@opencsw.org> <20090123035919.GA59756@bolthole.com> Message-ID: <20090123041026.GB59756@bolthole.com> On Thu, Jan 22, 2009 at 07:59:19PM -0800, Philip Brown wrote: > I see "libcurl.so.3" in the dependancy database. but it doesnt come up on > the search page. I'll look into it. Aha.. you hit an edge case; you queried it, after "libcurl.so.3" did not exist in any active package. The search page made an invalid assumption, that if a shared lib did not exist in any existing package, there was no point in doing a dependancy search for that lib. now fixed. From phil at bolthole.com Fri Jan 23 06:35:25 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 22 Jan 2009 21:35:25 -0800 Subject: [csw-maintainers] Best-practice on texinfo - cswclassutils? In-Reply-To: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> References: <2800FF38-2630-412B-87A6-0F10F60A6F64@opencsw.org> Message-ID: <20090123053525.GL71834@bolthole.com> On Thu, Jan 22, 2009 at 05:09:41PM +0100, Dagobert Michelsen wrote: > Hi, > > I noticed that some legacy packages have an integration of > regenerating the texinfo index when files are added in a > package. We don't have anything in GAR for this yet. I guess > it would be nice to have that in cswclassutils. Thoughts? yes, precisely. that is on my waay-too-long todo list. would be nice if someone else did that class script. [ so XXX.info files, can be of class cswtexinfo, and the info 'dir' file can be automatically regenerated when needed ] From trygvis at opencsw.org Fri Jan 23 11:45:31 2009 From: trygvis at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 23 Jan 2009 11:45:31 +0100 Subject: [csw-maintainers] Status of the suggestions In-Reply-To: <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> References: <496FAB77.8000208@wbonnet.net> <20090118194810.GE81262@bolthole.com> <9ABD9F65-65F0-4FFA-9BE1-37F49F054C2B@opencsw.org> <625385e30901211112t7ca6265fr59fef736bebebd1a@mail.gmail.com> <4978D9C2.2070904@opencsw.org> <625385e30901221308n4c7f680if25e9a95de28b154@mail.gmail.com> <4978F861.2040301@opencsw.org> <625385e30901221543l66a51f7aob015b58c040e2e1d@mail.gmail.com> Message-ID: <49799FCB.3070509@opencsw.org> Peter Bonivart wrote: > On Thu, Jan 22, 2009 at 11:51 PM, Trygve Laugst?l wrote: >> You know I've already given you several feature requests. > > ...and I'm working on that... :-) Excellent! I'm looking forward to trying out 1.4. -- Trygve From dam at opencsw.org Fri Jan 23 16:18:11 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:18:11 +0100 Subject: [csw-maintainers] [csw-users] lsof In-Reply-To: <4978E284.CC54.005D.3@emporia.edu> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220929q3251d481ye4cf0ddbe57314e8@mail.gmail.com> <20090122223502.GA2836@keevey> <4978E284.CC54.005D.3@emporia.edu> Message-ID: <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> Hi Glen, Am 23.01.2009 um 04:17 schrieb Glen Gunselman: > Are there any plans to update lsof? > > It looks like an update has been requested several times in the past. Plans, yes. We don't currently have Solaris 9 build machines in the farm. I look into it. BTW: If I recall correctly you offered to help in november. We are desperately needing testers who try out stuff in testing at and give feedback. It would be a great help if you used the new packages on some of your machines. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Jan 23 16:24:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:24:54 +0100 Subject: [csw-maintainers] Updating CSW packages on the buildfarm now Message-ID: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> Hi, I am updating all installed CSW packages form the buildfarms to the most recent versions in current/ now. I'll let you know when I'm finished. Sorry for inconvenience -- Dago From dam at opencsw.org Fri Jan 23 16:47:43 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 16:47:43 +0100 Subject: [csw-maintainers] [csw-buildfarm] Updating CSW packages on the buildfarm now In-Reply-To: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> References: <2B97B646-C92E-43CA-A986-FE36B0B57F4C@opencsw.org> Message-ID: <67F910E3-2C1F-4EEA-8043-3311A0068684@opencsw.org> Hi, Am 23.01.2009 um 16:24 schrieb Dagobert Michelsen: > I am updating all installed CSW packages form the buildfarms to the > most recent versions in current/ now. I'll let you know when I'm > finished. All buildfarm servers now run current. Best regards -- Dago From harpchad at opencsw.org Fri Jan 23 20:04:56 2009 From: harpchad at opencsw.org (Chad Harp) Date: Fri, 23 Jan 2009 13:04:56 -0600 Subject: [csw-maintainers] Mantis issue Message-ID: <497A14D8.9090406@opencsw.org> I was opening bugs against several packages today. I opened four tabs in my browser, one for each project, and submitted the reports. But all four reports were filed against the last tab I opened. Apparently Mantis uses cookies to track the active project rather than fields in the post data? Is that fixed in a later revision? Can one of the Mantis admins remove bugs 3039, 3040 and 3041 from bzflag? Sorry, Chad From dam at opencsw.org Fri Jan 23 20:14:05 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 20:14:05 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Hi, I put the monthly thematics proposal in the Wiki at for further reference. If you feel your points in the discussion should be reflected on the page please reply with the updates. Thanks! -- Dago From dam at opencsw.org Fri Jan 23 22:21:39 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 23 Jan 2009 22:21:39 +0100 Subject: [csw-maintainers] Now available: build9s Message-ID: Fellow maintainers, an OpenCSW-user has recently requested an updated version from top. top needs to be compiled on each Solaris version separately, so it is necessary to have a Solaris 9 build infrastructure. The Sparc server is available now: build9s Let me know if you encounter anything strange. The x86 version build9x will follow soon. Thanks! -- Dago From phil at bolthole.com Sat Jan 24 00:32:21 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 23 Jan 2009 15:32:21 -0800 Subject: [csw-maintainers] /testing: new gd package Message-ID: <20090123233221.GJ57355@bolthole.com> i just made a new gd package and dropped it in testing. i hope folks will give it a spin and verify that it fixes the issues with the current one. From dam at opencsw.org Sat Jan 24 22:37:37 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 24 Jan 2009 22:37:37 +0100 Subject: [csw-maintainers] Design decision: NFS-Sharing against OS-specific branches Message-ID: <62A15A05-A76C-4A51-8AC5-720AD7B8C86B@opencsw.org> Hi, I am currently inspecting some packages to be renewed and some like lsof have binaries for all os releases in it: As this is of course necessary for NFS-sharing it makes different directories in the mirror like redundant. What is the way to go here? Include all in one package if feasible and keep directories for the difficult ones? Best regards -- Dago From william at wbonnet.net Sun Jan 25 11:09:49 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 11:09:49 +0100 Subject: [csw-maintainers] Thematics month proposal Message-ID: <497C3A6D.9040403@wbonnet.net> Hi Dagobert > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > Thanks :) I would like to put online the text i've written about events, but i cannot modify the page. I have the following permission error : Oooops! Sorry, you can not edit this page. Only members of this site, site administrators and perhaps selected moderators are allowed to. Anyone knows what can i do ? thanks in advance cheers ps: i used a wrong email address to send this email, i resend it, you can delete it from moderation queue. Sorry ... :) -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From bonivart at opencsw.org Sun Jan 25 11:15:35 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 25 Jan 2009 11:15:35 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497C3A6D.9040403@wbonnet.net> References: <497C3A6D.9040403@wbonnet.net> Message-ID: <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> On Sun, Jan 25, 2009 at 11:09 AM, William Bonnet wrote: > I would like to put online the text i've written about events, but i > cannot modify the page. I have the following permission error : > > > Oooops! > > Sorry, you can not edit this page. Only members of this site, site > administrators and perhaps selected moderators are allowed to. > > > Anyone knows what can i do ? To edit the wiki you need a wikidot.com account and then join the OpenCSW wiki. I can send you an invite to ease things for you. -- /peter From korpela at ssl.berkeley.edu Fri Jan 23 00:27:53 2009 From: korpela at ssl.berkeley.edu (Eric J Korpela) Date: Thu, 22 Jan 2009 15:27:53 -0800 Subject: [csw-maintainers] [csw-buildfarm] FYI: Temporarily deactivation .la-files In-Reply-To: References: <4978A12E.8090407@opencsw.org> <8DA4800E-66BF-41AB-97AE-7D0FE4543F00@opencsw.org> <4978BC00.8050706@opencsw.org> Message-ID: That should probably work. Some packages may need some fixes to their build scripts to bring them in line. Some stuff developed on Linux assumes that they are there, or that a library isn't there if the .la file isn't, but IMHO, that's a bug anyway. It also can make static linking a pain, but that's rarely required when using a package manager. Eric From ggunselm at emporia.edu Sat Jan 24 02:46:36 2009 From: ggunselm at emporia.edu (Glen Gunselman) Date: Fri, 23 Jan 2009 19:46:36 -0600 Subject: [csw-maintainers] [csw-users] lsof In-Reply-To: <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> References: <1231428990-sup-1369@ntdws12.chass.utoronto.ca> <20090122033613.GA31064@keevey> <20090122050944.GA31372@keevey> <625385e30901220929q3251d481ye4cf0ddbe57314e8@mail.gmail.com> <20090122223502.GA2836@keevey> <4978E284.CC54.005D.3@emporia.edu> <93485876-6935-4C77-AEDD-11B8929706AB@opencsw.org> Message-ID: <497A1E9C.CC54.005D.3@emporia.edu> I looked over the current stuff available for testing and I'm not currently using any of it in a Solaris environment. I'm looking for a current lsof for a Solaris 10 system (update 5). Thanks and have a good weekend, Glen Gunselman Systems Software Specialist TCS Emporia State University >>> Dagobert Michelsen 1/23/2009 9:18 AM >>> Hi Glen, Am 23.01.2009 um 04:17 schrieb Glen Gunselman: Are there any plans to update lsof? It looks like an update has been requested several times in the past. Plans, yes. We don't currently have Solaris 9 build machines in the farm. I look into it. BTW: If I recall correctly you offered to help in november. We are desperately needing testers who try out stuff in testing at and give feedback. It would be a great help if you used the new packages on some of your machines. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From wbonnet at opencsw.org Sun Jan 25 00:27:17 2009 From: wbonnet at opencsw.org (William Bonnet) Date: Sun, 25 Jan 2009 00:27:17 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Message-ID: <497BA3D5.8060306@opencsw.org> Hi Dagobert > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > Thanks :) I would like to put online the text i've written about events, but i cannot modify the page. I have the following permission error : Oooops! Sorry, you can not edit this page. Only members of this site, site administrators and perhaps selected moderators are allowed to. Anyone knows what can i do ? thanks in advance cheers -- William Bonnet http://www.wbonnet.net http://www.opencsw.org Community SoftWare for Solaris From william at wbonnet.net Sun Jan 25 12:29:10 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 12:29:10 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> References: <497C3A6D.9040403@wbonnet.net> <625385e30901250215k3bbd35aj7994a19ab7ec52c@mail.gmail.com> Message-ID: <497C4D06.3060102@wbonnet.net> Hi Peter > To edit the wiki you need a wikidot.com account and then join the > OpenCSW wiki. I can send you an invite to ease things for you. > It works thanks :) I forgot one step. I only had an account. Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Sun Jan 25 19:44:21 2009 From: william at wbonnet.net (William Bonnet) Date: Sun, 25 Jan 2009 19:44:21 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> Message-ID: <497CB305.8050807@wbonnet.net> Hi > I put the monthly thematics proposal in the Wiki at > > for further reference. If you feel your points in > the discussion should be reflected on the page please > reply with the updates. > I have added some details to this page. Comments feedback are welcome. Does anyone disagree with the fact that first theme should be communication ? Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 26 04:17:40 2009 From: phil at bolthole.com (Philip Brown) Date: Sun, 25 Jan 2009 19:17:40 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497CB305.8050807@wbonnet.net> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> Message-ID: <20090126031740.GE22989@bolthole.com> On Sun, Jan 25, 2009 at 07:44:21PM +0100, William Bonnet wrote: > I have added some details to this page. Comments feedback are welcome. > > Does anyone disagree with the fact that first theme should be > communication ? I think it is not focused enough. I think that the way you have currently worded it, includes both "better communication with existing users", and also "better ADVERTISING". I think that each deserves its own full month of focus. From dam at opencsw.org Mon Jan 26 11:06:53 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 26 Jan 2009 11:06:53 +0100 Subject: [csw-maintainers] New server build9x Message-ID: Hi, I finally managed to add the missing Solaris 9 x86 build server: build9x We have now a full set of Solaris 8, 9 and 10 for both sparc and x86. Ben: This time I remembered to add all buildfarm-admins from the start :-) Have fun! -- Dago From william at wbonnet.net Mon Jan 26 12:59:33 2009 From: william at wbonnet.net (William Bonnet) Date: Mon, 26 Jan 2009 12:59:33 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090126031740.GE22989@bolthole.com> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> Message-ID: <497DA5A5.1000407@wbonnet.net> Hi > I think it is not focused enough. > > I think that the way you have currently worded it, includes both > "better communication with existing users", and also > "better ADVERTISING". > That's right My question was "Are you ok that first theme is communication ? If no, please let us know, if yes let's start writing detailled content before 1st of Feb". I'll start to work and write on this tomorrow night. > I think that each deserves its own full month of focus. > Surely. It is a large area to be covered for both subject. What i target for first month is to do as much as we can on both subjects. We won't cover everything, and we will have to work on this again. Now we first we have to create the foundation of our communication and advertising, refresh and update some documentation, put content into the new web site, and setup a communication strategy with users. I'll create a wiki page about this tomorrow (today it's a long long day at office...) Cheers, W. > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers > -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Mon Jan 26 16:59:35 2009 From: phil at bolthole.com (Philip Brown) Date: Mon, 26 Jan 2009 07:59:35 -0800 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <497DA5A5.1000407@wbonnet.net> References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> Message-ID: <20090126155935.GF84666@bolthole.com> On Mon, Jan 26, 2009 at 12:59:33PM +0100, William Bonnet wrote: > Hi *wave* > > I think that each deserves its own full month of focus. > > > Surely. It is a large area to be covered for both subject. What i target > for first month is to do as much as we can on both subjects. We won't > cover everything, and we will have to work on this again. Now we first > we have to create the foundation of our communication and advertising, > refresh and update some documentation, .... I think that once we have an advertising blitz, it would be best for the new people to see our site, etc. at its best. So it would be the most strategic, to first improve our "user communication", *before* doing all the advertising. So I would like to propose the first month be "communication", possibly overlapping with *planning* advertising, and then the month after that be when we actually do the advertising. From pfelecan at opencsw.org Mon Jan 26 17:54:45 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Mon, 26 Jan 2009 17:54:45 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: <20090126155935.GF84666@bolthole.com> (Philip Brown's message of "Mon\, 26 Jan 2009 07\:59\:35 -0800") References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> <20090126155935.GF84666@bolthole.com> Message-ID: Philip Brown writes: > On Mon, Jan 26, 2009 at 12:59:33PM +0100, William Bonnet wrote: >> > I think that each deserves its own full month of focus. >> > >> Surely. It is a large area to be covered for both subject. What i target >> for first month is to do as much as we can on both subjects. We won't >> cover everything, and we will have to work on this again. Now we first >> we have to create the foundation of our communication and advertising, >> refresh and update some documentation, .... > > I think that once we have an advertising blitz, it would be best for the > new people to see our site, etc. at its best. So it would be the most > strategic, to first improve our "user communication", *before* doing all > the advertising. So I would like to propose the first month be > "communication", possibly overlapping with *planning* advertising, and then > the month after that be when we actually do the advertising. It seems to me most reasonable to do it in that order, i.e., user communication and then advertising. But don't forget to update the thematics page accordingly. -- Peter From william at wbonnet.net Tue Jan 27 09:55:32 2009 From: william at wbonnet.net (William Bonnet) Date: Tue, 27 Jan 2009 09:55:32 +0100 Subject: [csw-maintainers] Thematics month proposal In-Reply-To: References: <172596FD-38C1-4BAE-A198-1A5EDB7F7E55@opencsw.org> <497CB305.8050807@wbonnet.net> <20090126031740.GE22989@bolthole.com> <497DA5A5.1000407@wbonnet.net> <20090126155935.GF84666@bolthole.com> Message-ID: <497ECC04.2090603@wbonnet.net> Hi guys >> I think that once we have an advertising blitz, it would be best for the >> new people to see our site, etc. at its best. So it would be the most >> strategic, to first improve our "user communication", *before* doing all >> the advertising. So I would like to propose the first month be >> "communication", possibly overlapping with *planning* advertising, and then >> the month after that be when we actually do the advertising. >> > > It seems to me most reasonable to do it in that order, i.e., user > communication and then advertising. But don't forget to update the > thematics page accordingly. > That's the good way to do it for sure :) I'll create a new page linked from thematics events for detailed description of the first event. What i had in my mind was to work on materials we need during this month, then at the end of month start massive communication. Well it's time for my first meeting of the day ;) more to come later. cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From pfelecan at opencsw.org Tue Jan 27 17:51:16 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 27 Jan 2009 17:51:16 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues Message-ID: Here is a story which shows an additional reason to have a better "communication": I'm a CSW maintainer since a few years. Not really active since some time but considering to submit some updated packages. In the "old world" I copied the packages to /export/newpkgs and sent a mail to Phil. In the "new world", on the only relevant page of our site, http://www.opencsw.org/standards/pkg-walkthrough, I read that I must "copy your finished packages to /home/newpkgs on www.opencsw.org". Being connected on login.opencsw.org I try to scp the package but I'm asked for a password. What password? I supplied many time my public key and I'm expecting to be authorized to release a package. I searched also the maintainers mailing list. Phil explains how to submit a package. But there is not a word about authorization. The only reference is a request by another maintainer in the same situation as mine. Again, no reference to an authorization procedure. Is there a kind soul who can explain the whole process, with an example, please? Maybe that before addressing the issue of communication toward the users we should enhance the one destined to the maintainers. -- Peter From phil at bolthole.com Tue Jan 27 20:20:34 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 27 Jan 2009 11:20:34 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: Message-ID: <20090127192034.GA54002@bolthole.com> On Tue, Jan 27, 2009 at 05:51:16PM +0100, Peter FELECAN wrote: >... > ... In the "new world", on the only relevant page of our site, > http://www.opencsw.org/standards/pkg-walkthrough, I read that I must > "copy your finished packages to /home/newpkgs on www.opencsw.org". > > Being connected on login.opencsw.org I try to scp the package but I'm > asked for a password. What password? I supplied many time my public key > and I'm expecting to be authorized to release a package. > ... > Is there a kind soul who can explain the whole process, with an example, > please? > It seems that the only "piece of the puzzle" you are missing from the process, is an easy way to copy a package from build machines, to www. Unfortunately, older maintainer accounts, do not have the scp set up to be seamless by default. But, since you have full login access to both machines already, you yourself have the power to "fix" this, as on any other unix machine that you scp to and from. if you scp the .ssh/id_dsa.pub from login, back to your normal (desktop?) machine, then copy it from there, over to www, and then append it to the authorized_keys file there, then you will have just given yourself access to scp directly between login.bo.opencsw.org, and www.opencsw.org I have also updated the web page with this information. From pfelecan at opencsw.org Tue Jan 27 21:41:57 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Tue, 27 Jan 2009 21:41:57 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090127192034.GA54002@bolthole.com> (Philip Brown's message of "Tue\, 27 Jan 2009 11\:20\:34 -0800") References: <20090127192034.GA54002@bolthole.com> Message-ID: Philip Brown writes: > On Tue, Jan 27, 2009 at 05:51:16PM +0100, Peter FELECAN wrote: >>... >> ... In the "new world", on the only relevant page of our site, >> http://www.opencsw.org/standards/pkg-walkthrough, I read that I must >> "copy your finished packages to /home/newpkgs on www.opencsw.org". >> >> Being connected on login.opencsw.org I try to scp the package but I'm >> asked for a password. What password? I supplied many time my public key >> and I'm expecting to be authorized to release a package. >> ... >> Is there a kind soul who can explain the whole process, with an example, >> please? >> > > It seems that the only "piece of the puzzle" you are missing from the > process, is an easy way to copy a package from build machines, to www. Indeed. > Unfortunately, older maintainer accounts, do not have the scp set up to be > seamless by default. Older? What defines "older"? > But, since you have full login access to both machines already, you > yourself have the power to "fix" this, as on any other unix machine that > you scp to and from. > > if you scp the .ssh/id_dsa.pub from login, back to your normal > (desktop?) machine, then copy it from there, over to www, and then > append it to the authorized_keys file there, then you will have just given > yourself access to scp directly between login.bo.opencsw.org, and > www.opencsw.org Trying to connect to pfelecan at www.opencsw.org requires a password that I have not. Consequently, I cannot fix it myself. BTW, I cannot see the changes to the documentation? Can you give me a reference URI? -- Peter From phil at bolthole.com Tue Jan 27 22:37:48 2009 From: phil at bolthole.com (Philip Brown) Date: Tue, 27 Jan 2009 13:37:48 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: <20090127192034.GA54002@bolthole.com> Message-ID: <20090127213748.GA13932@bolthole.com> On Tue, Jan 27, 2009 at 09:41:57PM +0100, Peter FELECAN wrote: > > > Unfortunately, older maintainer accounts, do not have the scp set up to be > > seamless by default. > > Older? What defines "older"? older than two weeks ago. so, "accounts created before jan 2009" > > if you scp the .ssh/id_dsa.pub from login, back to your normal > > (desktop?) machine, then copy it from there, over to www, and then > > append it to the authorized_keys file there, then you will have just given > > yourself access to scp directly between login.bo.opencsw.org, and > > www.opencsw.org > > Trying to connect to pfelecan at www.opencsw.org requires a password that I > have not. Consequently, I cannot fix it myself. Hmmm...... i tried tweaking one thing on www. please try again. also, please note that it is expecting ssh access from the host that has your public key on it which ends in: 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan From harpchad at opencsw.org Tue Jan 27 22:44:44 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 27 Jan 2009 15:44:44 -0600 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) Message-ID: <497F804C.7080503@opencsw.org> I want to propose and get feedback on the following patch to gar. I'd like to add a configuration variable called ISAEXEC_EXCLUDE_FILES. The purpose of this variable would be to define items that should not be moved to a bin/$(ISA) directory and wrapped with isaexec. Examples of executables that you may not want to wrap: shell & other interpreted language scripts symbolic links (i.e. view->vim, no need to wrap the view symlink) executables that wouldn't benefit from 64bit support I've implemented this in the attached patch by adding another flag to pathfilter (-n) and calling it with the excluded files from gar.pkg.mk I've done some testing and it works as I need it to. Hopefully I haven't missed a simpler way to do this. --chad -------------- next part -------------- A non-text attachment was scrubbed... Name: isaexec_exclude.patch Type: text/x-patch Size: 2290 bytes Desc: not available URL: From dam at opencsw.org Tue Jan 27 22:57:27 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 27 Jan 2009 22:57:27 +0100 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <497F804C.7080503@opencsw.org> References: <497F804C.7080503@opencsw.org> Message-ID: <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> Hi Chad, Am 27.01.2009 um 22:44 schrieb Chad Harp: > I want to propose and get feedback on the following patch to gar. > > I'd like to add a configuration variable called > ISAEXEC_EXCLUDE_FILES. The purpose of this variable would be to > define items that should not be moved to a bin/$(ISA) directory and > wrapped with isaexec. > > Examples of executables that you may not want to wrap: > shell & other interpreted language scripts > symbolic links (i.e. view->vim, no need to wrap the view symlink) > executables that wouldn't benefit from 64bit support This sounds reasonable. > I've implemented this in the attached patch by adding another flag > to pathfilter (-n) and calling it with the excluded files from > gar.pkg.mk > I've done some testing and it works as I need it to. Hopefully I > haven't missed a simpler way to do this. Well, it should work but I think you have missed a simpler way to do this ;-) The list of files to be isaexec'ed is defined in ISAEXEC_FILES in gar.mk, which adds one option per isaexec-file to pathfilter. Taking them out at pathfilter after explicitly passing them to pathfilter looks wrong to me. It is easier to add something like ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. I'll take a look tomorrow. Best regards -- Dago From harpchad at opencsw.org Tue Jan 27 23:03:13 2009 From: harpchad at opencsw.org (Chad Harp) Date: Tue, 27 Jan 2009 16:03:13 -0600 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> References: <497F804C.7080503@opencsw.org> <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> Message-ID: <497F84A1.9@opencsw.org> Dagobert Michelsen wrote: > > Well, it should work but I think you have missed a simpler way to do > this ;-) > The list of files to be isaexec'ed is defined in ISAEXEC_FILES in > gar.mk, which > adds one option per isaexec-file to pathfilter. Taking them out at > pathfilter > after explicitly passing them to pathfilter looks wrong to me. It is > easier > to add something like > ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) > where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. > I'll take a look tomorrow. That does sound simpler, I based it on the existing -x functionality for PKGFILES_EXCLUDE, but I think stripping it prior to calling pathfilter would have the same result. From pfelecan at opencsw.org Wed Jan 28 09:37:21 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 28 Jan 2009 09:37:21 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090127213748.GA13932@bolthole.com> (Philip Brown's message of "Tue\, 27 Jan 2009 13\:37\:48 -0800") References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> Message-ID: Philip Brown writes: > On Tue, Jan 27, 2009 at 09:41:57PM +0100, Peter FELECAN wrote: >> >> > Unfortunately, older maintainer accounts, do not have the scp set up to be >> > seamless by default. >> >> Older? What defines "older"? > > older than two weeks ago. so, "accounts created before jan 2009" Never saw a discussion about this kind of stuff on the maintainers mailing list. BTW, it means that almost everybody has this issue. >> > if you scp the .ssh/id_dsa.pub from login, back to your normal >> > (desktop?) machine, then copy it from there, over to www, and then >> > append it to the authorized_keys file there, then you will have just given >> > yourself access to scp directly between login.bo.opencsw.org, and >> > www.opencsw.org >> >> Trying to connect to pfelecan at www.opencsw.org requires a password that I >> have not. Consequently, I cannot fix it myself. > > Hmmm...... > i tried tweaking one thing on www. please try again. ssh pfelecan at www.opencsw.org Password: Received disconnect from 147.87.98.73: 2: Too many authentication failures for pfelecan > also, please note that it is expecting ssh access from the host that has > your public key on it which ends in: > > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan That's the case. -- Peter From bonivart at opencsw.org Wed Jan 28 09:47:27 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 28 Jan 2009 09:47:27 +0100 Subject: [csw-maintainers] /testing dhcp 4.1.0 Message-ID: <625385e30901280047j5823f0dfkc289fe0997ce3310@mail.gmail.com> I would like some help testing the new ISC DHCP 4.1.0 packages. They use cswclassutils for configuration file handling and SMF support. http://mirror.opencsw.org/testing.html dhcp-4.1.0,REV=2009.01.27-SunOS5.8-sparc-CSW.pkg.gz dhcp-4.1.0,REV=2009.01.27-SunOS5.8-i386-CSW.pkg.gz dhcp_devel-4.1.0,REV=2009.01.27-SunOS5.8-sparc-CSW.pkg.gz dhcp_devel-4.1.0,REV=2009.01.27-SunOS5.8-i386-CSW.pkg.gz -- /peter From dam at opencsw.org Wed Jan 28 11:35:00 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 11:35:00 +0100 Subject: [csw-maintainers] Proposed patch for mgar v2 (ISAEXEC_EXCLUDE_FILES) In-Reply-To: <497F84A1.9@opencsw.org> References: <497F804C.7080503@opencsw.org> <553CFABF-1CE5-4C72-81E6-7528A05EC4E8@opencsw.org> <497F84A1.9@opencsw.org> Message-ID: <8C85C443-6D93-43A6-9CF9-5534E9B7C71B@opencsw.org> Hi Chad, Am 27.01.2009 um 23:03 schrieb Chad Harp: > Dagobert Michelsen wrote: >> Well, it should work but I think you have missed a simpler way to do >> this ;-) >> The list of files to be isaexec'ed is defined in ISAEXEC_FILES in >> gar.mk, which >> adds one option per isaexec-file to pathfilter. Taking them out at >> pathfilter >> after explicitly passing them to pathfilter looks wrong to me. It is >> easier >> to add something like >> ISAEXEC_FILES = $(filter-out $(ISAEXEC_EXCLUDE_FILES), ) >> where ISAEXEC_EXCLUDE_FILES is applied one-file-at-a-time in gar.mk. >> I'll take a look tomorrow. > > That does sound simpler, I based it on the existing -x functionality > for > PKGFILES_EXCLUDE, but I think stripping it prior to calling pathfilter > would have the same result. I implemented this in r2918. Please test it and see if this fixes your request :-) Best regards -- Dago From dam at opencsw.org Wed Jan 28 13:44:12 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 13:44:12 +0100 Subject: [csw-maintainers] Fwd: [csw-users] HELP - non functioning openssl References: <49805295.6030602@ericsson.com> Message-ID: <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> Hi, FYI on users@ Best regards -- Dago Anfang der weitergeleiteten E-Mail: > Von: Mats Larsson > Datum: 28. Januar 2009 13:41:57 MEZ > An: users at lists.opencsw.org > Kopie: Ove Lundell > Betreff: [csw-users] HELP - non functioning openssl > Antwort an: questions and discussions > > Hi all, > > Latest 'pkg-get -uU' gave me a amongst others a non functioning > openssl. > I'm not even able to do a 'pkg-get -uU' any more: > > # pg -uU > Getting catalog... > ld.so.1: wget: fatal: libssl.so.0.9.8: open failed: No such file or > directory > /usr/bin/pkg-get[34]: 20393 Killed > > So I went to > http://www.ibiblio.org/pub/packages/solaris/opencsw/unstable/sparc/ > 5.8/ > and downloaded > openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg.gz since > libssl.so.0.9.8 live there and did try to pkgadd it instead > > pkgadd -d > ~/downloads/openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc- > CSW.pkg > > # pkgadd -d openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc- > CSW.pkg > ... > > ## Executing checkinstall script. > /var/tmp/dstreAAAIpaW1N/CSWosslrt/install/checkinstall: test: argument > expected > pkgadd: ERROR: checkinstall script did not complete successfully > > Installation of failed. > No changes were made to the system. > > I'm lost. Any help appreciated. > > BR MOL > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users From yann at pleiades.fr.eu.org Wed Jan 28 14:31:28 2009 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Wed, 28 Jan 2009 14:31:28 +0100 Subject: [csw-maintainers] Fwd: [csw-users] HELP - non functioning openssl In-Reply-To: <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> References: <49805295.6030602@ericsson.com> <95CA7217-751D-4F7B-B743-4F9D7F1B15F4@opencsw.org> Message-ID: <49805E30.9000006@pleiades.fr.eu.org> For the "test argument expected", I am currently producing a new package fixing this bug. I already received an email about it today: http://www.opencsw.org/mantis/view.php?id=3050 BTW, I didn't catch this bug because I have only a solaris 10 server. Would it be possible to have root access on some solaris 8 server ? It would even nicer to have some automatic script to test package installation (like piuparts on Debian), but that might be not so easy on Solaris. Yann Dagobert Michelsen a ?crit : > Hi, > > FYI on users@ > > Best regards > > -- Dago > > Anfang der weitergeleiteten E-Mail: > >> Von: Mats Larsson >> Datum: 28. Januar 2009 13:41:57 MEZ >> An: users at lists.opencsw.org >> Kopie: Ove Lundell >> Betreff: [csw-users] HELP - non functioning openssl >> Antwort an: questions and discussions >> >> Hi all, >> >> Latest 'pkg-get -uU' gave me a amongst others a non functioning openssl. >> I'm not even able to do a 'pkg-get -uU' any more: >> >> # pg -uU >> Getting catalog... >> ld.so.1: wget: fatal: libssl.so.0.9.8: open failed: No such file or >> directory >> /usr/bin/pkg-get[34]: 20393 Killed >> >> So I went to >> http://www.ibiblio.org/pub/packages/solaris/opencsw/unstable/sparc/5.8/ >> and downloaded >> openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg.gz since >> libssl.so.0.9.8 live there and did try to pkgadd it instead >> >> pkgadd -d >> ~/downloads/openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg >> >> # pkgadd -d openssl_rt-0.9.8,REV=2009.01.25_rev=j-SunOS5.8-sparc-CSW.pkg >> ... >> >> ## Executing checkinstall script. >> /var/tmp/dstreAAAIpaW1N/CSWosslrt/install/checkinstall: test: argument >> expected >> pkgadd: ERROR: checkinstall script did not complete successfully >> >> Installation of failed. >> No changes were made to the system. >> >> I'm lost. Any help appreciated. >> >> BR MOL >> _______________________________________________ >> users mailing list >> users at lists.opencsw.org >> https://lists.opencsw.org/mailman/listinfo/users > From harpchad at opencsw.org Wed Jan 28 17:27:22 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 10:27:22 -0600 Subject: [csw-maintainers] .la discussion Message-ID: <4980876A.8070806@opencsw.org> There's been discussion, but I'm not sure there's a consensus yet. I've got some .la files that are causing issues. I've seen some requests to have them deleted (on a single file basis) from the build farm, is that how we should handle them for now? Should that e-mail go to the buildfarm list? I suspect there will be less work is we mass relocate them and add them as needed (i.e. there will be fewer requests for adds than deletes). --chad From phil at bolthole.com Wed Jan 28 18:02:51 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:02:51 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <4980876A.8070806@opencsw.org> References: <4980876A.8070806@opencsw.org> Message-ID: <20090128170250.GZ23122@bolthole.com> On Wed, Jan 28, 2009 at 10:27:22AM -0600, Chad Harp wrote: > There's been discussion, but I'm not sure there's a consensus yet. > > I've got some .la files that are causing issues. I've seen some > requests to have them deleted (on a single file basis) from the build > farm, is that how we should handle them for now? Should that e-mail go > to the buildfarm list? you should both email/contact the maintainer, and also the build farm, if you are in a hurry. if you are not in a hurry, then just contact the maintainer. > I suspect there will be less work is we mass relocate them and add them > as needed (i.e. there will be fewer requests for adds than deletes). there are "only" 10 packages with .la files on the build farm. So, it's not THAT much work, I would think. ones that are probably the easiest to fix, are: libsqlite3.la (Michael libgdbm.la (Me) libsasl2.la (Damjan) the notsoseay, are for libiconv and ggettext (both me, unfortunately) From phil at bolthole.com Wed Jan 28 18:05:39 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:05:39 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170250.GZ23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> Message-ID: <20090128170539.GB23122@bolthole.com> On Wed, Jan 28, 2009 at 09:02:51AM -0800, Philip Brown wrote: > libgdbm.la (Me) > ... > the notsoseay, are for libiconv and ggettext (both me, unfortunately) i should mention, that if anyone would LIKE to take over these packages, please speak up! ;-) From phil at bolthole.com Wed Jan 28 18:10:16 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:10:16 -0800 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> Message-ID: <20090128171016.GC23122@bolthole.com> On Wed, Jan 28, 2009 at 09:37:21AM +0100, Peter FELECAN wrote: > > also, please note that it is expecting ssh access from the host that has > > your public key on it which ends in: > > > > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan > > That's the case. Errr... it would appear that you have a different public key for external access, on login.bo.opencsw.org, than on www.opencsw.org I'm guessing the www one was a "legacy" one, that is no longer valid for you. Soooo.. i just copied over your login one, to www. you should now be able to access www from outside, AND from login. i think. From harpchad at opencsw.org Wed Jan 28 18:10:47 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:10:47 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170250.GZ23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> Message-ID: <49809197.8050801@opencsw.org> Philip Brown wrote: > you should both email/contact the maintainer, and also the build farm, if > you are in a hurry. > if you are not in a hurry, then just contact the maintainer. The packages are unmaintained. I'll send in buildfarm requests from the ones that are causing me issues. > there are "only" 10 packages with .la files on the build farm. > So, it's not THAT much work, I would think. harpchad at build8s (CSW)$ ls -1 /opt/csw/lib/*.la | wc -l 231 231 .la requests to buildfarm might result in no buildfarm maintainers :) From phil at bolthole.com Wed Jan 28 18:22:25 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:22:25 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <49809197.8050801@opencsw.org> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> Message-ID: <20090128172225.GF23122@bolthole.com> On Wed, Jan 28, 2009 at 11:10:47AM -0600, Chad Harp wrote: > > there are "only" 10 packages with .la files on the build farm. > > So, it's not THAT much work, I would think. > > harpchad at build8s (CSW)$ ls -1 /opt/csw/lib/*.la | wc -l > 231 oh. nuts. I did it on "login", not on "buildxxx" :-} Well, I'd say there are two "clean" ways to handle this. One is less work, and less clean to outside, but clean to US. Other is a lot more work, but clean to everyone. "clean to us": ssh buildX && rm /opt/csw/lib/lib*.la "clean to outside": make a list of all packages that have .la files, and graph em as dependancies, and then start prodding the appropriate people to repackage them starting at "leaf nodes" in the graph. Note: It's no good just doing a one-time repackage. we need to make sure that the maintainers build it "the next time" without .la files too. From harpchad at opencsw.org Wed Jan 28 18:25:46 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:25:46 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128172225.GF23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> Message-ID: <4980951A.2050003@opencsw.org> Philip Brown wrote: > Well, I'd say there are two "clean" ways to handle this. > One is less work, and less clean to outside, but clean to US. > Other is a lot more work, but clean to everyone. > > "clean to us": ssh buildX && rm /opt/csw/lib/lib*.la > > > "clean to outside": > make a list of all packages that have .la files, and graph em as > dependancies, and then start prodding the appropriate people > to repackage them starting at "leaf nodes" in the graph. > > Note: It's no good just doing a one-time repackage. we need to make sure > that the maintainers build it "the next time" without .la files too. Why not do both? The "clean to us" would allow our maintainers to continue building their packages while we take care of the "clean to outside". From phil at bolthole.com Wed Jan 28 18:43:01 2009 From: phil at bolthole.com (Philip Brown) Date: Wed, 28 Jan 2009 09:43:01 -0800 Subject: [csw-maintainers] .la discussion In-Reply-To: <4980951A.2050003@opencsw.org> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> <4980951A.2050003@opencsw.org> Message-ID: <20090128174301.GG23122@bolthole.com> On Wed, Jan 28, 2009 at 11:25:46AM -0600, Chad Harp wrote: > Philip Brown wrote: > > "clean to outside": > > make a list of all packages that have .la files, and graph em as > > dependancies, and then start prodding the appropriate people > > to repackage them starting at "leaf nodes" in the graph. > > > > Note: It's no good just doing a one-time repackage. we need to make sure > > that the maintainers build it "the next time" without .la files too. > > Why not do both? The "clean to us" would allow our maintainers to > continue building their packages while we take care of the "clean to > outside". you kinda missed the point of "clean to outside". If we are trying to remain "clean to outside", that means that "outside" people will be able to build easily on top of our published packages, without getting TOO messed up with .la missing linkages. The only way that can happen, is if we rebuild packages in a deterministic manner, working from the "leaf nodes" inward. If we just rm all the .la files, then we will effectively be clearing things for random package rebuilds, which will break the "clean to outside" paradigm". From harpchad at opencsw.org Wed Jan 28 18:58:35 2009 From: harpchad at opencsw.org (Chad Harp) Date: Wed, 28 Jan 2009 11:58:35 -0600 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128174301.GG23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <49809197.8050801@opencsw.org> <20090128172225.GF23122@bolthole.com> <4980951A.2050003@opencsw.org> <20090128174301.GG23122@bolthole.com> Message-ID: <49809CCB.60600@opencsw.org> Philip Brown wrote: > you kinda missed the point of "clean to outside". > > If we are trying to remain "clean to outside", that means that "outside" > people will be able to build easily on top of our published packages, > without getting TOO messed up with .la missing linkages. > > The only way that can happen, is if we rebuild packages in a deterministic > manner, working from the "leaf nodes" inward. > > If we just rm all the .la files, then we will effectively be clearing > things for random package rebuilds, which will break the "clean to outside" > paradigm". I understand the concept, but it will likely take some time to get all of the packages cleaned up (and find maintainers for the ones that need them). We don't have a clean build environment in either place today. I'm proposing we go ahead with "clean to inside" because it will facilitate "clean to outside". While it won't make it immediately possible to have a clean build environment on the outside, it will allow the active maintainers to update their packages where they otherwise might not be able to because of .la dependencies (at the same time removing .la files from their packages). While that's going on we try to push for updates on the remaining packages (starting with the leaf nodes), eventually cleaning the "outside" as well. From pfelecan at opencsw.org Wed Jan 28 19:26:23 2009 From: pfelecan at opencsw.org (Peter FELECAN) Date: Wed, 28 Jan 2009 19:26:23 +0100 Subject: [csw-maintainers] submitting a package and "communication" issues In-Reply-To: <20090128171016.GC23122@bolthole.com> (Philip Brown's message of "Wed\, 28 Jan 2009 09\:10\:16 -0800") References: <20090127192034.GA54002@bolthole.com> <20090127213748.GA13932@bolthole.com> <20090128171016.GC23122@bolthole.com> Message-ID: Philip Brown writes: > On Wed, Jan 28, 2009 at 09:37:21AM +0100, Peter FELECAN wrote: >> > also, please note that it is expecting ssh access from the host that has >> > your public key on it which ends in: >> > >> > 91tKRe0xDzP/kFca0oBQs1XDezE= pfelecan >> >> That's the case. > > Errr... it would appear that you have a different public key for external > access, on login.bo.opencsw.org, than on www.opencsw.org > > I'm guessing the www one was a "legacy" one, that is no longer valid for > you. > > Soooo.. i just copied over your login one, to www. > you should now be able to access www from outside, AND from login. > i think. Now it works. Thank you. -- Peter From dam at opencsw.org Wed Jan 28 21:39:45 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 21:39:45 +0100 Subject: [csw-maintainers] .la discussion In-Reply-To: <20090128170539.GB23122@bolthole.com> References: <4980876A.8070806@opencsw.org> <20090128170250.GZ23122@bolthole.com> <20090128170539.GB23122@bolthole.com> Message-ID: <56E111E6-A022-4839-90A2-57D275FBA4DB@opencsw.org> Hi Phil, Am 28.01.2009 um 18:05 schrieb Philip Brown: > On Wed, Jan 28, 2009 at 09:02:51AM -0800, Philip Brown wrote: >> libgdbm.la (Me) >> ... >> the notsoseay, are for libiconv and ggettext (both me, unfortunately) > > i should mention, that if anyone would LIKE to take over these > packages, > please speak up! ;-) Please send me your buildscripts so I can add them to the GAR for reference if volunteers pop up. For libiconv I have a 95% build recipe in GAR. Best regards -- Dago From dam at opencsw.org Wed Jan 28 22:18:49 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:18:49 +0100 Subject: [csw-maintainers] More thematics topics Message-ID: Hi, I have some proposals for thematics: (1) Tiering: Identify tier 1/2/3 packages and find people who adopt them (2) File bugs for packages containing .la-files (3) Go 64: Make sure libraries are always 32/64 bit for sparc / x86 (4) CPAN Coverage: Compare the OpenCSW offered modules against CPAN availability Timing: (1) April, with priority on tier 1 packages (2) Should be before Bug Hunting in May (3) Should also be before Bug Hunting as missing 64 bit libs could be considered a bug ;-) (4) Quite optional, end of year? Sounds reasonable? Best regards -- Dago From william at wbonnet.net Wed Jan 28 22:24:27 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:24:27 +0100 Subject: [csw-maintainers] Package creation problem Message-ID: <4980CD0B.3000609@wbonnet.net> Hi all I am currently facing a problem that goes far beyond my GAR knowledge... I started to move my old java libs package, and update them by the way, but i have a problem at package creation. In the Makefile i use a custom install step in which i create symlinks to jar files and licence. This links do exists in my install dir, and they do exists in the prototype files that are generated automatically. BUT they are not in the package once build. Anyone ( looking towards Dago direction... ) has an idea of what i did wrong ? Here is my custom-install steps. Everything is commited to gar in the beanutils folder. Thanks in advance cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:27:48 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:27:48 +0100 Subject: [csw-maintainers] Use of java folder Message-ID: <4980CDD4.5080106@wbonnet.net> Hi, Still talking about the beanutils package... but different subject. Beautils package is Apache Jakarta Commons Beanutils. A java lib. I have several libs to add to gar, and i was planning to add them to GAR under the java folder (just like there is xfce, x11 and cpan folders). A few weeks ago, Dago, you told me you were planning to put jdk packages under *java* , but i noticed they are the root of pkg. Do you still plan to do it or can i use it ? I you use it, is it a problem if i call my folder *javalibs* instead ? cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:30:30 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:30:30 +0100 Subject: [csw-maintainers] More thematics topics In-Reply-To: References: Message-ID: <4980CE76.3010601@wbonnet.net> Hi Dagobert > Sounds reasonable? > Sounds good to me. If we have enough volunteers it is not a problem to work on several theme at a time. Cheers, W. /me working on first theme... i'll publish some notes this friday or early in the week end -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 28 22:33:02 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:33:02 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <4980CD0B.3000609@wbonnet.net> References: <4980CD0B.3000609@wbonnet.net> Message-ID: Hi William, Am 28.01.2009 um 22:24 schrieb William Bonnet: > Here is my custom-install steps. Everything is commited to gar in the > beanutils folder. Please also commit gar/categories/java/category.mk ;-) Thanks! -- Dago From dam at opencsw.org Wed Jan 28 22:37:28 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:37:28 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <4980CDD4.5080106@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> Message-ID: <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> Hi William, Am 28.01.2009 um 22:27 schrieb William Bonnet: > Still talking about the beanutils package... but different subject. > > Beautils package is Apache Jakarta Commons Beanutils. A java lib. I > have > several libs to add to gar, and i was planning to add them to GAR > under > the java folder (just like there is xfce, x11 and cpan folders). A few > weeks ago, Dago, you told me you were planning to put jdk packages > under > *java* , but i noticed they are the root of pkg. Do you still plan > to do > it or can i use it ? I am still negatioating with Suns legal department. For reference I installed jdk6 / jre6 on build8s / build8x. I am very well aware that this is against the release-first policy, but as it does not have any side-effects on any other software I hope you'll forgive me ;-) > I you use it, is it a problem if i call my folder > *javalibs* instead ? javalibs/ or java/, both ok for me. Are you planning to do GAR magic in the category? If no, it is just a grouping. Best regards -- Dago From dam at opencsw.org Wed Jan 28 22:55:58 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 22:55:58 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: References: <4980CD0B.3000609@wbonnet.net> Message-ID: <8D4A6033-DAE1-477A-B486-A17B6DC7D0C3@opencsw.org> Hi William, Am 28.01.2009 um 22:33 schrieb Dagobert Michelsen: > Am 28.01.2009 um 22:24 schrieb William Bonnet: >> Here is my custom-install steps. Everything is commited to gar in the >> beanutils folder. > > Please also commit gar/categories/java/category.mk ;-) files/CSWajcbeanutils.gspec is missing also... Best regards -- Dago From william at wbonnet.net Wed Jan 28 22:56:14 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:56:14 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: References: <4980CD0B.3000609@wbonnet.net> Message-ID: <4980D47E.4050008@wbonnet.net> Hi Dago > Please also commit gar/categories/java/category.mk ;-) > > ooops :) done -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Wed Jan 28 22:59:06 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 22:59:06 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> References: <4980CDD4.5080106@wbonnet.net> <35983B31-751D-4A93-B710-D97FD0BA102A@opencsw.org> Message-ID: <4980D52A.3070206@wbonnet.net> Hi Dago > javalibs/ or java/, both ok for me. Are you planning to do GAR magic > in the > category? If no, it is just a grouping. > It is just a grouping. Category will be used to defines frequently used URL and regexp for uwatch (apache.org stuff etc.) I propose to use java so far, i think there is yet no special need to create too much extra dir. I'll can move libs to another later when we will have more packages. are you ok guys ? cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Wed Jan 28 23:08:49 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 28 Jan 2009 23:08:49 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <4980CD0B.3000609@wbonnet.net> References: <4980CD0B.3000609@wbonnet.net> Message-ID: <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> Hi William, Am 28.01.2009 um 22:24 schrieb William Bonnet: > In the Makefile i use a custom install step in which i create symlinks > to jar files and licence. This links do exists in my install dir, and > they do exists in the prototype files that are generated > automatically. > BUT they are not in the package once build. You mean in root/? That is normal, as links are generated during pkgadd. Have you tried adding the package? I guess the link is there :-) Best regards -- Dago From william at wbonnet.net Wed Jan 28 23:18:29 2009 From: william at wbonnet.net (William Bonnet) Date: Wed, 28 Jan 2009 23:18:29 +0100 Subject: [csw-maintainers] Package creation problem In-Reply-To: <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> References: <4980CD0B.3000609@wbonnet.net> <1A322ADE-8E21-44D5-B6FA-06D638FC4139@opencsw.org> Message-ID: <4980D9B5.2040109@wbonnet.net> Dagobert Michelsen wrote: > Hi William, > > Am 28.01.2009 um 22:24 schrieb William Bonnet: > >> In the Makefile i use a custom install step in which i create symlinks >> to jar files and licence. This links do exists in my install dir, and >> they do exists in the prototype files that are generated >> automatically. >> BUT they are not in the package once build. >> > > You mean in root/? That is normal, as links are generated during pkgadd. > Have you tried adding the package? I guess the link is there :-) > That's right :) Stupid me... i did not installed it but used pkgtrans to extract its content and i was expecting it to create the symlinks :( It's time to go to bed :D Thanks Dago, sorry for the noise cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From william at wbonnet.net Thu Jan 29 00:22:11 2009 From: william at wbonnet.net (William Bonnet) Date: Thu, 29 Jan 2009 00:22:11 +0100 Subject: [csw-maintainers] Licence file handling proposal Message-ID: <4980E8A3.1090305@wbonnet.net> Hi Tonight i talk about licenses with Trygve, and a need for a shared folder is here. After gathering our ideas, here is a first proposal for discussion. 1/ Creation of a "License package". This package will contains a list of files, each file is a licence text. In both full version, and short version (for pkgadd). Like the ca-certificate package, it is a reference datapackage that will be updated upon need. The files are stored under /opt/csw/share/licences. So as an example we will have the following layout : |-- opt `-- csw `-- share `-- licences |-- Apache_License_2.0_full_text.txt |-- Apache_License_2.0_desc.txt |-- GPL_2.0_full_text.txt |-- GPL_2.0_desc.txt |-- GPL_3.0_full_text.txt `-- GPL_3.0_desc.txt 2/ Use reference to theses files from installed packages (when applicable), and create and entry under /opt/csw/share/licences for each package For instance package foo which is released under GPL v2 will create the following entry |-- opt `-- csw `-- share `-- licences `-- foo `-- GPL_V2.0.txt -> /opt/csw/share/licenses/GPL_2.0_full_text.txt I think it is better to use the license name instead of license.txt for the symlink. So the user know immediately which license it is. Most of software are released under a single license, but for some packages it will be possible to create several link under the /opt/csw/share/license/ directory. If need a small readme.txt can explain that the software is released under several licenses. 3/ In the gspec file use a reference to the short "descriptive version" of the license. Doing this will reduce the output /garbage/ when installing a list of software under gpl. We do have a constraint to distribute the license with the package. If linking it to a license text is not enough (which is my guess). This will still be done as actually. Just keep the license.txt where they are actually, and for convenience use the symlinks and the short description. The short description can be like this : This software is distributed under the GNU General Public Licence V2 as published by the Free Software Foundation. See the file /opt/csw/share/licences/foo/GPL_V2.0.txt for the conditions under which this software is made available. What about this ? Cheers -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From korpela at opencsw.org Thu Jan 29 04:26:22 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Wed, 28 Jan 2009 19:26:22 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem Message-ID: I'm trying to install packages to test a build on my local machine (sparc Solaris 10) I installed pkg-get 4.0 2008.12.15 For example, one package dependency is mesalibs. Attempting to install it tells me that CSWcommon is not up to date. Attempting to update CSWcommon tells me that I have the current version installed. Updating the catalogs with -U doesn't help I've tried uninstalling all CSW packages and reinstalling pkg-get to no avail. -bash-3.00# pkg-get -i mesalibs No existing install of CSWmesa found. Installing... Pre-existing local file mesalibs-7.2,REV=2008.10.19-SunOS5.8-sparc-CSW.pkg.gz matches checksum Keeping existing file Analysing special files... Error: dependancy common (CSWcommon) not up to date Call pkg-get again in 'upgrade all' mode eg: '/opt/csw/bin/pkg-get upgrade' This will then upgrade all packages cleanly ERROR: could not install required dependancies for CSWmesa Once dependancies are up to date, call /opt/csw/bin/pkg-get -i mesalibs to (re)install -bash-3.00# pkg-get -u common No worries... you already have version 1.4.6,REV=2008.04.28 of common If you doubt this message, run 'pkg-get -U', then run 'pkg-get upgrade common' From Murray.Jensen at csiro.au Thu Jan 29 05:32:12 2009 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Thu, 29 Jan 2009 15:32:12 +1100 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: Your message of "Thu, 29 Jan 2009 14:26:22 +1100" Message-ID: <3226.1233203532@gerd> On Thu, 29 Jan 2009 14:26:22 +1100, Eric J Korpela writes: >... >Analysing special files... >Error: dependancy common (CSWcommon) not up to date >Call pkg-get again in 'upgrade all' mode >eg: '/opt/csw/bin/pkg-get upgrade' >This will then upgrade all packages cleanly >... So did you try running '/opt/csw/bin/pkg-get upgrade' ?? Cheers! Murray... -- Murray Jensen, CSIRO Materials Science and Engineering Phone: +61 3 9545 2075 Private Bag 33, Clayton South 3169, Australia Fax: +61 3 9544 1128 Internet: Murray.Jensen at csiro.au To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference. The information contained in this e-mail may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this e-mail in error, please delete it immediately and notify Murray Jensen on +61 3 9545 2075. Thank you. From phil at bolthole.com Thu Jan 29 13:18:02 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 04:18:02 -0800 Subject: [csw-maintainers] Licence file handling proposal In-Reply-To: <4980E8A3.1090305@wbonnet.net> References: <4980E8A3.1090305@wbonnet.net> Message-ID: <20090129121802.GC67198@bolthole.com> On Thu, Jan 29, 2009 at 12:22:11AM +0100, William Bonnet wrote: > |-- opt > `-- csw > `-- share > `-- licences > |-- Apache_License_2.0_full_text.txt > |-- Apache_License_2.0_desc.txt > |-- GPL_2.0_full_text.txt > |-- GPL_2.0_desc.txt > |-- GPL_3.0_full_text.txt > `-- GPL_3.0_desc.txt > > 2/ Use reference to theses files from installed packages (when > applicable), and create and entry under /opt/csw/share/licences for each > package for MOST of our packages, this is NOT applicable. the license file MUST be shipped with the package, for GPL'd packages, i believe. > Doing this will reduce the output /garbage/ when installing a list of > software under gpl. well, a common location for this stuff is not what fixes that issue. In contrast, the following bit does: > The short description can be like this : > > This software is distributed under the GNU General Public Licence V2 as published > by the Free Software Foundation. See the file /opt/csw/share/licences/foo/GPL_V2.0.txt > for the conditions under which this software is made available. This was already agreed upon (having the "i copyright" file say "go read this file here") and there are already packages that do this. From phil at bolthole.com Thu Jan 29 13:21:21 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 04:21:21 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: References: Message-ID: <20090129122121.GD67198@bolthole.com> Please send me, in private, output from pkg-get -c From bonivart at opencsw.org Thu Jan 29 17:49:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 29 Jan 2009 17:49:42 +0100 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site Message-ID: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> I was thinking about updating phpMyAdmin and happened to notice a bug in the display script for files: http://www.opencsw.org/search/phpmyadmin. Note that the true BASEDIR used is not included in the paths shown there, it's instead replaced by /opt/csw. I'm pretty sure I have reported this back in the Blastwave days and they show it correctly but somehow it's still wrong here. The other thing is that I vaguely remember that files shouldn't be dumped into /opt/csw/apache2/share/htdocs any more to be more web server neutral. But what was the new location? /var/opt/csw/www? -- /peter From skayser at opencsw.org Thu Jan 29 18:04:12 2009 From: skayser at opencsw.org (Sebastian Kayser) Date: Thu, 29 Jan 2009 18:04:12 +0100 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site In-Reply-To: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> References: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> Message-ID: <4981E18C.5040509@opencsw.org> Peter Bonivart wrote: > The other thing is that I vaguely remember that files shouldn't be > dumped into /opt/csw/apache2/share/htdocs any more to be more web > server neutral. But what was the new location? /var/opt/csw/www? According to http://opencsw.org/standards/layout: /opt/csw/share/www "pure php" and other arch-neutral web packages should deploy to here, for similar reasons to the java location. (One reason being that we dont want to limit the users' choice of web server if we dont have to). If there is a particular reason why the app doesnt belong under "share", though, perhaps /var/opt/csw/share/www or similar would be appropriate. Sebastian From korpela at opencsw.org Thu Jan 29 18:27:55 2009 From: korpela at opencsw.org (Eric J Korpela) Date: Thu, 29 Jan 2009 09:27:55 -0800 Subject: [csw-maintainers] pkg-get 4.0 problem In-Reply-To: <3226.1233203532@gerd> References: <3226.1233203532@gerd> Message-ID: > So did you try running '/opt/csw/bin/pkg-get upgrade' ?? Cheers! Yep. The upgrade fails on every package, because CSWcommon is supposedly out of date. Eric From phil at bolthole.com Thu Jan 29 19:50:31 2009 From: phil at bolthole.com (Philip Brown) Date: Thu, 29 Jan 2009 10:50:31 -0800 Subject: [csw-maintainers] phpMyAdmin: where to place files now and bug in file display script on web site In-Reply-To: <4981E18C.5040509@opencsw.org> References: <625385e30901290849v78b6b905ucd71ea12facd7669@mail.gmail.com> <4981E18C.5040509@opencsw.org> Message-ID: <20090129185030.GA42131@bolthole.com> On Thu, Jan 29, 2009 at 06:04:12PM +0100, Sebastian Kayser wrote: > According to http://opencsw.org/standards/layout: > > /opt/csw/share/www "pure php" and other arch-neutral web packages should > deploy to here, for similar reasons to the java location. (One reason > being that we dont want to limit the users' choice of web server if we > dont have to). If there is a particular reason why the app doesnt belong > under "share", though "a particular reason" being, "if the app writes to its directories", since /opt/csw/share should be read-only. From harpchad at opencsw.org Thu Jan 29 23:22:08 2009 From: harpchad at opencsw.org (Chad Harp) Date: Thu, 29 Jan 2009 16:22:08 -0600 Subject: [csw-maintainers] vim/gvim 7.2.93 available in testing Message-ID: <49822C10.3090009@opencsw.org> Changes: - Update to patch level 093 - vim now has 64-bit binaries (gvim won't until gtk2 does) From dam at opencsw.org Fri Jan 30 17:04:55 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:04:55 +0100 Subject: [csw-maintainers] General package update on the buildfarm Message-ID: Hi, there has been a request for package installation where I must update all dependencies. Please be patient while I run a full upgrade of CSW packages on all build servers. Thanks! -- Dago From phil at bolthole.com Fri Jan 30 17:19:18 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 08:19:18 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: <4980CDD4.5080106@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> Message-ID: <20090130161918.GB72531@bolthole.com> On Wed, Jan 28, 2009 at 10:27:48PM +0100, William Bonnet wrote: > Hi, > > Still talking about the beanutils package... but different subject. > > Beautils package is Apache Jakarta Commons Beanutils. A java lib. I have > several libs to add to gar, and i was planning to add them to GAR under > the java folder (just like there is xfce, x11 and cpan folders). A few > weeks ago, Dago, you told me you were planning to put jdk packages under > *java* , but i noticed they are the root of pkg. Do you still plan to do > it or can i use it ? I you use it, is it a problem if i call my folder > *javalibs* instead ? I think it's best to use full path names when you're talking about this stuff From dam at opencsw.org Fri Jan 30 17:27:34 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:27:34 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <20090130161918.GB72531@bolthole.com> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> Message-ID: Hi, Am 30.01.2009 um 17:19 schrieb Philip Brown: > On Wed, Jan 28, 2009 at 10:27:48PM +0100, William Bonnet wrote: >> Still talking about the beanutils package... but different subject. >> >> Beautils package is Apache Jakarta Commons Beanutils. A java lib. I >> have >> several libs to add to gar, and i was planning to add them to GAR >> under >> the java folder (just like there is xfce, x11 and cpan folders). A >> few >> weeks ago, Dago, you told me you were planning to put jdk packages >> under >> *java* , but i noticed they are the root of pkg. Do you still plan >> to do >> it or can i use it ? I you use it, is it a problem if i call my >> folder >> *javalibs* instead ? > > I think it's best to use full path names when you're talking about > this > stuff The directory layout of the Java stuff is now exactly as we have discussed: /opt/csw/java jdk/ jdk1.6.0_52/ (CSWjdk6) jdk6 -> jdk1.6.0_52 (CSWjdk6) latest -> jdk6 (CSWjdk) jre/ jre1.6.0_52 -> jdk1.6.0_52/jre/ (CSWjre6) jre6 -> jre1.6.0_52 (CSWjre6) latest -> jre6 (CSWjre) javalibs/ (New one??) The packages have been installed on build8s and build8x for inspection. Best regards -- Dago From dam at opencsw.org Fri Jan 30 17:28:54 2009 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 30 Jan 2009 17:28:54 +0100 Subject: [csw-maintainers] General package update on the buildfarm In-Reply-To: References: Message-ID: <6C85BFA5-B667-45CE-950D-E538280AAF5E@opencsw.org> Hi, Am 30.01.2009 um 17:04 schrieb Dagobert Michelsen: > there has been a request for package installation where I must update > all dependencies. Please be patient while I run a full upgrade of > CSW packages on all build servers. All packages have been upgraded. Sorry for the inconvenience. -- Dago From phil at bolthole.com Fri Jan 30 17:41:48 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 08:41:48 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> Message-ID: <20090130164148.GC72531@bolthole.com> On Fri, Jan 30, 2009 at 05:27:34PM +0100, Dagobert Michelsen wrote: > Hi, > ... > The directory layout of the Java stuff is now exactly as we have > discussed: > > /opt/csw/java > .... > javalibs/ (New one??) > I dont remember discussing /opt/csw/java/javalibs before. what should its statement of purpose be? and why would it be different form the preexisting /opt/csw/share/java/ ? (whose current purpose is primarily for .jar files, but given the name, could be most other "java related libraries" also ?) From harpchad at opencsw.org Fri Jan 30 20:05:10 2009 From: harpchad at opencsw.org (Chad Harp) Date: Fri, 30 Jan 2009 13:05:10 -0600 Subject: [csw-maintainers] pidgin 2.5.4 in testing Message-ID: <49834F66.6000901@opencsw.org> Changes: update from 2.5.3 -> 2.5.4 From bonivart at opencsw.org Sat Jan 31 03:38:32 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 03:38:32 +0100 Subject: [csw-maintainers] Package page broken Message-ID: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> I reported about the file display being wrong for phpMyAdmin the other day. I remember reporting the same thing to Blastwave sometime before the split and it was fixed but we still have the broken code that doesn't use the BASEDIR setting. I also noted that my new package, botnet, can't be displayed at all. According to the page there is no such package. A third problem is that bzip2 doesn't show isaexec as a dependency on the main site but in the catalog it's there. All three of these problems do not exist with James Lee's more informative package page: http://www.canoedissent.org.uk/packages/ Overall the web site is pretty shaky with broken stuff that has been broken for a long time and new stuff being "out of sync" like above. I hope the new web site will use more stable tools for us, like James page which has always worked fine for me. -- /peter From phil at bolthole.com Sat Jan 31 04:25:05 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:25:05 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131032505.GF2538@bolthole.com> On Sat, Jan 31, 2009 at 03:38:32AM +0100, Peter Bonivart wrote: > ... > All three of these problems do not exist with James Lee's more > informative package page: http://www.canoedissent.org.uk/packages/ > > Overall the web site is pretty shaky with broken stuff that has been > broken for a long time and new stuff being "out of sync" like above. I > hope the new web site will use more stable tools for us, like James > page which has always worked fine for me. james page has always worked for what you use it for, i understand that. but does james's page, have ALL the features of the existing page? I'm not aware that it does. for example, you cannot search for shared libs nor does it link to the mantis section, for an individual package. I am not averse to replacing the existing page. I'd just like to make sure that it is an UPgrade, rather than a sidegrade. Features should be added, not traded one for another. From phil at bolthole.com Sat Jan 31 04:37:18 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:37:18 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131033718.GG2538@bolthole.com> btw; the reason that sometimes there is a lag for "new" packages to be displayed as packages, is two fold: 1. a package doesnt display as "officially" a package on www.opencsw.org/packages until it has an official mantis section for it. 2. there is a separate "checkmantis" script, that i run from time to time, to do this. The reason #2 is separate, is because creating the mantis space is kinda messy to back out from, so it's nice to avoid adding something by mistake, or in error. SO, at the moment, we're erroring on the side of not updating frequently enough, as opposed to updating mantis all the time. james' stuff doesnt try to integrate/update anything else, so it's a little simpler on his end. From phil at bolthole.com Sat Jan 31 04:40:21 2009 From: phil at bolthole.com (Philip Brown) Date: Fri, 30 Jan 2009 19:40:21 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> Message-ID: <20090131034021.GH2538@bolthole.com> btw: thank you for reminding me about the package search page, not having proper paths, when basedir != "/opt/csw". i have now fixed that bug, and reregistered phpmyadmin. please let me know if there are other packages that need similar reregistering. From bonivart at opencsw.org Sat Jan 31 10:59:43 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 10:59:43 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> On Sat, Jan 31, 2009 at 4:25 AM, Philip Brown wrote: > but does james's page, have ALL the features of the existing page? > I'm not aware that it does. > > for example, you cannot search for shared libs > nor does it link to the mantis section, for an individual package. > > I am not averse to replacing the existing page. I'd just like to make sure > that it is an UPgrade, rather than a sidegrade. Features should be added, > not traded one for another. History tells me that your reasoning here means that things will remain the way they are so I won't waste my time arguing with you. But I would like to show another useful thing James page has, it shows symlinks properly. Look at the difference for a package like gnulinks: http://www.opencsw.org/search/gnulinks http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/files/ I also want to remind you that bzip2 still lacks the isaexec dependency. -- /peter From phil at bolthole.com Sat Jan 31 13:27:02 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:27:02 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> Message-ID: <20090131122702.GA12692@bolthole.com> On Sat, Jan 31, 2009 at 10:59:43AM +0100, Peter Bonivart wrote: > But I would like to show another useful thing James page has, it shows > symlinks properly. Look at the difference for a package like gnulinks: > > http://www.opencsw.org/search/gnulinks > http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/files/ That was actually a deliberate design decision on my part. Unfortunately, given that it was 6 years ago, i dont remember off the top of my head WHY i made that decision at the time :-/ I'll try to ponder on that . > I also want to remind you that bzip2 still lacks the isaexec dependency. not the fault of the registration script. bzip2 doesnt actually have a declared dependancy on isaexec. bender$ cat /tmp/CSWbzip2/install/depend P CSWcommon common - common files and dirs for CSW packages From james at opencsw.org Sat Jan 31 13:36:02 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:36:02 GMT Subject: [csw-maintainers] .la discussion In-Reply-To: <4980876A.8070806@opencsw.org> References: <4980876A.8070806@opencsw.org> Message-ID: <20090131.12360200.3638938294@gyor.oxdrove.co.uk> On 28/01/09, 16:27:22, Chad Harp wrote regarding [csw-maintainers] .la discussion: > I've got some .la files that are causing issues. I've seen some > requests to have them deleted (on a single file basis) from the build > farm, is that how we should handle them for now? I was criticised the the last time I offered my workaround but here goes again because it actually works. It is not so much the la files that are a problem but libtool's use of them. My strategy is one of living with libtool rather than avoiding or fighting it. Write a shell script (or whatever you like) and name it cc and/or CC. Place it on the path in front of real compiler. Make the script dismantle the compiler args, reassemble in a sane order, exclude and add anything you want and call the real compiler with your own new arg list. James. From bonivart at opencsw.org Sat Jan 31 13:38:42 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 13:38:42 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131122702.GA12692@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> Message-ID: <625385e30901310438l1e52bf5ay331468ae7bdadd85@mail.gmail.com> On Sat, Jan 31, 2009 at 1:27 PM, Philip Brown wrote: >> I also want to remind you that bzip2 still lacks the isaexec dependency. > > not the fault of the registration script. bzip2 doesnt actually have a > declared dependancy on isaexec. > > bender$ cat /tmp/CSWbzip2/install/depend > P CSWcommon common - common files and dirs for CSW packages Then we have broken catalogs which are much worse. http://ftp.math.purdue.edu/mirrors/opencsw.org/current/i386/5.10/catalog bzip2 1.0.5,REV=2009.01.17 CSWbzip2 bzip2-1.0.5,REV=2009.01.17-SunOS5.8-i386-CSW.pkg.gz bfd482c82ec78e5d4ae974679e890ddd 404667 CSWcommon|CSWisaexec none Sparc looks ok. -- /peter From james at opencsw.org Sat Jan 31 13:39:57 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:39:57 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> Message-ID: <20090131.12395700.2202691244@gyor.oxdrove.co.uk> On 31/01/09, 09:59:43, Peter Bonivart wrote regarding Re: [csw-maintainers] Package page broken: > But I would like to show another useful thing James page has, it shows > symlinks properly. Look at the difference for a package like gnulinks: > http://www.opencsw.org/search/gnulinks > http://www.canoedissent.org.uk/packages/unstable/i386/5.8/CSWgnulinks/fi les/ I not sure mine is right, if one runs "ls" on a sym link it just shows the file name, so perhaps this simple file list should show only the file names. An "ls -l" style long output too would be useful showing the size, date, owners and perms of all files, then we could add checksum... no, I wanted to keep it simple. From james at opencsw.org Sat Jan 31 13:39:58 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:39:58 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <20090131.12395800.4260684360@gyor.oxdrove.co.uk> On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > but does james's page, have ALL the features of the existing page? > I'm not aware that it does. > for example, you cannot search for shared libs True. I only read the top part of the package file to extract the info parts (as a stream from a remote URL). This mean only a small amount needs to be downloaded. To read the ELF headers and extract the shared lib usage the whole package has to be read and I chose not to. > nor does it link to the mantis section, for an individual package. It don't know the mapping from package name to mantis number, (no access to the mantis data). Mantis would be better if it used package name itself not an arbitrary id number. Of course if someone could set up a forwarder... From james at opencsw.org Sat Jan 31 13:40:39 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:40:39 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131032505.GF2538@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> Message-ID: <20090131.12403900.475170348@gyor.oxdrove.co.uk> On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > I am not averse to replacing the existing page. I'd just like to make > sure that it is an UPgrade, rather than a sidegrade. Features should > be added, not traded one for another. Ahh.. so this is how software turns into bloatware. From james at opencsw.org Sat Jan 31 13:41:50 2009 From: james at opencsw.org (James Lee) Date: Sat, 31 Jan 2009 12:41:50 GMT Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131122702.GA12692@bolthole.com> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> Message-ID: <20090131.12415000.3743127150@gyor.oxdrove.co.uk> On 31/01/09, 12:27:02, Philip Brown wrote regarding Re: [csw-maintainers] Package page broken: > > I also want to remind you that bzip2 still lacks the isaexec dependency. > not the fault of the registration script. bzip2 doesnt actually have a > declared dependancy on isaexec. Compare: http://www.canoedissent.org.uk/packages/unstable/i386/5.10/CSWbzip2/ http://www.canoedissent.org.uk/packages/unstable/sparc/5.10/CSWbzip2/ The problem is Phil's single listing. James. From bonivart at opencsw.org Sat Jan 31 13:48:12 2009 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 31 Jan 2009 13:48:12 +0100 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12415000.3743127150@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <625385e30901310159n47bad754o29d9941bf4583b7b@mail.gmail.com> <20090131122702.GA12692@bolthole.com> <20090131.12415000.3743127150@gyor.oxdrove.co.uk> Message-ID: <625385e30901310448p28c61b8alddef73bdaf5b53af@mail.gmail.com> On Sat, Jan 31, 2009 at 1:41 PM, James Lee wrote: > On 31/01/09, 12:27:02, Philip Brown wrote regarding Re: > [csw-maintainers] Package page broken: > >> > I also want to remind you that bzip2 still lacks the isaexec dependency. > >> not the fault of the registration script. bzip2 doesnt actually have a >> declared dependancy on isaexec. > > Compare: > http://www.canoedissent.org.uk/packages/unstable/i386/5.10/CSWbzip2/ > http://www.canoedissent.org.uk/packages/unstable/sparc/5.10/CSWbzip2/ > > > The problem is Phil's single listing. Ah...that explains it. Thank you James. -- /peter From phil at bolthole.com Sat Jan 31 13:49:31 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:49:31 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12403900.475170348@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <20090131.12403900.475170348@gyor.oxdrove.co.uk> Message-ID: <20090131124931.GB12692@bolthole.com> On Sat, Jan 31, 2009 at 12:40:39PM +0000, James Lee wrote: > On 31/01/09, 03:25:05, Philip Brown wrote regarding Re: > [csw-maintainers] Package page broken: > > > I am not averse to replacing the existing page. I'd just like to make > > sure that it is an UPgrade, rather than a sidegrade. Features should > > be added, not traded one for another. > > Ahh.. so this is how software turns into bloatware. haha :-) well, I dont think something should be considered "bloat", if it is a feature that is both useful, and relevant. From phil at bolthole.com Sat Jan 31 13:56:05 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 04:56:05 -0800 Subject: [csw-maintainers] Package page broken In-Reply-To: <20090131.12395800.4260684360@gyor.oxdrove.co.uk> References: <625385e30901301838n2b780cc0lec8baec416630e90@mail.gmail.com> <20090131032505.GF2538@bolthole.com> <20090131.12395800.4260684360@gyor.oxdrove.co.uk> Message-ID: <20090131125605.GC12692@bolthole.com> On Sat, Jan 31, 2009 at 12:39:58PM +0000, James Lee wrote: > > nor does it link to the mantis section, for an individual package. > > It don't know the mapping from package name to mantis number, (no access > to the mantis data). Mantis would be better if it used package name > itself not an arbitrary id number. Of course if someone could set up a > forwarder... thats an idea... it would be nice if some motivated person could code up an add-on, that we could drop into the mantis area, that would maybe look something like [http://....mantis/]showproject.php/softwarenamehere This could potentially benefit both us, and mantis itself. It could be contributed to "upstream", if written nicely. From william at wbonnet.net Sat Jan 31 18:43:36 2009 From: william at wbonnet.net (William Bonnet) Date: Sat, 31 Jan 2009 18:43:36 +0100 Subject: [csw-maintainers] Use of java folder In-Reply-To: <20090130164148.GC72531@bolthole.com> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> <20090130164148.GC72531@bolthole.com> Message-ID: <49848DC8.8070705@wbonnet.net> Hi guys > I dont remember discussing /opt/csw/java/javalibs before. what should its > statement of purpose be? > It has never been discussed > and why would it be different form the preexisting > /opt/csw/share/java/ ? > I don't think it has to be In fat the problem is that my original email was /not clear/. I was talking about adding files to GAR, so it was about the java (or javalibs) directory in svn not under /opt/csw :) cheers W. -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From phil at bolthole.com Sat Jan 31 21:06:29 2009 From: phil at bolthole.com (Philip Brown) Date: Sat, 31 Jan 2009 12:06:29 -0800 Subject: [csw-maintainers] Use of java folder In-Reply-To: <49848DC8.8070705@wbonnet.net> References: <4980CDD4.5080106@wbonnet.net> <20090130161918.GB72531@bolthole.com> <20090130164148.GC72531@bolthole.com> <49848DC8.8070705@wbonnet.net> Message-ID: <20090131200629.GD12692@bolthole.com> On Sat, Jan 31, 2009 at 06:43:36PM +0100, William Bonnet wrote: > ... > In fat the problem is that my original email was /not clear/. I was > talking about adding files to GAR, so it was about the java (or > javalibs) directory in svn not under /opt/csw :) ahaha.. good to know now :-)