repo is not yet installed. Use "repo init" to install it here.

[Babak Rezai]

Um, *embarrassed* here, I setup depot_tools before but can't seem to get it to work this time on an new install.

why is repo not working correctly, seems to me that its included in the path appropriately.

babak@G750JHA ~/chromiumos $ cat ~/.bashrc

export PATH=`pwd`/depot_tools:$PATH

export PATH=/opt/android-sdk-linux/tools:/opt/android-sdk-linux/platform-tools:/opt/android-studio/bin:$PATH

export LD_LIBRARY_PATH=/usr/lib/nvidia-319-updates:$LD_LIBRARY_PATH

babak@G750JHA ~ $ echo $PATH
/opt/android-sdk-linux/tools:/opt/android-sdk-linux/platform-tools:/opt/android-studio/bin:/home/babak/depot_tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
babak@G750JHA ~ $ cd chromiumos/
babak@G750JHA ~/chromiumos $ ls

babak@G750JHA ~/chromiumos $ repo init -u https://chromium.googlesource.com/chromiumos/manifest.git --repo-url https://chromium.googlesource.com/external/repo.git

Get https://chromium.googlesource.com/external/repo.git

remote: Counting objects: 102, done

remote: Finding sources: 100% (102/102)

remote: Total 2006 (delta 1245), reused 2006 (delta 1245)

Receiving objects: 100% (2006/2006), 850.97 KiB | 630 KiB/s, done.

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

From https://chromium.googlesource.com/external/repo

== SNIPPED ==

babak@G750JHA ~/chromiumos $ repo sync
error: command 'sync' requires repo to be installed first.
Use "repo init" to install it here.

[Matt Tennant]

Confusingly, the "repo" that needs to be installed first is not the "repo" command but the .repo directory/manifest.  Basically, the stuff that "repo init" is supposed to do.  Were there no errors reported in the snipped output?

-Matt

--
--
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
 

[Babak Rezai]

Here's what I omitted, nothing looked like it would cause it to not init...there is that signature thing at the end.

I figured that was somewhat trivial.

From https://chromium.googlesource.com/external/repo

 * [new branch]      maint      -> origin/maint

 * [new branch]      master     -> origin/master

 * [new branch]      stable     -> origin/stable

 * [new tag]         v1.0       -> v1.0

 * [new tag]         v1.0.1     -> v1.0.1

 * [new tag]         v1.0.2     -> v1.0.2

 * [new tag]         v1.0.3     -> v1.0.3

 * [new tag]         v1.0.4     -> v1.0.4

 * [new tag]         v1.0.5     -> v1.0.5

 * [new tag]         v1.0.6     -> v1.0.6

 * [new tag]         v1.0.7     -> v1.0.7

 * [new tag]         v1.0.8     -> v1.0.8

 * [new tag]         v1.0.9     -> v1.0.9

 * [new tag]         v1.1       -> v1.1

 * [new tag]         v1.10.0    -> v1.10.0

 * [new tag]         v1.10.1    -> v1.10.1

 * [new tag]         v1.10.2    -> v1.10.2

 * [new tag]         v1.10.3    -> v1.10.3

 * [new tag]         v1.10.4    -> v1.10.4

 * [new tag]         v1.11.0    -> v1.11.0

 * [new tag]         v1.11.1    -> v1.11.1

 * [new tag]         v1.11.1-cr1 -> v1.11.1-cr1

 * [new tag]         v1.11.1-cr2 -> v1.11.1-cr2

 * [new tag]         v1.11.1-cr3 -> v1.11.1-cr3

 * [new tag]         v1.11.1-cr4 -> v1.11.1-cr4

 * [new tag]         v1.2       -> v1.2

 * [new tag]         v1.3       -> v1.3

 * [new tag]         v1.3.1     -> v1.3.1

 * [new tag]         v1.3.2     -> v1.3.2

 * [new tag]         v1.4       -> v1.4

 * [new tag]         v1.4.1     -> v1.4.1

 * [new tag]         v1.4.2     -> v1.4.2

 * [new tag]         v1.4.3     -> v1.4.3

 * [new tag]         v1.4.4     -> v1.4.4

 * [new tag]         v1.5       -> v1.5

 * [new tag]         v1.5.1     -> v1.5.1

 * [new tag]         v1.6       -> v1.6

 * [new tag]         v1.6.1     -> v1.6.1

 * [new tag]         v1.6.10    -> v1.6.10

 * [new tag]         v1.6.10.1  -> v1.6.10.1

 * [new tag]         v1.6.10.2  -> v1.6.10.2

 * [new tag]         v1.6.2     -> v1.6.2

 * [new tag]         v1.6.3     -> v1.6.3

 * [new tag]         v1.6.4     -> v1.6.4

 * [new tag]         v1.6.5     -> v1.6.5

 * [new tag]         v1.6.6     -> v1.6.6

 * [new tag]         v1.6.7     -> v1.6.7

 * [new tag]         v1.6.7.1   -> v1.6.7.1

 * [new tag]         v1.6.7.2   -> v1.6.7.2

 * [new tag]         v1.6.7.3   -> v1.6.7.3

 * [new tag]         v1.6.7.4   -> v1.6.7.4

 * [new tag]         v1.6.7.5   -> v1.6.7.5

 * [new tag]         v1.6.8     -> v1.6.8

 * [new tag]         v1.6.8.1   -> v1.6.8.1

 * [new tag]         v1.6.8.10  -> v1.6.8.10

 * [new tag]         v1.6.8.11  -> v1.6.8.11

 * [new tag]         v1.6.8.2   -> v1.6.8.2

 * [new tag]         v1.6.8.3   -> v1.6.8.3

 * [new tag]         v1.6.8.4   -> v1.6.8.4

 * [new tag]         v1.6.8.5   -> v1.6.8.5

 * [new tag]         v1.6.8.6   -> v1.6.8.6

 * [new tag]         v1.6.8.7   -> v1.6.8.7

 * [new tag]         v1.6.8.8   -> v1.6.8.8

 * [new tag]         v1.6.8.9   -> v1.6.8.9

 * [new tag]         v1.6.9     -> v1.6.9

 * [new tag]         v1.6.9.1   -> v1.6.9.1

 * [new tag]         v1.6.9.2   -> v1.6.9.2

 * [new tag]         v1.6.9.3   -> v1.6.9.3

 * [new tag]         v1.6.9.4   -> v1.6.9.4

 * [new tag]         v1.6.9.5   -> v1.6.9.5

 * [new tag]         v1.6.9.6   -> v1.6.9.6

 * [new tag]         v1.6.9.7   -> v1.6.9.7

 * [new tag]         v1.6.9.8   -> v1.6.9.8

 * [new tag]         v1.7       -> v1.7

 * [new tag]         v1.7.1     -> v1.7.1

 * [new tag]         v1.7.2     -> v1.7.2

 * [new tag]         v1.7.3     -> v1.7.3

 * [new tag]         v1.7.3.1   -> v1.7.3.1

 * [new tag]         v1.7.4     -> v1.7.4

 * [new tag]         v1.7.4.1   -> v1.7.4.1

 * [new tag]         v1.7.4.2   -> v1.7.4.2

 * [new tag]         v1.7.4.3   -> v1.7.4.3

 * [new tag]         v1.7.5     -> v1.7.5

 * [new tag]         v1.7.6     -> v1.7.6

 * [new tag]         v1.7.6.1   -> v1.7.6.1

 * [new tag]         v1.7.7     -> v1.7.7

 * [new tag]         v1.7.7.1   -> v1.7.7.1

 * [new tag]         v1.7.7.2   -> v1.7.7.2

 * [new tag]         v1.7.7.3   -> v1.7.7.3

 * [new tag]         v1.7.7.4   -> v1.7.7.4

 * [new tag]         v1.7.7.5   -> v1.7.7.5

 * [new tag]         v1.7.7.6   -> v1.7.7.6

 * [new tag]         v1.7.8     -> v1.7.8

 * [new tag]         v1.7.8.1   -> v1.7.8.1

 * [new tag]         v1.7.8.2   -> v1.7.8.2

 * [new tag]         v1.8.0     -> v1.8.0

 * [new tag]         v1.8.1     -> v1.8.1

 * [new tag]         v1.8.2     -> v1.8.2

 * [new tag]         v1.9.0     -> v1.9.0

 * [new tag]         v1.9.1     -> v1.9.1

 * [new tag]         v1.9.2     -> v1.9.2

 * [new tag]         v1.9.3     -> v1.9.3

 * [new tag]         v1.9.4     -> v1.9.4

 * [new tag]         v1.9.5     -> v1.9.5

 * [new tag]         v1.9.6     -> v1.9.6

object 26488179d666fc3a18010cc6aa2749941639df58

type commit

tag v1.11.1-cr4

tagger Stefan Zager <sza...@chromium.org> 1382466203 -0700

Chromium-specific release.

gpg: Signature made Tue 22 Oct 2013 11:23:31 AM PDT using RSA key ID 18275935

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

error: could not verify the tag 'v1.11.1-cr4'

[Matt Tennant]

You might be picking up another repo tool from earlier in your PATH, instead of the one in the depot_tools.  You have some android sdk stuff in your path.

What do the following commands say:

repo --version

which repo

[Mike Frysinger]

also make sure your depot tools repo is up-to-date

-mike

[Babak Rezai]

:P Strange

babak@G750JHA ~/chromiumos $ repo --version

error: repo is not installed.  Use "repo init" to install it here.

babak@G750JHA ~/chromiumos $ which repo

/home/babak/depot_tools/repo

[Matt Tennant]

So the PATH is probably not a problem.  The "repo --version" does have to be run within a repo checkout, it looks like, but I have a hunch now that Mike's advice of just updating depot tools is all you need.

git pull in depot_tools should do it.

--

[David James]

On Mon, Dec 30, 2013 at 3:06 PM, Babak Rezai <babak...@gmail.com> wrote:

Try this:

$ grep ^VERSION ~/depot_tools/repo 

The expected answer is:

VERSION = (1, 18)

If you get a different version, then this means that /home/babak/depot_tools/repo has local modifications (or is not up to date). Try looking in that directory and reverting any local changes.

Cheers,

David

[Babak Rezai]

I just pulled it today from git.

[Babak Rezai]

It def matches.

babak@G750JHA ~ $ grep ^VERSION ~/depot_tools/repo 

VERSION = (1, 18)

[Mike Frysinger]

then try as Matt suggested -- make sure depot_tools is first in your $PATH

-mike

--

[Babak Rezai]

it is, my bashrc contains:

export PATH=`pwd`/depot_tools:$PATH

export PATH=/opt/android-sdk-linux/tools:/opt/android-sdk-linux/platform-tools:/opt/android-studio/bin:$PATH

export LD_LIBRARY_PATH=/usr/lib/nvidia-319-updates:$LD_LIBRARY_PATH

I did clone it again, but still the same issue. Kinda odd.

[Mike Frysinger]

no, you've put android paths before depot_tools

-mike

[Babak Rezai]

Not sure how to work order with bashrc , I just removed the android stuff from the PATH, tried again that didn't work.

Then I rm -rf .repo* from my home and re-init everything. All working good now :D , not sure if it was a conflict with 

android repo or something was up in the .repo* files. I'll try re-adding them see.

[hram...@gmail.com]

Well, the dev guide is bogus.

You need the keys which are used to sign the repo releases to check out the repo or pass --no-repo-verify to repo init. Since the guide does not tell how to get the keys you have to check out the repo without verification.

HTH

Michal
 

[Mike Frysinger]

sorry, but that is incorrect.  if you follow the dev guide, one of the first steps is to check out depot_tools.git and put that first in your $PATH.

-mike

[Michal Suchanek]

Well, you get those. So what? That gives you the repo tool but not the
keys. And without the keys the init step fails unless you pass
--no-repo-verify. You get some keys later when you have created the
chroot but that's way too late.

Thanks

Michal

[Mike Frysinger]

> Well, you get those. So what? That gives you the repo tool but not the
> keys.

in other words, you haven't actually tried what the documentation said
to do, nor did you actually read the code that's in said repo. please
try both first before posting again.
-mike

[Michal Suchanek]

I followed this doc
https://sites.google.com/a/chromium.org/dev/chromium-os/developer-guide
and got the exact same error as the OP.

The error is caused by the instructions in the document being
incomplete. I read through the steps before "get the source" again and
in none of those there is a step that gives you the public keys of the
repo signatures I could find.

As a result the "get the source" step fails with the gpg error. To
read through the source you would have to get it first. Or what source
did you mean here?

M

[Michal Suchanek]

Oh, indeed. The repo tool from dept_tools has the very key you are
missing if you follow the guide.

Skimming through the code it looks like if you did sync and did not
have the keys set up it would set them up them for you. Problem is you
never get there because you can only sync after you init and init
fails without the keys.

So it indeed looks broken to me.

Did *you* actually look at the guide and code :->

Michal

[Steev Klimaszewski]

I've just run into this here as well...   I'm not entirely sure why, but my ~/.repoconfig directory appeared to be missing the gnupg directory, so i just rm -r'd ~/.repoconfig and re-ran the repo init command and it imported the key.

--
--
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

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Mike Frysinger]

> Oh, indeed. The repo tool from dept_tools has the very key you are
> missing if you follow the guide.
>
> Skimming through the code it looks like if you did sync and did not
> have the keys set up it would set them up them for you. Problem is you
> never get there because you can only sync after you init and init
> fails without the keys.

all you've said is "i followed the guide but it didn't work". you
haven't actually stated the actual commands you ran.

running the steps that guide tells you to works perfectly fine for me:
$ cd
$ git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
$ PATH=$PWD/depot_tools:$PATH
$ mkdir chromiumos && cd chromiumos

$ repo init -u https://chromium.googlesource.com/chromiumos/manifest.git
--repo-url https://chromium.googlesource.com/external/repo.git

$ repo sync

worked fine for me
-mike

[Michal Suchanek]

And fails for others. As has been pointed out the cause is that if you
have used repo for anything other than chromeos development before you
follow this guide the existing repo configuration is not updated.

Thanks

Michal

[Tim Dysinger]

Mike,

Protip: a seasoned developer would try verifying claims of bugs by cloning & building in _clean_ environment (not your "worked fine for me [on my well-worn-in personal laptop! SCIENCE! <mic-drop>].")  An experienced dev would see the same gpg verification error on a clean build machine.  A smart developer would do these steps before blasting so as to not offend other smart people. You know! So we can all be smart together without getting offended and calling each other names.

Meanwhile: can someone on this project figure out how gpg works and update depot_tools so the rest of us can build for the first time?  I have no problem building CoreOS (same build system) but ChromiumOS is broken out of the box right now WRT that gpg error.  It just halts & you have to come hunting on maillists for ways to turn off the broken pgp verification.  This probably wasted an hour of my evening last night.

-Tim

[Gaurav Shah]

On Jan 18, 2014 11:11 AM, "Tim Dysinger" <dysi...@gmail.com> wrote:

Mike,

Protip: a seasoned developer would try verifying claims of bugs by cloning & building in _clean_ environment (not your "worked fine for me [on my well-worn-in personal laptop! SCIENCE! <mic-drop>].")  An experienced dev would see the same gpg verification error on a clean build machine.  A smart developer would do these steps before blasting so as to not offend other smart people. You know! So we can all be smart together without getting offended and calling each other names.

Meanwhile: can someone on this project figure out how gpg works and update depot_tools so the rest of us can build for the first time?  I have no problem building CoreOS (same build system) but ChromiumOS is broken out of the box right now WRT that gpg error.  It just halts & you have to come hunting on maillists for ways to turn off the broken pgp verification.  This probably wasted an hour of my evening last night.

I filed crbug.com/335924 for the issue.

Meanwhile, in case anyone missed the workaround Steve mentioned earlier in the thread, try blowing away your ~/.repoconfig directory.

$ mv ~/.repoconfig{,.old}

--

[Mike Frysinger]

i might suggest using some of your own suggestions.  the machine i tested on had never seen repo or chromiumos or android before.  it was one of the various ssh headless machines that i use for completely unrelated work purposes.  but as was pointed out already (in fact, in the e-mails you replied to), the issue isn't with clean machines but with dirty ones.

-mike

--

[Mike Frysinger]

On Sat, Jan 18, 2014 at 3:21 PM, Gaurav Shah <gaur...@google.com> wrote:

On Jan 18, 2014 11:11 AM, "Tim Dysinger" <dysi...@gmail.com> wrote:

Mike,

Protip: a seasoned developer would try verifying claims of bugs by cloning & building in _clean_ environment (not your "worked fine for me [on my well-worn-in personal laptop! SCIENCE! <mic-drop>].")  An experienced dev would see the same gpg verification error on a clean build machine.  A smart developer would do these steps before blasting so as to not offend other smart people. You know! So we can all be smart together without getting offended and calling each other names.

Meanwhile: can someone on this project figure out how gpg works and update depot_tools so the rest of us can build for the first time?  I have no problem building CoreOS (same build system) but ChromiumOS is broken out of the box right now WRT that gpg error.  It just halts & you have to come hunting on maillists for ways to turn off the broken pgp verification.  This probably wasted an hour of my evening last night.

I filed crbug.com/335924 for the issue.

David has already been getting our changes merged into upstream repo so we can drop our copy.  it's really the only way to go (sans blowing away the previous ~/.repoconfig caches which isn't terribly cross-project friendly).

-mike

[Tim Dysinger]

I've reproduced this on clean machines of Ubuntu 12.04.3

Scenario #1 (Success):

Build CoreOS or ChromiumOS by itself.

Senario #2 (Fail):
1) Build CoreOS (Success!)

2) Try to repo init for ChromiumOS (Fail)

Scenario #3 (Fail):

1) Build ChromiumOS (Success!)

2) Try to repo init for CoreOS (Fail).

--

Tim Dysinger | 808-212-3231 | PGP Public Key

[Tim Dysinger]

It took me 5 minutes & some amazon instances to find the problem. I'm glad that we have a bug filed for it now.  Cheers.

[Tim Dysinger]

I filed a bug with CoreOS also

https://github.com/coreos/scripts/issues/153

[Tim Dysinger]

To Mike's credit, this does work on a very clean box brand new box.  It's broken if you've even attempted to init something else with `repo` first.

[Jonas Andersson]

I've been on it for two days.. I dont get any further than this

repo init -u https://chromium.googlesource.com/chromiumos/manifest.git

error: manifest required for this command -- please run init

[David James]

Hi Jonas,

Might you have an old .repo dir lying around somewhere hidden?

Here's an example command that'll test with a completely empty directory.

( rm -rf /tmp/.repo && rm -rf /tmp/foo && mkdir -p /tmp/foo && cd /tmp/foo && repo init -u https://chromium.googlesource.com/chromiumos/manifest.git --repo-url https://chromium.googlesource.com/external/repo.git && repo sync )

Notice how I was careful there to make sure you had no .repo dirs sitting around in /tmp/foo or in a parent dir, like /tmp :)

Please also send the output of:

  $ grep '^VERSION =' $(which repo)

  $ repo version

--
--
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
 

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.