From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ReEO2-0002u3-Gf for garchives@archives.gentoo.org; Fri, 23 Dec 2011 23:18:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 86ED721C058; Fri, 23 Dec 2011 23:18:41 +0000 (UTC) Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 4AAAA21C031 for ; Fri, 23 Dec 2011 23:17:35 +0000 (UTC) Received: by ggnr5 with SMTP id r5so7994115ggn.40 for ; Fri, 23 Dec 2011 15:17:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=JZuiJCG1fiAoHYo287zDNd7d6RisneSrjBXxcUF70es=; b=GR+45xNLVZbUmXlIxzFe7T9awUkBYVJopM4JFMlX8eoBftfYE3MHoYhvaK8GT+p5nn hn1xYwTzUZe1zwGWRd6kLQdyaCKr/kNn3ueQs0qWjjxP1CBZJ4k7BJPeN5/EskAKlr39 uYWw/RYDMoemN4RrqvoxMB/lC+NIurO1bU6n0= Received: by 10.101.61.5 with SMTP id o5mr7437127ank.37.1324682254801; Fri, 23 Dec 2011 15:17:34 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-122-130.jan.bellsouth.net. [65.0.122.130]) by mx.google.com with ESMTPS id j21sm36815104ann.0.2011.12.23.15.17.32 (version=SSLv3 cipher=OTHER); Fri, 23 Dec 2011 15:17:33 -0800 (PST) Message-ID: <4EF50C0B.7010900@gmail.com> Date: Fri, 23 Dec 2011 17:17:31 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111022 Firefox/7.0.1 SeaMonkey/2.4.1 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure References: <20111222135813.42263034@weird.wonkology.org> <201112231038.54812.michaelkintzios@gmail.com> <4EF48AC2.3090105@gmail.com> <4EF4926A.3080102@gmail.com> In-Reply-To: <4EF4926A.3080102@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: c3c605f4-7a9f-4100-af5a-ac6bf6c50c8c X-Archives-Hash: 1363ee889a09abcaef7c5fbcdfa9b4b9 Michael Mol wrote: > Dale wrote: >> Michael Mol wrote: >>> On Fri, Dec 23, 2011 at 5:38 AM, Mick wrote: >>>> You need portage-2.2 to be able to use sets. >>> Sadly, 2.1.10.11 is the latest marked stable for ~amd64. (Or was, last >>> time I synced.) >>> >>> It'll be nice when it's available, though. >>> >> >> I been using the unstable portage for a long time. Since I built this >> rig if I recall correctly. It works fine but it does get updated pretty >> regular. Zac is always adding some new frills and shiney things. ;-) I >> wouldn't blame you for staying stable but it works fine here on my amd64 >> and old x86 rig. > > Devs don't seem to like bug reports involving mixes of stable and > unstable. I was mildly scolded for filing a bug report against xemacs' > failing to build with libpng15, when xemacs was stable, and libpng15 > wasn't, yet. I'm trying to being slightly more conservative about what > I unmask. > > Between autounmask and specific desires to be on top of some packages, > it's not easy. For example, stable WINE hasn't built since February > 2011... ( https://bugs.gentoo.org/show_bug.cgi?id=354745 ) Anyone who > needs WINE for any reason needs to use their unstable 1.3.x tree. This > isn't expected to be fixed until this coming *March*, when ICU 49 goes > generally available. > > /rant > > I file bugs with the unstable portage and I don't think I've ever heard them complain about running unstable portage. That said, sometimes when you run some software unstable and some not, then you can run into issues. A while back I was trying to burn home DVDs. I run the latest KDE4 but not all the way up to 9999 but unstable still. I had to also install unstable for the packages that it depended on as well. Things like DeVeDe and Bombono would not work well with them being unstable and the things under the hood running stable. Things like this, you have to make choices and just sort of figure out my trial and error. If in doubt, ask here first to see if a bug should be posted or not. If others have ran into the same issue, then maybe it needs to be filed possibly upstream. Thing is, the latest portage seems to fix things more than it breaks. It handles updates a lot better. The downside, docs are not to up to date. Zac manages to stay ahead of the docs at times. I monitor -dev to sort of keep up. Maybe they will mark it stable soon and you can test out all the new stuff. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"