Closed KevinMKorb closed 10 years ago
@KevinMKorb could you add your specific usecase here, I'll test in the meantime if I can reproduce
On usenet it has become common to post things with completely bogus names with the real names stored in the par2 file. IOW there will be a 5 digit number filename with .par2 .sfv .rar and .r?? extensions. In the past I could do: par2repair 12345.par2 12345.* and the files would be renamed to the correct names which I would then unrar. Now it simply ignores the 12345.* files.
I have been compensating with either quickpar under wine or 'cfv -snf 12345.par2' in Linux however only the former works if there is corruption that will need to be repaired with par2 blocks.
can you send me an example ? if you don't want an example here, just send me directly by mail.
there is a test in the testsuite to test the renaming and thatone works, maybe i need to extend that
Email sent.
thx i'll look into it
some extra info: what OS is this ? ubuntu, debian, gentoo, arch, ... ?
I am on Gentoo Linux (32bit) with par2cmdline 0.6.10
I version bumped my local portage tree and your new version fixes my problem. Thanks.
Commit https://github.com/BlackIkeEagle/par2cmdline/commit/f265e71aacf9b435917e8bdfcb0cac6158230902 breaks the behavior documented under https://github.com/BlackIkeEagle/par2cmdline#misnamed-and-incomplete-data-files
Now any incorrectly named files that are specified on the command line are not checked for content but are simply ignored.