-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unrarall cleans files if subs rar has extracted cleanly #31
Comments
I'm sorry However the behavior describe doesn't seem desirable so we should try to fix it. I need to have a chat with @arfoll first though about setting up some basic testing infrastructure so we don't introduce regressions. |
lmao |
@delcypher I know sorry I was in shock, I didn't demanded I made urgency about serious problem. https://mega.nz/#!R5V0iQxD!eqey5KB9peZLMYtHVp1SuCL-Y1GugEgznINnTEHbImA These were the example files, one of these "london.has.fallen.2016.1080p.bluray.x264-drones.subs.rar", has acceptable naming and archiving type, other were with the idiotic archiving and naming. |
hi @loa11, thanks for reporting this and apologies it's caused you issues. If I understand the issue, unrarall considers the subs.rar successfully extracted so then removes everything that looks like a rar archive, including your unfinished stuff. Unfortunately I'm not sure how to best treat the issue, did you have cksfv running? It would possibly have worked (not 100%) but we could definately introduce strict cksfv checking that would fix it. If you run unrarall with @delcypher I did create part of a test harness at one point but never completed it, hopefully it's still around somewhere or we can start from scratch. |
Most of rared subs had sfv file and almost every rared movie had own sfv set. Here is the direct example I see few possible solutions, one is that unrarall ignores all the rars with naming *subs.rar or that unararall search for *subs.rar and *subs.sfv and to remove them into the Subs folder or as the final solution is that unrarall skips overwriting. |
wasn't this fixed in #40 ? And it's confusing.. because that PR says it was merged in the last comments.. yet it doesn't appear to have been merged.. is this problem patched or not? If so then this issue should be closed? |
Uhhh unrarall made me a horror situation, it made huge mess, you need to fix this issue.
Let me explain, lot of scene files have idiotic naming of base rar file and the archived sub file which has the same rar name as the base rar file, inside the *subs.rar.
In that case unrarall would unpack firstly the sub rar which would overwrite the base rar file.
Example:
name of the base rar file rep-13hoursthesecretsoldiers.1080p.bluray.x264.rar
name of the subtitle file rared with the name "rep-13hoursthesecretsoldiers.1080p.bluray.x264-subs.rar" iside of this rar were two files:
rep-13hoursthesecretsoldiers.1080p.bluray.x264.rar and
rep-13hoursthesecretsoldiers.1080p.bluray.x264.idx
rep-13hoursthesecretsoldiers.1080p.bluray.x264.rar has rep-13hoursthesecretsoldiers.1080p.bluray.x264.sub
As you can see
In my case unrarall deleted 244 base rar files which made 30% of my rared HD movies uncompleted.
There are almost 10 scene groups (REPLICA, SPARKS...) which use such naming formatting, most of them use SUB folders but on most private trackers and on most NNTP indexers uploaders decide that SUB folder were not needed and we have because of that this problem.
There are even cases that those scene groups wouldn't use rared subs inside the rared sub.
The text was updated successfully, but these errors were encountered: