Google Git
Sign in
gerrit / git-repo / 0531a623e19dd414840d062e19048a2ee5def235
commit0531a623e19dd414840d062e19048a2ee5def235[log] [tgz]
authorMike Frysinger <vapier@google.com>Fri Nov 05 15:22:01 2021 -0400
committerMike Frysinger <vapier@google.com>Fri Nov 05 20:13:30 2021 +0000
treea71c8b20c5ba9aa67df7568e7d8ca3b21496fa31
parent2273f46cb36893d20ab77d4dde1461d670d88e2c [diff]
sync: make --prune the default

If a remote deletes a ref, and it points to an object that doesn't
exist locally, we can get into a bad state, and the only way for the
user to recover is to run `repo sync --prune` (and to know that is
the option they need).  The error message is not helpful:

fatal: bad object refs/remotes/cros/firmware-zork-13421.B-master
error: https://chromium.googlesource.com/chromiumos/platform/ec did not send all necessary objects

This situation can also come up when the remote renames refs in a
UNIX FS incompatible way.  For example, replacing refs/heads/foo
with refs/heads/foo/bar.

Also add a --no-prune option for users to disable the behavior.

Bug: https://issuetracker.google.com/203366450
Change-Id: Icf45d838a10938feb091d29800f7e49240830ec3
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/322956
Reviewed-by: Andrew Lamb <andrewlamb@google.com>
Tested-by: Mike Frysinger <vapier@google.com>
1 file changed
tree: a71c8b20c5ba9aa67df7568e7d8ca3b21496fa31
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .mailmap
  12. .project
  13. .pydevproject
  14. color.py
  15. command.py
  16. completion.bash
  17. editor.py
  18. error.py
  19. event_log.py
  20. fetch.py
  21. git_command.py
  22. git_config.py
  23. git_refs.py
  24. git_ssh
  25. git_superproject.py
  26. git_trace2_event_log.py
  27. gitc_utils.py
  28. hooks.py
  29. LICENSE
  30. main.py
  31. MANIFEST.in
  32. manifest_xml.py
  33. pager.py
  34. platform_utils.py
  35. platform_utils_win32.py
  36. progress.py
  37. project.py
  38. README.md
  39. repo
  40. repo_trace.py
  41. requirements.json
  42. run_tests
  43. setup.py
  44. ssh.py
  45. SUBMITTING_PATCHES.md
  46. tox.ini
  47. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo