BUG=chromium-os:16364
TEST=Ran with symlinked directories
Change-Id: I374eced27f1b0b3147b9632d5f9dd2637b0d7d28
Reviewed-on: http://gerrit.chromium.org/gerrit/2390
Reviewed-by: Daniel Erat <derat@chromium.org>
Tested-by: David James <davidjames@chromium.org>
chrontel.conf has changed, adjust this patch to match.
BUG=chromium-os:16079
TEST=none
Change-Id: I50709efe1d37084be5d974ba5a6353e6039d65f1
Reviewed-on: http://gerrit.chromium.org/gerrit/2394
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
mod_for_factory patches boot-complete since it disables the ui job,
meaning that login-prompt-visible will never happen. The correct
place to move "boot-complete" to is "started boot-services" - this
means all boot services are done.
system-services depends on boot-complete, so this means that without
ui, system-services will be run on started boot-services which is
what we want.
BUG=chromium-os:16079
TEST=none
Change-Id: I93b86eefe8df9da2e9fbff75aa1e9b80a1f9ad1b
Reviewed-on: http://gerrit.chromium.org/gerrit/2323
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
BUG=none
TEST=none
Change-Id: Iaed383363c0eb73a1e378cd99e39403d9296b4bf
Reviewed-on: http://gerrit.chromium.org/gerrit/2369
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
This script also helps out with chromeos-u-boot-next -> chromeos-u-boot
migration.
BUG=chromium-os:16310
TEST=Run the script and verify right packages are uninstalled.
Change-Id: I4ebaa0a0b3e1eea32005b4d2a47f4581e44d825c
Reviewed-on: http://gerrit.chromium.org/gerrit/2309
Tested-by: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Also adding various dependent packages.
BUG=chromium-os:15600
TEST=Make sure upower can be emerged
Signed-off-by: Simon Que <sque@chromium.org>
Change-Id: Id92d10b8cc2b1e2b84fc5cd965992cc4f8ed4f67
Reviewed-on: http://gerrit.chromium.org/gerrit/1849
Reviewed-by: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
BUG=none
TEST=Write an image to an SD card
Change-Id: I79f2ab4a30c424ab2fbeee8f2636a4900338bcd8
Reviewed-on: http://gerrit.chromium.org/gerrit/1440
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mario Limonciello <mario_limonciello@dell.com>
TEST=Test incremental build_packages after libtool upgrade,
verify all packages still work.
BUG=chromium-os:15595
Change-Id: I7cf130a4b537eb0b02f52681801346c62fc9fd69
Reviewed-on: http://gerrit.chromium.org/gerrit/2161
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
cros_make_image_bootable is called up to 4 times in a typical workflow. The fsck
check can take up to a minute or more because it first copies 2G of the image to
run the fsck on. It adds several minutes to the build.
The check itself is just a sanity check that shouldn't trigger in normal builds.
BUG=none
TEST=build_image
Change-Id: I86512f7efc67027fe687f0c0ad8f6df32579dbe2
Reviewed-on: http://gerrit.chromium.org/gerrit/2250
Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
These hacks are all at least three months old, and our official policy is to
remove hacks after two weeks. For future hacks, the plan is to use the chroot
upgrader script so that old chroots can be supported indefinitely.
Thanks to the Gerrit transition, there are probably few old chroots around
anyway that aren't going to be recreated anyway.
BUG=chromium-os:16151
TEST=Verify enter_chroot.sh still works.
Change-Id: Ie0c777aabbd70d2a0c88b59ddd71e9b67965ca94
Reviewed-on: http://gerrit.chromium.org/gerrit/2158
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Add script that adds depot_tools and chromite/bin to the PATH globally using /etc/env.d
BUG=16093
TEST=Ran make_chroot and run_chroot_version_hooks
Change-Id: I6011d7436f18ce46dfe215f01068e862d2567273
Reviewed-on: http://gerrit.chromium.org/gerrit/2022
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Ryan Cui <rcui@chromium.org>
Default netroot factory install kernel mounts rootfs in ram. The
USE flag "blkdevram" was implemented in
http://gerrit.chromium.org/gerrit/#change,1802
BUG=None
TEST=Build factory install kernel and rootfs uimg. Kernel should
be able to mount the in-ram initrd downloaded from tftp.
Change-Id: Idb83375e0587432c5dec87357a8aa8e229f40af2
Reviewed-on: http://gerrit.chromium.org/gerrit/1803
Reviewed-by: Rong Chang <rongchang@chromium.org>
Tested-by: Rong Chang <rongchang@chromium.org>
This 'update_kernel.sh' script gratuitiously broke on ARM targets
because the bootloader file has been changed to 'bootloader.bin' from
its previous name.
TEST=Used the script with a small kernel change to my Arthur board.
BUG=none
Change-Id: I146f08256543ffe2c4c52995625b26a1b3f28318
Reviewed-on: http://gerrit.chromium.org/gerrit/1989
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Taylor Hutt <thutt@chromium.org>
Tested-by: Taylor Hutt <thutt@chromium.org>
A new parameter --hwid_updater is added to support updating
HWID component list by mini-omaha server.
BUG=chrome-os-partner:4276
TEST=./make_factory_package --release RELEASE --factory FACTORY \
--firmware FIRMWARE --hwid hwid_updater.sh # success
Change-Id: I5889bf63545f0ed118320b60963e22ebc00c76f7
Reviewed-on: http://gerrit.chromium.org/gerrit/1826
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
The script used to assume that you were running it from src/scripts.
That assumption has now been removed.
BUG=none
TEST=After this change I can run update_kernel.sh from anywhere.
Change-Id: I2676e1c16f5682d06be48e99c915660e4cb35be8
Reviewed-on: http://gerrit.chromium.org/gerrit/1933
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Mandeep Singh Baines <msb@chromium.org>
This solves this issue where if we don't upload to gsutil and instead
just archive locally we still have the test tarball.
BUG=chromium-os:16014
TEST=Ran with no gsutil option set and a tarball file.
Change-Id: I5e14801f7b0a58f589a400278274fb566e580bea
Reviewed-on: http://gerrit.chromium.org/gerrit/1921
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Update sed cmd to reflect multi-profile changes.
BUG=chromium-os:12948
TEST=run mod_image_for_test; boot and verify flimflam.conf is properly edited
Change-Id: I9f58aabc4c302b1e24737b0fcb15fc2719d120d6
Reviewed-on: http://gerrit.chromium.org/gerrit/1198
Tested-by: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Copied linux-headers-2.6.30-r1.ebuild to portage-stable overlay, so
that we upgrade to the new linux-headers without crossdev complaining.
Also added linux-headers-2.6.38.ebuild from upstream portage.
BUG=chromium-os:15872
TEST=Ran setup_board --nousepkg and checked that crossdev correctly
still uses the 2.6.30-r1 ebuild.
Change-Id: I7904c7db2b7d220f155d236a64fb0da4812bf3dc
Reviewed-on: http://gerrit.chromium.org/gerrit/1850
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Raymes Khoury <raymes@chromium.org>
Changes from 1.0.6 -> 1.0.7:
* cleanup of documentation and buildsystem
BUG=none
TEST=Rebuild setxkbmap (with new libxkbfile)
setxkbmap fr
Enable French "azerty" keyboard
setkbxmap -layout us -variant dvorak
Enables US Dvorak keyboard layout
Change-Id: I7672e961a7aa989cb919351b5b268c3f8091a5f1
Reviewed-on: http://gerrit.chromium.org/gerrit/1785
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
Changes from 1.1.0 -> 1.2.0:
* Change default XKB rules file from "xorg" to "base"
* Much cleanup of documentation and buildsystem
BUG=none
TEST=setxkbmap fr
Enable French "azerty" keyboard
setkbxmap -layout us -variant dvorak
Enables US Dvorak keyboard layout
Change-Id: Iff768876fec80d869e95ed18c10f177cde129390
Reviewed-on: http://gerrit.chromium.org/gerrit/1753
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Satoru Takabayashi <satorux@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Various members of /dev are used (such as /dev/random) in this script,
and <() style redirection is used which requires a mounted /proc in the
image.
So bind-mount /dev and /proc while running so they work.
BUG=chromiumos:15951
TEST=examined output before/after
Change-Id: I3e8f0edef0da7e63b2af6736e8becfa1cd6d723d
Reviewed-on: http://gerrit.chromium.org/gerrit/1846
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
learn_arch is only called by update_kernel.sh. Until recently, we
were only using learn_arch to detect whether the device is arm or not.
However, with a recent change, update_kernel.sh is now passing the
arch flag to vbutil_kernel which only knows about x86 and not i686.
BUG=chromium-os:15932
TEST=Before change update_kernel.sh fails on x86 and now it works.
Change-Id: Idafc71c017c8ed0595fd0260fce63f327ff021bd
Reviewed-on: http://gerrit.chromium.org/gerrit/1831
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Tested-by: Mandeep Singh Baines <msb@chromium.org>
This reverts commit 09c6565f638848d291f9a4903282ffc7c5db0674.
BUG=chromium-os:15872
TBR=build breaker
TEST=confirmed emerge shows available with ACCEPT_KEYWORDS
Change-Id: I6bded3ce3e5f57a2c7a8874faa51786fa8ff6d89
Reviewed-on: http://gerrit.chromium.org/gerrit/1721
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/1777
Tested-by: David James <davidjames@chromium.org>
BUG=chromiumos:15872
TEST=confirmed emerge shows available with ACCEPT_KEYWORDS
Change-Id: I1e2460fec27299a738cb0c62f50ca5deb9edb025
Reviewed-on: http://gerrit.chromium.org/gerrit/1721
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
This avoid skipping the dependencies of bsdiff, bspatch and cgpt.
BUG=chromium-os:15766
TEST=ran generate_au_zip, ensured bsdiff dependencies are included in the .zip
Change-Id: I7dfe5d1a3197df0f6036e33a20989813a22b16cc
Reviewed-on: http://gerrit.chromium.org/gerrit/1564
Tested-by: Darin Petkov <petkov@chromium.org>
Reviewed-by: David McMahon <djmm@google.com>
Tested-by: David McMahon <djmm@google.com>
Tested-by: David McMahon <djmm@chromium.org>
Reviewed-by: David McMahon <djmm@chromium.org>
This commit is a part of transition to enable ARM kernel signing. It is
at first an option that is enabled manually, and then (in this commit)
enabled by default. After more tests, the scripts that generate unsigned
ARM kernel partition will probably be removed.
BUG=chromium-os:12352
TEST=./build_image && load_kernel_test -b 2 /path/to/chromiumos_image.bin /usr/share/vboot/devkeys/recovery_key.vbpubk
Change-Id: I7d4ecc566f9c5cc0106a7af59255fc63fdfe017a
Tested-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Rong Chang <rongchang@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/1319
Tested-by: Nick Sanders <nsanders@chromium.org>
This CL is separated from http://gerrit.chromium.org/gerrit/#change,1104 which
is depends on the UUID replacement. In order to make update_kernel not break on
officail ChromeOS firmware, this CL just signs the kernel and use the original
cmdline approach, i.e. /dev/${devname}${rootpart}.
TEST=./update_kernel --remote IP
BUG=none
Change-Id: I6a194da0ebb0b3f5a442b62ffb76186909eb4321
Reviewed-on: http://gerrit.chromium.org/gerrit/1538
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
BUG=chromium-os:10048
TEST=Enter chroot with http_proxy set and check export.
Change-Id: I590bd38d22ca1be8164d2a2b408230163d9e5777
Reviewed-on: http://gerrit.chromium.org/gerrit/344
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Tested-by: Doug Anderson <dianders@chromium.org>
BUG=chromium-os:13977
TEST=Build an image with new compiler, boot image and verify new ldd is used.
Build image with old compiler and verify old ldd is used.
Change-Id: I8cbc5b87342245106f0a8fd0fa80ae42329eff60
Reviewed-on: http://gerrit.chromium.org/gerrit/1367
Tested-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
As reported in Bug 15561, build_image sometimes reports incorrect blacklist
packages if it reports an error about a package that is not actually installed.
For example, if you install =dev-libs/glib-2.28.6, and then replace it with
=dev-libs/glib-2.26.1-r1, build_image will report a blacklist failure because
glib depends on Python. But that's wrong -- it's looking at the wrong package.
BUG=chromium-os:15561
TEST=Test that build_image does not report an error when the package it's
complaining about is not installed anymore.
Change-Id: I86b25684d0e211fd144231c7a34276ecf5607ad7
Reviewed-on: http://gerrit.chromium.org/gerrit/1227
Reviewed-by: Darin Petkov <petkov@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
The messages printed out by the code that checks if chromium's libcros and the system's libcros are
in sync were kind of confusing and not quite accurate. The system library implements a range of API
versions, and it is chromium that requires a particular version of the API. The messages now clearly
reflect this.
BUG=None
TEST=manual
Change-Id: I7308d7eb724edfb7fa11edbe0fbec86ee12c5afe
Reviewed-on: http://gerrit.chromium.org/gerrit/1136
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
The "merge_shim_image" does not work for recovery shims; and that makes the name
confusing.
This CL changed its name to a more slef-documenting one,
"make_universal_factory_shim.sh". Also updated the comments in script file to
describe its real behavior.
BUG=chrome-os-partner:2888
TEST=none # no change in code except more comments
Change-Id: I965c93b39021935c12e21e14b63ba04fce2f43e6
Reviewed-on: http://gerrit.chromium.org/gerrit/1035
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
I missed two library dependancies for pushimage when I moved it from
crostools to src/script. Moving them now.
BUG=chromiumos:14372
TEST=None
Change-Id: I47fffa3c09d8eb0d119b9c8732fcf4e1ce149189
Reviewed-on: http://gerrit.chromium.org/gerrit/1120
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
The design of Chromium OS disk image allows trying to boot with multiple
partitions. This script can merge images with different kernels (even signed
with different keys) into one single image.
Useful for factory process which usually needs to deal with DEV/PVT/MP signed
shims.
BUG=chrome-os-partner:2888
TEST=./merge_shim_image.sh mp.bin pvt.bin # output image works for both PVT/MP devices
Change-Id: I21d267bc74fab2d581ccbd0818160407aff35467
Reviewed-on: http://gerrit.chromium.org/gerrit/847
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
The name chroot_upgrade is rather confusing since we already have
"chroot_update" and those two scripts will be chained. It was the
original name before update_chroot existed.
BUG=none
TEST=run the new one, see it work the same
Change-Id: I851fc4a0f28e32a9bbd01b2e4ddedbaffc6abf1c
Reviewed-on: http://gerrit.chromium.org/gerrit/876
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
BUG=quickfix for bot break
TEST=run ./update_chroot
Change-Id: I459d50f3e3374c1ff8ff8fc692c8ba7f3582bbd5
Reviewed-on: http://gerrit.chromium.org/gerrit/743
Tested-by: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
