This is a corrective commit to also handle md5 sum comparisons in burning methods the same way that is done in rest places. Without it the current (patched) implementation is broken in the sense that md5 comparisons in burning methods will fail.
I didn't had time to actually test it, because I do not burn cds/dvds anymore. However I believe it to be correct because the changes are concentrated in few lines of code. I plan to make burn tests later in spring, but didn't want to leave the issue unreported / unsolved till then.
The commit also drops calculation of md5 sum from the burned disk if not in database and issues a warning instead (since we cannot guarantee that a copy error did not occurred during burning if the original hash is missing, I find it more appropriate to warn; it also saves time).
I interleaved the last one to the main theme of the commit for convenience; the changed lines are very few anyway. If you do not like it that way I can split it to two separate commits in a topic branch instead.
This is a corrective commit to also handle md5 sum comparisons in burning methods the same way that is done in rest places. Without it the current (patched) implementation is broken in the sense that md5 comparisons in burning methods will fail.
I didn't had time to actually test it, because I do not burn cds/dvds anymore. However I believe it to be correct because the changes are concentrated in few lines of code. I plan to make burn tests later in spring, but didn't want to leave the issue unreported / unsolved till then.
The commit also drops calculation of md5 sum from the burned disk if not in database and issues a warning instead (since we cannot guarantee that a copy error did not occurred during burning if the original hash is missing, I find it more appropriate to warn; it also saves time).
I interleaved the last one to the main theme of the commit for convenience; the changed lines are very few anyway. If you do not like it that way I can split it to two separate commits in a topic branch instead.