How to fix "Unresolved RID values: 0"

(1) By jose i cabrera (jicman) on 2020-02-28 20:34:04 [link] [source]

Greetings.

I can start from scratch, if I need to, but after getting,

14:41:46.11>fossil ci -m "initial import"
./] contains CR/LF line endings. Use --no-warnings or the "crlf-glob" setting to disable this warning.
Commit anyhow (a=all/c=convert/y/N)? n
Abandoning commit due to CR/LF line endings in ./]

and then running this command,

fossil settings ignore-glob ".obj,.ksp,.map,.~,.rsp,.def,.exe,.*" --global

I ran the same 'fossil ci -m "initial import"' command and got the same message. So, I deleted the .fossil file and this is what I did:

14:50:27.48>fossil init c:UtilsFossilPMOReport.fossil project-id: d54e2367c9324e89fdbea7d98c10e94928396e4a server-id: 6bf9ce79fe6899f6fe7742bd0313a319f1be284c admin-user: e608313 (initial password is "66ac47")

14:54:50.97>fossil open c:UtilsFossilPMOReport.fossil Unresolved RID values: 0

14:55:01.84>fossil add . Unresolved RID values: 0

14:55:44.60>fossil timeline Unresolved RID values: 0

14:57:14.25>fossil changes Unresolved RID values: 0

Is there a way of getting this undone? Again, I can just rename that repo. Thanks.

josé

(2) By Stephan Beal (stephan) on 2020-02-28 22:54:19 in reply to 1 [source]

That's... odd. Try this:

fossil close --force
fossil open c:/Utils/Fossil/PMOReport.fossil

i suspect the problem is not with your repo file but with the checkout db, and this will delete and recreate it. If the first command fails with the same error, look in that directory for a file named .fslckout, or maybe _FOSSIL_ on Windows, and delete it (which is effectively what close does), then try open again.

(3) By anonymous on 2020-02-29 00:32:59 in reply to 1 [link] [source]

You're on Windows, that's clear. Windows uses CR-LF for end-of-line in text files, unlike other platforms. Fossil warned you that your text files do contain CR-LF, which may be non-portable to other platforms (in case your fellow developers are working under Linux or macOS, for example).

I understand CR-LF is not an issue for you to worry about, and you'd like to keep all of your text files Windows-bound. Thus you'd need to specify crlf-glob setting to cover all of your source files.

fossil set crlf-glob "*,"

NOTE: the "comma" is required under Windows, otherwise cmd.exe will match it to the first file in the current dir.

More about Fossil Filename Globbing

BTW, instead of the prompted crlf-glob you went on to set ignore-glob, which is useful too, but mostly for 'fossil add', 'fossil clean', and 'fossil extra' commands.

(4) By Florian Balmer (florian.balmer) on 2020-02-29 08:33:39 in reply to 3 [link] [source]

CMD.EXE never expands globs, but fossil.exe itself (if linked with wsetargv.obj). Some Cygwin-Shells may do globbing, however.

(5) By jose i cabrera (jicman) on 2020-03-02 01:15:16 in reply to 2 [link] [source]

Yep, this worked. Thanks.

(6) By Florian Balmer (florian.balmer) on 2020-03-18 15:46:19 in reply to 4 [link] [source]

I've corrected the statement that the command shell performs glob pattern expansion on Windows. While at it, I've also made a few more updates. This is ready to merge, for my part.

(7) By Warren Young (wyoung) on 2020-03-18 17:26:07 in reply to 6 [link] [source]

Done.

(8) By Florian Balmer (florian.balmer) on 2020-03-18 17:41:43 in reply to 7 [link] [source]

Great, thanks for the extra work!

Fossil User Forum

How to fix ”Unresolved RID values: 0”