repo command not getting recognized...

[Vikas]

Hi,

I am following the steps on http://source.android.com/source/download.html,
but as soon as I run repo command, it shows an error as below.
vikas@ubuntu:~/mydroid$ repo init
No command 'repo' found, did you mean:
Command 'rep' from package 'rep' (universe)
Command 'repl' from package 'nmh' (universe)
Command 'repl' from package 'mailutils-mh' (universe)
repo: command not found

I am not able to figure out how to run the repo.
Any help?

Thanks,
Vikas

[Jean-Baptiste Queru]

Is it in your path? Is it executable?

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Al Sutton]

You've either missed the step for downloading repo, copying it to the right place, or adding it to your path.

Al.

[amol verule]

Hi,
 have u did these steps?

chmod a+x ~/bin/repo

check ~/bin is in your PATH
echo $PATH
if not then you need to add it

export PATH=~/bin:$PATH
then run repo init

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--
Thanks & Regards,
Verule Amol R.

[Joshua J Mallory]

I had the same problem until I rebooted the computer.

On Jan 17, 1:09 pm, Vikas <vikas.vtan...@gmail.com> wrote:
> Hi,
>

> I am following the steps onhttp://source.android.com/source/download.html,

[Jean-Baptiste Queru]

Some shells (including old versions of bash) don't immediately react
to changes in the PATH. They may have a command to re-parse it, though
(I think it was "rehash" in bash). You might also find that opening a
fresh terminal "works" by making the new shell initialize itself from
scratch.

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--

[Magnus Bäck]

On Tuesday, January 18, 2011 at 23:23 CET,
Jean-Baptiste Queru <j...@android.com> wrote:

> Some shells (including old versions of bash) don't immediately react
> to changes in the PATH. They may have a command to re-parse it, though
> (I think it was "rehash" in bash).

In bash and other Bourne-derivatives it's "hash -r" that flushes the
command cache, but csh and derivatives (plus zsh) have "rehash" instead.
But I always thought negative hits weren't cached, so executables added
to directories in $PATH would get picked up right away.

> You might also find that opening a fresh terminal "works" by making
> the new shell initialize itself from scratch.

I believe Ubuntu's default bashrc adds ~/bin to the path iff it exists,
so users creating that directory and downloading Repo into it will have
to start a new shell or modify $PATH by hand. I suppose

exec bash

would be the easiest way out.

--
Magnus B�ck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson

[Vladimir Lushnikov]

Usually source ~/.profile fixes this as well (on a bash shell)

On Tue, 2011-01-18 at 23:54 +0100, Magnus Bäck wrote:

On Tuesday, January 18, 2011 at 23:23 CET,
     Jean-Baptiste Queru <j...@android.com

> wrote:

> Some shells (including old versions of bash) don't immediately react
> to changes in the PATH. They may have a command to re-parse it, though
> (I think it was "rehash" in bash).

In bash and other Bourne-derivatives it's "hash -r" that flushes the
command cache, but csh and derivatives (plus zsh) have "rehash" instead.
But I always thought negative hits weren't cached, so executables added
to directories in $PATH would get picked up right away.

> You might also find that opening a fresh terminal "works" by making
> the new shell initialize itself from scratch.

I believe Ubuntu's default bashrc adds ~/bin to the path iff it exists,
so users creating that directory and downloading Repo into it will have
to start a new shell or modify $PATH by hand. I suppose

   exec bash

would be the easiest way out.

-- 
Magnus Bäck                      Opinions are my own and do not necessarily
SW Configuration Manager         represent the ones of my employer, etc.
Sony Ericsson

[modyrater]

try installing repo its explained on TI wiki