From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] chromium-59.0.3053.3 will require >=sys-apps/sandbox-2.11 (currently hard masked)
Date: Thu, 13 Apr 2017 16:01:27 -0400 [thread overview]
Message-ID: <CAJ0EP43ZsgSPdZkzXAsJs3fBV_DgYkB8yfCBUBgCcHdF9wz5AA@mail.gmail.com> (raw)
In-Reply-To: <b102e802-2160-057c-d13f-47b773472229@gentoo.org>
On Thu, Apr 13, 2017 at 3:29 PM, Paweł Hajdan, Jr.
<phajdan.jr@gentoo.org> wrote:
> The latest dev channel release of chromium (59.0.3053.3) will require
>>=sys-apps/sandbox-2.11 to build.
>
> I'm sending this announcement because this version of sandbox is
> currently hard masked. So is the chromium version, but with its fast
> release cycle we can expect it hitting ~arch in few weeks, and stable in
> the next few weeks. I'd like to make sure we'd be able to push sandbox
> to stable at the same pace, or find some alternative solution.
>
> For curious folks, new sandbox fixes a hang which occurs with tcmalloc.
> See https://crbug.com/586444 . The new chromium adds a code generator
> needed for build (inside the network stack). I didn't find an easy way
> to disable tcmalloc just for that code generator, and after finding
> above bug new sandbox seemed like the best choice.
>
> See
> <https://gitweb.gentoo.org/repo/gentoo.git/commit/www-client/chromium?id=f2345c0af633116a69051239ab10d858d5aea69a>
> for the commit which introduced this, and feel free to share your
> suggestions.
The sandbox blocker could be moved behind a use-conditional:
tcmalloc? ( !<sys-apps/sandbox-2.11 )
If vapier or the QA team don't drop the sandbox mask, we can
package.mask the tcmalloc USE flag as an interim workaround.
next prev parent reply other threads:[~2017-04-13 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 19:29 [gentoo-dev] chromium-59.0.3053.3 will require >=sys-apps/sandbox-2.11 (currently hard masked) Paweł Hajdan, Jr.
2017-04-13 20:01 ` Mike Gilbert [this message]
2017-04-18 7:12 ` Mart Raudsepp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ0EP43ZsgSPdZkzXAsJs3fBV_DgYkB8yfCBUBgCcHdF9wz5AA@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox