From schapht at gmail.com Tue Mar 4 17:00:50 2008 From: schapht at gmail.com (Mat Schaffer) Date: Tue, 4 Mar 2008 17:00:50 -0500 Subject: [Rubyinstaller-devel] Website redirect request Message-ID: Has anyone considered turning http://rubyinstaller.sourceforge.net/ into a server side redirect to http://rubyinstaller.rubyforge.org/ ? I've seen a lot of people google for "ruby windows" and accidentally end up confused and on rubyforge's home page after clicking that rubyforge link. If you change it to a 302 or meta redirect, google should bump the search results down for the old sourceforge page. It's still #1 from where I'm sitting: http://www.google.com/search?q=ruby+windows Thanks, Mat From luislavena at gmail.com Tue Mar 4 17:13:10 2008 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 4 Mar 2008 21:13:10 -0100 Subject: [Rubyinstaller-devel] Website redirect request In-Reply-To: References: Message-ID: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> On Tue, Mar 4, 2008 at 9:00 PM, Mat Schaffer wrote: > Has anyone considered turning http://rubyinstaller.sourceforge.net/ > into a server side redirect to http://rubyinstaller.rubyforge.org/ ? > > I've seen a lot of people google for "ruby windows" and accidentally > end up confused and on rubyforge's home page after clicking that > rubyforge link. If you change it to a 302 or meta redirect, google > should bump the search results down for the old sourceforge page. > > It's still #1 from where I'm sitting: > http://www.google.com/search?q=ruby+windows > Thank you Mat for the input. I don't know if that is possible (need to be admin also on SF and request SF team to do it), but the page clearly states that the project has been moved to rubyforge: "Ruby Installer For Windows The Ruby Installer for Windows project has moved to RubyForge. Please go to here." I don't see a lot of confusion when visiting the wiki page. In any case, a website is in the works, but still need a talented markup wizard ;-) Thank you and have a nice week. -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams From schapht at gmail.com Tue Mar 4 17:45:18 2008 From: schapht at gmail.com (Mat Schaffer) Date: Tue, 4 Mar 2008 17:45:18 -0500 Subject: [Rubyinstaller-devel] Website redirect request In-Reply-To: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> References: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> Message-ID: <26D0C209-2D52-47DB-99D4-FE4641647B45@gmail.com> On Mar 4, 2008, at 5:13 PM, Luis Lavena wrote: > I don't know if that is possible (need to be admin also on SF and > request SF team to do it), but the page clearly states that the > project has been moved to rubyforge: Anyone listed as an admin on the project should be able to add a meta- redirect. Curt Hubbs has all the permissions he needs assuming he still knows his sf.net password. > "Ruby Installer For Windows > The Ruby Installer for Windows project has moved to RubyForge. > > Please go to here." > > I don't see a lot of confusion when visiting the wiki page. You'd be surprised. At least 4/5 people I've had search for this themselves click on the "RubyForge" link and end up on the rubyforge homepage looking confused. Curt, I've attached an updated file to this email. Just scp it up to shell.sourceforge.net:/home/groups/r/ru/rubyinstaller/htdocs/ index.html and all should we well. Thanks, Mat From schapht at gmail.com Wed Mar 5 13:13:24 2008 From: schapht at gmail.com (Mat Schaffer) Date: Wed, 5 Mar 2008 13:13:24 -0500 Subject: [Rubyinstaller-devel] Website redirect request In-Reply-To: <26D0C209-2D52-47DB-99D4-FE4641647B45@gmail.com> References: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> <26D0C209-2D52-47DB-99D4-FE4641647B45@gmail.com> Message-ID: <291A7A8E-2398-4D3C-A451-FCA1E6FF803E@gmail.com> On Mar 4, 2008, at 5:45 PM, Mat Schaffer wrote: > Curt, I've attached an updated file to this email. Just scp it up > to shell.sourceforge.net:/home/groups/r/ru/rubyinstaller/htdocs/ > index.html and all should we well. With Curt's help I changed this to a 302 redirect. It looks like some of the sf.net servers still have it cached because I'm still seeing the old page sometimes. Other times is a clean redirect. Let's hope sf refreshes in a timely manner and google gets the hint :) Thanks all, Mat From luislavena at gmail.com Wed Mar 5 13:18:10 2008 From: luislavena at gmail.com (Luis Lavena) Date: Wed, 5 Mar 2008 16:18:10 -0200 Subject: [Rubyinstaller-devel] Website redirect request In-Reply-To: <291A7A8E-2398-4D3C-A451-FCA1E6FF803E@gmail.com> References: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> <26D0C209-2D52-47DB-99D4-FE4641647B45@gmail.com> <291A7A8E-2398-4D3C-A451-FCA1E6FF803E@gmail.com> Message-ID: <71166b3b0803051018w640726e6wd35a395df6bf190b@mail.gmail.com> On Wed, Mar 5, 2008 at 4:13 PM, Mat Schaffer wrote: > On Mar 4, 2008, at 5:45 PM, Mat Schaffer wrote: > > Curt, I've attached an updated file to this email. Just scp it up > > to shell.sourceforge.net:/home/groups/r/ru/rubyinstaller/htdocs/ > > index.html and all should we well. > > With Curt's help I changed this to a 302 redirect. It looks like some > of the sf.net servers still have it cached because I'm still seeing > the old page sometimes. Other times is a clean redirect. Let's hope > sf refreshes in a timely manner and google gets the hint :) > Thank you Mat, sorry wasn't more helpful :-) Have a nice week! -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams From schapht at gmail.com Wed Mar 5 13:46:54 2008 From: schapht at gmail.com (Mat Schaffer) Date: Wed, 5 Mar 2008 13:46:54 -0500 Subject: [Rubyinstaller-devel] Website redirect request In-Reply-To: <71166b3b0803051018w640726e6wd35a395df6bf190b@mail.gmail.com> References: <71166b3b0803041413q83f2fcoe18181f38cc77cd7@mail.gmail.com> <26D0C209-2D52-47DB-99D4-FE4641647B45@gmail.com> <291A7A8E-2398-4D3C-A451-FCA1E6FF803E@gmail.com> <71166b3b0803051018w640726e6wd35a395df6bf190b@mail.gmail.com> Message-ID: <0E8B1FE8-8D76-44A5-ABE7-0DD4F02FCC5D@gmail.com> On Mar 5, 2008, at 1:18 PM, Luis Lavena wrote: > Thank you Mat, sorry wasn't more helpful :-) > > Have a nice week! No worries. Thanks for being responsive! Hope you have a good week too. -Mat From hramrach at centrum.cz Fri Mar 21 14:49:00 2008 From: hramrach at centrum.cz (Michal Suchanek) Date: Fri, 21 Mar 2008 19:49:00 +0100 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: References: <47D728F3.9040907@gmail.com> <47D9704C.4000400@gmail.com> <165EF431-3AB9-497F-8AFB-6E506EEED5C4@gmail.com> <47DD54F3.7080503@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> Message-ID: On 21/03/2008, Luis Lavena wrote: > On Mar 20, 5:52 pm, Michal Suchanek wrote: > > > > Well, I consider myself sort of developer but I haven't used Rake so far. > > > > > I'm just used to do every repetitive task with Rake and I think other > developers will agree. There are also other alternatives like make, shell scripts, etc. And it does not help with the repetitiveness of the download that much as there are the timeouts. I do not quite understand how the stuff fits together but I suspect these are somewhere in the rake itself so perhaps rake needs a retry option for downloads. > > Anyway, I don't feel very happy with the layout I got for this > project, since the separated task for every dependency are over- > engineered :-P > > > > > > That's why the script would be helpful ;-) > > > > > Hmm, a script that just fire 'rake' don't sound too useful :-P > When that's the only thing needed there is no reason to write a script, yes ;-) > > > I do not get a download timeout or it is quite well obfuscated at > > least. I get slow download of packages one after another and then I > > get something like: > > > > execution timed out > > rake aborted > > > > > The error message you get can vary, that depends on the sourceforge > mirror you got. sorry about that. > > The idea is that you don't need to download the sources package again > unless you 'clobber' or nuke your downloads directory (rake clean will > only clean the sandbox) Good, but if you unpack a fresh copy of the installer the downloads aren't there unless you save them and put them into the fresh copy manually. > > > > > > I installed the OCI but did not do anything to put the ruby bin > > directory into my path, and the installer did not do it either. There > > must be a zlib1.dll somewhere in your system but there's none in mine. > > It is quite common so it might be installed by some other software. > > > > > If the installer didn't add Ruby\bin into the PATH then you're running > without administrative privileges or something like that. > > I just added a README.txt file that roughly indicates zlib1.dll as > requirement. I still think it would be overall easier to just put a copy of zlib1.dll into the extract_tools folder. > > > > Yes, I tried some tasks until I was sure there's nothing that does not > > produce any error but it might be that executing the tasks out of > > order leaves some fallout. > > > > > To make you happy: the Rakefile now have a defaults (recipes/ > defaults.rake) that: > > download, > extract, > prepare, > configure, > compile and > install Very nice, now running rake gives me a ruby build :-) However, it would be nice if this copy also included rubygems and/or rake so that rebuilding with this copy new was easier. To rebuild I had to - download rubygems - run the extract process of the installer so that I got bsdtar - extract rubygems - in rubygems run setup.rb configure (this for some reason performed the installation already) - run gem install rake After this I could nuke the install3 folder, extract a new one, and build ruby with the newly installed ruby. Thanks Michal From luislavena at gmail.com Fri Mar 21 18:04:10 2008 From: luislavena at gmail.com (Luis Lavena) Date: Fri, 21 Mar 2008 19:04:10 -0300 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: References: <47D728F3.9040907@gmail.com> <47D9704C.4000400@gmail.com> <165EF431-3AB9-497F-8AFB-6E506EEED5C4@gmail.com> <47DD54F3.7080503@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> Message-ID: <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> Welcome Michal! On Fri, Mar 21, 2008 at 3:49 PM, Michal Suchanek wrote: > On 21/03/2008, Luis Lavena wrote: > > On Mar 20, 5:52 pm, Michal Suchanek wrote: > > > > > > Well, I consider myself sort of developer but I haven't used Rake so far. > > > > > > > > > I'm just used to do every repetitive task with Rake and I think other > > developers will agree. > > There are also other alternatives like make, shell scripts, etc. > > And it does not help with the repetitiveness of the download that much > as there are the timeouts. I do not quite understand how the stuff > fits together but I suspect these are somewhere in the rake itself so > perhaps rake needs a retry option for downloads. > Well, the ideas, as I said: use the most ruby you could possible use, that means use Ruby to build ruby :-) There is no shell script that could perform what are we doing right now without external tools for download and unpack (yes, Is a bummer have zlib1.dll around, will try to fix this weekend). If you have used the garbagagecollect builds for your "Yet another Ruby Installer for Windows", then you know there is no documentation or way to recreate the process locally, and thus there is no way to simple fix the problems the current Ruby for Windows faces. Then you're stuck each time to the releases made by somebody else and reply lots of tickets and support request when things don't work out of the box, like WIN32OLE in 1.8.6-p110 (which was replaced soon enough by p111)... I think you get the picture. Instead of gargabecollect release, I'm not using Visual C as compiler, since is not available anymore, and couldn't be freely obtained like MinGW (there is also the lack of good speed we got from MinGW build). This compilation of recipes try to get MinGW+MSYS tools to fully build Ruby without you prior requiring nothing more than a working Ruby installation. So there is no manual setup of MinGW or something similar. > > > I do not get a download timeout or it is quite well obfuscated at > > > least. I get slow download of packages one after another and then I > > > get something like: > > > > > > execution timed out > > > rake aborted > > > > > > > > > The error message you get can vary, that depends on the sourceforge > > mirror you got. sorry about that. > > > > The idea is that you don't need to download the sources package again > > unless you 'clobber' or nuke your downloads directory (rake clean will > > only clean the sandbox) > > Good, but if you unpack a fresh copy of the installer the downloads > aren't there unless you save them and put them into the fresh copy > manually. > Hmm, don't understand what are you saying, let me explain how I designed this in the first place. 1) after you unpack latest.zip (I actually name the folder installer3.dev, anyway) you jump in and perform the 'rake download' task. This is the first and only time you require to do so, since that task will download all the zip, tar.bz and tar.gz files to build a clean ruby each time, unless you update some of the required files (version updates or security fixes, etc). 2) since you start with a clean checkout of the installer, you proceed to "extract" and "prepare", which will create the required directories in sandbox and unpack all the tools. Then it arrange (prepare) some of the files and dlls to proceed with the next step. This is required every time you "clean" your sandbox (that means when you change something in the recipes and want to do a fresh start). 3) configure task actually run the GNU autoconf script that is bundled with ruby, and generate the proper config file and the makefile required by the compile task. 4) compile will try (at this time) to build ruby with the bindings that extract and prepare made available, at this time, only "zlib" and "readline" are in place. 5) Install task emulates the directory structure the garbage collect distribution have (is a ruby installation). The idea is later in the process rubygems gets installed over there, but there are no recipes for it right now. 6) check task will ensure that everything built in the compile task works out of the box. It runs the ruby test units to garantee that. Since readline is failing, I didn't proceed to work on the MSI installer generators or the RubyGems installation. > > I still think it would be overall easier to just put a copy of > zlib1.dll into the extract_tools folder. > Is a bad practice add binaries to your repository... doing that you're forced to keep it updated from release to release... I'll fix the extract utils to expand the downloaded zlib package. > > > > > > > Yes, I tried some tasks until I was sure there's nothing that does not > > > produce any error but it might be that executing the tasks out of > > > order leaves some fallout. > > > > > > > > > To make you happy: the Rakefile now have a defaults (recipes/ > > defaults.rake) that: > > > > download, > > extract, > > prepare, > > configure, > > compile and > > install > > Very nice, now running rake gives me a ruby build :-) > > However, it would be nice if this copy also included rubygems and/or > rake so that rebuilding with this copy new was easier. To rebuild I > had to > > - download rubygems > - run the extract process of the installer so that I got bsdtar > - extract rubygems > - in rubygems run setup.rb configure (this for some reason performed > the installation already) > - run gem install rake > As explain above, RubyGems is not my main focus right now, but get a stable working ruby build instead (there are lot of extensions don't build right now, like iconv, curses and others). However, if you want it included right now, I think a rubygems recipe can be added to dependencies, and download, extract and install tasks too. > After this I could nuke the install3 folder, extract a new one, and > build ruby with the newly installed ruby. > That's part of the idea, but how you nuke installer3? just use rake clean to erase the sandbox, don't stress the servers doing several downloads (clean will not remove the downloads, clobber or a new checkout will). > Thanks Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From hramrach at centrum.cz Sat Mar 22 05:33:21 2008 From: hramrach at centrum.cz (Michal Suchanek) Date: Sat, 22 Mar 2008 10:33:21 +0100 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> References: <47D728F3.9040907@gmail.com> <165EF431-3AB9-497F-8AFB-6E506EEED5C4@gmail.com> <47DD54F3.7080503@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> Message-ID: On 21/03/2008, Luis Lavena wrote: > Welcome Michal! > > > On Fri, Mar 21, 2008 at 3:49 PM, Michal Suchanek wrote: > > On 21/03/2008, Luis Lavena wrote: > > > On Mar 20, 5:52 pm, Michal Suchanek wrote: > > > > > > > > Well, I consider myself sort of developer but I haven't used Rake so far. > > > > > > > > > > > > > I'm just used to do every repetitive task with Rake and I think other > > > developers will agree. > > > > There are also other alternatives like make, shell scripts, etc. > > > > And it does not help with the repetitiveness of the download that much > > as there are the timeouts. I do not quite understand how the stuff > > fits together but I suspect these are somewhere in the rake itself so > > perhaps rake needs a retry option for downloads. > > > > > Well, the ideas, as I said: use the most ruby you could possible use, > that means use Ruby to build ruby :-) > > There is no shell script that could perform what are we doing right > now without external tools for download and unpack (yes, Is a bummer > have zlib1.dll around, will try to fix this weekend). I am not arguing against Rake, I am just saying that there are other tools that could do the job, and thus there are people who aren't familiar with Rake. > > If you have used the garbagagecollect builds for your "Yet another > Ruby Installer for Windows", then you know there is no documentation > or way to recreate the process locally, and thus there is no way to > simple fix the problems the current Ruby for Windows faces. > > Then you're stuck each time to the releases made by somebody else and > reply lots of tickets and support request when things don't work out > of the box, like WIN32OLE in 1.8.6-p110 (which was replaced soon > enough by p111)... I think you get the picture. Yes, I have seen the earlier discussions about installers. It's actually not mine "yet another installer", I was just replying to the thread. And I am aware of the grief with binary-only releases :-/ > > Instead of gargabecollect release, I'm not using Visual C as compiler, > since is not available anymore, and couldn't be freely obtained like > MinGW (there is also the lack of good speed we got from MinGW build). > > This compilation of recipes try to get MinGW+MSYS tools to fully build > Ruby without you prior requiring nothing more than a working Ruby > installation. So there is no manual setup of MinGW or something > similar. > Yes, this is very nice. The better automation you get the more likely people are going to use the scripts and possibly find or even fix problems. > > > > > I do not get a download timeout or it is quite well obfuscated at > > > > least. I get slow download of packages one after another and then I > > > > get something like: > > > > > > > > execution timed out > > > > rake aborted > > > > > > > > > > > > > The error message you get can vary, that depends on the sourceforge > > > mirror you got. sorry about that. > > > > > > The idea is that you don't need to download the sources package again > > > unless you 'clobber' or nuke your downloads directory (rake clean will > > > only clean the sandbox) > > > > Good, but if you unpack a fresh copy of the installer the downloads > > aren't there unless you save them and put them into the fresh copy > > manually. > > > > > Hmm, don't understand what are you saying, let me explain how I > designed this in the first place. > > 1) after you unpack latest.zip (I actually name the folder > installer3.dev, anyway) you jump in and perform the 'rake download' > task. Well, the zip archives contain an installer3 folder ... > > This is the first and only time you require to do so, since that task > will download all the zip, tar.bz and tar.gz files to build a clean > ruby each time, unless you update some of the required files (version > updates or security fixes, etc). > > 2) since you start with a clean checkout of the installer, you proceed > to "extract" and "prepare", which will create the required directories > in sandbox and unpack all the tools. Then it arrange (prepare) some of > the files and dlls to proceed with the next step. > > This is required every time you "clean" your sandbox (that means when > you change something in the recipes and want to do a fresh start). > > 3) configure task actually run the GNU autoconf script that is bundled > with ruby, and generate the proper config file and the makefile > required by the compile task. > > 4) compile will try (at this time) to build ruby with the bindings > that extract and prepare made available, at this time, only "zlib" and > "readline" are in place. > > 5) Install task emulates the directory structure the garbage collect > distribution have (is a ruby installation). > > The idea is later in the process rubygems gets installed over there, > but there are no recipes for it right now. > > 6) check task will ensure that everything built in the compile task > works out of the box. It runs the ruby test units to garantee that. > > Since readline is failing, I didn't proceed to work on the MSI > installer generators or the RubyGems installation. > 7) and then I download a new latest.zip, and since I am not sure nothing was removed between the different version the only safe way is to start with a fresh copy of the installer3 folder. BTW stuff breaks if the path to installer3 contains a space, this could be mentioned in README it it is not already. > > > > > I still think it would be overall easier to just put a copy of > > zlib1.dll into the extract_tools folder. > > > > > Is a bad practice add binaries to your repository... doing that you're > forced to keep it updated from release to release... > > I'll fix the extract utils to expand the downloaded zlib package. Yes, that's what I had in mind. There's even a separate download for zlib1.dll only. > > > > > > > > > > > > Yes, I tried some tasks until I was sure there's nothing that does not > > > > produce any error but it might be that executing the tasks out of > > > > order leaves some fallout. > > > > > > > > > > > > > To make you happy: the Rakefile now have a defaults (recipes/ > > > defaults.rake) that: > > > > > > download, > > > extract, > > > prepare, > > > configure, > > > compile and > > > install > > > > Very nice, now running rake gives me a ruby build :-) > > > > However, it would be nice if this copy also included rubygems and/or > > rake so that rebuilding with this copy new was easier. To rebuild I > > had to > > > > - download rubygems > > - run the extract process of the installer so that I got bsdtar > > - extract rubygems > > - in rubygems run setup.rb configure (this for some reason performed > > the installation already) > > - run gem install rake > > > > > As explain above, RubyGems is not my main focus right now, but get a > stable working ruby build instead (there are lot of extensions don't > build right now, like iconv, curses and others). > > However, if you want it included right now, I think a rubygems recipe > can be added to dependencies, and download, extract and install tasks > too. I guess it is time to add it because with rubygems and rake added you have enough to rebuild ruby with the image that is built by the recipes. Also you could release the image as .zip and somebody would perhaps try it out and test their favourite gems. I guess iconv and openssl are important but curses are broken anyway. Actually they might work on some language versions of Windows that do not (and cannot) use multibyte characters but then you have the additional problem of finding out the encoding that's currently in use. > > > > After this I could nuke the install3 folder, extract a new one, and > > build ruby with the newly installed ruby. > > > > > That's part of the idea, but how you nuke installer3? just use rake > clean to erase the sandbox, don't stress the servers doing several > downloads (clean will not remove the downloads, clobber or a new > checkout will). But how do you update the scripts then? Thanks Michal From luislavena at gmail.com Sat Mar 22 10:05:36 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 22 Mar 2008 11:05:36 -0300 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: References: <47D728F3.9040907@gmail.com> <47DD54F3.7080503@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> Message-ID: <71166b3b0803220705w6782bd1cld8afdfe3254f9669@mail.gmail.com> On Sat, Mar 22, 2008 at 6:33 AM, Michal Suchanek wrote: > On 21/03/2008, Luis Lavena wrote: > > > > That's part of the idea, but how you nuke installer3? just use rake > > clean to erase the sandbox, don't stress the servers doing several > > downloads (clean will not remove the downloads, clobber or a new > > checkout will). > > But how do you update the scripts then? > It is part of a bazaar [0] repository. (bzr) is a distributed revision software similar to git or mercurial, but offer a more flexible workflow than these two and also has Windows as supported platform :-) If you don't have Python installed, you can grab bazaar standalone setup [1] and add it to your PATH, bzr commands are quite similar to those from subversion, but just to get you started: 0) bzr whoami "your name " This is required to identify yourself on each commit :-D 1) bzr branch http://code.mmediasys.com/installer3/dev installer3.dev Doing that you will grab a copy of the current repository (dev branch) of installer3. 2) bzr update (inside installer3.dev) to get latest changes 3) (outside installer3.dev) bzr branch installer3.dev my-feature-or-fix-branch This will create a new branch (locally) that will let you fix, enhance and commit your enhancements without requiring write access to dev branch 4) when you have something to contribute back (until I set a better repository) just generate a bundle patch with: bzr send my-feature-or-fix-branch installer3.dev -o my-first-bundle.bundle Then you attach it to your mail and send it to the list :-) I'll reply your other comments right now :-) Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From luislavena at gmail.com Sat Mar 22 10:57:33 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 22 Mar 2008 11:57:33 -0300 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: <71166b3b0803220705w6782bd1cld8afdfe3254f9669@mail.gmail.com> References: <47D728F3.9040907@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> <71166b3b0803220705w6782bd1cld8afdfe3254f9669@mail.gmail.com> Message-ID: <71166b3b0803220757x5d2f4359t6089822d66dc34c1@mail.gmail.com> On Sat, Mar 22, 2008 at 11:05 AM, Luis Lavena wrote: Forgot to provide the links! :-P [0] http://bazaar-vcs.org/ [1] http://bazaar-vcs.org/WindowsDownloads -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From luislavena at gmail.com Sat Mar 22 11:16:59 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 22 Mar 2008 12:16:59 -0300 Subject: [Rubyinstaller-devel] Yet another Windows installer In-Reply-To: References: <47D728F3.9040907@gmail.com> <47DD54F3.7080503@gmail.com> <1440f190-0b73-4e74-bb52-cf62d4984d1b@59g2000hsb.googlegroups.com> <71166b3b0803211504w23e88b9bn233733bdc5b7155a@mail.gmail.com> Message-ID: <71166b3b0803220816g5b4d4624lf57ea3b74779b7fe@mail.gmail.com> On Sat, Mar 22, 2008 at 6:33 AM, Michal Suchanek wrote: > > I am not arguing against Rake, I am just saying that there are other > tools that could do the job, and thus there are people who aren't > familiar with Rake. > Don't take my comments personal. I self learned english and sometimes what I express in words are not actually 100% accurate on what I think it should express :-) I had used in the past a series of batch files to perform this, and if you take a closer look of the current code in installer2 in the rubyforge repository, you will see Curt and Andy already used something similar to bootstrap building One Click Installer By "people" I meant other Ruby developers, working on Windows, willing to collaborate in the project. The end-user of the project wouldn't care about all the effort of download MinGW or build everything from scratch, they will only use the generated output (the MSI installer). > > > > > If you have used the garbagagecollect builds for your "Yet another > > Ruby Installer for Windows", then you know there is no documentation > > or way to recreate the process locally, and thus there is no way to > > simple fix the problems the current Ruby for Windows faces. > > > > Then you're stuck each time to the releases made by somebody else and > > reply lots of tickets and support request when things don't work out > > of the box, like WIN32OLE in 1.8.6-p110 (which was replaced soon > > enough by p111)... I think you get the picture. > > Yes, I have seen the earlier discussions about installers. It's > actually not mine "yet another installer", I was just replying to the > thread. And I am aware of the grief with binary-only releases :-/ > Sorry about that, got lost in the translation :-P The dependency on external and non directly related developers to release fixes is a no-no. As example, take Mongrel project. I shared the most as possible of my Windows environment setup with the other Mongrel developers, so they don't need me to be around when a bug/security fix show up. Right now, we depend 110% on garbagecollect releases, but the few times I politely asked the developers for his scripts (to recreate the build environment locally) he didn't replied back. So I ended creating, from scratch again, the build scripts for VC6 and VC8 at that time, just to found it too complicated and decided to go for a Pure Ruby alternative :-) > > > > 1) after you unpack latest.zip (I actually name the folder > > installer3.dev, anyway) you jump in and perform the 'rake download' > > task. > > Well, the zip archives contain an installer3 folder ... > Oh yes, the zip files contains installer3 folder, I meant the Bazaar branch :-) > > 7) and then I download a new latest.zip, and since I am not sure > nothing was removed between the different version the only safe way is > to start with a fresh copy of the installer3 folder. > That will end download *everything* again... please don't do that... a huge hit to SF server is not polite :-( > BTW stuff breaks if the path to installer3 contains a space, this > could be mentioned in README it it is not already. Hehehe, I just get used to not use spaces in my path that forgot about it. I'll rewrite README for better reading of requirements and limitations. > > > > I'll fix the extract utils to expand the downloaded zlib package. > > Yes, that's what I had in mind. There's even a separate download for > zlib1.dll only. > We already have it, the download is zlib123-dll.zip I'll patch the extract utils in the following minutes. > > I guess it is time to add it because with rubygems and rake added you > have enough to rebuild ruby with the image that is built by the > recipes. You're correct, maybe I'll do that before putting all the pending dependencies in place :-P > Also you could release the image as .zip and somebody would perhaps > try it out and test their favourite gems. > I'm still concerned by readline test being broken and that this generates IRB uses 50% of the processor being idle! (yes, that is a huge bug that need to be backported to 1.8 from trunk branch of ruby). > I guess iconv and openssl are important but curses are broken anyway. > Actually they might work on some language versions of Windows that do > not (and cannot) use multibyte characters but then you have the > additional problem of finding out the encoding that's currently in > use. > We need to determine what built-in extensions are really used. OpenSSL is a must since signed gems (like Mongrel) will not work without it. for Iconv I think will follow the suggestions from _why and use the win32 alternative, the gnuwin32 packages for these tools are older and unmaintained :-( Thank you for your feedback Michal! I really appreciate it and it give me a push to fix these things! :-) Regards and have a nice weekend! -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From luislavena at gmail.com Mon Mar 24 00:55:05 2008 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 24 Mar 2008 01:55:05 -0300 Subject: [Rubyinstaller-devel] [ANN] Bootstrapping Ruby with MinGW: selfhosted and test sandbox! Message-ID: <71166b3b0803232155h12f3c588la1b89497f4edd30d@mail.gmail.com> Hello List, I'm happy to announce that huge progress (hack-a-ton) was made this weekend to bring a new implementation of One-Click Installer for Windows! This test version is based on the rake recipes I commented on previous posts [1], and it download MinGW, MSYS and some Ruby dependencies to get a working Ruby implementation using MinGW (i386-mingw32 platform). I've packaged Ruby 1.8.6 (revision 15830) as 7zip package (2.7MB). You can download it form the following URL: http://dump.mmediasys.com/installer3/ The project and the recipes code can be downloaded from here: http://code.mmediasys.com/installer3/latest.zip I'll like to point a few things before everyone start using this ruby version: THIS BUILD OF RUBY IS *NOT* READY FOR PRODUCTION. USE IT ONLY FOR TESTING PURPOSES. All the enhancements got here will be injected back in the new version of One-Click Installer for Windows. Caveats: 1) Pre-built gems for i386-mswin32 are not compatible with this build of ruby. You'll require to download sources of your favorite gems. If you haven't created the sandbox environment using the recipes, you can grab the baked mingw+msys sandbox from installer3 URL. You need to put MinGW binaries and MSYS binaries in the PATH (in that order) before firing the gem install or any build procedure. 2) Don't expect Rails, Mongrel, Merb, Sqlite3 or "name your favorite gem" will work with this release out of the box (hey, this is not even a release!). 3) The package contains the bare minimum stuff to serve as self hosting environment: Ruby 1.8.6 Zlib 1.2.3 OpenSSL 0.9.7c Readline 5.2 Iconv alternative RubyGems 1.0.1 Nothing more, nothing less. 4) Readline is still broken. I removed the readline tests from the check procedure to continue working on this (was stuck for two months without feedback). If you wanna help, search for my previous posts about this issue. For CI information: 1760 tests, 1343436 assertions, 2 failures, 0 errors 5) GNU Utils are a nightmare to get it working or find proper builds for Windows. following _why advice [2], opted for win_iconv which seems working (but there aren't tests for it). 6) Microsoft Installer (MSI) recipes are still missing. Future releases will be use WiX tools and will provide patches between releases. 7) Contributions are highly welcome! I'm using Bazaar as VCS since Windows support for Git (the new cool tool) is still behind... Remember: everything shown here will became part of the next One-Click Installer. As you can see, I'm trying to keep it to the minimum. Later we can discuss "addons" or different versions that are target different usage scenarios. Check my blog [2] for upcoming hack-a-ton dates and keep an eye on #ruby-lang if you wanna help ;-) Regards and everybody have a nice week! [1] http://groups.google.com/group/ruby-talk-google/browse_thread/thread/1e2f1b9a3d611e3b/ [2] http://blog.mmediasys.com -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From joe.swatosh at gmail.com Mon Mar 24 22:59:18 2008 From: joe.swatosh at gmail.com (Joe Swatosh) Date: Mon, 24 Mar 2008 19:59:18 -0700 Subject: [Rubyinstaller-devel] [ANN] Bootstrapping Ruby with MinGW: selfhosted and test sandbox! In-Reply-To: <71166b3b0803232155h12f3c588la1b89497f4edd30d@mail.gmail.com> References: <71166b3b0803232155h12f3c588la1b89497f4edd30d@mail.gmail.com> Message-ID: Hi Luis! On Sun, Mar 23, 2008 at 9:55 PM, Luis Lavena wrote: > Hello List, > > I'm happy to announce that huge progress (hack-a-ton) was made this > weekend to bring a new implementation of One-Click Installer for > Windows! Great news! > > This test version is based on the rake recipes I commented on previous > posts [1], and it download MinGW, MSYS and some Ruby dependencies to > get a working Ruby implementation using MinGW (i386-mingw32 platform). > > > Caveats: > > 1) Pre-built gems for i386-mswin32 are not compatible with this build > of ruby. You'll require to download sources of your favorite gems. Ouch. I misunderstood that MinGW used the same run-time as vc6. > > If you haven't created the sandbox environment using the recipes, you > can grab the baked mingw+msys sandbox from installer3 URL. You need to I just want to add my "good job" here as someone who appreciates what you're doing, but has been too quiet about it (and too busy to contribute). -- Joe From luislavena at gmail.com Mon Mar 24 23:32:58 2008 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 25 Mar 2008 00:32:58 -0300 Subject: [Rubyinstaller-devel] [ANN] Bootstrapping Ruby with MinGW: selfhosted and test sandbox! In-Reply-To: References: <71166b3b0803232155h12f3c588la1b89497f4edd30d@mail.gmail.com> Message-ID: <71166b3b0803242032r410bebdm55d015f59a0ccd2f@mail.gmail.com> On Mon, Mar 24, 2008 at 11:59 PM, Joe Swatosh wrote: > Hi Luis! > Hey there Joe ;-) > > On Sun, Mar 23, 2008 at 9:55 PM, Luis Lavena wrote: > > > Caveats: > > > > 1) Pre-built gems for i386-mswin32 are not compatible with this build > > of ruby. You'll require to download sources of your favorite gems. > > Ouch. I misunderstood that MinGW used the same run-time as vc6. > Both link to MSVCRT runtime DLL version, but the platforms signatures (or the 'arch' used by ruby to identify them) differs. So i386-mswin32 gems will not be valid 'as gems' for i386-mingw32 Also, I found there are a few issues between the generated msvcrt-ruby18.dll by MinGW and extensions compiled with VC6, even both link to the same DLL and the same CRT, sometimes they crash. I can point to issues under C and low level stuff down there that differ between implementation. In any case, I set as next step configure a CI for some of the OSS project that will be "supported" by me, like Mongrel and others which right now provide better support for Windows than others. Ruby developers willing to bring Windows love to their projects are welcome to mail me and request some slice into the CI system we (my company) have. > > I just want to add my "good job" here as someone who appreciates what > you're doing, but has been too quiet about it (and too busy to > contribute). > Thank you, I really appreciate the kind words and the encourage a few users sent me directly :-) It's been difficult times and the task is not easy, and still lot of work need to be done, but I think we are in the right path. Regards and have a nice week! -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From luislavena at gmail.com Sat Mar 29 15:52:38 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 29 Mar 2008 16:52:38 -0300 Subject: [Rubyinstaller-devel] Collecting list of gems and projects Message-ID: <71166b3b0803291252k68364f98g97a2d1896dc548f9@mail.gmail.com> Hello fellow developers, It seems the post at RubyInside [1] generated quite a reaction, rest assured that One-Click Installer will not be dead, but we should shake the ground and put new blood in it. For that job, the move to MinGW was the best looking alternative I found. Even after the negative comments and the lack of feedback and general troubleshooting from the community, we moved forward. What's our plan? (you may ask). Right now the idea is play with the generated sandboxed ruby (from now own installer3 ruby) and find something that wouldn't work. Since there aren't too many things out there that will work out of the box. Tip: For those who don't know where to get the sandbox, look here [2] Our list of priorities: - Move the work being done in the Bazaar repository to Subversion I know bzr is not spread like git among developers, but is not so complex to use. In any case, I'll push updates into rubyinstaller svn repository and allow integration from it, so developers familiar with subversion can work with us :-D - Provide a simple One-Click Installer "Developer Kit" This is almost done, since you can right now grab the generated sandboxed MinGW and MSYS installation (using the installer3 recipes), add it to your PATH and you're done. What it misses right now is a proper Windows Installer and the creation of some shortcuts for the standard console and other to start the MSYS (Bash) console. This will make it more easy for developers and users to install and use gems that requires a compiler and that will not be "prepared" for MinGW. Read the next point about this. - Improve compatibility of existing gems. Ruby on Windows definition is shared among three platforms (RUBY_PLATFORMS), i386-mswin32 (VC), i386-mingw32 (MinGW) and last, but not least i386-cygwin. The later ships with is own compiler, so mixing environments with that will only make your head hurts. Regarding the other two platforms, a lot of projects uses regexp (regular expressions) to determine "if you are running on Windows". Some of them only consider 'win32', which will leave mingw32 and even x64 version of Ruby out of the equation. I even see others that look for 'win' and mark it as Windows... wrong! Ruby for OSX also fall into this category (darwin?). So, since I can't work on projects I don't use on a daily basis, I encourage everybody list the gems and extensions that cannot run out of the box with the tools provided by the Developer Kit and the Installer3 Ruby. I'll try to add them to our CI and provide the patches needed to fix most of the situations with them, but will require also original developers merge them and start providing releases for it. So, where we are right now. RubyGems 1.1.0 is out, which is compatible with this new Installer3 Ruby. I've in my list, ordered by priority: Mongrel sqlite3-ruby mysql win32console rspec Please share with me your gems that don't work out of the box either because there is no pre-compiled gem (and it requires special libraries) or because it looks wrongly for the RUBY_PLATFORM. Just open a Integration Request (Support and Continuous Integration Requests) tracker at RubyForge [3], provide project name, repository url, category of usage (ui, console, database, testing, etc.) and comments regarding your problems with it. Thanks everybody for your support, your mails and your comments either in RubyInside, directly to my inbox, IM or IRC. [1] http://www.rubyinside.com/is-windows-a-first-class-platform-for-ruby-823.html [2] http://groups.google.com/group/comp.lang.ruby/browse_frm/thread/1e2f1b9a3d611e3b?tvc=1 [3] http://rubyforge.org/tracker/?atid=22895&group_id=167&func=browse Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From gthiesfeld at gmail.com Sat Mar 29 18:17:41 2008 From: gthiesfeld at gmail.com (Gordon Thiesfeld) Date: Sat, 29 Mar 2008 17:17:41 -0500 Subject: [Rubyinstaller-devel] Collecting list of gems and projects In-Reply-To: <71166b3b0803291252k68364f98g97a2d1896dc548f9@mail.gmail.com> References: <71166b3b0803291252k68364f98g97a2d1896dc548f9@mail.gmail.com> Message-ID: Luis, I'm really glad to see this is gaining momentum. As far as gems go, I think Hoe would be a good candidate to work on. I tested it, and it has some problems. I think all it needs is a fix to the regex in a few places. I'll take a closer look soon. I was able to compile, package and install the win32console gem into my sandbox. From some early tests, it seems to work just fine. I don't have time tonight, but if you're interested, I'll put some notes together on what I did. I also have some questions about rake tasks, and maybe some ideas about new ones. I want to be able to clobber the sandbox, without clobbering the downloads. Is this currently possible? If not, how about splitting these into two tasks? Something like this (pseudocode): namespace(:clobber) do namespace(:sandbox) do #clobber sandbox end namespace(:downloads) do #clobber sandbox end end task :clobber => ['clobber:sandbox', 'clobber:downloads'] Thanks, Gordon From luislavena at gmail.com Sat Mar 29 18:25:59 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 29 Mar 2008 19:25:59 -0300 Subject: [Rubyinstaller-devel] Collecting list of gems and projects In-Reply-To: References: <71166b3b0803291252k68364f98g97a2d1896dc548f9@mail.gmail.com> Message-ID: <71166b3b0803291525r16a8b055uf02b975a0f213db3@mail.gmail.com> On Sat, Mar 29, 2008 at 7:17 PM, Gordon Thiesfeld wrote: > Luis, > > I'm really glad to see this is gaining momentum. > > As far as gems go, I think Hoe would be a good candidate to work on. > I tested it, and it has some problems. I think all it needs is a fix > to the regex in a few places. I'll take a closer look soon. I was > able to compile, package and install the win32console gem into my > sandbox. From some early tests, it seems to work just fine. I don't > have time tonight, but if you're interested, I'll put some notes > together on what I did. > Hehehe, I was the responsible for the Hoe patches, so blame me :-P I didn't listed Hoe or RubyInline (and ParseTree) --- yet :-) > I also have some questions about rake tasks, and maybe some ideas > about new ones. I want to be able to clobber the sandbox, without > clobbering the downloads. Is this currently possible? If not, how > about splitting these into two tasks? Something like this > (pseudocode): > yes: rake clean that will "clean" your sandbox and let you be ready to extract, prepare, configure and compile! ;-) clobber will just wip your downloads folder :-D > > Thanks, > No problem, is good to have "echo" to my messages :-D Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From will at hotgazpacho.org Sat Mar 29 18:45:01 2008 From: will at hotgazpacho.org (Will Green) Date: Sat, 29 Mar 2008 18:45:01 -0400 Subject: [Rubyinstaller-devel] rake fails Message-ID: <47EEC66D.40704@hotgazpacho.org> So, I downloaded the latest.zip file, extracted it, opened a command prompt in the directory and ran rake. Several minutes later, the compile/install of ruby failed. I think it has something to do with my RUBYOPT (which is now set to -rubygems) environment variable. Here's the relevant output: make[1]: Leaving directory `/c/Share/installer3/sandbox/ruby_build' "C:/Share/installer3/sandbox/msys/bin/bash.exe" --login -i -c "make install" ./miniruby.exe ../ruby_1_8/instruby.rb --dest-dir="" --extout=".ext" --make="make" --mflags="- --un ix" --make-flags=" --unix" --installed-list .installed.list --mantype="man" installing binary commands installing command scripts installing library scripts installing headers installing manpages installing extension objects installing extension scripts ruby setup.rb install --no-ri --no-rdoc ruby: no such file to load -- ubygems (LoadError) rake aborted! Command failed with status (1): [ruby setup.rb install --no-ri --no-rdoc...] (See full trace by running task with --trace) == Will Green From luislavena at gmail.com Sun Mar 30 06:27:51 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sun, 30 Mar 2008 07:27:51 -0300 Subject: [Rubyinstaller-devel] rake fails In-Reply-To: <47EEC66D.40704@hotgazpacho.org> References: <47EEC66D.40704@hotgazpacho.org> Message-ID: <71166b3b0803300327ha6c763eoec5e8d9ddd5f781@mail.gmail.com> On Sat, Mar 29, 2008 at 7:45 PM, Will Green wrote: > So, I downloaded the latest.zip file, extracted it, opened a command > prompt in the directory and ran rake. > > Several minutes later, the compile/install of ruby failed. I think it > has something to do with my RUBYOPT (which is now set to -rubygems) > environment variable. Here's the relevant output: > > make[1]: Leaving directory `/c/Share/installer3/sandbox/ruby_build' > "C:/Share/installer3/sandbox/msys/bin/bash.exe" --login -i -c "make install" > ./miniruby.exe ../ruby_1_8/instruby.rb --dest-dir="" --extout=".ext" > --make="make" --mflags="- --un > ix" --make-flags=" --unix" --installed-list .installed.list --mantype="man" > installing binary commands > installing command scripts > installing library scripts > installing headers > installing manpages > installing extension objects > installing extension scripts > ruby setup.rb install --no-ri --no-rdoc > ruby: no such file to load -- ubygems (LoadError) > rake aborted! > Command failed with status (1): [ruby setup.rb install --no-ri --no-rdoc...] > > (See full trace by running task with --trace) > > Thank you Will. We need to blame RubyGems for this. I'm checking it right now, but that change will not be available until next official release :-( Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From luislavena at gmail.com Sun Mar 30 06:51:19 2008 From: luislavena at gmail.com (Luis Lavena) Date: Sun, 30 Mar 2008 07:51:19 -0300 Subject: [Rubyinstaller-devel] rake fails In-Reply-To: <71166b3b0803300327ha6c763eoec5e8d9ddd5f781@mail.gmail.com> References: <47EEC66D.40704@hotgazpacho.org> <71166b3b0803300327ha6c763eoec5e8d9ddd5f781@mail.gmail.com> Message-ID: <71166b3b0803300351m23a7675ey447dd08456c4e686@mail.gmail.com> On Sun, Mar 30, 2008 at 7:27 AM, Luis Lavena wrote: > > Thank you Will. > > We need to blame RubyGems for this. > Ok, I just fixed this in Installer3 codebase. RubyGems installation now includes empty RUBYOPT to avoid loading of existing rubygems and thus, halting the install procedure. > I'm checking it right now, but that change will not be available until > next official release :-( I can't replicate the direct behavior since we are "shelling" two levels deep, so normal installation of RubyGems via command line do not raises this :-( Anyway, just solved it ;-) Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From builder at mmediasys.com Sun Mar 30 14:03:27 2008 From: builder at mmediasys.com (builder at mmediasys.com) Date: Sun, 30 Mar 2008 15:03:27 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-trunk-mswin32 build 996 failed Message-ID: <47efd5ef6ab08_c4813de3a61a6@KEORE.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- This is the first build BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" rake aborted! Could not find RubyGem echoe (>= 2.7.5) D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work/rakefile:3 (See full trace by running task with --trace) (in D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work) dir : D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/build-996/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-trunk-mswin32\build-996\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test' project.scheduler.polling_interval = 5.minutes end From builder at mmediasys.com Sun Mar 30 14:16:23 2008 From: builder at mmediasys.com (builder at mmediasys.com) Date: Sun, 30 Mar 2008 15:16:23 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-trunk-mswin32 build 997 failed Message-ID: <47efd8f798968_d5013de3a6164@KEORE.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- New revision 997 detected Revision 997 committed by luislavena on 2008-03-30 18:11:47 Remove deprecated WIN32 and use Gem::Platform::CURRENT instead. M /trunk M /trunk/Rakefile BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" C:/Ruby/bin/ruby extconf.rb (in D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work) [CruiseControl] Invoking Rake task "clobber" Cleaning - ext/http11/http11-i386-mswin32.def - ext/http11/http11-i386-mswin32.exp - ext/http11/http11-i386-mswin32.lib - ext/http11/http11-i386-mswin32.pdb - ext/http11/http11.obj - ext/http11/http11_parser.obj - ext/http11/Makefile - ext/http11/vc60.pdb - lib/http11.so [CruiseControl] Invoking Rake task "compile" checking for main() in c.lib... no creating Makefile Microsoft (R) Program Maintenance Utility Version 6.00.9782.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. C:\Ruby\bin\ruby -e "puts 'EXPORTS', 'Init_http11'" > http11-i386-mswin32.def cl -nologo -I. -I. -IC:/Ruby/lib/ruby/1.8/i386-mswin32 -I. -MD -Zi -O2b2xg- -G6 -c -Tchttp11.c http11.c cl -nologo -I. -I. -IC:/Ruby/lib/ruby/1.8/i386-mswin32 -I. -MD -Zi -O2b2xg- -G6 -c -Tchttp11_parser.c http11_parser.c cl -nologo -LD -Fehttp11.so http11.obj http11_parser.obj msvcrt-ruby18.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -incremental:no -debug -opt:ref -opt:icf -dll -libpath:"." -libpath:"C:/Ruby/lib" -def:http11-i386-mswin32.def -implib:http11-i386-mswin32.lib -pdb:http11-i386-mswin32.pdb Creating library http11-i386-mswin32.lib and object http11-i386-mswin32.exp C:/Ruby/bin/ruby -Ilib;ext;bin;test "C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" "test/test_cgi_wrapper.rb" "test/test_command.rb" "test/test_conditional.rb" "test/test_configurator.rb" "test/test_debug.rb" "test/test_handlers.rb" "test/test_http11.rb" "test/test_redirect_handler.rb" "test/test_request_progress.rb" "test/test_response.rb" "test/test_stats.rb" "test/test_uriclassifier.rb" "test/test_ws.rb" [CruiseControl] Invoking Rake task "test" Loaded suite C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader Started ...............F............................................. Finished in 30.797 seconds. 1) Failure: test_base_handler_config(ConfiguratorTest) [./test/test_configurator.rb:82]: <[Errno::EBADF, Errno::ECONNREFUSED]> exception expected but was Class: Message: <"An existing connection was forcibly closed by the remote host."> ---Backtrace--- C:/Ruby/lib/ruby/1.8/net/protocol.rb:133:in `sysread' C:/Ruby/lib/ruby/1.8/net/protocol.rb:133:in `rbuf_fill' C:/Ruby/lib/ruby/1.8/timeout.rb:56:in `timeout' C:/Ruby/lib/ruby/1.8/timeout.rb:76:in `timeout' C:/Ruby/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill' C:/Ruby/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' C:/Ruby/lib/ruby/1.8/net/protocol.rb:126:in `readline' C:/Ruby/lib/ruby/1.8/net/http.rb:2029:in `read_status_line' C:/Ruby/lib/ruby/1.8/net/http.rb:2018:in `read_new' C:/Ruby/lib/ruby/1.8/net/http.rb:1059:in `request' C:/Ruby/lib/ruby/1.8/net/http.rb:957:in `request_get' C:/Ruby/lib/ruby/1.8/net/http.rb:380:in `get_response' C:/Ruby/lib/ruby/1.8/net/http.rb:547:in `start' C:/Ruby/lib/ruby/1.8/net/http.rb:379:in `get_response' C:/Ruby/lib/ruby/1.8/net/http.rb:356:in `get' ./test/test_configurator.rb:83:in `test_base_handler_config' ./test/test_configurator.rb:82:in `test_base_handler_config' --------------- 61 tests, 541 assertions, 1 failures, 0 errors rake aborted! Command failed with status (1): [C:/Ruby/bin/ruby -Ilib;ext;bin;test "C:/Ru...] (See full trace by running task with --trace) dir : D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-trunk-mswin32/build-997/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-trunk-mswin32\build-997\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test' project.scheduler.polling_interval = 5.minutes end From builder at mmediasys.com Sun Mar 30 22:51:09 2008 From: builder at mmediasys.com (Integration Builder) Date: Sun, 30 Mar 2008 23:51:09 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-trunk-mingw32 build 997.1 failed Message-ID: <47f0519d53bd8_de01462a8819a@edicion01.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- Build was manually requested BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" rake clean (in D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work) [CruiseControl] Invoking Rake task "clobber" Cleaning rake aborted! undefined method `exitstatus' for nil:NilClass D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work/rakefile:127:in `sub_project' (See full trace by running task with --trace) dir : D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/build-997.1/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-trunk-mingw32\build-997.1\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test' project.scheduler.polling_interval = 5.minutes end From builder at mmediasys.com Sun Mar 30 23:00:37 2008 From: builder at mmediasys.com (Integration Builder) Date: Mon, 31 Mar 2008 00:00:37 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] rubygems-mswin32 build 1681.1 fixed Message-ID: <47f053d5ec540_d2c13de3a619e@edicion01.tmail> The build has been fixed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- Build was manually requested BUILD LOG --------- D:/Users/Luis/.cruise/projects/rubygems-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" (in D:/Users/Luis/.cruise/projects/rubygems-mswin32/work) [CruiseControl] Invoking Rake task "test" Loaded suite D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader Started .............................................................D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialized D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialized D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialized ................................D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/rdoc/parsers/parse_c.rb:204: warning: method redefined; discarding old progress ...WARNING: Unable to use symlinks on Windows, installing wrapper .WARNING: Unable to use symlinks on Windows, installing wrapper .WARNING: Unable to use symlinks on Windows, installing wrapper ..............................................................WARNING: Unable to use symlinks on Windows, installing wrapper .............WARNING: Unable to use symlinks on Windows, installing wrapper ..WARNING: Unable to use symlinks on Windows, installing wrapper .............................................................................................................................................................................................................................................................................................................................................................................................................................. Finished in 55.891 seconds. 589 tests, 1758 assertions, 0 failures, 0 errors PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['rubygems-developers at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.scheduler.polling_interval = 5.minutes end From luislavena at gmail.com Sun Mar 30 23:41:09 2008 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 31 Mar 2008 00:41:09 -0300 Subject: [Rubyinstaller-devel] Integration Builder in place. Message-ID: <71166b3b0803302041u1ee3534cl378cc5f5b976de75@mail.gmail.com> I guess everyone has noticed the Integration Builder emails on list. Still needs a few tweaks, dynamic ip and a UPS (yeah, it's directly to the powerline). Anyway, I started adding the projects I commented previously, split on two platforms: mswin32 to keep compatibility with i386-mswin32 and mingw32 for the new Installer3 Ruby. Since ruby tests still don't pass, I cannot add Installer3 to the Builder, which is a bummer. I'll try to hack and manually remove the test_readline to make it work. Until the dynamic IP is set, this is the list of the projects loaded: mongrel-trunk-mingw32 mongrel-trunk-mswin32 rubygems-mingw32 rubygems-mswin32 I didn't reference 'trunk' for rubygems since is the only 'active' branch right now, Mongrel, on the other hand, have stable_1-2 and trunk, but 1.2 is pretty damn broken at least for me. I'll check what can be done to fix it. Good night everybody and good week! -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams From builder at mmediasys.com Mon Mar 31 01:30:22 2008 From: builder at mmediasys.com (Integration Builder) Date: Mon, 31 Mar 2008 02:30:22 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-trunk-mingw32 build 998 failed Message-ID: <47f076ee66c88_de01462a88286@edicion01.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- New revision 998 detected Revision 998 committed by luislavena on 2008-03-31 05:25:39 Remove fixed port numbers used in tests, make tests more friendly to CI tools. Use of #process_based_port as port number. M /trunk/test/test_redirect_handler.rb M /trunk/test/test_handlers.rb M /trunk M /trunk/test/test_configurator.rb M /trunk/test/test_conditional.rb M /trunk/test/test_ws.rb M /trunk/test/testhelp.rb M /trunk/test/test_request_progress.rb BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" rake clean (in D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work) [CruiseControl] Invoking Rake task "clobber" Cleaning rake aborted! undefined method `exitstatus' for nil:NilClass D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work/rakefile:127:in `sub_project' (See full trace by running task with --trace) dir : D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-trunk-mingw32/build-998/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-trunk-mingw32\build-998\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test' project.scheduler.polling_interval = 5.minutes end From builder at mmediasys.com Mon Mar 31 04:30:03 2008 From: builder at mmediasys.com (Integration Builder) Date: Mon, 31 Mar 2008 05:30:03 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-stable_1-2-mswin32 build 1001 failed Message-ID: <47f0a10bbeac8_ee013de3a612@edicion01.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- This is the first build BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/bin/ruby extconf.rb (in D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mswin32/work) [CruiseControl] Invoking Rake task "clobber" Cleaning [CruiseControl] Invoking Rake task "compile" checking for main() in c.lib... no creating Makefile Microsoft (R) Program Maintenance Utility Version 6.00.9782.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. D:\Users\Luis\ruby\ruby-186-p114-VC6-rubygems-110\bin\ruby -e "puts 'EXPORTS', 'Init_http11'" > http11-i386-mswin32.def cl -nologo -I. -I. -ID:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/i386-mswin32 -I. -MD -Zi -O2b2xg- -G6 -c -Tchttp11.c http11.c cl -nologo -I. -I. -ID:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/1.8/i386-mswin32 -I. -MD -Zi -O2b2xg- -G6 -c -Tchttp11_parser.c http11_parser.c cl -nologo -LD -Fehttp11.so http11.obj http11_parser.obj msvcrt-ruby18.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -incremental:no -debug -opt:ref -opt:icf -dll -libpath:"." -libpath:"D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib" -def:http11-i386-mswin32.def -implib:http11-i386-mswin32.lib -pdb:http11-i386-mswin32.pdb Creating library http11-i386-mswin32.lib and object http11-i386-mswin32.exp D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/bin/ruby -Ilib;ext;bin;test "D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" "test/test_helper.rb" "test/unit/test_cgi_wrapper.rb" "test/unit/test_command.rb" "test/unit/test_conditional.rb" "test/unit/test_configurator.rb" "test/unit/test_debug.rb" "test/unit/test_handlers.rb" "test/unit/test_http_parser.rb" "test/unit/test_redirect_handler.rb" "test/unit/test_request_progress.rb" "test/unit/test_response.rb" "test/unit/test_stats.rb" "test/unit/test_uriclassifier.rb" "test/unit/test_ws.rb" [CruiseControl] Invoking Rake task "test" ./test/test_helper.rb:8: warning: already initialized constant HERE Loaded suite D:/Users/Luis/ruby/ruby-186-p114-VC6-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader Started .......................F..E................................ Finished in 32.297 seconds. 1) Failure: test_horrible_queries(HttpParserTest) [./test/unit/test_http_parser.rb:105:in `test_horrible_queries' ./test/unit/test_http_parser.rb:103:in `times' ./test/unit/test_http_parser.rb:103:in `test_horrible_queries']: exception expected but none was thrown. 2) Error: test_parse_strange_headers(HttpParserTest): Mongrel::HttpParserError: Invalid HTTP format, parsing fails. ./test/unit/test_http_parser.rb:49:in `execute' ./test/unit/test_http_parser.rb:49:in `test_parse_strange_headers' 59 tests, 458 assertions, 1 failures, 1 errors rake aborted! Command failed with status (1): [D:/Users/Luis/ruby/ruby-186-p114-VC6-rubyg...] (See full trace by running task with --trace) dir : D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mswin32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mswin32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mswin32/build-1001/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-stable_1-2-mswin32\build-1001\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test package' project.scheduler.polling_interval = 5.minutes end From builder at mmediasys.com Mon Mar 31 04:30:26 2008 From: builder at mmediasys.com (Integration Builder) Date: Mon, 31 Mar 2008 05:30:26 -0300 Subject: [Rubyinstaller-devel] [CruiseControl] mongrel-stable_1-2-mingw32 build 1001 failed Message-ID: <47f0a122222e0_bd41462a8815d@edicion01.tmail> The build failed. Note: if you set Configuration.dashboard_url in config/site_config.rb, you'd see a link to the build page here. CHANGES ------- This is the first build BUILD LOG --------- D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/bin/ruby extconf.rb (in D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mingw32/work) [CruiseControl] Invoking Rake task "clobber" Cleaning [CruiseControl] Invoking Rake task "compile" checking for main() in -lc... no creating Makefile gcc -I. -I. -ID:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/1.8/i386-mingw32 -I. -g -O2 -c http11.c gcc -I. -I. -ID:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/1.8/i386-mingw32 -I. -g -O2 -c http11_parser.c gcc -shared -s -o http11.so http11.o http11_parser.o -L. -LD:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib -L. -Wl,--enable-auto-image-base,--enable-auto-import,--export-all -lmsvcrt-ruby18 -lshell32 -lws2_32 D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/bin/ruby -Ilib;ext;bin;test "D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" "test/test_helper.rb" "test/unit/test_cgi_wrapper.rb" "test/unit/test_command.rb" "test/unit/test_conditional.rb" "test/unit/test_configurator.rb" "test/unit/test_debug.rb" "test/unit/test_handlers.rb" "test/unit/test_http_parser.rb" "test/unit/test_redirect_handler.rb" "test/unit/test_request_progress.rb" "test/unit/test_response.rb" "test/unit/test_stats.rb" "test/unit/test_uriclassifier.rb" "test/unit/test_ws.rb" [CruiseControl] Invoking Rake task "test" ./test/test_helper.rb:8: warning: already initialized constant HERE ./test/unit/test_command.rb:9: uninitialized constant GemPlugin (NameError) from D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5:in `load' from D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5 from D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5:in `each' from D:/Users/Luis/ruby/ruby-186-svn-MINGW-rubygems-110/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5 rake aborted! Command failed with status (1): [D:/Users/Luis/ruby/ruby-186-svn-MINGW-ruby...] (See full trace by running task with --trace) dir : D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mingw32/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" executed command : echo D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mingw32/work Luis$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:/Users/Luis/.cruise/projects/mongrel-stable_1-2-mingw32/build-1001/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'D:/Users/Luis/tools/ccrb/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-stable_1-2-mingw32\build-1001\build.log 2>&1 exitstatus: 1 STDERR TAIL START STDERR TAIL END PROJECT SETTINGS ---------------- # Project-specific configuration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = ['mongrel-development at rubyforge.org', 'rubyinstaller-devel at rubyforge.org'] project.rake_task = 'clobber compile test package' project.scheduler.polling_interval = 5.minutes end