AOSP source code back online

[Dan Morrill]

Hi!

As you know, like many other projects the Android Open-Source Project was affected by the recent kernel.org downtime. So, we’re pleased to let you know that the Gingerbread source code is now available again, and AOSP git servers are back online.

Even before the kernel.org downtime, it was clear that AOSP was sometimes taxing kernel.org’s git infrastructure. When we did the Gingerbread source release, for example, load due to AOSP made part of kernel.org unusable for several days. This isn’t fair to kernel.org’s staff or the community, so for some time we’ve been preparing our own git hosting on Google servers.

We were finishing up just as kernel.org experienced their downtime, so the Gingerbread source is now available on Google’s servers. Accordingly, the git URLs have changed.

Here are the instructions to access the new git servers:

• You need to get the latest version of the repo tool:
  curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
• You need to initialize a new repository:
  repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1
• The full instructions are at http://source.android.com/source/downloading.html

There are a few limitations to be aware of:

• Our priority has been getting the main source code mirrors back online, so for the moment gitweb source browsing and Gerrit Code Review are still unavailable.
• We are now working on bringing AOSP’s Gerrit Code Review site back up, and hope to be able to say something here soon.
• It might be a little while longer before gitweb comes back, unfortunately, since Gerrit Code Review is the next priority.
• To reiterate, these servers contain only the ‘gingerbread’ and ‘master’ branches from the old AOSP servers. We plan to release the source for the recently-announced Ice Cream Sandwich soon, once it’s available on devices.
• As these new servers are, well, new, there may be hiccups if we encounter unexpected issues. However we’re keeping a close eye on them and will respond to any issues as quickly as possible.

Finally, we’d like to send a huge “thank-you” to the kernel.org community and Oregon State University Open-Source Lab staff. They’ve done an incredible job hosting the AOSP source code mirror and Gerrit Code Review for nearly 3 years. Without them, it’s safe to say that AOSP would not be where we are today.

Thanks, and happy coding!

- Dan

[Carlos Silva]

Hurray for that! :)

See as it doesn't hurt to speek to us? (Devs)

Now off to host a mirror... just in case :P

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

You will not that the manifests now use relative URLs to find the
projects, so that you can mirror all the projects unmodified
(including the manifests) and not have to worry about url.insteadOf
git configs or other such tricks. That should make it much easier for
anyone to host straight clean mirrors.

JBQ

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

[Carlos Silva]

On Wed, Oct 19, 2011 at 21:31, Jean-Baptiste Queru <j...@android.com> wrote:

You will not that the manifests now use relative URLs to find the
projects, so that you can mirror all the projects unmodified
(including the manifests) and not have to worry about url.insteadOf
git configs or other such tricks. That should make it much easier for
anyone to host straight clean mirrors.

JBQ

2 #win's in 2 posts :)

Congrats to everyone @ Google and Android team 

[Matt Oakes]

Thank you, thank you, thank you, thank you, and again, thank you!

[jason]

Gingerbread only or is froyo up as well?

[Jean-Baptiste Queru]

All the tagged branches mentioned on
http://source.android.com/source/build-numbers.html, plus the
development branches for froyo and gingerbrad, and the AOSP master
itself.

JBQ

[jason]

Cool thank you for the hard work


On Oct 19, 5:51 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> All the tagged branches mentioned onhttp://source.android.com/source/build-numbers.html, plus the

> development branches for froyo and gingerbrad, and the AOSP master
> itself.
>
> JBQ
>

[Ilan Caspi]

Thank you for all the hard work

[Kaspter Ju]

On 10/20/2011 05:51 AM, Jean-Baptiste Queru wrote:
> All the tagged branches mentioned on
> http://source.android.com/source/build-numbers.html, plus the
> development branches for froyo and gingerbrad, and the AOSP master
> itself.
>

Haha..What a wonderfull day today.
thanks for all your hard work.

--
Kaspter Ju

[bluestar8783]

Dear Sir:

 

        I tried to follow above steps to git source code and can't download

 

//-----------------------------------------------------------------------------------------------------------------//

You need to get the latest version of the repo tool:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
You need to initialize a new repository:
repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1
The full instructions are at http://source.android.com/source/downloading.html

//-----------------------------------------------------------------------------------------------------------------//

 

        Two steps:"curl" and "repo init" don't work and halt 

        Do you tell what I miss?

 

        Thank you!

BR,

Alan

2011/10/20 Jean-Baptiste Queru <j...@android.com>

[Jean-Baptiste Queru]

My apologies, we should have mentioned that the instructions in the
original message above assumed that you already have a machine set up
for Android.

The full instructions to start from scratch are here:
http://source.android.com/source/initializing.html

JBQ

[Tero Saarni]

Besides installing gitweb could you also consider maintaining search functionality in some form for the AOSP now that code search site will be closed [1] (which is very unfortunate!)

--

Tero

[1] http://googleblog.blogspot.com/2011/10/fall-sweep.html

[Hannah Fontana]

What about Honeycomb and Ice Cream Sandwich?

[Chislon Chow]

Thanks for putting the code back up. Does someone have a link to a web GUI for viewing the source similar to how kernel.org works using gitweb? 

[CodeMonkey]

repo init -u https://android.googlesource.com/platform/manifest

Get https://android.googlesource.com/tools/repo

fatal: branch 'stable' has not been signed

What am I doing wrong?

[SangHee]

Thank you. 감사합니다.

[bluestar8783]

Dear Sir:

 

        I think my server is ok, because I use this server to download all android

        source code(1.5/1.6/2.3/2.3.4) successfully. So I think the initializing for

        my server is ok.

 

        But in this morning I halt to git source code from new URL

        Below is my message when git repo file

 

root@my_server:~/bin# curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                                  Dload  Upload   Total   Spent    Left  Speed
       0     0    0     0    0     0      0      0       --:--:--  0:00:11 --:--:-- 

        Thank you!

[Nathaniel Husted]

Are the repositories for the goldfish and other kernels also back up
or is it easier to build emulator kernels from the released SDK code?
I was somewhat reliant upon the publicly available directory structure
to download the kernels on android.git.kernel.org and those structures
are no longer available on the new repository (for now). Thanks for
any information.

Cheers,
Nathaniel

On Oct 19, 9:42 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> My apologies, we should have mentioned that the instructions in the
> original message above assumed that you already have a machine set up
> for Android.
>
> The full instructions to start from scratch are here:http://source.android.com/source/initializing.html
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Wed, Oct 19, 2011 at 7:25 PM, bluestar8783 <bluestar8...@gmail.com> wrote:
> > Dear Sir:
>
> >         I tried to follow above steps to git source code and can't download
>
> > //------------------------------------------------------------------------- ----------------------------------------//
> > You need to get the latest version of the repo tool:

> > curlhttps://dl-ssl.google.com/dl/googlesource/git-repo/repo> ~/bin/repo

> > You need to initialize a new repository:
> > repo init -uhttps://android.googlesource.com/platform/manifest-b
> > android-2.3.7_r1
> > The full instructions are at
> >http://source.android.com/source/downloading.html
> > //------------------------------------------------------------------------- ----------------------------------------//
>
> >         Two steps:"curl" and "repo init" don't work and halt
> >         Do you tell what I miss?
>
> >         Thank you!
> > BR,
> > Alan
> > 2011/10/20 Jean-Baptiste Queru <j...@android.com>
>
> >> All the tagged branches mentioned on
> >>http://source.android.com/source/build-numbers.html, plus the
> >> development branches for froyo and gingerbrad, and the AOSP master
> >> itself.
>
> >> JBQ
>

[Jean-Baptiste Queru]

That's odd, I'm not seeing any issue on my side, it's working for me
and none of the dashboards I can think of seem to indicate any issue.

I'm thinking that there might be a firewall in your way.

JBQ

[Jean-Baptiste Queru]

The kernel source trees aren't available at the moment. Getting them
back is definitely on the to-do list.

JBQ

[Jean-Baptiste Queru]

Ice Cream Sandwich was mentioned in the original post on this thread,
and a few more times in the thread. It hasn't shipped yet, so it's not
available in AOSP either. It'll be released in AOSP a little bit after
it gets in the hands of consumers.

Since Ice Cream Sandwich does everything that Honeycomb does (and much
more), there's no plan to release Honeycomb in AOSP.

JBQ

On Wed, Oct 19, 2011 at 11:13 PM, Hannah Fontana
<hannahf...@gmail.com> wrote:
> What about Honeycomb and Ice Cream Sandwich?
>

[Weston Weems]

I tried to take the necessary "search before you ask" precautions
before sending this question in... having a problem building android
source on osx.

I followed initializing repo and preparing system, and likewise just
grabbed latest gb source from newly restored repo. Having a problem
building sdl related functionality (in the make -j4 step)

Install: out/host/darwin-x86/bin/sig-create
Install: out/host/darwin-x86/bin/traceview
host Executable: triangleCM (out/host/darwin-x86/obj/EXECUTABLES/
triangleCM_intermediates/triangleCM)
libpng warning: Ignoring attempt to set cHRM RGB triangle with zero
area
Undefined symbols:
"__dyld_func_lookup", referenced from:
_promoteLocalToGlobal in libSDL.a(SDL_dlcompat.o)
_dlcompat_init_func in libSDL.a(SDL_dlcompat.o)
_dlcompat_init_func in libSDL.a(SDL_dlcompat.o)
_dlcompat_init_func in libSDL.a(SDL_dlcompat.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [out/host/darwin-x86/obj/EXECUTABLES/
triangleCM_intermediates/triangleCM] Error 1
make: *** Waiting for unfinished jobs....
libpng warning: Ignoring attempt to set cHRM RGB triangle with zero
area
wweemss-macbook-pro:WORKING_DIRECTORY wweems$


Is there an obvious cause for this or solution? Played with different
options but seems like consistently breaks here.

Weston

On Oct 19, 7:42 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> My apologies, we should have mentioned that the instructions in the
> original message above assumed that you already have a machine set up
> for Android.
>
> The full instructions to start from scratch are here:http://source.android.com/source/initializing.html
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Wed, Oct 19, 2011 at 7:25 PM, bluestar8783 <bluestar8...@gmail.com> wrote:
> > Dear Sir:
>
> >         I tried to follow above steps to git source code and can't download
>
> > //------------------------------------------------------------------------- ----------------------------------------//
> > You need to get the latest version of the repo tool:

> > curlhttps://dl-ssl.google.com/dl/googlesource/git-repo/repo> ~/bin/repo

> > You need to initialize a new repository:
> > repo init -uhttps://android.googlesource.com/platform/manifest-b
> > android-2.3.7_r1
> > The full instructions are at
> >http://source.android.com/source/downloading.html
> > //------------------------------------------------------------------------- ----------------------------------------//
>
> >         Two steps:"curl" and "repo init" don't work and halt
> >         Do you tell what I miss?
>
> >         Thank you!
> > BR,
> > Alan
> > 2011/10/20 Jean-Baptiste Queru <j...@android.com>
>
> >> All the tagged branches mentioned on
> >>http://source.android.com/source/build-numbers.html, plus the
> >> development branches for froyo and gingerbrad, and the AOSP master
> >> itself.
>
> >> JBQ
>

[Jean-Baptiste Queru]

Most Android platform development is done with XCode 3.x on MacOS
10.6. Newer versions are believed to have incompatibilities with
Android.

JBQ

[Federico Mancini]

Also the kernels source code?

On Oct 19, 11:51 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> All the tagged branches mentioned onhttp://source.android.com/source/build-numbers.html, plus the

> development branches for froyo and gingerbrad, and the AOSP master
> itself.
>
> JBQ
>

[Jean-Baptiste Queru]

No kernels sources at the moment. That's on the list of items to take care of.

JBQ

[Srinidhi K V]

Hi,
What is the path to download kernel/common.git previously
git://android.git.kernel.org/kernel/common.git

Thanks,
Srinidhi KV

[Jean-Baptiste Queru]

The kernels aren't available yet. Once they are, I'll let people know.

JBQ

[Name Less, the Jedi]

2011/10/19 Jean-Baptiste Queru <j...@android.com>

All the tagged branches mentioned on
http://source.android.com/source/build-numbers.html, plus the
development branches for froyo and gingerbrad, and the AOSP master
itself.

First of all great, big, huge thanks for you and all others involved in bringing AOSP online back again.

Is it intentional that repo init ... -b froyo gives exactly the same manifest.xml as repo init ... -b master ?

I'd think that master should be much closer to Gingerbread ;o)
Anyway could you please update build-numbers.html with information how to access dev branch for froyo?

Best regards,

 Robert

--
NameLess, the Jedi           NameLessFroyo
Just a friendly Jedi Knight

[Jean-Baptiste Queru]

Hmmm, that's odd, i'm not seeing any such issue here.

From .repo/manifest, I do get the diff I expect when I run the
following command:

git diff origin/froyo origin/master default.xml

JBQ

[roberj13]

Are all the repositories not online yet. Syncing 2.3.7 gives an error on e2fsprogs and grub that they are not git repositories or don't exist.

[Jean-Baptiste Queru]

Lemme check that.

Is anyone seeing issues?

JBQ

[Jean-Baptiste Queru]

We don't have such a web service at the moment on our servers, it's in
our plans but not the the immediate future. It should be possible to
mirror AOSP and run gitweb on a mirror.

JBQ

On Thu, Oct 20, 2011 at 3:56 AM, Chislon Chow <chi...@gmail.com> wrote:
> Thanks for putting the code back up. Does someone have a link to a web GUI
> for viewing the source similar to how kernel.org works using gitweb?
>

[Jean-Baptiste Queru]

This is the repo launcher (i.e. ~/bin/repo) failing to download the
rest of the repo code (i.e.
https://android.googlesource.com/tools/repo) because it doesn't
recognize it.

You might be using a customized version of the repo launcher that
doesn't recognize the official signature for the repo code... or
something else is wrong.

You should have the following checksum for your repo launcher:

$ sha1sum ~/bin/repo
e1fd3bef059d152edf4d0522590725d317bc637f

If you don't, download the latest version with curl
https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

JBQ

[Jean-Baptiste Queru]

This is odd, I've had no problem downloading 2.3.7 from scratch.

I used:

"repo init -u https://android.googlesource.com/platform/manifest -b
android-2.3.7_r1"

Can you try to repo init a new client and sync just those two projects?
repo sync external/e2fsprogs external/grub

Thanks,
JBQ

[Rodrigo]

I got the following error when running "repo sync":
fatal: '../platform/bionic.git' does not appear to be a git repository

So I had to manually fix the ".repo/manifest.xml" to make it work...
It was:
<remote name="aosp"
fetch=".." />
(don't ask me how it got fetch="..")
Changed it to:
<remote name="aosp"
fetch="https://android.googlesource.com/" />

Working fine now :)

[Jean-Baptiste Queru]

It sounds like you're using an old version of repo that's doesn't
support the features necessary to properly access the new servers.
Please use a new version.

JBQ

[Stephen Smalley]

On Wed, 2011-10-19 at 14:31 -0700, Jean-Baptiste Queru wrote:
> You will not that the manifests now use relative URLs to find the
> projects, so that you can mirror all the projects unmodified
> (including the manifests) and not have to worry about url.insteadOf
> git configs or other such tricks. That should make it much easier for
> anyone to host straight clean mirrors.

Is repo --mirror still the recommended way to mirror all of the
projects? For some reason when I just did that, I ended up with
manifest.git at top-level rather than under platform in the mirror,
which then breaks attempts to repo init/sync from the mirror. Moving it
manually back under platform seems to have "fixed" the problem, but
obviously isn't clean. repo --mirror used to work from the a.g.k.o
site, so I'm not sure why it isn't now.

--
Stephen Smalley
National Security Agency

[Jean-Baptiste Queru]

Hmmm, that's a use case I hadn't tested, and I can imagine how the
support for relative URIs might have broken something here. I'll let
the experts know :)

JBQ