Recursive unpacking not working in 0.5.2 & 0.5.3

[garakz]

After updating Sabnzb to 0.5.2 or 0.5.3 from 0.5.0, Recursive unpacking stopped working for me. After reverting back to 0.5.0, recursive unpacking worked again. Is there any setting I need to change to make it work in 0.5.3?

Thanks

[shypike]

"Recursive unpacking stopped working for me."
You will need to specify exactly what goes wrong.
As a general statement it's not true.

[garakz]

Say on the top level there are multiple zip file a01.zip a02.zip. After unzipping, there are b.rar b.r01 files. After unrar there is c.exe. Under 0.5.0, after processing, I got c.exe. under 0.5.2 and 0.5.3, I got b.rar and b.r01. Does this help?

[shypike]

Well, if you could PM me an example NZB, it would be easier to diagnose.

[garakz]

Thanks a lot, just PMed.

[shypike]

The result isn't rescanned after ZIP files have been unpacked.
Rescanning is done after unrar and join actions, but never after an unzip.
You situation is sufficiently rare to never having triggered a complaint before.
BTW: your example is rather bizarre. Why does anyone bother to zip individual rar segment files?

I'll see that it's fixed in a future version.

BTW: the difference between 0.5.0 and 0.5.2/3 is that other unpack issues were solved.
This might be a side-effect.

[garakz]

Thank you, looking forward for next version.

[bugmenot]

Hope you fix this one. It's in the scene rules to pack 0day releases twice:

"Filenames must be amed up to a maximum of 8.3 characters (filename/extension). Acceptable compression format at this time is any compression method that supports multiple volumes and long file names, followed by the traditional PKZIPing. Compressions other than RAR should include an extract utility or be a self-extracting archive."

[c0ld]

Yep, rarring then zipping is pretty common for apps.

[shypike]

Will be fixed in 0.5.4