Last modified: 2013-05-30 23:44:52 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 T50674, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 48674 - Unable to update submodules on tin
Unable to update submodules on tin
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: High major (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-05-21 09:08 UTC by Sam Reed (reedy)
Modified: 2013-05-30 23:44 UTC (History)
6 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sam Reed (reedy) 2013-05-21 09:08:23 UTC 
Not sure why, but it started happening recently, trying to update (some) submodules give a 403.

Some still work, some don't, and more seem to not be working


reedy@tin:/a/common/php-1.22wmf4$ git submodule update extensions/Wikibase/
error: The requested URL returned error: 403 while accessing https://gerrit.wikimedia.org/r/p/mediawiki/extensions/Wikibase.git/info/refs
fatal: HTTP request failed
Unable to fetch in submodule path 'extensions/Wikibase'
reedy@tin:/a/common/php-1.22wmf4$ git submodule update extensions/CodeReview/
reedy@tin:/a/common/php-1.22wmf4$


It's getting annoying and now I'm updating in /h/w/c on fenari, shifting the files across and modifying extensions/FOOBAR/.git
Comment 1 Chad H. 2013-05-27 18:13:14 UTC 
Lowering to high--workarounds exist.
Comment 2 Greg Grossmeier 2013-05-30 05:17:17 UTC 
Tim: I'm going to assign this to you since you are probably the one most well equipped to handle it. If you don't agree feel free to un-assign and assign someone else :)
Comment 3 Tim Starling 2013-05-30 23:44:52 UTC 
This was apparently due to http.proxy being set in ~reedy/.gitconfig
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links