Updating reference checksum might break integrity
Just now, Mutalyzer on our main server tried to update the MD5 checksum for a NM reference. This failed because there was already a reference (UD) with the new checksum in the database (indeed, it was the same file, presumably uploaded earlier by hand).
The database error occured in the _update_db_md5
method of the retriever module. Not sure what the best course of action would be in this case though.
In this case the result was a bit dramatic, since updating the MD5 checksum was triggered by a batch job and therefore the batch processor got stuck on this entry.