http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9326 --- Comment #2 from Jared Camins-Esakov <jcamins@cpbibliography.com> --- (In reply to comment #1)
I understand what we discuss yesterday :)
It is the normal behavior: A new version is available, you execute it. This version is an already executed file (same md5) so you must mark it as "ok" . The execute routine checks the md5 before any operation and returns this error if the same md5 already exists in DB.
It is not a bug for me.
What do you propose? Do you have a better way to manage this kind of files?
Since it is impossible to rerun the update even if you want to, the MD5 needs to be checked prior to deciding that there are database updates to run. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.