Upgraded sys-fs/dosfstools to version 3.0.9 on arm, x86
Removed dosfstools-3.0.11-name-ext.patch
BUG=chromium-os:21245
TEST=booted on alex and kaen and ran dosfsck on each
Change-Id: I395b3983ff3656999dcbe7b7ad06c80915f36496
Reviewed-on: http://gerrit.chromium.org/gerrit/10413
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Paul Taysom <taysom@google.com>
Legacy boot loader like syslinux is only for x86 platforms.
We should ignore the configuration files if they don't exist.
BUG=chromium-os:21887
TEST=./make_factory_package --diskimg OUTPUT \
--release PATH_TO_ARM_IMAGE \
--factory PATH_TO_ARM_IMAGE \
--hwid none # success
# do the same for x86 builds, mount ESP (#12)
# and found 'sda3' in root.A.cfg
Change-Id: I53a8b418045465a69d700298b73793d60187f31a
Reviewed-on: http://gerrit.chromium.org/gerrit/10385
Reviewed-by: Tammo Spalink <tammo@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
If files are in the board build dir with newer mtimes than the dirs
or symlinks, then the get_latest_image code selects the file instead
of the latest dir. And then it all falls down:
Cannot find image directory /path/to/file
So tweak the look up code by having bash do the expansion of dirs
only, and then let ls do the mtime sorting.
BUG=None
TEST=`./image_to_usb.sh --board=x86-alex -y --to=/dev/sdb` still works after deleting "latest"
Change-Id: Ic06a2ddd0206748d35cb7762009df67a267d4746
Reviewed-on: http://gerrit.chromium.org/gerrit/10258
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
These files need not be +x to work since we source them directly.
BUG=None
TEST=update chroot from ver 12 to ver 13
Change-Id: I3133cf532286bed63308e82767f0c95900f54e84
Reviewed-on: http://gerrit.chromium.org/gerrit/10342
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:21850
TEST=`emerge chromeos-base` works cleanly
TEST=`emerge timezone-data` works cleanly
TEST=build_packages+build_image for x86-alex produces a bootable image
TEST=build_packages+build_image for arm-generic works
Change-Id: I35a76e6319ebcc6c95b9a7c1792686c1c2a291dd
Reviewed-on: http://gerrit.chromium.org/gerrit/10315
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
This basically just gets us arm stable.
BUG=None
TEST=`emerge-arm-generic attr` works
TEST=build_packages+build_image for arm-generic works
Change-Id: I0bf9a6da05ef940563181e3aabef48abb6918c1b
Reviewed-on: http://gerrit.chromium.org/gerrit/10330
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Since we need this anyways (can't assume the host outside of the chroot
provides shflags), always source the local copy rather than searching
for versions provided by the chroot.
BUG=chromium-os:21742
TEST=`cros_sdk --enter` works
TEST=`./build_packages --board=amd64-generic` works
Change-Id: Ia390042131f59948472b124cfe4e273483eada6a
Reviewed-on: http://gerrit.chromium.org/gerrit/10231
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=build_packages for amd64-generic works
TEST=build_packages+build_image for arm-generic works
TEST=build_packages+build_image for x86-alex works & boots
Change-Id: I95f35ccf7fd62a4b3d52746b17ad18157fcec0a6
Reviewed-on: http://gerrit.chromium.org/gerrit/10329
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This basically just gets us arm stable.
BUG=None
TEST=`emerge-arm-generic acl` works
TEST=build_packages+build_image for arm-generic works
Change-Id: I057883e6b860ca158ed2d25b94165b7347d71110
Reviewed-on: http://gerrit.chromium.org/gerrit/10331
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
"new_kern.bin" was being generated in the current directory and not
being cleaned up. Additionally, without this change, it is not safe to
run update_kernel.sh concurrently to separate devices.
BUG=None
TEST=Updated a kernel on a running VM, verified /tmp/update_kernel.* was
created and used for generated outputs.
Change-Id: I27cd236ee9d38263dcca361ce063078a13b11864
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/10240
Reviewed-by: Olof Johansson <olofj@chromium.org>
Convert image_to_usb.sh, mod_image_for_recovery.sh, and
mod_image_for_test.sh to use get_latest image; previously these
scripts wouldn't honor the 'latest' symlink.
BUG=None
TEST=re-link 'latest' to an alternate directory; test scripts
Change-Id: Ibb56bb993eae9b6ff9dbfea5090c7cae46f2c133
Reviewed-on: http://gerrit.chromium.org/gerrit/10267
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
The KVM examples boot from the syslinux partiton, so update the kernel
that lives there too.
BUG=None
TEST=correctly updated a kernel in a VM
Change-Id: I1526064f85d6c9233696590e9e746bc91bcd6d2a
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/10239
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>
Verified boot is not supported yet for USB+EFI boot, which is the case
of factory install shim. We need to select normal boot in legacy boot
loaders when building factory install shim.
BUG=chrome-os-partner:6358
TEST=build_image --factory_install
# boots successfully under ZGB H2O firmware
Change-Id: Ic4645a1766514bf7e0c31f8a4df21452bf195705
Reviewed-on: http://gerrit.chromium.org/gerrit/10013
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
BUG=chromium-os:21822
TEST=manual
testing: ran with --debug, and verified that the chosen image file
is appropriate. (test image is chosen, unless --no-test is specified.
if both --test and --no-test are present, image file is chosen
according to whichever option appears last.)
Change-Id: Ia0a6d0ebac889a347d1b8989b8b2c3db8231dcae
Reviewed-on: http://gerrit.chromium.org/gerrit/10265
Tested-by: mukesh agrawal <quiche@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Ready: mukesh agrawal <quiche@chromium.org>
Nothing uses this directly yet. We'll be migrating packages from
dev-libs/shflags in future CLs.
BUG=chromium-os:21742
TEST=`emerge dev-util/shflags` works even when dev-libs/shflags is installed
Change-Id: I5177f90c4bfcf339c44aa64d1b2ceabe7676d750
Reviewed-on: http://gerrit.chromium.org/gerrit/10230
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Upgraded dev-embedded/u-boot-tools to version 2011.06 on amd64
Removed 3 unneeded patch files.
BUG=chromium-os:21241
TEST=emerge u-boot-tools; see that it succeeds
Change-Id: I3ab6b52e68fd166bcbe18ff2bdc5d319b96e7564
Reviewed-on: http://gerrit.chromium.org/gerrit/10237
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
Currently not causing any issues due to use-manifests being in lenient mode,
but should sort this prior.
BUG=chromium-os:11308
TEST=repoman manifest a pkg, check the results
Change-Id: I8006fb04ba84cef372881d6d684b35fe99d30f06
Reviewed-on: http://gerrit.chromium.org/gerrit/10122
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
Upgraded sys-fs/mtools to version 4.0.15 on x86 and arm.
BUG=chromium-os:21238
TEST=built x86 and arm platforms
Change-Id: I2fcf0bfd098a12e69d54111e80feec8d2177aa4a
Reviewed-on: http://gerrit.chromium.org/gerrit/9955
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
This package is used internally by portage for a lot of ELF checking,
so any update that continues to identify ELFs means it's working.
BUG=None
TEST=`emerge pax-utils` worked
TEST=`emerge-amd64-generic pax-utils` worked
TEST=`emerge-arm-generic pax-utils` worked
TEST=`emerge-x86-generic pax-utils` worked
TEST=`emerge-x86-alex pax-utils` worked
Change-Id: I6209970a217544b6dc369e8125ef3e10586111a5
Reviewed-on: http://gerrit.chromium.org/gerrit/10073
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upgraded app-text/poppler-data to version 0.4.4 on amd64
Upgraded media-libs/jpeg to version 8b on amd64
Upgraded media-fonts/urw-fonts to version 2.4.9 on amd64
Upgraded app-text/ghostscript-gpl to version 9.04-r3 on amd64
Upgraded virtual/jpeg to version 0 on amd64
BUG=None
TEST=trybot chromiumos-sdk
All of these packages are currently only installed on the host.
Change-Id: Ib93c328d30fcd9840dab468ac610e7928f180a74
Reviewed-on: http://gerrit.chromium.org/gerrit/10004
Tested-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Section header like [x86-zgb] would match any single-character
file/directory name within 6-z. Escape open brackets to prevent
config section headers from being evaluated to match local files.
BUG=chromium-os:21518
TEST=1. Create a single-character file 'u', under the same
directory where you'll run make_factory_package.
2. Create a test.conf with section header "x86-zgb".
3. ./make_factory_package.sh --config test.conf
4. Verify u is not part of the executed command.
Change-Id: Ia6178b7fc2f8d707830ee7fed54f9e5ab60d6836
Reviewed-on: http://gerrit.chromium.org/gerrit/10012
Tested-by: Chinyue Chen <chinyue@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Commit-Ready: Chinyue Chen <chinyue@chromium.org>
Upgraded sys-fs/sshfs-fuse to version 2.3 on arm, x86
sshfs-fuse is only used by gmerge
BUG=chromium-os:21239
TEST=on both x86 and arm: ran gmerge sshfs-fuse twice (VERY recursive :)
Change-Id: I1a3c619f0c5ccd7e9bd27db5e4b41ace5c059473
Reviewed-on: http://gerrit.chromium.org/gerrit/10057
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
Upgraded dev-libs/libusb to version 1.0.8 on arm, x86
Upgraded sys-apps/usbutils to version 001 on arm, x86
usbutils was the last user of libusb-0.1.x, now everything should use
libusb-1.x API and we can remove the former.
BUG=chromium-os:21264 chromium-os:21265
TEST=./run_remote_tests.sh --board=x86-alex hardware_USB20
./lab_test.py --board=x86-alex --platforms=netbook_ALEX,netbook_ALEX_CDMA_GOBI3K suite_Smoke
manually inspect lsusb output
Change-Id: I2ff9be2add7b43cdbcf535b1a6441efdd9a5c4b0
Reviewed-on: http://gerrit.chromium.org/gerrit/10020
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
add a hook for fixing all pending config updates
BUG=chromium-os:13987
TEST=below
1) export CONFIG_PROTECT="/etc /usr/share"
2) checkout as old as possible revision of cros-overlay, update chroot to it
3) checkout HEAD and update back
4) run the hook, see it update thousands of files correctly
Change-Id: Idabf5475516ed58b76ceee6ffdc817a5f46839ad
Reviewed-on: http://gerrit.chromium.org/gerrit/10022
Reviewed-by: Sameer Nanda <snanda@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
BUG=chromium-os:13987
TEST=below
1) export CONFIG_PROTECT="/etc /usr/share"
2) checkout as old as possible revision of cros-overlay, update chroot to it
3) checkout HEAD and update back
4) run the hook, see it update thousands of files correctly
Change-Id: I4213de8ccba6e573541e96591ea0d033a10218a5
Reviewed-on: http://gerrit.chromium.org/gerrit/8938
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
This causes the script to treat amd64 the same as x86.
BUG=chromium-os:21284
TEST=./build_image for amd64-generic shouldn't generate an invalid
architecture error
Change-Id: I37284def3cb2f0b16ece20a74d65bdb8e0116cff
Reviewed-on: http://gerrit.chromium.org/gerrit/9962
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
This causes the script to treat amd64 the same as x86.
BUG=chromium-os:21284
TEST=./build_image for amd64-generic shouldn't generate an invalid
architecture error
Change-Id: I8f40a827684dde1258158d470a38623a8c936bca
Reviewed-on: http://gerrit.chromium.org/gerrit/9963
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>
Upgraded sys-libs/e2fsprogs-libs to version 1.41.14 on amd64
Upgraded sys-fs/e2fsprogs to version 1.41.14 on amd64
BUG=chromium-os:21256
TEST=ran build_image for alex and kaen, ran update engine unit tests
Change-Id: I35a4554afe7a2aecf01323e96f8c4f4c55059749
Reviewed-on: http://gerrit.chromium.org/gerrit/9875
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Paul Taysom <taysom@google.com>
Upgraded app-editors/vim-core to version 7.3.266 on amd64, arm, x86
Upgraded app-vim/gentoo-syntax to version 20101212 on amd64, arm, x86
BUG=chromium-os:21547
TEST=trybot chromiumos-sdk
Also open ebuild file using vi in chroot.
Change-Id: Ia6e1ba09f2ab750063f0533ba53640e8ba3e3077
Reviewed-on: http://gerrit.chromium.org/gerrit/9898
Tested-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Upgraded virtual/man to version 0 on amd64. Previously, we were
still using the old-style virtual/man support.
BUG=chromium-os:21532
TEST=`cros_sdk --delete ; cros_sdk`
Ensure that sys-apps/man-1.6f-r4 (latest) is now installed.
Verify accessing man pages still works in chroot.
Change-Id: Ieebf6fe80323974c1387ec7f95b9e2be58998393
Reviewed-on: http://gerrit.chromium.org/gerrit/9864
Tested-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
BUG=chromium-os:21030 chromium-os:21417
TEST=test uploads with ARM and x86 targets
test that Chrome symbols are ~87M when stripped down from ~160MB
Change-Id: I9207b3f6a5b757ffa58468c58b4440467dc44738
Reviewed-on: http://gerrit.chromium.org/gerrit/8777
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Ken Mixter <kmixter@chromium.org>
Commit-Ready: Ken Mixter <kmixter@chromium.org>
Upgraded dev-util/dialog to version 1.1.20100428 on arm, x86
BUG=chromium-os:21257
TEST=alsa-util uses this library, test alsa-mixer on Kaen and ZGB.
testbot: x86-generic-pre-flight-queue
Change-Id: I3971efb17cc98f034a47fe18e23a66f71d2e6641
Reviewed-on: http://gerrit.chromium.org/gerrit/9774
Tested-by: Dylan Reid <dgreid@chromium.org>
Commit-Ready: Dylan Reid <dgreid@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Details
This change updates 'alsa-plugins-1.0.22.ebuild' to
'alsa-plugins-1.0.24.ebuild'.
Testing
Followed instructions:
http://www.chromium.org/chromium-os/gentoo-package-upgrade-process
Executed the following, all successfully:
C="I2a77e14b"
cbuildbot --gerrit-patches "${C}" arm-generic-bin
cbuildbot --gerrit-patches "${C}" arm-tegra2-bin
cbuildbot --gerrit-patches "${C}" x86-generic-pre-flight-queue
cbuildbot --gerrit-patches "${C}" x86-mario-pre-flight-queue
o x86-mario
Built and installed new image
Played youtube video, w/ sound
Played wav file using aplay
Used gtalk
o tegra2_kaen
Built and installed new image
Played youtube video, w/ sound
Played wav file using aplay
Used gtalk
o Validated alsa-plugins-1.0.22 is currently used
In a source tree without my change:
equery-tegra2_asymptote list -op alsa-plugins
* Searching for alsaplugins ...
[-P-] [ ] media-plugins/alsa-plugins-1.0.20:0
[IP-] [ ] media-plugins/alsa-plugins-1.0.21:0
[-P-] [ ~] media-plugins/alsa-plugins-1.0.22:0
[--O] [ ~] media-plugins/alsa-plugins-1.0.24:0
In same source tree after cherry picking gerrit change 8911:
[-P-] [ ] media-plugins/alsa-plugins-1.0.20:0
[-P-] [ ] media-plugins/alsa-plugins-1.0.21:0
[-P-] [ ~] media-plugins/alsa-plugins-1.0.22:0
[I-O] [ ] media-plugins/alsa-plugins-1.0.24:0
In source tree which originated this change set:
equery-tegra2_kaen list -op alsa-plugins
* Searching for alsaplugins ...
[-P-] [ ] media-plugins/alsa-plugins-1.0.20:0
[-P-] [ ] media-plugins/alsa-plugins-1.0.21:0
[-P-] [ ~] media-plugins/alsa-plugins-1.0.22:0
[I-O] [ ] media-plugins/alsa-plugins-1.0.24:0
BUG=chromium-os:21259
TEST=See above
Change-Id: I2a77e14b484ecaead4f5b70914609f5d0c3324f4
Signed-off-by: Taylor Hutt <thutt@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/8911
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
To help developers knowing the proper usage of such command.
BUG=none
TEST=./make_factory_package --help
Change-Id: I5a5d0efd215d0239bd56830165f0a057ad7c7474
Reviewed-on: http://gerrit.chromium.org/gerrit/9707
Reviewed-by: Tammo Spalink <tammo@chromium.org>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Usually make_factory_package operates with normal files that does not need root
permission - except if output is a block device.
This CL tries to grant root permission by sudo if a block device is assigned to
--diskimg.
BUG=chrome-os-partner:2827
TEST=(as normal user) ./make_factory_acpakge --factory FACTORY \
--release RELEASE --hwid none --diskimg /dev/sde # completed
Change-Id: Ie1285e6b6f46f1af286e795a02a83294fce4eeaa
Reviewed-on: http://gerrit.chromium.org/gerrit/8789
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Tammo Spalink <tammo@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Upgraded dev-python/pyudev to version 0.12 on x86
BUG=chrome-os-partner:6235
TEST="sudo emerge udev" and "emerge-x86-zgb pyudev"
Change-Id: I5d9e8ff7d50631cc3b898768fa1389f679eeb282
Reviewed-on: http://gerrit.chromium.org/gerrit/8843
Tested-by: Chinyue Chen <chinyue@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Upgraded dev-libs/expat to version 2.0.1-r5 on amd64, arm, x86
BUG=chromium-os:21465
TEST=trybots:
x86-generic-pre-flight-queue
arm-generic-bin
chromiumos-sdk
Change-Id: I2425e67dd8e86ab8e61d37f73375067289f7a2b1
Reviewed-on: http://gerrit.chromium.org/gerrit/9794
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Matt Tennant <mtennant@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Tegra2 systems require a minimum vmalloc bootarg to successfully
reserve the graphics carveout memory. If the vmalloc is insufficient
a crash can result prior to any serial output reported. The minimum
vmalloc is >= carveout size + framebuffer - 32MB, thus for a 256MB
graphics carveout (with 10MB framebuffer), vmalloc>=234MB. This
arg is not added in the u-boot configs to avoid tightly coupling
the u-boot and kernel and is discussed in greater depth at
http://gerrit.chromium.org/gerrit/#change,8293.
BUG=chrome-os-partner:5197,chrome-os-partner:5902
TEST=Manually observe /proc/cmdline reflects change
Change-Id: I66b35b266c7542771f2d4fc497dd4429587529f8
Reviewed-on: http://gerrit.chromium.org/gerrit/8373
Commit-Ready: Katie Roberts-Hoffman <katierh@chromium.org>
Reviewed-by: Katie Roberts-Hoffman <katierh@chromium.org>
Tested-by: Katie Roberts-Hoffman <katierh@chromium.org>
It was not marked executable, and was also broken. Now updates the
CHROMEOS_RELEASE_TRACK to be testimage-channel for test images.
BUG=chromium-os:20019
TEST=Manual
Change-Id: I8741f0e21831fe3d9184ca11b73dcea96a1b01b1
Reviewed-on: http://gerrit.chromium.org/gerrit/9801
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Upgraded dev-libs/newt to version 0.52.12 on amd64
BUG=chromium-os:21242
TEST=`sudo emerge newt perf` inside the chroot,
run perf on data collected on a target
Change-Id: Iedc173dce92f4f58f4aa69b0c64f3374fcec8bcf
Reviewed-on: http://gerrit.chromium.org/gerrit/9773
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>
This is needed to update gtk+, which is needed for Xi2 events.
Change-Id: Ieca0e1d6d09792ebca4ed46ad8d1c25a6aeb7f33
Reviewed-on: http://gerrit.chromium.org/gerrit/9763
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Upgraded sys-apps/gawk to version 3.1.8 on amd64
Upgraded dev-util/scons to version 2.0.1 on amd64
Upgraded dev-libs/libxslt to version 1.1.26-r1 on amd64
Upgraded app-text/texi2html to version 1.78 on amd64
BUG=chromium-os:21328
TEST=Each package is only on the host, so: trybot chromiumos-sdk
Change-Id: I4c91d5fb1a54dff55ea1420a290792dd6b503071
Reviewed-on: http://gerrit.chromium.org/gerrit/8825
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Tested-by: Matt Tennant <mtennant@chromium.org>
