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 44E5313877A for ; Thu, 24 Jul 2014 22:05:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 383BAE0A8A; Thu, 24 Jul 2014 22:05:24 +0000 (UTC) Received: from mx2.cims.nyu.edu (MX2.CIMS.NYU.EDU [128.122.49.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A8CF9E0969 for ; Thu, 24 Jul 2014 22:05:18 +0000 (UTC) Received: from smtp.cs.nyu.edu (smtp.cs.nyu.edu [128.122.49.97]) by mx2.cims.nyu.edu (8.14.4+Sun/8.14.4) with ESMTP id s6NDOnD6026815 for ; Wed, 23 Jul 2014 09:24:49 -0400 (EDT) Received: from newlap-wireless.localdomain (ool-182de8a5.dyn.optonline.net [24.45.232.165]) (authenticated bits=0) by smtp.cs.nyu.edu (8.14.3/8.14.4) with ESMTP id s6NDOiO1026812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 23 Jul 2014 09:24:49 -0400 (EDT) Received: by newlap-wireless.localdomain (Postfix, from userid 1000) id BDB38AAF19; Wed, 23 Jul 2014 09:24:44 -0400 (EDT) From: gottlieb@nyu.edu To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] updating ALL packages Date: Wed, 23 Jul 2014 09:24:44 -0400 Message-ID: <874my82oo3.fsf@nyu.edu> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.1 (mx2.cims.nyu.edu [128.122.49.96]); Wed, 23 Jul 2014 09:24:49 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.97.4 at mx2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.73 on 128.122.49.96 X-Archives-Salt: 365de64e-1601-4c65-8677-4e36489cc89d X-Archives-Hash: b565a5dadf4cf3f4c1f20cf8e7c9a240 My normal updating procedure is EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --jobs --load-average=5" emerge --update --changed-use --keep-going @world I had mistakenly thought this would update all packages not at the latest version (subject to package.accept_keywords, package.mask, ...). I now realize that it only does this for the packages in world and then follows the dependency tree. So if package A in world is up to date, A depends of B, and a new version of B appears, B will not be updated. As a result eix-test-obsolete finds that I have packages installed that are no longer in the database. I could do emerge --update the-2-dozen-such-packages Is that wise? thanks, allan PS This system is in the midst of the multi-month bothwick "goingstable" procedure. I don't know if that is relevant to the decision. Neil Bothwick wrote: > > You can generate the list with > > qlist -ICv | sed -e 's/^/~/' -e 's/-r[1-9]$//' \ > >/etc/portage/package.accept_keywords/goingstable > > This allows revision updates, which is useful as they usually contain bug > or security fixes, but doesn't allow any higher versions. > > Occasionally running eix-test-obsolete will let you know which entries > have become redundant because stable has caught up with them. > > I recently used it to move a machine from testing to stable. The one > caveat is that sometimes the testing version your have installed, and in > package.accept_keywords, is removed from the tree so portage wants to > downgrade to the latest stable version. You have the choice of letting > this happen or unmasking a later testing version. [ subsequently he recommended using the latter choice ]