https://bugzilla.wikimedia.org/show_bug.cgi?id=17057
--- Comment #10 from Aaron Schulz <[email protected]> 2009-07-27 08:32:05 UTC --- (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #5) > > > populateSha1 wouldn't fix anything, since it only works on files which > > > don't > > > have hash in the db. These files do have a hash, although it's wrong. > > > > Adding an overwrite mode sounds trivial. > Running a maintenance script every time a particular image has a hash issue is > impractical. There should be a way to re-generate the hash without requiring a > re-upload or command-line access. Regardless of whether the maintenance script > is adjusted (which it probably should be). Obviously. But we can use to retroactively fix the numerous wrong values, once the reason for the keys getting stuck is found. A sha-1 purge link shouldn't be needed unless something is just flat broken...users shouldn't be expected to deal with that. It could be a temporary stop-gap solution if all else fails though... -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
