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 1NOpcE-0000Wm-32 for garchives@archives.gentoo.org; Sun, 27 Dec 2009 09:40:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 52F6FE07D5; Sun, 27 Dec 2009 09:39:36 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id 0E86BE07D5 for ; Sun, 27 Dec 2009 09:39:36 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NOpb3-0003bi-WE for gentoo-amd64@lists.gentoo.org; Sun, 27 Dec 2009 10:39:34 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 27 Dec 2009 10:39:33 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 27 Dec 2009 10:39:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Updates other than the masked one Date: Sun, 27 Dec 2009 09:39:11 +0000 (UTC) Message-ID: References: <40bb8d3b0912262345v5449b9b9p4db2ff8f1e894335@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b2e69848-4b09-4c9d-a15c-5f5588ab7861 X-Archives-Hash: 96ec0762e0720b257fcb4dea510c2087 Martin Herrman posted on Sun, 27 Dec 2009 08:45:50 +0100 as excerpted: > All, >=20 > since about a week or so, the kdebase-runtime-meta package is masked, > see below. I'm quite sure that in the mean time other packages have bee= n > updated as well. How can I install these other updates to prevent that > eventually I have to update a bunch of packages that takes me several > hours to compile? (of course, without allowing the masked package to be > installed..) >=20 > Thanx, >=20 > Martin >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D >=20 > martindesktop ~ # emerge --update --deep --newuse --pretend world >=20 > These are the packages that would be merged, in order: >=20 > Calculating dependencies... done! >=20 > !!! All ebuilds that could satisfy > ">=3Dkde-base/kdebase-runtime-meta-4.3.4[-kdeprefix,semantic- desktop,handbook]" > have been masked. > !!! One of the following masked packages is required to complete your > request: - kde-base/kdebase-runtime-meta-4.3.4-r1 (masked by: ~amd64 > keyword) >=20 > For more information, see the MASKED PACKAGES section in the emerge man > page or refer to the Gentoo Handbook. (dependency required by > "kde-base/kdelibs-4.3.4" [ebuild]) (dependency required by "world" > [argument]) >=20 > martindesktop ~ # Are you running standard amd64 keyword, or ~amd64? It appears from that,= =20 that you'd be running amd64 (stable), because it's ~amd64 masked. So which version of kde (or kdelibs if you only have a few kde packages,=20 not most/all of the software collection) is installed? According to the=20 changelog, kde-base/kdebase-runtime-meta was only introduced for kde=20 4.3.4, the package didn't exist earlier. But kde 4.3.4 is ~amd64=20 masked. So why is a package that never existed for previous versions now= =20 in your world file, or a dependency of something that is, if you're not=20 yet running the ~amd64 kde 4.3.4? If you're running stable amd64 normally, but have whatever parts of kde=20 4.3.4 you have installed in your package.keywords file, then you now need= =20 to add kde-base/kdebase-runtime-meta to it as well, as it's now required=20 by kdelibs 4.3.4 (because upstream requires it, see gentoo bug #295456). Bottom line, if you have (amd64 stable) kdelibs-4.3.3 installed, kdebase- runtime-meta shouldn't be being pulled in, unless you're trying to=20 upgrade whatever kde parts you have to 4.3.4. If you have=20 package.keyworded parts of kde 4.3.4 and have it installed, they you need= =20 to package.keyword kdebase-runtime-meta (and all the packages it pulls=20 in), because it's now a dependency. Either that, or downgrade back to=20 4.3.3 and remove the 4.3.4 package.keyword entries you already have, if=20 you aren't prepared to keyword runtime-meta and its dependencies as well. --- Alternatively, and directly answering your question, tho it won't be=20 supported and may not work so well, to get a list of @world upgrades, you= =20 can (temporarily) add kdebase-runtime-meta (and its dependencies) to your= =20 package.keywords, then do an emerge --pretend --update, and get a list. =20 You can then update (emerge --oneshot package, so it doesn't put extra=20 entries in your world file) the ones you want from that list,=20 individually. When you are done updating what you want, you can remove=20 the temporary package.keywords, so they're masked again. But rather than that, I'd seriously recommend either downgrading to 4.3.3= =20 if you want to stick with stable, or keywording the rest of your kde=20 4.3.4 dependencies so all of kde is ~arch and sticking with 4.3.4. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman