repo v2.11.1 prerelease

Mike Frysinger

unread,

Jan 7, 2021, 6:06:37 PM1/7/21

to Repo and Gerrit Discussion

I've created a new release, but not yet pushed it live. Instead, people have to opt-in to it by passing --repo-rev=main when running `repo init`. You can then run `repo selfupdate && repo version` to double check your local state.

So please bang on things and let us know how it goes. Even "it works" is useful feedback as it means I'm not the only one running it :).
If things look good the rest of this week, I'll publish it next week.

The 2.11 had a minor bug so this resolves that. We'll skip the 2.11 release entirely.

Here's the short log since the last release.

v2.11.1

b64bec6acc0e (Mike Frysinger) launcher: bump version for new release
343d585ff99c (Ian Kasprzak) Fix bug in git trace2 event Write() function when no config present.

v2.11
acf63b28928b (Mike Frysinger) drop pyversion & is_python3 checking
784ccfc040dc (Mike Frysinger) strip python2-only coding:utf-8 & print_function settings
1379a9b1851e (Mike Frysinger) launcher: add test for version requirements
128f34e8741f (Mike Frysinger) main: require Python 3.5 now
30bc354e25cb (Ian Kasprzak) Enable git trace2 event format logging.
ce9b6c43b239 (Mike Frysinger) launcher: abort if python3 reexec failed
47692019b326 (Mike Frysinger) launcher: support Python 3.5 for now
1469c28ec3e2 (Remy Böhmer) project: detach HEAD in internal worktree checkout.
8add62325dbe (Chris McDonald) Add parallelism to 'branches' command
974774761c5d (Jashank Jeremy) docs: Add Markdown inline code marker around inline XML example.
dc60e54d3618 (Mike Frysinger) gitc: write the manifest directly
0a849b660ff3 (Mike Frysinger) replace javadoc docs with standard python style
5e2f32fe1398 (Mike Frysinger) init: reset hard to --repo-rev
51e39d536d92 (Mike Frysinger) manifest_xml: harmonize list fields
6342d5691478 (Fredrik de Groot) Fix tests after "use new main branch"
9dfd69f7730b (Mike Frysinger) run_tests: rewrite to use Python 3
08eb63cea430 (Mike Frysinger) setup: update Python version info

-mike

Mike Frysinger

unread,

Jan 13, 2021, 12:03:25 PM1/13/21

to Repo and Gerrit Discussion

I've pushed this live now.

NB: Repo will automatically check for & upgrade itself. There is no need for users to handle this themselves. This happens once every 24hrs. If you want to force it locally, run `repo selfupdate`.

-mike

SHEN YINGYING

unread,

Jan 18, 2021, 2:29:22 AM1/18/21

to Repo and Gerrit Discussion

i use the following command

repo init -u https://dev.azure.com/**************/****/_git/Test-repo -m manifest.xml --no-clone-bundle --repo-rev=main

SHEN YINGYING

unread,

Jan 18, 2021, 2:29:22 AM1/18/21

to Repo and Gerrit Discussion

Hello ,

i meet the problem when i tried to run repo init , just now i also add the option --repo-rev=main, but also failed

do you know the reason , here is the error message

Receiving objects: 100% (5877/5877), 1.68 MiB | 466.00 KiB/s, done.

Resolving deltas: 100% (4044/4044), done.

repo: error: unable to resolve "main"

fatal: cloning the git-repo repository failed, will remove '.repo\repo'

if i don't use repo-ver=main , make it as "stable" , it will have same error

Receiving objects: 100% (5877/5877), 1.68 MiB | 203.00 KiB/s, done.

Resolving deltas: 100% (4044/4044), done.

repo: error: unable to resolve "stable"

fatal: cloning the git-repo repository failed, will remove '.repo\repo'

在2021年1月14日星期四 UTC+8 上午1:03:25<Mike Frysinger> 写道：

Mike Frysinger

unread,

Jan 19, 2021, 11:52:38 PM1/19/21

to Vadim Bendebury (вб), Repo and Gerrit Discussion

this isn't repo's fault, it's a Chromium/CrOS thing

sync your CrOS checkout to get the fix from crbug.com/1166896

-mike

On Tue, Jan 19, 2021 at 5:34 PM Vadim Bendebury (вб) <vbe...@google.com> wrote:

I started getting this error inside chroot:

$ repo sync
depot_tools update failed. Conflict in /mnt/host/depot_tools
fatal: not a git repository (or any parent up to mount point /mnt/host)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Outside chroot repo sync succeeds. Any idea what's going on?

TIA,
-vb

--
You received this message because you are subscribed to the Google Groups "Repo tool (git-repo) announcements" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-repo-annou...@google.com.
To view this discussion on the web visit https://groups.google.com/a/google.com/d/msgid/git-repo-announce/CAAbOScneL-n70t5jjBCQ5i5XKeqBq5WRE-RiLLKjjqALM0TgWA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "chromeos-chatty-eng" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromeos-chatty...@google.com.
To view this discussion on the web visit https://groups.google.com/a/google.com/d/msgid/chromeos-chatty-eng/CAAbOScneL-n70t5jjBCQ5i5XKeqBq5WRE-RiLLKjjqALM0TgWA%40mail.gmail.com.

Mike Frysinger

unread,

Jan 20, 2021, 12:52:26 AM1/20/21

to Bob Moragues, Repo and Gerrit Discussion

you will need to go into .repo/repo/ and run `git checkout -f`. there were bugs in earlier releases that caused this, but 2.11+ should fix it.

-mike

On Wed, Jan 20, 2021 at 12:48 AM Bob Moragues <mora...@google.com> wrote:

Hi Mike -

I have noticed a bit of strange behavior recently.
Is this related to this recent 2.11 RC?

I see both 2.10 and 2.11 version numbers below.
Should this have auto-updated to the 2.11.1 that you mention in this email?

-Bob

moragues@moragues-cloud:~/chromeos/master/src/platform/signing/signer-dev$ repo sync .
remote: Finding sources: 100% (6/6)
remote: Total 6 (delta 3), reused 6 (delta 3)
Fetching projects: 100% (1/1), done.
src/platform/signing/signer-dev: Shared project chromeos/cros-signing found, disabling pruning.
info: A new version of repo is available

error: .repo/repo/: contains uncommitted changes
moragues@moragues-cloud:~/chromeos/master/src/platform/signing/signer-dev$ repo --version
repo version v2.10-cr1
(from https://chromium.googlesource.com/external/repo.git)
(Mon, 30 Nov 2020 19:03:56 -0500)
repo launcher version 2.11
(from /usr/local/google/home/moragues/depot_tools/repo_launcher)
(currently at 2.10-cr1)
repo User-Agent git-repo/2.10-cr1 (Linux) git/2.30.0.284.gd98b1dd5eaa7-goog Python/3.6.8
git 2.30.0.284.gd98b1dd5eaa7-goog
git User-Agent git/2.30.0.284.gd98b1dd5eaa7-goog (Linux) git-repo/2.10-cr1
Python 3.6.8 (default, Jan 3 2019, 03:42:36)
[GCC 8.2.0]
OS Linux 5.7.17-1rodete4-amd64 (#1 SMP Debian 5.7.17-1rodete4 (2020-10-01))
CPU x86_64 (unknown)
moragues@moragues-cloud:~/chromeos/master/src/platform/signing/signer-dev$

Looking at .repo/repo, I see this. Is this an artifact of a failed update?

moragues@moragues-cloud:~/chromeos/master/.repo/repo$ git status
On branch default
Your branch is behind 'origin/main' by 21 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)

Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: .github/workflows/test-ci.yml
modified: SUBMITTING_PATCHES.md
modified: docs/internal-fs-layout.md
modified: docs/manifest-format.md
modified: docs/python-support.md
modified: docs/release-process.md
modified: docs/repo-hooks.md
deleted: hooks.py
modified: main.py
modified: manifest_xml.py
modified: project.py
modified: repo
modified: subcmds/diffmanifests.py
modified: subcmds/help.py
modified: subcmds/info.py
modified: subcmds/init.py
modified: subcmds/manifest.py
modified: subcmds/status.py
modified: subcmds/sync.py
modified: subcmds/upload.py
deleted: tests/test_hooks.py
modified: tests/test_manifest_xml.py
modified: tests/test_project.py
modified: tests/test_wrapper.py

Doing the suggested git pull seemed to clear up the situation for me.

Just mentioning it, in case this is an unexpected side effect.

Have a good week.

-Bob