My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2444: repo: <remove-project> no longer working
1 person starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Jan 2014


Sign in to add a comment
 
Reported by jona...@gmail.com, Jan 30, 2014
************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.    *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS!  *****
************************************************************

Affected Version: v1.12.9

What steps will reproduce the problem?
1. Using an android environment, add this line to a local manifest:   <remove-project name="platform/packages/inputmethods/LatinIME" />
2. rm -rf packages/inputmethods/LatinIME
3. repo sync packages/inputmethods/LatinIME

What is the expected output? What do you see instead?
"error: project packages/inputmethods/LatinIME is not found"
And no code should be synced.

Instead there's no such error and the code is synced.

Since remove-project doesn't work I cannot replace an existing project in a manifest in a local manifest. 

Please provide any additional information below.

Using git bisect I have narrowed the problem down to this change:
commit 8d20116038ff78b22069dd4e993b5819775f03d1
Author: David James <davidjames@google.com>
Date:   Fri Oct 11 17:03:19 2013 -0700

    repo: Support multiple branches for the same project.

    It is often useful to be able to include the same project more than
    once, but with different branches and placed in different paths in the
    workspace. Add this feature.

    This CL adds the concept of an object directory. The object directory
    stores objects that can be shared amongst several working trees. For
    newly synced repositories, we set up the git repo now to share its
    objects with an object repo.

    Each worktree for a given repo shares objects, but has an independent
    set of references and branches. This ensures that repo only has to
    update the objects once; however the references for each worktree are
    updated separately. Storing the references separately is needed to
    ensure that commits to a branch on one worktree will not change the
    HEAD commits of the others.

    One nice side effect of sharing objects between different worktrees is
    that you can easily cherry-pick changes between the two worktrees
    without needing to fetch them.

    Bug:  Issue 141 
    Change-Id: I5e2f4e1a7abb56f9d3f310fa6fd0c17019330ecd
Jan 30, 2014
#1 jona...@gmail.com
Since repo is auto-updating to the latest version, this bug if quite severe and I would expect a lot of builds to start failing shortly.
Jan 30, 2014
Project Member #2 jrn@google.com
The repo issue tracker is at https://code.google.com/p/git-repo/issues/list
Status: Invalid
Jan 30, 2014
#3 jonas.be...@senseg.com
Ok, sorry!
Jan 30, 2014
Project Member #4 jrn@google.com
No problem. If I could move the issue myself I would have done that instead.
Sign in to add a comment

Powered by Google Project Hosting