From hgs at dmu.ac.uk Thu Mar 3 07:20:40 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Thu Mar 3 07:20:51 2005 Subject: [Rubygems-developers] The yaml file. Message-ID: I've found downloading the yaml file, which happens whenever I do updates, to be rather slow over a 56k line. (OK, I can't expect much to be fast over such a line, but still, we are trying to support the largest user base possible.). So, I look in the code and see that it is yaml.Z I think "compress, and not gzip?". I think: I'll do some tests to see if gzip is much smaller, because I have written gunzip support for http in ruby.... I get the file, but I can't use gunzip to uncompress it, or uncompress, or unzip. I've unpacked it using require 'zlib' yaml_spec = File.open("./yaml.Z"){|f| f.read() } yaml_spec = Zlib::Inflate.inflate(yaml_spec) File.open('yaml', 'w'){|f| f.print yaml_spec } and then I tried gzip -9 (results with just gzip were slightly bigger than zlib): brains hgs 227 %> ls -l total 7346 -rw-r--r-- 1 hgs staff 158 Mar 3 12:08 uncompact.rb -rw-r--r-- 1 hgs staff 312839 Mar 2 13:55 yaml.Z -rw-r--r-- 1 hgs staff 303443 Mar 3 12:08 yaml.gz -rw-r--r-- 1 hgs staff 2772407 Mar 3 12:08 yaml.orig brains hgs 228 %> ruby -e 'puts 303443.0 / 312839.0 ' 0.96996538155409 brains hgs 229 %> gunzip yaml brains hgs 230 %> bzip2 yaml brains hgs 231 %> ls -l total 7074 -rw-r--r-- 1 hgs staff 158 Mar 3 12:08 uncompact.rb -rw-r--r-- 1 hgs staff 312839 Mar 2 13:55 yaml.Z -rw-r--r-- 1 hgs staff 170235 Mar 3 12:08 yaml.bz2 -rw-r--r-- 1 hgs staff 2772407 Mar 3 12:08 yaml.orig brains hgs 232 %> ruby -e 'puts 170235.0 / 312839.0 ' 0.544161693395005 brains hgs 233 %> Questions that arise are: Is about a 4% saving worth moving to gzip? Does anyone know of plans (or reasons for the absence of plans) to add bzip2 support to ruby? What actually is the compressed format used now, given that I can't read it except with ruby? From drbrain at segment7.net Thu Mar 3 12:32:11 2005 From: drbrain at segment7.net (Eric Hodel) Date: Thu Mar 3 12:28:14 2005 Subject: [Rubygems-developers] The yaml file. In-Reply-To: References: Message-ID: <738b5ca7c719fc8d5a0bbec85940cff4@segment7.net> On 03 Mar 2005, at 04:20, Hugh Sasse Staff Elec Eng wrote: > Questions that arise are: > What actually is the compressed format used now, given that I can't > read it except with ruby? deflate: > require 'zlib' > yaml_spec = File.open("./yaml.Z"){|f| f.read() } > yaml_spec = Zlib::Inflate.inflate(yaml_spec) > > File.open('yaml', 'w'){|f| f.print yaml_spec } -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/rubygems-developers/attachments/20050303/66c9e512/PGP.bin From hgs at dmu.ac.uk Thu Mar 3 12:45:45 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Thu Mar 3 12:42:36 2005 Subject: [Rubygems-developers] The yaml file. In-Reply-To: <738b5ca7c719fc8d5a0bbec85940cff4@segment7.net> References: <738b5ca7c719fc8d5a0bbec85940cff4@segment7.net> Message-ID: On Thu, 3 Mar 2005, Eric Hodel wrote: > On 03 Mar 2005, at 04:20, Hugh Sasse Staff Elec Eng wrote: > >> Questions that arise are: >> What actually is the compressed format used now, given that I can't >> read it except with ruby? > > deflate: Yes, but as defined where? Presumably this is not unique to ruby, is it? I'm aware of a number of compression systems (Huffman, run length, Shannon-Fano, Ziv-Lempel(-Welch), Tunstall...) but have no information about deflate. Hugh From drbrain at segment7.net Thu Mar 3 13:50:46 2005 From: drbrain at segment7.net (Eric Hodel) Date: Thu Mar 3 13:46:42 2005 Subject: [Rubygems-developers] The yaml file. In-Reply-To: References: <738b5ca7c719fc8d5a0bbec85940cff4@segment7.net> Message-ID: On 03 Mar 2005, at 09:45, Hugh Sasse Staff Elec Eng wrote: > On Thu, 3 Mar 2005, Eric Hodel wrote: > >> On 03 Mar 2005, at 04:20, Hugh Sasse Staff Elec Eng wrote: >> >>> Questions that arise are: >>> What actually is the compressed format used now, given that I can't >>> read it except with ruby? >> >> deflate: > > Yes, but as defined where? Presumably this is not unique to ruby, is > it? > I'm aware of a number of compression systems (Huffman, run length, > Shannon-Fano, Ziv-Lempel(-Welch), Tunstall...) but have no > information about deflate. First hit on google, or: ftp://ftp.rfc-editor.org/in-notes/rfc1951.txt -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/rubygems-developers/attachments/20050303/8a68ff2e/PGP.bin From hgs at dmu.ac.uk Thu Mar 3 14:52:50 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Thu Mar 3 14:51:51 2005 Subject: [Rubygems-developers] The yaml file. In-Reply-To: References: <738b5ca7c719fc8d5a0bbec85940cff4@segment7.net> Message-ID: On Thu, 3 Mar 2005, Eric Hodel wrote: > > On 03 Mar 2005, at 09:45, Hugh Sasse Staff Elec Eng wrote: > >> On Thu, 3 Mar 2005, Eric Hodel wrote: >> >>> On 03 Mar 2005, at 04:20, Hugh Sasse Staff Elec Eng wrote: >>> >> Yes, but as defined where? Presumably this is not unique to ruby, is it? >> I'm aware of a number of compression systems (Huffman, run length, >> Shannon-Fano, Ziv-Lempel(-Welch), Tunstall...) but have no >> information about deflate. > > First hit on google, or: Oh, I didn't try google because pkzip used to refer to inflating and deflating circa 1988, so I expected to get LOADS of compression progs claiming to be this... > > ftp://ftp.rfc-editor.org/in-notes/rfc1951.txt OH, ok, the reasons for writing the spec probably run counter to using Bzip2, maybe. Thank you, Hugh From jim at weirichhouse.org Mon Mar 7 18:56:47 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Mon Mar 7 18:52:28 2005 Subject: [Rubygems-developers] why does 'gem install og' result in installation of log4r rather than installation of og? In-Reply-To: References: Message-ID: <200503071856.47875.jim@weirichhouse.org> That is a bug in gem's overzelous attempt to match gem names during installation (l_og_4r). I think that bug was squashed around verion 0.8.5 or so, but I can't find the notes that say so. If gem --version reports a version earlier than 0.8.5, try upgrading. If you have a recent version, let me know and I'll investigate further (BTW, the CVS version of gems does not do that). -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Mon Mar 7 19:02:00 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Mon Mar 7 18:57:36 2005 Subject: [Rubygems-developers] Patch to fix custom_require In-Reply-To: <20050205183904.5d734f9b@photon.lepton> References: <20050205183904.5d734f9b@photon.lepton> Message-ID: <200503071902.00627.jim@weirichhouse.org> On Saturday 05 February 2005 12:39 pm, Michael Witrant wrote: > Anyone to apply the patch I added in the comment of bug #1290? > > http://rubyforge.org/tracker/?func=detail&atid=575&aid=1290&group_id=126 This was fixed in 0.8.5. I accepted the report and closed it out. Someone really needs to go through the bug reports and close the ones that have been fixed. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Mon Mar 7 19:06:41 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Mon Mar 7 19:02:16 2005 Subject: [Rubygems-developers] Ruby Gem Install Problem on OSX In-Reply-To: References: Message-ID: <200503071906.41391.jim@weirichhouse.org> On Monday 10 January 2005 08:51 am, Jason Savidge wrote: > Hi, > I am trying to install Ruby and Rails so I can begin testing it for web > development on OSX. I seem to have gotten Ruby installed and Rubygems but I > get the following error when trying to get to next step of installing > rails. I installed 1.8 as specified for OSX which leaves 1.6 still on the > OSX system. It seems to be looking towards the 1.6 default install of ruby > for some reason. You're right, it does look like it it using the 1.6 version of Ruby. I am guessing this is because (1) the 1.6 version preceeds the 1.8 version in the PATH environment variable, or (2) the gem command got installed so that it directly references the 1.6 version. I do see that the gems library is in the 1.6 directory tree, so you might have to reinstall RubyGems in the 1.8 tree. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From marcel at vernix.org Wed Mar 9 11:00:37 2005 From: marcel at vernix.org (Marcel Molina Jr.) Date: Wed Mar 9 10:56:20 2005 Subject: [Rubygems-developers] Codefest Grant Message-ID: <20050309160037.GL27959@simons-rock.edu> I just saw on Redhanded that one of the RubyCentral Codefest grants was going toward a RubyGems cleanup and enhancement. I hadn't seen anything about that on this list so I was wondering who is involved (beside Ryan Davis). I'm not wanting to get a piece of the funds, just curious about details. marcel -- Marcel Molina Jr. From drbrain at segment7.net Wed Mar 9 15:06:48 2005 From: drbrain at segment7.net (Eric Hodel) Date: Wed Mar 9 15:02:40 2005 Subject: [Rubygems-developers] Codefest Grant In-Reply-To: <20050309160037.GL27959@simons-rock.edu> References: <20050309160037.GL27959@simons-rock.edu> Message-ID: <2922ae744532fd158dee1e16efeca9a8@segment7.net> On 09 Mar 2005, at 08:00, Marcel Molina Jr. wrote: > I just saw on Redhanded that one of the RubyCentral Codefest grants > was going toward a RubyGems cleanup and enhancement. I hadn't seen > anything about that on this list so I was wondering who is involved > (beside Ryan Davis). I'm not wanting to get a piece of the funds, just > curious about details. If you can get to Seattle, you too can get a piece of the pie. The cleanup work is planned to involve the Seattle, PDX and Vancouver (BC) Ruby groups. We're still compiling a list of things to clean up. -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/rubygems-developers/attachments/20050309/11cebb32/PGP.bin From chad at chadfowler.com Wed Mar 9 17:10:31 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Wed Mar 9 15:59:45 2005 Subject: [Rubygems-developers] Codefest Grant In-Reply-To: <2922ae744532fd158dee1e16efeca9a8@segment7.net> References: <20050309160037.GL27959@simons-rock.edu> <2922ae744532fd158dee1e16efeca9a8@segment7.net> Message-ID: <61676.208.252.131.50.1110406231.squirrel@208.252.131.50> > On 09 Mar 2005, at 08:00, Marcel Molina Jr. wrote: > >> I just saw on Redhanded that one of the RubyCentral Codefest grants >> was going toward a RubyGems cleanup and enhancement. I hadn't seen >> anything about that on this list so I was wondering who is involved >> (beside Ryan Davis). I'm not wanting to get a piece of the funds, just >> curious about details. > > If you can get to Seattle, you too can get a piece of the pie. The > cleanup work is planned to involve the Seattle, PDX and Vancouver (BC) > Ruby groups. We're still compiling a list of things to clean up. > Do you guys know when you'll be doing it? Looks like I'll be in Seattle most of the week of March 28. I could probably bleed into a weekend if you wanted to get together (even if you can't pull this thing off that quickly--I bet you can't). Chad From jim at weirichhouse.org Fri Mar 11 00:52:38 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Fri Mar 11 00:47:49 2005 Subject: [Rubygems-developers] Possible Fix for the "gem update rails" bug on WInXP Message-ID: <200503110052.38638.jim@weirichhouse.org> Actually, I don't think the bug is WinXP only, nor directly related to rails. But the following message is typical of this kind of error ... ------------------------------------------------------------ Attempting remote installation of 'actionmailer' ERROR: While executing gem ... (NoMethodError) undefined method `serialize' for CGI::Session::ActiveRecordStore::Session:Class ------------------------------------------------------------ This error manifests as an error message that /looks/ as if the client code is being run. Since RubyGems doesn't run client code during an install, this bug has mystified me for some time. So today I was reading through the Installer class working on an unrelated issue when I noticed that the installer used a "require_gem" command on the dependencies, and attempted to set the autorequire flag to false. The problem is that require_gem doesn't support an autorequire flag. So if a gem has a dependency, and that dependent gem has a autorequire file specified, then that autorequire file will be loaded during the installation. This is quite possibly the source of the bug mentioned above. I've fixed the problem in CVS, and would like anyone who has had the above problem (or a similar one) to give the CVS version a try and see if it fixes anything (Unfortunately (or perhaps fortunately) I've never run into the problem on my machine). Thanks. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From hgs at dmu.ac.uk Fri Mar 11 11:27:11 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Fri Mar 11 11:35:37 2005 Subject: [Rubygems-developers] 'nodoc' errors -- may be nothing... Message-ID: Should I be the least bit concerned about messages like: brains# gem install -r log4r Attempting remote installation of 'log4r' Updating Gem source index for: http://gems.rubyforge.org Successfully installed log4r, version 1.0.5 Installing RDoc documentation for log4r-1.0.5-... src/log4r/config.rb:4:0: Unrecognized directive 'nodoc' src/log4r/base.rb:2:7: Unrecognized directive 'nodoc' src/log4r/logevent.rb:2:6: Unrecognized directive 'nodoc' src/log4r/loggerfactory.rb:4:0: Unrecognized directive 'nodoc' src/log4r/repository.rb:4:0: Unrecognized directive 'nodoc' src/log4r/staticlogger.rb:2:6: Unrecognized directive 'nodoc' and plenty more the same? I confident that it doesn't matter, but thought I'd raise it in case it has significance for someone. This occurred with rubygems-0.8.4 and after I tried with rubygems-0.8.6, if that helps Thank you, Hugh From jim at weirichhouse.org Fri Mar 11 12:03:58 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Fri Mar 11 11:59:09 2005 Subject: [Rubygems-developers] Possible Fix for the "gem update rails" bug on WInXP In-Reply-To: <200503110052.38638.jim@weirichhouse.org> References: <200503110052.38638.jim@weirichhouse.org> Message-ID: <200503111203.58581.jim@weirichhouse.org> Ok, this is the third attempt to squash this bug. After finding some code that didn't set the auto_require flag to false correctly, and then finding another location that had the same error, I finally discovered that the Gem.activate method didn't properly honor the auto_require=>false request under all situations. The CVS tree is fixed and updated for anyone who would like to try it out. Let me know if it works this time. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Fri Mar 11 12:59:04 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Fri Mar 11 12:54:05 2005 Subject: [Rubygems-developers] Possible Fix for the "gem update rails" bug on WInXP In-Reply-To: <200503111203.58581.jim@weirichhouse.org> References: <200503110052.38638.jim@weirichhouse.org> <200503111203.58581.jim@weirichhouse.org> Message-ID: <200503111259.04115.jim@weirichhouse.org> On Friday 11 March 2005 12:03 pm, Jim Weirich wrote: > Ok, this is the third attempt to squash this bug. > > After finding some code that didn't set the auto_require flag to false > correctly, and then finding another location that had the same error, > I finally discovered that the Gem.activate method didn't properly honor the > auto_require=>false request under all situations. > > The CVS tree is fixed and updated for anyone who would like to try it out. > Let me know if it works this time. Bill Guindon reports that this fixed it for him. Yea! I'm moving on to the next issue. Jim Freeze had some usability concerns on uninstall. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From agorilla at gmail.com Fri Mar 11 13:02:28 2005 From: agorilla at gmail.com (Bill Guindon) Date: Fri Mar 11 12:58:03 2005 Subject: [Rubygems-developers] Possible Fix for the "gem update rails" bug on WInXP In-Reply-To: <200503111203.58581.jim@weirichhouse.org> References: <200503110052.38638.jim@weirichhouse.org> <200503111203.58581.jim@weirichhouse.org> Message-ID: <67a2229205031110022f664fb4@mail.gmail.com> On Fri, 11 Mar 2005 12:03:58 -0500, Jim Weirich wrote: > Ok, this is the third attempt to squash this bug. > > After finding some code that didn't set the auto_require flag to false > correctly, and then finding another location that had the same error, > I finally discovered that the Gem.activate method didn't properly honor the > auto_require=>false request under all situations. > > The CVS tree is fixed and updated for anyone who would like to try it out. > Let me know if it works this time. Just ran a test: Uninstalled rails and all dependencies Rolled back to Gem 0.8.4 Tried to "gem install rails", got an error. Dropped in the new (0.8.6.2) gem "gem install rails" worked, and it worked with the defaults (I didn't type the "y") Thanks much for the time you put into this. I now have Rails 0.10.1 -- Bill Guindon (aka aGorilla) From chad at chadfowler.com Fri Mar 11 16:54:58 2005 From: chad at chadfowler.com (Chad Fowler) Date: Fri Mar 11 16:50:33 2005 Subject: [Rubygems-developers] 'nodoc' errors -- may be nothing... In-Reply-To: References: Message-ID: On 11-Mar-05, at 11:27 AM, Hugh Sasse Staff Elec Eng wrote: > Should I be the least bit concerned about messages like: > > brains# gem install -r log4r > Attempting remote installation of 'log4r' > Updating Gem source index for: http://gems.rubyforge.org > Successfully installed log4r, version 1.0.5 > Installing RDoc documentation for log4r-1.0.5-... > > src/log4r/config.rb:4:0: Unrecognized directive 'nodoc' > > src/log4r/base.rb:2:7: Unrecognized directive 'nodoc' > > src/log4r/logevent.rb:2:6: Unrecognized directive 'nodoc' > > src/log4r/loggerfactory.rb:4:0: Unrecognized directive 'nodoc' > > src/log4r/repository.rb:4:0: Unrecognized directive 'nodoc' > > src/log4r/staticlogger.rb:2:6: Unrecognized directive 'nodoc' > > > and plenty more the same? I confident that it doesn't matter, but > thought I'd raise it in case it has significance for someone. > > This occurred with rubygems-0.8.4 and after I tried with > rubygems-0.8.6, if that helps > > Hugh, if you run rdoc directly against your installed log4r source, you'll see that you get the same errors. The errors are being reported by RDoc and not by RubyGems. I'm not sure what causes them, but it would be best to ask Dave, probably. Chad From jim at weirichhouse.org Sat Mar 12 08:52:29 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Sat Mar 12 08:47:22 2005 Subject: [Rubygems-developers] Pre 0.8.7 release & docs.rubygems.org announcement Message-ID: <200503120852.29680.jim@weirichhouse.org> I'm getting ready to make a 0.8.7 release of RubyGems. There are a lot of changes in this release and would appreciate it if folks could download the current CVS tree and give it a try. I plan to make the release Sunday night if there are no objections. Chad, there were a couple of things on our list that didn't make the cut. The uninstall --with-dependencies didn't make it, mainly because of the potential of uninstalling a lot more than you expect. I want some more thought on that one. The other thing that didn't make it is the Robert Feldt issue (extensions in nested libraries). I strongly suspect that can be address by a rake tasks and needn't be a gems issue. But again, I need more time to investigate that. In addition to 0.8.7, we are also announcing the RubyGems documentation website: http://docs.rubygems.org. Take a look at that and quick feedback is appreciated. Here are the release announcements (both 0.8.7 and docs.rubygems). Please review. Thank you. --BEGIN ANNOUNCEMENT------------------------------------------------------- = Announce: RubyGems Release 0.8.7 Time passes quickly, and so does software developement. Release 0.8.7 of RubyGems is availble for public release. Although another point release, you will find a number of very nice new features. First the numbers, 220 different gems available, almost 22,000 downloads of RubyGems, and nearly 190,000 gems downloads. Thanks to everyone for their support. == What's New Even though it has only been a few weeks since that last release, there are quite a number of new features in 0.8.7. A complete list of new features will be given below, but here is a summary of the hot items. * The bug that prevented some users from installing rails has been squashed. A big thanks to Bill Guindon (aGorilla) for helping track that one down. There are several new commands available on the gem command: * gem cleanup GEMNAME -- Cleanup (uninstall) all the old versions of gem. If the gem name is omitted, the entire repository is cleaned. * gem dependency GEMNAME -- Show the dependencies for the named gems. This is really helpful when trying to figure out what gem needs what other gem. There changes to the existing commands as well. * gem uninstall is much smarter about removing gems from the repository. Lists of gems are now uninstalled in proper dependency order (ie. if A depends on B, A is uninstalled first). Also, warnings about broken dependencies occur only when removing the *last* gem that supports a dependency is removed. Both gem install and gem uninstall support some new command line options that can reduce the amount of yes/no queries given the user. For install we have: * --ignored-dependencies -- Only install requests gems, no dependendecies are automatically installed. * --include-dependencies -- Automatically install dependencies, without confirmation. For gem uninstall, the new options are: * --all -- Uninstall all matching gems without confirmation. * --ignore-dependencies -- Uninstall, even if dependencies are broken. * --executables -- Remove executables without confirmation And finally there is a new library file 'gemconfigure' to aid in writing version sensitive applications (without undo dependencies on RubyGems); and 'gemwhich', a short script to locate libraries in the file system. You can read more about them here: * gemconfigure: http://docs.rubygems.org/read/chapter/4#page73 * gemwhich: http://docs.rubygems.org/read/chapter/17 == What is RubyGems? RubyGems is a package management system for Ruby applications and libraries. RubyGems one command download makes installing Ruby software fun and enjoyable again. (Ok, not really.) Many gems are available for download from the RubyForge site. Browse the list of gems with a "gem list --remote" command and download what you need with a simple "gem install ". RubyGems takes care of the details of installing, not only the gem you requested, but also any gems needed by the software you selected. == How can I get all this great stuff? Well, here's how ... To download and install: 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 2. UNPACK INTO A DIRECTORY AND CD THERE 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) ... or, if you have RubyGems version 0.8.5 or later .... $ gem update --system (again, might need to be admin/root) ... If you don't have a recent RubyGems, you can still do the two-step .... $ gem install rubygems-update (again, might need to be admin/root) $ update_rubygems (... here too) == Detailed Change List This list touches on most of the user visible changes in the RubyGems change log. See the change log file for even more details. * Fixed bug in cache manager that caused the cache to be reread every time on Windows. * Removed annoying message about not finding .gemrc. * Uninstall command will now accept the following options: * --all (uninstall all matches without query), * --ignore-dependencies (ignore dependency constraints while uninstalling), * --executables (remove the executables without querying). * New command: "gem cleanup" will remove all old versions of the list gems (or the entire repository). * Uninstalling now will only query if removing a gem actually will cause a dependency to be unfulfilled. * A new library file "gemconfigure.rb" makes is easy to take advantage of dynamic versioning without becoming tied to using RubyGems. * Source URIs given to the --source option will now assume an "http://" prefix if one is not given. * New Command: "gem dependency" will show the dependency requirements of any installed gem. Reverse dependencies are also supported. == Thanks Thanks to David Heinemeier Hansson for a number of suggestions that made it into this release. Also thanks go to Bill Guindon (aGorilla) and Jim Freeze for feedback and testing of intermediate versions. Keep those gems coming! -- Jim & Chad (for the RubyGems team) -- DOCS.RUBYGEMS.ORG ANNOUNCEMENT ------------------------------- == Announcing the RubyGems Documentation Site http://docs.rubygems.org Concurrent with RubyGems 0.8.7, I am very pleased to announce the public release of the RubyGems documentation website. This site is built upon the excellent Hieraki application (the same one used to document Ruby on Rails). After fighting with wiki spammers and missing data, the RubyGems team decided to move the documentation to something a little more durable than a wiki page. The content from the wiki pages have been reviewed, reorganized, and moved to the docs.rubygems.org site. The move is not complete, there is still information on the wiki that has not made it into the RubyGems document set yet. But we will continue to convert the site as time goes on. We feel the Hieraki application gives us a much better opportunity to provide quality documentation for the RubyGems system. We hope you enjoy it. Thanks to Tobias L?tke for Hieraki and to Bruce Williams for the RubyGems icon. If you are interested in helping with the RubyGems documentation, please contact Jim Weirich (jim@weirichhouse.org) or Chad Fowler (chad@chadfowler.com) about becoming an RubyGems document author. -- END ----------------------------------------------------- -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From chad at chadfowler.com Sat Mar 12 09:31:22 2005 From: chad at chadfowler.com (Chad Fowler) Date: Sat Mar 12 09:26:57 2005 Subject: [Rubygems-developers] Pre 0.8.7 release & docs.rubygems.org announcement In-Reply-To: <200503120852.29680.jim@weirichhouse.org> References: <200503120852.29680.jim@weirichhouse.org> Message-ID: <7610250a71d4140e0737ca7bf1c4f240@chadfowler.com> On 12-Mar-05, at 8:52 AM, Jim Weirich wrote: > I'm getting ready to make a 0.8.7 release of RubyGems. There are a > lot of > changes in this release and would appreciate it if folks could > download the > current CVS tree and give it a try. I plan to make the release Sunday > night > if there are no objections. Great! You've done a TON this last week or two. Great stuff! > > Chad, there were a couple of things on our list that didn't make the > cut. The > uninstall --with-dependencies didn't make it, mainly because of the > potential > of uninstalling a lot more than you expect. I want some more thought > on that > one. > I don't think that's a very important one, relatively. > The other thing that didn't make it is the Robert Feldt issue > (extensions in > nested libraries). I strongly suspect that can be address by a rake > tasks > and needn't be a gems issue. But again, I need more time to > investigate > that. > > In addition to 0.8.7, we are also announcing the RubyGems documentation > website: http://docs.rubygems.org. Take a look at that and quick > feedback is > appreciated. > I've looked through most of it (and not contributed anything other than helping to set it up, sadly). Looks great. It's a big improvement over the Wiki. We should clear all of the Wiki stuff out and just point to this. > Here are the release announcements (both 0.8.7 and docs.rubygems). > Please > review. > > Thank you. > > --BEGIN > ANNOUNCEMENT------------------------------------------------------- > = Announce: RubyGems Release 0.8.7 > > Time passes quickly, and so does software developement. Release 0.8.7 > of RubyGems is availble for public release. Although another point > release, you will find a number of very nice new features. > > First the numbers, 220 different gems available, almost 22,000 > downloads of RubyGems, and nearly 190,000 gems downloads. Thanks to > everyone for their support. > RubyGems has actually been downloaded 25,000 times counting the rubygems-update package. > == What's New > > Even though it has only been a few weeks since that last release, > there are quite a number of new features in 0.8.7. A complete list of > new features will be given below, but here is a summary of the hot > items. > > * The bug that prevented some users from installing rails has been > squashed. A big thanks to Bill Guindon (aGorilla) for helping track > that one down. > > There are several new commands available on the gem command: > > * gem cleanup GEMNAME -- Cleanup (uninstall) all the old versions of > gem. If the gem name is omitted, the entire repository is cleaned. > > * gem dependency GEMNAME -- Show the dependencies for the named gems. > This is really helpful when trying to figure out what gem needs what > other gem. This'n is real nice. > > There changes to the existing commands as well. > > * gem uninstall is much smarter about removing gems from the > repository. Lists of gems are now uninstalled in proper dependency > order (ie. if A depends on B, A is uninstalled first). Also, > warnings about broken dependencies occur only when removing the > *last* gem that supports a dependency is removed. > > Both gem install and gem uninstall support some new command line > options that can reduce the amount of yes/no queries given the user. > For install we have: > > * --ignored-dependencies -- Only install requests gems, no > dependendecies are automatically installed. > * --include-dependencies -- Automatically install dependencies, > without confirmation. > Man, --include-dependencies sure is nice. > For gem uninstall, the new options are: > > * --all -- Uninstall all matching gems without confirmation. > * --ignore-dependencies -- Uninstall, even if dependencies are broken. > * --executables -- Remove executables without confirmation > I guess there are more things we can remove from our TODO list! > And finally there is a new library file 'gemconfigure' to aid in > writing version sensitive applications (without undo dependencies on > RubyGems); and 'gemwhich', a short script to locate libraries in the > file system. You can read more about them here: > > * gemconfigure: http://docs.rubygems.org/read/chapter/4#page73 > * gemwhich: http://docs.rubygems.org/read/chapter/17 > A big one for Rails is that if you set has_rdoc to false, it won't gen rdoc for that gem. A few people have mentioned this one to me, so I fixed it after 0.8.6. Or did Jim fix it? I can't remember now ;) > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby > software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes > care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == How can I get all this great stuff? > > Well, here's how ... > > To download and install: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root > privilege) > > ... or, if you have RubyGems version 0.8.5 or later .... > > $ gem update --system (again, might need to be admin/root) > > ... If you don't have a recent RubyGems, you can still do the two-step > .... > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > == Detailed Change List > > This list touches on most of the user visible changes in the RubyGems > change log. See the change log file for even more details. > > * Fixed bug in cache manager that caused the cache to be reread every > time on Windows. > > * Removed annoying message about not finding .gemrc. > > * Uninstall command will now accept the following options: > * --all (uninstall all matches without query), > * --ignore-dependencies (ignore dependency constraints while > uninstalling), > * --executables (remove the executables without querying). > > * New command: "gem cleanup" will remove all old versions of the list > gems (or the entire repository). > > * Uninstalling now will only query if removing a gem actually will > cause a dependency to be unfulfilled. > > * A new library file "gemconfigure.rb" makes is easy to take advantage > of dynamic versioning without becoming tied to using RubyGems. > > * Source URIs given to the --source option will now assume an > "http://" prefix if one is not given. > > * New Command: "gem dependency" will show the dependency requirements > of any installed gem. Reverse dependencies are also supported. > > == Thanks > > Thanks to David Heinemeier Hansson for a number of suggestions that > made it into this release. Also thanks go to Bill Guindon (aGorilla) > and Jim Freeze for feedback and testing of intermediate versions. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) > > -- DOCS.RUBYGEMS.ORG ANNOUNCEMENT ------------------------------- > == Announcing the RubyGems Documentation Site > > http://docs.rubygems.org > > Concurrent with RubyGems 0.8.7, I am very pleased to announce the > public release of the RubyGems documentation website. This site is > built upon the excellent Hieraki application (the same one used to > document Ruby on Rails). > > After fighting with wiki spammers and missing data, the RubyGems team > decided to move the documentation to something a little more durable > than a wiki page. The content from the wiki pages have been reviewed, > reorganized, and moved to the docs.rubygems.org site. > > The move is not complete, there is still information on the wiki that > has not made it into the RubyGems document set yet. But we will > continue to convert the site as time goes on. > > We feel the Hieraki application gives us a much better opportunity to > provide quality documentation for the RubyGems system. We hope you > enjoy it. > > Thanks to Tobias L?tke for Hieraki and to Bruce Williams for the > RubyGems icon. > > If you are interested in helping with the RubyGems documentation, > please contact Jim Weirich (jim@weirichhouse.org) or Chad Fowler > (chad@chadfowler.com) about becoming an RubyGems document author. > > -- END ----------------------------------------------------- > Excellent release notes and excellent release! I ran through all of the features and it's working great for me. Chad From gsinclair at soyabean.com.au Sat Mar 12 09:31:19 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sat Mar 12 09:28:34 2005 Subject: [Rubygems-developers] Pre 0.8.7 release & docs.rubygems.org announcement In-Reply-To: <200503120852.29680.jim@weirichhouse.org> References: <200503120852.29680.jim@weirichhouse.org> Message-ID: <131411326269.20050313013119@soyabean.com.au> On Sunday, March 13, 2005, 12:52:29 AM, Jim wrote: > Here are the release announcements (both 0.8.7 and docs.rubygems). Please > review. s/undo/undue s/developement/development s/ignored-/ignore- Think that's it. Looks like a good release. Cheers, Gavin From gsinclair at soyabean.com.au Sat Mar 12 10:07:43 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sat Mar 12 10:04:56 2005 Subject: [Rubygems-developers] Whence gemconfigure.rb? Message-ID: <221413509949.20050313020743@soyabean.com.au> Hi, What purpose does gemconfigure.rb serve? What I read in the ChangeLog I can't see in the code. Can an example be provided, and added as a comment in the code? Actually, there is an example in the code, sort of. What's needed is a rationale. Thanks, Gavin From curt at hibbs.com Sat Mar 12 11:21:14 2005 From: curt at hibbs.com (Curt Hibbs) Date: Sat Mar 12 11:16:51 2005 Subject: [Rubygems-developers] Pre 0.8.7 release & docs.rubygems.organnouncement In-Reply-To: <200503120852.29680.jim@weirichhouse.org> Message-ID: Yeaaaaaah!!! Good timing! In a week or to I'm going to put together a new relase of the one-click installer, so I can include this new version. The last time, you guys released released a new version just a day or so *after* I released the one-click installer :-( Curt Jim Weirich wrote: > > I'm getting ready to make a 0.8.7 release of RubyGems. There are > a lot of > changes in this release and would appreciate it if folks could > download the > current CVS tree and give it a try. I plan to make the release > Sunday night > if there are no objections. > > Chad, there were a couple of things on our list that didn't make > the cut. The > uninstall --with-dependencies didn't make it, mainly because of > the potential > of uninstalling a lot more than you expect. I want some more > thought on that > one. > > The other thing that didn't make it is the Robert Feldt issue > (extensions in > nested libraries). I strongly suspect that can be address by a > rake tasks > and needn't be a gems issue. But again, I need more time to investigate > that. > > In addition to 0.8.7, we are also announcing the RubyGems documentation > website: http://docs.rubygems.org. Take a look at that and quick > feedback is > appreciated. > > Here are the release announcements (both 0.8.7 and > docs.rubygems). Please > review. > > Thank you. > > --BEGIN > ANNOUNCEMENT------------------------------------------------------- > = Announce: RubyGems Release 0.8.7 > > Time passes quickly, and so does software developement. Release 0.8.7 > of RubyGems is availble for public release. Although another point > release, you will find a number of very nice new features. > > First the numbers, 220 different gems available, almost 22,000 > downloads of RubyGems, and nearly 190,000 gems downloads. Thanks to > everyone for their support. > > == What's New > > Even though it has only been a few weeks since that last release, > there are quite a number of new features in 0.8.7. A complete list of > new features will be given below, but here is a summary of the hot > items. > > * The bug that prevented some users from installing rails has been > squashed. A big thanks to Bill Guindon (aGorilla) for helping track > that one down. > > There are several new commands available on the gem command: > > * gem cleanup GEMNAME -- Cleanup (uninstall) all the old versions of > gem. If the gem name is omitted, the entire repository is cleaned. > > * gem dependency GEMNAME -- Show the dependencies for the named gems. > This is really helpful when trying to figure out what gem needs what > other gem. > > There changes to the existing commands as well. > > * gem uninstall is much smarter about removing gems from the > repository. Lists of gems are now uninstalled in proper dependency > order (ie. if A depends on B, A is uninstalled first). Also, > warnings about broken dependencies occur only when removing the > *last* gem that supports a dependency is removed. > > Both gem install and gem uninstall support some new command line > options that can reduce the amount of yes/no queries given the user. > For install we have: > > * --ignored-dependencies -- Only install requests gems, no > dependendecies are automatically installed. > * --include-dependencies -- Automatically install dependencies, > without confirmation. > > For gem uninstall, the new options are: > > * --all -- Uninstall all matching gems without confirmation. > * --ignore-dependencies -- Uninstall, even if dependencies are broken. > * --executables -- Remove executables without confirmation > > And finally there is a new library file 'gemconfigure' to aid in > writing version sensitive applications (without undo dependencies on > RubyGems); and 'gemwhich', a short script to locate libraries in the > file system. You can read more about them here: > > * gemconfigure: http://docs.rubygems.org/read/chapter/4#page73 > * gemwhich: http://docs.rubygems.org/read/chapter/17 > > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == How can I get all this great stuff? > > Well, here's how ... > > To download and install: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) > > ... or, if you have RubyGems version 0.8.5 or later .... > > $ gem update --system (again, might need to be admin/root) > > ... If you don't have a recent RubyGems, you can still do the > two-step .... > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > == Detailed Change List > > This list touches on most of the user visible changes in the RubyGems > change log. See the change log file for even more details. > > * Fixed bug in cache manager that caused the cache to be reread every > time on Windows. > > * Removed annoying message about not finding .gemrc. > > * Uninstall command will now accept the following options: > * --all (uninstall all matches without query), > * --ignore-dependencies (ignore dependency constraints while > uninstalling), > * --executables (remove the executables without querying). > > * New command: "gem cleanup" will remove all old versions of the list > gems (or the entire repository). > > * Uninstalling now will only query if removing a gem actually will > cause a dependency to be unfulfilled. > > * A new library file "gemconfigure.rb" makes is easy to take advantage > of dynamic versioning without becoming tied to using RubyGems. > > * Source URIs given to the --source option will now assume an > "http://" prefix if one is not given. > > * New Command: "gem dependency" will show the dependency requirements > of any installed gem. Reverse dependencies are also supported. > > == Thanks > > Thanks to David Heinemeier Hansson for a number of suggestions that > made it into this release. Also thanks go to Bill Guindon (aGorilla) > and Jim Freeze for feedback and testing of intermediate versions. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) > > -- DOCS.RUBYGEMS.ORG ANNOUNCEMENT ------------------------------- > == Announcing the RubyGems Documentation Site > > http://docs.rubygems.org > > Concurrent with RubyGems 0.8.7, I am very pleased to announce the > public release of the RubyGems documentation website. This site is > built upon the excellent Hieraki application (the same one used to > document Ruby on Rails). > > After fighting with wiki spammers and missing data, the RubyGems team > decided to move the documentation to something a little more durable > than a wiki page. The content from the wiki pages have been reviewed, > reorganized, and moved to the docs.rubygems.org site. > > The move is not complete, there is still information on the wiki that > has not made it into the RubyGems document set yet. But we will > continue to convert the site as time goes on. > > We feel the Hieraki application gives us a much better opportunity to > provide quality documentation for the RubyGems system. We hope you > enjoy it. > > Thanks to Tobias L?tke for Hieraki and to Bruce Williams for the > RubyGems icon. > > If you are interested in helping with the RubyGems documentation, > please contact Jim Weirich (jim@weirichhouse.org) or Chad Fowler > (chad@chadfowler.com) about becoming an RubyGems document author. > > -- END ----------------------------------------------------- > -- > -- Jim Weirich jim@weirichhouse.org http://onestepback.org > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.308 / Virus Database: 266.7.2 - Release Date: 3/11/2005 > From jim at weirichhouse.org Sat Mar 12 15:32:12 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Sat Mar 12 15:27:09 2005 Subject: [Rubygems-developers] Whence gemconfigure.rb? In-Reply-To: <221413509949.20050313020743@soyabean.com.au> References: <221413509949.20050313020743@soyabean.com.au> Message-ID: <200503121532.12441.jim@weirichhouse.org> On Saturday 12 March 2005 10:07 am, Gavin Sinclair wrote: > What purpose does gemconfigure.rb serve? What I read in the ChangeLog > I can't see in the code. Can an example be provided, and added as a > comment in the code? Actually, there is an example in the code, sort > of. What's needed is a rationale. http://docs.rubygems.org/read/chapter/4#page73 -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From gsinclair at soyabean.com.au Sat Mar 12 18:21:31 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sat Mar 12 18:18:48 2005 Subject: [Rubygems-developers] Whence gemconfigure.rb? In-Reply-To: <200503121532.12441.jim@weirichhouse.org> References: <221413509949.20050313020743@soyabean.com.au> <200503121532.12441.jim@weirichhouse.org> Message-ID: <1681443137812.20050313102131@soyabean.com.au> On Sunday, March 13, 2005, 7:32:12 AM, Jim wrote: > On Saturday 12 March 2005 10:07 am, Gavin Sinclair wrote: >> What purpose does gemconfigure.rb serve? What I read in the ChangeLog >> I can't see in the code. Can an example be provided, and added as a >> comment in the code? Actually, there is an example in the code, sort >> of. What's needed is a rationale. > http://docs.rubygems.org/read/chapter/4#page73 That's pretty good. How about a Gem.configure_from_yaml method? require 'gemconfigure' Gem.configure_from_yaml('config.yml', 'gems') The second argument could default to 'gems'. Gavin From gsinclair at soyabean.com.au Sat Mar 12 18:41:30 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sat Mar 12 18:38:48 2005 Subject: [Rubygems-developers] Bug: ^M in shebang line of application stub Message-ID: <321444336996.20050313104130@soyabean.com.au> Gem-installing instiki on a UML virtual server (uname output below), I was unable to run the resulting application because it stuffed up the shebang line. `uname -a`: Linux server.pointstorm.com 2.4.20-020stab009.23.777-enterprise #1 SMP Fri Aug 6 10:14:32 MSD 2004 i686 unknown Shebang line: #!/home/gavin/software/bin/ruby^M On running 'instiki': : bad interpreter: No such file or directorye/gavin/software/bin/ruby On replacing shebang line with '#!xyz' and running 'instiki': bash: /home/gavin/software/bin/instiki: xyz: bad interpreter: No such file or directory So the ^M in the shebang line is stuffing up not only the application, but the bash error message! :) Cheers, Gavin From gsinclair at soyabean.com.au Sun Mar 13 00:55:27 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sun Mar 13 00:52:54 2005 Subject: [Rubygems-developers] Bug: ^M in shebang line of application stub In-Reply-To: <321444336996.20050313104130@soyabean.com.au> References: <321444336996.20050313104130@soyabean.com.au> Message-ID: <81466773829.20050313165527@soyabean.com.au> On Sunday, March 13, 2005, 10:41:30 AM, Gavin wrote: > Gem-installing instiki on a UML virtual server (uname output below), I > was unable to run the resulting application because it stuffed up the > shebang line. Fixed (from ChangeLog): * lib/rubygems/installer.rb (Gem::Installer#shebang): Refactored and stripped result to avoid ^M issues. Gavin P.S. I'm going to remove the code in installer.rb which installs library stubs. The line that calls it is commented out, and we don't need any of it anymore. From gsinclair at soyabean.com.au Sun Mar 13 01:05:28 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sun Mar 13 01:02:54 2005 Subject: [Rubygems-developers] Bug: ^M in shebang line of application stub In-Reply-To: <81466773829.20050313165527@soyabean.com.au> References: <321444336996.20050313104130@soyabean.com.au> <81466773829.20050313165527@soyabean.com.au> Message-ID: <651467374813.20050313170528@soyabean.com.au> On Sunday, March 13, 2005, 4:55:27 PM, Gavin wrote: > P.S. I'm going to remove the code in installer.rb which installs > library stubs. The line that calls it is commented out, and we don't > need any of it anymore. Done: revision 1.87 date: 2005/03/13 06:01:30; author: gsinclair; state: Exp; lines: +4 -237 * lib/rubygems/installer.rb: Removed all code relating to library stubs as we haven't generated them for ages. Gavin From gsinclair at soyabean.com.au Sun Mar 13 01:09:02 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Sun Mar 13 01:06:29 2005 Subject: [Rubygems-developers] Post-install problem Message-ID: <1991467589091.20050313170902@soyabean.com.au> Is this a known issue? When I run "ruby setup.rb", I get [.......] No library stubs found. Successfully built RubyGem Name: sources Version: 0.0.1 File: sources-0.0.1.gem hook /home/gavin/projects/rubygems/./post-install.rb failed: wrong number of arguments (1 for 2) Try 'ruby setup.rb --help' for detailed usage. I can't see what it might mean by looking at post-install.rb, so I just remove that file and run setup.rb again. ::shrug:: Gavin From hgs at dmu.ac.uk Mon Mar 14 06:23:52 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Mon Mar 14 06:19:29 2005 Subject: [Rubygems-developers] 'nodoc' errors -- may be nothing... In-Reply-To: References: Message-ID: On Fri, 11 Mar 2005, Chad Fowler wrote: > > Hugh, if you run rdoc directly against your installed log4r source, you'll > see that you get the same errors. The errors are being reported by RDoc and OK. > not by RubyGems. I'm not sure what causes them, but it would be best to ask > Dave, probably. Well, I'll probably wait till the new maintainer steps forward, in that case, at least I know there's no real problem. Thank you. > > Chad Hugh From chad at chadfowler.com Mon Mar 14 09:49:30 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Mon Mar 14 08:38:32 2005 Subject: [Rubygems-developers] Major problem with 0.8.7 Message-ID: <65039.208.252.131.52.1110811770.squirrel@208.252.131.52> Jim, The source index on the server wasn't updating for remote installs of the new version. Rich and I looked at it, and it was actually skipping the 0.8.7 gem. So, I downloaded the gem and tried to install it locally. I got this: ERROR: Error installing gem rubygems-update-0.8.7.gem[.gem]: uninitialized cons tant Gem::Requirement I noticed last night that you moved Requirement up out of Version. I guess this is the problem, but I'm not sure exactly why (I'm a bit delirious with fever now, so I'm probably not going to figure it out either :) Chad From hgs at dmu.ac.uk Mon Mar 14 09:37:07 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Mon Mar 14 09:33:14 2005 Subject: [Rubygems-developers] 0.8.[67] should reject ruby 1.6.x ??? Message-ID: I tried to install rubygems 0.8.6 on a system that accidentally picked up the wrong version of Ruby (1.6.8) and thus the postinstall failed. I've not looked into how to implement this for 0.8.7, but would it be a good idea to die gracefully earlier if the version of ruby is too old? Thank you Hugh From jim at weirichhouse.org Mon Mar 14 10:02:08 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Mon Mar 14 09:57:37 2005 Subject: [Rubygems-developers] Major problem with 0.8.7 In-Reply-To: <65039.208.252.131.52.1110811770.squirrel@208.252.131.52> References: <65039.208.252.131.52.1110811770.squirrel@208.252.131.52> Message-ID: <35926.192.223.163.5.1110812528.squirrel@weirichhouse.org> chad@chadfowler.com said: > Jim, > > The source index on the server wasn't updating for remote installs of > the new version. Rich and I looked at it, and it was actually skipping > the 0.8.7 gem. So, I downloaded the gem and tried to install it > locally. I got this: > > ERROR: Error installing gem rubygems-update-0.8.7.gem[.gem]: > uninitialized constant Gem::Requirement > > I noticed last night that you moved Requirement up out of Version. I > guess this is the problem, but I'm not sure exactly why (I'm a bit > delirious with fever now, so I'm probably not going to figure it out > either :) Rats. It's a bootstrap problem. The Requirement object is in the Gem spec file and the existing software needs to load the gemspec. Sorry, I should have tried updating the gem with an older version of the gem software. I won't have a chance to fix this until this evening. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From chad at chadfowler.com Mon Mar 14 11:10:30 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Mon Mar 14 09:59:31 2005 Subject: [Rubygems-developers] 0.8.[67] should reject ruby 1.6.x ??? In-Reply-To: References: Message-ID: <1797.208.252.131.52.1110816630.squirrel@208.252.131.52> > I tried to install rubygems 0.8.6 on a system that accidentally > picked up the wrong version of Ruby (1.6.8) and thus the postinstall > failed. I've not looked into how to implement this for 0.8.7, but > would it be a good idea to die gracefully earlier if the version of > ruby is too old? > Hey Hugh. Good idea. We added the check to the RubyGems 'gem' script, but we didn't add it to setup.rb. Chad From hgs at dmu.ac.uk Mon Mar 14 10:22:19 2005 From: hgs at dmu.ac.uk (Hugh Sasse Staff Elec Eng) Date: Mon Mar 14 10:21:22 2005 Subject: [Rubygems-developers] 0.8.[67] should reject ruby 1.6.x ??? In-Reply-To: <1797.208.252.131.52.1110816630.squirrel@208.252.131.52> References: <1797.208.252.131.52.1110816630.squirrel@208.252.131.52> Message-ID: On Mon, 14 Mar 2005 chad@chadfowler.com wrote: > Hey Hugh. Good idea. We added the check to the RubyGems 'gem' script, > but we didn't add it to setup.rb. Thank you. One thing I really like about the Ruby community is that people accept constructive suggestions, rather than responding with the fast backhand "Send us a patch/fix it yourself". When I'm familiar with internals I do send patches where I can, of course, but being able to contribute at a lower level of familiarity is great. > > Chad > Thank you, Hugh From chad at chadfowler.com Mon Mar 14 11:41:10 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Mon Mar 14 10:30:12 2005 Subject: [Rubygems-developers] 0.8.[67] should reject ruby 1.6.x ??? In-Reply-To: References: <1797.208.252.131.52.1110816630.squirrel@208.252.131.52> Message-ID: <2415.208.252.131.52.1110818470.squirrel@208.252.131.52> > On Mon, 14 Mar 2005 chad@chadfowler.com wrote: > >> Hey Hugh. Good idea. We added the check to the RubyGems 'gem' script, >> but we didn't add it to setup.rb. > > Thank you. One thing I really like about the Ruby community is that > people accept constructive suggestions, rather than responding with > the fast backhand "Send us a patch/fix it yourself". When I'm > familiar with internals I do send patches where I can, of course, > but being able to contribute at a lower level of familiarity is > great. > > Yes, I like that about the Ruby community too. FYI, I've added this change to our official TODO list. Chad From jim at weirichhouse.org Wed Mar 16 23:24:10 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Mar 16 23:20:44 2005 Subject: [Rubygems-developers] Fixed require_gem bug with redundent requests. Message-ID: <200503162324.10617.jim@weirichhouse.org> I've been working with Tobias Luetke in tracking down a gems bug where multiple versions of a gem is requested. I've committed a fix to CVS. Since this touches on some pretty basic functionality, I would like to have more heads looking at it. The change is in Gem.activate and affects the way multiple requests for the same gem (with possibly conflicting version constraints) are handled. So, if you could download the CVS version and give it a try with as many applications as you can, I would appreciate it. Thanks. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From lumbergh at gmail.com Sun Mar 20 17:05:32 2005 From: lumbergh at gmail.com (Peter Marreck) Date: Sun Mar 20 17:00:48 2005 Subject: [Rubygems-developers] Need to know how to get a particular Ruby install to "see" a particular gem In-Reply-To: <200503141530.j2EFUDdS001731@rubyforge.org> References: <200503141530.j2EFUDdS001731@rubyforge.org> Message-ID: Here's the situation- I'm on OS X. "ruby -v" shows 1.8.2. I've installed "sqlite", "sqlite-ruby", "sqlite3" (at some point) and "sqlite3-ruby" via Gems. The command-line version of these utilities works fine (I can edit database info, etc.). "gem list" shows the following. ----- sqlite (2.0.1) ... sqlite-ruby (2.2.3, 2.2.2) ... sqlite3-ruby (1.1.0, 0.9.0) ... ----- Yet the line "require 'sqlite'" still fails in Apache with: [error] mod_ruby: /placeholder/path/to/rubytest.rbx:4:in `require': No such file to load -- sqlite (LoadError) What am I missing here? Is there a Ruby or Gem config file that I can use to point Ruby at the installed location of these gems? Help! Thanks ahead of time! -Peter From lists at atrus.org Sun Mar 20 18:54:19 2005 From: lists at atrus.org (Nikolas 'Atrus' Coukouma) Date: Sun Mar 20 18:48:20 2005 Subject: [Rubygems-developers] Need to know how to get a particular Ruby install to "see" a particular gem In-Reply-To: References: <200503141530.j2EFUDdS001731@rubyforge.org> Message-ID: <423E0D2B.8000106@atrus.org> You have to use: require 'rubygems'; require_gem 'gem-name'; Cheers, -Nikolas Peter Marreck wrote: >Here's the situation- I'm on OS X. "ruby -v" shows 1.8.2. I've >installed "sqlite", "sqlite-ruby", "sqlite3" (at some point) and >"sqlite3-ruby" via Gems. The command-line version of these utilities >works fine (I can edit database info, etc.). "gem list" shows the >following. >----- >sqlite (2.0.1) > ... >sqlite-ruby (2.2.3, 2.2.2) > ... >sqlite3-ruby (1.1.0, 0.9.0) > ... >----- >Yet the line "require 'sqlite'" still fails in Apache with: >[error] mod_ruby: /placeholder/path/to/rubytest.rbx:4:in `require': No >such file to load -- sqlite (LoadError) > >What am I missing here? Is there a Ruby or Gem config file that I can >use to point Ruby at the installed location of these gems? Help! > >Thanks ahead of time! >-Peter > > From tobias.luetke at gmail.com Tue Mar 22 09:57:50 2005 From: tobias.luetke at gmail.com (Tobias Luetke) Date: Tue Mar 22 09:53:02 2005 Subject: [Rubygems-developers] Some errors Message-ID: <9963c1bd05032206574d2d644b@mail.gmail.com> Hello, I'm running gems 0.8.8.1 (thanks to jim and the fix about version pinning) but ran in some problems this morning upgrading rails. I attach a transcript of what happened, basically i had to run gem update multiple times to finish the process. Its only my CVS version as others seem to update just fine. Feel free to ignore this. -- Tobi http://www.snowdevil.ca - Snowboards that don't suck http://www.hieraki.org - Open source book authoring http://blog.leetsoft.com - Technical weblog -------------- next part -------------- Last login: Tue Mar 22 09:00:57 on console Welcome to Darwin! tobi@tobmac tobi $ gem update Password: Upgrading installed gems... Updating Gem source index for: http://gems.rubyforge.org Attempting remote upgrade of actionmailer Attempting remote installation of 'actionmailer' Install required dependency actionpack? [Yn] y Install required dependency activesupport? [Yn] y /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:195:in `report_activate_error': RubyGem version error: activesupport(1.0.0 not = 1.0.2) (Gem::LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:137:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:38:in `require_gem_with_options' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:60:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:385:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:489:in `install_dependencies' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:485:in `each' ... 9 levels... from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:92:in `process_args' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:65:in `run' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:9:in `run' from /usr/local/bin/gem:17 tobi@tobmac tobi $ gem update Upgrading installed gems... Attempting remote upgrade of actionmailer Attempting remote installation of 'actionmailer' Install required dependency actionpack? [Yn] y /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:195:in `report_activate_error': RubyGem version error: actionpack(1.4.0 not = 1.6.0) (Gem::LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:137:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:38:in `require_gem_with_options' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:60:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:385:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:179:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:694:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:49:in `invoke' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:92:in `process_args' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:65:in `run' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:9:in `run' from /usr/local/bin/gem:17 tobi@tobmac tobi $ gem update Upgrading installed gems... Attempting remote upgrade of actionmailer Attempting remote installation of 'actionmailer' Successfully installed actionmailer-0.8.0 Installing RDoc documentation for actionmailer-0.8.0... Attempting remote upgrade of actionwebservice Attempting remote installation of 'actionwebservice' Install required dependency activerecord? [Yn] y /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:195:in `report_activate_error': RubyGem version error: activerecord(1.6.0 not = 1.9.0) (Gem::LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:137:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:38:in `require_gem_with_options' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:60:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:385:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:179:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:694:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:49:in `invoke' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:92:in `process_args' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:65:in `run' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:9:in `run' from /usr/local/bin/gem:17 tobi@tobmac tobi $ gem update Upgrading installed gems... Attempting remote upgrade of actionwebservice Attempting remote installation of 'actionwebservice' Successfully installed actionwebservice-0.6.1 Installing RDoc documentation for actionwebservice-0.6.1... Attempting remote upgrade of rails Attempting remote installation of 'rails' Install required dependency actionwebservice? [Yn] y /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:195:in `report_activate_error': RubyGem version error: actionwebservice(0.6.0 not = 0.6.1) (Gem::LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:137:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:38:in `require_gem_with_options' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:60:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:58:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/remote_installer.rb:385:in `install' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:179:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:137:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:694:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:690:in `execute' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:49:in `invoke' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:92:in `process_args' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:65:in `run' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:9:in `run' from /usr/local/bin/gem:17 tobi@tobmac tobi $ gem update Upgrading installed gems... Attempting remote upgrade of rails Attempting remote installation of 'rails' Successfully installed rails-0.11.0 Gems: [rails] updated tobi@tobmac tobi $ gem dependency rails Gem rails-0.9.5 Requires rake (>= 0.4.15) activerecord (>= 1.6.0) actionpack (>= 1.4.0) actionmailer (>= 0.6.1) Gem rails-0.10.1 Requires rake (>= 0.4.15) activesupport (= 1.0.1) activerecord (= 1.8.0) actionpack (= 1.5.1) actionmailer (= 0.7.1) actionwebservice (= 0.6.0) Gem rails-0.11.0 Requires rake (>= 0.4.15) activesupport (= 1.0.2) activerecord (= 1.9.0) actionpack (= 1.6.0) actionmailer (= 0.8.0) actionwebservice (= 0.6.1) From jim at weirichhouse.org Tue Mar 22 12:31:40 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Tue Mar 22 12:26:52 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <9963c1bd05032206574d2d644b@mail.gmail.com> References: <9963c1bd05032206574d2d644b@mail.gmail.com> Message-ID: <24957.192.223.163.5.1111512700.squirrel@weirichhouse.org> Tobias Luetke said: > Hello, > > I'm running gems 0.8.8.1 (thanks to jim and the fix about version > pinning) but ran in some problems this > morning upgrading rails. > > I attach a transcript of what happened, basically i had to run gem > update multiple times to finish the process. > > Its only my CVS version as others seem to update just fine. Feel free > to ignore this. Thanks ... I will check this out this evening. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Wed Mar 23 08:17:56 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Mar 23 09:03:38 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <24957.192.223.163.5.1111512700.squirrel@weirichhouse.org> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <24957.192.223.163.5.1111512700.squirrel@weirichhouse.org> Message-ID: <200503230817.56727.jim@weirichhouse.org> On Tuesday 22 March 2005 12:31 pm, Jim Weirich wrote: > Tobias Luetke said: > > Hello, > > > > I'm running gems 0.8.8.1 (thanks to jim and the fix about version > > pinning) but ran in some problems this > > morning upgrading rails. > > > > I attach a transcript of what happened, basically i had to run gem > > update multiple times to finish the process. > > > > Its only my CVS version as others seem to update just fine. Feel free > > to ignore this. > > Thanks ... I will check this out this evening. The latest CVS version (0.8.8.2) has a fix for this. It needs more testing before release, but if you could try it out, I would appreciate it. Thanks. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From tobias.luetke at gmail.com Wed Mar 23 10:06:17 2005 From: tobias.luetke at gmail.com (Tobias Luetke) Date: Wed Mar 23 10:01:26 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <200503230817.56727.jim@weirichhouse.org> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <24957.192.223.163.5.1111512700.squirrel@weirichhouse.org> <200503230817.56727.jim@weirichhouse.org> Message-ID: <9963c1bd05032307064004eb83@mail.gmail.com> The 0.8.8.2 installed rails fine. However it installed activesupport a couple times to many but that doesn't do any harm: tobi@tobmac rubygems $ gem install rails Attempting local installation of 'rails' Local gem file not found: rails*.gem Attempting remote installation of 'rails' Updating Gem source index for: http://gems.rubyforge.org Install required dependency activesupport? [Yn] y Install required dependency activerecord? [Yn] y Install required dependency activesupport? [Yn] y Install required dependency actionmailer? [Yn] y Install required dependency actionwebservice? [Yn] y Install required dependency activerecord? [Yn] y Install required dependency activesupport? [Yn] y Install required dependency activesupport? [Yn] y Successfully installed rails-0.11.0 Successfully installed activesupport-1.0.2 Successfully installed activerecord-1.9.0 Successfully installed activesupport-1.0.2 Successfully installed actionmailer-0.8.0 Successfully installed actionwebservice-0.6.1 Successfully installed activerecord-1.9.0 Successfully installed activesupport-1.0.2 Successfully installed activesupport-1.0.2 Installing RDoc documentation for activesupport-1.0.2... Installing RDoc documentation for activerecord-1.9.0... Installing RDoc documentation for activesupport-1.0.2... Installing RDoc documentation for actionmailer-0.8.0... Installing RDoc documentation for actionwebservice-0.6.1... Installing RDoc documentation for activerecord-1.9.0... Installing RDoc documentation for activesupport-1.0.2... Installing RDoc documentation for activesupport-1.0.2... On Wed, 23 Mar 2005 08:17:56 -0500, Jim Weirich wrote: > On Tuesday 22 March 2005 12:31 pm, Jim Weirich wrote: > > Tobias Luetke said: > > > Hello, > > > > > > I'm running gems 0.8.8.1 (thanks to jim and the fix about version > > > pinning) but ran in some problems this > > > morning upgrading rails. > > > > > > I attach a transcript of what happened, basically i had to run gem > > > update multiple times to finish the process. > > > > > > Its only my CVS version as others seem to update just fine. Feel free > > > to ignore this. > > > > Thanks ... I will check this out this evening. > > The latest CVS version (0.8.8.2) has a fix for this. It needs more testing > before release, but if you could try it out, I would appreciate it. > > Thanks. > > -- > -- Jim Weirich jim@weirichhouse.org http://onestepback.org > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) > -- Tobi http://www.snowdevil.ca - Snowboards that don't suck http://www.hieraki.org - Open source book authoring http://blog.leetsoft.com - Technical weblog From jim at weirichhouse.org Wed Mar 23 11:17:36 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Mar 23 11:12:48 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <9963c1bd05032307064004eb83@mail.gmail.com> References: <9963c1bd05032206574d2d644b@mail.gmail.com><24957.192.223.163.5.1111512700.squirrel@weirichhouse.org><200503230817.56727.jim@weirichhouse.org> <9963c1bd05032307064004eb83@mail.gmail.com> Message-ID: <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> Tobias Luetke said: > The 0.8.8.2 installed rails fine. > However it installed activesupport a couple times to many but that > doesn't do any harm: We wanted to make sure it was /really/ installed. :) Technical notes if anyone on the list is interested. Thanks. The root problem is that the installed "activated" a gem to detect if it is installed (activation is the process of putting the gem's directories into Ruby's load path). Since the list of versioned gems changes as the install proceeds the version of activesupport activated early in the install cycle can be different that one activated later (ie. after activesupport has been upgraded). Since 0.8.8.1 make activation of different versions an error (it always /should/ have been an error), the install cycle can cause the error you have seen. My fix has been to /not/ use activation during an install (although activation was a simple way to detect errors, it strikes me as a really bad idea ... more below). Instead I just search the source index to see if the dependent software is available (which is what activation does anyways). The duplication above is probably caused by not reloading the in-memory copy of the source index after each installation, causing the installer to not realize that "activesupport" is already installed. That should be an easy fix this evening. BTW, in a related bug, the ICONV problems that a lot of people are reporting are caused by using activation to detect the presence of dependencies. If a gem has an autorequire property, activating the gem will automatically require that piece of the installed gem. The problem is that installation is not the proper time to be autorequiring files and tends to cause errors. There have been a bunch of reported errors with gems over the months where it looks like gems is running non-gem code during installation. This is the reason. Using activation for dependency presence testing is a /bad/ idea, and the above fix addresses this as well. I should have an update available this evening. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From tobias.luetke at gmail.com Wed Mar 23 12:44:33 2005 From: tobias.luetke at gmail.com (Tobias Luetke) Date: Wed Mar 23 12:39:43 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <24957.192.223.163.5.1111512700.squirrel@weirichhouse.org> <200503230817.56727.jim@weirichhouse.org> <9963c1bd05032307064004eb83@mail.gmail.com> <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> Message-ID: <9963c1bd0503230944696ca871@mail.gmail.com> I'm not familiar with gems inner working but perhaps a good approach to this would be to figure out all required libraries at the beginning, .uniq! them and then present a list to the user with things which are about to be installed asking for confirmation. This would cut down on the required amount of confirmations for installing something big like a new rails release as well. On Wed, 23 Mar 2005 16:17:36 -0000 (UTC), Jim Weirich wrote: > > Tobias Luetke said: > > The 0.8.8.2 installed rails fine. > > However it installed activesupport a couple times to many but that > > doesn't do any harm: > > We wanted to make sure it was /really/ installed. :) > > Technical notes if anyone on the list is interested. > > Thanks. The root problem is that the installed "activated" a gem to > detect if it is installed (activation is the process of putting the gem's > directories into Ruby's load path). Since the list of versioned gems > changes as the install proceeds the version of activesupport activated > early in the install cycle can be different that one activated later (ie. > after activesupport has been upgraded). > > Since 0.8.8.1 make activation of different versions an error (it always > /should/ have been an error), the install cycle can cause the error you > have seen. > > My fix has been to /not/ use activation during an install (although > activation was a simple way to detect errors, it strikes me as a really > bad idea ... more below). Instead I just search the source index to see > if the dependent software is available (which is what activation does > anyways). The duplication above is probably caused by not reloading the > in-memory copy of the source index after each installation, causing the > installer to not realize that "activesupport" is already installed. That > should be an easy fix this evening. > > BTW, in a related bug, the ICONV problems that a lot of people are > reporting are caused by using activation to detect the presence of > dependencies. If a gem has an autorequire property, activating the gem > will automatically require that piece of the installed gem. The problem > is that installation is not the proper time to be autorequiring files and > tends to cause errors. There have been a bunch of reported errors with > gems over the months where it looks like gems is running non-gem code > during installation. This is the reason. Using activation for dependency > presence testing is a /bad/ idea, and the above fix addresses this as > well. > > I should have an update available this evening. > > -- > -- Jim Weirich jim@weirichhouse.org http://onestepback.org > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) > > -- Tobi http://www.snowdevil.ca - Snowboards that don't suck http://www.hieraki.org - Open source book authoring http://blog.leetsoft.com - Technical weblog From jim at weirichhouse.org Wed Mar 23 14:25:54 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Mar 23 14:21:04 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <9963c1bd0503230944696ca871@mail.gmail.com> References: <9963c1bd05032206574d2d644b@mail.gmail.com><24957.192.223.163.5.1111512700.squirrel@weirichhouse.org><200503230817.56727.jim@weirichhouse.org><9963c1bd05032307064004eb83@mail.gmail.com><63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> <9963c1bd0503230944696ca871@mail.gmail.com> Message-ID: <54784.192.223.163.5.1111605954.squirrel@weirichhouse.org> Tobias Luetke said: > I'm not familiar with gems inner working but perhaps a good approach > to this would be > to figure out all required libraries at the beginning, .uniq! them and > then present a list to the user with > things which are about to be installed asking for confirmation. This > would cut down on the required amount of confirmations for installing > something big like a new rails release as well. The next *big* item on my RubyGems todo list is the Remote/Local installer merge. We will be reworking the installer logic based on what we have learned over the past year. Part of the plan is to determine the list of require modules upfront. Asking for a single confirmation would be an easy thing to do in that case. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Thu Mar 24 01:08:25 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Thu Mar 24 01:03:53 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <9963c1bd05032307064004eb83@mail.gmail.com> <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> Message-ID: <200503240108.25796.jim@weirichhouse.org> On Wednesday 23 March 2005 11:17 am, Jim Weirich wrote: > Tobias Luetke said: > > The 0.8.8.2 installed rails fine. > > However it installed activesupport a couple times to many but that > > doesn't do any harm: > > We wanted to make sure it was /really/ installed. :) The multiple install issue is fixed. The CVS version is marked 0.8.8.3. I'm thinking that on Friday I can get a new release out and let it hit the streets for a bit before Curt needs to cut his one-click installer release. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From gsinclair at soyabean.com.au Thu Mar 24 01:30:59 2005 From: gsinclair at soyabean.com.au (Gavin Sinclair) Date: Thu Mar 24 01:27:18 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <200503240108.25796.jim@weirichhouse.org> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <9963c1bd05032307064004eb83@mail.gmail.com> <63061.192.223.163.5.1111594656.squirrel@weirichhouse.org> <200503240108.25796.jim@weirichhouse.org> Message-ID: <178810594993.20050324173059@soyabean.com.au> On Thursday, March 24, 2005, 5:08:25 PM, Jim wrote: > The multiple install issue is fixed. The CVS version is marked 0.8.8.3. I'm > thinking that on Friday I can get a new release out and let it hit the > streets for a bit before Curt needs to cut his one-click installer release. gem update --system is spoiling you :) Gavin From jim at weirichhouse.org Thu Mar 24 06:30:18 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Thu Mar 24 06:25:44 2005 Subject: [Rubygems-developers] Some errors In-Reply-To: <178810594993.20050324173059@soyabean.com.au> References: <9963c1bd05032206574d2d644b@mail.gmail.com> <200503240108.25796.jim@weirichhouse.org> <178810594993.20050324173059@soyabean.com.au> Message-ID: <200503240630.18708.jim@weirichhouse.org> On Thursday 24 March 2005 01:30 am, Gavin Sinclair wrote: > On Thursday, March 24, 2005, 5:08:25 PM, Jim wrote: > > The multiple install issue is fixed. The CVS version is marked 0.8.8.3. > > I'm thinking that on Friday I can get a new release out and let it hit > > the streets for a bit before Curt needs to cut his one-click installer > > release. > > gem update --system is spoiling you :) Release early, release often ... right? Seriously, I just hope I can get it right in one try this time. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Fri Mar 25 15:09:03 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Fri Mar 25 15:04:12 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready Message-ID: <200503251509.03565.jim@weirichhouse.org> Ok, I've got a version of RubyGems I'd like to release. ?Considering the fact that the last releases needed a quick fix after publicly announcing them, I'm announcing them here first, with a view to doing a public announcement in day or two (probably Sunday evening). Two bug fixes in this release (1) Better handling for pinning required versions of libraries (thanks to Tobias Luetke for helping with this one). (2) Better gem update --sysgem handling. I would like some help testing (2), particularly on windows box (which I don't have acces to at the moment). Here's what you need to do to test (2). ?Manually download (do not use the gem update command here!) the 0.8.9.3 version of RubyGems from http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem Then do a local install with it. Something like ? $ gem install rubygems-update-0.8.9.3.gem ? $ update_rubygems should do the trick. ?Version 0.8.9.3 is essentially identical to version 0.8.10, but with a smaller version number. ?That allows us to do the following command ... ? $ gem update --system --source http://onestepback.org/betagems After that installs, double check that the gem command claims to be version 0.8.10. ? $ gem --version ? ? ? # should report 0.8.10 As I mentioned, I'm particularly interested that I didn't break how this works on windows boxes. I also attached the 0.8.10 announcement for review. Thanks to everyone for their help. -- -- Jim Weirich ? ?jim@weirichhouse.org ? ? http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) -------------- next part -------------- = Announce: RubyGems Release 0.8.10 Version 0.8.10 is bug fix release. We address two bugs in this release, one obscure and the other only slightly annoying. In multi-user environments, it is common to supply mulitple versions of gems (for example Rails), allowing individual users to select the version of the gem they desire. This allows a user to be insulated from updates to that gem. RubyGems 0.8.10 fixes a problem where gems could occasionally become confused about the current versions of libraries selected by the user. The other annoying bug is that if there are any existing rubygems-update gems installed, then the "gem update --system" command will download a new udpate, but install the latest update prior to the download. == What is RubyGems? RubyGems is a package management system for Ruby applications and libraries. RubyGems one command download makes installing Ruby software fun and enjoyable again. (Ok, not really.) Many gems are available for download from the RubyForge site. Browse the list of gems with a "gem list --remote" command and download what you need with a simple "gem install ". RubyGems takes care of the details of installing, not only the gem you requested, but also any gems needed by the software you selected. == RubyGems Statistics * About 230 different gems available (I say _about_ because I don't think "Bangkok" and "bangkok" are really different gems). * Over 30,000 downloads of the RubyGems software * 230,075 gem loads If you are interested in finding out when new gems are released, I maintain an RSS feed at http://onestepback.org/gemwatch.rss. == How can I get RubyGems? If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: $ gem update --system (you might need to be admin/root) (Note: You may have to run the command twice if you have any previosly installed rubygems-update gems). If you have an older version of RubyGems installed, then you can still do it in two steps: $ gem install rubygems-update (again, might need to be admin/root) $ update_rubygems (... here too) If you don't have any gems install, there is still the pre-gem approach to getting software ... doing it manually: 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 2. UNPACK INTO A DIRECTORY AND CD THERE 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) == Thanks Thanks to Tobias Luetke for reporting the problem and assisting in tracking it down. Keep those gems coming! -- Jim & Chad (for the RubyGems team) From chad at chadfowler.com Fri Mar 25 16:25:21 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Fri Mar 25 15:13:57 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready In-Reply-To: <200503251509.03565.jim@weirichhouse.org> References: <200503251509.03565.jim@weirichhouse.org> Message-ID: <26584.208.252.131.50.1111785921.squirrel@208.252.131.50> > Ok, I've got a version of RubyGems I'd like to release. Considering the > fact > that the last releases needed a quick fix after publicly announcing them, > I'm > announcing them here first, with a view to doing a public announcement in > day > or two (probably Sunday evening). > > Two bug fixes in this release > > (1) Better handling for pinning required versions of libraries (thanks to > Tobias Luetke for helping with this one). > > (2) Better gem update --sysgem handling. > > I would like some help testing (2), particularly on windows box (which I > don't > have acces to at the moment). > > Here's what you need to do to test (2). Manually download (do not use the > gem > update command here!) the 0.8.9.3 version of RubyGems from > > http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem > > Then do a local install with it. Something like > > $ gem install rubygems-update-0.8.9.3.gem > $ update_rubygems > > should do the trick. Version 0.8.9.3 is essentially identical to version > 0.8.10, but with a smaller version number. That allows us to do the > following command ... > > $ gem update --system --source http://onestepback.org/betagems > > After that installs, double check that the gem command claims to be > version > 0.8.10. > > $ gem --version # should report 0.8.10 > > As I mentioned, I'm particularly interested that I didn't break how this > works > on windows boxes. > > I also attached the 0.8.10 announcement for review. > > Thanks to everyone for their help. > So far, it looks like it's working fine for me on Windows. I followed the steps above to get 0.8.10 and have successfully upgraded rails and installed and searched on a few other gems. Cool! Chad From curt at hibbs.com Fri Mar 25 15:25:18 2005 From: curt at hibbs.com (Curt Hibbs) Date: Fri Mar 25 15:20:39 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready In-Reply-To: <200503251509.03565.jim@weirichhouse.org> References: <200503251509.03565.jim@weirichhouse.org> Message-ID: <424473AE.6020600@hibbs.com> Jim Weirich wrote: > Ok, I've got a version of RubyGems I'd like to release. Considering the fact > that the last releases needed a quick fix after publicly announcing them, I'm > announcing them here first, with a view to doing a public announcement in day > or two (probably Sunday evening). > > Two bug fixes in this release > > (1) Better handling for pinning required versions of libraries (thanks to > Tobias Luetke for helping with this one). > > (2) Better gem update --sysgem handling. > > I would like some help testing (2), particularly on windows box (which I don't > have acces to at the moment). > > Here's what you need to do to test (2). Manually download (do not use the gem > update command here!) the 0.8.9.3 version of RubyGems from > > http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem > > Then do a local install with it. Something like > > $ gem install rubygems-update-0.8.9.3.gem > $ update_rubygems > > should do the trick. Version 0.8.9.3 is essentially identical to version > 0.8.10, but with a smaller version number. That allows us to do the > following command ... > > $ gem update --system --source http://onestepback.org/betagems > > After that installs, double check that the gem command claims to be version > 0.8.10. > > $ gem --version # should report 0.8.10 > > As I mentioned, I'm particularly interested that I didn't break how this works > on windows boxes. > > I also attached the 0.8.10 announcement for review. > > Thanks to everyone for their help. > > > > ------------------------------------------------------------------------ > > = Announce: RubyGems Release 0.8.10 > > Version 0.8.10 is bug fix release. We address two bugs in this > release, one obscure and the other only slightly annoying. > > In multi-user environments, it is common to supply mulitple versions > of gems (for example Rails), allowing individual users to select the > version of the gem they desire. This allows a user to be insulated > from updates to that gem. RubyGems 0.8.10 fixes a problem where gems > could occasionally become confused about the current versions of > libraries selected by the user. > > The other annoying bug is that if there are any existing > rubygems-update gems installed, then the "gem update --system" command > will download a new udpate, but install the latest update prior to the > download. > > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == RubyGems Statistics > > * About 230 different gems available (I say _about_ because I don't > think "Bangkok" and "bangkok" are really different gems). > * Over 30,000 downloads of the RubyGems software > * 230,075 gem loads > > If you are interested in finding out when new gems are released, I > maintain an RSS feed at http://onestepback.org/gemwatch.rss. > > == How can I get RubyGems? > > If you have a recent version of RubyGems (0.8.5 or later), then all > you need to do is: > > $ gem update --system (you might need to be admin/root) > > (Note: You may have to run the command twice if you have any previosly > installed rubygems-update gems). > > If you have an older version of RubyGems installed, then you can still > do it in two steps: > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > If you don't have any gems install, there is still the pre-gem > approach to getting software ... doing it manually: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) > > == Thanks > > Thanks to Tobias Luetke for reporting the problem and assisting in > tracking it down. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) I'll try this tonight on my windows box. Curt From tobias.luetke at gmail.com Fri Mar 25 15:49:06 2005 From: tobias.luetke at gmail.com (Tobias Luetke) Date: Fri Mar 25 15:44:09 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready In-Reply-To: <200503251509.03565.jim@weirichhouse.org> References: <200503251509.03565.jim@weirichhouse.org> Message-ID: <9963c1bd05032512496dcc7bce@mail.gmail.com> I tried it on my windows box and went from 0.8.1 (!) to 0.8.10 no problems. I also ran gem update to and it completed successfully: Gems: [actionmailer, actionpack, activerecord, rails, rake, sqlite-ruby] updated On Fri, 25 Mar 2005 15:09:03 -0500, Jim Weirich wrote: > Ok, I've got a version of RubyGems I'd like to release. Considering the fact > that the last releases needed a quick fix after publicly announcing them, I'm > announcing them here first, with a view to doing a public announcement in day > or two (probably Sunday evening). > > Two bug fixes in this release > > (1) Better handling for pinning required versions of libraries (thanks to > Tobias Luetke for helping with this one). > > (2) Better gem update --sysgem handling. > > I would like some help testing (2), particularly on windows box (which I don't > have acces to at the moment). > > Here's what you need to do to test (2). Manually download (do not use the gem > update command here!) the 0.8.9.3 version of RubyGems from > > http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem > > Then do a local install with it. Something like > > $ gem install rubygems-update-0.8.9.3.gem > $ update_rubygems > > should do the trick. Version 0.8.9.3 is essentially identical to version > 0.8.10, but with a smaller version number. That allows us to do the > following command ... > > $ gem update --system --source http://onestepback.org/betagems > > After that installs, double check that the gem command claims to be version > 0.8.10. > > $ gem --version # should report 0.8.10 > > As I mentioned, I'm particularly interested that I didn't break how this works > on windows boxes. > > I also attached the 0.8.10 announcement for review. > > Thanks to everyone for their help. > > -- > -- Jim Weirich jim@weirichhouse.org http://onestepback.org > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) > > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > > > > -- Tobi http://www.snowdevil.ca - Snowboards that don't suck http://www.hieraki.org - Open source book authoring http://blog.leetsoft.com - Technical weblog From curt at hibbs.com Sat Mar 26 00:08:27 2005 From: curt at hibbs.com (Curt Hibbs) Date: Sat Mar 26 00:03:36 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready In-Reply-To: <200503251509.03565.jim@weirichhouse.org> References: <200503251509.03565.jim@weirichhouse.org> Message-ID: <4244EE4B.9000705@hibbs.com> Jim Weirich wrote: > Ok, I've got a version of RubyGems I'd like to release. Considering the fact > that the last releases needed a quick fix after publicly announcing them, I'm > announcing them here first, with a view to doing a public announcement in day > or two (probably Sunday evening). > > Two bug fixes in this release > > (1) Better handling for pinning required versions of libraries (thanks to > Tobias Luetke for helping with this one). > > (2) Better gem update --sysgem handling. > > I would like some help testing (2), particularly on windows box (which I don't > have acces to at the moment). > > Here's what you need to do to test (2). Manually download (do not use the gem > update command here!) the 0.8.9.3 version of RubyGems from > > http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem > > Then do a local install with it. Something like > > $ gem install rubygems-update-0.8.9.3.gem > $ update_rubygems > > should do the trick. Version 0.8.9.3 is essentially identical to version > 0.8.10, but with a smaller version number. That allows us to do the > following command ... > > $ gem update --system --source http://onestepback.org/betagems > > After that installs, double check that the gem command claims to be version > 0.8.10. > > $ gem --version # should report 0.8.10 > > As I mentioned, I'm particularly interested that I didn't break how this works > on windows boxes. > > I also attached the 0.8.10 announcement for review. > > Thanks to everyone for their help. > > > > ------------------------------------------------------------------------ > > = Announce: RubyGems Release 0.8.10 > > Version 0.8.10 is bug fix release. We address two bugs in this > release, one obscure and the other only slightly annoying. > > In multi-user environments, it is common to supply mulitple versions > of gems (for example Rails), allowing individual users to select the > version of the gem they desire. This allows a user to be insulated > from updates to that gem. RubyGems 0.8.10 fixes a problem where gems > could occasionally become confused about the current versions of > libraries selected by the user. > > The other annoying bug is that if there are any existing > rubygems-update gems installed, then the "gem update --system" command > will download a new udpate, but install the latest update prior to the > download. > > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == RubyGems Statistics > > * About 230 different gems available (I say _about_ because I don't > think "Bangkok" and "bangkok" are really different gems). > * Over 30,000 downloads of the RubyGems software > * 230,075 gem loads > > If you are interested in finding out when new gems are released, I > maintain an RSS feed at http://onestepback.org/gemwatch.rss. > > == How can I get RubyGems? > > If you have a recent version of RubyGems (0.8.5 or later), then all > you need to do is: > > $ gem update --system (you might need to be admin/root) > > (Note: You may have to run the command twice if you have any previosly > installed rubygems-update gems). > > If you have an older version of RubyGems installed, then you can still > do it in two steps: > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > If you don't have any gems install, there is still the pre-gem > approach to getting software ... doing it manually: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) > > == Thanks > > Thanks to Tobias Luetke for reporting the problem and assisting in > tracking it down. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) It worked fine for me, too (on windows)! Curt From curt at hibbs.com Sat Mar 26 01:08:20 2005 From: curt at hibbs.com (Curt Hibbs) Date: Sat Mar 26 01:03:23 2005 Subject: [Rubygems-developers] RubyGems 0.8.10 Prerelease Ready In-Reply-To: <200503251509.03565.jim@weirichhouse.org> References: <200503251509.03565.jim@weirichhouse.org> Message-ID: <4244FC54.3050007@hibbs.com> This weekend I starting the process of putting together the next release of the one-click ruby installer. As soon as you guys release this version of RubyGems, I'll grab it and build it in. Curt Jim Weirich wrote: > Ok, I've got a version of RubyGems I'd like to release. Considering the fact > that the last releases needed a quick fix after publicly announcing them, I'm > announcing them here first, with a view to doing a public announcement in day > or two (probably Sunday evening). > > Two bug fixes in this release > > (1) Better handling for pinning required versions of libraries (thanks to > Tobias Luetke for helping with this one). > > (2) Better gem update --sysgem handling. > > I would like some help testing (2), particularly on windows box (which I don't > have acces to at the moment). > > Here's what you need to do to test (2). Manually download (do not use the gem > update command here!) the 0.8.9.3 version of RubyGems from > > http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem > > Then do a local install with it. Something like > > $ gem install rubygems-update-0.8.9.3.gem > $ update_rubygems > > should do the trick. Version 0.8.9.3 is essentially identical to version > 0.8.10, but with a smaller version number. That allows us to do the > following command ... > > $ gem update --system --source http://onestepback.org/betagems > > After that installs, double check that the gem command claims to be version > 0.8.10. > > $ gem --version # should report 0.8.10 > > As I mentioned, I'm particularly interested that I didn't break how this works > on windows boxes. > > I also attached the 0.8.10 announcement for review. > > Thanks to everyone for their help. > > > > ------------------------------------------------------------------------ > > = Announce: RubyGems Release 0.8.10 > > Version 0.8.10 is bug fix release. We address two bugs in this > release, one obscure and the other only slightly annoying. > > In multi-user environments, it is common to supply mulitple versions > of gems (for example Rails), allowing individual users to select the > version of the gem they desire. This allows a user to be insulated > from updates to that gem. RubyGems 0.8.10 fixes a problem where gems > could occasionally become confused about the current versions of > libraries selected by the user. > > The other annoying bug is that if there are any existing > rubygems-update gems installed, then the "gem update --system" command > will download a new udpate, but install the latest update prior to the > download. > > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == RubyGems Statistics > > * About 230 different gems available (I say _about_ because I don't > think "Bangkok" and "bangkok" are really different gems). > * Over 30,000 downloads of the RubyGems software > * 230,075 gem loads > > If you are interested in finding out when new gems are released, I > maintain an RSS feed at http://onestepback.org/gemwatch.rss. > > == How can I get RubyGems? > > If you have a recent version of RubyGems (0.8.5 or later), then all > you need to do is: > > $ gem update --system (you might need to be admin/root) > > (Note: You may have to run the command twice if you have any previosly > installed rubygems-update gems). > > If you have an older version of RubyGems installed, then you can still > do it in two steps: > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > If you don't have any gems install, there is still the pre-gem > approach to getting software ... doing it manually: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) > > == Thanks > > Thanks to Tobias Luetke for reporting the problem and assisting in > tracking it down. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) > > > ------------------------------------------------------------------------ > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers From jim at weirichhouse.org Sun Mar 27 18:11:40 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Sun Mar 27 18:06:46 2005 Subject: [Rubygems-developers] [ANN] RubyGems 0.8.10 Message-ID: <200503271811.40294.jim@weirichhouse.org> = Announce: RubyGems Release 0.8.10 Version 0.8.10 is bug fix release. We address two bugs in this release, one obscure and the other only slightly annoying. In multi-user environments, it is common to supply mulitple versions of gems (for example Rails), allowing individual users to select the version of the gem they desire. This allows a user to be insulated from updates to that gem. RubyGems 0.8.10 fixes a problem where gems could occasionally become confused about the current versions of libraries selected by the user. The other annoying bug is that if there are any existing rubygems-update gems installed, then the "gem update --system" command will download a new udpate, but install the latest update prior to the download. == What is RubyGems? RubyGems is a package management system for Ruby applications and libraries. RubyGems one command download makes installing Ruby software fun and enjoyable again. (Ok, not really.) Many gems are available for download from the RubyForge site. Browse the list of gems with a "gem list --remote" command and download what you need with a simple "gem install ". RubyGems takes care of the details of installing, not only the gem you requested, but also any gems needed by the software you selected. == RubyGems Statistics * About 230 different gems available (I say _about_ because I don't think "Bangkok" and "bangkok" are really different gems). * Over 30,000 downloads of the RubyGems software * 230,075 gem loads If you are interested in finding out when new gems are released, I maintain an RSS feed at http://onestepback.org/gemwatch.rss. == How can I get RubyGems? If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: $ gem update --system (you might need to be admin/root) (Note: You may have to run the command twice if you have any previosly installed rubygems-update gems). If you have an older version of RubyGems installed, then you can still do it in two steps: $ gem install rubygems-update (again, might need to be admin/root) $ update_rubygems (... here too) If you don't have any gems install, there is still the pre-gem approach to getting software ... doing it manually: 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 2. UNPACK INTO A DIRECTORY AND CD THERE 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) == Thanks Thanks to Tobias Luetke for reporting the problem and assisting in tracking it down. Keep those gems coming! -- Jim & Chad (for the RubyGems team) From jim at weirichhouse.org Sun Mar 27 19:51:06 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Sun Mar 27 19:45:55 2005 Subject: [Rubygems-developers] Request for rubygems.org Message-ID: <200503271951.06511.jim@weirichhouse.org> James Britt suggested ... > A request: ?Please add some links to http://www.rubygems.org/ > It seems like a reasonable starting place for people looking for > RubyGems docs, FAQ, etc., but it remains a dark, cryptic page. > I couldn't remember the exact URL for the gems manual, and on each > failed guess ?I ended up on that page, which currently isn't very helpful. Seemed like a reasonable request, so I went ahead and added an unobtrusive link at the bottom of the page. If someone disagrees, feel free to restore the page (I left a copy of the original), or would like to change the way the link is done ... feel free. I just wanted to get something there ASAP. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From curt at hibbs.com Mon Mar 28 00:35:17 2005 From: curt at hibbs.com (Curt Hibbs) Date: Mon Mar 28 00:30:17 2005 Subject: [Rubygems-developers] [ANN] RubyGems 0.8.10 In-Reply-To: <200503271811.40294.jim@weirichhouse.org> References: <200503271811.40294.jim@weirichhouse.org> Message-ID: <42479795.2070702@hibbs.com> Jim Weirich wrote: > = Announce: RubyGems Release 0.8.10 > > Version 0.8.10 is bug fix release. We address two bugs in this > release, one obscure and the other only slightly annoying. > > In multi-user environments, it is common to supply mulitple versions > of gems (for example Rails), allowing individual users to select the > version of the gem they desire. This allows a user to be insulated > from updates to that gem. RubyGems 0.8.10 fixes a problem where gems > could occasionally become confused about the current versions of > libraries selected by the user. > > The other annoying bug is that if there are any existing > rubygems-update gems installed, then the "gem update --system" command > will download a new udpate, but install the latest update prior to the > download. > > == What is RubyGems? > > RubyGems is a package management system for Ruby applications and > libraries. RubyGems one command download makes installing Ruby software > fun and enjoyable again. (Ok, not really.) > > Many gems are available for download from the RubyForge site. Browse > the list of gems with a "gem list --remote" command and download what > you need with a simple "gem install ". RubyGems takes care > of the details of installing, not only the gem you requested, but also > any gems needed by the software you selected. > > == RubyGems Statistics > > * About 230 different gems available (I say _about_ because I don't > think "Bangkok" and "bangkok" are really different gems). > * Over 30,000 downloads of the RubyGems software > * 230,075 gem loads > > If you are interested in finding out when new gems are released, I > maintain an RSS feed at http://onestepback.org/gemwatch.rss. > > == How can I get RubyGems? > > If you have a recent version of RubyGems (0.8.5 or later), then all > you need to do is: > > $ gem update --system (you might need to be admin/root) > > (Note: You may have to run the command twice if you have any previosly > installed rubygems-update gems). > > If you have an older version of RubyGems installed, then you can still > do it in two steps: > > $ gem install rubygems-update (again, might need to be admin/root) > $ update_rubygems (... here too) > > If you don't have any gems install, there is still the pre-gem > approach to getting software ... doing it manually: > > 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 > 2. UNPACK INTO A DIRECTORY AND CD THERE > 3. INSTALL WITH: ruby setup.rb all (you may need admin/root privilege) > > == Thanks > > Thanks to Tobias Luetke for reporting the problem and assisting in > tracking it down. > > Keep those gems coming! > > -- Jim & Chad (for the RubyGems team) Great! I'll grab this for the new one-click installer. Thanks, Curt From assaph at gmail.com Mon Mar 28 20:12:35 2005 From: assaph at gmail.com (Assaph Mehr) Date: Mon Mar 28 20:07:38 2005 Subject: [Rubygems-developers] require issue with 0.8.10 Message-ID: <3ff47be905032817122b9a4764@mail.gmail.com> Hi Guys, The HTMLTools gem, which used to work with gems 0.8.8, now gives me grief using gems 0.8.10 due to (I presume) a behaviour change in #require. I have RUBYOPT=rubygems set on my machine (WinXP, ruby 1.8.2). I used to be able to simply require the files I needed from the gems, e.g.: require 'html/tree' which would load fine. With gems 0.8.10 it doesn't (complaining 'LoadError: No such file to load -- html/tools'). I think that's because all files in the gem are under its lib/html directory, and all files require other files (in the same dir) via require 'html/somefile'. So something now prevents it from picking up those files that are in the same dir. Changing it to: require_gem 'htmltools' # gemspec has autorequire set (or adding the gem/lib dir to $LOAD_PATH) fixes this for me, but I was wondering about the behaviour change. Cheers, Assaph From jim at weirichhouse.org Mon Mar 28 23:40:09 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Mon Mar 28 23:34:50 2005 Subject: [Rubygems-developers] require issue with 0.8.10 In-Reply-To: <3ff47be905032817122b9a4764@mail.gmail.com> References: <3ff47be905032817122b9a4764@mail.gmail.com> Message-ID: <200503282340.09897.jim@weirichhouse.org> On Monday 28 March 2005 08:12 pm, Assaph Mehr wrote: > The HTMLTools gem, which used to work with gems 0.8.8, now gives me > grief using gems 0.8.10 due to (I presume) a behaviour change in > #require. > > I have RUBYOPT=rubygems set on my machine (WinXP, ruby 1.8.2). I used > to be able to simply require the files I needed from the gems, e.g.: > require 'html/tree' > which would load fine. With RUBYOPT set and gem 0.8.10: $ ruby -e 'require "html/tree"; puts "OK"' OK > With gems 0.8.10 it doesn't (complaining > 'LoadError: No such file to load -- html/tools'). What is 'html/tools'? I didn't see any file by that name (although the name of the gem is htmltools). Nor could I find any reference to that file in the source code of htmltools. > I think that's > because all files in the gem are under its lib/html directory, and all > files require other files (in the same dir) via require > 'html/somefile'. That shouldn't be a problem. It's how I have all my projects setup. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From assaph at gmail.com Mon Mar 28 23:56:47 2005 From: assaph at gmail.com (Assaph Mehr) Date: Mon Mar 28 23:51:47 2005 Subject: [Rubygems-developers] require issue with 0.8.10 In-Reply-To: <200503282340.09897.jim@weirichhouse.org> References: <3ff47be905032817122b9a4764@mail.gmail.com> <200503282340.09897.jim@weirichhouse.org> Message-ID: <3ff47be9050328205667fb5a85@mail.gmail.com> > With RUBYOPT set and gem 0.8.10: > > $ ruby -e 'require "html/tree"; puts "OK"' > OK I swear I tested this a dozen times and it failed... until now. > > With gems 0.8.10 it doesn't (complaining > > 'LoadError: No such file to load -- html/tools'). > > What is 'html/tools'? I didn't see any file by that name (although the name > of the gem is htmltools). Nor could I find any reference to that file in the > source code of htmltools. I must have had a brainfart, reading 'tree' where 'tools' was written... Thanks for your patience towards the mentally chalanged ;-) Cheers, Assaph