Closed Andrew-Coppin closed 4 years ago
Oh dear, 2 files with the same filename CRC ... thanks, I have enough information, will look into it.
Thank you very much for reporting this issue. It should be fixed now, please test it and let me know if it works.
I just tried ee71aa5; it does indeed appear to fix the issue. Thank you.
I recently stumbled across an odd problem. I have a disk image with 2 files I cannot access. For example:
However, if I revert to a (much) older commit, now I can access these files perfectly. So this seems like some kind of regression.
Using commit 309ecb030f38edac4c10fa741a004c5eb7a23e15:
Using commit 0ca2e1f5cdfe32613b662713dd9b87ddb82a96e7:
I did a Git bisect, and discovered the following:
0ca2e1f5cdfe32613b662713dd9b87ddb82a96e7: Works. a56d0b7c9624431ea72a18605f40079f8b5d16c8: Works. 713430b18deb6025e4cf5020ca3e5c2262df7135: Doesn't compile. cc70cb9a8488cb6e43048b992dbf82b905231277: Doesn't compile. 9de1a6c77f1fdc9702503d9e2d1a1bf400c6483f: Doesn't compile. 4a5bb16df28f441d046e4b569d45248377f8bd0f: Cannot access the files. 0eb5f2386b3d67e482e2119c67e0d0b8d2e6824b: Cannot access the files.
I found the
-d 7
option makes the program print some debugging info, but... I don't really know what I'm doing. If there's any further debugging info I can supply, let me know.