From owner-cvs-ports@FreeBSD.ORG Thu Dec 2 13:15:27 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AF7E16A4CE; Thu, 2 Dec 2004 13:15:27 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 548EB43D48; Thu, 2 Dec 2004 13:15:26 +0000 (GMT) (envelope-from tilman@arved.at) Received: from jim.arved.de (localhost [127.0.0.1])iB2DFOP7021648; Thu, 2 Dec 2004 14:15:24 +0100 (CET) (envelope-from tilman@arved.at) Received: (from arved@localhost) by jim.arved.de (8.13.1/8.13.1/Submit) id iB2DFOHU021647; Thu, 2 Dec 2004 14:15:24 +0100 (CET) (envelope-from tilman@arved.at) X-Authentication-Warning: jim.arved.de: arved set sender to tilman@arved.at using -f Date: Thu, 2 Dec 2004 14:15:24 +0100 From: Tilman Linneweh To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Message-ID: <20041202131524.GB8793@arved.at> References: <200412011855.iB1ItKHC005936@repoman.freebsd.org> <20041202014558.GU18619@hex.databits.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202014558.GU18619@hex.databits.net> User-Agent: Mutt/1.4.2.1i Subject: Re: operation of addport & modulesupdate in particular (was Re: cvs commit: CVSROOT modules) X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 13:15:27 -0000 * Will Andrews [2004-12-02 02:46]: > > X-Mas whish: Santa Claus, please fix addport for me > > Nothing wrong with it; been using it since I wrote it almost 5 > years ago, without any trouble. It can be blamed for several > thousand CVSROOT/modules changes since then. :) > > My usual reply to this recurring issue is: Yes I know this, that's why I asked Santa and not you to fix it :-). > > Make sure your ssh configuration works the way it does, i.e. can > ssh to freefall from committing location and subsequently from > there to repoman - usually involves ssh-agent or another key that > is local to the freebsd.org cluster. modulesupdate worked for me nearly two years and dozens of ports, but oneday it stopped (between Feb 13 and May 22). I am still committing from the same machines, i can ssh to freefall and further to repoman without entering a passphrase. So I have no idea, why modulesupdate does not like me anymore, but i still believe in Santa Claus' ability to fix it :-) regards tilman