Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Invalid par2 files, cannot verify or repair" - invalid par breaking nzb #182

Closed
thezoggy opened this issue Oct 4, 2014 · 4 comments
Closed

"Invalid par2 files, cannot verify or repair" - invalid par breaking nzb #182

thezoggy opened this issue Oct 4, 2014 · 4 comments
Assignees
@shypike
Labels
Bug Fixed
Milestone
1.0.0

Comments

@thezoggy
Copy link
Contributor

thezoggy commented Oct 4, 2014

http://forums.sabnzbd.org/viewtopic.php?f=2&t=14897&p=96610#p96610
@thezoggy
Copy link
Contributor Author

thezoggy commented Oct 4, 2014

so why does sab puke on invalid par's when I have config > switches > Enable Quick Check enabled and the sfv validated (and release extracts just fine)... seems like its not working

@shypike
Copy link
Member

shypike commented Oct 4, 2014

QuickCheck needs at least one valid par2 file, how else could it check?
The matching of SFV files and RAR-sets was done case-sensitive, which doesn't always work out well.
Fixed now: 92bc48c

@thezoggy
Copy link
Contributor Author

thezoggy commented Oct 4, 2014

"Skip par2 checking when files are 100% valid." makes me think that the par2 would be skipped.... if its valid (sfv?)

@shypike shypike added this to the 0.7.19 milestone Oct 23, 2014
@shypike shypike self-assigned this Oct 23, 2014
@shypike shypike modified the milestones: 0.8.0, 0.7.19 Jan 19, 2016
@shypike
Copy link
Member

shypike commented Jan 19, 2016

The actual problem of bad casing of files has been solved.

@shypike shypike closed this as completed Jan 19, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@shypike shypike

Labels
Bug Fixed
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@thezoggy @shypike