Return-Path: Message-ID: <5256d0b05070610026bd6a1cc@mail.gmail.com> From: Peter Robinson To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] Moving over to GCC 4.0 In-Reply-To: <1120669070.18553.2.camel@pegasus> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <1120649879.8836.5.camel@pegasus> <42CBF7A6.7090708@xmission.com> <1120669070.18553.2.camel@pegasus> Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 6 Jul 2005 18:02:51 +0100 Hi Marcel, > > just FYI everybody... sourceforge seems to have broken anonymous cvs > > (both bluez and bluetooth-alsa are affected) > > > > $ cvs update -d > > cvs [update aborted]: unrecognized auth response from cvs.bluez.org: cv= s > > pserver: cannot read /cvsroot/bluez/CVSROOT/config: Input/output error >=20 > argh, not again. This crazy error postponed the bluez-{libs|utils}-2.18 > release already, because I always build the release packages from the > anonymous CVS. I've been seeing this problem on and off for a week or more. Peter ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel