need a username&password to access https://chrome-internal.googlesource.com

[Jiazi Yang]

Hi
 when getting intel MRC via command 'emerge-$BOARD chromeos-mrc --getbinpkg', need to enter a username&password , but running successfully a few days ago.
....
>>> Unpacking source...
Cloning into bare repository '/var/cache/chromeos-cache/distfiles/target/egit-src/chromeos/third_party/intel-framework'...
Username for 'https://chrome-internal.googlesource.com':
Password for 'https://chrome-internal.googlesource.com':
fatal: remote error:


Invalid authentication credentials.

Please generate a new identifier:
  https://chrome-internal.googlesource.com/new-password


then I modified the ~/.gitcookies and ~/.netrc according to settings in https://chrome-internal.googlesource.com/new-password, but still failed with same error

Verification:
>>git ls-remote https://chrome-internal.googlesource.com/a/chromeos/manifest-internal.git
>>fatal: remote error: Access denied to xxx_...@asus.com

[Mike Frysinger]

pretty sure the intel-framework repo, by design, is not available to partners (other than Intel of course).  you should be getting a binary package of chromeos-mrc only.  make sure your tree sync is up-to-date and if it's still failing, please file a bug at http://crosbug.com/p/new and provide *full* logs as attachments.  when you hand delete details (like saying "$BOARD" and snipping whole lines of logs) it makes it much harder to understand why it's failing.

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Jiazi Yang]

thanks, it's ok now

[Jiazi Yang]

Shawn, Mike
I was in trouble again.
start a new BOARD 'terra', also failed to get binary mrc file.
branch: firmware-strago-7287.B
board: terra (a new bashwell project)
repo sync to up-to-data
./build_packages --board= terra
emerge-terra chromeos-mrc --getbinpkg

Add terra board in mrc ebuild,
-CROS_WORKON_COMMIT="82926dd24c0adf2250abfc2d20157e02b4174e54"
-CROS_WORKON_TREE="7c0cbe745ba39ea544d53ef3bd351ea728780c2f"
+CROS_WORKON_COMMIT="35547931b02bb346619fc260dae91840878175c3"
+CROS_WORKON_TREE="09de852fa9d2378c923fd38108e466e4378f3ea3"
 inherit cros-constants
 
 CROS_WORKON_PROJECT="chromeos/third_party/intel-framework"
@@ -112,7 +112,7 @@ src_compile_fsp() {
             links=('SkylakeFspPkg SkylakeSiPkg')
             build_script='SkylakeFspPkg/BuildFv.sh'
             ;;
-        (strago|celes|cyan|reks|ultima)
+        (strago|celes|cyan|reks|terra|ultima)
             plat_root='braswell_fsp'
             links=('BraswellFspPkg ChvRefCodePkg')
             build_script='BraswellFspPkg/BuildFv.sh'
@@ -203,6 +203,10 @@ src_install_fsp() {
             build_root=${build_root}'/BSWFSP'
             ins_root=${ins_root}'/google/reks/fsp'
             ;;
+        (terra)
+            build_root=${build_root}'/BSWFSP'
+            ins_root=${ins_root}'/google/terra/fsp'
+            ;;

(cr) (firmware-strago-7287.B/(17d39bd...)) tomato@tomato-X751LN ~/trunk/src/scripts $ emerge-terra chromeos-mrc --getbinpkg

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!

>>> Emerging (1 of 1) sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner for /build/terra/
 * Running stacked hooks for pre_pkg_setup
 *    sysroot_build_bin_dir ...                                                                                                                                                                       [ ok ]
 * Running stacked hooks for pre_src_unpack
 *    python_multilib_setup ...                                                                                                                                                                       [ ok ]

>>> Unpacking source...
Cloning into bare repository '/var/cache/chromeos-cache/distfiles/target/egit-src/chromeos/third_party/intel-framework'...
Username for 'https://chrome-internal.googlesource.com':
Password for 'https://chrome-internal.googlesource.com':
fatal: remote error:


Invalid authentication credentials.

Please generate a new identifier:
  https://chrome-internal.googlesource.com/new-password

 * ERROR: sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner failed (unpack phase):
 *   git-2_initial_clone: can't fetch from https://chrome-internal.googlesource.com/chromeos/third_party/intel-framework.git
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_unpack
 *   environment, line 3438:  Called cros-workon_src_unpack
 *   environment, line  815:  Called git-2_src_unpack
 *   environment, line 2215:  Called git-2_fetch
 *   environment, line 2023:  Called git-2_initial_clone
 *   environment, line 2114:  Called die
 * The specific snippet of code:
 *           die "${FUNCNAME}: can't fetch from ${EGIT_REPO_URI}";
 *
 * If you need support, post the output of `emerge --info '=sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner'`,
 * the complete build log and the output of `emerge -pqv '=sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner'`.
 * The complete build log is located at '/build/terra/tmp/portage/logs/sys-boot:chromeos-mrc-0.0.1-r183:20151104-075922.log'.
 * For convenience, a symlink to the build log is located at '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/temp/build.log'.
 * The ebuild environment file is located at '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/temp/environment'.
 * Working directory: '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/work'
 * S: '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/work/chromeos-mrc-0.0.1'

>>> Failed to emerge sys-boot/chromeos-mrc-0.0.1-r183 for /build/terra/, Log file:

>>>  '/build/terra/tmp/portage/logs/sys-boot:chromeos-mrc-0.0.1-r183:20151104-075922.log'

 * Messages for package sys-boot/chromeos-mrc-0.0.1-r183 merged to /build/terra/:

 * ERROR: sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner failed (unpack phase):
 *   git-2_initial_clone: can't fetch from https://chrome-internal.googlesource.com/chromeos/third_party/intel-framework.git
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_unpack
 *   environment, line 3438:  Called cros-workon_src_unpack
 *   environment, line  815:  Called git-2_src_unpack
 *   environment, line 2215:  Called git-2_fetch
 *   environment, line 2023:  Called git-2_initial_clone
 *   environment, line 2114:  Called die
 * The specific snippet of code:
 *           die "${FUNCNAME}: can't fetch from ${EGIT_REPO_URI}";
 *
 * If you need support, post the output of `emerge --info '=sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner'`,
 * the complete build log and the output of `emerge -pqv '=sys-boot/chromeos-mrc-0.0.1-r183::chromeos-partner'`.
 * The complete build log is located at '/build/terra/tmp/portage/logs/sys-boot:chromeos-mrc-0.0.1-r183:20151104-075922.log'.
 * For convenience, a symlink to the build log is located at '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/temp/build.log'.
 * The ebuild environment file is located at '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/temp/environment'.
 * Working directory: '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/work'
 * S: '/build/terra/tmp/portage/sys-boot/chromeos-mrc-0.0.1-r183/work/chromeos-mrc-0.0.1'
(cr) (firmware-strago-7287.B/(17d39bd...)) tomato@tomato-X751LN ~/trunk/src/scripts $

[Mike Frysinger]

you probably need to post the cl to the branch and let the firmware bots produce binaries. otherwise, please talk to the partner eng team directly.
-mike