Can't upgrade repo

[Chirantan Ekbote]

Hi, 

Everytime I run 'repo sync' I see the following warnings:

info: A new version of repo is available

object 69034721e607ecbe8dad736c8ce07d91efdc8353

type commit

tag v1.12.37-cr1

tagger Mike Frysinger <vap...@chromium.org> 1476811349 -0400

Chromium-specific release

gpg: Signature made Tue 18 Oct 2016 10:22:29 AM PDT using RSA key ID 16B500A8

gpg: Can't check signature: public key not found

error: could not verify the tag 'v1.12.37-cr1'

warning: Skipped upgrade to unverified version

I've read the PSA about updating depot_tools, which I've done, and I've verified that the repo I'm using is the one from depot_tools.  This is the output of 'git show' in my depot_tools directory:

commit e9c794ea4e4d1c62729757ed20c3dffb5a877914

Author: Quinten Yearsley <qyea...@google.com>

    Make DoPresubmitChecks unit tests clearer.

I'm sure I'm just missing something stupid.  Anyone know what it is?

[Prathmesh Prabhu Chromium]

cd $(which repo)

git pull

This was posted as a PSA earlier.

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Prathmesh Prabhu Chromium]

oh oops. Didn't even read the email fully.

Scratch that. Your git hash seems recent enough.

Are you running repo sync from inside the chroot? iirc, there used to be some trouble upgrading the repo checkout from inside the chroot.

[Chirantan Ekbote]

Nope, I'm running it outside the chroot.

[Yang]

I got same error when running
repo init:

tag v1.12.37-cr1
tagger Mike Frysinger <vap...@chromium.org> 1476811349 -0400

Chromium-specific release

gpg: Signature made Tue 18 Oct 2016 05:22:29 PM UTC using RSA key ID 16B500A8

gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.37-cr1'

------------------------------------------------------------
By the way, there are only two public key imported to local trustdb:
------------------------------------------------------------
gpg: key 920F5C65: public key "Repo Maintainer <re...@android.kernel.org>" imported
gpg: key 692B382C: public key "Conley Owens <cc...@android.com>" imported

------------------------------------------------------------

[Mike Frysinger]

i don't know why sometimes repo still complains even when it knows about the key

you could try:

cd ~/chromiumos/.repo/repo

git pull

git reset --hard v1.12.37-cr1

and then see if repo starts importing the key

-mike

[wwz...@gmail.com]

Hi, I also meet this question when i run 'repo  sync'. I suggest you check if your repo tool has been installed and inited. If not, you can try install it and inti it in the folder where you want to repo. I try it and it passed .