--
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
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.
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
JBQ
Haha..What a wonderfull day today.
thanks for all your hard work.
--
Kaspter Ju
The full instructions to start from scratch are here:
http://source.android.com/source/initializing.html
JBQ
I'm thinking that there might be a firewall in your way.
JBQ
JBQ
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?
>
JBQ
JBQ
Thanks,
Srinidhi KV
JBQ
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.
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
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.
Is anyone seeing issues?
JBQ
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?
>
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
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
JBQ
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
JBQ
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
These are the commits that I have in the manifest project:
$ git rev-parse origin/froyo origin/master
71480329b4ff4ee7f07d756d139425676b09b7c9
1e41b439288f9814810f2008739a28203d0b4d7c
Can you try a plain git clone of the manifest project, and let me know
if you're still getting the wrong froyo manifest?
git clone https://android.googlesource.com/platform/manifest
Also, do you have the manifest for android-2.2.2_r1?
$ git rev-parse origin/android-2.2.2_r1
320229cd98b6f101488b9f20872db99f135da901
JBQ
Weird, yes that works to just sync those by themselves. I'll will try a full sync again. Thanks
rm -rf external/e2fsprogs/ external/grub/
.repo/projects/external/e2fsprogs.git/
.repo/projects/external/grub.git/
JBQ
Any instructions how to mirror AOSP?
From what I understand, the --mirror flag in repo init doesn't actually mirror all of AOSP.
Thank you.
JBQ
Indeed, --mirror only mirrors the projects mentioned in a manifest.
Right now there's no easy way to get the list of all projects.
However, with a bit of creativity, it's possible to get a list of all
projects in all platform manifests, which could be a starting point:
(beware, ugly hack non-portable script hack ahead)
git branch -a |
grep remotes/origin |
while read B
do
git checkout -q $B
ls -1 |
xargs grep \<project |
tr \ \\n |
grep ^name=\" |
cut -d \" -f 2
done |
sort -u
git checkout -q default
I'm thinking that I should be able to create a manifest that contains
all known projects (not just platform, really everything). Running
repo init --mirror on that should do the trick. Would that help?
JBQ
No kernels sources at the moment. That's on the list of items to take care of.
Lemme try to create a manifest.
JBQ
You should be able to test it by either initializing a new mirror, or
running "repo selfupdate" on an existing mirror to make it immediately
pick up the new repo code (the default selfupdate interval is 24
hours).
JBQ
We've pushed a fix for the issue with repo init --mirror and the
manifest projects.
You should be able to test it by either initializing a new mirror, or
running "repo selfupdate" on an existing mirror to make it immediately
pick up the new repo code (the default selfupdate interval is 24
hours).
JBQ
> On quick question:
> To let clients of my mirror checkout a branch different from master,
> do I need anything specific on the mirror itself?
No. A mirror is a mirror.
--
Magnus B�ck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
> On Thursday, October 20, 2011 at 20:58 CEST,
> Carlos Silva <r3...@r3pek.org> wrote:
>
> > On quick question:
> > To let clients of my mirror checkout a branch different from master,
> > do I need anything specific on the mirror itself?
>
> No. A mirror is a mirror.
...that said, a mirror based on a single manifest branch might not get
you all gits that you need for mirroring other manifest branches. For
example, platform/packages/apps/AlarmClock disappeared between Froyo
and Gingerbread.
Make sure u have a lot of bandwidth for the server to use or ur mirror will timeout or have other issues if more than a couple downloads at a time which would be slow in a low vandwidth enviornment
On Thursday, October 20, 2011 at 20:58 CEST,
Carlos Silva <r3...@r3pek.org> wrote:
> On quick question:
> To let clients of my mirror checkout a branch different from master,
> do I need anything specific on the mirror itself?
No. A mirror is a mirror.
--
Magnus Bäck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
Hmmm, that's odd, even with that version of repo (which isn't the one
that we typically use for AOSP but should also have all the necessary
features), I still don't have any issues with froyo.
These are the commits that I have in the manifest project:
$ git rev-parse origin/froyo origin/master
71480329b4ff4ee7f07d756d139425676b09b7c9
1e41b439288f9814810f2008739a28203d0b4d7c
--
It already has one :)
~cco3
>
>> - Dan
>
> --
> Andrea
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
>
--
JBQ
JBQ
JBQ
The Google infrastructure is actually more complex than that. It's
possible however that you're ultimately a different server than I am.
JBQ
Same "not been signed" error here, same up to date repo. Anyone find a solution?