I am trying to run repo init and repo sync commands and having trouble with them as detailed below:
repo init -u <git-url> -b release -m <manifest-xml> --repo-url=<url> --repo-branch=<branch>
I was getting the following error
gpg: Can't check signature: No public key
fatal: cloning the git-repo repository failed, will remove '.repo/repo'
but then I followed these steps and was able to get it to work but then repo sync fails now
repo sync
warning: Python 3 support is currently experimental. YMMV.
Please use Python 2.6 - 2.7 instead.
Traceback (most recent call last):
File "/home/tmp/.repo/repo/main.py", line 500, in <module>
_Main(sys.argv[1:])
File "/home/tmp/.repo/repo/main.py", line 476, in _Main
result = repo._Run(argv) or 0
File "/home/tmp/.repo/repo/main.py", line 155, in _Run
result = cmd.Execute(copts, cargs)
File "/home//tmp/.repo/repo/subcmds/sync.py", line 624, in Execute
submodules_ok=opt.fetch_submodules)
File "/home/tmp/.repo/repo/command.py", line 148, in GetProjects
all_projects_list.extend(derived_projects.values())
AttributeError: 'dict_values' object has no attribute 'extend'
Is it implying I need to use python 2 now? I thought repo version 1.22 would require python 3.6+
Is this a safe solution?
I even tried this solution to no avail
warning: Python 3 support is currently experimental. YMMV.python -Vis 2.7.12python -Vmay report 2.7.12, the version of python thatrepois getting is 3.something. You might want to figure out why that is the case and fix that first. (It seems odd that the virtualenv trick did not work - that's how I normally deal with these Python version issues myself, and it works fine for me in multiple OSes.)repo initcommand to work, and nowrepo syncseemingly requires python 2.x