jonnybluesman
commented
2 years ago Does this only happen when cloning / forking the repository? Did they try to disable the warning with git config --global core.protectNTFS false?
If we are providing the raw (original) files of these collections, then this may not be solvable. From the link you provided:
Do not use the following reserved names for the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended
If the original collections include these files, then we can consider doing some cleaning, as long as this does not interfere with our pipelines.
andreamust
Testers (validators) report that there are problems cloning and working with the ChoCo repository due to some naming conventions in the subfolders of
partitions.More specifically, these errors refer to:
?).The use of Docker containers can solve this problem for end users. However, the problem of reproducibility of the results on non-UNIX-based environments and the potential expansion of the community of contributors behind the ChoCo project remain.