Unpacking failed, an expected file was not unpacked

Report & discuss bugs found in SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Unpacking failed, an expected file was not unpacked

Post by shypike »

I think I located the problem.
A fix in sanitizing paths coming from Sorting doesn't take UNC paths into account.
There will be an RC3 within a few days.
User avatar
Taomyn
Full Member
Full Member
Posts: 129
Joined: August 25th, 2008, 3:29 am

Re: Unpacking failed, an expected file was not unpacked

Post by Taomyn »

shypike wrote:In that case, something is wrong in SABnzbd itself.
Both the forward slash at the front and the back are suspect.
Back to the drawing board.
Should you be using Sort for this download, can you post your Sort expression?
It's set to:

Code: Select all

%sn/%sn - S%0sE%0e - %en.%ext
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Unpacking failed, an expected file was not unpacked

Post by shypike »

Thanks.
It's a problem with all UNC paths.
Just bad testing, sorry for the inconvenience, thanks for the report!
User avatar
Taomyn
Full Member
Full Member
Posts: 129
Joined: August 25th, 2008, 3:29 am

Re: Unpacking failed, an expected file was not unpacked

Post by Taomyn »

shypike wrote:Thanks.
It's a problem with all UNC paths.
Just bad testing, sorry for the inconvenience, thanks for the report!
No worries, just glad you spotted the error. Look forward to the fix soon.
Post Reply