Last modified: 2013-11-12 16:18:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58618, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56618 - Wikibase maintenance scripts fail if using Wikidata build
Wikibase maintenance scripts fail if using Wikidata build
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
master
All All
: Normal minor (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-05 14:43 UTC by Aude
Modified: 2013-11-12 16:18 UTC (History)
2 users (show)

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


Attachments

Description Aude 2013-11-05 14:43:25 UTC
If Wikibase is in a non-standard location (e.g. another level deep in the extensions folder) then all the maintenance scripts (e.g change dispatcher) fail.

If MW_INSTALL_PATH environment variable is set, then this is not an issue.  

Fortunately, WMF setup defines MW_INSTALL_PATH so the scripts still work, but we shouldn't rely on that completely.
Comment 1 Gerrit Notification Bot 2013-11-05 14:45:14 UTC
Change 93711 had a related patch set uploaded by Aude:
Check Wikidata build install path for dispatchChanges script

https://gerrit.wikimedia.org/r/93711
Comment 2 Gerrit Notification Bot 2013-11-07 10:12:37 UTC
Change 93711 abandoned by Aude:
Check Wikidata build install path for dispatchChanges script

Reason:
prefer https://gerrit.wikimedia.org/r/#/c/93737/ over doing things this way

https://gerrit.wikimedia.org/r/93711
Comment 3 Aude 2013-11-12 15:16:39 UTC
https://gerrit.wikimedia.org/r/#/c/93737/ is merged.  It provides a way to run scripts for extensions and stuff in non-standard locations.

One could also set the MW_INSTALL_PATH environment variable.  WMF sets MW_INSTALL_PATH (dynamically) and uses their own wrapper for scripts, so no problem. :)

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


Navigation
Links