[fossil-users] Can't Pull from fossil-scm.org Anymore?

2010-01-23 Thread Zed A. Shaw
Hey,

Just tried pulling the latest code from fossil-scm.org via fossil and I
get:

~/source $ fossil clone http://fossil-scm.org/ ~/fossils/fossil.fossil
Bytes  Cards  Artifacts Deltas
Send: 597 24  0  0
1fossil: server says: login failed

Or, with an existing checkout:

projects $ fossil pull -R ~/fossils/fossil.fossil 
Server:http://fossil-scm.org/
Bytes  Cards  Artifacts Deltas
Send: 130  1  0  0
2fossil: server says: login failed

Did someone change it so people can't pull anymore unless they're on the
project?

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

2010-01-23 Thread Zed A. Shaw
On Sat, Jan 23, 2010 at 10:01:58AM -0800, Zed A. Shaw wrote:
 Hey,
 
 Just tried pulling the latest code from fossil-scm.org via fossil and I
 get:

Alright, found the previous email about this in the archives.  Someone
should put a nice big announce out saying we need to get the latest
binary if we want to continue tracking via fossil.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

2010-01-23 Thread Venkat Iyer

Is there a workaround for this with the old client?  I have
modifications to my local fossil that I need for emacs integration and
this makes it slightly harder.  Still not a big deal.

 - Venkat


-Original Message-
From: Zed A. Shaw zeds...@zedshaw.com
Sent: Saturday, January 23, 2010 10:04:42
Subject: Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

On Sat, Jan 23, 2010 at 10:01:58AM -0800, Zed A. Shaw wrote:
 Hey,
 
 Just tried pulling the latest code from fossil-scm.org via fossil and I
 get:

Alright, found the previous email about this in the archives.  Someone
should put a nice big announce out saying we need to get the latest
binary if we want to continue tracking via fossil.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

2010-01-23 Thread Zed A. Shaw
On Sat, Jan 23, 2010 at 10:18:25AM -0800, Venkat Iyer wrote:
 
 Is there a workaround for this with the old client?  I have
 modifications to my local fossil that I need for emacs integration and
 this makes it slightly harder.  Still not a big deal.

What you should do is go grab the binary for your platform from
fossil-scm.org.  Use the binary to get a new clone from fossil-scm.org
and do a rebuild.  Then you *should* be able to either take your changes
from your old fossil repo and merge them in, or just apply a diff from
your old repo.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

2010-01-23 Thread Venkat Iyer

Yeah - that's what I had done, took me about half hour of hacking to
get back to the state where it was before (even using fossil-diff and
path -p0) - a lot of files have changed.  That was my slightly
harder.  Again, as I said, not a big deal for me, but might be for
others.

 - Venkat


-Original Message-
From: Zed A. Shaw zeds...@zedshaw.com
Sent: Saturday, January 23, 2010 10:25:14
Subject: Re: [fossil-users] Can't Pull from fossil-scm.org Anymore?

On Sat, Jan 23, 2010 at 10:18:25AM -0800, Venkat Iyer wrote:
 
 Is there a workaround for this with the old client?  I have
 modifications to my local fossil that I need for emacs integration and
 this makes it slightly harder.  Still not a big deal.

What you should do is go grab the binary for your platform from
fossil-scm.org.  Use the binary to get a new clone from fossil-scm.org
and do a rebuild.  Then you *should* be able to either take your changes
from your old fossil repo and merge them in, or just apply a diff from
your old repo.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] cloning http://www.fossil-scm.org/ fails

2010-01-23 Thread D. Richard Hipp

On Jan 23, 2010, at 5:55 PM, Florian Weimer wrote:

 * D. Richard Hipp:

 Better: Just download the latest precompiled binary or tarball from
 http://www.fossil-scm.org/download.html and use that instead of the
 version you are currently using.

 Is this supposed to reoccur?  I'm asking because Debian is planning to
 release Fossil with squeeze, and this doesn't make sense if the client
 needs constant code changes to stay interoperable with other people's
 repositories.


No.  It was a mistake that it occurred this time.  And probably soon  
I'll fix the server so that it works with both old and new clients.

The change was that the server is now a little stricter about login  
credentials.  If the password is not correct, it complains and refuses  
to do anything.  Before the change, the server would continue running  
with the permissions of the special user nobody.  Meanwhile, older  
clients are sending (bogus) login credentials even if the user doesn't  
specify any.  (That has also been fixed.)  The combination of these  
two issues results in older clients not being able to clone from newer  
servers.

I can probably come up with a hack to the server-side that allows  
older clients to work.  But it seems like a relatively minor problem,  
so I haven't put much effort into that yet.

 (This is a bit like changing the on-disk file format for SQLite. 8-)

The Fossil file format is unchanged.  It is just the authentication  
protocol that has been updated and which caused the problem.

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

D. Richard Hipp
d...@hwaci.com



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users