From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-185310-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 40D67138334
	for <garchives@archives.gentoo.org>; Mon,  5 Nov 2018 16:44:11 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 24971E0BAF;
	Mon,  5 Nov 2018 16:44:04 +0000 (UTC)
Received: from blaine.gmane.org (unknown [195.159.176.226])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 9A787E0AF9
	for <gentoo-user@lists.gentoo.org>; Mon,  5 Nov 2018 16:44:03 +0000 (UTC)
Received: from list by blaine.gmane.org with local (Exim 4.84_2)
	(envelope-from <lnx-gentoo-user@m.gmane.org>)
	id 1gJhwj-0008Vl-KB
	for gentoo-user@lists.gentoo.org; Mon, 05 Nov 2018 17:41:49 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-user@lists.gentoo.org
From: Nikos Chantziaras <realnc@gmail.com>
Subject: [gentoo-user] Re: Permissions error on starting X.
Date: Mon, 5 Nov 2018 18:43:57 +0200
Message-ID: <prprs5$v8u$1@blaine.gmane.org>
References: <20181103140151.GA5029@ACM> <prlgsb$i84$1@blaine.gmane.org>
 <prpnmk$r04$3@blaine.gmane.org> <prpqt4$iqu$1@blaine.gmane.org>
 <CAGfcS_=SWwjp8at9VTB++70a4U9MQUXbT6nd8tOXynWQA7pq0w@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@blaine.gmane.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
In-Reply-To: <CAGfcS_=SWwjp8at9VTB++70a4U9MQUXbT6nd8tOXynWQA7pq0w@mail.gmail.com>
Content-Language: en-US
X-Archives-Salt: 2852fcde-0322-4e67-896e-e58d1d630fe9
X-Archives-Hash: 14b563bd37dd1e5fa07b625b60874ebd

On 05/11/2018 18:35, Rich Freeman wrote:
> On Mon, Nov 5, 2018 at 11:27 AM Nikos Chantziaras <realnc@gmail.com> wrote:
>>
>> On 05/11/2018 17:30, Grant Edwards wrote:
>>> On 2018-11-04, Nikos Chantziaras <realnc@gmail.com> wrote:
>>>> On 03/11/2018 16:01, Alan Mackenzie wrote:
>>>>> The developers, in this instance, failed to raise the ebuild's version
>>>>> number from 1.20.3 when making this change, and also didn't notify users
>>>>> by a NEWS item, that I can see.
>>>>
>>>> Emerge will catch this, no need for revbump. Unless you're not using -D
>>>> (--deep) when updating world. Which you should.
>>>
>>> What do you mean "catch this"?
>>>
>>> I always use -D, and the change broke my system.
>>
>> I mean that a USE flag change will trigger a rebuild of the package
> 
> -D will not cause USE flag changes to trigger a rebuild of a package.
> 
> You're thinking of --newuse in this particular case. 

Oops, yes. I meant -N (--newuse). Not -D. Got confused. I always upgrade 
using:

emerge -auDN --changed-deps @world

The "N" was the important flag here, not the "D".