(Minor): Wrong display if job contains >200 rar files

[finalius]

Seems that if a job contains more than 200 rar files, SAB displays the unpacking procedure wrongly.

[shypike]

Probably because unrar sends incorrect info.
Does it work correctly otherwise?

[finalius]

yes, works fine otherwise.

I use Debian wheezy non-free unrar:

Package: unrar
New: yes
State: installed
Automatically installed: no
Version: 1:4.0.3-1
Priority: optional
Section: non-free/utils
Maintainer: Martin Meredith <[email protected]>
Uncompressed Size: 254 k
Depends: libc6 (>= 2.2.5), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1)
Conflicts: rar (<= 2.60-1)
Description: Unarchiver for .rar files (non-free version)
Unrar can extract files from .rar archives. If you want to create .rar archives, install package rar.
Homepage: http://www.rarlabs.com/

[shypike]

I wasn't doubting your specific unrar version, but unrar in general.
To make my life easier, can you email an example NZB that shows this behaviour?
Email to bugs at sabnzbd.org and add the URL of this thread.

[finalius]

I've sent the NZB that caused this issue

[shypike]

This post was created with old-style RAR segments. r01..r99 up to t01..t51.
Few posters use that any more.
New style numbering, like *.part001.* to *.part300.* will show proper numbering.
I consider this a low priority issue.

[finalius]

absolutely It's purely cosmetic