On Fri, Oct 26, 2012 at 5:42 PM, Bernd Paysan <bernd.pay...@gmx.de> wrote:
> We have "managed" to create a repository that can't be cloned anymore - > after > a fork and merge where some larger files have been changed (date > 2012-09-26). > The two developers who created fork and merge were able to continue to > work, > but everybody else was excluded. Pulling or cloning (via fossil's web > protocol) the repository beyond that point fails with an out of error > message. > > The workaround we used: Do a verbatim copy of the fossil database from the > server or one of the two developers. > > You can download the db from > > http://forth-ev.de/~bp/vd-2012-03.fossil > > or try cloning it (will fail!) from > > http://fossil.forth-ev.de/vd-2012-03 > > It's 105MB large, and our server is well connected; though for debugging > you > probably better copy the repository and serve it locally. The repository > does > not contain anything confidential. > If I clone from your repo, I do indeed get a corrupt clone. But if I download the raw repo, set up a server locally ("fossil server vd-2012-03.fossil") then clone it locally ("fossil clone http://localhost:8080/ vd-new.fossil") the clone works just fine. What does your webserver setup look like? Might it be doing an undesirable \n to \r\n translation or something, that is messing of the clone traffic? (I'm fishing for ideas here because I don't know what is wrong.) > > Version: "This is fossil version [0448438c56] 2011-05-28 18:51:22 UTC" > > -- > Bernd Paysan > "If you want it done right, you have to do it yourself" > http://bernd-paysan.de/ > > _______________________________________________ > 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
