From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 602AE138CD0 for ; Thu, 21 May 2015 14:06:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 208E2E0930; Thu, 21 May 2015 14:05:56 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1F5D9E084A for ; Thu, 21 May 2015 14:05:54 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 03271340DD7 for ; Thu, 21 May 2015 14:05:53 +0000 (UTC) Received: by iebgx4 with SMTP id gx4so8904679ieb.0 for ; Thu, 21 May 2015 07:05:50 -0700 (PDT) X-Received: by 10.43.34.205 with SMTP id st13mr3473017icb.4.1432217150835; Thu, 21 May 2015 07:05:50 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.64.124.229 with HTTP; Thu, 21 May 2015 07:05:30 -0700 (PDT) In-Reply-To: References: From: Mike Gilbert Date: Thu, 21 May 2015 10:05:30 -0400 Message-ID: Subject: Re: [gentoo-user] [~and64] Headsup for google-chrome users To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 319d53a7-a610-45cc-86b3-ef80cce43166 X-Archives-Hash: 3a06bb559cc863356f80465d47a5a373 On Thu, May 21, 2015 at 8:55 AM, walt wrote: > I just wasted some time figuring out this mess: > > I just updated google-chrome, which printed this confusing warning message: > > "CONFIG_USED_NS not seen when it should be" > > First, there's a typo: it should read "CONFIG_USER_NS" > ^ > Sorry about that. It's been fixed.