Re: [fossil-users] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 8:52 AM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Oct 4, 2013 at 6:27 AM, Ron Aaron r...@ronware.org wrote: I have a large-ish repo, and after cloning it and updating some files, I try to commit ... and get this message. I did already try fossil rebuild to no effect. eeek! It should never be possible that that happens _after_ a commit (if it's going to happen it should fail during the before-commit checking). Spoke too soon: it DID happen while committing, which means nothing is permanently broken :-D But that also means that the command i sent you won't work because rid 12892 gets rolled back. Hmmm... we might need you to add some printfs() to fossil to debug this one, unless there's a switch i'm unaware of to dump the manifest out before committing. What platform are you on? Is there any weird filename encoding in play (Windows/Mac)? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 8:57 AM, Stephan Beal sgb...@googlemail.com wrote: Hmmm... we might need you to add some printfs() to fossil to debug this one, unless there's a switch i'm unaware of to dump the manifest out before committing. i need to leave for a while, but here's something we can try, and with any luck i'll be back about the time you've got this running (i'm naively assuming you're running a fossil built locally): http://fossil-scm.org/index.html/artifact/468d7f73a4b09fe03d16d8477f9fe6a99481bec9?ln=494 right after that line, please add: cgi_printf(TEST FOR RON:\n%b, pOut); all that will do is dump the manifest (and any other stuff it tries to save) to stdout. Please try with a small commit first, because this will also dump the contents of the file(s) being committed, and send the output to a file: # fossil commit foo.out what i'm mostly interested in seeing is the contents of the manifest file itself. The error is happening during the before-commit verification of the manifest because it cannot load that manifest: http://fossil-scm.org/index.html/artifact/0e2f3aa96c9d2fc79f158f3944378b1e7fe8f3ec?ln=868 -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
Sorry, Ron: 2nd arg is pBlob, not pOut. (mobile phone - please excuse brevity and typos) - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal On Oct 4, 2013 9:17 AM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Oct 4, 2013 at 8:57 AM, Stephan Beal sgb...@googlemail.comwrote: Hmmm... we might need you to add some printfs() to fossil to debug this one, unless there's a switch i'm unaware of to dump the manifest out before committing. i need to leave for a while, but here's something we can try, and with any luck i'll be back about the time you've got this running (i'm naively assuming you're running a fossil built locally): http://fossil-scm.org/index.html/artifact/468d7f73a4b09fe03d16d8477f9fe6a99481bec9?ln=494 right after that line, please add: cgi_printf(TEST FOR RON:\n%b, pOut); all that will do is dump the manifest (and any other stuff it tries to save) to stdout. Please try with a small commit first, because this will also dump the contents of the file(s) being committed, and send the output to a file: # fossil commit foo.out what i'm mostly interested in seeing is the contents of the manifest file itself. The error is happening during the before-commit verification of the manifest because it cannot load that manifest: http://fossil-scm.org/index.html/artifact/0e2f3aa96c9d2fc79f158f3944378b1e7fe8f3ec?ln=868 -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
2013/10/4 Stephan Beal sgb...@googlemail.com: On Fri, Oct 4, 2013 at 8:57 AM, Stephan Beal sgb...@googlemail.com wrote: Hmmm... we might need you to add some printfs() to fossil to debug this one, unless there's a switch i'm unaware of to dump the manifest out before committing. Shouldn't the error-message in this case be more helpful anyway? Something like: http://fossil-scm.org/index.html/info/1eb438d61a Regards, Jan Nijtmans ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 11:30 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: Shouldn't the error-message in this case be more helpful anyway? Something like: http://fossil-scm.org/index.html/info/1eb438d61a That's essentially how libfossil reports the errors for this case. At this point i don't know if Ron's problem is caused at parse-time (i don't think so - IIRC, manifest parsing errors are immediately fatal) or if it's trying to load a manifest which is not there (which i find hard to believe), or some such. If i can get a copy of the manifest i can run it through the libfossil manifest parser as a sanity check :). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 12:10 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: Fully agreed! I also don't think that the parser is the problem, maybe it's a bug somewhere else which does not properly fossilize some field which ends up in the manifest later. My hope is that the That's my suspicion. i just got a copy of the repo off-list and am looking into it now using your patched error reporting. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 12:13 PM, Richard Hipp d...@sqlite.org wrote: Doesn't the -n option cause the manifest to be printed on standard output? Quite possibly so - never used it :/. In any case, i'm cloning the repo now (going a bit slowly) and will report back as soon as i know something concrete (and will report whether or not -n spits out the manifest). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 12:19 PM, Stephan Beal sgb...@googlemail.com wrote: In any case, i'm cloning the repo now (going a bit slowly) and will report back as soon as i know something concrete (and will report whether or not -n spits out the manifest). Follow-up: it's not the debugging which is taking so long, but the reproduce/build process (cloning a remote site) has been running for about 80 minutes now and i have no idea how long it will run. @Ron: this has prio 1 for me today (other than walking my dog ;), and i'll be in touch as soon as possible. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 1:53 PM, Stephan Beal sgb...@googlemail.com wrote: Follow-up: it's not the debugging which is taking so long, but the reproduce/build process (cloning a remote site) has been running for about 80 minutes now and i have no idea how long it will run. @Ron: this has prio 1 for me today (other than walking my dog ;), and i'll be in touch as soon as possible. Bad news: i can't reproduce it :/ [stephan@host:~/cvs/fossil/ron]$ f set | grep autosy autosync (local) 0 [stephan@host:~/cvs/fossil/ron]$ f com -m 'crash test' 21 | tee foo New_Version: 6d5ef0c1b9988dc2400e98024b3ac42d0f14a976 [stephan@host:~/cvs/fossil/ron]$ cat foo New_Version: 6d5ef0c1b9988dc2400e98024b3ac42d0f14a976 [stephan@host:~/cvs/fossil/ron]$ f time -n 1 === 2013-10-04 === 12:13:54 [6d5ef0c1b9] *CURRENT* crash test (user: stephan tags: trunk) [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-timeline -n 2 ci [6d5ef0c1b998] @ 2013-10-04 14:13:54 by [stephan] in branch [trunk] crash test ci [6c0d3704e381] @ 2013-01-15 11:00:18 by [ron] in branch [trunk] no comment [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-ls | wc -l 10806 [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-acat current | head C crash\stest D 2013-10-04T12:13:54.361 F a.js 8051128fc23969a5894bd916de0719fde0a94f29 F about.htm a9c3c9d80131b5021e292e8be0f30957dd836313 F amex.gif 14979ef159d2c3a7caa72215ab7f9824cb7a2854 ... [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-ls -v current 1 [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-ls -v prev 2 [stephan@host:~/cvs/fossil/ron]$ diff 1 2 | less 1c1 File list from manifest version 'current' [6d5ef0c1b998] (RID 12814)... --- File list from manifest version 'prev' [6c0d3704e381] (RID 10825)... ... lots of file diffs and the big RID diff between the current and prev commits implies lots of changes were made. i backed it up before the commit, so i can try a few more things out without having to rebuild, but without a reproduce i won't be able to do much :/. This is 64-bit Ubuntu 12.04.2, btw. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 2:22 PM, Stephan Beal sgb...@googlemail.com wrote: ... lots of file diffs and the big RID diff between the current and prev commits implies lots of changes were made. And... [stephan@host:~/cvs/fossil/ron]$ ../libfossil/f-acat tip | ../libfossil/f-mfparse -r Parsing this manifest: - Artifact type=MANIFEST, rid=12814, uuid=6d5ef0c1b9988dc2400e98024b3ac42d0f14a976 10804 files seen in manifest(s). Trying to re-calculate R-card: original=[136592d60d99845173057784350a3afb] Re-calculated R-card: [136592d60d99845173057784350a3afb] R-card match? yes Round-trip re-generated artifact (type=MANIFEST) from input file: Rather large - not dumping to console. Dumping mf to file [mf.out] SHA of [mf.out] = [6d5ef0c1b9988dc2400e98024b3ac42d0f14a976] SHA match? yes i.e. the manifest looks good. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
2013/10/4 Stephan Beal sgb...@googlemail.com: On Fri, Oct 4, 2013 at 2:22 PM, Stephan Beal sgb...@googlemail.com wrote: ... lots of file diffs and the big RID diff between the current and prev commits implies lots of changes were made. I did the same, and everything looks fine. But it indeed takes a lot of time. I did it on Cygwin64, without seeing this error message. Noting that both Stephan and I tried it on a 64-bit machine with a lot of memory, could this be an unchecked memory overflow somewhere? Regards, Jan Nijtmans ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:00 PM, Jan Nijtmans jan.nijtm...@gmail.com wrote:
Noting that both Stephan and I tried it on a 64-bit machine with a lot
of memory, could this be an unchecked memory overflow somewhere?
i'm also working on a repro in a 32-bit vm in parallel. In theory a
malloc failure is not possible because fossil_malloc() aborts on alloc
error, but we do have a few places which use malloc()/free() instead of
fossil_{malloc,free}().
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:01 PM, Stephan Beal sgb...@googlemail.com wrote:
i'm also working on a repro in a 32-bit vm in parallel. In theory a
malloc failure is not possible because fossil_malloc() aborts on alloc
error, but we do have a few places which use malloc()/free() instead of
fossil_{malloc,free}().
Update: we've got the broken manifest now (off-list) and have found the
problem (malformed/empty P-card) but don't yet know why. Jan and i are
playing with it.
@Devs: anyone touched P-card generation lately?
...
F xr.css 35f07555a0420a382004217172b613bd38a3a3f4
P
R e7fa81c6d596b4d5bf77ffdeb62d71ba
U ron
...
the only commit which can legally have a empty P-card is the initial commit
(or one without a parent, but i think that's only possible on the first
commit?).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:01 PM, Stephan Beal sgb...@googlemail.com wrote:
i'm also working on a repro in a 32-bit vm in parallel. In theory a
malloc failure is not possible because fossil_malloc() aborts on alloc
error, but we do have a few places which use malloc()/free() instead of
fossil_{malloc,free}().
Also work on 32-bit for me. Normally one is happy about success, but this
time not.
i'm at a loss.
The problem is definitely the empty P-card (meaning that the manifest looks
like it has no parent version, which is just wrong), but i cannot say why
that happens. As Jan hypothesized, this sounds almost like a memory misuse,
but that seems to have been ruled out. It's too specific of a problem (and
reproducible on Ron's end) to be generic memory corrupt.
Thankfully, the verify-before-commit logic catches this and keeps this from
being immortalized in the repo.
@Ron: which fossil version are you on, and what platform?
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] manifest file (12892) is malformed
On 10/04/2013 04:24 PM, Stephan Beal wrote: @Ron: which fossil version are you on, and what platform? I'm using fossil 816e893d3b on Linux Mint 15 64bit (kernel 3.8.0-30-generic) -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:28 PM, Ron Aaron r...@ronware.org wrote: I'm using fossil 816e893d3b on Linux Mint 15 64bit (kernel 3.8.0-30-generic) Bummer: still works for me :( [stephan@host:~/cvs/fossil/ron]$ f version This is fossil version 1.27 [816e893d3b] 2013-10-04 02:50:26 UTC [stephan@host:~/cvs/fossil/ron]$ fst | head repository: /home/stephan/cvs/fossil/ron/../mtr.fsl local-root: /home/stephan/cvs/fossil/ron/ config-db:/home/stephan/.fossil checkout: 6c0d3704e381430edaef8424b1c1d8d059325a65 2013-01-15 10:00:18 UTC parent: 221b639542e0ef25f06e59a3fc24f6bf5ec9eda3 2012-12-07 09:01:38 UTC tags: trunk comment: no comment (user: ron) EDITED b/r/r1503.htm EDITED b/r/r1903.htm EDITED b/r/r2111.htm [stephan@host:~/cvs/fossil/ron]$ f set autosync 0 [stephan@host:~/cvs/fossil/ron]$ f com -m blah 12 | tee foo New_Version: cfc9450f5ff5a2c3d17d03ceccb0f4617d0d2520 [stephan@host:~/cvs/fossil/ron]$ f artifact cfc9450f5ff5a2c3d17d03ceccb0f4617d0d2520 | grep '^P ' P 6c0d3704e381430edaef8424b1c1d8d059325a65 that's the expected value. @Ron: please try: fossil test-integrity The output on my machine (and Jan's - thanks to him for this idea): [stephan@host:~/cvs/fossil/ron]$ f test-integrity 10826 non-phantom blobs (out of 10826 total) checked: 0 errors [stephan@host:~/cvs/fossil/ron]$ f test-integrity --parse 10826 non-phantom blobs (out of 10826 total) checked: 0 errors 22 total control artifacts 6 manifests 16 clusters -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
ron@monster ~/proj/mtrweb $ fossil test-integrity 10826 non-phantom blobs (out of 10826 total) checked: 0 errors ron@monster ~/proj/mtrweb $ fossil test-integrity --parse 10826 non-phantom blobs (out of 10826 total) checked: 0 errors 22 total control artifacts 6 manifests 16 clusters sigh On 10/04/2013 04:37 PM, Stephan Beal wrote: On Fri, Oct 4, 2013 at 3:28 PM, Ron Aaron r...@ronware.org mailto:r...@ronware.org wrote: I'm using fossil 816e893d3b on Linux Mint 15 64bit (kernel 3.8.0-30-generic) Bummer: still works for me :( [stephan@host:~/cvs/fossil/ron]$ f version This is fossil version 1.27 [816e893d3b] 2013-10-04 02:50:26 UTC [stephan@host:~/cvs/fossil/ron]$ fst | head repository: /home/stephan/cvs/fossil/ron/../mtr.fsl local-root: /home/stephan/cvs/fossil/ron/ config-db:/home/stephan/.fossil checkout: 6c0d3704e381430edaef8424b1c1d8d059325a65 2013-01-15 10:00:18 UTC parent: 221b639542e0ef25f06e59a3fc24f6bf5ec9eda3 2012-12-07 09:01:38 UTC tags: trunk comment: no comment (user: ron) EDITED b/r/r1503.htm EDITED b/r/r1903.htm EDITED b/r/r2111.htm [stephan@host:~/cvs/fossil/ron]$ f set autosync 0 [stephan@host:~/cvs/fossil/ron]$ f com -m blah 12 | tee foo New_Version: cfc9450f5ff5a2c3d17d03ceccb0f4617d0d2520 [stephan@host:~/cvs/fossil/ron]$ f artifact cfc9450f5ff5a2c3d17d03ceccb0f4617d0d2520 | grep '^P ' P 6c0d3704e381430edaef8424b1c1d8d059325a65 that's the expected value. @Ron: please try: fossil test-integrity The output on my machine (and Jan's - thanks to him for this idea): [stephan@host:~/cvs/fossil/ron]$ f test-integrity 10826 non-phantom blobs (out of 10826 total) checked: 0 errors [stephan@host:~/cvs/fossil/ron]$ f test-integrity --parse 10826 non-phantom blobs (out of 10826 total) checked: 0 errors 22 total control artifacts 6 manifests 16 clusters -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
2013/10/4 Stephan Beal sgb...@googlemail.com: the only commit which can legally have a empty P-card is the initial commit (or one without a parent, but i think that's only possible on the first commit?). An empty P-card (or a manifest without a P-card) is allowed for any manifest, but then it shouldn't have a space after the P (it would look strange in the timeline, here is one: http://fossil-scm.org/index.html/timeline?c=2013-08-21T14:49:41.624 ). Of course we could remove the space when there is no parent manifest, but that would only mask the problem: in this case the parent blob should be there. Regards, Jan Nijtmans ___ 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] manifest file (12892) is malformed
Ron, can you run: sqlite3 .fslckout '.dump v%' And post make that output available to us? The .fslckout file should be at the root of your check-out. It might be called _FOSSIL_ if your checkout was originally opened with a much older version of Fossil. -- D. Richard Hipp d...@sqlite.org ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:42 PM, Jan Nijtmans jan.nijtm...@gmail.com wrote: An empty P-card (or a manifest without a P-card) is allowed for any manifest, but then it shouldn't have a space after the P (it would look strange in the timeline, here is one: http://fossil-scm.org/index.html/timeline?c=2013-08-21T14:49:41.624 ). Of course we could remove the space when there is no parent manifest, but that would only mask the problem: in this case the parent blob should be there. You are certainly correct. i had the P (with space) answer backwards in my memory, but found a comment to that effect: /* Evil ugly hack, primarily for round-trip compatibility with manifest #1, which has an empty P card. fossil(1) ignores empty P-cards in all cases, and must continue to do so for backwards compatibility with rid #1 in all repos. Pedantic note: there must be no space between the 'P' and the newline. */ fsl_deck_append(os, P\n); -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
Done, you can pick it up here: http://ronware.org/dump.sql.gz Thanks! On 10/04/2013 04:44 PM, Richard Hipp wrote: sqlite3 .fslckout '.dump v%' -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 9:50 AM, Ron Aaron r...@ronware.org wrote: Done, you can pick it up here: http://ronware.org/dump.sql.gz That looks ok. What does the following query against the repository give: SELECT uuid FROM blob WHERE rid=15513; It should yield a SHA1 hash, which will become the argument to the P card. If in your repository it yields an empty string, that would explain the malformed manifest. (Still unexplained is how the above query could possible yield an empty string.) -- D. Richard Hipp d...@sqlite.org ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 3:50 PM, Ron Aaron r...@ronware.org wrote:
Done, you can pick it up here: http://ronware.org/dump.sql.gz
i think what Richard wanted there was:
INSERT INTO vvar VALUES('checkout','15513');
So that we can check:
[stephan@host:~/cvs/fossil/ron]$ echo select uuid from blob where
rid=15513; | fossil sqlite
(no results)
(please try that on your machine)
which is somewhat surprising. i was expecting to see:
[stephan@host:~/cvs/fossil/ron]$ echo select rid from blob where
uuid='6c0d3704e381430edaef8424b1c1d8d059325a65'; | fossil sqlite
10825
That said, the RIDs can theoretically be different across sites, so this
isn't definitive.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] manifest file (12892) is malformed
2013/10/4 Ron Aaron r...@ronware.org:
Done, you can pick it up here: http://ronware.org/dump.sql.gz
Fossil code:
vid = db_lget_int(checkout, 0);
zParentUuid = db_text(0, SELECT uuid FROM blob WHERE rid=%d, vid);
From the dump:
INSERT INTO vvar VALUES('checkout','15513');
So the parent blob has rid 15513. that looks OK.
In my cloned repository the rid of this blob is 10825.
$ fossil sqlite
SQLite version 3.8.1 2013-09-16 12:57:19
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite SELECT * FROM blob where rid=10825;
10825|1|627733|6c0d3704e381430edaef8424b1c1d8d059325a65|
sqlite .exit
So, Ron, can you try:
$fossil sqlite
sqlite SELECT * FROM blob where rid=15513
Regards,
Jan Nijtmans
___
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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:03 PM, Jan Nijtmans jan.nijtm...@gmail.com wrote: sqlite SELECT * FROM blob where rid=15513 lol... all of us racing at once to say the same thing. At least the answers are consistent, though ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
Indeed, it gives an empty string. On 10/04/2013 05:02 PM, Richard Hipp wrote: SELECT uuid FROM blob WHERE rid=15513; -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On 10/04/2013 05:02 PM, Stephan Beal wrote: echo select rid from blob where uuid='6c0d3704e381430edaef8424b1c1d8d059325a65'; | fossil sqlite For me it's 10798 -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On 10/04/2013 05:03 PM, Jan Nijtmans wrote:
2013/10/4 Ron Aaron r...@ronware.org:
Done, you can pick it up here: http://ronware.org/dump.sql.gz
Fossil code:
vid = db_lget_int(checkout, 0);
zParentUuid = db_text(0, SELECT uuid FROM blob WHERE rid=%d, vid);
From the dump:
INSERT INTO vvar VALUES('checkout','15513');
So the parent blob has rid 15513. that looks OK.
In my cloned repository the rid of this blob is 10825.
$ fossil sqlite
SQLite version 3.8.1 2013-09-16 12:57:19
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite SELECT * FROM blob where rid=10825;
10825|1|627733|6c0d3704e381430edaef8424b1c1d8d059325a65|
sqlite .exit
So, Ron, can you try:
$fossil sqlite
sqlite SELECT * FROM blob where rid=15513
it's blank (empty) for me.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
For confidential messages, please use my GnuPG key
http://ronware.org/gpg_key.html
___
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] manifest file (12892) is malformed
Interestingly, select max(rid) from blob gives me 10826... On 10/04/2013 05:02 PM, Richard Hipp wrote: On Fri, Oct 4, 2013 at 9:50 AM, Ron Aaron r...@ronware.org mailto:r...@ronware.org wrote: Done, you can pick it up here: http://ronware.org/dump.sql.gz That looks ok. What does the following query against the repository give: SELECT uuid FROM blob WHERE rid=15513; It should yield a SHA1 hash, which will become the argument to the P card. If in your repository it yields an empty string, that would explain the malformed manifest. (Still unexplained is how the above query could possible yield an empty string.) -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:07 PM, Ron Aaron r...@ronware.org wrote: On 10/04/2013 05:02 PM, Stephan Beal wrote: echo select rid from blob where uuid='6c0d3704e381430edaef8424b1c1d8d059325a65'; | fossil sqlite For me it's 10798 Somehow the record of your checkout version and the actual checkout seem to have gotten out of sync. i can't currently speculate as to how that might happen. Rather than fiddle without the checkout db, i'd suggest trying the following: fossil close --force cd .. tar cf foo.tar $OLDPWD cd - fossil open /path/to/repo.fsl --keep cd - tar xf foo.tar # probably not necessary with --keep, but can't hurt cd - fossil status should show you your list of changes (several hundred, IIRC). And then do your checkin again. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
2013/10/4 Ron Aaron r...@ronware.org: Indeed, it gives an empty string. Then I have a theory what happened. My guess is that you cloned the repository and opened it. Later you cloned the repository again (which got different row-id's), storing it in the exact original location. Then the row-id's of the .fslckout database and the repository don't match any more. What you can do to fix this: - fossil update trunk (find the new rowid of trunk, and bring the checkout there) - fossil revert (clean up any garbage) then do a make and everything else, and try the commit. Am I close? Regards, Jan Nijtmans ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:10 PM, Ron Aaron r...@ronware.org wrote: Interestingly, select max(rid) from blob gives me 10826... The RIDs aren't 100% dependable as a point of reference, though. They are sequential but not necessarily in increments of one. In theory the highest-number RID must refer to an Fossil Artifact (as opposed a user file), but i'm largely speculating based on my understanding of the model. In any case, it's not guaranteed that RIDs across different systems (or even clones) are identical (though in practice they normally would be identical across clones). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 10:09 AM, Ron Aaron r...@ronware.org wrote: So, Ron, can you try: $fossil sqlite sqlite SELECT * FROM blob where rid=15513 it's blank (empty) for me. Blank as in the row does not exist, or blank in the sense that the row exists but contains no content? -- D. Richard Hipp d...@sqlite.org ___ 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] manifest file (12892) is malformed
Don't know, I'll have to try and see. I can't recall doing that, but it's certainly possible. On 10/04/2013 05:12 PM, Jan Nijtmans wrote: 2013/10/4 Ron Aaron r...@ronware.org: Indeed, it gives an empty string. Then I have a theory what happened. My guess is that you cloned the repository and opened it. Later you cloned the repository again (which got different row-id's), storing it in the exact original location. Then the row-id's of the .fslckout database and the repository don't match any more. What you can do to fix this: - fossil update trunk (find the new rowid of trunk, and bring the checkout there) - fossil revert (clean up any garbage) then do a make and everything else, and try the commit. Am I close? Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:21 PM, Ron Aaron r...@ronware.org wrote: Well, boy howdy! That seems to have cured it. :-D Somehow I must have done Something Bad, but not clear just what it may have been... Jan's hypothesis sounds better than anything i can come up with. It was, in any case, a mismatch between expected and available RID values. The RID values are transient, local to a specific copy of a repo. Jan's idea of a re-clone would explain the difference there (and i can't think of any other cause for it, other than restoring from backup or similar, but the end effect would be the same as a re-clone). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
Well, boy howdy! That seems to have cured it. Somehow I must have done Something Bad, but not clear just what it may have been... Thanks to all of you for your help Ron On 10/04/2013 05:12 PM, Stephan Beal wrote: On Fri, Oct 4, 2013 at 4:07 PM, Ron Aaron r...@ronware.org mailto:r...@ronware.org wrote: On 10/04/2013 05:02 PM, Stephan Beal wrote: echo select rid from blob where uuid='6c0d3704e381430edaef8424b1c1d8d059325a65'; | fossil sqlite For me it's 10798 Somehow the record of your checkout version and the actual checkout seem to have gotten out of sync. i can't currently speculate as to how that might happen. Rather than fiddle without the checkout db, i'd suggest trying the following: fossil close --force cd .. tar cf foo.tar $OLDPWD cd - fossil open /path/to/repo.fsl --keep cd - tar xf foo.tar # probably not necessary with --keep, but can't hurt cd - fossil status should show you your list of changes (several hundred, IIRC). And then do your checkin again. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:25 PM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Oct 4, 2013 at 4:21 PM, Ron Aaron r...@ronware.org wrote: Well, boy howdy! That seems to have cured it. :-D Somehow I must have done Something Bad, but not clear just what it may have been... Jan's hypothesis sounds better than anything i can come up with. It was, in any case, a mismatch between expected and available RID values. The RID values are transient, local to a specific copy of a repo. You did a rebuild in the middle, too, which might have further changed the RIDs (they get regenerated during a rebuild, and not necessarily in the same order as before). The rebuild didn't _cause_ this, but might have exacerbated it (why is it that i can spell exacerbated on the first try, but can't remember how many pairs are in occasionally without the help of a spell checker?). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:29 PM, Stephan Beal sgb...@googlemail.com wrote: You did a rebuild in the middle, too, which might have further changed the RIDs (they get regenerated during a rebuild, and not necessarily in the same order as before). The rebuild didn't _cause_ this, but might have exacerbated it (why is it that i can spell exacerbated on the first try, but can't remember how many pairs are in occasionally without the help of a spell checker?). New theory! @Jan: please help me out here: fossil rebuild -R repo from outside the checkout could change the RIDs out from under any checkouts. OTOH, i would have expected to see this problem before now as a side effect of rebuild all. :-? (that's a question for Jan and Richard) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 10:32 AM, Stephan Beal sgb...@googlemail.com wrote: New theory! @Jan: please help me out here: fossil rebuild -R repo from outside the checkout could change the RIDs out from under any checkouts. I don't think rebuild changes RIDs. The RIDs are set by the BLOB table and BLOB is not changed by a rebuild. -- D. Richard Hipp d...@sqlite.org ___ 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] manifest file (12892) is malformed
2013/10/4 Richard Hipp d...@sqlite.org: On Fri, Oct 4, 2013 at 10:32 AM, Stephan Beal sgb...@googlemail.com wrote: I don't think rebuild changes RIDs. The RIDs are set by the BLOB table and BLOB is not changed by a rebuild. I was about to answer the same: A clone is the only thing I know that changes RID's of Blobs. A rebuild doesn't do that. Regards, Jan Nijtmans ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:35 PM, Richard Hipp d...@sqlite.org wrote: I don't think rebuild changes RIDs. The RIDs are set by the BLOB table and BLOB is not changed by a rebuild. Good to know. i thought (haven't ported that far yet) that a rebuild reconstructed the whole blob table one artifact at a time. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file (12892) is malformed
On Fri, Oct 4, 2013 at 4:21 PM, Ron Aaron r...@ronware.org wrote: Well, boy howdy! That seems to have cured it. Next time it won't take so long: http://www.fossil-scm.org/index.html/info/7bf9fdb068 that adds a check for this specific case and fails earlier in the process. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] manifest file (12892) is malformed
What can I do about this error? I have a large-ish repo, and after cloning it and updating some files, I try to commit ... and get this message. I did already try fossil rebuild to no effect. -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html ___ 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] manifest file is malformed - one cause explained
On Sun, Jul 8, 2012 at 10:09 PM, Thomas Stover c...@thomasstover.com wrote: the problem was apparently that fossil was storing absolute file names, That sounds like a serious problem. Fossil *should* store all filenames relative to the root of the repository file hierarchy. Can you provide a reproducible test case on how we can get Fossil to try to store absolute pathnames, so that I can fix this bug? For clarity: I assume that you mean in the manifest file, right? -- D. Richard Hipp d...@sqlite.org ___ 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] manifest file is malformed - one cause explained
On Mon, Jul 9, 2012 at 4:09 AM, Thomas Stover c...@thomasstover.com wrote: In my case the problem was apparently that fossil was storing absolute file names, which were now different. So even though I didn't rename Are you sure this has to do with absolute file names? We had a bug a week or two ago with a malformed manifest, and you might be seeing that. Can you try this with the latest version, and paste in any error messages? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] manifest file is malformed - one cause explained
On Monday, July 9, 2012 12:51pm, Stephan Beal sgb...@googlemail.com said: Are you sure this has to do with absolute file names? We had a bug a week or two ago with a malformed manifest, and you might be seeing that. Can you try this with the latest version, and paste in any error messages? No I'm not sure. That was just one guess I had since the problem went away when I made the directory names the same as on the source computer. Hopefully later today / early tomorrow I'll get a chance to get you guys something more to go on. I'll try the latest source on it also. www.thomasstover.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] manifest file is malformed - one cause explained
Forgoing the sordid tale of why I had to do this, to commit changes from a laptop, I had to copy my fossil project directories over to another computer with functioning internet connectivity. Once there, I tried a fossil commit only to be hit with a manifest file is malformed error. Some searching yielded some talk on the list about some mysteries about the error in the past. In my case the problem was apparently that fossil was storing absolute file names, which were now different. So even though I didn't rename any of my project files, fossil was afraid that it had lost track of a rename or something to that effect. The solution was to mangle directory names around until the project was using the same absolute file names that existed on the laptop. Hey at least it's not like the time I opened the gates of hell with a similar stunt involving linux - windows raw directory copies with svn. -- www.thomasstover.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] manifest file (3967) is malformed error
fossil.exe: manifest file (3967) is malformed I don't think this will be of much help but I have a reproducible test case that results in such an error. I tested it on Russian Windows 7 x64 only. Initial script is in the attachment, encoding is UTF-8 without a byte order mark (cmd.exe chokes on it). Here is the output of the script: -8--- Microsoft Windows [Version 6.1.7601] (c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены. e:\tempfossil_bug.cmd e:\tempchcp 65001 Active code page: 65001 e:\tempfossil version This is fossil version [d5b9674ec5] 2011-06-01 22:39:44 UTC e:\tempfossil init test.fossil -A admin project-id: 18e018f905b5d5f9e77a9addd10c631b5bb0d1e2 server-id: fb3108cb82f00f6173662df2c80d5c38f2276781 admin-user: admin (initial password is b42b28) e:\tempmkdir test e:\tempcd test e:\temp\testfossil open ..\test.fossil e:\temp\testmkdir doc e:\temp\testecho ZZZ 1doc\график.txt e:\temp\testfossil add doc\график.txt ADDED doc/график.txt e:\temp\testfossil commit -m New file with filename in Russian New_Version: a0c69380a1d1e9f8d6ad3192226b47c14ae1e72b e:\temp\testecho ZZZ 1doc\plan.txt e:\temp\testfossil add doc\plan.txt ADDED doc/plan.txt e:\temp\testfossil commit -m Added plan New_Version: af1be78a3f61386bbd21fd1c5bdfd48dca7152df D:\portable\CLI\develop\fossil.exe: manifest file (4) is malformed e:\temp\testrem ^ The above line is where error occurs ^ e:\temp\testcd .. e:\temp -8--- File addition order is insignificant. I've tried swapping addition of doc/график.txt and doc/plan.txt and error occurs anyway on the second commit. Rough conditions of a bug: 01. Execution environment is non-US Windows. 01. Repository has at least one non-ascii filename. 03. Filenames added to repository contain common left substring to Filenames existing in repository (doc/ in my case). Has anyone got any suggestion on where to go with this ? Maybe try to find non-ascii filenames in repository manifest and rename them? Is there a command to fix a corrupted fossil databases ? AFAIK, the database is not corrupted in the result of such an error, It just refuses your commits. All you need for now is to get rid of non-ascii filenames. P.S. Sorry for possible bad English. -- Roman Gistzev. chcp 65001 fossil version fossil init test.fossil -A admin mkdir test cd test fossil open ..\test.fossil mkdir doc echo ZZZ doc\гÑаÑик.txt fossil add doc\гÑаÑик.txt fossil commit -m New file with filename in Russian echo ZZZ doc\plan.txt fossil add doc\plan.txt fossil commit -m Added plan rem ^ The above line is where error occurs ^ cd ..___ 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] manifest file (3967) is malformed error
I've experienced this before and it turns out the work-around is simple. It normally happens when you rename file1, modify file2, then attempt to commit file2 without including file1 in the commit. If you commit file1 first, things work and the error vanishes. It would be helpful if you included (a scrubbed) the output of a 'fossil status'. -sc -- Sean Chittenden ___ 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] manifest file (3967) is malformed error
Sean Chittenden wrote: I've experienced this before and it turns out the work-around is simple. It normally happens when you rename file1, modify file2, then attempt to commit file2 without including file1 in the commit. If you commit file1 first, things work and the error vanishes. Hi, thanks, yes this is the repeat by. The problem is that for a large number of changes it's not possible to guess what would have to be committed in what order to avoid this bug, and it's not nice to have to split up a single logical commit into two or more. I guess the workaround is to do all renames as a separate commit. I've added a ticket (0ff64b0a5f) to track this, as well as a request that fossil status show more information about pending renames (040dcddb1e). cheers, Graeme Gill. ___ 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] manifest file (3967) is malformed error
Graeme Gill wrote: fossil.exe: manifest file (3967) is malformed Has anyone got any suggestion on where to go with this ? Is there a command to fix a corrupted fossil databases ? Is there a way of diagnosing where/why/what is malformed about the manifest ? Should I just give up and use a different CMS ? Graeme Gill. ___ 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] manifest file (3967) is malformed error
On Thu, May 5, 2011 at 8:41 PM, Graeme Gill grae...@argyllcms.com wrote: Hi, I've been using fossil happily for a few weeks, but suddenly have a problem. After renaming a couple of files, I can't do a commit anymore: fossil commit afiles vim ci-comment-D69892D388C2.txt New_Version: abfcdd99b08f7f0aa3fa20e55656a732ca9d754e fossil.exe: manifest file (3967) is malformed and fossil diff shows that the file wasn't committed. Questions: 1) What caused this ? 2) How do I fix it ? I dunno. Can you send me the repository so that I can investigate? thanks, Graeme Gill. ___ 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...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] manifest file
I just did fossil update $ID in order to build a particular version of the source and I find no manifest file in the checkout directory. The documentation on the website still talks about a manifest file, so has something changed in recent versions of fossil? Why don't I have a manifest file? Thanks, //Bill ___ 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] manifest file
On Fri, Feb 18, 2011 at 12:54:23PM -0500, Bill Whiting wrote: I just did fossil update $ID in order to build a particular version of the source and I find no manifest file in the checkout directory. The documentation on the website still talks about a manifest file, so has something changed in recent versions of fossil? Why don't I have a manifest file? fossil settings will tell you if the creation is enabled. The default changed, IIRC. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
