32.0.1700.77 released

[René Ladan]

On 01/16/2014 15:45, Carlos Jacobo Puga Medina wrote:
> I installed it by passing the DDISABLE_VULNERABILITIES option, but I
> can confirm that the new chrome released doesn't work as expected. It
> crashes over and over again e.g. when I check the chrome
> version/plugins/chrome info (just typing 'chrome://command' in the
> address bar).
>
> I deleted the $HOME/.config/chromium directory, but no change in
> behaviour. So I will return to previous version.
>
Can you try updating to 32.0.1700.77 instead? .72 is a beta version but
has most likely less vulnerabilities than 31.0.* (which is now unsupported).

René
> 2014/1/16 Carlos Jacobo Puga Medina <cjpugmed at gmail.com
> <mailto:cjpugmed at gmail.com>>
>
>     When upgrading chromium port shows that it has multiple
>     vulnerabilities.
>
>     ===>  chromium-32.0.1700.72 has known vulnerabilities:
>     Affected package: chromium-32.0.1700.72
>     Type of problem: chromium -- multiple vulnerabilities.
>     Reference:
>     http://portaudit.FreeBSD.org/5acf4638-7e2c-11e3-9fba-00262d5ed8ee.html
>     => Please update your ports tree and try again.
>     *** [check-vulnerable] Error code 1
>
>     Stop in /usr/ports/www/chromium.
>     *** [build] Error code 1
>
>     Stop in /usr/ports/www/chromium.
>
>     ===>>> make failed for www/chromium
>     ===>>> Aborting update
>
>
>
>