google / moe-py Goto Github PK

A system for synchronizing repositories

Makefile 0.03% Python 25.81% JavaScript 0.50% CSS 0.61% HTML 0.86% Java 72.12% Shell 0.01% PHP 0.01% C++ 0.02% Protocol Buffer 0.04%

moe-py's Introduction

MOE-py

A system for synchronizing repositories

Installation

Please see the wiki pages for installation and setup instructions.

Project status

This is the project originally hosted at http://code.google.com/p/make-open-easy, written in python, to synchronize private and open-source repositories. It is not under active development, though many stil find it useful

A related java-basedtool is under active (resumed) development at http://github.com/google/MOE, which does not require an active server, but uses JSON files to store migrations and equivalencies.

The python-based scrubber infrastructure is used by some installations of java-moe.

License

  Copyright 2011 Google, Inc. All Rights Reserved.

  Licensed under the Apache License, Version 2.0 (the "License");
  you may not use this file except in compliance with the License.
  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.

moe-py's People

Contributors

Stargazers

Watchers

Forkers

jlnewton zippelmitz pir8aye kshithijiyer neotim neverso isabella232 ghas-results

moe-py's Issues

Installation instructions need to address OS X libutf installation

OS X has switched to x86_64 by default, but the libutf Makefile uses 
per-platform makefiles and only has Make.Darwin-i386, so doesn't compile by 
default. homebrew deals with this by just manually overwriting the line in the 
Makefile, and this seems to work: 
https://github.com/mxcl/homebrew/pull/14766/files

I guess somebody could also chase it down upstream and make them do the right 
thing?

Original issue reported on code.google.com by [email protected] on 19 Mar 2013 at 9:48

empty commit results in an error

When there is nothing to commit git returns an error code of 1 which halts the 
process.

git command ['commit', '-m', '\n\n\nRevision created by MOE tool 
push_codebase.\nMOE_MIGRATION=\n'] in /tmp/moe.macvicar/dbproxy/git returned 1
# On branch master
nothing to commit (working directory clean)

Patch adds in ChangesMade() check prior to commit.

Original issue reported on code.google.com by [email protected] on 8 Apr 2011 at 12:47

Attachments:

git_empty_commit.diff

Initial repository creation asks for svn username / passwords

We're pushing to git for out initial commit, it prompts for svn username / 
password and these have a hardcoded message about google code.

Patch to expose Types from the config and hide this if its not subversion.

Original issue reported on code.google.com by [email protected] on 8 Apr 2011 at 12:46

Attachments:

svn_initial_checkout.diff

git config throws key errors for things that should be optional

Our public repository config was

 "public_repository": {
  "type": "git",
  "url": "ssh://[email protected]:facebook/project_name.git"
 },

It threw a key exception for branch, so I added master as the branch then it 
threw a key exception for gerrit_autoapprove.

Small Stacktrace:

  File "/usr/local/lib/python2.6/dist-packages/moe-0.1-py2.6.egg/moe/config.py", line 187, in MoeProjectConfigFromJson
    project_space=base.PUBLIC_STR)
  File "/usr/local/lib/python2.6/dist-packages/moe-0.1-py2.6.egg/moe/config.py", line 274, in MakeRepositoryConfig
    project_space=project_space)
  File "/usr/local/lib/python2.6/dist-packages/moe-0.1-py2.6.egg/moe/git.py", line 469, in __init__
    self.gerrit_autoapprove = config_json['gerrit_autoapprove']

Original issue reported on code.google.com by [email protected] on 7 Apr 2011 at 11:27

make install fails to copy the "comment" resource

When I checkout the code and run:

  sudo make install

the MOE scrubber code ends up in 
/usr/local/lib/python2.7/dist-packages/moe-0.1-py2.7.egg.

Unfortunately, one file that does not end up in there is:

  moe/scrubber/comment

Without this file, the following line in comment_scrubber.py fails:

  extractor_binary = resources.GetResourceFilename(base.ResourceName('comment')\
)

In my case, I manually copied this file to 
/usr/local/lib/python2.7/dist-packages/moe-0.1-py2.7.egg/moe/scrubber/comment, 
but it would be nice if the installation process did this automatically.

Original issue reported on code.google.com by [email protected] on 9 Nov 2012 at 6:38

Fix typos in ScrubberConfig

Fix typos in ScrubberConfig

Original issue reported on code.google.com by [email protected] on 14 Aug 2014 at 10:45

Attachments:

ScrubberConfig.wiki.patch

Fix Makefile to work on CentOS

Unfortunately, CentOS 5.8 has some stupid version of flex that does not 
tolerate a space after -o:

http://sourceware.org/ml/crossgcc/2012-06/msg00008.html

Please change:

  flex  -o moe/scrubber/comment.yy.c moe/scrubber/comment.l

to:

  flex  -omoe/scrubber/comment.yy.c moe/scrubber/comment.l

Original issue reported on code.google.com by [email protected] on 22 Mar 2013 at 7:09

google / moe-py Goto Github PK

moe-py's Introduction

MOE-py

Installation

Project status

License

moe-py's People

Contributors

Stargazers

Watchers

Forkers

moe-py's Issues

Recommend Projects

Recommend Topics

Recommend Org