I haven't changed much recently about my repository topology.  One central
"master" repo that I push to from my "dev" repo.  No one else is doing any
pushing.  The master repo has hooks set up for publishing my commits etc to
a remote HTTP REST API.

The only change I made recently is to open up my same local repo a second
time into a new sandbox.  That worked fine for many commits.  But today I
suddenly see this:

$ fossil version
This is fossil version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC
$ uname -a
Linux miami 3.6.11-4.fc16.x86_64 #1 SMP Tue Jan 8 20:57:42 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux

$ fossil commit --branch test -m "Test check-in."
New_Version: 81ba47a887f005b11fe14aedb9c8c25f0bc23ffe
$ fossil push
Push to https://eas@<snip>:10444/
Round-trips: 1   Artifacts sent: 2  received: 0
Error: push script failed: syntax error in manifest
Round-trips: 1   Artifacts sent: 2  received: 0
Push finished with 817830 bytes sent, 330 bytes received
$ fossil push
Push to https://eas@<snip>:10444/
Round-trips: 1   Artifacts sent: 0  received: 0
Push finished with 817459 bytes sent, 286 bytes received

The only interesting thing I did recently was (a) make a commit from my old
sandbox on a dev branch; (b) switch to my new sandbox, make two new
unrelated commits to trunk; (c) cherrypick the commit I made in (a) to
trunk.  That's when the issue seems to have started.

The data appears to have landed on the server properly.  The error now
happens consistently every time I try a check-in + push sequence (twice in
a row, anyway).  My Transfer hooks on the server don't seem to have fired.

I tried this, which doesn't give much useful info:

$ fossil test-parse-manifest ./manifest
$ echo $?
0
$

I assume it's the remove fossil complaining, though -- not the local one.

How can I gather more info?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to