Add a script to import all binary packages for a given source package
from ports.ubuntu.com, convert and install them using 'chromiumos-build
--convert', and write out a fake .changes file so that chromiumos-build
doesn't try to re-import them. Use it like this:
./import_native_build.sh anthy libchewing
For the moment, there are a number of source packages that won't
cross-build successfully but that can be imported from native Ubuntu
builds, and this wraps up the process of doing so.
Review URL: http://codereview.chromium.org/543059
This makes it possible to attempt a build using chromiumos-build by
running './build_platform_packages.sh --new-build', with an -a option to
select the architecture (e.g. -a armel).
Right now, this uses --apt-source to build all build-dependencies as
well, since that usually ends up being what you want when
cross-compiling. I'd appreciate feedback from buildbot-oriented folks
on whether this is an acceptable load in general. For the meantime,
this is mainly for the convenience of people working on the cross-build
project.
Review URL: http://codereview.chromium.org/546042
The package_script_whitelist.sh is intendended to make it easy
to make passes through the set of packages that have preinst
or postinst maintainer scripts and add them to the whitelist.
The audit mode will use the PAGER to show non-whitelisted preinst
and postinst scripts and ask you if you want to whitelist them,
create a template alternative maintainer script, skip, etc.
There are also commands to add individual scripts or check to
see if they are in the whitelist.
Review URL: http://codereview.chromium.org/543027
This changes install_packages to always have apt use our dpkg
wrapper when building an image. The dpkg_no_scripts.sh has been
modified to check if a package's maintainer scripts have been
whitelisted. If so, it will install without maintainer scripts.
If any relevant maintainer script has not been whitelisted it
will fall back to standard dpkg which will process the
maintainer scripts.
This will allow us to transition to installing packages without
maintainer scripts in batches rather than all at once. Once
everything is switched over we will have dpkg_no_scripts.sh
throw an error if it encounters a package with maintainer
scripts that have not been whitelisted.
Move postinst stuff from install_packages.sh to actual postinst
scripts.
Review URL: http://codereview.chromium.org/549017
This change switches to mastering an image without using debootstrap.
We turn on the previously experimental bits that install a small
set of packages manually before handing things over to apt. In both
cases we use apt to download the packages so that it can populate
it's local package cache.
With this change we will no longer depend on the local_repo when
mastering an image. Developers will not have to rebuild their
local repo when repo_list_image.txt changes. Instead we will use
and lazy-fill the local apt-cache. The first time you build_image.sh
it will be slow since it needs to download the packages. Subsequent
runs should be as before since it will use the local cache. If
packages are added they should be lazily fetched in the next image
build.
Until we have a fully populated external mirror, developers will
still have to add packages to repo_list_image.txt. Also, until
make_chroot is switched over to use the external repo then
developers will have to redo their local repo when the
repo_list_dev.txt changes.
Review URL: http://codereview.chromium.org/521073
This is a script to run client or server autotests on a live Chromium OS instance, collect results, and optionally upload the to an autotest database. This includes functional and performance tests. We assume the remote instance is running an appropriate image installed (one created using mod_image_for_test.sh and possibly installed using image_to_live.sh).
An example run might be
run_remote_tests.sh --remote=192.168.1.5 BootPerfServer -o results.txt
This example will run src/platform/testing/server_tests/system_BootPerfServer
5 times on instance at 192.168.1.5 and collect results in result.txt.
Also refactors and improves readability in image_to_live.sh.
Review URL: http://codereview.chromium.org/519041
This change also switches us to pre-populate the apt cache with
the set of packages needed to run apt and install them from there
rather than referring to the soon-to-be-defunct local repo.
Review URL: http://codereview.chromium.org/523146
We use apt to install the majority of our packages. In order to
get apt running where it can install packages we first need to
force install a small set of packages that have cyclic dependencies.
This CL reduces the required set quite a bit and fixes a bug where
we were installing a few wrong packages than what we were attempting
to install due to a bad glob.
Review URL: http://codereview.chromium.org/519075
Set LANG=C also when providing a command to enter_chroot.sh. Should make
buildbot logs quite a bit shorter.
Review URL: http://codereview.chromium.org/521053
A few weeks ago, dbus-uuidgen command was removed from the platform/init/dbus.conf script, but after the "upgrade-everything-to-Karmic" change, I think generating the uuid has become mandatorty again.
Without the uuid file (/var/lib/dbus/machine-id), ibus-daemon which uses D-Bus as its IPC channel does not work at all. I'm not sure but possibly the same is true for dbus-daemon?
chronos@localhost:/home/chronos$ ibus-daemon
process 2254: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
BUG=1127
TEST=On xterm, run /usr/bin/ibus-setup and verify the command does not show an error like "ibus-daemon is not working."
Review URL: http://codereview.chromium.org/508018
running maintainer scripts.
This is a work-in-progress. If you build_image like:
EXPERIMENTAL_NO_DEBOOTSTRAP=1 ./build_image.sh
it will skip debootstrap and install the base required packages
without running maintainer scripts. This is about 68 packages that
have lots of interleaved dependencies so it is nasty to trim down.
If you build like:
EXPERIMENTAL_NO_MAINTAINER_SCRIPTS=1 ./build_image.sh
it will install all packages skipping maintainer scripts.
Using these we can try and get things in a state where we can
create an image built of cross-compiled packages.
This is obviously not finished but in this case I prefer to commit
early so others can poke at it.
Review URL: http://codereview.chromium.org/527015
src/third_party/chrome/ needs dh-chromeos. Fortunately at least
dh-chromeos doesn't need anything else from our tree, so let's build and
install it really early.
Review URL: http://codereview.chromium.org/518051
Add make_pkg.sh for src/third_party/chrome/ (a.k.a. libchrome-dev) and
src/common/ (a.k.a. libchromeos-dev) and (ab)use it to install those
packages once built.
Installing the packages from make_pkg.sh isn't very clean. However, this
gives us a migration path to future use of chromeos-build, which will
need these headers and libraries to be built as packages in order to
support cross-building cleanly.
Review URL: http://codereview.chromium.org/523109
dh-chromeos was originally intended for use once we switch to
chromiumos-build, but it turns out that it would be useful to be able to
use it beforehand to correct some cross-build problems. Accordingly,
give it a make_pkg.sh file and add it to build_platform_packages.sh.
Review URL: http://codereview.chromium.org/525030
This puts all package installation for the rootfs in one place. It
also makes it so that you can run install_packages.sh --root="foo"
outside of the build_image.sh script if you want to test something
without going through the full image build. With this change
build_image basically:
- Sets up a loopback mounted rootfs
- Calls install_packages.sh on rootfs
- Calls customize_rootfs on rootfs
- Makes the rootfs bootable
Review URL: http://codereview.chromium.org/520004
The chroot's apt.conf.d has a debconf file which tells apt
to run dpkg-preconfigure on all packages before installing.
We don't want to do this, especially with an automated build.
This CL changes the apt config used by install_packages.sh to
be self-contained and skip including the default configs by
using the APT_CONFIG evnironement variable.
The CL also cleans up some of the apt command lines as well
as getting rid of some ugly "$ROOT_FS_DIR/..".
Review URL: http://codereview.chromium.org/522003
ibus-hangul provides an input method for Korean.
- third_party/ibus-hangul/libhangul_0.0.10-1.diff.gz
- third_party/ibus-hangul/libhangul_0.0.10.orig.tar.gz
These files are source package of libhangul for Ubuntu Lucid (10.04 LTS) at http://packages.ubuntu.com/en/lucid/libhangul0-data.
Since Karmic's libhangle (0.0.9) is too old to build ibus-hangul trunk, we'll build libhangul packages ourselves.
- third_party/ibus-hangul/make_pkg.sh
This script first builds and installs libhangul debian packages, then builds ibus-hangul.
- third_party/ibus-hangul/ibus-hangul_1.2.0.20090617-2.diff.gz
Copied from the Ubuntu Karmic's ibus-m17n package just like as third_party/clutter/clutter-1.0_1.0.4-0ubuntu1.diff.gz.
- third_party/ibus-hangul/ibus-hangul_remove_python_deps.diff
Patch for third_party/ibus-hangul/debian/rules which removes setup tools written in Python from the ibus-hangul debian package.
Review URL: http://codereview.chromium.org/501150
ibus-m17n provides input method engines for many languages such as Thai.
- third_party/ibus-m17n/make_pkg.sh
Copied from third_party/ibus-anthy/make_pkg.sh, then slightly modified.
- third_party/ibus-m17n/ibus-m17n_1.2.0.20090930-1.diff.gz
Copied from the Ubuntu Karmic's ibus-m17n package just like as third_party/clutter/clutter-1.0_1.0.4-0ubuntu1.diff.gz.
Review URL: http://codereview.chromium.org/502089
Given this we need to explicitly install xterm and lsof, but
otherwise it is a net reduction of about 45 packages, which is nice.
Review URL: http://codereview.chromium.org/515009
the maintainer scripts on installed packages.
I've experimented with using this in the install_packages.sh that
runs from outside the targetfs. It is able to extract packages and
make them appear to be installed (for the most part) without
running the maintainer scripts.
This will allow us to start figuring out what problems we will
have when we no longer run the maintainer scripts.
In the long run it would be nice to add an option to "dpkg" to
skip maintainer scripts.
Review URL: http://codereview.chromium.org/517004
and install debs into the target rootfs.
This will still run the maintainer scripts, but it is a step in
the right direction to being able to create a cross-compiled image.
This will allow us to experiment with disabling the maintainer
scripts and attempt to get that working. It also makes it easier
to modify the install_packages script since it now has access to
shflags and the source tree properly.
This CL also cleans up stuff doing in build_image.sh to bind mount
the trunk into the target rootfs, set up packages for install there,
etc.
The next step is to experiment with disabling maintainer scripts.
One possible way to do that would be to put a shim in place of dpkg
so that when apt calls dpkg it install a package we call dpkg-deb
with a simple unpack instead. This would allow us to continue to
use the good nice features that apt provides.
Review URL: http://codereview.chromium.org/517003
