A Community Edition for the legendary Comic Book Manager ComicRack. ComicRack is back from the dead.
**Describe the bug** ComicRackCE marks some files to be updated every time i open comic book info. If i update book metadata and close ComicRackCE it marks them again to be updated. Files are all converted to cbz and were originally pdf, cbr or epud (converted by hand to cbz). Original file format does not matter, happens to all of them. It's always the same files. Even if i remove/delete the comic book and import and convert the original file, it always ends up to the same behavior. Happens to like 10 percent of my files. If i diff the old and new file after updating book files, there a three varying results I can get. 1. The files are identical and nothing changed. ComicRackCE just remade identical cbz file. 2. Files are different but when I unzip them the files inside are identical. 3. Files are different but when I unzip them there is one byte difference in ComicInfo.xml (can't find where). Because I'm a Linux Mint user I run ComicRackCE in a Windows 11 VM with VirtualBox. Works like a dream. Comic book files reside on my OpenMediaVault 6 server on a zfs filesystem mounted as a network drive. Tried to set DisableNTFS=true but no difference. Modern ZFS over Samba should manage ADS without problems, but if I'm wrong please correct me. I'm well aware that running native Windows installation with local files would be better, but unfortunately that's not an option for me. **Exact Steps to Reproduce** 1. Add new comic. File format does not matter. 2. Convert to cbz. 3. Update desired metadata and update book files. 4. Close ComicRackCE. 5. Start ComicRackCE. 6. Open comic book info. 7. Change nothing. 8. Close comic book info. 9. ComicRackCE marks comic book with orange star (metadata changes to update). **Version/Commit (check the about page, next to the version, for the string between brackets):** Version: 0.9.180 Commit: 73c03b8
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by loopk1n and has received 6 comments.