Re: [fossil-users] Trouble when making new repository

2014-05-09 Thread Jan Nijtmans
2014-05-09 16:45 GMT+02:00 Andy Bradford : > Yes, it was on trunk, and that's actually how I discovered it. I used > the no-initial-commit fossil to create a new Fossil, then I opened it > and added a file. It refused to commit the file, so I took an old > version of fossil ran statu

Re: [fossil-users] Trouble when making new repository

2014-05-09 Thread Andy Bradford
Thus said Stephan Beal on Fri, 09 May 2014 11:16:04 +0200: > > So it didn't even attempt to add the file that it said was ADDED. > > > > That's why the R-card is right. The error is the missing F-card. > > Please tell me that's not on the trunk? Yes, it was on trunk, and that's actually how I d

Re: [fossil-users] Trouble when making new repository

2014-05-09 Thread Stephan Beal
On Fri, May 9, 2014 at 9:53 AM, Jan Nijtmans wrote: > 2014-05-08 22:20 GMT+02:00 B Harder : > > I restrained myself in the previous discussion that ended up being about > the > > initial empty commit, but now I feel compelled: the rational, > "discussion", > > and decision to remove the initial e

Re: [fossil-users] Trouble when making new repository

2014-05-09 Thread Stephan Beal
On Fri, May 9, 2014 at 3:13 AM, Andy Bradford wrote: > I too get this same error, however, not for an empty commit: > >From the current trunk or the one which was moved? > > Also, I can commit if I do ``fossil status'' first: > That's a hint that the vfile table is not being updated in the fir

Re: [fossil-users] Trouble when making new repository

2014-05-09 Thread Jan Nijtmans
2014-05-09 3:13 GMT+02:00 Andy Bradford : > Also, I can commit if I do ``fossil status'' first: That's the difference!: I use "fossil status" a lot, therefore I didn't notice that the function unsaved_changes() doesn't do anything when vid=0. This bug can be triggered on trunk as well (although wi

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Andy Bradford
Thus said Andy Goth on Thu, 08 May 2014 14:26:14 -0500: > andy|slack|14:24|0|~/foo > $ f commit -m test > New_Version: 3a4aff36993d288a6dfb7b5c968c3af613c25547 > ERROR: [file] is 6 bytes on disk but 0 in the repository > NOTICE: Repository version of [file] stored in [file-22ef63d951e2b17d] > work

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread B Harder
I restrained myself in the previous discussion that ended up being about the initial empty commit, but now I feel compelled: the rational, "discussion", and decision to remove the initial empty commit were pretty poor, IMO. I don't want to belabor the point, so I'll leave it at that. Happy to disc

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Stephan Beal
On Thu, May 8, 2014 at 9:57 PM, Stephan Beal wrote: > Going back a version does indeed fix it. i'll roll back that commit, as > soon as i figure out what the proper approach is to rolling back a commit. > (Suggestions welcomed ;) > i always forget about "move to new branch..." Richard just move

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Stephan Beal
On Thu, May 8, 2014 at 9:52 PM, Stephan Beal wrote: > On Thu, May 8, 2014 at 9:46 PM, Andy Goth wrote: > >> Looking into it now, but suspect that Jan or Andy B might have a more >>> immediate suspicion, seeing as they've been around that code lately. >>> >> >> I think [3ef59c357c] is the culprit

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Stephan Beal
On Thu, May 8, 2014 at 9:46 PM, Andy Goth wrote: > Looking into it now, but suspect that Jan or Andy B might have a more >> immediate suspicion, seeing as they've been around that code lately. >> > > I think [3ef59c357c] is the culprit. In fact, the reason I made a new > repository was to test t

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Andy Goth
On 5/8/2014 2:40 PM, Stephan Beal wrote: On Thu, May 8, 2014 at 9:26 PM, Andy Goth wrote: andy|slack|14:25|0|~/foo May i say: that's a a pretty crazy prompt you have there! Username, hostname, time, background job count, current directory, (newline), dollar sign or pound sign depending on U

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Stephan Beal
On Thu, May 8, 2014 at 9:40 PM, Stephan Beal wrote: > Confirmed: > > [stephan@host:~/cvs/fossil/X/x]$ f com -m test > Seems to be caused by an ignored return value check which assumes true. Should have a fix soon. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/s

Re: [fossil-users] Trouble when making new repository

2014-05-08 Thread Stephan Beal
On Thu, May 8, 2014 at 9:26 PM, Andy Goth wrote: > With today's version of Fossil, I can't add anything to any > freshly-created repositories. > > andy|slack|14:25|0|~/foo > May i say: that's a a pretty crazy prompt you have there! > $ f version > This is fossil version 1.29 [3ef59c357c] 2014-

[fossil-users] Trouble when making new repository

2014-05-08 Thread Andy Goth
With today's version of Fossil, I can't add anything to any freshly-created repositories. andy|slack|14:25|0|~/foo $ f version This is fossil version 1.29 [3ef59c357c] 2014-05-08 10:25:32 UTC andy|slack|14:23|0|~ $ mkdir foo andy|slack|14:23|0|~ $ cd foo andy|slack|14:23|0|~/foo $ f new foo.f