Any ideas on this? Regards, -Roberto On Wed, Mar 31, 2010 at 09:01:12PM -0400, Roberto C. Sánchez wrote: > > > > > > > > libmemcache-client-ruby1.8 (>> 1.7.4) > > > > This is not maintained within the team. Roberto? > > > I also setup a watchfile for this one. However, upstream has the > following code in the memcache.rb file: > > begin > # Try to use the SystemTimer gem instead of Ruby's timeout library > # when running on something that looks like Ruby 1.8.x. See: > # http://ph7spot.com/articles/system_timer > # We don't want to bother trying to load SystemTimer on jruby and > # ruby 1.9+ > if defined?(JRUBY_VERSION) || (RUBY_VERSION >= '1.9') > require 'timeout' > MemCacheTimer = Timeout > else > require 'system_timer' > MemCacheTimer = SystemTimer > end > rescue LoadError => e > puts "[memcache-client] Could not load SystemTimer gem, falling back to Ruby's slower/unsafe timeout library: #{e.message}" > require 'timeout' > MemCacheTimer = Timeout > end > > Does the problem in the referenced URL apply to the Ruby 1.8 in Debian? > Can I just patch it down to this: > > require 'timeout' > MemCacheTimer = Timeout > > I ask because I do not want to allow a spurious warning to remain. > Recommendations? > > Regards, > > -Roberto > > -- > Roberto C. Sánchez > http://people.connexer.com/~roberto > http://www.connexer.com -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature