Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Sean Woods
> No.  Did you start with a clean checkout?  No prior "configure" results > sitting around? Yes I did. After receiving your message, I re-extracted it from the tar archive and tried configure again. No luck. See below. swoods@web75:tmp$ rm -r Fossil-e0199bfc43 swoods@web75:tmp$ tar -xzvf Fos

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Richard Hipp
On Sat, Aug 2, 2014 at 1:46 PM, Sean Woods wrote: > > Any insight into why I get the glob.tcl error when I try ./configure? > No. Did you start with a clean checkout? No prior "configure" results sitting around? -- D. Richard Hipp d...@sqlite.org _

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Sean Woods
> Support for filenames that contain the "?" character was added on 2012-11-30 > (see http://www.fossil-scm.org/fossil/info/647bb7b79f for the change).  Since > your Fossil server is earlier than this, it won't be able to interpret files > that contain "?" characters and so it won't see this ch

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Richard Hipp
On Sat, Aug 2, 2014 at 1:18 PM, Sean Woods wrote: > > > Can you share the text of the missing artifact with us? That might be > instructive. > > Here you go. This is the textual representation. [...] > F headers/pr_schema_???.csv 5ec9a158fc6f89c2d70cdcefff05a84a60d3f45b > Support for filenam

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Sean Woods
> Can you share the text of the missing artifact with us?  That might be > instructive. Here you go. This is the textual representation. It shows up in the Web UI as if it were source code -- like it appears in a gray box with dashed lines. I can browse to other SHAs for files I changed and

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Richard Hipp
On Sat, Aug 2, 2014 at 12:19 PM, Sean Woods wrote: > > The missing artifacts are present on the server, but fossil appears to > be interpreting them incorrectly. > Can you share the text of the missing artifact with us? That might be instructive. -- D. Richard Hipp d...@sqlite.org ___

Re: [fossil-users] Can't push or autosync

2014-08-02 Thread Sean Woods
> A manifest indeed does contain details about a checkin[1]. So the UUID > that you see in the local repository but not he remote repository is a > UUID of a checkin? If so, it will look something like this: > > http://www.fossil-scm.org/index.html/info/36c4551e7cda231c0b5fe99600afc75c10eba2c7

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Fri, 01 Aug 2014 19:04:47 -0400: > So it seems I a missing some kind of "manifest" artifact that > describes which "files" go into which "checkin." I realize these terms > have special meaning within Fossil, thus the quotes. A manifest indeed does contain details

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
> > swoods@sachem:~/code/pr$ fossil remote > > http://swo...@code.seanwoods.com/pr.fossil.cgi > > Does the artifact actually exist if you take the UUID of the missing > artifact and ask /info about it via the server URL? > > Something like: > > http://swo...@code.seanwoods.com/pr.fossil.cgi/

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Fri, 01 Aug 2014 15:16:09 -0400: > swoods@sachem:~/code/pr$ fossil remote > http://swo...@code.seanwoods.com/pr.fossil.cgi Does the artifact actually exist if you take the UUID of the missing artifact and ask /info about it via the server URL? Something like: http://

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Fri, 01 Aug 2014 15:14:42 -0400: > I checked 5-10 and they are all there. Should I check all of them? Perhaps not. It might be better to focus on what we can know. Do you know the UUID of the artifacts which are in your local client that you expect to be on the remo

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
> > > > Have you tried running: fossil sync --verily > > > > This didn't help. Still doesn't appear in the timeline. > > And what does "fossil remote" show you? Is it the correct URL? Yes. swoods@sachem:~/code/pr$ fossil remote http://swo...@code.seanwoods.com/pr.fossil.cgi > > What is t

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
>> Host: code.seanwoods.com >> >> push ac45ca13555b013a9ca55832a7fcfb9278195aba >> 8cc0c6c4c9c2c2bb99247d69a198d3587f65fbcf >> igot 0287f09da88e80d4dcc2275c143bdf017259b59c >> [more igot cards removed] > > Are any of the artifact UUIDs in the above igots (including those elided > from the list

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Richard Hipp
On Fri, Aug 1, 2014 at 3:08 PM, Sean Woods wrote: > > > > Have you tried running: fossil sync --verily > > > > This didn't help. Still doesn't appear in the timeline. > And what does "fossil remote" show you? Is it the correct URL? What is the output when you run "fossil sync"? Are you get

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
> > Have you tried running: fossil sync --verily > This didn't help. Still doesn't appear in the timeline. swoods@sachem:~/code$ fossil sync -R pr.fossil --verily Sync with http://swo...@code.seanwoods.com/pr.fossil.cgi Round-trips: 1 Artifacts sent: 0 received: 0 Sync finished with 6045

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Fri, 01 Aug 2014 14:17:22 -0400: > I forget where I put it! I usually put that in ~/fossils but it's not > there. Is there a way I can tell, looking at the checkout, where the > repository actually is (the local one, that is)? If you are in an open repository you can ju

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
> Have you tried running: fossil sync --verily I have not. I tried invoking that command but looks like it needs an argument to the repository (vs. the cloned checkout). I forget where I put it! I usually put that in ~/fossils but it's not there. Is there a way I can tell, looking at the

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Fri, 01 Aug 2014 13:26:34 -0400: > Host: code.seanwoods.com > > push ac45ca13555b013a9ca55832a7fcfb9278195aba > 8cc0c6c4c9c2c2bb99247d69a198d3587f65fbcf > igot 0287f09da88e80d4dcc2275c143bdf017259b59c > [more igot cards removed] Are any of the artifact UUIDs in the above

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Richard Hipp
On Thu, Jul 31, 2014 at 10:47 PM, Sean Woods wrote: > Hello! > > I have a remote machine with Fossil on it. Fossil version [8d758d3715] > 2012-10-22 12:48:04 - which is really old, I know, but it works fine and > that machine is on a Linux 2.6 kernel still (!) CGI enabled, etc. I > have being d

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Sean Woods
>> Recently it just stopped auto syncing. I do `fossil push` and it still >> doesn't work. > > Can you provide some sample output for a commit that doesn't sync? Also, > what about: > > fossil settings autosync > fossil settings dont-push > > Also, since you mentioned push is failing, you could

Re: [fossil-users] Can't push or autosync

2014-08-01 Thread Andy Bradford
Thus said Sean Woods on Thu, 31 Jul 2014 22:47:23 -0400: > Recently it just stopped auto syncing. I do `fossil push` and it still > doesn't work. Can you provide some sample output for a commit that doesn't sync? Also, what about: fossil settings autosync fossil settings dont-push Also, since y

Re: [fossil-users] Can't push or autosync

2014-07-31 Thread Sean Woods
> I recompiled off the latest trunk and that didn't help. Clarification: server is on ancient 2012 version, client is on latest trunk just compiled. When I commit on the client, it doesn't push to the server, even `fossil remote-url` says that's where it should go for remotes. Sorry; "I am le ti

[fossil-users] Can't push or autosync

2014-07-31 Thread Sean Woods
Hello! I have a remote machine with Fossil on it. Fossil version [8d758d3715] 2012-10-22 12:48:04 - which is really old, I know, but it works fine and that machine is on a Linux 2.6 kernel still (!) CGI enabled, etc. I have being doing fossil commit for months and it always autosyncs with the se