Last modified: 2012-05-03 02:42:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 34285 - Make use of rev_sha1 per-wiki configurable
Make use of rev_sha1 per-wiki configurable
Product: MediaWiki
Classification: Unclassified
Export/Import (Other open bugs)
All All
: High normal (vote)
: 1.19.0 release
Assigned To: Aaron Schulz
Depends on:
Blocks: 31217 33994
  Show dependency treegraph
Reported: 2012-02-08 22:30 UTC by Mark A. Hershberger
Modified: 2012-05-03 02:42 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Mark A. Hershberger 2012-02-08 22:30:46 UTC
<robla> hexmode: can you file a blocking bug for AaronSchulz to make the MD5
        stuff per wiki configurable?
Comment 1 Sam Reed (reedy) 2012-02-09 01:33:53 UTC
Needs doing when we branch 1.19wmf1

Not actually that much to do, just don't attempt to select the column, and don't attempt to insert a value for rev_sha1

Most of the rest of the code is reasonably sane that it'll just carry on and mark it as not having been calculated (ie ''), as it's output in very few places
Comment 2 Sam Reed (reedy) 2012-02-09 01:59:30 UTC
I might just end up doing this after branching as part of the pre deployment prep.

Likely to branch on Friday and then can get the files onto fenari (cause copying to the NFS home directory won't be a quick process this time either), and the initial copy scapped out in an idle state
Comment 3 Rob Lanphier 2012-02-09 18:20:41 UTC
For what it's worth, it should only be important to get this done by the time we deploy to enwiki, since that's where we have the biggest problem.  So, this shouldn't block our deployment to test2, for example.
Comment 4 Aaron Schulz 2012-02-14 21:02:37 UTC
Done in r111486.

Note You need to log in before you can comment on or make changes to this bug.