[ubuntu/saucy-proposed] chromium-browser 28.0.1500.71-0ubuntu1.13.10.1 (Accepted)

Chad MILLER chad.miller at canonical.com
Wed Jul 24 15:06:43 UTC 2013


chromium-browser (28.0.1500.71-0ubuntu1.13.10.1) saucy; 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.
  * Release to PPA.

Date: Thu, 18 Jul 2013 20:05:00 -0400
Changed-By: Chad MILLER <chad.miller at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: Chris Coulson <chris.coulson at canonical.com>
https://launchpad.net/ubuntu/saucy/+source/chromium-browser/28.0.1500.71-0ubuntu1.13.10.1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 18 Jul 2013 20:05:00 -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.10.1
Distribution: saucy
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Chad MILLER <chad.miller at 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.10.1) saucy; 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.
   * Release to PPA.
Checksums-Sha1: 
 804a0f509d630cff1cb5f8f6d3f0e6047f86dd3e 3085 chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.dsc
 a2203c1b4176e8258f6aba7391a190b4a447de1b 147343244 chromium-browser_28.0.1500.71.orig.tar.xz
 808c8cbbf0b0cc2ec6217592fff269a574e43abe 250453 chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.debian.tar.gz
Checksums-Sha256: 
 698823be2ec117c4dab867cd195a841b9f7b96b1a396b97865a39b3cb283ecdf 3085 chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.dsc
 8ff0c0b2a61ffc366a1d2d88377ac852364d57c769b39201f6cfa8d5a82c1449 147343244 chromium-browser_28.0.1500.71.orig.tar.xz
 fc3fb5ba625d8a24c767a47a8edc93d31be2ef2772637abb6465beb4a80c1697 250453 chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.debian.tar.gz
Files: 
 16cbdde5801deeb287e425a6ae32fbcd 3085 web optional chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.dsc
 bd19a76d5d8feffc169ae7ee7a4fbca1 147343244 web optional chromium-browser_28.0.1500.71.orig.tar.xz
 403ca09739a9ff43224e704e88ae66d8 250453 web optional chromium-browser_28.0.1500.71-0ubuntu1.13.10.1.debian.tar.gz
Original-Maintainer: Micah Gersten <micahg at ubuntu.com>, Fabien Tassin <fta at ubuntu.com>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJR7+vjAAoJEGEfvezVlG4P6AgH/j2LPjtmTz4HDKv0VlEfKKPo
5+8rmvR/yhrDo9sOncHbS/1Cd1Woz8Dn6D4iTTa55zsebnSYjaRuJEwPepDcSOsa
JEqHvAz6nFDEI6v1x+hAmB1ZqdgddAlxmVhr2nC+whQCfWqUR4lOY//OaWVodRk+
S3Gtg7zOuuh4KlJe6Z/vkxRabpQ4aeCRPXcwjbdeZa5Pa2Bv8yh7Bg2MWS9vTOLq
B+AVBu8VUQn/TsVwLreD8wjdkXuZEcpecFhiV7zJij3TiytQ7WxTVcY6BU69tbQk
E9JdIWB1ZSxb9xWsZlgkIWySTqekInAGb1OQgsSHSlyiXHQeKEzse/Yva2YX+H8=
=TaEZ
-----END PGP SIGNATURE-----


More information about the Saucy-changes mailing list