Created by Chad Miller and last modified
Get this branch:
bzr branch lp://qastaging/~chromium-team/chromium-browser/precise-proposed
Members of Chromium team can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Chromium team
Chromium Browser

Recent revisions

841. By C Miller <email address hidden>

Release '28.0.1500.71-0ubuntu1.12.04.1'.

840. By Chad Miller

Removing testing code from rules near get-orig-src.

839. By Chad Miller

Fix control breakage

838. By Chad Miller

* New release 28.0.1500.71.
* debian/chromium-browser.install: Include inspector resources in
  chromium-browser package.
* debian/rules:
  - Remove tests for ancient versions of Ubuntu.
  - Return to using no explicity NEON fpu, and instead try to detect at
    runtime NEON caps. This effectively disables NEON, so far.
  - Build and run unit test suite as part of making a package. Abort if
    more than 15 out of ~1000 tests fail.
  - Clean up packaging sanity test that verifies everything we build is
    put into a package.
  - Set relative rpath to libs/ for chromium-browser executable, but . for
    libraries in libs/ ; that makes dpkg-shlibdeps happy and process run.
  - Strip out some ugly logic around keeping only one language in the main
    package, and keeping the contents verifier happy based on the
  - EXPERIMENT: Try not stripping enormous libraries' symbols explicitly.
  - Add more exceptions for packaging contents tests, this time to exclude
    files that are in package but not from the build tree.
  - Be more explicit about what files we set the rpath on. Get all
    executables. We missed chromedriver before.
  - Only one hardware arch builds the independent files, so in our sanity
    test that we install everything upstream built once and only once in
    packages, we have to consider whether this build didn't even try to
    take and use arch-independent files. Don't look for some file paths if
    we don't use them. (Also, if we match too much of what we used, also
    remove matches from the list of created. This should be better.)
* debian/patches/arm-neon.patch:
  - Compile in NEON instructions for ARM, even if we can't reliably check for
    whether our CPU is capable of running them yet. The major problem
    remaining is that the sandbox security wrapper defeats any test of
    /proc/cpuinfo .
* debian/source/lintian-overrides:
  - Supress warnings about known intentional decisions: Package name,
    statically linked bundled libraries, setuid root sandbox.
* debian/chromium-browser.sh.in:
  - Detect at startup the features of the CPU that we might be intersted
    in and export info into the environment. This is step one of a longer
    workaround for sandbox /proc restrictions.
* Make a fall-back for when upstream fails to release a Release. Package up
  as best we can from source control. debian/rules and
  debian/checkout-orig-source.mk .
* debian/tests/:
  - Add smoketest to verify that chromium runs.
  - Add a empty webapps test file for notes about what parts of webapps will
    or should be tested.
* debian/keep-alive.sh. Quit if disk environment disappears.
* debian/chromium-browser.install
  - Conform to newer Ayatana standard for Desktop Actions.

837. By Chad Miller

* Conform to newer Ayatana standard for Desktop Actions.
* Prefer "-extra" codecs package.

836. By Chad Miller

[Chris Coulson]
debian/rules: Disable tcmalloc on all component builds, not just on
arm builds.

835. By Chad Miller

* New stable release 28.0.1500.52
* Add new build-dep, "chrpath".

834. By Chad Miller

* New stable release 28.0.1500.45
* New stable release 27.0.1453.110:
  - CVE-2013-2855: Memory corruption in dev tools API.
  - CVE-2013-2856: Use-after-free in input handling.
  - CVE-2013-2857: Use-after-free in image handling.
  - CVE-2013-2858: Use-after-free in HTML5 Audio.
  - CVE-2013-2859: Cross-origin namespace pollution.
  - CVE-2013-2860: Use-after-free with workers accessing database APIs.
  - CVE-2013-2861: Use-after-free with SVG.
  - CVE-2013-2862: Memory corruption in Skia GPU handling.
  - CVE-2013-2863: Memory corruption in SSL socket handling.
  - CVE-2013-2864: Bad free in PDF viewer.
* Exclude included XDG files even if they are built.
* Use NEON instructions on ARM, optionally. This might use run-time checks
  for hardware capability, but even if it doesn't we can add it later.
* Clean up difference checks in debian/rules that make sure that all files
  that the build makes are used in packages, and no longer hide any, and no
  longer consider it an error if some are unused. Treat it as a warning,
  not a fatality.
* Use legible shell instead of make-generated shell in setting the rpath
  in rules.

833. By Chad Miller

About 32-bit component libraries, fix a libdir path bug in
debian/chromium-browser.sh.in .

No longer try to use system libraries. Generally, Security Team would
hate bundled libraries because they provide a wide liability, but
Chromium Project is pretty good about maintaining their bundled-source
libraries. We can not pull cr-required lib versions forward in older
Ubuntus, and we can't guarantee all the distro versions of libraries work
with chromium-browser. The default security policy might be worse. Bundled
libraries is less work overall.

832. By Chad Miller

Reenable dyn-linking of major components of chromium for 32-bit machines.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.