From owner-freebsd-ports@FreeBSD.ORG Sat Jun 16 13:40:27 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF228106566B; Sat, 16 Jun 2012 13:40:27 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6438A8FC0A; Sat, 16 Jun 2012 13:40:27 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so2603395vcb.13 for ; Sat, 16 Jun 2012 06:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2G0T+A3BzA00w5r2gshWoc+YDeIcl/0nDigQgdIdMLA=; b=YSE4v23IGCBJVrv372Ns4AWuO/h6acKDEVh9MEDAA3hfJ9q80mH6biG1Uxy+b+ATt9 PeujymXYiJ/H8GD4X/M8YYzuFyhxVcABKW+QbgmpMmfKtClVzwkEqsJwbECZyZuZ5Qwp MYFOwwT2xpP7ThHPCzc6eq7ElzTRGgpj4F9iLo9bZHoAIPSBgL9AlLiMRkNgQN6b/rB5 BxCBHA+CnWTUhOYRtK2cNvVkC2xWny6lygHdqjZ1TnI9+1jRuPZMhro4zP7kj/zGCFOc 4Nc/rkToVRl0/ZXCY4U0PWnbRcycwMa+PGN1LNzGBNy2ZMDKQNzGV4tGWaIMiw9yW98D 4scw== MIME-Version: 1.0 Received: by 10.220.222.16 with SMTP id ie16mr4850770vcb.29.1339854021548; Sat, 16 Jun 2012 06:40:21 -0700 (PDT) Received: by 10.52.18.139 with HTTP; Sat, 16 Jun 2012 06:40:21 -0700 (PDT) In-Reply-To: References: Date: Sat, 16 Jun 2012 15:40:21 +0200 Message-ID: From: Torfinn Ingolfsen To: FreeBSD Ports ML , demon@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: p5-Locale-gettext fails 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: Sat, 16 Jun 2012 13:40:27 -0000 On Wed, Jun 13, 2012 at 10:59 PM, Torfinn Ingolfsen wrote: > What's wrong with devel/p5-Locale-gettext all of a sudden? Please ignore, this was a local problem. Turned out the the SSD was starting to corrupt files. Luckily I got a backup off the drive in time, and the SSSD was fixed by upgrading firmware on it. -- Regards, Torfinn Ingolfsen