Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/29/17, Joerg Sonnenberger wrote: >> >> For example, if checkin [1234abcd] has a comment that refers to ticket >> [bcdef522] which in turn refers to artifact ID [6543cfe], is the >> migration tool expected to chase and re-point all those links when all >> the hashes change? >

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Wed, Nov 29, 2017 at 03:36:07PM -0700, Warren Young wrote: > On Nov 29, 2017, at 3:10 PM, Joerg Sonnenberger wrote: > > > > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > >> On 11/29/17, Jacob MacDonald wrote: > >>> Ah, I see. It seems

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Wed, Nov 29, 2017 at 03:36:07PM -0700, Warren Young wrote: > On Nov 29, 2017, at 3:10 PM, Joerg Sonnenberger wrote: > > > > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > >> On 11/29/17, Jacob MacDonald wrote: > >>> Ah, I see. It seems

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Nov 29, 2017, at 3:10 PM, Joerg Sonnenberger wrote: > > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: >> On 11/29/17, Jacob MacDonald wrote: >>> Ah, I see. It seems strange to me that the policy didn't get set when I >>> cloned. How can I

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

Thanks for the help, all. I still don't completely understand what happened but things are sane again! On Wed, Nov 29, 2017 at 4:11 PM Joerg Sonnenberger wrote: > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > > On 11/29/17, Jacob MacDonald

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > On 11/29/17, Jacob MacDonald wrote: > > Ah, I see. It seems strange to me that the policy didn't get set when I > > cloned. How can I avoid the same thing in the future and is there any way > > to change the

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/29/17, Jacob MacDonald wrote: > "manifest checksum does not agree with disk", seen when cloning the bad > repo for the first time and trying to open in. That sounds like it is missing some content files. Once you sync up the two repos, that problem will go away. --

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

"manifest checksum does not agree with disk", seen when cloning the bad repo for the first time and trying to open in. On Wed, Nov 29, 2017 at 2:01 PM Richard Hipp wrote: > On 11/29/17, Jacob MacDonald wrote: > > So I'll just have to reconcile the two

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/29/17, Jacob MacDonald wrote: > So I'll just have to reconcile the two histories manually? I'm super > confused by the manifest message since it makes it sound like the artifacts > were not shunned, just stored where I can't see them somehow. It should just sync up, as

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

So I'll just have to reconcile the two histories manually? I'm super confused by the manifest message since it makes it sound like the artifacts were not shunned, just stored where I can't see them somehow. On Wed, Nov 29, 2017, 12:25 Jacob MacDonald wrote: > I believe so.

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

I believe so. On Wed, Nov 29, 2017, 11:13 Martin Gagnon wrote: > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > > On 11/29/17, Jacob MacDonald wrote: > > > Ah, I see. It seems strange to me that the policy didn't get set when I > > >

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > On 11/29/17, Jacob MacDonald wrote: > > Ah, I see. It seems strange to me that the policy didn't get set when I > > cloned. How can I avoid the same thing in the future and is there any way > > to change the

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/29/17, Jacob MacDonald wrote: > Ah, I see. It seems strange to me that the policy didn't get set when I > cloned. How can I avoid the same thing in the future and is there any way > to change the artifacts in the local repository to SHA3? There is no good way to change

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

Ah, I see. It seems strange to me that the policy didn't get set when I cloned. How can I avoid the same thing in the future and is there any way to change the artifacts in the local repository to SHA3? On Wed, Nov 29, 2017, 05:39 Richard Hipp wrote: > On 11/28/17, Jacob

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/28/17, Jacob MacDonald wrote: > > While the Chisel page says shun-sha1 is on, That could be a problem. That means chisel is rejecting any SHA1 artifacts. The only want to change that is via command-line - there is no web interface to set the hash policy. The command

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

Yes, that project code is correct. While the Chisel page says shun-sha1 is on, the local repository has no such note on the schema version line. On Tue, Nov 28, 2017 at 6:20 PM Richard Hipp wrote: > On 11/28/17, Jacob MacDonald wrote: > > My hash-policy

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/28/17, Jacob MacDonald wrote: > My hash-policy is in fact just "auto", so this doesn't seem to be as > similar to my situation as I thought. OK. Let's verify that the project-IDs match. On chisel we have:

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

My hash-policy is in fact just "auto", so this doesn't seem to be as similar to my situation as I thought. On Tue, Nov 28, 2017 at 11:47 AM Jacob MacDonald wrote: > Thank you, I believe I changed the hash-policy locally. However, 2.1 > should support the new hash policies

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

Thank you, I believe I changed the hash-policy locally. However, 2.1 should support the new hash policies as well. Perhaps I need to tweak something on the Chisel side for them to work, though. On Tue, Nov 28, 2017 at 11:38 AM Martin Gagnon wrote: > On Tue, Nov 28, 2017 at

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On Tue, Nov 28, 2017 at 12:01:45PM -0500, Richard Hipp wrote: > On 11/28/17, Jacob MacDonald wrote: > > On my end, I added a couple of local files in two commits. Then I ran > > "fossil sync". The commits do not show up on Chisel even though the sync > > command says it

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

2.4 [a0001dcf57] is what I'm running locally. On Tue, Nov 28, 2017 at 11:01 AM Richard Hipp wrote: > On 11/28/17, Jacob MacDonald wrote: > > On my end, I added a couple of local files in two commits. Then I ran > > "fossil sync". The commits do not show up

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/28/17, Jacob MacDonald wrote: > On my end, I added a couple of local files in two commits. Then I ran > "fossil sync". The commits do not show up on Chisel even though the sync > command says it succeeds. Furthermore, opening a new clone of the > repository from Chisel

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

I expect the sync to fail or for the state of the remote repository to match my local state. On Tue, Nov 28, 2017 at 10:51 AM Jacob MacDonald wrote: > On my end, I added a couple of local files in two commits. Then I ran > "fossil sync". The commits do not show up on Chisel

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On my end, I added a couple of local files in two commits. Then I ran "fossil sync". The commits do not show up on Chisel even though the sync command says it succeeds. Furthermore, opening a new clone of the repository from Chisel seems to be corrupt: When I try to open it, it tells me the

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/28/17, Jacob MacDonald wrote: > http://chiselapp.com/user/jaccarmac/repository/adventofcode/index is the > broken repository. I can also package up my local instance of it/perform > whatever steps are necessary to debug. Let me know. From your original description, I

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

http://chiselapp.com/user/jaccarmac/repository/adventofcode/index is the broken repository. I can also package up my local instance of it/perform whatever steps are necessary to debug. Let me know. On Tue, Nov 28, 2017, 03:03 Richard Hipp wrote: > On 11/28/17, Jacob MacDonald

Re: [fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

On 11/28/17, Jacob MacDonald wrote: > I'm using 2.4 locally, Chisel says it's using 2.1. If I change a file in a > repository the changes go out properly but adding files to another > repository doesn't work. The push or sync seems to succeed, but the Chisel > web UI does not

[fossil-users] Weird behavior on Chisel, perhaps a version mismatch?

I'm using 2.4 locally, Chisel says it's using 2.1. If I change a file in a repository the changes go out properly but adding files to another repository doesn't work. The push or sync seems to succeed, but the Chisel web UI does not reflect the change and on clone I get a "manifest checksum does