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.

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

Print par-files creator app, especially if par-repair fails #467

hugbug opened this issue Nov 6, 2017 · 1 comment


None yet
1 participant
Copy link

commented Nov 6, 2017

An issue was reported on forum where par-repair fails with message:

repair completed but the data files still appear to be damaged

It seems the issue is caused by posters using development version of ParPar, a version which wasn't released for public usage actually.

Par2 file format specification describes a field of par2-file containing identification information about application which created par2-files. The specification also says:

If a client is unable to process a recovery set, the contents of the creator packet must be shown to the user. The goal of this is that any client incompatibilities can be found and resolved quickly.

If NZBGet would print par2 creator that would certainly helped to identify the cause of the issue sooner.

@hugbug hugbug added the improvement label Nov 6, 2017

@hugbug hugbug added this to the v20 milestone Nov 6, 2017

hugbug added a commit that referenced this issue Nov 6, 2017

#467: print par2 creator packet
as INFO on par-check start and as part of ERROR message on par-repair

@hugbug hugbug closed this Nov 6, 2017


This comment has been minimized.

Copy link
Member Author

commented Nov 6, 2017

Example error message including creator info:

screen shot 2017-11-06 at 22 49 59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.