Format: 1.8
Date: Mon, 15 Jul 2013 17:44:47 -0400
Source: chromium-browser
Binary: chromium-browser chromium-browser-dbg chromium-browser-l10n chromium-codecs-ffmpeg chromium-codecs-ffmpeg-dbg chromium-codecs-ffmpeg-extra chromium-codecs-ffmpeg-extra-dbg chromium-chromedriver chromium-chromedriver-dbg
Architecture: source
Version: 28.0.1500.71-0ubuntu1.13.04.1
Distribution: raring-security
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Changed-By: Chad MILLER <chad.miller@canonical.com>
Description: 
 chromium-browser - Chromium browser
 chromium-browser-dbg - chromium-browser debug symbols
 chromium-browser-l10n - chromium-browser language packages
 chromium-chromedriver - WebDriver driver for the Chromium Browser
 chromium-chromedriver-dbg - chromium-chromedriver debug symbols
 chromium-codecs-ffmpeg - Free ffmpeg codecs for the Chromium Browser
 chromium-codecs-ffmpeg-dbg - chromium-codecs-ffmpeg debug symbols
 chromium-codecs-ffmpeg-extra - Extra ffmpeg codecs for the Chromium Browser
 chromium-codecs-ffmpeg-extra-dbg - chromium-codecs-ffmpeg-extra debug symbols
Changes: 
 chromium-browser (28.0.1500.71-0ubuntu1.13.04.1) raring-security; urgency=low
 .
   * New release 28.0.1500.71.
   * debian/chromium-browser.install: Include inspector resources in
     chromium-browser package.
   * debian/control: Make new -dbg package for chromedriver.
   * 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
       architecture.
     - 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.
Checksums-Sha1: 
 1f9b366990531305ec19e0d78822b12aa94d51ab 3085 chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.dsc
 a2203c1b4176e8258f6aba7391a190b4a447de1b 147343244 chromium-browser_28.0.1500.71.orig.tar.xz
 c8aaeed3caf19064c9b118e5bbd248d65e5cf8a8 250175 chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.debian.tar.gz
Checksums-Sha256: 
 2003131738cd2e92724ab453883c3bf04430b61ac8826e88a1db88421ae2b4e8 3085 chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.dsc
 8ff0c0b2a61ffc366a1d2d88377ac852364d57c769b39201f6cfa8d5a82c1449 147343244 chromium-browser_28.0.1500.71.orig.tar.xz
 adae5749754ae82210718c74116d6b52e1a66f326f3ca75eeafead225a2d1c45 250175 chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.debian.tar.gz
Files: 
 971433be1f4a34edde90115bbc77cf18 3085 web optional chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.dsc
 bd19a76d5d8feffc169ae7ee7a4fbca1 147343244 web optional chromium-browser_28.0.1500.71.orig.tar.xz
 6a98e7b8bcbeae1bacb402c5f7e5cef8 250175 web optional chromium-browser_28.0.1500.71-0ubuntu1.13.04.1.debian.tar.gz
Original-Maintainer: Micah Gersten <micahg@ubuntu.com>, Fabien Tassin <fta@ubuntu.com>