From buildfarm at lists.opencsw.org Sun May 3 21:07:50 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 3 May 2015 21:07:50 +0200 Subject: Buildfarm offer for Solaris Message-ID: <6464A95D-9A5F-4025-BFC3-909F9DD569F8@baltic-online.de> Hi, we run the buildfarm for OpenCSW and would like to offer access for continous integration as asked for at http://wiki.squid-cache.org/BuildFarm The buildfarm consists of Solaris 9, 10 and 11 for both Sparc and i386 with different compilers installed (GCC 4, Sun Studio 12 to Oracle Studio 12.4). The Sparc machines and Solaris 10/11 i386 are both 32 and 64 bit as usual on Solaris. The i386 machines are virtual machines on VMware, Solaris 9 Sparc is a branded zone on a T5220 Sparc, Solaris 10 is a zone on the same machine. Solaris 11 is run on a zone on a M3000. The buildfarm has a single public IP (login.opencsw.org) and several build machines on a private network (192.168.*.*) which can access the internet over proxy. Is this a viable setup for your requirements? Best regards ? Dago -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 6 10:35:32 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Wed, 06 May 2015 10:35:32 +0200 Subject: fix / reboot proxy machine ? Message-ID: <5549D254.4080806@opencsw.org> Hi, during package I get, I think a machine needs some "massaging" Transferring package instance mkp: exec( gzip -9 -f /tmp/libpng16_dev-1.6.16,REV=2015.05.06-SunOS5.10-i386-UNCOMMITTED.pkg ) mkp: exec( mv /tmp/libpng16_dev-1.6.16,REV=2015.05.06-SunOS5.10-i386-UNCOMMITTED.pkg.gz /home/rmottola/pkgs ) mkp: exec( rm -rf /home/rmottola/spool.5.10-i386/CSWlibpng16-dev ) INFO 2015-05-06 10:20:15,594 package_stats.py:132 Juicing the svr4 package stream files... CRITICAL 2015-05-06 10:21:09,985 shell.py:55 | CRITICAL 2015-05-06 10:21:09,986 shell.py:56 INFO 2015-05-06 10:20:19,817 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') INFO 2015-05-06 10:20:29,827 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') INFO 2015-05-06 10:20:39,837 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') INFO 2015-05-06 10:20:49,847 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') INFO 2015-05-06 10:20:59,857 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') Traceback (most recent call last): Riccardo From buildfarm at lists.opencsw.org Wed May 6 10:47:55 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 6 May 2015 10:47:55 +0200 Subject: fix / reboot proxy machine ? In-Reply-To: <5549D254.4080806@opencsw.org> References: <5549D254.4080806@opencsw.org> Message-ID: Hi Riccardo, > Am 06.05.2015 um 10:35 schrieb Riccardo Mottola via buildfarm : > > Hi, > > during package I get, I think a machine needs some "massaging" > > Transferring package instance > mkp: exec( gzip -9 -f /tmp/libpng16_dev-1.6.16,REV=2015.05.06-SunOS5.10-i386-UNCOMMITTED.pkg ) > mkp: exec( mv /tmp/libpng16_dev-1.6.16,REV=2015.05.06-SunOS5.10-i386-UNCOMMITTED.pkg.gz /home/rmottola/pkgs ) > mkp: exec( rm -rf /home/rmottola/spool.5.10-i386/CSWlibpng16-dev ) > INFO 2015-05-06 10:20:15,594 package_stats.py:132 Juicing the svr4 package stream files... > CRITICAL 2015-05-06 10:21:09,985 shell.py:55 | > CRITICAL 2015-05-06 10:21:09,986 shell.py:56 INFO 2015-05-06 10:20:19,817 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') > INFO 2015-05-06 10:20:29,827 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') > INFO 2015-05-06 10:20:39,837 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') > INFO 2015-05-06 10:20:49,847 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') > INFO 2015-05-06 10:20:59,857 retry_decorator.py:35 Retry, exception: (7, 'Failed to connect to proxy port 3128: Connection refused') > Traceback (most recent call last): I cleared the fault and it should work again. Last time I updated to Squid 3.5.3 which is pretty recent, unfortunately looking at the stacktrace leads to the assumption that this issue has not been fixed yet: https://www.opencsw.org/mantis/view.php?id=5163 http://bugs.squid-cache.org/show_bug.cgi?id=4004 Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 6 11:21:00 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Wed, 06 May 2015 11:21:00 +0200 Subject: fix / reboot proxy machine ? In-Reply-To: References: <5549D254.4080806@opencsw.org> Message-ID: <5549DCFC.4040605@opencsw.org> Hi, Dagobert Michelsen wrote: > I cleared the fault and it should work again. Last time I updated to Squid 3.5.3 > which is pretty recent, unfortunately looking at the stacktrace leads to the > assumption that this issue has not been fixed yet: > https://www.opencsw.org/mantis/view.php?id=5163 > http://bugs.squid-cache.org/show_bug.cgi?id=4004 thanks for the quick response. I have another problem though now, I can't run svn update or even ping: rmottola at unstable10x [global]:~/opencsw/libpng/trunk > svn update Updating '.': svn: E000146: Unable to connect to a repository at URL 'https://svn.code.sf.net/p/gar/code/csw/mgar/pkg/libpng' svn: E000146: Error running context: Connection refused rmottola at unstable10x [global]:~/opencsw/libpng/trunk > ping svn.code.sf.net ICMP Host Unreachable from gateway unstable10x (192.168.1.33) for icmp from unstable10x (192.168.1.33) to svn.code.sf.net (216.34.181.157) ICMP Host Unreachable from gateway unstable10x (192.168.1.33) for icmp from unstable10x (192.168.1.33) to svn.code.sf.net (216.34.181.157) I can reach the host from my network, so it must be something on the buildfarm network. Riccardo From buildfarm at lists.opencsw.org Wed May 6 11:23:13 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 6 May 2015 11:23:13 +0200 Subject: fix / reboot proxy machine ? In-Reply-To: <5549DCFC.4040605@opencsw.org> References: <5549D254.4080806@opencsw.org> <5549DCFC.4040605@opencsw.org> Message-ID: Hi Riccardo, > Am 06.05.2015 um 11:21 schrieb Riccardo Mottola : > > Hi, > > Dagobert Michelsen wrote: >> I cleared the fault and it should work again. Last time I updated to Squid 3.5.3 >> which is pretty recent, unfortunately looking at the stacktrace leads to the >> assumption that this issue has not been fixed yet: >> https://www.opencsw.org/mantis/view.php?id=5163 >> http://bugs.squid-cache.org/show_bug.cgi?id=4004 > > thanks for the quick response. > > I have another problem though now, I can't run svn update or even ping: > > rmottola at unstable10x [global]:~/opencsw/libpng/trunk > svn update > Updating '.': > svn: E000146: Unable to connect to a repository at URL 'https://svn.code.sf.net/p/gar/code/csw/mgar/pkg/libpng' > svn: E000146: Error running context: Connection refused This is a sourceforge issue. > rmottola at unstable10x [global]:~/opencsw/libpng/trunk > ping svn.code.sf.net > ICMP Host Unreachable from gateway unstable10x (192.168.1.33) > for icmp from unstable10x (192.168.1.33) to svn.code.sf.net (216.34.181.157) > ICMP Host Unreachable from gateway unstable10x (192.168.1.33) > for icmp from unstable10x (192.168.1.33) to svn.code.sf.net (216.34.181.157) > > I can reach the host from my network, so it must be something on the buildfarm network. There is no NAT from inside the farm, you can reach official IPs only from ?login? or ?web? via proxy or nc. To verify you can test from ?login?. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 6 11:45:59 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Wed, 06 May 2015 11:45:59 +0200 Subject: fix / reboot proxy machine ? In-Reply-To: References: <5549D254.4080806@opencsw.org> <5549DCFC.4040605@opencsw.org> Message-ID: <5549E2D7.4020604@opencsw.org> Hi, Dagobert Michelsen wrote: > > This is a sourceforge issue. I don't think so. From "login" can run: rmottola at login [login]:~/opencsw/libpng/trunk > mgar update Updating current package directory + build system Updating '.': U checksums U Makefile Updated to revision 24940. from unstable10x: rmottola at unstable10x [global]:~/opencsw/libpng/trunk > mgar update Updating current package directory + build system Updating '.': svn: E000146: Unable to connect to a repository at URL 'https://svn.code.sf.net/p/gar/code/csw/mgar/pkg/libpng' svn: E000146: Error running context: Connection refused > There is no NAT from inside the farm, you can reach official IPs only from ?login? or ?web? > via proxy or nc. To verify you can test from ?login?. > Sorry, didn't know that. Riccardo From buildfarm at lists.opencsw.org Wed May 6 12:00:23 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 6 May 2015 12:00:23 +0200 Subject: fix / reboot proxy machine ? In-Reply-To: <5549E2D7.4020604@opencsw.org> References: <5549D254.4080806@opencsw.org> <5549DCFC.4040605@opencsw.org> <5549E2D7.4020604@opencsw.org> Message-ID: <95AEDD92-810B-4903-9D5C-F44861C3FFD9@opencsw.org> Hi Riccardo, > Am 06.05.2015 um 11:45 schrieb Riccardo Mottola : > > Hi, > > Dagobert Michelsen wrote: >> >> This is a sourceforge issue. > > I don't think so. From "login" can run: Danm, crashed again. I need to get this Squid issue fixed. Best reagrds ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 6 15:16:38 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Wed, 06 May 2015 15:16:38 +0200 Subject: CSWpy-requests: MISSING Message-ID: <554A1436.1050604@opencsw.org> Hi, building libpng I ow get this package missing (unstable10x): ==> Verifying installed package CSWpy-requests: MISSING it must be an implied dependenency that was not needed until recently... or well was satisfied without knowing it. What pulls it in Can you make sure it is available on 10x/10s and 9x/9s ? Thank you very much Riccardo From buildfarm at lists.opencsw.org Wed May 6 15:23:12 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 6 May 2015 15:23:12 +0200 Subject: CSWpy-requests: MISSING In-Reply-To: <554A1436.1050604@opencsw.org> References: <554A1436.1050604@opencsw.org> Message-ID: <02951BA0-ED67-4873-A130-82EC6B6F3B92@opencsw.org> Hi Riccardo, > Am 06.05.2015 um 15:16 schrieb Riccardo Mottola via buildfarm : > > Hi, > > building libpng I ow get this package missing (unstable10x): > > ==> Verifying installed package CSWpy-requests: MISSING > it must be an implied dependenency that was not needed until recently... or well was satisfied without knowing it. What pulls it in > > Can you make sure it is available on 10x/10s and 9x/9s ? It is, are you running it from ?login?? Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 7 10:05:06 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Thu, 07 May 2015 10:05:06 +0200 Subject: libcrypto problems on sol9 Message-ID: <554B1CB2.4030909@opencsw.org> Hi, when doing "make platforms" I get a failure on solaris 9 sparc: ===== NOW BUILDING: libpng-1.5.13 MODULATION isa-sparcv8: ISA=sparcv8 =====] ==> Extracting work/solaris9-sparc/download/libpng-1.5.13.tar.gz ==> Snapshotting extracted source tree with git ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory Killed ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory Killed ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory Killed ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory Killed ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory Killed Riccardo From buildfarm at lists.opencsw.org Thu May 7 10:25:42 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 7 May 2015 10:25:42 +0200 Subject: libcrypto problems on sol9 In-Reply-To: <554B1CB2.4030909@opencsw.org> References: <554B1CB2.4030909@opencsw.org> Message-ID: <140BD598-EE3F-4D69-B38D-2F7D5B007C93@opencsw.org> Hi Riccardo, > Am 07.05.2015 um 10:05 schrieb Riccardo Mottola via buildfarm : > > Hi, > > when doing "make platforms" I get a failure on solaris 9 sparc: > > ===== NOW BUILDING: libpng-1.5.13 MODULATION isa-sparcv8: ISA=sparcv8 =====] > ==> Extracting work/solaris9-sparc/download/libpng-1.5.13.tar.gz > ==> Snapshotting extracted source tree with git > ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory > Killed > ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory > Killed > ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory > Killed > ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory > Killed > ld.so.1: git: fatal: libcrypto.so.1.0.0: open failed: No such file or directory > Killed This is fixed again. I was trying the get some progress on the Solaris 9 OpenSSL issue. No solution so far :-( I reinstalled the old version 1.0.1l. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Fri May 8 00:25:37 2015 From: buildfarm at lists.opencsw.org (maquinasparacafe.com.br via buildfarm) Date: Thu, 7 May 2015 19:25:37 -0300 Subject: =?iso-8859-1?Q?CAF=C9_EXPRESSO=5FChocolate=5FCappuccino=5FCh=E1=5FAutoser?= =?iso-8859-1?Q?vi=E7o?= Message-ID: <0e75f8be398c6dd235fa7d3e25d268e0@localhost.localdomain> Para visualizar esta mensagem, use um programa de e-mail compativel com html! -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Fri May 8 09:46:08 2015 From: buildfarm at lists.opencsw.org (Jan Holzhueter via buildfarm) Date: Fri, 08 May 2015 09:46:08 +0200 Subject: Downtime x86 Part of the Buildfarm Message-ID: <554C69C0.3030704@opencsw.org> Hi, I plan to update our ESX infrastructure this afternoon. So the x86 part needs to be shut down. Will keep you posted. Greetings Jan From buildfarm at lists.opencsw.org Fri May 8 21:58:09 2015 From: buildfarm at lists.opencsw.org (Jan Holzhueter via buildfarm) Date: Fri, 08 May 2015 21:58:09 +0200 Subject: Downtime x86 Part of the Buildfarm In-Reply-To: <554C69C0.3030704@opencsw.org> References: <554C69C0.3030704@opencsw.org> Message-ID: <554D1551.2010300@opencsw.org> Am 08.05.15 um 09:46 schrieb Jan Holzhueter: > Hi, > I plan to update our ESX infrastructure this afternoon. > So the x86 part needs to be shut down. > Will keep you posted. took longer then I thought. But should all be back now. If something does not work let me know. Greetings Jan From buildfarm at lists.opencsw.org Wed May 13 13:09:12 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 13 May 2015 13:09:12 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> Message-ID: <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> Hi Francesco, > Am 06.05.2015 um 15:35 schrieb Francesco Chemolli : > > Hi, > I can confirm I logged in to the system. > What are the build hosts after I do that? How are you coming along? Anything I can help you with? Best regards ? Dago > > On Wed, May 6, 2015 at 3:33 PM, Dagobert Michelsen wrote: >> >>> Am 06.05.2015 um 15:32 schrieb Dagobert Michelsen : >>> >>> Hi Francesco, >>> >>>> Am 06.05.2015 um 15:26 schrieb Francesco Chemolli : >>>> >>>> I'm not entirely sure about the double ssh hop, but I'll try to make >>>> it work; it's worth a try at least :) >>>> >>>> I'm attaching the key (or line wrapping will make a mess). >>> >>> Please give it a try to >>> login.opencsw.org >> >> The user is >> squidci at login.opencsw.org >> >>> >>> The relevant build flags for our OpenCSW-distribution are described at >>> https://www.opencsw.org/manual/for-developers/index.html >>> >>> The setup of the farm is described at /etc/SETUP on "login". If you need anything >>> or have any questions just let me know. >>> >>> >>> Best regards >>> >>> -- Dago >>> >>> -- >>> "You don't become great by trying to be great, you become great by wanting to do something, >>> and then doing it so hard that you become great in the process." - xkcd #896 >>> >> >> -- >> "You don't become great by trying to be great, you become great by wanting to do something, >> and then doing it so hard that you become great in the process." - xkcd #896 >> > > > > -- > Francesco Chemolli > Squid Software Foundation -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 13 16:47:26 2015 From: buildfarm at lists.opencsw.org (Francesco Chemolli via buildfarm) Date: Wed, 13 May 2015 16:47:26 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> Message-ID: Hi, I've done some testing but without full success so far. You can find my results here: http://build.squid-cache.org/job/trunk-opensolaris-matrix/ In short, I was able to nudge our Jenkins in connecting to the build nodes through the login server and to run a test build. There is a strange incompatibility in the berkeley db library: it relies on some types (u_int_{16,32,64}) which are not defined anywhere in the system headers (the standard is uint_{16,32,64}). Another small difficulty is that Solaris lacks vfork(2) in favor of posix_spawn (which is not present on any other mainstream OS that I know of). I had to install to the user's home directory some software; it'd be nice if it could become part of the standard software setup of the build nodes: that's bzr (http://bazaar.canonical.com/en/) and libcppunit. Do you think it could be arranged? Thanks! On Wed, May 13, 2015 at 1:09 PM, Dagobert Michelsen wrote: > Hi Francesco, > >> Am 06.05.2015 um 15:35 schrieb Francesco Chemolli : >> >> Hi, >> I can confirm I logged in to the system. >> What are the build hosts after I do that? > > How are you coming along? Anything I can help you with? > > > Best regards > > -- Dago > >> >> On Wed, May 6, 2015 at 3:33 PM, Dagobert Michelsen wrote: >>> >>>> Am 06.05.2015 um 15:32 schrieb Dagobert Michelsen : >>>> >>>> Hi Francesco, >>>> >>>>> Am 06.05.2015 um 15:26 schrieb Francesco Chemolli : >>>>> >>>>> I'm not entirely sure about the double ssh hop, but I'll try to make >>>>> it work; it's worth a try at least :) >>>>> >>>>> I'm attaching the key (or line wrapping will make a mess). >>>> >>>> Please give it a try to >>>> login.opencsw.org >>> >>> The user is >>> squidci at login.opencsw.org >>> >>>> >>>> The relevant build flags for our OpenCSW-distribution are described at >>>> https://www.opencsw.org/manual/for-developers/index.html >>>> >>>> The setup of the farm is described at /etc/SETUP on "login". If you need anything >>>> or have any questions just let me know. >>>> >>>> >>>> Best regards >>>> >>>> -- Dago >>>> >>>> -- >>>> "You don't become great by trying to be great, you become great by wanting to do something, >>>> and then doing it so hard that you become great in the process." - xkcd #896 >>>> >>> >>> -- >>> "You don't become great by trying to be great, you become great by wanting to do something, >>> and then doing it so hard that you become great in the process." - xkcd #896 >>> >> >> >> >> -- >> Francesco Chemolli >> Squid Software Foundation > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > -- Francesco Chemolli Squid Software Foundation From buildfarm at lists.opencsw.org Wed May 13 17:50:16 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 13 May 2015 17:50:16 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> Message-ID: Hi Francesco, > Am 13.05.2015 um 16:47 schrieb Francesco Chemolli : > > Hi, > I've done some testing but without full success so far. You can find > my results here: > > http://build.squid-cache.org/job/trunk-opensolaris-matrix/ > > In short, I was able to nudge our Jenkins in connecting to the build > nodes through the login server and to run a test build. > There is a strange incompatibility in the berkeley db library: it > relies on some types (u_int_{16,32,64}) which are not defined anywhere > in the system headers (the standard is uint_{16,32,64}). Which version are you talking about specifically? We have several versions under /opt/csw/bdb* and also an old 1.85 in addition to the system provided ones. > Another small > difficulty is that Solaris lacks vfork(2) in favor of posix_spawn > (which is not present on any other mainstream OS that I know of). > > I had to install to the user's home directory some software; it'd be > nice if it could become part of the standard software setup of the > build nodes: that's bzr (http://bazaar.canonical.com/en/) We already have a package for that. It is now available at /opt/csw/bin/bzr on all unstable* hosts. > and libcppunit. Do you think it could be arranged? We already had a package Makefile but never released it. I took care of that and it is now also installed in /opt/csw on all unstable* hosts. Please keep in mind that this is compiler-specific due to the name-mangling and that we only have the GCC version. Best regards ? Dago > > Thanks! > > On Wed, May 13, 2015 at 1:09 PM, Dagobert Michelsen wrote: >> Hi Francesco, >> >>> Am 06.05.2015 um 15:35 schrieb Francesco Chemolli : >>> >>> Hi, >>> I can confirm I logged in to the system. >>> What are the build hosts after I do that? >> >> How are you coming along? Anything I can help you with? >> >> >> Best regards >> >> -- Dago >> >>> >>> On Wed, May 6, 2015 at 3:33 PM, Dagobert Michelsen wrote: >>>> >>>>> Am 06.05.2015 um 15:32 schrieb Dagobert Michelsen : >>>>> >>>>> Hi Francesco, >>>>> >>>>>> Am 06.05.2015 um 15:26 schrieb Francesco Chemolli : >>>>>> >>>>>> I'm not entirely sure about the double ssh hop, but I'll try to make >>>>>> it work; it's worth a try at least :) >>>>>> >>>>>> I'm attaching the key (or line wrapping will make a mess). >>>>> >>>>> Please give it a try to >>>>> login.opencsw.org >>>> >>>> The user is >>>> squidci at login.opencsw.org >>>> >>>>> >>>>> The relevant build flags for our OpenCSW-distribution are described at >>>>> https://www.opencsw.org/manual/for-developers/index.html >>>>> >>>>> The setup of the farm is described at /etc/SETUP on "login". If you need anything >>>>> or have any questions just let me know. >>>>> >>>>> >>>>> Best regards >>>>> >>>>> -- Dago >>>>> >>>>> -- >>>>> "You don't become great by trying to be great, you become great by wanting to do something, >>>>> and then doing it so hard that you become great in the process." - xkcd #896 >>>>> >>>> >>>> -- >>>> "You don't become great by trying to be great, you become great by wanting to do something, >>>> and then doing it so hard that you become great in the process." - xkcd #896 >>>> >>> >>> >>> >>> -- >>> Francesco Chemolli >>> Squid Software Foundation >> >> -- >> "You don't become great by trying to be great, you become great by wanting to do something, >> and then doing it so hard that you become great in the process." - xkcd #896 >> > > > > -- > Francesco Chemolli > Squid Software Foundation -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 14 17:36:53 2015 From: buildfarm at lists.opencsw.org (Jake Goerzen via buildfarm) Date: Thu, 14 May 2015 08:36:53 -0700 Subject: proxy connection refused Message-ID: <5554C115.1000608@opencsw.org> Hi, Is there a problem with our buildfarm proxy? I cannot "mgar fetch" or "commit" anything outside of the buildfarm hosts. I get an error: ==> Trying http://www.torproject.org/dist/tor-0.2.7.1-alpha.tar.gz --2015-05-14 17:32:15-- http://www.torproject.org/dist/tor-0.2.7.1-alpha.tar.gz Resolving proxy (proxy)... 192.168.1.6 Connecting to proxy (proxy)|192.168.1.6|:3128... failed: Connection refused. Regards, Jake From buildfarm at lists.opencsw.org Thu May 14 18:09:02 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 14 May 2015 18:09:02 +0200 Subject: proxy connection refused In-Reply-To: <5554C115.1000608@opencsw.org> References: <5554C115.1000608@opencsw.org> Message-ID: Hi Jake, > Am 14.05.2015 um 17:36 schrieb Jake Goerzen via buildfarm : > > Hi, > > Is there a problem with our buildfarm proxy? I cannot "mgar fetch" or "commit" anything outside of the buildfarm hosts. I get an error: > > ==> Trying http://www.torproject.org/dist/tor-0.2.7.1-alpha.tar.gz > --2015-05-14 17:32:15-- http://www.torproject.org/dist/tor-0.2.7.1-alpha.tar.gz > Resolving proxy (proxy)... 192.168.1.6 > Connecting to proxy (proxy)|192.168.1.6|:3128... failed: Connection refused. Squid crashes once in a while, this is still the long-standing bug https://www.opencsw.org/mantis/view.php?id=5163 which neither upstream nor me was able to track down and fix. I restarted squid for now. Best regards - Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Mon May 18 09:17:17 2015 From: buildfarm at lists.opencsw.org (Carsten Grzemba via buildfarm) Date: Mon, 18 May 2015 09:17:17 +0200 Subject: Please install CSWnspr-dev In-Reply-To: References: Message-ID: Please install: ?CSWlibplc4 ?CSWlibplds4 ?CSWnspr-dev Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Mon May 18 17:17:20 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Mon, 18 May 2015 17:17:20 +0200 Subject: Please install CSWnspr-dev In-Reply-To: References: Message-ID: <3DABB1F9-B7F2-4E98-AAD9-85DE2D9E234E@opencsw.org> Hi Carsten, Am 18.05.2015 um 09:17 schrieb Carsten Grzemba via buildfarm: > Please install: > CSWlibplc4 > CSWlibplds4 > CSWnspr-dev Done. Best regards -- Dago From buildfarm at lists.opencsw.org Tue May 19 09:24:34 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 19 May 2015 09:24:34 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> Message-ID: <67028BCA-DDF0-412F-9202-5F708649026A@opencsw.org> Hi Francesco, > Am 13.05.2015 um 17:50 schrieb Dagobert Michelsen via buildfarm : >> Am 13.05.2015 um 16:47 schrieb Francesco Chemolli : >> >> Hi, >> I've done some testing but without full success so far. You can find >> my results here: >> >> http://build.squid-cache.org/job/trunk-opensolaris-matrix/ >> >> In short, I was able to nudge our Jenkins in connecting to the build >> nodes through the login server and to run a test build. >> There is a strange incompatibility in the berkeley db library: it >> relies on some types (u_int_{16,32,64}) which are not defined anywhere >> in the system headers (the standard is uint_{16,32,64}). > > Which version are you talking about specifically? We have several versions > under /opt/csw/bdb* and also an old 1.85 in addition to the system provided ones. > >> Another small >> difficulty is that Solaris lacks vfork(2) in favor of posix_spawn >> (which is not present on any other mainstream OS that I know of). >> >> I had to install to the user's home directory some software; it'd be >> nice if it could become part of the standard software setup of the >> build nodes: that's bzr (http://bazaar.canonical.com/en/) > > We already have a package for that. It is now available at > /opt/csw/bin/bzr > on all unstable* hosts. > >> and libcppunit. Do you think it could be arranged? > > We already had a package Makefile but never released it. I took care of that > and it is now also installed in /opt/csw on all unstable* hosts. Please keep > in mind that this is compiler-specific due to the name-mangling and that we > only have the GCC version. I hope the adjustments are working for you. Additionally I noticed that the Solaris builds are not yet showing up at http://build.squid-cache.org Is there anything I can be of additional help? Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue May 19 09:26:54 2015 From: buildfarm at lists.opencsw.org (Francesco Chemolli via buildfarm) Date: Tue, 19 May 2015 09:26:54 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: <67028BCA-DDF0-412F-9202-5F708649026A@opencsw.org> References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> <67028BCA-DDF0-412F-9202-5F708649026A@opencsw.org> Message-ID: Hi, I am currently traveling, I had to suspend work for a few days. Builds are starting to trickle in at http://build.squid-cache.org/job/trunk-opensolaris-matrix/ :) On Tue, May 19, 2015 at 9:24 AM, Dagobert Michelsen wrote: > Hi Francesco, > >> Am 13.05.2015 um 17:50 schrieb Dagobert Michelsen via buildfarm : >>> Am 13.05.2015 um 16:47 schrieb Francesco Chemolli : >>> >>> Hi, >>> I've done some testing but without full success so far. You can find >>> my results here: >>> >>> http://build.squid-cache.org/job/trunk-opensolaris-matrix/ >>> >>> In short, I was able to nudge our Jenkins in connecting to the build >>> nodes through the login server and to run a test build. >>> There is a strange incompatibility in the berkeley db library: it >>> relies on some types (u_int_{16,32,64}) which are not defined anywhere >>> in the system headers (the standard is uint_{16,32,64}). >> >> Which version are you talking about specifically? We have several versions >> under /opt/csw/bdb* and also an old 1.85 in addition to the system provided ones. >> >>> Another small >>> difficulty is that Solaris lacks vfork(2) in favor of posix_spawn >>> (which is not present on any other mainstream OS that I know of). >>> >>> I had to install to the user's home directory some software; it'd be >>> nice if it could become part of the standard software setup of the >>> build nodes: that's bzr (http://bazaar.canonical.com/en/) >> >> We already have a package for that. It is now available at >> /opt/csw/bin/bzr >> on all unstable* hosts. >> >>> and libcppunit. Do you think it could be arranged? >> >> We already had a package Makefile but never released it. I took care of that >> and it is now also installed in /opt/csw on all unstable* hosts. Please keep >> in mind that this is compiler-specific due to the name-mangling and that we >> only have the GCC version. > > I hope the adjustments are working for you. Additionally I noticed that the Solaris > builds are not yet showing up at > http://build.squid-cache.org > > Is there anything I can be of additional help? > > > Best regards > > -- Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > -- Francesco Chemolli Squid Software Foundation From buildfarm at lists.opencsw.org Tue May 19 10:13:52 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 19 May 2015 10:13:52 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> <67028BCA-DDF0-412F-9202-5F708649026A@opencsw.org> Message-ID: <8E5D9878-1F31-47AC-8014-01E761CFC9DE@opencsw.org> Hi Francesco, Am 19.05.2015 um 09:26 schrieb Francesco Chemolli : > I am currently traveling, I had to suspend work for a few days. Ah ok, NP. > Builds are starting to trickle in at > http://build.squid-cache.org/job/trunk-opensolaris-matrix/ :) I was confused because there was ?OpenSolaris? in the title and our buildfarm versions are only the ?closed? ones. Best regards ? Dago > > > > On Tue, May 19, 2015 at 9:24 AM, Dagobert Michelsen wrote: >> Hi Francesco, >> >>> Am 13.05.2015 um 17:50 schrieb Dagobert Michelsen via buildfarm : >>>> Am 13.05.2015 um 16:47 schrieb Francesco Chemolli : >>>> >>>> Hi, >>>> I've done some testing but without full success so far. You can find >>>> my results here: >>>> >>>> http://build.squid-cache.org/job/trunk-opensolaris-matrix/ >>>> >>>> In short, I was able to nudge our Jenkins in connecting to the build >>>> nodes through the login server and to run a test build. >>>> There is a strange incompatibility in the berkeley db library: it >>>> relies on some types (u_int_{16,32,64}) which are not defined anywhere >>>> in the system headers (the standard is uint_{16,32,64}). >>> >>> Which version are you talking about specifically? We have several versions >>> under /opt/csw/bdb* and also an old 1.85 in addition to the system provided ones. >>> >>>> Another small >>>> difficulty is that Solaris lacks vfork(2) in favor of posix_spawn >>>> (which is not present on any other mainstream OS that I know of). >>>> >>>> I had to install to the user's home directory some software; it'd be >>>> nice if it could become part of the standard software setup of the >>>> build nodes: that's bzr (http://bazaar.canonical.com/en/) >>> >>> We already have a package for that. It is now available at >>> /opt/csw/bin/bzr >>> on all unstable* hosts. >>> >>>> and libcppunit. Do you think it could be arranged? >>> >>> We already had a package Makefile but never released it. I took care of that >>> and it is now also installed in /opt/csw on all unstable* hosts. Please keep >>> in mind that this is compiler-specific due to the name-mangling and that we >>> only have the GCC version. >> >> I hope the adjustments are working for you. Additionally I noticed that the Solaris >> builds are not yet showing up at >> http://build.squid-cache.org >> >> Is there anything I can be of additional help? >> >> >> Best regards >> >> -- Dago >> >> -- >> "You don't become great by trying to be great, you become great by wanting to do something, >> and then doing it so hard that you become great in the process." - xkcd #896 >> > > > > -- > Francesco Chemolli > Squid Software Foundation -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue May 19 10:19:36 2015 From: buildfarm at lists.opencsw.org (Francesco Chemolli via buildfarm) Date: Tue, 19 May 2015 10:19:36 +0200 Subject: Buildfarm offer for Solaris In-Reply-To: <8E5D9878-1F31-47AC-8014-01E761CFC9DE@opencsw.org> References: <1FA42E1F-3CB3-4DE0-BB4F-3C1739F3C994@opencsw.org> <5EA6E08A-4E79-4C24-B206-629FBFED13BE@opencsw.org> <53CF900C-4277-42B3-883C-F822392DA8FB@opencsw.org> <67028BCA-DDF0-412F-9202-5F708649026A@opencsw.org> <8E5D9878-1F31-47AC-8014-01E761CFC9DE@opencsw.org> Message-ID: Oops, my mistake. Will renale asap On May 19, 2015 10:14 AM, "Dagobert Michelsen" wrote: > Hi Francesco, > > Am 19.05.2015 um 09:26 schrieb Francesco Chemolli >: > > I am currently traveling, I had to suspend work for a few days. > > Ah ok, NP. > > > Builds are starting to trickle in at > > http://build.squid-cache.org/job/trunk-opensolaris-matrix/ :) > > I was confused because there was "OpenSolaris" in the title and our > buildfarm versions are only the "closed" ones. > > > Best regards > > -- Dago > > > > > > > > > On Tue, May 19, 2015 at 9:24 AM, Dagobert Michelsen > wrote: > >> Hi Francesco, > >> > >>> Am 13.05.2015 um 17:50 schrieb Dagobert Michelsen via buildfarm < > buildfarm at lists.opencsw.org>: > >>>> Am 13.05.2015 um 16:47 schrieb Francesco Chemolli < > kinkie at squid-cache.org>: > >>>> > >>>> Hi, > >>>> I've done some testing but without full success so far. You can find > >>>> my results here: > >>>> > >>>> http://build.squid-cache.org/job/trunk-opensolaris-matrix/ > >>>> > >>>> In short, I was able to nudge our Jenkins in connecting to the build > >>>> nodes through the login server and to run a test build. > >>>> There is a strange incompatibility in the berkeley db library: it > >>>> relies on some types (u_int_{16,32,64}) which are not defined anywhere > >>>> in the system headers (the standard is uint_{16,32,64}). > >>> > >>> Which version are you talking about specifically? We have several > versions > >>> under /opt/csw/bdb* and also an old 1.85 in addition to the system > provided ones. > >>> > >>>> Another small > >>>> difficulty is that Solaris lacks vfork(2) in favor of posix_spawn > >>>> (which is not present on any other mainstream OS that I know of). > >>>> > >>>> I had to install to the user's home directory some software; it'd be > >>>> nice if it could become part of the standard software setup of the > >>>> build nodes: that's bzr (http://bazaar.canonical.com/en/) > >>> > >>> We already have a package for that. It is now available at > >>> /opt/csw/bin/bzr > >>> on all unstable* hosts. > >>> > >>>> and libcppunit. Do you think it could be arranged? > >>> > >>> We already had a package Makefile but never released it. I took care > of that > >>> and it is now also installed in /opt/csw on all unstable* hosts. > Please keep > >>> in mind that this is compiler-specific due to the name-mangling and > that we > >>> only have the GCC version. > >> > >> I hope the adjustments are working for you. Additionally I noticed that > the Solaris > >> builds are not yet showing up at > >> http://build.squid-cache.org > >> > >> Is there anything I can be of additional help? > >> > >> > >> Best regards > >> > >> -- Dago > >> > >> -- > >> "You don't become great by trying to be great, you become great by > wanting to do something, > >> and then doing it so hard that you become great in the process." - xkcd > #896 > >> > > > > > > > > -- > > Francesco Chemolli > > Squid Software Foundation > > -- > "You don't become great by trying to be great, you become great by wanting > to do something, > and then doing it so hard that you become great in the process." - xkcd > #896 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Tue May 19 22:58:48 2015 From: buildfarm at lists.opencsw.org (Bank.of.Ireland 365 MESSAGE CENTER via buildfarm) Date: 19 May 2015 23:58:48 +0300 Subject: ATTENTION: Important Information Regarding 365 Account Message-ID: <20150519235848.DBC7F7BD2A9A01B6@365security.com> An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Wed May 20 11:20:06 2015 From: buildfarm at lists.opencsw.org (Carsten Grzemba via buildfarm) Date: Wed, 20 May 2015 11:20:06 +0200 Subject: Please install NSS3 In-Reply-To: References: Message-ID: Please install/update: - libnss_dev (and dependend) - nss3_tools Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Wed May 20 11:39:09 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 11:39:09 +0200 Subject: Please install NSS3 In-Reply-To: References: Message-ID: Hi Carsten, > Am 20.05.2015 um 11:20 schrieb Carsten Grzemba via buildfarm : > > Please install/update: > - libnss_dev (and dependend) > - nss3_tools Done. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 14:09:38 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 14:09:38 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> Message-ID: Hi Steffen, Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : > I'm maintaining S-nail, an extended mailx(1)-like MUA. I came > along OpenCSW via an announcement from Ingo Schwarze and would be > very interested in gaining access to the Solaris operating system > for compile-testing (and "make test"ing) this program! (I'm also > in the process of forking GNU troff, and being able to check the > build system i will introduce on Solaris i would like very much, > too). > S-nail is part of ArchLinux core and is also (and already) > packaged by CRUX Linux, Void Linux, and OpenBSD. Maybe you are > interested ? i surely would appreciate this possibility! > It follows an excerpt of the README file. > Ciao! Sure, just send me your ssh public key and I?ll set you up. Best regards ? Dago > > S-nail is a mail processing system with a command syntax reminiscent of > ed(1) with lines replaced by messages. It is intended to provide the > functionality of the POSIX mailx(1) command and offers (mostly optional) > extensions for line editing, IDNA, MIME, S/MIME, SMTP and POP3. > It is usable as a mail batch language. > S-nail is a derivative of Heirloom mailx, formerly known as nail, which > itself is based upon Berkeley Mail that has a history back to the 70s. > > Please refer to the file INSTALL for build and installation remarks, > and to NEWS for release update information. The file THANKS mentions > people who have helped improving S-nail and deserve acknowledgement. > > S-nail has git(1) repositories at Sourceforge[1] (browsable[2]) and > GitLab.com[3] (browsable[4]), and regulary produces release tarballs[5], > which can also be addressed directly[6] (e.g., via `curl -v -L'). > There is also something visual on the web that includes the latest > version of the manual online[7]. > And we have a mailing list[8] with moderated unsubscribed posting > possibilities; subscriptions can be managed via webinterface[9]; > GMANE.org added s-nail-users@ to their archive[10] -- thank you! > > [1] git.code.sf.net/p/s-nail/code (HTTP / GIT) > [2] http://sourceforge.net/p/s-nail/code/ > [3] https://gitlab.com/s-nail/s-nail.git > [4] https://gitlab.com/s-nail/s-nail > [5] https://sourceforge.net/projects/s-nail/files/?source=navbar > [6] https://downloads.sourceforge.net/project/s-nail/s-nail-VERSION.tar.xz > [7] http://sdaoden.users.sourceforge.net/code.html#s-nail > [8] mailto:s-nail-users at lists.sourceforge.net > [9] https://lists.sourceforge.net/lists/listinfo/s-nail-users/ > [10] news://news.gmane.org/gmane.mail.s-nail.user > > > --steffen -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 15:31:36 2015 From: buildfarm at lists.opencsw.org (Steffen Nurpmeso via buildfarm) Date: Wed, 20 May 2015 15:31:36 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> Message-ID: <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> Hello! Dagobert Michelsen wrote: |Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : |> I'm maintaining S-nail, an extended mailx(1)-like MUA. I came |> along OpenCSW via an announcement from Ingo Schwarze and would be |> very interested in gaining access to the Solaris operating system |> for compile-testing (and "make test"ing) this program! (I'm also |Sure, just send me your ssh public key and I?ll set you up. Wow, great, thank you very much! I'll attach the key! And... where do i have to look when i need more info? |Best regards Fantastic! Ciao, --steffen -------------- next part -------------- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQC7HMqNRcYhLugZBJuaIq6XnWrPY3kUtJ44RBK7YmyeeUPr8m/d8HJZGhuY95LXhRM4MeVGr8ncvxjUqJGg651cbi8WhJtOanpwMljJqbFa+w3eTmmrsfthHqtAosk2TPizQeeJCZTum5AtqS063jopWbXFFEKT1UaOuXymhb+fJSmLoN9aZjx57eXIEeQxJ7g5/vdh/eC/fJhBiZ+/I4hmD02NGQBQly3WbAit6kwEUi8w3IDEP23sQQCEcqsRNPA82o+6yIAuGLNepP43R6kcwGGxUVPxjtL71Pu0jVnVaCD1vE5MYhFg1POhHE7b0O0Q+eG/oKkfpITjOCLGHT2FoSns19jzMG5ZUFM/kYlHlzuafo7dPHwg+ghWZdRUIgdfrImJjKXhY9Jy89ICxHJkqHcjakgPRuUr6yLUFewJU17gFOd7kjH+7J1zMZC/6/gMjgV9TXurQuItfNr8I7cHWJJujl/ndT9j66OZfaqOO2i5iKhLRmbVMgJ5AHH1MnqOoJ+k+O/Of8LxEJxjvczmUazEl+lPobVGaaS6zvr7xpuXRJMsp2oEYDYJnclZdGg0yAUocLGFetq9pO96esJnN2Ep6ke7Jr7owxRQHZCEpxLF/TWf4jbxiCDTnfjbV8Bs3Cg21u60takmbGTQYHdBLMAvA/sPK9Knvl5rgM+omQ== sdaoden at yandex.com From buildfarm at lists.opencsw.org Wed May 20 17:48:39 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 17:48:39 +0200 Subject: Solaris Buildfarm In-Reply-To: References: Message-ID: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> Hallo Rainer, Am 20.05.2015 um 17:42 schrieb Rainer Gerhards : > super, danke! pub key anbei.... > > Das gr??te Problem ist f?r mich immer, eine lauff?hige Umgebung f?r > "alles m?gliche" zusammenzubauen, da ist das super-hilfreich. Das sollte jetzt gehen: ssh rgerhards at login.opencsw.org In /etc/SETUP steht alles wichtige. Melde Dich einfach wenn Du besondere Pakete brauchst oder was fehlt. Beste Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 17:55:55 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 17:55:55 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> Message-ID: <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> Hi Steffen, Am 20.05.2015 um 15:31 schrieb Steffen Nurpmeso : > Dagobert Michelsen wrote: > |Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : > |> I'm maintaining S-nail, an extended mailx(1)-like MUA. I came > |> along OpenCSW via an announcement from Ingo Schwarze and would be > |> very interested in gaining access to the Solaris operating system > |> for compile-testing (and "make test"ing) this program! (I'm also > > |Sure, just send me your ssh public key and I?ll set you up. > > Wow, great, thank you very much! > I'll attach the key! > And... where do i have to look when i need more info? You should be able to do ssh sdaoden at login.opencsw.org Please make sure to read /etc/SETUP. Just let me know if you need anything. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 18:05:44 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Wed, 20 May 2015 18:05:44 +0200 Subject: Solaris Buildfarm In-Reply-To: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> Message-ID: 2015-05-20 17:48 GMT+02:00 Dagobert Michelsen : > Hallo Rainer, > > Am 20.05.2015 um 17:42 schrieb Rainer Gerhards : >> super, danke! pub key anbei.... >> >> Das gr??te Problem ist f?r mich immer, eine lauff?hige Umgebung f?r >> "alles m?gliche" zusammenzubauen, da ist das super-hilfreich. > > Das sollte jetzt gehen: > ssh rgerhards at login.opencsw.org > In /etc/SETUP steht alles wichtige. Melde Dich einfach wenn Du besondere Pakete brauchst > oder was fehlt. sieht sehr gut aus! k?nntest du mir kurz das cmd schicken um die build umgebung aufzusetzen - hast Du ja wahrscheinlich eben erst gemacht. Also pkgutil -i automake ... Thx! Rainer > > > Beste Gr??e > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > From buildfarm at lists.opencsw.org Wed May 20 18:10:38 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 18:10:38 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> Message-ID: <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> Hallo Rainer, Am 20.05.2015 um 18:05 schrieb Rainer Gerhards : > 2015-05-20 17:48 GMT+02:00 Dagobert Michelsen : >> Am 20.05.2015 um 17:42 schrieb Rainer Gerhards : >>> super, danke! pub key anbei.... >>> >>> Das gr??te Problem ist f?r mich immer, eine lauff?hige Umgebung f?r >>> "alles m?gliche" zusammenzubauen, da ist das super-hilfreich. >> >> Das sollte jetzt gehen: >> ssh rgerhards at login.opencsw.org >> In /etc/SETUP steht alles wichtige. Melde Dich einfach wenn Du besondere Pakete brauchst >> oder was fehlt. > > sieht sehr gut aus! > > k?nntest du mir kurz das cmd schicken um die build umgebung > aufzusetzen - hast Du ja wahrscheinlich eben erst gemacht. Also > > pkgutil -i automake ... Das brauchst Du nicht, die Zonen sind geshared zwischen allen Portern und ich maintaine die, d.h. die sind immer mit aktuellen Paketen, Compilern, Patches etc. versehen. Du kannst gleich loslegen mit Bauen. Hier sind noch ein paar Infos was man setzen muss: https://www.opencsw.org/manual/for-developers/index.html Mein Buildbot Setup sieht momentan so aus, das sollte also auch manuell gehen falls erforderlich: > rsyslog = BuildFactory() > rsyslog.addStep(Git(repourl='git://github.com/rsyslog/rsyslog.git', branch='master', mode='full')) > rsyslog.addStep(ShellCommand(command=['./autogen.sh'], env={'NOCONFIGURE': 'TRUE'})) > rsyslog.addStep(ShellCommand(command=['./configure'], > env={'CC': '/opt/csw/bin/gcc', > 'CFLAGS': '-I/opt/csw/include', > 'LDFLAGS': '-L/opt/csw/lib', > 'LD_OPTIONS': '-R/opt/csw/lib', > 'PKG_CONFIG_PATH': '/opt/csw/lib/pkgconfig'}, > logfiles={"config.log": "config.log"})) > rsyslog.addStep(ShellCommand(command=['gmake', 'all'])) > rsyslog.addStep(ShellCommand(command=['gmake', 'check'], > logfiles={"test-suite.log": "info/test-suite.log"})) Beste Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 18:25:55 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Wed, 20 May 2015 18:25:55 +0200 Subject: Solaris Buildfarm In-Reply-To: <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> Message-ID: 2015-05-20 18:10 GMT+02:00 Dagobert Michelsen : > Hallo Rainer, > > Am 20.05.2015 um 18:05 schrieb Rainer Gerhards : >> 2015-05-20 17:48 GMT+02:00 Dagobert Michelsen : >>> Am 20.05.2015 um 17:42 schrieb Rainer Gerhards : >>>> super, danke! pub key anbei.... >>>> >>>> Das gr??te Problem ist f?r mich immer, eine lauff?hige Umgebung f?r >>>> "alles m?gliche" zusammenzubauen, da ist das super-hilfreich. >>> >>> Das sollte jetzt gehen: >>> ssh rgerhards at login.opencsw.org >>> In /etc/SETUP steht alles wichtige. Melde Dich einfach wenn Du besondere Pakete brauchst >>> oder was fehlt. >> >> sieht sehr gut aus! >> >> k?nntest du mir kurz das cmd schicken um die build umgebung >> aufzusetzen - hast Du ja wahrscheinlich eben erst gemacht. Also >> >> pkgutil -i automake ... > > Das brauchst Du nicht, die Zonen sind geshared zwischen allen Portern und ich maintaine die, > d.h. die sind immer mit aktuellen Paketen, Compilern, Patches etc. versehen. Du kannst > gleich loslegen mit Bauen. Hier sind noch ein paar Infos was man setzen muss: > https://www.opencsw.org/manual/for-developers/index.html > > Mein Buildbot Setup sieht momentan so aus, das sollte also auch manuell gehen falls > erforderlich: > >> rsyslog = BuildFactory() >> rsyslog.addStep(Git(repourl='git://github.com/rsyslog/rsyslog.git', branch='master', mode='full')) >> rsyslog.addStep(ShellCommand(command=['./autogen.sh'], env={'NOCONFIGURE': 'TRUE'})) >> rsyslog.addStep(ShellCommand(command=['./configure'], >> env={'CC': '/opt/csw/bin/gcc', >> 'CFLAGS': '-I/opt/csw/include', >> 'LDFLAGS': '-L/opt/csw/lib', >> 'LD_OPTIONS': '-R/opt/csw/lib', >> 'PKG_CONFIG_PATH': '/opt/csw/lib/pkgconfig'}, >> logfiles={"config.log": "config.log"})) >> rsyslog.addStep(ShellCommand(command=['gmake', 'all'])) >> rsyslog.addStep(ShellCommand(command=['gmake', 'check'], >> logfiles={"test-suite.log": "info/test-suite.log"})) alles klar -- wenn man erst mal wenigstens etwas liest und dann erst macht, wird's eh schon einfacher ;) Trotzdem habe ich noch ein Problem: configure findet json-c nicht, und auf http://buildfarm.opencsw.org/versionmatrix.html habe ich es auch nicht gefunden. Bei Dir m?sste es aber eigentlich da gewesen sein... ich in im moment auf der u11s. Rainer > > > Beste Gr??e > > ? Dago > > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > From buildfarm at lists.opencsw.org Wed May 20 18:47:37 2015 From: buildfarm at lists.opencsw.org (Steffen Nurpmeso via buildfarm) Date: Wed, 20 May 2015 18:47:37 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> Message-ID: <20150520164737.MCPus99e6M3A%sdaoden@yandex.com> Hallo! Dagobert Michelsen wrote: |Am 20.05.2015 um 15:31 schrieb Steffen Nurpmeso : |> Dagobert Michelsen wrote: |>|Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : |>|> I'm maintaining S-nail, an extended mailx(1)-like MUA. I came |>|> along OpenCSW via an announcement from Ingo Schwarze and would be |>|> very interested in gaining access to the Solaris operating system |>|> for compile-testing (and "make test"ing) this program! (I'm also |> |>|Sure, just send me your ssh public key and I?ll set you up. |> |> Wow, great, thank you very much! |> I'll attach the key! |> And... where do i have to look when i need more info? | |You should be able to do | ssh sdaoden at login.opencsw.org I'm in! Thanks!! |Please make sure to read /etc/SETUP. Just let me know if you need anything. Got it. Wonderful service! Ciao, --steffen From buildfarm at lists.opencsw.org Wed May 20 21:34:06 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 21:34:06 +0200 Subject: [platform-testers] texinfo pretest In-Reply-To: <201505201710.t4KHA9Su019451@freefriends.org> References: <201505201710.t4KHA9Su019451@freefriends.org> Message-ID: <41F6EABD-34E5-4FE4-B827-8901AB79C3CB@opencsw.org> Hi Karl, Am 20.05.2015 um 19:10 schrieb Karl Berry : > Sure, I would need your ssh public key and intended user name. > > ssh attached, user karl if available, else karlb, else karlberry, > else whatever. > > Can I list you with texinfo here? > https://www.opencsw.org/extend-it/signup/to-upstream-maintainers/ > > Yes, Gavin and I are the maintainers of Texinfo. You should be able to do now ssh karl at login.opencsw.org Please make sure to read /etc/SETUP. Just let me know if you need anything. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 21:36:28 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 20 May 2015 21:36:28 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> Message-ID: <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> Hallo Rainer, Am 20.05.2015 um 18:25 schrieb Rainer Gerhards : > Trotzdem habe ich noch ein Problem: configure findet json-c nicht, und > auf http://buildfarm.opencsw.org/versionmatrix.html > habe ich es auch nicht gefunden. Bei Dir m?sste es aber eigentlich da > gewesen sein... ich in im moment auf der u11s. Das liegt daran, das ich die Pakete f?r die Library erst heute gebaut habe und da noch ein Fehler drin war. Deshalb habe ich das aktuelle Paket per Hand installiert, da ich nicht auf das automatische Update warten wollte und auf Solaris 11 habe ich das nicht gebraucht und nicht damit gerechnet, dass das heute noch erforderlich ist :-) Ich habe das jetzt auch manuell auf unstable11s und unstable11x installiert. Normalerweise sollten alle Pakete von unstable* auch auf unstable* installiert sein. Beste Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Wed May 20 21:39:09 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Wed, 20 May 2015 21:39:09 +0200 Subject: Solaris Buildfarm In-Reply-To: <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> Message-ID: Np ich hatte einfach die aktuellste platform gew?hlt weil es da meistens am wenigsten Problem gibt;) ich schau morgen fr?h rein.. Sent from phone, thus brief. Am 20.05.2015 21:36 schrieb "Dagobert Michelsen" : > Hallo Rainer, > > Am 20.05.2015 um 18:25 schrieb Rainer Gerhards : > > Trotzdem habe ich noch ein Problem: configure findet json-c nicht, und > > auf http://buildfarm.opencsw.org/versionmatrix.html > > habe ich es auch nicht gefunden. Bei Dir m?sste es aber eigentlich da > > gewesen sein... ich in im moment auf der u11s. > > Das liegt daran, das ich die Pakete f?r die Library erst heute gebaut habe > und da noch ein Fehler drin war. Deshalb habe ich das aktuelle Paket per > Hand installiert, da ich nicht auf das automatische Update warten wollte > und > auf Solaris 11 habe ich das nicht gebraucht und nicht damit gerechnet, dass > das heute noch erforderlich ist :-) > Ich habe das jetzt auch manuell auf unstable11s und unstable11x > installiert. > Normalerweise sollten alle Pakete von unstable* auch auf unstable* > installiert sein. > > > Beste Gr??e > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting > to do something, > and then doing it so hard that you become great in the process." - xkcd > #896 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Thu May 21 09:37:37 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 21 May 2015 09:37:37 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> Message-ID: <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> Hallo Rainer, Am 20.05.2015 um 21:39 schrieb Rainer Gerhards : > Np ich hatte einfach die aktuellste platform gew?hlt weil es da meistens am wenigsten Problem gibt;) ich schau morgen fr?h rein.. Neue Pakete von json-c sind gebaut und gepushed und auch auf unstable10* und unstable11* installiert. Hattest Du schon Gelegenheit den master-candidate umzuschalten? Ich muss mal schauen ob das so geht wie ich das jetzt gemacht habe, bisher hatte ich nur einen Branch pro Repository. Alternativ kann man auch Hooks ?ber das GitHub-API aktivieren, so dass nach einem Commit ohne Pollen direkt getriggert wird. Beste Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 21 09:47:54 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Thu, 21 May 2015 09:47:54 +0200 Subject: Solaris Buildfarm In-Reply-To: <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> Message-ID: 2015-05-21 9:37 GMT+02:00 Dagobert Michelsen : > Hallo Rainer, > > Am 20.05.2015 um 21:39 schrieb Rainer Gerhards : >> Np ich hatte einfach die aktuellste platform gew?hlt weil es da meistens am wenigsten Problem gibt;) ich schau morgen fr?h rein.. > > Neue Pakete von json-c sind gebaut und gepushed und auch auf unstable10* und > unstable11* installiert. super, build hat gerade auch geklappt. > > Hattest Du schon Gelegenheit den master-candidate umzuschalten? Ich muss mal schauen > ob das so geht wie ich das jetzt gemacht habe, bisher hatte ich nur einen Branch pro > Repository. Noch nicht, kommt aber gleich. Zum rsyslog workflow: 1. mache changes in eigenem branch (NICHT master-candidate!) 2. mache PR --> travis l?uft los (unter ubuntu, k?nnen halt nur das) 3. travis OK --> merge nach master-candidate 4. master-candidate wird auf eigener buildfarm getestet ich habe da diverse linux flavors; dieser step findet selten was, kommt aber alle Zeit lang vor. Die platformen l?ufen scheduled, ein voller Durchlauf braucht einen Tag (wegen der Schedule). In diesem step sind in master-candidate verschiedene changes drin (wobei alle step 3 "passed" sind). 5. Wenn in 4 keine problem mehr auftraten, merge master-candidate -> master 6. bei n?chster Release merge master -> v8-stable Die merges werden dabei manuell gemacht, von daher kann es ggfs. auch mal schneller oder langsamer gehen (vor allen Dingen, wenn in step 4 doch noch ein change "durchgefallen" ist). Der strndup patch steckte bisher noch in step 2. Wobei ich hier den Sonderfall hatte, dass ich erst mal sehen wollte, ob es ?berhaupt auf Solaris baut, sprich ob es ?berhaupt ein ordentlicher fix ist (normalerweise passiert das in step 1). Ich sch jetzt noch, ob die testbench auch auf der buildfamr l?uft und dann gehts wohl weiter zu step 3, d.h. Du siehst den Patch dann auf master-candidate. > Alternativ kann man auch Hooks ?ber das GitHub-API aktivieren, so dass > nach einem Commit ohne Pollen direkt getriggert wird. Das h?rt sich recht interessant an -- w?rde step 2 wertvoller machen. Rainer > > > Beste Gr??e > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > From buildfarm at lists.opencsw.org Thu May 21 10:18:56 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Thu, 21 May 2015 10:18:56 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> Message-ID: so, jetzt ist es in master-candidate. Die testbench hat zwar noch ein paar problemchen, aber das h?ngt nicht mit dem fix zusammen... 2015-05-21 9:47 GMT+02:00 Rainer Gerhards : > 2015-05-21 9:37 GMT+02:00 Dagobert Michelsen : >> Hallo Rainer, >> >> Am 20.05.2015 um 21:39 schrieb Rainer Gerhards : >>> Np ich hatte einfach die aktuellste platform gew?hlt weil es da meistens am wenigsten Problem gibt;) ich schau morgen fr?h rein.. >> >> Neue Pakete von json-c sind gebaut und gepushed und auch auf unstable10* und >> unstable11* installiert. > > super, build hat gerade auch geklappt. > >> >> Hattest Du schon Gelegenheit den master-candidate umzuschalten? Ich muss mal schauen >> ob das so geht wie ich das jetzt gemacht habe, bisher hatte ich nur einen Branch pro >> Repository. > > Noch nicht, kommt aber gleich. Zum rsyslog workflow: > > 1. mache changes in eigenem branch (NICHT master-candidate!) > 2. mache PR --> travis l?uft los (unter ubuntu, k?nnen halt nur das) > 3. travis OK --> merge nach master-candidate > 4. master-candidate wird auf eigener buildfarm getestet > ich habe da diverse linux flavors; dieser step findet selten was, kommt aber > alle Zeit lang vor. Die platformen l?ufen scheduled, ein voller > Durchlauf braucht > einen Tag (wegen der Schedule). In diesem step sind in master-candidate > verschiedene changes drin (wobei alle step 3 "passed" sind). > 5. Wenn in 4 keine problem mehr auftraten, merge master-candidate -> master > 6. bei n?chster Release merge master -> v8-stable > > Die merges werden dabei manuell gemacht, von daher kann es ggfs. auch > mal schneller oder langsamer gehen (vor allen Dingen, wenn in step 4 > doch noch ein change "durchgefallen" ist). > > Der strndup patch steckte bisher noch in step 2. Wobei ich hier den > Sonderfall hatte, dass ich erst mal sehen wollte, ob es ?berhaupt auf > Solaris baut, sprich ob es ?berhaupt ein ordentlicher fix ist > (normalerweise passiert das in step 1). Ich sch jetzt noch, ob die > testbench auch auf der buildfamr l?uft und dann gehts wohl weiter zu > step 3, d.h. Du siehst den Patch dann auf master-candidate. > > >> Alternativ kann man auch Hooks ?ber das GitHub-API aktivieren, so dass >> nach einem Commit ohne Pollen direkt getriggert wird. > > Das h?rt sich recht interessant an -- w?rde step 2 wertvoller machen. > > Rainer >> >> >> Beste Gr??e >> >> ? Dago >> >> -- >> "You don't become great by trying to be great, you become great by wanting to do something, >> and then doing it so hard that you become great in the process." - xkcd #896 >> From buildfarm at lists.opencsw.org Thu May 21 10:28:32 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 21 May 2015 10:28:32 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> Message-ID: <8AE39975-6766-42B5-97B7-C0E7EBE414E0@opencsw.org> Hallo Rainer, Am 21.05.2015 um 09:47 schrieb Rainer Gerhards : > Noch nicht, kommt aber gleich. Zum rsyslog workflow: > > 1. mache changes in eigenem branch (NICHT master-candidate!) > 2. mache PR --> travis l?uft los (unter ubuntu, k?nnen halt nur das) > 3. travis OK --> merge nach master-candidate > 4. master-candidate wird auf eigener buildfarm getestet > ich habe da diverse linux flavors; dieser step findet selten was, kommt aber > alle Zeit lang vor. Die platformen l?ufen scheduled, ein voller > Durchlauf braucht > einen Tag (wegen der Schedule). In diesem step sind in master-candidate > verschiedene changes drin (wobei alle step 3 "passed" sind). > 5. Wenn in 4 keine problem mehr auftraten, merge master-candidate -> master > 6. bei n?chster Release merge master -> v8-stable > > Die merges werden dabei manuell gemacht, von daher kann es ggfs. auch > mal schneller oder langsamer gehen (vor allen Dingen, wenn in step 4 > doch noch ein change "durchgefallen" ist). > > Der strndup patch steckte bisher noch in step 2. Wobei ich hier den > Sonderfall hatte, dass ich erst mal sehen wollte, ob es ?berhaupt auf > Solaris baut, sprich ob es ?berhaupt ein ordentlicher fix ist > (normalerweise passiert das in step 1). Ich sch jetzt noch, ob die > testbench auch auf der buildfamr l?uft und dann gehts wohl weiter zu > step 3, d.h. Du siehst den Patch dann auf master-candidate. Verstehe. Wie passt da denn die OpenCSW Buildfarm am besten mit rein? Ich kann auch auf alle Branches triggern und nach Commits in jedem Branch bauen. Wie bekommst Du die Ergebnisse? Hast Du ein Dashboard oder etwas vergleichbares wo man den Buildbot integrieren k?nnte? Oder sollte die OpenCSW-Farm eher als direkter Client an Deine Buildfarm angeschlossen werden? Beste Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 21 11:00:10 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Thu, 21 May 2015 11:00:10 +0200 Subject: Solaris Buildfarm In-Reply-To: <8AE39975-6766-42B5-97B7-C0E7EBE414E0@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> <8AE39975-6766-42B5-97B7-C0E7EBE414E0@opencsw.org> Message-ID: 2015-05-21 10:28 GMT+02:00 Dagobert Michelsen : > Hallo Rainer, > > Am 21.05.2015 um 09:47 schrieb Rainer Gerhards : >> Noch nicht, kommt aber gleich. Zum rsyslog workflow: >> >> 1. mache changes in eigenem branch (NICHT master-candidate!) >> 2. mache PR --> travis l?uft los (unter ubuntu, k?nnen halt nur das) >> 3. travis OK --> merge nach master-candidate >> 4. master-candidate wird auf eigener buildfarm getestet >> ich habe da diverse linux flavors; dieser step findet selten was, kommt aber >> alle Zeit lang vor. Die platformen l?ufen scheduled, ein voller >> Durchlauf braucht >> einen Tag (wegen der Schedule). In diesem step sind in master-candidate >> verschiedene changes drin (wobei alle step 3 "passed" sind). >> 5. Wenn in 4 keine problem mehr auftraten, merge master-candidate -> master >> 6. bei n?chster Release merge master -> v8-stable >> >> Die merges werden dabei manuell gemacht, von daher kann es ggfs. auch >> mal schneller oder langsamer gehen (vor allen Dingen, wenn in step 4 >> doch noch ein change "durchgefallen" ist). >> >> Der strndup patch steckte bisher noch in step 2. Wobei ich hier den >> Sonderfall hatte, dass ich erst mal sehen wollte, ob es ?berhaupt auf >> Solaris baut, sprich ob es ?berhaupt ein ordentlicher fix ist >> (normalerweise passiert das in step 1). Ich sch jetzt noch, ob die >> testbench auch auf der buildfamr l?uft und dann gehts wohl weiter zu >> step 3, d.h. Du siehst den Patch dann auf master-candidate. > > Verstehe. Wie passt da denn die OpenCSW Buildfarm am besten mit rein? > Ich kann auch auf alle Branches triggern und nach Commits in jedem Branch > bauen. Wie bekommst Du die Ergebnisse? Hast Du ein Dashboard oder etwas > vergleichbares wo man den Buildbot integrieren k?nnte? Oder sollte die > OpenCSW-Farm eher als direkter Client an Deine Buildfarm angeschlossen > werden? Meine Buildfarm ist stark historisch gewachsen und eine Bastell?sung, die man bei Gelegenheit (wenn Zeit ist ;)) mal aktualisieren sollte. Ich habe schon mit Interesse den Buildbot gesehen ;) Ich bekomme die Ergebnisse im Moment ganz einfach per mail - das sind 5 am Tag, das geht. Von daher w?rde ich sagen, lass OpenCSW erst mal master-candidate bauen und mir bei fehler eine Mail schicken. Das reicht zu Anfang. Wenn ich intern umbaue, dann sollten wir aber nochmal weiterdenken. Sofern m?glich, sollte OpenCSW bei Fehlern in *master* ein github issue erzeugen. Denn da sollte ich eigentlich nicht mehr reinlaufen. In dem Zusammenhang sei allerdings auch angemerkt, dass auch die *testbench* (nur die) historisch gewachsen ist und teilweise noch fehler erzeugt, wo keine sind. Da bin ich dran, ist aber ein etwas schwierigere Prozess. Harte Fehler sind aber definitiv alle build issues -- und davon gibt es gerade auf solaris immer wieder welche (ab jetzt wird's vermutlich besser! :-)). Rainer > > > Beste Gr??e > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > From buildfarm at lists.opencsw.org Thu May 21 11:56:10 2015 From: buildfarm at lists.opencsw.org (Jan Holzhueter via buildfarm) Date: Thu, 21 May 2015 11:56:10 +0200 Subject: Solaris Buildfarm In-Reply-To: References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> <8AE39975-6766-42B5-97B7-C0E7EBE414E0@opencsw.org> Message-ID: <555DABBA.6090401@opencsw.org> Hi, missbrauche den Thread mal (hoffe das ist ok) um mal ein patches durch die Gegend zu schmei?en :) Oracle selbst hat ein paar Patches: https://hg.java.net/hg/solaris-userland~gate/file/feeaeac8a97c/components/rsyslog/patches die sind zwar f?r 6 irgendwas aber vielleicht ist da noch was von Interessent. Au?erdem haben die pkgsrc leute auch eine sammlung: https://github.com/joyent/pkgsrc/tree/trunk/sysutils/rsyslog/patches die Teilweise auch Solaris betreffen. Gru? Jan Holzh?ter From buildfarm at lists.opencsw.org Thu May 21 12:04:35 2015 From: buildfarm at lists.opencsw.org (Rainer Gerhards via buildfarm) Date: Thu, 21 May 2015 12:04:35 +0200 Subject: Solaris Buildfarm In-Reply-To: <555DABBA.6090401@opencsw.org> References: <446A9AC8-E500-4C11-89BB-71B5D7594144@opencsw.org> <13260C00-6D70-4146-A42B-E2B632658CCE@opencsw.org> <784AFA92-C1C3-4651-AB1F-91AA8D0192DE@opencsw.org> <3ED49F89-124C-4389-B3E1-719DB984F3CD@opencsw.org> <8AE39975-6766-42B5-97B7-C0E7EBE414E0@opencsw.org> <555DABBA.6090401@opencsw.org> Message-ID: 2015-05-21 11:56 GMT+02:00 Jan Holzhueter : > Hi, > missbrauche den Thread mal (hoffe das ist ok) > um mal ein patches durch die Gegend zu schmei?en :) > > Oracle selbst hat ein paar Patches: > https://hg.java.net/hg/solaris-userland~gate/file/feeaeac8a97c/components/rsyslog/patches > > die sind zwar f?r 6 irgendwas aber vielleicht ist da noch was von > Interessent. > > Au?erdem haben die pkgsrc leute auch eine sammlung: > https://github.com/joyent/pkgsrc/tree/trunk/sysutils/rsyslog/patches > > die Teilweise auch Solaris betreffen. ach, ist ja interessant.... Ich hab bei mir mal nen issue tracker aufgemacht: https://github.com/rsyslog/rsyslog/issues/352 Rainer > > Gru? > Jan Holzh?ter > > > From buildfarm at lists.opencsw.org Thu May 21 15:22:01 2015 From: buildfarm at lists.opencsw.org (Carsten Grzemba via buildfarm) Date: Thu, 21 May 2015 15:22:01 +0200 Subject: brocken link libpcre.so: Please update CSWlibpcre-dev In-Reply-To: References: Message-ID: At least on unstable10x the CSWlibpcre-dev version is outdated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Thu May 21 15:24:58 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 21 May 2015 15:24:58 +0200 Subject: brocken link libpcre.so: Please update CSWlibpcre-dev In-Reply-To: References: Message-ID: Hi Carsten, > Am 21.05.2015 um 15:22 schrieb Carsten Grzemba via buildfarm : > > At least on unstable10x the CSWlibpcre-dev version is outdated. PCRE has been updated on unstable*. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 21 18:21:42 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Thu, 21 May 2015 18:21:42 +0200 Subject: binutils 2.24 on solaris 9 Message-ID: <555E0616.40406@opencsw.org> Hi, may you update binutils to 2.24 freshly build on solaris 9x and 9s? Can you confirm that solaris 10 is already at 2.24 level? binutils-2.24,REV=2015.05.21-SunOS5.9-i386-CSW.pkg.gz binutils-2.24,REV=2015.05.21-SunOS5.9-sparc-CSW.pkg.gz Thanks, Riccardo From buildfarm at lists.opencsw.org Thu May 21 18:32:41 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 21 May 2015 18:32:41 +0200 Subject: binutils 2.24 on solaris 9 In-Reply-To: <555E0616.40406@opencsw.org> References: <555E0616.40406@opencsw.org> Message-ID: <138F058E-07E8-44DB-9E79-BC5080AA6809@opencsw.org> Hi Riccardo, Am 21.05.2015 um 18:21 schrieb Riccardo Mottola via buildfarm : > may you update binutils to 2.24 freshly build on solaris 9x and 9s? > > Can you confirm that solaris 10 is already at 2.24 level? > > binutils-2.24,REV=2015.05.21-SunOS5.9-i386-CSW.pkg.gz > binutils-2.24,REV=2015.05.21-SunOS5.9-sparc-CSW.pkg.gz Did you push it? I only see the old version: > unstable9s# pkgutil -U -a binutils > => Fetching new catalog and descriptions (file:///export/mirror/opencsw-official/unstable/sparc/5.9) if available ... > ==> 3032 packages loaded from /var/opt/csw/pkgutil/catalog._export_mirror_opencsw-official_unstable_sparc_5.9 > common package catalog size > binutils CSWbinutils 2.22,REV=2012.06.14 82.8 MB Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Fri May 22 09:10:49 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Fri, 22 May 2015 09:10:49 +0200 Subject: binutils 2.24 on solaris 9 In-Reply-To: <138F058E-07E8-44DB-9E79-BC5080AA6809@opencsw.org> References: <555E0616.40406@opencsw.org> <138F058E-07E8-44DB-9E79-BC5080AA6809@opencsw.org> Message-ID: <555ED679.70408@opencsw.org> Hi Dagobert, Dagobert Michelsen wrote: > Did you push it? I only see the old version: > >> unstable9s# pkgutil -U -a binutils >> => Fetching new catalog and descriptions (file:///export/mirror/opencsw-official/unstable/sparc/5.9) if available ... >> ==> 3032 packages loaded from /var/opt/csw/pkgutil/catalog._export_mirror_opencsw-official_unstable_sparc_5.9 >> common package catalog size >> binutils CSWbinutils 2.22,REV=2012.06.14 82.8 MB I did csw-upload it! Just retrying again: Checking 1 package against catalog unstable sparc SunOS5.9 Checking 1 package against catalog unstable i386 SunOS5.9 All checks successful. Proceeding. Inserting binutils (i386 SunOS5.9) into catalog unstable i386 SunOS5.9 Inserting binutils (sparc SunOS5.9) into catalog unstable sparc SunOS5.9 Riccardo From buildfarm at lists.opencsw.org Fri May 22 11:11:07 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Fri, 22 May 2015 11:11:07 +0200 Subject: binutils 2.24 on solaris 9 In-Reply-To: <555ED679.70408@opencsw.org> References: <555E0616.40406@opencsw.org> <138F058E-07E8-44DB-9E79-BC5080AA6809@opencsw.org> <555ED679.70408@opencsw.org> Message-ID: Hi Riccardo, Am 22.05.2015 um 09:10 schrieb Riccardo Mottola : > Dagobert Michelsen wrote: >> Did you push it? I only see the old version: >> >>> unstable9s# pkgutil -U -a binutils >>> => Fetching new catalog and descriptions (file:///export/mirror/opencsw-official/unstable/sparc/5.9) if available ... >>> ==> 3032 packages loaded from /var/opt/csw/pkgutil/catalog._export_mirror_opencsw-official_unstable_sparc_5.9 >>> common package catalog size >>> binutils CSWbinutils 2.22,REV=2012.06.14 82.8 MB > > I did csw-upload it! > > Just retrying again: > > Checking 1 package against catalog unstable sparc SunOS5.9 > Checking 1 package against catalog unstable i386 SunOS5.9 > All checks successful. Proceeding. > Inserting binutils (i386 SunOS5.9) into catalog unstable i386 SunOS5.9 > Inserting binutils (sparc SunOS5.9) into catalog unstable sparc SunOS5.9 You broke the catalog :-) > 2015/05/22 10:54:40 Problem in the catalog: Package CSWbinutils declares dependency on CSWlibfl2 but CSWlibfl2 is missing from the {unstable i386 SunOS5.9} catalog. Hmmm?. > CHECKPKG_OVERRIDES_CSWbinutils_i386_5.9 += dependency-on-nonexistent-package|CSWlibfl2 http://wiki.opencsw.org/checkpkg-error-tags#toc18 Ok, I cheated :-) I added the description right now. Please take out the override and make that a conditional dependency to only depend on CSWlibfl2 on Solaris 10 and 11. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Sun May 24 08:59:48 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Sun, 24 May 2015 08:59:48 +0200 Subject: check status of machine Message-ID: <556176E4.6030204@opencsw.org> Hi, I have a build failed this night, I lost the log but I suppose the proxy machine is hanging again, at least for me http://buildfarm.opencsw.org/pkgdb/srv4/ Is not reachable :( May you check? Riccardo From buildfarm at lists.opencsw.org Sun May 24 13:46:01 2015 From: buildfarm at lists.opencsw.org (Riccardo Mottola via buildfarm) Date: Sun, 24 May 2015 13:46:01 +0200 Subject: binutil packages ready Message-ID: <5561B9F9.7030409@opencsw.org> Hello, please install/update all 2.24 packages. * Platform solaris9-sparc (built on host 'unstable9s') CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.9-sparc-CSW.pkg.gz * Platform solaris9-i386 (built on host 'unstable9x') CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.9-i386-CSW.pkg.gz * Platform solaris10-sparc (built on this host) CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.10-sparc-CSW.pkg.gz * Platform solaris10-i386 (built on host 'unstable10x') CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.10-i386-CSW.pkg.gz Riccardo From buildfarm at lists.opencsw.org Sun May 24 22:53:11 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 24 May 2015 22:53:11 +0200 Subject: binutil packages ready In-Reply-To: <5561B9F9.7030409@opencsw.org> References: <5561B9F9.7030409@opencsw.org> Message-ID: <4746DE32-4277-4D43-85D7-647FABC3DCC6@opencsw.org> Hi Riccardo, Am 24.05.2015 um 13:46 schrieb Riccardo Mottola via buildfarm : > please install/update all 2.24 packages. > > * Platform solaris9-sparc (built on host 'unstable9s') > CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.9-sparc-CSW.pkg.gz > > * Platform solaris9-i386 (built on host 'unstable9x') > CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.9-i386-CSW.pkg.gz > > * Platform solaris10-sparc (built on this host) > CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.10-sparc-CSW.pkg.gz > > * Platform solaris10-i386 (built on host 'unstable10x') > CSWbinutils /home/rmottola/pkgs/binutils-2.24,REV=2015.05.24-SunOS5.10-i386-CSW.pkg.gz Done. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue May 26 20:51:19 2015 From: buildfarm at lists.opencsw.org (Steffen Nurpmeso via buildfarm) Date: Tue, 26 May 2015 20:51:19 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> Message-ID: <20150526185119.v-LmWG_el-m_%sdaoden@yandex.com> Hello! Dagobert Michelsen wrote: |Am 20.05.2015 um 15:31 schrieb Steffen Nurpmeso : |> Dagobert Michelsen wrote: |>|Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : |>|> I'm maintaining S-nail, an extended mailx(1)-like MUA. I came |>|> along OpenCSW via an announcement from Ingo Schwarze and would be |>|> very interested in gaining access to the Solaris operating system |>|> for compile-testing (and "make test"ing) this program! (I'm also |You should be able to do | ssh sdaoden at login.opencsw.org |Please make sure to read /etc/SETUP. Just let me know if you need anything. Once more i want to thank you for giving me this option! Nothing more than some name shadowing warnings on the code side. The build system of S-nail however required quite a lot of work to be able to get us going here, on at least 5.10 and 5.11. And i have to admit i remain having problems that seem to originate in the gcc(1) installations and also in OpenSSL; i have spend this entire day on your systems and wasted an immense amount of CPU time without being able to improve this situation. Excerpt of our [master] INSTALL: . Solaris * First of all: thanks to OpenCSW.org for offering SSH access to their Solaris build cluster! Yes. Yes. Yes! - According to standards(5) we require the /usr/xpg4 environment, and will bail if we cannot find it. - I couldn't get us going on SunOS 5.9: the build system had to be extended to check for UINTPTR_MAX being defined as the empty string and similar very special things. I first worked around that on the Sun via __UINTPTR_MAX__, but on x86 that wouldn't have helped, so i removed that hack again. Otherwise nothing much should prevent us. - With WANT_AUTOCC: we try to use Sun cc(1) whenever we find it. If your gcc(1) installation is doing alright you have to turn WANT_AUTOCC off and use $CC, $CFLAGS and $LDFLAGS. Yeah! (+_?) - I will never get iconv(3) right for Solaris it seems. Just like for DragonFly we'd had to do a dance around "char", "const char", "char restrict" and whatever combinations are possible. (Maybe the build system will at a later time check -Werror and generate test programs to do that really right by not causing compiler warnings.) - In order to be able to run the tests you will need a cksum that supports CRC-32 (POSIX). We look into /opt/csw/gnu/cksum, but if that is not there you have to adjust cksum (see above) to something that works. (A future version of S-nail will use different testing, but until then: Sorry!) A later version of S-nail will include expected-/real-result comparison, but i didn't make it to this one yet. (Of course we could do so today for what we have, but the entire MIME code will be replaced and then all of that will have to be changed anyway. I searched for a quick-and-dirty approach once i took maintainership, facing this situation, and then i didn't expect any problems with cksum(1) a.k.a. CRC-32. And including a CRC-32 tester isn't worth it either with the upcoming changes in mind.) SunOS 5.10 Generic_150400-17 sun4v sparc SUNW,SPARC-Enterprise-T5220 - gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) + A lot of warnings on longjmp() clobbering. + S/MIME tests fail with "OpenSSL 1.0.1j 15 Oct 2014 (Library: OpenSSL 1.0.1m 19 Mar 2015)": behave:s/mime:sign/verify: Error creating the PKCS#7 signing object: \ error:21083097:lib(33):func(131):reason(151) "login". This error we now produce, so something seems to have been broken -- since, on "login", S-nail already ran last Friday, and back then we didn't produce this error! SunOS 5.10 Generic_150400-17 sun4v sparc SUNW,SPARC-Enterprise-T5220 - cc: Sun C 5.9 SunOS_sparc Patch 124867-16 2010/08/11 + Some harmless warnings. + S/MIME tests fail with "OpenSSL 1.0.1m 19 Mar 2015": behave:s/mime:sign/verify: Error creating the PKCS#7 signing object: \ error:21083097:lib(33):func(131):reason(151) Ouch! The same. Something must have been broken on the installation? SunOS 5.10 Generic_147441-19 i86pc i386 i86pc - cc: Sun C 5.9 SunOS_i386 Patch 124868-15 2010/08/11 + Some harmless warnings. Fine beside that. SunOS 5.11 11.2 sun4u sparc SUNW,SPARC-Enterprise - (GCC) 4.9.2 + We forcefully disable stack protectors on SunOS/gcc because of linking errors: Undefined first referenced symbol in file __stack_chk_fail accmacvar.o __stack_chk_guard accmacvar.o ld: fatal: symbol referencing errors It works just fine if we don't use -fstack-protector-X. Internet suggests we will have to link in -lssp manually. That is good enough for now, i'll check that when i release v14.8.1 in a month with the final codebase. + Quite some (false) warnings on maybe-uninitialized. SunOS 5.11 11.0 i86pc i386 i86pc - gcc (GCC) 4.9.2 + Couldn't link: Undefined first referenced symbol in file __builtin_stdarg_start auxlily.o Here i do believe this is a gcc(1) installation issue? Do you have any hints on how to circumvent that? I can't get around to thank you once again. Ciao! --steffen From buildfarm at lists.opencsw.org Wed May 27 18:58:06 2015 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Wed, 27 May 2015 18:58:06 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: <20150526185119.v-LmWG_el-m_%sdaoden@yandex.com> References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> <20150526185119.v-LmWG_el-m_%sdaoden@yandex.com> Message-ID: Hi Steffen, > Am 26.05.2015 um 20:51 schrieb Steffen Nurpmeso : > > Hello! > > Dagobert Michelsen wrote: > |Am 20.05.2015 um 15:31 schrieb Steffen Nurpmeso : > |> Dagobert Michelsen wrote: > |>|Am 20.05.2015 um 13:10 schrieb Steffen Nurpmeso : > |>|> I'm maintaining S-nail, an extended mailx(1)-like MUA. I came > |>|> along OpenCSW via an announcement from Ingo Schwarze and would be > |>|> very interested in gaining access to the Solaris operating system > |>|> for compile-testing (and "make test"ing) this program! (I'm also > > |You should be able to do > | ssh sdaoden at login.opencsw.org > |Please make sure to read /etc/SETUP. Just let me know if you need anything. > > Once more i want to thank you for giving me this option! Sure, glad I could help. > Nothing more than some name shadowing warnings on the code side. > The build system of S-nail however required quite a lot of work to > be able to get us going here, on at least 5.10 and 5.11. > > And i have to admit i remain having problems that seem to > originate in the gcc(1) installations and also in OpenSSL; i have > spend this entire day on your systems and wasted an immense amount > of CPU time without being able to improve this situation. > Excerpt of our [master] INSTALL: > > . Solaris > * First of all: thanks to OpenCSW.org for offering SSH access to > their Solaris build cluster! > > Yes. Yes. Yes! > > - According to standards(5) we require the /usr/xpg4 environment, and > will bail if we cannot find it. > - I couldn't get us going on SunOS 5.9: the build system had to be > extended to check for UINTPTR_MAX being defined as the empty string > and similar very special things. > > I first worked around that on the Sun via __UINTPTR_MAX__, but on > x86 that wouldn't have helped, so i removed that hack again. > Otherwise nothing much should prevent us. > > - With WANT_AUTOCC: we try to use Sun cc(1) whenever we find it. > If your gcc(1) installation is doing alright you have to turn > WANT_AUTOCC off and use $CC, $CFLAGS and $LDFLAGS. > > Yeah! (+_?) The path what somewhat standardized to /opt/SUNWspro for earlier versions and /opt/sunstudio12.1 /opt/solarisstudio12.3 /opt/solarisstudio12.4 for newer versions where the prefixes are hardcoded in the installer. > - I will never get iconv(3) right for Solaris it seems. > > Just like for DragonFly we'd had to do a dance around "char", > "const char", "char restrict" and whatever combinations are > possible. (Maybe the build system will at a later time check > -Werror and generate test programs to do that really right by not > causing compiler warnings.) This is also a speciality with Sun Studio which is very strict on ?const? issues. > - In order to be able to run the tests you will need a cksum that > supports CRC-32 (POSIX). We look into /opt/csw/gnu/cksum, but if > that is not there you have to adjust cksum (see above) to something > that works. (A future version of S-nail will use different > testing, but until then: Sorry!) > > A later version of S-nail will include expected-/real-result > comparison, but i didn't make it to this one yet. (Of course we > could do so today for what we have, but the entire MIME code will > be replaced and then all of that will have to be changed anyway. > I searched for a quick-and-dirty approach once i took > maintainership, facing this situation, and then i didn't expect > any problems with cksum(1) a.k.a. CRC-32. And including a CRC-32 > tester isn't worth it either with the upcoming changes in mind.) > > SunOS 5.10 Generic_150400-17 sun4v sparc SUNW,SPARC-Enterprise-T5220 > - gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) > + A lot of warnings on longjmp() clobbering. > + S/MIME tests fail with "OpenSSL 1.0.1j 15 Oct 2014 (Library: > OpenSSL 1.0.1m 19 Mar 2015)": > behave:s/mime:sign/verify: > Error creating the PKCS#7 signing object: \ > error:21083097:lib(33):func(131):reason(151) This gcc is really old and shipped with Solaris. I suggest not to use it. > "login". This error we now produce, so something seems to have > been broken -- since, on "login", S-nail already ran last Friday, > and back then we didn't produce this error! > > SunOS 5.10 Generic_150400-17 sun4v sparc SUNW,SPARC-Enterprise-T5220 > - cc: Sun C 5.9 SunOS_sparc Patch 124867-16 2010/08/11 > + Some harmless warnings. > + S/MIME tests fail with "OpenSSL 1.0.1m 19 Mar 2015": > behave:s/mime:sign/verify: > Error creating the PKCS#7 signing object: \ > error:21083097:lib(33):func(131):reason(151) > > Ouch! The same. Something must have been broken on the > installation? > > SunOS 5.10 Generic_147441-19 i86pc i386 i86pc > - cc: Sun C 5.9 SunOS_i386 Patch 124868-15 2010/08/11 > + Some harmless warnings. > > Fine beside that. > > SunOS 5.11 11.2 sun4u sparc SUNW,SPARC-Enterprise > - (GCC) 4.9.2 > + We forcefully disable stack protectors on SunOS/gcc because of > linking errors: > Undefined first referenced > symbol in file > __stack_chk_fail accmacvar.o > __stack_chk_guard accmacvar.o > ld: fatal: symbol referencing errors > > It works just fine if we don't use -fstack-protector-X. > Internet suggests we will have to link in -lssp manually. > That is good enough for now, i'll check that when i release > v14.8.1 in a month with the final codebase. > > + Quite some (false) warnings on maybe-uninitialized. > SunOS 5.11 11.0 i86pc i386 i86pc > - gcc (GCC) 4.9.2 > + Couldn't link: > Undefined first referenced > symbol in file > __builtin_stdarg_start auxlily.o > > Here i do believe this is a gcc(1) installation issue? > Do you have any hints on how to circumvent that? I have never seen this issue. Best regards and keep up porting! ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu May 28 08:08:42 2015 From: buildfarm at lists.opencsw.org (=?utf-8?Q?Invierte_solo_=241200_pesos_por_44horas_de_capacitaci=C3=B3n=2E?= via buildfarm) Date: Thu, 28 May 2015 06:08:42 +0000 Subject: Desarrolla habilidades de mercadotecnia y ventas para tu empresa. Message-ID: Email Newsletter of this month. Esta informaci?n es importante para ti, si no la puedes ver da clic aqu? ( http://www.crecimiento.info/admin2 ) Desarrollo de Habilidades de Mercadotecnia para micro empresas. APROVECHA EL 90% DE SUBSIDIO DA CLIC AQU?. ( http://www.crecimiento.info/capacontacto ) El objetivo es desarrollar habilidades mercadol?gicas y de ventas en los participantes que les permitan incrementar las ventas de su empresa.. EL PROGRAMA INCLUYE ( http://www.crecimiento.info/capacontacto ) ? 44 horas de capacitaci?n. ? 12 horas de consultor?a grupal. COSTO DEL PROGRAMA ( http://www.crecimiento.info/capacontacto ) ? Costo total del programa: $12,000 Pesos. ? Subsidio gubernamental: 90% ? Costo para la micro empresa: $1,200 Pesos. Fecha de inicio: 11 de Junio. APROVECHA EL 90% DE SUBSIDIO DA CLIC AQU?. ( http://www.crecimiento.info/capacontacto ) CONTACTO Lic. Cora Dom?nguez Programas de Capacitaci?n y Consultor?a Coparmex N.L. Cel: 811-0505-945 informacion at capacitacion-pymes.com ( mailto:informacion at capacitacion-pymes.com ) DARSE DE BAJA/UNSUSCRIBE ( http://crecimiento.info/index.php?subid=387830&option=com_acymailing&ctrl=user&task=out&mailid=339&key=4ada690f5b112fd4c9afb2c214c19d1d ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Fri May 29 19:02:24 2015 From: buildfarm at lists.opencsw.org (Steffen Nurpmeso via buildfarm) Date: Fri, 29 May 2015 19:02:24 +0200 Subject: Solaris access for porting S-nail (a MUA)? In-Reply-To: References: <20150520111049.I4h2cWvvcrA1%sdaoden@yandex.com> <20150520133136.sNFLhREgKtGd%sdaoden@yandex.com> <88490234-0525-417B-BB4B-202A676D74CD@opencsw.org> <20150526185119.v-LmWG_el-m_%sdaoden@yandex.com> Message-ID: <20150529170224.bGG3q5yGiv8z%sdaoden@yandex.com> Hallo Dagobert, Dagobert Michelsen wrote: |> Am 26.05.2015 um 20:51 schrieb Steffen Nurpmeso : |> SunOS 5.11 11.0 i86pc i386 i86pc |> - gcc (GCC) 4.9.2 |> + Couldn't link: |> Undefined first referenced |> symbol in file |> __builtin_stdarg_start auxlily.o |> |> Here i do believe this is a gcc(1) installation issue? |> Do you have any hints on how to circumvent that? | |I have never seen this issue. Seems to be a (somewhat known) gcc / system header problem. I don't use autotools and never will, so all i can do is document that in case of such errors it may be necessary to do ADDCFLAGS=-D__builtin_stdarg_start=__builtin_va_start |Best regards and keep up porting! Yes, thank you. ?_? Ciao (and have a nice weekend)! --steffen