Last modified: 2014-09-02 11:21:25 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 27961 - Deploy translations made to the Vector extension after December 2010
Deploy translations made to the Vector extension after December 2010
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
unspecified
All All
: High minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net
:
Depends on:
Blocks: 27339
  Show dependency treegraph
 
Reported: 2011-03-09 18:08 UTC by Malafaya
Modified: 2014-09-02 11:21 UTC (History)
6 users (show)

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


Attachments

Description Malafaya 2011-03-09 18:08:02 UTC
Translations I have made to the Vector extension in December are yet not deployed in the live wiki.

I.e.:
r1=78229&r2=78274">http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/Vector/Vector.i18n.php?r1=78229&r2=78274

Changes to other message groups (such as Core or Abusefilter) are up to date and I can spot no problem in those groups.

When WMF MW version was 1.16 I was told the reason Extension Updater could not update Vector was because of a trunk move of this extension in relation to its branch counterpart.

I wonder if this is still the same issue.

Thanks.
Comment 1 Malafaya 2011-03-09 18:09:07 UTC
Link above points to r78274.
Comment 2 Roan Kattouw 2011-03-20 14:52:44 UTC
Fixed by clearing and rebuilding the LU cache. There seemed to be some issues with applying the trunk move you mentioned on the cluster.

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


Navigation
Links