From owner-freebsd-ports@FreeBSD.ORG Sat Jan 4 14:41:33 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCAAAD81 for ; Sat, 4 Jan 2014 14:41:33 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CCC2167C for ; Sat, 4 Jan 2014 14:41:33 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 2CFEEBDC44; Sat, 4 Jan 2014 15:41:32 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id 0D879BDC3E; Sat, 4 Jan 2014 15:41:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id A34E1CB5DE23; Sat, 4 Jan 2014 15:41:31 +0100 (CET) Date: Sat, 04 Jan 2014 15:41:31 +0100 From: Mathieu Arnold To: Marco Beishuizen , freebsd-ports@freebsd.org Subject: Re: how to install ruby18 Message-ID: <9F088A2B56BC5D46E2C5A3E5@atuin.in.mat.cc> In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 14:41:33 -0000 +--On 4 janvier 2014 15:21:07 +0100 Marco Beishuizen wrote: | Hi, | | Since portupgrade doesn't work with the default ruby19 ("invalid byte | sequence" errors) I want to reinstall ruby18 instead. But ruby18 has been | removed from the ports, so how can I install ruby18 again? That error may come from a non us-ascii character in portupgrade's configuration files. -- Mathieu Arnold