[Pkg-chromium-maint] Bug#585801: fixed in chromium-browser 5.0.375.86~r49890-1

[Jonathan Nieder]

>  chromium-browser (5.0.375.86~r49890-1) unstable; urgency=low
>  .
>    [ Jonathan Nieder ]
>    * Use dpkg-architecture directly instead of relying on
>      dpkg-buildpackage to set DEB_*_ARCH variables.  Use
>      DEB_HOST_ARCH_CPU instead of DEB_BUILD_ARCH to detect target CPU.
>      (Closes: #585801)

Thank you. :)

>    [ Giuseppe Iuculano ]
>    * New stable version, this release fixes the following security
>      issues:
>      - [38105] Medium XSS via application/json response (regression). Credit to
>         Ben Davis for original discovery and Emanuele Gentili for regression
>         discovery.
>      - [43322] Medium Memory error in video handling. Credit to Mark Dowd under
>         contract to Google Chrome Security Team.
>      - [43967] High Subresource displayed in omnibox loading. Credit to Michal
>         Zalewski of Google Security Team.
>      - [45267] High Memory error in video handling. Credit to Google Chrome
>        Security Team (Cris Neckar).
>      - [46126] High Stale pointer in x509-user-cert response. Credit to Rodrigo
>        Marcos of SECFORCE.
>      - Drop the XLIB_SKIP_ARGB_VISUALS workaround as it creates regressions.
>        See http://crbug.com/46439

For the future: wouldn’t security fixes like this warrant urgency=medium?