From owner-freebsd-ports@FreeBSD.ORG Tue Nov 15 01:20:02 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61F1C16A41F for ; Tue, 15 Nov 2005 01:20:02 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from core.inec.ru (core.inec.ru [213.148.3.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E370D43D46 for ; Tue, 15 Nov 2005 01:20:01 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from [213.85.81.137] (helo=[192.168.0.4]) by core.inec.ru with esmtp (Exim 4.51 (FreeBSD)) id 1EbpTm-0002m7-6Y; Tue, 15 Nov 2005 04:19:22 +0300 Message-ID: <437937A7.3040203@FreeBSD.org> Date: Tue, 15 Nov 2005 04:19:35 +0300 From: Sergey Matveychuk User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051113) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <4378E1B9.8060509@mac.com> <20051114193625.GA80577@xor.obsecurity.org> In-Reply-To: <20051114193625.GA80577@xor.obsecurity.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Linimon , FreeBSD - Ports Subject: Re: ruby version going backwards...? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 01:20:02 -0000 Kris Kennaway wrote: > On Mon, Nov 14, 2005 at 02:12:57PM -0500, Chuck Swiger wrote: > >>Hi, all (and Mark in particular :-)-- >> >>I just saw a message about the version for ruby and other ports maintained >>by knu being reset. I'm getting a rather odd update message from >>portupgrade now: >> >>---> Upgrade of lang/ruby18 started at: Mon, 14 Nov 2005 14:06:08 -0500 >>---> Upgrading 'ruby-1.8.3' to 'ruby-1.8.2_5,1' (lang/ruby18) >>OK? [yes] n >> >>Did PORTEPOCH get removed? What is a problem here? 1.8.3<1.8.2,1 > > > No, as you can see there was no PORTEPOCH that was removed :) > > The ruby upgrade was reverted, but this has just caused further > problems :/ If user update both bsd.ruby.mk and lang/ruby18 there is no problem there. Or I something miss? -- Sem.