Exception using repo sync --current-branch

[Luciano Carvalho]

All,

I want to thank you for the --current-branch option released with repo 1.8.2 . It reduced my workspace size from 59GB to 34GB

It's perfect if you're working with a single manifest branch.

I ran into an issue a couple times though.

When I have a project in the manifest with revision=SHA1 for example, it'll break and throw the following exception up:

Exception in thread Thread-7:

Traceback (most recent call last):

  File "/usr/local/lib/python2.5/threading.py", line 486, in __bootstrap_inner

    self.run()

  File "/usr/local/lib/python2.5/threading.py", line 446, in run

    self.__target(*self.__args, **self.__kwargs)

  File "/root/workspace/nr5/.repo/repo/subcmds/sync.py", line 200, in _FetchHelper

    clone_bundle=not opt.no_clone_bundle)

  File "/root/workspace/nr5/.repo/repo/project.py", line 986, in Sync_NetworkHalf

    self._InitMRef()

  File "/root/workspace/nr5/.repo/repo/project.py", line 1760, in _InitMRef

    self._InitAnyMRef(R_M + self.manifest.branch)

  File "/root/workspace/nr5/.repo/repo/project.py", line 1772, in _InitAnyMRef

    self.bare_git.UpdateRef(ref, dst, message = msg, detach = True)

  File "/root/workspace/nr5/.repo/repo/project.py", line 1946, in UpdateRef

    self.update_ref(*cmdv)

  File "/root/workspace/nr5/.repo/repo/project.py", line 2007, in runner

    p.stderr))

GitError: android/platform/cts update-ref: fatal: 0e0ff7494a35d05618923cb11586d9487cf5b62e^0: not a valid SHA1

If I'm using Jenkins' gerrit-repo plugin for example, I cannot use the manifest it generates for every build for syncing.

Thanks in advance for taking a look at it.

Luciano.

[Anatol Pomazau]

Hi

This change (merged after 1.8.2 release) should fix the issue https://gerrit-review.googlesource.com/#/c/34761/

 

If I'm using Jenkins' gerrit-repo plugin for example, I cannot use the manifest it generates for every build for syncing.

Thanks in advance for taking a look at it.

Luciano.

--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

[Luciano Carvalho]

Thanks.
Any plan to release a new tag soon?
1.8.2.1 maybe. :-)

[kevin]

Same question here. May I know when we will have a new official release get this patch included? My team is really rely on --current-branch option to reduce the downloaded repo size and would like to have a new version of repo tool with this issue fixed ASAP. Thanks a lot.

Best regards,

Kevin

Hi

Luciano.

--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com

[Luciano Carvalho]

+1 for a  1.8.2.1 with this fix.  :-)

Do we have more support?

Thanks

--
To unsubscribe, email repo-discuss...@googlegroups.com

[Luciano Carvalho]

Works fine with 1.9.1 here...  its out for some time already.

On Jun 11, 2012 1:13 AM, "kevin" <kevin.g...@gmail.com> wrote:

Hello, any good news? 

Regards,

Kevin