Missing froyo branch?

[Edgard Castro]

I've just tried to repo init the 'froyo' branch but it doesn't seem to exist anymore. What would be the "latest and greatest" non-release available branch? froyo-plus-aosp?

[Jean-Baptiste Queru]

We've been having an issue with the froyo manifest for a few weeks,
and we're still trying to figure out what happened. Every server-side
workaround I've tried so far has failed.

Here's a client-side workaround that doesn't make me proud but that
should get the job done:
-sync an android-2.2.2_r1 client
repo forall -c git checkout korg/froyo
repo forall external/qemu sdk -c git checkout korg/tools_r6

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.

[F D]

Hi JBQ,

Can you help me understand what I'm missing?

I invoked the following:

mkdir froyo
cd froyo
repo init -u git://android.git.kernel.org/platform/manifest.git

repo forall -c git checkout korg/froyo
repo forall external/qemu sdk -c git checkout korg/tools_r6

The 2nd to last command came back almost right away (and silent,
nothing on the shell) while the last command came back with "error:
project external/qemu not found". Do I have to do a "repo sync" first
after initializing? I've done that before in a separate directory and
that took more than an hour and am trying to avoid that if I can as
I'm just trying to get FroYo sources (and, not even everything if I
can, just the ones for the apps).

Thank you.

On Feb 10, 11:12 am, Jean-Baptiste Queru <j...@android.com> wrote:
> We've been having an issue with the froyo manifest for a few weeks,
> and we're still trying to figure out what happened. Every server-side
> workaround I've tried so far has failed.
>
> Here's a client-side workaround that doesn't make me proud but that
> should get the job done:
> -sync an android-2.2.2_r1 client
> repo forall -c git checkout korg/froyo
> repo forall external/qemu sdk -c git checkout korg/tools_r6
>
> JBQ
>

[Jean-Baptiste Queru]

Make that repo init -u
git://android.git.kernel.org/platform/manifest.git -b android-2.2.2_r1
Followed by repo sync
(and then the two repo forall commands I mentioned earlier).

JBQ

[Xianghua Xiao]

same problem here, suddenly froyo branch is gone.

is there a way to get a _fully_ mirror first just in case, the current
mirror only works for certain branch/manifest, e.g. need something
like:
repo init -u URL -m everything-for-android --mirror?

-or-, repo can support it directly by :
repo init -u URL --mirrorall

i believe this will save quite some bandwidth

thanks,
xianghua

[Jean-Baptiste Queru]

That's not currently possible, and not recommended either.

JBQ

[F D]

Thank you for the reply, JBQ.

Will synchronize and check out later.

I just noticed that the "android-8" platform was based on 2.2_r1 and
that's what I'm looking for to be able to have the proper sources to
run through the debugger in Eclipse. If there's a tarball or
something packaged up like that for that specific version, I'd
appreciate pointers to it.

Thank you.

[Xianghua Xiao]

just curious, why is this not recommended.
if I have a local full mirror, and run a cron on it, so local
developers can repo sync from it, it can save both bandwidth and time.

thanks,

[Jean-Baptiste Queru]

If you sync e.g. every 10 minutes for 5 people who'd normally sync
once a day, now you're doing 40 times as many syncs as there would
normally be.

JBQ

[Magnus Bäck]

On Thursday, February 10, 2011 at 22:41 CET,
Xianghua Xiao <xiaoxi...@gmail.com> wrote:

> same problem here, suddenly froyo branch is gone.
>
> is there a way to get a _fully_ mirror first just in case, the current
> mirror only works for certain branch/manifest, e.g. need something
> like:
> repo init -u URL -m everything-for-android --mirror?
>
> -or-, repo can support it directly by :
> repo init -u URL --mirrorall
>
> i believe this will save quite some bandwidth

As JBQ pointed out, you might not necessarily save any bandwidth but
you're likely to load the servers more (depending on how many users
you have and how they work). That said, another reason to be doing
this is that corporate firewalls might block port 9418. We sync the
AOSP gits every night and push them to our internal server so that
all developers can compare and merge from the AOSP branches.

Anyway, I don't understand your problem. Git will by nature clone the
whole repositories with all branches. Using Repo's --mirror option is
probably a good idea, but you'll get all branches regardless.

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

[Xianghua Xiao]

On Fri, Feb 11, 2011 at 1:00 AM, Magnus Bäck
<magnu...@sonyericsson.com> wrote:
> On Thursday, February 10, 2011 at 22:41 CET,
>     Xianghua Xiao <xiaoxi...@gmail.com> wrote:
>
>> same problem here, suddenly froyo branch is gone.
>>
>> is there a way to get a _fully_ mirror first just in case, the current
>> mirror only works for certain branch/manifest, e.g. need something
>> like:
>> repo init -u URL -m everything-for-android --mirror?
>>
>> -or-, repo can support it directly by :
>> repo init -u URL --mirrorall
>>
>> i believe this will save quite some bandwidth
>
> As JBQ pointed out, you might not necessarily save any bandwidth but
> you're likely to load the servers more (depending on how many users
> you have and how they work). That said, another reason to be doing
> this is that corporate firewalls might block port 9418. We sync the
> AOSP gits every night and push them to our internal server so that
> all developers can compare and merge from the AOSP branches.
>
> Anyway, I don't understand your problem. Git will by nature clone the
> whole repositories with all branches. Using Repo's --mirror option is
> probably a good idea, but you'll get all branches regardless.
>
> --

> Magnus Bäck                      Opinions are my own and do not necessarily

> SW Configuration Manager         represent the ones of my employer, etc.
> Sony Ericsson
>

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

repo --mirror will only mirror the manifest you chose, if you want to
switch to a different manifest some projects may not have been
mirrored yet, that's why I'm asking a full-mirror for all projects
upstream. I did similar thing with Rowboat project and it worked well.

i set up the cron to 'repo sync' once per midnight. whenever someone
needs to do a new 'repo init && repo sync" locally they can do it fast
and locally, thus save time and bandwidth, yes firewall could be
another reason.

i am manually editing a full mirror manifest for this purpose now.

thanks,

[Xianghua Xiao]

will Froyo branch be recovered sometime? thanks.

[Jean-Baptiste Queru]

We're working on figuring out what went wrong.

JBQ

--