Chromium Code Reviews
|
|
Chromium Code Reviews
Issue
6279010:
kernel: remove chromeos-base/kernel (Closed)
|
Created:
9 years, 11 months ago by Mandeep Singh Baines Modified:
9 years, 7 months ago CC:
chromium-os-reviews_chromium.org, msb+crosoverlay_chromium.org, adlr+crosoverlay_chromium.org Visibility:
Public. |
Descriptionkernel: remove chromeos-base/kernel
Take two. Fixed issues which cause earlier build break.
Also, re-synced sys-kernel/chromeos-kernel with chromeos-base/kernel. This
fixes strangeness that can occur at build_image time. See the bug for
details.
BUG=11124
TEST=Reran build_packages and build_image
Change-Id: I27a2340038ac9d7520fa06918e6a18c51902993f
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=a82f476
Patch Set 1 #Patch Set 2 : Forget build_packages #Patch Set 3 : profile #
Messages
Total messages: 11 (0 generated)
LGTM On 2011/01/21 22:25:55, Mandeep Singh Baines wrote:
Hi, This breaks the build for me. I just cloned a repo _from scratch_ (repo init + repo sync) and did exactly this: ./make_chroot --replace ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ ./setup_board --board=x86-generic --default ./set_shared_user_password.sh ./build_packages --board=x86-generic and after a while, I get: === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for /build/x86-generic/ chromeos-kernel-0.0.1-r131: !!! Manifest file not found: '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' chromeos-kernel-0.0.1-r131: * CPV: sys-kernel/chromeos-kernel-0.0.1-r131 chromeos-kernel-0.0.1-r131: * REPO: chromiumos chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc kernel_linux userland_GNU x86 chromeos-kernel-0.0.1-r131: * GIT NEW clone --> chromeos-kernel-0.0.1-r131: * repository: http://git.chromium.org/git/chromeos-kernel chromeos-kernel-0.0.1-r131: Cloning into bare repository /var/lib/portage/distfiles-target/git-src/chromeos-kernel... chromeos-kernel-0.0.1-r131: fatal: http://git.chromium.org/git/chromeos-kernel/info/refs not found: did you run git update-server-info on the server? chromeos-kernel-0.0.1-r131: * ERROR: sys-kernel/chromeos-kernel-0.0.1-r131 failed: chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from http://git.chromium.org/git/chromeos-kernel. chromeos-kernel-0.0.1-r131: * chromeos-kernel-0.0.1-r131: * Call stack: chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called src_unpack chromeos-kernel-0.0.1-r131: * environment, line 3068: Called cros-workon_src_unpack chromeos-kernel-0.0.1-r131: * environment, line 763: Called git_src_unpack chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die chromeos-kernel-0.0.1-r131: * The specific snippet of code: chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; chromeos-kernel-0.0.1-r131: * chromeos-kernel-0.0.1-r131: * If you need support, post the output of 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', chromeos-kernel-0.0.1-r131: * the complete build log and the output of 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses from overlays: chromeos-kernel-0.0.1-r131: * /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass chromeos-kernel-0.0.1-r131: * /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' chromeos-kernel-0.0.1-r131: * The complete build log is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. chromeos-kernel-0.0.1-r131: * S: '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' chromeos-kernel-0.0.1-r131: >>> Failed to emerge sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log file: chromeos-kernel-0.0.1-r131: >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' chromeos-kernel-0.0.1-r131: chromeos-kernel-0.0.1-r131: * Messages for package sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: chromeos-kernel-0.0.1-r131: chromeos-kernel-0.0.1-r131: * GIT NEW clone --> chromeos-kernel-0.0.1-r131: * repository: http://git.chromium.org/git/chromeos-kernel chromeos-kernel-0.0.1-r131: * ERROR: sys-kernel/chromeos-kernel-0.0.1-r131 failed: chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from http://git.chromium.org/git/chromeos-kernel. chromeos-kernel-0.0.1-r131: * chromeos-kernel-0.0.1-r131: * Call stack: chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called src_unpack chromeos-kernel-0.0.1-r131: * environment, line 3068: Called cros-workon_src_unpack chromeos-kernel-0.0.1-r131: * environment, line 763: Called git_src_unpack chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die chromeos-kernel-0.0.1-r131: * The specific snippet of code: chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; chromeos-kernel-0.0.1-r131: * chromeos-kernel-0.0.1-r131: * If you need support, post the output of 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', chromeos-kernel-0.0.1-r131: * the complete build log and the output of 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses from overlays: chromeos-kernel-0.0.1-r131: * /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass chromeos-kernel-0.0.1-r131: * /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' chromeos-kernel-0.0.1-r131: * The complete build log is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. chromeos-kernel-0.0.1-r131: * S: '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build has failed. chromeos-base/chromeos-0.0.1-r97: (merge) needs sys-kernel/chromeos-kernel-0.0.1-r131 sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs no dependencies Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 Stéphane
Thanks for tracking the issue. I pushed up http://codereview.chromium.org/6255012 and this should work now. On Fri, Jan 21, 2011 at 7:15 PM, Stéphane Marchesin <marcheu@google.com>wrote: > Hi, > > This breaks the build for me. I just cloned a repo _from scratch_ (repo > init + repo sync) and did exactly this: > > ./make_chroot --replace > ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ > ./setup_board --board=x86-generic --default > ./set_shared_user_password.sh > ./build_packages --board=x86-generic > > and after a while, I get: > > === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === > chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) > sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for > /build/x86-generic/ > chromeos-kernel-0.0.1-r131: !!! Manifest file not found: > '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' > chromeos-kernel-0.0.1-r131: * CPV: sys-kernel/chromeos-kernel-0.0.1-r131 > chromeos-kernel-0.0.1-r131: * REPO: chromiumos > chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc > kernel_linux userland_GNU x86 > chromeos-kernel-0.0.1-r131: * GIT NEW clone --> > chromeos-kernel-0.0.1-r131: * repository: > http://git.chromium.org/git/chromeos-kernel > chromeos-kernel-0.0.1-r131: Cloning into bare repository > /var/lib/portage/distfiles-target/git-src/chromeos-kernel... > chromeos-kernel-0.0.1-r131: fatal: > http://git.chromium.org/git/chromeos-kernel/info/refs not found: did you > run git update-server-info on the server? > chromeos-kernel-0.0.1-r131: * ERROR: sys-kernel/chromeos-kernel-0.0.1-r131 > failed: > chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from > http://git.chromium.org/git/chromeos-kernel. > chromeos-kernel-0.0.1-r131: * > chromeos-kernel-0.0.1-r131: * Call stack: > chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 3068: Called > cros-workon_src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 763: Called > git_src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch > chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die > chromeos-kernel-0.0.1-r131: * The specific snippet of code: > chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} > ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die > "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; > chromeos-kernel-0.0.1-r131: * > chromeos-kernel-0.0.1-r131: * If you need support, post the output of > 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', > chromeos-kernel-0.0.1-r131: * the complete build log and the output of > 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. > chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses from > overlays: > chromeos-kernel-0.0.1-r131: * > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > chromeos-kernel-0.0.1-r131: * > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named > 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' > chromeos-kernel-0.0.1-r131: * The complete build log is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. > chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. > chromeos-kernel-0.0.1-r131: * S: > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' > chromeos-kernel-0.0.1-r131: >>> Failed to emerge > sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log file: > chromeos-kernel-0.0.1-r131: >>> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' > chromeos-kernel-0.0.1-r131: > chromeos-kernel-0.0.1-r131: * Messages for package > sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: > chromeos-kernel-0.0.1-r131: > chromeos-kernel-0.0.1-r131: * GIT NEW clone --> > chromeos-kernel-0.0.1-r131: * repository: > http://git.chromium.org/git/chromeos-kernel > chromeos-kernel-0.0.1-r131: * ERROR: sys-kernel/chromeos-kernel-0.0.1-r131 > failed: > chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from > http://git.chromium.org/git/chromeos-kernel. > chromeos-kernel-0.0.1-r131: * > chromeos-kernel-0.0.1-r131: * Call stack: > chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 3068: Called > cros-workon_src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 763: Called > git_src_unpack > chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch > chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die > chromeos-kernel-0.0.1-r131: * The specific snippet of code: > chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} > ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die > "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; > chromeos-kernel-0.0.1-r131: * > chromeos-kernel-0.0.1-r131: * If you need support, post the output of > 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', > chromeos-kernel-0.0.1-r131: * the complete build log and the output of > 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. > chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses from > overlays: > chromeos-kernel-0.0.1-r131: * > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > chromeos-kernel-0.0.1-r131: * > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named > 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' > chromeos-kernel-0.0.1-r131: * The complete build log is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. > chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. > chromeos-kernel-0.0.1-r131: * S: > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' > === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === > Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build has > failed. > chromeos-base/chromeos-0.0.1-r97: (merge) needs > sys-kernel/chromeos-kernel-0.0.1-r131 > sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs > no dependencies > Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 > > Stéphane > >
Hi Anush, I still have the same problem (with -r132.) I ran repo sync && ./make_chroot --replace a few hours ago, but they didn't work. For me, 'cros_workon start chromeos-kernel-next' was necessary to fix the problem. outside$ ./cros_workon start sys-kernel/chromeos-kernel-next chroot$ emerge-x86-generic -a chromeos-kernel-next Could you let me know if there's a better way to fix the problem? Thanks, Yusuke ----------------------------- (cros-chroot) yusukes@harapeko ~/trunk/src/scripts $ emerge-x86-generic -a chromeos-kernel These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] sys-kernel/chromeos-kernel-0.0.1-r132 to /build/x86-generic/ USE="compat_wireless -initramfs" Would you like to merge these packages? [Yes/No] >>> Emerging (1 of 1) sys-kernel/chromeos-kernel-0.0.1-r132 from chromiumos for /build/x86-generic/ !!! Manifest file not found: '/home/yusukes/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' * CPV: sys-kernel/chromeos-kernel-0.0.1-r132 * REPO: chromiumos * USE: compat_wireless elibc_glibc kernel_linux userland_GNU x86 >>> Unpacking source... * GIT NEW clone --> * repository: http://git.chromium.org/git/chromeos-kernel Cloning into bare repository /var/lib/portage/distfiles-target/git-src/chromeos-kernel... fatal: http://git.chromium.org/git/chromeos-kernel/info/refs not found: did you run git update-server-info on the server? * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: * git.eclass: can't fetch from http://git.chromium.org/git/chromeos-kernel . * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 3051: Called cros-workon_src_unpack * environment, line 746: Called git_src_unpack * environment, line 2158: Called git_fetch * environment, line 2076: Called die * The specific snippet of code: * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; * * If you need support, post the output of 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r132', * the complete build log and the output of 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r132'. * This ebuild used the following eclasses from overlays: * /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass * /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass * This ebuild is from an overlay named 'chromiumos': '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' * The complete build log is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. * The ebuild environment file is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. * S: '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' >>> Failed to emerge sys-kernel/chromeos-kernel-0.0.1-r132 for /build/x86-generic/, Log file: >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log' * Messages for package sys-kernel/chromeos-kernel-0.0.1-r132 merged to /build/x86-generic/: * GIT NEW clone --> * repository: http://git.chromium.org/git/chromeos-kernel * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: * git.eclass: can't fetch from http://git.chromium.org/git/chromeos-kernel . * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 3051: Called cros-workon_src_unpack * environment, line 746: Called git_src_unpack * environment, line 2158: Called git_fetch * environment, line 2076: Called die * The specific snippet of code: * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; * * If you need support, post the output of 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r132', * the complete build log and the output of 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r132'. * This ebuild used the following eclasses from overlays: * /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass * /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass * This ebuild is from an overlay named 'chromiumos': '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' * The complete build log is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. * The ebuild environment file is located at '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. * S: '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' On Sun, Jan 23, 2011 at 4:57 AM, Anush Elangovan(அனுஷ்) <anush@chromium.org> wrote: > Thanks for tracking the issue. I pushed > up http://codereview.chromium.org/6255012 and this should work now. > > On Fri, Jan 21, 2011 at 7:15 PM, Stéphane Marchesin <marcheu@google.com> > wrote: >> >> Hi, >> This breaks the build for me. I just cloned a repo _from scratch_ (repo >> init + repo sync) and did exactly this: >> ./make_chroot --replace >> ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ >> ./setup_board --board=x86-generic --default >> ./set_shared_user_password.sh >> ./build_packages --board=x86-generic >> and after a while, I get: >> === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === >> chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) >> sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for >> /build/x86-generic/ >> chromeos-kernel-0.0.1-r131: !!! Manifest file not found: >> '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' >> chromeos-kernel-0.0.1-r131: * CPV: sys-kernel/chromeos-kernel-0.0.1-r131 >> chromeos-kernel-0.0.1-r131: * REPO: chromiumos >> chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc >> kernel_linux userland_GNU x86 >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >> chromeos-kernel-0.0.1-r131: * repository: >> http://git.chromium.org/git/chromeos-kernel >> chromeos-kernel-0.0.1-r131: Cloning into bare repository >> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... >> chromeos-kernel-0.0.1-r131: fatal: >> http://git.chromium.org/git/chromeos-kernel/info/refs not found: did you run >> git update-server-info on the server? >> chromeos-kernel-0.0.1-r131: * ERROR: >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >> http://git.chromium.org/git/chromeos-kernel. >> chromeos-kernel-0.0.1-r131: * >> chromeos-kernel-0.0.1-r131: * Call stack: >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >> src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >> cros-workon_src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >> git_src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >> chromeos-kernel-0.0.1-r131: * >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >> from overlays: >> chromeos-kernel-0.0.1-r131: * >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> chromeos-kernel-0.0.1-r131: * >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >> chromeos-kernel-0.0.1-r131: * S: >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >> chromeos-kernel-0.0.1-r131: >>> Failed to emerge >> sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log file: >> chromeos-kernel-0.0.1-r131: >>> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' >> chromeos-kernel-0.0.1-r131: >> chromeos-kernel-0.0.1-r131: * Messages for package >> sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: >> chromeos-kernel-0.0.1-r131: >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >> chromeos-kernel-0.0.1-r131: * repository: >> http://git.chromium.org/git/chromeos-kernel >> chromeos-kernel-0.0.1-r131: * ERROR: >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >> http://git.chromium.org/git/chromeos-kernel. >> chromeos-kernel-0.0.1-r131: * >> chromeos-kernel-0.0.1-r131: * Call stack: >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >> src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >> cros-workon_src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >> git_src_unpack >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called git_fetch >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >> chromeos-kernel-0.0.1-r131: * >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >> from overlays: >> chromeos-kernel-0.0.1-r131: * >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> chromeos-kernel-0.0.1-r131: * >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >> chromeos-kernel-0.0.1-r131: * S: >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >> === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === >> Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build has >> failed. >> chromeos-base/chromeos-0.0.1-r97: (merge) needs >> sys-kernel/chromeos-kernel-0.0.1-r131 >> sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs >> no dependencies >> Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 >> Stéphane > >
On Sun, Jan 23, 2011 at 10:17 PM, Yusuke Sato <yusukes@chromium.org> wrote: > Hi Anush, > I still have the same problem (with -r132.) I ran repo sync && > ./make_chroot --replace a few hours ago, but they didn't work. For me, > 'cros_workon start chromeos-kernel-next' was necessary to fix the problem. > > outside$ ./cros_workon start sys-kernel/chromeos-kernel-next > chroot$ emerge-x86-generic -a chromeos-kernel-next > chromeos-kernel-next shouldn't have any changes w.r.t chromeos-kernel. However when I made the change to chromeos-kernel I hadn't bumped the ebuild so you will need a repo sync (which you indicated you had done). Can you confirm my change exists in your chromeos-kernel ebuild? Thanks Anush > > Could you let me know if there's a better way to fix the problem? > > Thanks, > Yusuke > > ----------------------------- > (cros-chroot) yusukes@harapeko ~/trunk/src/scripts $ emerge-x86-generic -a > chromeos-kernel > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] sys-kernel/chromeos-kernel-0.0.1-r132 to > /build/x86-generic/ USE="compat_wireless -initramfs" > > Would you like to merge these packages? [Yes/No] > > >>> Emerging (1 of 1) sys-kernel/chromeos-kernel-0.0.1-r132 from chromiumos > for /build/x86-generic/ > !!! Manifest file not found: > '/home/yusukes/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' > * CPV: sys-kernel/chromeos-kernel-0.0.1-r132 > * REPO: chromiumos > > * USE: compat_wireless elibc_glibc kernel_linux userland_GNU x86 > >>> Unpacking source... > * GIT NEW clone --> > > * repository: http://git.chromium.org/git/chromeos-kernel > Cloning into bare repository > /var/lib/portage/distfiles-target/git-src/chromeos-kernel... > fatal: http://git.chromium.org/git/chromeos-kernel/info/refs not found: > did you run git update-server-info on the server? > * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: > > * git.eclass: can't fetch from > http://git.chromium.org/git/chromeos-kernel. > * > * Call stack: > > * ebuild.sh, line 54: Called src_unpack > * environment, line 3051: Called cros-workon_src_unpack > * environment, line 746: Called git_src_unpack > * environment, line 2158: Called git_fetch > * environment, line 2076: Called die > > * The specific snippet of code: > * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} > "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from > ${EGIT_REPO_URI}."; > * > * If you need support, post the output of 'emerge --info > =sys-kernel/chromeos-kernel-0.0.1-r132', > * the complete build log and the output of 'emerge -pqv > =sys-kernel/chromeos-kernel-0.0.1-r132'. > > * This ebuild used the following eclasses from overlays: > * > /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > * > /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > * This ebuild is from an overlay named 'chromiumos': > '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' > * The complete build log is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. > * The ebuild environment file is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. > * S: > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' > > >>> Failed to emerge sys-kernel/chromeos-kernel-0.0.1-r132 for > /build/x86-generic/, Log file: > > >>> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log' > > * Messages for package sys-kernel/chromeos-kernel-0.0.1-r132 merged to > /build/x86-generic/: > > * GIT NEW clone --> > > * repository: http://git.chromium.org/git/chromeos-kernel > * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: > > * git.eclass: can't fetch from > http://git.chromium.org/git/chromeos-kernel. > * > * Call stack: > > * ebuild.sh, line 54: Called src_unpack > * environment, line 3051: Called cros-workon_src_unpack > * environment, line 746: Called git_src_unpack > * environment, line 2158: Called git_fetch > * environment, line 2076: Called die > > * The specific snippet of code: > * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} > "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from > ${EGIT_REPO_URI}."; > * > * If you need support, post the output of 'emerge --info > =sys-kernel/chromeos-kernel-0.0.1-r132', > * the complete build log and the output of 'emerge -pqv > =sys-kernel/chromeos-kernel-0.0.1-r132'. > > * This ebuild used the following eclasses from overlays: > * > /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > * > /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > * This ebuild is from an overlay named 'chromiumos': > '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' > * The complete build log is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. > * The ebuild environment file is located at > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. > * S: > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' > > > > > > > > > > On Sun, Jan 23, 2011 at 4:57 AM, Anush Elangovan(அனுஷ்) < > anush@chromium.org> wrote: > > Thanks for tracking the issue. I pushed > > up http://codereview.chromium.org/6255012 and this should work now. > > > > On Fri, Jan 21, 2011 at 7:15 PM, Stéphane Marchesin <marcheu@google.com> > > wrote: > >> > >> Hi, > >> This breaks the build for me. I just cloned a repo _from scratch_ (repo > >> init + repo sync) and did exactly this: > >> ./make_chroot --replace > >> ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ > >> ./setup_board --board=x86-generic --default > >> ./set_shared_user_password.sh > >> ./build_packages --board=x86-generic > >> and after a while, I get: > >> === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === > >> chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) > >> sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for > >> /build/x86-generic/ > >> chromeos-kernel-0.0.1-r131: !!! Manifest file not found: > >> > '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' > >> chromeos-kernel-0.0.1-r131: * CPV: > sys-kernel/chromeos-kernel-0.0.1-r131 > >> chromeos-kernel-0.0.1-r131: * REPO: chromiumos > >> chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc > >> kernel_linux userland_GNU x86 > >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> > >> chromeos-kernel-0.0.1-r131: * repository: > >> http://git.chromium.org/git/chromeos-kernel > >> chromeos-kernel-0.0.1-r131: Cloning into bare repository > >> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... > >> chromeos-kernel-0.0.1-r131: fatal: > >> http://git.chromium.org/git/chromeos-kernel/info/refs not found: did > you run > >> git update-server-info on the server? > >> chromeos-kernel-0.0.1-r131: * ERROR: > >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: > >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from > >> http://git.chromium.org/git/chromeos-kernel. > >> chromeos-kernel-0.0.1-r131: * > >> chromeos-kernel-0.0.1-r131: * Call stack: > >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called > >> src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called > >> cros-workon_src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called > >> git_src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called > git_fetch > >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die > >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: > >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} > >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die > >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; > >> chromeos-kernel-0.0.1-r131: * > >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of > >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', > >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of > >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. > >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses > >> from overlays: > >> chromeos-kernel-0.0.1-r131: * > >> > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > >> chromeos-kernel-0.0.1-r131: * > >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named > >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' > >> chromeos-kernel-0.0.1-r131: * The complete build log is located at > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. > >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. > >> chromeos-kernel-0.0.1-r131: * S: > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' > >> chromeos-kernel-0.0.1-r131: >>> Failed to emerge > >> sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log file: > >> chromeos-kernel-0.0.1-r131: >>> > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' > >> chromeos-kernel-0.0.1-r131: > >> chromeos-kernel-0.0.1-r131: * Messages for package > >> sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: > >> chromeos-kernel-0.0.1-r131: > >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> > >> chromeos-kernel-0.0.1-r131: * repository: > >> http://git.chromium.org/git/chromeos-kernel > >> chromeos-kernel-0.0.1-r131: * ERROR: > >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: > >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from > >> http://git.chromium.org/git/chromeos-kernel. > >> chromeos-kernel-0.0.1-r131: * > >> chromeos-kernel-0.0.1-r131: * Call stack: > >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called > >> src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called > >> cros-workon_src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called > >> git_src_unpack > >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called > git_fetch > >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die > >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: > >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} > >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || die > >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; > >> chromeos-kernel-0.0.1-r131: * > >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of > >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', > >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of > >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. > >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses > >> from overlays: > >> chromeos-kernel-0.0.1-r131: * > >> > /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass > >> chromeos-kernel-0.0.1-r131: * > >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass > >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named > >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' > >> chromeos-kernel-0.0.1-r131: * The complete build log is located at > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. > >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located at > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. > >> chromeos-kernel-0.0.1-r131: * S: > >> > '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' > >> === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === > >> Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build has > >> failed. > >> chromeos-base/chromeos-0.0.1-r97: (merge) needs > >> sys-kernel/chromeos-kernel-0.0.1-r131 > >> sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs > >> no dependencies > >> Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 > >> Stéphane > > > > > >
My chromiumos-overlay repo seems to be up-to-date, but the ebuild file does not contain the CROS_WORKON_PROJECT="kernel" line. hmm... probably your -r131 change is automatically overwritten by the -9999 file? Thanks, Yusuke yusukes@harapeko:~/mychromiumos/src/third_party/chromiumos-overlay$ grep CROS_WORKON_PROJECT sys-kernel/chromeos-kernel/chromeos-kernel-0.0.1-r132.ebuild yusukes@harapeko:~/mychromiumos/src/third_party/chromiumos-overlay$ git log 4e1b9e31f1555696a1f99be0c4c9a6ffa5f7d676 commit 4e1b9e31f1555696a1f99be0c4c9a6ffa5f7d676 Author: Anush Elangovan <anush@chromium.org> Date: Sat Jan 22 11:55:11 2011 -0800 Fix minilayout to work with new kernel ebuild Change-Id: I15f74b3dfca463b14cde75599293106c9d11815b BUG=n0ne TEST=emerge-board chromeos-kernel Review URL: http://codereview.chromium.org/6255012 On Mon, Jan 24, 2011 at 3:25 PM, Anush Elangovan(அனுஷ்) <anush@google.com>wrote: > > > On Sun, Jan 23, 2011 at 10:17 PM, Yusuke Sato <yusukes@chromium.org>wrote: > >> Hi Anush, >> I still have the same problem (with -r132.) I ran repo sync && >> ./make_chroot --replace a few hours ago, but they didn't work. For me, >> 'cros_workon start chromeos-kernel-next' was necessary to fix the problem. >> >> outside$ ./cros_workon start sys-kernel/chromeos-kernel-next >> chroot$ emerge-x86-generic -a chromeos-kernel-next >> > > chromeos-kernel-next shouldn't have any changes w.r.t chromeos-kernel. > However when I made the change to chromeos-kernel I hadn't bumped the > ebuild so you will need a repo sync (which you indicated you had done). Can > you confirm my change exists in your chromeos-kernel ebuild? > > Thanks > Anush > > >> >> Could you let me know if there's a better way to fix the problem? >> >> Thanks, >> Yusuke >> >> ----------------------------- >> (cros-chroot) yusukes@harapeko ~/trunk/src/scripts $ emerge-x86-generic >> -a chromeos-kernel >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> [ebuild N ] sys-kernel/chromeos-kernel-0.0.1-r132 to >> /build/x86-generic/ USE="compat_wireless -initramfs" >> >> Would you like to merge these packages? [Yes/No] >> >> >>> Emerging (1 of 1) sys-kernel/chromeos-kernel-0.0.1-r132 from >> chromiumos for /build/x86-generic/ >> !!! Manifest file not found: >> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' >> * CPV: sys-kernel/chromeos-kernel-0.0.1-r132 >> * REPO: chromiumos >> >> * USE: compat_wireless elibc_glibc kernel_linux userland_GNU x86 >> >>> Unpacking source... >> * GIT NEW clone --> >> >> * repository: http://git.chromium.org/git/chromeos-kernel >> Cloning into bare repository >> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... >> fatal: http://git.chromium.org/git/chromeos-kernel/info/refs not found: >> did you run git update-server-info on the server? >> * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: >> >> * git.eclass: can't fetch from >> http://git.chromium.org/git/chromeos-kernel. >> * >> * Call stack: >> >> * ebuild.sh, line 54: Called src_unpack >> * environment, line 3051: Called cros-workon_src_unpack >> * environment, line 746: Called git_src_unpack >> * environment, line 2158: Called git_fetch >> * environment, line 2076: Called die >> >> * The specific snippet of code: >> * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} >> "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from >> ${EGIT_REPO_URI}."; >> * >> * If you need support, post the output of 'emerge --info >> =sys-kernel/chromeos-kernel-0.0.1-r132', >> * the complete build log and the output of 'emerge -pqv >> =sys-kernel/chromeos-kernel-0.0.1-r132'. >> >> * This ebuild used the following eclasses from overlays: >> * >> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> * >> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> * This ebuild is from an overlay named 'chromiumos': >> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' >> * The complete build log is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. >> * The ebuild environment file is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. >> * S: >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' >> >> >>> Failed to emerge sys-kernel/chromeos-kernel-0.0.1-r132 for >> /build/x86-generic/, Log file: >> >> >>> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log' >> >> * Messages for package sys-kernel/chromeos-kernel-0.0.1-r132 merged to >> /build/x86-generic/: >> >> * GIT NEW clone --> >> >> * repository: http://git.chromium.org/git/chromeos-kernel >> * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: >> >> * git.eclass: can't fetch from >> http://git.chromium.org/git/chromeos-kernel. >> * >> * Call stack: >> >> * ebuild.sh, line 54: Called src_unpack >> * environment, line 3051: Called cros-workon_src_unpack >> * environment, line 746: Called git_src_unpack >> * environment, line 2158: Called git_fetch >> * environment, line 2076: Called die >> >> * The specific snippet of code: >> * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} >> "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from >> ${EGIT_REPO_URI}."; >> * >> * If you need support, post the output of 'emerge --info >> =sys-kernel/chromeos-kernel-0.0.1-r132', >> * the complete build log and the output of 'emerge -pqv >> =sys-kernel/chromeos-kernel-0.0.1-r132'. >> >> * This ebuild used the following eclasses from overlays: >> * >> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> * >> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> * This ebuild is from an overlay named 'chromiumos': >> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' >> * The complete build log is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. >> * The ebuild environment file is located at >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. >> * S: >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' >> >> >> >> >> >> >> >> >> >> On Sun, Jan 23, 2011 at 4:57 AM, Anush Elangovan(அனுஷ்) < >> anush@chromium.org> wrote: >> > Thanks for tracking the issue. I pushed >> > up http://codereview.chromium.org/6255012 and this should work now. >> > >> > On Fri, Jan 21, 2011 at 7:15 PM, Stéphane Marchesin <marcheu@google.com >> > >> > wrote: >> >> >> >> Hi, >> >> This breaks the build for me. I just cloned a repo _from scratch_ (repo >> >> init + repo sync) and did exactly this: >> >> ./make_chroot --replace >> >> ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ >> >> ./setup_board --board=x86-generic --default >> >> ./set_shared_user_password.sh >> >> ./build_packages --board=x86-generic >> >> and after a while, I get: >> >> === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === >> >> chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) >> >> sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for >> >> /build/x86-generic/ >> >> chromeos-kernel-0.0.1-r131: !!! Manifest file not found: >> >> >> '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' >> >> chromeos-kernel-0.0.1-r131: * CPV: >> sys-kernel/chromeos-kernel-0.0.1-r131 >> >> chromeos-kernel-0.0.1-r131: * REPO: chromiumos >> >> chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc >> >> kernel_linux userland_GNU x86 >> >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >> >> chromeos-kernel-0.0.1-r131: * repository: >> >> http://git.chromium.org/git/chromeos-kernel >> >> chromeos-kernel-0.0.1-r131: Cloning into bare repository >> >> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... >> >> chromeos-kernel-0.0.1-r131: fatal: >> >> http://git.chromium.org/git/chromeos-kernel/info/refs not found: did >> you run >> >> git update-server-info on the server? >> >> chromeos-kernel-0.0.1-r131: * ERROR: >> >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >> >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >> >> http://git.chromium.org/git/chromeos-kernel. >> >> chromeos-kernel-0.0.1-r131: * >> >> chromeos-kernel-0.0.1-r131: * Call stack: >> >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >> >> src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >> >> cros-workon_src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >> >> git_src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called >> git_fetch >> >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >> >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >> >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >> >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || >> die >> >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >> >> chromeos-kernel-0.0.1-r131: * >> >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >> >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >> >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of >> >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >> >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >> >> from overlays: >> >> chromeos-kernel-0.0.1-r131: * >> >> >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> >> chromeos-kernel-0.0.1-r131: * >> >> >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >> >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >> >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >> >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located >> at >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >> >> chromeos-kernel-0.0.1-r131: * S: >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >> >> chromeos-kernel-0.0.1-r131: >>> Failed to emerge >> >> sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log >> file: >> >> chromeos-kernel-0.0.1-r131: >>> >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' >> >> chromeos-kernel-0.0.1-r131: >> >> chromeos-kernel-0.0.1-r131: * Messages for package >> >> sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: >> >> chromeos-kernel-0.0.1-r131: >> >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >> >> chromeos-kernel-0.0.1-r131: * repository: >> >> http://git.chromium.org/git/chromeos-kernel >> >> chromeos-kernel-0.0.1-r131: * ERROR: >> >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >> >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >> >> http://git.chromium.org/git/chromeos-kernel. >> >> chromeos-kernel-0.0.1-r131: * >> >> chromeos-kernel-0.0.1-r131: * Call stack: >> >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >> >> src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >> >> cros-workon_src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >> >> git_src_unpack >> >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called >> git_fetch >> >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >> >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >> >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >> >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || >> die >> >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >> >> chromeos-kernel-0.0.1-r131: * >> >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >> >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >> >> chromeos-kernel-0.0.1-r131: * the complete build log and the output of >> >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >> >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >> >> from overlays: >> >> chromeos-kernel-0.0.1-r131: * >> >> >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >> >> chromeos-kernel-0.0.1-r131: * >> >> >> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >> >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >> >> 'chromiumos': '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >> >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >> >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located >> at >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >> >> chromeos-kernel-0.0.1-r131: * S: >> >> >> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >> >> === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === >> >> Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build >> has >> >> failed. >> >> chromeos-base/chromeos-0.0.1-r97: (merge) needs >> >> sys-kernel/chromeos-kernel-0.0.1-r131 >> >> sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs >> >> no dependencies >> >> Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 >> >> Stéphane >> > >> > >> >> >
On Sun, Jan 23, 2011 at 10:39 PM, Yusuke Sato <yusukes@chromium.org> wrote: > My chromiumos-overlay repo seems to be up-to-date, but the ebuild file does > not contain the CROS_WORKON_PROJECT="kernel" line. > hmm... probably your -r131 change is automatically overwritten by the -9999 > file? > > That is true. http://codereview.chromium.org/6296021 should fix the 9999 ebuild. Thanks > Thanks, > Yusuke > > yusukes@harapeko:~/mychromiumos/src/third_party/chromiumos-overlay$ grep > CROS_WORKON_PROJECT > sys-kernel/chromeos-kernel/chromeos-kernel-0.0.1-r132.ebuild > yusukes@harapeko:~/mychromiumos/src/third_party/chromiumos-overlay$ git > log 4e1b9e31f1555696a1f99be0c4c9a6ffa5f7d676 > > commit 4e1b9e31f1555696a1f99be0c4c9a6ffa5f7d676 > Author: Anush Elangovan <anush@chromium.org> > Date: Sat Jan 22 11:55:11 2011 -0800 > > Fix minilayout to work with new kernel ebuild > > Change-Id: I15f74b3dfca463b14cde75599293106c9d11815b > > BUG=n0ne > TEST=emerge-board chromeos-kernel > > Review URL: http://codereview.chromium.org/6255012 > > > > > On Mon, Jan 24, 2011 at 3:25 PM, Anush Elangovan(அனுஷ்) <anush@google.com>wrote: > >> >> >> On Sun, Jan 23, 2011 at 10:17 PM, Yusuke Sato <yusukes@chromium.org>wrote: >> >>> Hi Anush, >>> I still have the same problem (with -r132.) I ran repo sync && >>> ./make_chroot --replace a few hours ago, but they didn't work. For me, >>> 'cros_workon start chromeos-kernel-next' was necessary to fix the problem. >>> >>> outside$ ./cros_workon start sys-kernel/chromeos-kernel-next >>> chroot$ emerge-x86-generic -a chromeos-kernel-next >>> >> >> chromeos-kernel-next shouldn't have any changes w.r.t chromeos-kernel. >> However when I made the change to chromeos-kernel I hadn't bumped the >> ebuild so you will need a repo sync (which you indicated you had done). Can >> you confirm my change exists in your chromeos-kernel ebuild? >> >> Thanks >> Anush >> >> >>> >>> Could you let me know if there's a better way to fix the problem? >>> >>> Thanks, >>> Yusuke >>> >>> ----------------------------- >>> (cros-chroot) yusukes@harapeko ~/trunk/src/scripts $ emerge-x86-generic >>> -a chromeos-kernel >>> >>> These are the packages that would be merged, in order: >>> >>> Calculating dependencies... done! >>> [ebuild N ] sys-kernel/chromeos-kernel-0.0.1-r132 to >>> /build/x86-generic/ USE="compat_wireless -initramfs" >>> >>> Would you like to merge these packages? [Yes/No] >>> >>> >>> Emerging (1 of 1) sys-kernel/chromeos-kernel-0.0.1-r132 from >>> chromiumos for /build/x86-generic/ >>> !!! Manifest file not found: >>> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' >>> * CPV: sys-kernel/chromeos-kernel-0.0.1-r132 >>> * REPO: chromiumos >>> >>> * USE: compat_wireless elibc_glibc kernel_linux userland_GNU x86 >>> >>> Unpacking source... >>> * GIT NEW clone --> >>> >>> * repository: http://git.chromium.org/git/chromeos-kernel >>> Cloning into bare repository >>> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... >>> fatal: http://git.chromium.org/git/chromeos-kernel/info/refs not found: >>> did you run git update-server-info on the server? >>> * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: >>> >>> * git.eclass: can't fetch from >>> http://git.chromium.org/git/chromeos-kernel. >>> * >>> * Call stack: >>> >>> * ebuild.sh, line 54: Called src_unpack >>> * environment, line 3051: Called cros-workon_src_unpack >>> * environment, line 746: Called git_src_unpack >>> * environment, line 2158: Called git_fetch >>> * environment, line 2076: Called die >>> >>> * The specific snippet of code: >>> * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} >>> "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from >>> ${EGIT_REPO_URI}."; >>> * >>> * If you need support, post the output of 'emerge --info >>> =sys-kernel/chromeos-kernel-0.0.1-r132', >>> * the complete build log and the output of 'emerge -pqv >>> =sys-kernel/chromeos-kernel-0.0.1-r132'. >>> >>> * This ebuild used the following eclasses from overlays: >>> * >>> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >>> * >>> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >>> * This ebuild is from an overlay named 'chromiumos': >>> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' >>> * The complete build log is located at >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. >>> * The ebuild environment file is located at >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. >>> * S: >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' >>> >>> >>> Failed to emerge sys-kernel/chromeos-kernel-0.0.1-r132 for >>> /build/x86-generic/, Log file: >>> >>> >>> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log' >>> >>> * Messages for package sys-kernel/chromeos-kernel-0.0.1-r132 merged to >>> /build/x86-generic/: >>> >>> * GIT NEW clone --> >>> >>> * repository: http://git.chromium.org/git/chromeos-kernel >>> * ERROR: sys-kernel/chromeos-kernel-0.0.1-r132 failed: >>> >>> * git.eclass: can't fetch from >>> http://git.chromium.org/git/chromeos-kernel. >>> * >>> * Call stack: >>> >>> * ebuild.sh, line 54: Called src_unpack >>> * environment, line 3051: Called cros-workon_src_unpack >>> * environment, line 746: Called git_src_unpack >>> * environment, line 2158: Called git_fetch >>> * environment, line 2076: Called die >>> >>> * The specific snippet of code: >>> * ${EGIT_FETCH_CMD} ${extra_clone_opts} ${EGIT_OPTIONS} >>> "${EGIT_REPO_URI}" ${GIT_DIR} || die "${EGIT}: can't fetch from >>> ${EGIT_REPO_URI}."; >>> * >>> * If you need support, post the output of 'emerge --info >>> =sys-kernel/chromeos-kernel-0.0.1-r132', >>> * the complete build log and the output of 'emerge -pqv >>> =sys-kernel/chromeos-kernel-0.0.1-r132'. >>> >>> * This ebuild used the following eclasses from overlays: >>> * >>> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >>> * >>> /home/yusukes/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >>> * This ebuild is from an overlay named 'chromiumos': >>> '/home/yusukes/trunk/src/third_party/chromiumos-overlay/' >>> * The complete build log is located at >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/build.log'. >>> * The ebuild environment file is located at >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/temp/environment'. >>> * S: >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r132/work/chromeos-kernel-0.0.1' >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On Sun, Jan 23, 2011 at 4:57 AM, Anush Elangovan(அனுஷ்) < >>> anush@chromium.org> wrote: >>> > Thanks for tracking the issue. I pushed >>> > up http://codereview.chromium.org/6255012 and this should work now. >>> > >>> > On Fri, Jan 21, 2011 at 7:15 PM, Stéphane Marchesin < >>> marcheu@google.com> >>> > wrote: >>> >> >>> >> Hi, >>> >> This breaks the build for me. I just cloned a repo _from scratch_ >>> (repo >>> >> init + repo sync) and did exactly this: >>> >> ./make_chroot --replace >>> >> ./enter_chroot.sh --chrome_root=/home/marcheu/chromium/ >>> >> ./setup_board --board=x86-generic --default >>> >> ./set_shared_user_password.sh >>> >> ./build_packages --board=x86-generic >>> >> and after a while, I get: >>> >> === Start output for job chromeos-kernel-0.0.1-r131 (0m2.2s) === >>> >> chromeos-kernel-0.0.1-r131: >>> Emerging (1 of 1) >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 from chromiumos for >>> >> /build/x86-generic/ >>> >> chromeos-kernel-0.0.1-r131: !!! Manifest file not found: >>> >> >>> '/home/marcheu/trunk/src/third_party/chromiumos-overlay/sys-kernel/chromeos-kernel/Manifest' >>> >> chromeos-kernel-0.0.1-r131: * CPV: >>> sys-kernel/chromeos-kernel-0.0.1-r131 >>> >> chromeos-kernel-0.0.1-r131: * REPO: chromiumos >>> >> chromeos-kernel-0.0.1-r131: * USE: compat_wireless elibc_glibc >>> >> kernel_linux userland_GNU x86 >>> >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >>> >> chromeos-kernel-0.0.1-r131: * repository: >>> >> http://git.chromium.org/git/chromeos-kernel >>> >> chromeos-kernel-0.0.1-r131: Cloning into bare repository >>> >> /var/lib/portage/distfiles-target/git-src/chromeos-kernel... >>> >> chromeos-kernel-0.0.1-r131: fatal: >>> >> http://git.chromium.org/git/chromeos-kernel/info/refs not found: did >>> you run >>> >> git update-server-info on the server? >>> >> chromeos-kernel-0.0.1-r131: * ERROR: >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >>> >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >>> >> http://git.chromium.org/git/chromeos-kernel. >>> >> chromeos-kernel-0.0.1-r131: * >>> >> chromeos-kernel-0.0.1-r131: * Call stack: >>> >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >>> >> src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >>> >> cros-workon_src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >>> >> git_src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called >>> git_fetch >>> >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >>> >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >>> >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >>> >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || >>> die >>> >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >>> >> chromeos-kernel-0.0.1-r131: * >>> >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >>> >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >>> >> chromeos-kernel-0.0.1-r131: * the complete build log and the output >>> of >>> >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >>> >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >>> >> from overlays: >>> >> chromeos-kernel-0.0.1-r131: * >>> >> >>> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >>> >> chromeos-kernel-0.0.1-r131: * >>> >> >>> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >>> >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >>> >> 'chromiumos': >>> '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >>> >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >>> >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located >>> at >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >>> >> chromeos-kernel-0.0.1-r131: * S: >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >>> >> chromeos-kernel-0.0.1-r131: >>> Failed to emerge >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 for /build/x86-generic/, Log >>> file: >>> >> chromeos-kernel-0.0.1-r131: >>> >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log' >>> >> chromeos-kernel-0.0.1-r131: >>> >> chromeos-kernel-0.0.1-r131: * Messages for package >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 merged to /build/x86-generic/: >>> >> chromeos-kernel-0.0.1-r131: >>> >> chromeos-kernel-0.0.1-r131: * GIT NEW clone --> >>> >> chromeos-kernel-0.0.1-r131: * repository: >>> >> http://git.chromium.org/git/chromeos-kernel >>> >> chromeos-kernel-0.0.1-r131: * ERROR: >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 failed: >>> >> chromeos-kernel-0.0.1-r131: * git.eclass: can't fetch from >>> >> http://git.chromium.org/git/chromeos-kernel. >>> >> chromeos-kernel-0.0.1-r131: * >>> >> chromeos-kernel-0.0.1-r131: * Call stack: >>> >> chromeos-kernel-0.0.1-r131: * ebuild.sh, line 54: Called >>> >> src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 3068: Called >>> >> cros-workon_src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 763: Called >>> >> git_src_unpack >>> >> chromeos-kernel-0.0.1-r131: * environment, line 2175: Called >>> git_fetch >>> >> chromeos-kernel-0.0.1-r131: * environment, line 2093: Called die >>> >> chromeos-kernel-0.0.1-r131: * The specific snippet of code: >>> >> chromeos-kernel-0.0.1-r131: * ${EGIT_FETCH_CMD} >>> >> ${extra_clone_opts} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${GIT_DIR} || >>> die >>> >> "${EGIT}: can't fetch from ${EGIT_REPO_URI}."; >>> >> chromeos-kernel-0.0.1-r131: * >>> >> chromeos-kernel-0.0.1-r131: * If you need support, post the output of >>> >> 'emerge --info =sys-kernel/chromeos-kernel-0.0.1-r131', >>> >> chromeos-kernel-0.0.1-r131: * the complete build log and the output >>> of >>> >> 'emerge -pqv =sys-kernel/chromeos-kernel-0.0.1-r131'. >>> >> chromeos-kernel-0.0.1-r131: * This ebuild used the following eclasses >>> >> from overlays: >>> >> chromeos-kernel-0.0.1-r131: * >>> >> >>> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/cros-workon.eclass >>> >> chromeos-kernel-0.0.1-r131: * >>> >> >>> /home/marcheu/trunk/src/third_party/chromiumos-overlay/eclass/git.eclass >>> >> chromeos-kernel-0.0.1-r131: * This ebuild is from an overlay named >>> >> 'chromiumos': >>> '/home/marcheu/trunk/src/third_party/chromiumos-overlay/' >>> >> chromeos-kernel-0.0.1-r131: * The complete build log is located at >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/build.log'. >>> >> chromeos-kernel-0.0.1-r131: * The ebuild environment file is located >>> at >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/temp/environment'. >>> >> chromeos-kernel-0.0.1-r131: * S: >>> >> >>> '/build/x86-generic/tmp/portage/sys-kernel/chromeos-kernel-0.0.1-r131/work/chromeos-kernel-0.0.1' >>> >> === Complete: job chromeos-kernel-0.0.1-r131 (0m2.2s) === >>> >> Failed sys-kernel/chromeos-kernel-0.0.1-r131 (in 0m2.2s). Your build >>> has >>> >> failed. >>> >> chromeos-base/chromeos-0.0.1-r97: (merge) needs >>> >> sys-kernel/chromeos-kernel-0.0.1-r131 >>> >> sys-kernel/chromeos-kernel-0.0.1-r131: (merge) needs >>> >> no dependencies >>> >> Packages failed: sys-kernel/chromeos-kernel-0.0.1-r131 >>> >> Stéphane >>> > >>> > >>> >>> >> >
So now it breaks in the build_image step: emerge: there are no ebuilds to satisfy "virtual/kernel". (dependency required by "chromeos-base/chromeos-0.0.1-r98" [binary]) (dependency required by "chromeos" [argument]) Stéphane
2011/1/24 Stéphane Marchesin <marcheu@google.com> > So now it breaks in the build_image step: > > emerge: there are no ebuilds to satisfy "virtual/kernel". > (dependency required by "chromeos-base/chromeos-0.0.1-r98" [binary]) > (dependency required by "chromeos" [argument]) > > > Oh of course this is when I cros_workon start chromeos-kernel-next Stéphane
Stéphane Marchesin (marcheu@google.com) wrote: > 2011/1/24 Stéphane Marchesin <marcheu@google.com> > > > So now it breaks in the build_image step: > > > > emerge: there are no ebuilds to satisfy "virtual/kernel". > > (dependency required by "chromeos-base/chromeos-0.0.1-r98" [binary]) > > (dependency required by "chromeos" [argument]) > > > > > > > Oh of course this is when I cros_workon start chromeos-kernel-next > So this issue is resolved? If you want to work on kernel-next, you need to: setup_board --profile=kernel-next --board=<some board> > Stéphane |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
