From owner-freebsd-ruby@FreeBSD.ORG Thu Jul 1 07:30:10 2010 Return-Path: Delivered-To: ruby@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48FB1065676 for ; Thu, 1 Jul 2010 07:30:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B3B538FC1C for ; Thu, 1 Jul 2010 07:30:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o617UA33015957 for ; Thu, 1 Jul 2010 07:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o617UAp7015954; Thu, 1 Jul 2010 07:30:10 GMT (envelope-from gnats) Date: Thu, 1 Jul 2010 07:30:10 GMT Message-Id: <201007010730.o617UAp7015954@freefall.freebsd.org> To: ruby@FreeBSD.org From: "O. Hartmann" Cc: Subject: Re: ports/147809: databases/ruby-dbi: /usr/local/lib/ruby/site_ruby/1.8/dbi/utils/date.rb:57: undefined method `deprecate' for DBI::Date:Class (NoMethodError) X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "O. Hartmann" List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 07:30:10 -0000 The following reply was made to PR ports/147809; it has been noted by GNATS. From: "O. Hartmann" To: argentoff@gmail.com Cc: bug-followup@FreeBSD.org Subject: Re: ports/147809: databases/ruby-dbi: /usr/local/lib/ruby/site_ruby/1.8/dbi/utils/date.rb:57: undefined method `deprecate' for DBI::Date:Class (NoMethodError) Date: Thu, 01 Jul 2010 09:20:43 +0200 On 06/29/10 19:43, Pavel Argentov wrote: > Hello there! > > I've found a workaround. > > I have just found that everything was broken by devel/rubygem-deprecated port. It's version was > changed from 2.0.1 to 3.0.0 with complete syntax and semantics re-write. So to solve the problem we > should either downgrade devel/rubygem-deprecated back to 2.0.1 or rewrite the DBI library. > Hello. deleting and reinstalling necessary ruby-gems by demand can be considered as a temporary workaround. I found some hints regarding this issue in the net, tried it and it worked for me. Regards, Oliver