From: Joshua Wright <jwright@hasborg.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] CVS not allowing anonymous authentication for checkout
Date: Wed, 08 Feb 2006 11:56:05 -0500 [thread overview]
Message-ID: <43EA22A5.5000105@hasborg.com> (raw)
In-Reply-To: <87hd7agci8.fsf@gismo.pca.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It appears that the BlueZ CVS repository is not allowing anonymous
access any longer:
$ cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez login
Logging in to :pserver:anonymous@cvs.bluez.org:2401/cvsroot/bluez
CVS password: <CR>
cvs login: authorization failed: server cvs.bluez.org rejected access to
/cvsroot/bluez for user anonymous
Also, the web interface to the CVS repository is returning a 502 Proxy
Error.
Other sf.net projects are not exhibiting these same errors. Has the CVS
repository for BlueZ been marked private?
Thanks,
- -Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFD6iKlTS8i9jZYpL8RAsGPAKC1SvmX3HWPDw0XWJStGA8/NBoTSACfY5ww
8DIBXOIrFIKe1eSk42NmPXY=
=6dE5
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2006-02-08 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hd7agci8.fsf@gismo.pca.it>
2006-02-08 16:56 ` Joshua Wright [this message]
2006-02-10 2:19 ` [Bluez-devel] CVS not allowing anonymous authentication for checkout Amateur
2006-02-10 7:50 ` John McCabe-Dansted
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43EA22A5.5000105@hasborg.com \
--to=jwright@hasborg.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).