Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

Hello Richard, I was going to write to you about reappearance of the 'malformed manifest' problem but found that you had checked in a fix to the previous bug fix. Now, I can confirm that the last fix [5f3a0681a0] works fine for me. Thank you, Jacek 2012/6/29 Richard Hipp : > > > On Fri, Jun

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

Yes, the commit went fine. Thank you again! Jacek 2012/6/29 Richard Hipp : > > > On Fri, Jun 29, 2012 at 8:36 AM, Jacek Cała wrote: >> >> Thank you for the prompt action. Please keep me/the list informed >> about the patch. > > > Please try the latest trunk version of Fossil.  I believe it has

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

On Fri, Jun 29, 2012 at 8:36 AM, Jacek Cała wrote: > Thank you for the prompt action. Please keep me/the list informed > about the patch. > Please try the latest trunk versionof Fossil. I believe it has fixed your issue and should be working for

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

Thank you for the prompt action. Please keep me/the list informed about the patch. Maybe it is also worth considering the case when a file has just been added to the repo (no commit) and then mv is issued from a MISSING to the ADDED file. I wrote about it a couple of days ago: http://www.mail-arch

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała wrote: > Hi, > > I've been doing some code maintenance (lots of deletes, renames, adds) > and now cannot do commit. Every commit attempt causes: > > > fossil.exe: manifest file (1816) is malformed. > > What does this mean? Is there any chance to fix th

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

2012/6/29 Richard Hipp : > > It means there is a bug in Fossil.  ... > > Note that the changes to the repository happen inside a transaction.  ... > ... This is one of the big advantages of using a transactional database engine > as the repository, rather than a pile-of-files as in other VCSes - bu

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

d:\...\MainSolution>fossil test-agg-cksum disk: 9b15edd8f59e6d06f24779627eb5d751 archive: ef042e223a29de7097b5bac505295812 manifest: 064345fe886bffeb23131fcc0ac5a5d5 recorded: 064345fe886bffeb23131fcc0ac5a5d5 Hardly readable for me :-) but no errors. Cheers, Jacek 2012/6/29 Stephan Beal

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała wrote: > Hi, > > I've been doing some code maintenance (lots of deletes, renames, adds) > and now cannot do commit. Every commit attempt causes: > > > fossil.exe: manifest file (1816) is malformed. > > What does this mean? Is there any chance to fix th

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

On Fri, Jun 29, 2012 at 11:33 AM, Jacek Cała wrote: > > fossil.exe: manifest file (1816) is malformed. > > What does this mean? Is there any chance to fix the repo? My fossil > version is 1.22. > That's a new one. :/ Can you please try: fossil test-agg-cksum just to make sure that the basic c

[fossil-users] cannot commit 'manifest file (1816) is malformed'

Hi, I've been doing some code maintenance (lots of deletes, renames, adds) and now cannot do commit. Every commit attempt causes: > fossil.exe: manifest file (1816) is malformed. What does this mean? Is there any chance to fix the repo? My fossil version is 1.22. Jacek _