Unresolved RID values: ...
(1.1) By Gour (gour) on 2019-09-19 11:11:02 edited from 1.0 [link] [source]
Hello,
today when I wanted to commit one change on one repo, I get the following even with simple command like:
$ fossil help
Unresolved RID values: 2596 3081 3082 3140 3783
Any hint what could be the cause for it?
How to fix it?
I'm on Debian (Sid) and regularly update my Fossil using trunk version...
Sincerely, Gour
(2) By Richard Hipp (drh) on 2019-09-19 12:27:41 in reply to 1.1 [source]
This error message comes from the relatively new logic that tries to update a check-in database (the .fslckout file) after you have replaced the main repository database with a clone that uses different RID values.
As best I can tell, you replaced the repository database with a different repository that omits some of the files that the check-out was using.
Can you tell us more about how you got into this state?
(3) By Gour (gour) on 2019-09-20 07:17:51 in reply to 2 [link] [source]
My reply did not go to the forum, but privately...
As best I can tell, you replaced the repository database with a different repository that omits some of the files that the check-out was using.
Hmm...I did re-install Debian on my machine going from Xfce to GNOME and before that I did backup which I was restroing in last few days...
Can you tell us more about how you got into this state?
iow. nothing special.
The strange thing is if I checkout the same repo.fossil into another directory it does not complain, but, of course, does not have up-to-date version of the VSC-ed files
Should I just re-open my repo into and replace files?
Any other hint?
Sincerely,
Gour
(4) By anonymous on 2019-09-20 16:13:46 in reply to 3 [link] [source]
if I checkout the same repo.fossil into another directory it does not complain
I would use the above checkout as my new working copy.
Should I just re-open my repo into and replace files?
Then copy the changes in the old working copy to the new working copy. Optionally, I might rename the old and new working copies
(5.1) By Gour (gour) on 2019-09-21 12:33:54 edited from 5.0 in reply to 4 [link] [source]
I would use the above checkout as my new working copy.
Yes, that helped!
I'm glad (again) that Fossil separates checkout from the repo itself. :-)
Sincerely,
Gour
(6) By Richard Hipp (drh) on 2019-09-23 19:37:51 in reply to 1.1 [link] [source]
I hit this same problem earlier today. I think I have it fixed now on trunk.