From owner-freebsd-questions@FreeBSD.ORG Mon Jan 27 12:30:12 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FE44ECE for ; Mon, 27 Jan 2014 12:30:12 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 75C801378 for ; Mon, 27 Jan 2014 12:30:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=igLFMOKkMTH8dqQfEMWxRb07nesb6honfX+ouhOI8og=; b=roorAoLEDL60mOnq/wBt0R4jKqgiIE9JKg31X8MKzfIqDQl7h3V8EzNX36O0gAaPWLquDRckKC5+dCXTjSLwOthyYUyDfs5avEe70rDTQ3FS468qYPxFcUWahUP+KqgKbQ0mEhuBPqokNfkONvMJjAiJiZAqG19So7ZhQpKMhK8=; Received: from [39.217.157.8] (port=17739 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1W7lKM-004Lpx-HR; Mon, 27 Jan 2014 05:30:12 -0700 Date: Mon, 27 Jan 2014 20:30:02 +0800 From: Erich Dollansky To: _1126 Subject: Re: [freebsd-questions] Re: [freebsd-questions] Re: weird error messages with various ports Message-ID: <20140127203002.37fbb036@X220.alogt.com> In-Reply-To: <20140127121011.GA68344@elfsechsundzwanzig.de> References: <20140127120519.Horde.zk6gGzrJZ8n-kUHavzPiTw1@webmail.df.eu> <20140127191858.78a3fa5d@X220.alogt.com> <20140127114919.GA66024@elfsechsundzwanzig.de> <20140127200326.026e6c35@X220.alogt.com> <20140127121011.GA68344@elfsechsundzwanzig.de> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 12:30:12 -0000 Hi, On Mon, 27 Jan 2014 13:10:12 +0100 _1126 wrote: > On Mon, Jan 27, 2014 at 08:03:26PM +0800, Erich Dollansky wrote: > > > > On Mon, 27 Jan 2014 12:49:19 +0100 > > _1126 wrote: > > > > > On Mon, Jan 27, 2014 at 07:18:58PM +0800, Erich Dollansky wrote: > > > > > > > > On Mon, 27 Jan 2014 12:05:19 +0100 > > > > lists@elfsechsundzwanzig.de wrote: > > > > > > > > > This is my first posting on this mailinglist, so I hope I am > > > > > doing everything ok. > > > > > > > > do not worry to much about this. > > > > > > > > > > I am running a 10.0-RELEASE on a Thinkpad X220 - and > > > > > everything was just fine. > > > > > > > > > I do the same. > > > > > > > > > Until I did a > > > > > > > > > > $ sudo portsnap fetch update > > > > > > > > > > today and afterwards a > > > > > > > > > > $ sudo portmaster -aD > > > > > > > > > I did nearly the same either yesterday night or this morning > > > > but I used svn and portupgrade without any problems. > > > > > > > > How old was your ports tree before the upgrade? > > > > > > Three days old. > > > > > ok, get the latest one and try again. If it still does not work, I > > could give you the revision number of my working ports tree. > > It still does not work. However, I do not have a revision number, > IIUC, because I'm updating my ports with portsnap and not with svn, > right? I might try to checkout ports anew and see whether that works > then. of course. You might should consider to switch to svn and portupgrade. There is one advantage of this pair. Portupgrade does not leave you with a machine that cannot be used anymore. The worst case is that no port gets upgraded but your machine still works. Svn has the advantage that you can chose your port 'version' if the current revision does not work for you. Anyway, some other reported the same problem with a current ports tree. I have the revision number 341159 in case of you want to try. Erich