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 1O9KN0-000836-OK for garchives@archives.gentoo.org; Tue, 04 May 2010 15:49:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A0AC2E0904; Tue, 4 May 2010 15:48:38 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by pigeon.gentoo.org (Postfix) with ESMTP id 50464E0904 for ; Tue, 4 May 2010 15:48:38 +0000 (UTC) Received: from [192.168.1.30] (dslb-188-099-249-025.pools.arcor-ip.net [188.99.249.25]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MTKyZ-1NkpCU20xj-00RsDH; Tue, 04 May 2010 17:48:37 +0200 Message-ID: <4BE041D5.6080903@konstantinhansen.de> Date: Tue, 04 May 2010 17:48:37 +0200 From: KH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100419 Thunderbird/3.0.4 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] emerge --update - why doesn't it update my kde packages References: <20100504155921.157968ee@karnak.local> In-Reply-To: <20100504155921.157968ee@karnak.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19IltXG87BscOZX9YSTaYO00g3z/24v87P6yj3 t9a6YhpB2jqr4QcAgr4TEqavsHfwwN2j6A3DKxsdj5kRgwat3Z QykNJGkCDRbMQdJo9QlKw== X-Archives-Salt: 2a198b1b-990b-4a61-9847-914b22052bed X-Archives-Hash: 9e2b56f1bfc5b63b751cb2a43c0b5048 Am 04.05.2010 16:59, schrieb David W Noon: > On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about > [gentoo-user] emerge --update - why doesn't it update my kde packages: > > [snip] >> Still, eix confirmed there were quite a lot of kde packages which have >> newer versions, and indeed, >> emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) >> upgraded 24 packages. >> >> Where does this discrepancy come from? > > I think Portage does not consider packages that are not in your world > file, if the update is on world (or system). > > To overcome this, I wrote a little script, called update_orphans.sh. > Here it is: > > <-------cut-----------> update_orphans.sh<----------cut-------------> > #!/bin/sh > > eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD > > exit $? > <-------cut-----------><--------cut------><----------cut-------------> > > I run it immediately after the main emerge, when I have rsync'ed the > Portage tree. No. --with-bdeps is not default anymore because it is considered to be a bug if portage updates packages not used in any way. This is only if a package is needed for buildtime. Program A is version 1.5. To build it, it needs program B which at this time is version 4.7 B is not needed for anything else! Now there is an update to B-4.9 . Portage will not update B as long as there is no update to A. B is not in the world file. It is not a runtime dependency nore is it a orphan. kh