how to use git to checkout Chromium release code?

[Xinwen Xue]

As checked from the following link, checking out Chromium release version code via SVN is Deprecated.

https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#Working_with_release_branches

Checking the chapter "Working with release branches" in above link, it requires SVN account and password to execute the command "git svn fetch svn_$BRANCH".

Could anyone prove a formal way to checkout Chromium Release code via git? 

[Victor Costan]

I documented the process I used to check out and build Chromium here.
As far as I know, the infrastructure hasn't undergone any breaking
changes since then.
http://pwnall.herokuapp.com/blog/2013/10/24/build-your-own-chromium/

The "References" section points out to relevant pages from the project site.

Hope this helps,
Victor

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-dev...@chromium.org.

[Xinwen Xue]

Victor, 

It is a great document from you. 

However, it is a pity I did not find how checkout Release version Chromium code.

[Thiago Farina]

Checkout a release version? What you mean? You can build a release
version of chromium (opposed to the debug build).

If you are using ninja is simple as running the following command line:

ninja -C out/Release chrome

--
Thiago

[Daniel Bratell]

On Tue, 31 Dec 2013 13:21:11 +0100, Thiago Farina <tfa...@chromium.org>
wrote:

I believe the issue is getting the source code that is used in a release,
because that is not trivial.

By using http://omahaproxy.appspot.com/ you can find the svn version
number for a release (for instance 238485 for the current Windows Stable
version) but to get that source out of git you have to try pretty hard. I
managed with the help of an svn account and "git svn" and careful guessing
of branch names. I don't know how to do it without one.

/Daniel

[Ryan Sleevi]

I'm not sure why guessing was needed? Omahaproxy lists the branch name, and http://www.chromium.org/developers/how-tos/get-the-code#Working_with_release_branches has the details on how to check out a release branch.

[Ryan Sleevi]

On Dec 30, 2013 5:30 AM, "Xinwen Xue" <xinwe...@gmail.com> wrote:
>
>
> As checked from the following link, checking out Chromium release version code via SVN is Deprecated.
> https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#Working_with_release_branches
>
> Checking the chapter "Working with release branches" in above link, it requires SVN account and password to execute the command "git svn fetch svn_$BRANCH".
>

Just replace the read/write URL (svn://svn.chromium.org) with the read-only URL (http://src.chromium.org/svn)

> Could anyone prove a formal way to checkout Chromium Release code via git? 
>

[Torne (Richard Coles)]

On 2 January 2014 15:58, Ryan Sleevi <rsl...@chromium.org> wrote:

On Dec 30, 2013 5:30 AM, "Xinwen Xue" <xinwe...@gmail.com> wrote:
>
>
> As checked from the following link, checking out Chromium release version code via SVN is Deprecated.
> https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#Working_with_release_branches
>
> Checking the chapter "Working with release branches" in above link, it requires SVN account and password to execute the command "git svn fetch svn_$BRANCH".
>

Just replace the read/write URL (svn://svn.chromium.org) with the read-only URL (http://src.chromium.org/svn)

This is what you want to do, yes. The easiest way right now to get a release branch is with svn. 

> Could anyone prove a formal way to checkout Chromium Release code via git? 

It's not really possible to check out a specific release with git currently from the open source repos last time I checked, but it's being worked on and will eventually be available. In the meantime, using svn works.

>
> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

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

[Daniel Bratell]

On Thu, 02 Jan 2014 16:53:25 +0100, Ryan Sleevi <rsl...@chromium.org>
wrote:

>
> I'm not sure why guessing was needed? Omahaproxy lists the branch name,
> and
> http://www.chromium.org/>developers/how-tos/get-the-code#Working_with_release_branches
> has the details on how to check out a >release branch.
>

I'm not sure guessing is needed. I just described my workflow.

Say for instance you want to take a look, in git, at version 33.0.1712.2
(just a random release). With "Revision Lookup" at
http://omahaproxy.appspot.com/ you can translate that to svn revision
235732 but from there on I've not found a 100% reliable way to proceed.
Most likely I will find that revision on branch 1712 (because that is how
branches are named) but not always.

So
git svn find-rev r235732 1712
might give me a git hash or it may not.

The branches are listed for current releases but I've not seen any such
listing for historic releases.

/Daniel

[Xinwen Xue]

On Tuesday, December 31, 2013 8:21:11 PM UTC+8, Thiago Farina wrote:

On Tue, Dec 31, 2013 at 7:45 AM, Xinwen Xue <xinwe...@gmail.com> wrote:
> Victor,
> It is a great document from you.
>
> However, it is a pity I did not find how checkout Release version Chromium
> code.
>
Checkout a release version? What you mean? You can build a release
version of chromium (opposed to the debug build).

I mean to checkout release Chromium code for example, 30.114.xx 

[Paweł Hajdan, Jr.]

+Michael - looks like https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#Working_with_release_branches could be updated to include URLs that also work for non-committers.

Could you take a look? The doc says to contact you.

Paweł

[Michael Moss]

We don't currently have git versions of the public release DEPS files (i.e. no .DEPS.git in http://src.chromium.org/svn/releases/). It might be possible to run deps2git.py on the release DEPS, but that probably hasn't been tested at all. We'll be creating release .DEPS.git files automatically at some point, but I don't know when it will be ready.

[Torne (Richard Coles)]

To be honest I think the best advice we could leave up there for now is to use the old purely SVN process to check out a release (by just doing gclient config on the release DEPS) and to not use git at all; this has the advantage of being the same thing that the release builders do, and thus should definitely work without any weird steps :)

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

--
Torne (Richard Coles)
to...@google.com

[Serg Peganov]

I'm having this problem too. So does this mean we need to get commiter access to SVN to be able to get release branch? If so how can we do this? https://chromium-access.appspot.com/request show s me blank page.

[Xinwen Xue]

Hello Michael,

Could you please give a workable guide to get one released Chromium version code in alternative way?

 

Thanks

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

[Serg]

Hello Michael,

Eventually I found a way to get release code. This works only with clear installation of depot_tools on Windows7. 

1. Backup all the chromium sources you have. 

2. Start with clear depot_tools and and new chromium src folder. Install depot_tools as it written here http://www.chromium.org/developers/how-tos/install-depot-tools (Be sure to change PATH environment variable to this new installation of depot_tools)

3. gclient config https://src.chromium.org/chrome/releases/31.0.1650.63  (or whatever release version you want)
4. svn ls https://src.chromium.org/chrome
5. gclient sync

You will get sorces for 31.0.1650.63 release version

Building:
6. cd src
7. set GYP_DEFINES=branding=Chromium buildtype=Official
8. set GYP_GENERATORS=ninja
9. python build\gyp_chromium
10. ninja -C out\Debug chrome.exe

[Carlo Gandolfi]

Il giorno lunedì 6 gennaio 2014 08:07:51 UTC+1, Serg ha scritto:

Hello Michael,

Eventually I found a way to get release code. This works only with clear installation of depot_tools on Windows7. 

1. Backup all the chromium sources you have. 

....

 Sorry Serge but your steps didn't work for me (I'm with OS X 10.9 and Xcode 4). After lot of hours it hung up and then I get this error:

Mac-mini-di-Admin:chromium_31.0.1650.63 admin$ gclient sync

________ running 'svn update /Users/admin/chromium_31.0.1650.63/31.0.1650.63 --non-interactive --accept postpone --ignore-externals' in '/Users/admin/chromium_31.0.1650.63'

At revision 243415.

Syncing projects:  10% ( 9/84) build/third_party/gsutil              

________ running 'svn cleanup /Users/admin/chromium_31.0.1650.63/src' in '/Users/admin/chromium_31.0.1650.63/src'

svn: In directory '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user'

svn: Error processing command 'modify-wcprop' in '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user'

svn: '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user/Safe Browsing Cookies' is not under version control

Not removing troublesome path . automatically.

You can pass --force to enable automatic removal.

Error: Command svn cleanup /Users/admin/chromium_31.0.1650.63/src returned non-zero exit status 1 in /Users/admin/chromium_31.0.1650.63/src

And if I user --force I get:

Mac-mini-di-Admin:chromium_31.0.1650.63 admin$ gclient sync --force

________ running 'svn update /Users/admin/chromium_31.0.1650.63/31.0.1650.63 --non-interactive --force --accept theirs-conflict --ignore-externals' in '/Users/admin/chromium_31.0.1650.63'

At revision 243580.

Syncing projects:   1% ( 1/84) 31.0.1650.63

________ running 'svn update /Users/admin/chromium_31.0.1650.63/commit-queue --revision 224610 --non-interactive --force --accept theirs-conflict --ignore-externals' in '/Users/admin/chromium_31.0.1650.63'

At revision 224610.

.....

svn: In directory '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user'

svn: Error processing command 'modify-wcprop' in '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user'

svn: '/Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user/Safe Browsing Cookies' is not under version control

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src/chrome

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src/chrome/test

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src/chrome/test/data

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics

Removing troublesome path /Users/admin/chromium_31.0.1650.63/src/chrome/test/data/diagnostics/user

Not removing troublesome path chrome/test/data/encoding_tests automatically.

Error: Command svn cleanup /Users/admin/chromium_31.0.1650.63/src returned non-zero exit status 1 in /Users/admin/chromium_31.0.1650.63/src

[Dragomir Goranov]

Hello Michael,

Could you please provide a guide, which non-committers can follow to get one released Chromium version code and compile the project ?

I am especially interested in having a guide which works on Windows and Visual Studio 201x .

I tried all of the following links:

https://github.com/breach/exo_browser/wiki/Building-the-ExoBrowser

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/C7j4XZjD2XA

http://stackoverflow.com/questions/21212869/how-to-update-chromium-source-with-local-changes

I take the following steps:

1. gclient config https://src.chromium.org/chrome/releases/30.0.1599.50/

2. svn ls https://src.chromium.org/chrome

3. gclient sync

4. cd src

5. set GYP_GENERATORS=msvs-ninja,ninja

6. ninja -C out\Debug chrome

Everytime I get this error: 

ninja: fatal: chdir to 'out\Debug' - No such file or directory

ninja: Entering directory `out\Debug'

Please, guys - tell me what the correct way to get and compile version 30.0.1599.50 is ?

[Dirk Pranke]

Try running 'gclient runhooks' in between steps 5 and 6. if you change what the GYP_GENERATORS are set to, you need to re-run GYP, which is one of the things that 'gclient runhooks' does (you can also just run 'python build/gyp_chromium').

I don't remember when we flipped the default generator on windows from visual studio to ninja offhand, but it might've been after the M30 release, in which case you're probably getting (regular, non-ninja) visual studio files generated (like build/all.sln), but not any ninja files.

 

Please, guys - tell me what the correct way to get and compile version 30.0.1599.50 is ?

Apart from what I wrote above, I have no other insight into whether what you're doing will get you that specific version correctly or not (I pretty much never check out and build branches). 

If you're stuck and no one is around to answer your questions, another thing you can always try is to at least ensure that you can check out and build tip-of-tree following the normal chromium instructions. Then, once you're sure you have that working, you can go back and work on getting particular versions checked out.

Hope this helps!

-- Dirk

[Dragomir Goranov]

By following the instructions I am able to check out and build the latest version. But my boss wants me to build a previous release version.

These are the commands that I used:

1. G:\CHROMIUM\src>gclient config https://src.chromium.org/chrome/releases/30.0.1599.50/

2. G:\CHROMIUM\src>svn ls https://src.chromium.org/chrome

3. G:\CHROMIUM\src>set GYP_GENERATORS=msvs-ninja,ninja

4. G:\CHROMIUM\src>gclient sync

This step finished with the following error:

Error: Command svn checkout http://gsutil.googlecode.com/svn/trunk/src@263 G:\CHROMIUM\build\third_party\gsutil --revision 263 --non-interactive --ignore-extern

als returned non-zero exit status 1 in G:\CHROMIUM

5. G:\CHROMIUM\src>cd src

6. G:\CHROMIUM\src>gclient runhooks

This step finished with the following error:

.gclient file in parent directory G:\CHROMIUM might not be the file you want to

use

________ running 'C:\depot_tools\python276_bin\python.exe src/build/download_nac

l_toolchains.py --no-arm-trusted --keep' in 'G:\CHROMIUM'

Can't find 'G:\CHROMIUM\src\native_client\build\download_toolchains.py'

Presumably you are intentionally building without NativeClient.

Skipping NativeClient toolchain download.

________ running 'C:\depot_tools\python276_bin\python.exe src/build/linux/instal

l-arm-sysroot.py --linux-only' in 'G:\CHROMIUM'

________ running 'C:\depot_tools\python276_bin\python.exe src/chrome/installer/l

inux/sysroot_scripts/install-debian.wheezy.sysroot.py --linux-only --arch=amd64'

 in 'G:\CHROMIUM'

________ running 'C:\depot_tools\python276_bin\python.exe src/chrome/installer/l

inux/sysroot_scripts/install-debian.wheezy.sysroot.py --linux-only --arch=i386'

in 'G:\CHROMIUM'

________ running 'C:\depot_tools\python276_bin\python.exe src/tools/clang/script

s/update.py --mac-only' in 'G:\CHROMIUM'

________ running 'C:\depot_tools\python276_bin\python.exe src/build/win/setup_cy

gwin_mount.py --win-only' in 'G:\CHROMIUM'

The system cannot find the path specified.

Error: Command C:\depot_tools\python276_bin\python.exe src/build/win/setup_cygwi

n_mount.py --win-only returned non-zero exit status 1 in G:\CHROMIUM

Thanks once again, I wish you best of luck :)

[Dragomir Goranov]

OK, here is what I did and now I am 1 step closer to building Chromium:

Steps:

1. gclient config https://src.chromium.org/chrome/releases/30.0.1599.101/

2. svn ls https://src.chromium.org/chrome

3. set GYP_GENERATORS=msvs-ninja,ninja

4. fetch chromium --nosvn=True

5. set GYP_GENERATORS=msvs-ninja,ninja

6. gclient runhook

7. ninja -C out\Debug chrome

After compiling for 2 hours I get this error, which I do not know how to solve: 

------------------------------------------------------------------------------------------------------------------------------------------------

[1/20] LINK_EMBED(DLL) chrome_child.dll

FAILED: C:\depot_tools\python276_bin\python.exe gyp-win-tool link-with-manifests

 environment.x86 True chrome_child.dll "C:\depot_tools\python276_bin\python.exe

gyp-win-tool link-wrapper environment.x86 False link.exe /nologo /IMPLIB:chrome_

child.dll.lib /DLL /OUT:chrome_child.dll @chrome_child.dll.rsp" 2 mt.exe rc.exe

"obj\chrome\chrome_child_dll.chrome_child.dll.intermediate.manifest" obj\chrome\

chrome_child_dll.chrome_child.dll.generated.manifest

LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO

Traceback (most recent call last):

  File "gyp-win-tool", line 293, in <module>

    sys.exit(main(sys.argv[1:]))

  File "gyp-win-tool", line 28, in main

    exit_code = executor.Dispatch(args)

  File "gyp-win-tool", line 70, in Dispatch

    return getattr(self, method)(*args[1:])

  File "gyp-win-tool", line 158, in ExecLinkWithManifests

    subprocess.check_call(ldcmd + add_to_ld)

  File "C:\depot_tools\python276_bin\lib\subprocess.py", line 540, in check_call

    raise CalledProcessError(retcode, cmd)

subprocess.CalledProcessError: Command 'C:\depot_tools\python276_bin\python.exe

gyp-win-tool link-wrapper environment.x86 False link.exe /nologo /IMPLIB:chrome_

child.dll.lib /DLL /OUT:chrome_child.dll @chrome_child.dll.rsp chrome_child.dll.

manifest.res' returned non-zero exit status 1210

ninja: build stopped: subcommand failed.

[Greg Thompson]

Try a Release build or try component=shared_library.

[Dragomir Goranov]

I tried component=shared_library and this time the compilation was successful.

But, when I ran the exe it shows : Version 35.0.1871.0 (254738)

:( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( 

[Greg Thompson]

What does src/chrome/VERSION say?

[Dragomir Goranov]

MAJOR=35

MINOR=0

BUILD=1871

PATCH=0

Can you please tell me which of the steps downloads the latest version, instead of version 30.0.1599.101 :

1. gclient config https://src.chromium.org/chrome/releases/30.0.1599.101/

2. svn ls https://src.chromium.org/chrome

3. set GYP_GENERATORS=msvs-ninja,ninja

4. fetch chromium --nosvn=True

5. set GYP_GENERATORS=msvs-ninja,ninja

6. gclient runhook

7. ninja -C out\Debug chrome

[Greg Thompson]

I'd say step 4. I've never tried to do what you're attempting, but my understanding is that fetch will give you trunk rather than a release branch.

[Dragomir Goranov]

OK, so with what command should I replace step 4 ?

[Dragomir Goranov]

Ok, I changed step 4, instead of using "fetch" now I am using "gclient sync":

1. gclient config https://src.chromium.org/chrome/releases/30.0.1599.101/

2. set GYP_GENERATORS=msvs-ninja,ninja

3. svn ls https://src.chromium.org/chrome

4. gclient sync

This step fails with the following error:

Checked out revision 227552.

Error: Command svn checkout http://gsutil.googlecode.com/svn/trunk/src@263 G:\CHROMIUM\build\third_party\gsutil --revision 263 --non-interactive --ignore-externals returned non-zero exit status 1 in G:\CHROMIUM

I am not a committer, is it possible that this error is somehow connected to that?

What is the correct way to checkout and compile an older version of Chromium?

[Paweł Hajdan, Jr.]

As a workaround please try removing any mention of gsutil from the buildspec DEPS file checked out by gclient.

If you're not sure what that means, please post directory names created in the directory you ran "gclient config" in.

Paweł

[Dirk Pranke]

On Tue, Mar 4, 2014 at 5:03 PM, Dragomir Goranov <dragomir...@gmail.com> wrote:

Ok, I changed step 4, instead of using "fetch" now I am using "gclient sync":

1. gclient config https://src.chromium.org/chrome/releases/30.0.1599.101/

2. set GYP_GENERATORS=msvs-ninja,ninja

3. svn ls https://src.chromium.org/chrome

4. gclient sync

This step fails with the following error:

Checked out revision 227552.

Error: Command svn checkout http://gsutil.googlecode.com/svn/trunk/src@263 G:\CHROMIUM\build\third_party\gsutil --revision 263 --non-interactive --ignore-externals returned non-zero exit status 1 in G:\CHROMIUM

I am not a committer, is it possible that this error is somehow connected to that?

What is the correct way to checkout and compile an older version of Chromium?

Okay, you got me interested :). You are basically following the correct steps. I ran them and got the same error. For whatever reason, that particular gclient config appears to reference repos that don't exist (anymore?). 

As Paweł suggests, you can try deleting the the references to gsutil from your build/DEPS file, but you'll probably have to do slightly more invasive surgery to figure out a gclient config that works. Perhaps one of the TPMs or branch managers can speak up as to why this particular DEPS file seems busted, I don't know.

I don't know where you're getting that particular version (30.0.1599.101) from; maybe it was the last release on the M30 branch? At any rate, if you go to omahaproxy.appspot.com, you can do a lookup and see that that should correspond to r227552, so you could try checking out the latest version, and then run 'gclient sync -r src@227552', which should rewind your main repo to that point in time and sync all of the dependencies properly.

Hope that helps,

-- Dirk

[Jason Kersey]

The gsutil repo moved, new DEPS files have a correct location I believe, but old ones remain pointing at the original location. We have thousands of DEPS for old releases, and don't plan to go through and update them when a repo changes.

--

[Ryan Sleevi]

Rather than post-correcting the DEPS, is there a recommended method to support a client-override, and perhaps documenting this if/when we do similar moves?

[Michael Moss]

You should be able to override it with a 'custom_deps' entry in your .gclient file, as described in http://www.chromium.org/developers/how-tos/chromium-modularization#Advanced_Usage. Something like this should work:

    "custom_deps" : {

      "build/third_party/gsutil" : "https://github.com/GoogleCloudPlatform/gsutil.git"

    }

[Ryan Sleevi]

And if you're using SVN? ;)

[Michael Moss]

And to clarify, _we_ didn't move anything, gsutil is a third_party package which moved to github quite a while ago, but apparently only recently disabled their svn repo.

On Tue, Mar 4, 2014 at 8:01 PM, Michael Moss <mm...@chromium.org> wrote:

[porky code]

Check this thread

On Monday, 30 December 2013 15:30:08 UTC+2, Xinwen Xue wrote:

As checked from the following link, checking out Chromium release version code via SVN is Deprecated.

https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#Working_with_release_branches

Checking the chapter "Working with release branches" in above link, it requires SVN account and password to execute the command "git svn fetch svn_$BRANCH".

[Dragomir Goranov]

Thanks, everyone for trying to help me (especially Dirk).

I managed to solve the problem by editing the file \CHROMIUM\.gclient  -->  

"custom_deps": {

"build/third_party/gsutil" : "svn://svn.chromium.org/gsutil/trunk/src@263",

    "src/content/test/data/layout_tests/LayoutTests": None,

    "src/chrome/tools/test/reference_build/chrome_win": None,

    "src/chrome_frame/tools/test/reference_build/chrome_win": None,

    "src/chrome/tools/test/reference_build/chrome_linux": None,

    "src/chrome/tools/test/reference_build/chrome_mac": None,

    "src/third_party/hunspell_dictionaries": None,

  },

This step should be done between steps 3 and 4 and everything will be OK.