From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 1E59E1382C5 for ; Sun, 25 Mar 2018 19:25:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A3669E0935; Sun, 25 Mar 2018 19:25:18 +0000 (UTC) Received: from very.loosely.org (very.loosely.org [173.255.215.69]) (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 37B15E0917 for ; Sun, 25 Mar 2018 19:25:17 +0000 (UTC) Received: from [10.8.78.6] (port=51246 helo=matica.foolinux.mooo.com) by ahiker.mooo.com with esmtp (Exim 4.89) (envelope-from ) id 1f0BGW-0007Xv-R2 for gentoo-user@lists.gentoo.org; Sun, 25 Mar 2018 12:25:16 -0700 Received: from itz by matica.foolinux.mooo.com with local (Exim 4.90_1) (envelope-from ) id 1f0BGQ-0000Fd-Kb for gentoo-user@lists.gentoo.org; Sun, 25 Mar 2018 12:25:10 -0700 Date: Sun, 25 Mar 2018 12:25:10 -0700 From: Ian Zimmerman To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: Would unmerging xorg-server certainly help it? Message-ID: <20180325192510.qfhe6hkpcfmkj7ey@matica.foolinux.mooo.com> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20180325135045.78a46753@digimed.co.uk> <20180325151029.epicfhzrdwrx3h22@matica.foolinux.mooo.com> <4MPLOSRD.OYRO6OHE.MRMCK25T@OZ4GAO6A.I7JTEDE2.5Y53XU5H> <878tagt7bv.fsf@gmail.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Loosely-Listed: yes User-Agent: NeoMutt/20170707-dirty (1.8.3) X-Archives-Salt: 3388a1ae-922b-4bed-833f-48244067c879 X-Archives-Hash: e94dec2b9657613783758835ab00c691 On 2018-03-25 17:49, Martin Vaeth wrote: > It should be scrnsaverproto-1.2.2-r2 which is pulled in. > Maybe you sync'ed at an unfortunate moment. Try emerge --sync again. In my case at least, the root cause was this: in the nightly webrsync snapshot (which I prefer to use instead of rsync), scrnsaverproto-1.2.2-r2 is keyworded and not stable. Adding it to portage/package.use magically unblocks everything. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.