[gentoo-user] Up-/Down-grade of KDE
Yesterday my ~x86 Gentoo box got KDE upgraded to 4.5.1 and today portage want to downgrade it again to 4.4.5 and I can not figure out why. My emerge --update --deep --verbose --reinstall changed-use world --pretend gives a lot of output for KDE-components like this: ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua) (-kdeprefix) 0 kB [uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix) [blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base/kdebase- meta:4.5[-kdeprefix] is blocking kde-base/kdebase-meta-4.4.5) [blocks b ] kde-base/kdebase-meta:4.4[-kdeprefix] (kde-base/kdebase- meta:4.4[-kdeprefix] is blocking kde-base/kdebase-meta-4.5.1) Any suggestion on what I have screwed up? -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] Up-/Down-grade of KDE
On Sunday 12 September 2010 12.11:14 Dan Johansson wrote: Yesterday my ~x86 Gentoo box got KDE upgraded to 4.5.1 and today portage want to downgrade it again to 4.4.5 and I can not figure out why. My emerge --update --deep --verbose --reinstall changed-use world --pretend gives a lot of output for KDE-components like this: ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua) (-kdeprefix) 0 kB [uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix) [blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base/kdebase- meta:4.5[-kdeprefix] is blocking kde-base/kdebase-meta-4.4.5) [blocks b ] kde-base/kdebase-meta:4.4[-kdeprefix] (kde-base/kdebase- meta:4.4[-kdeprefix] is blocking kde-base/kdebase-meta-4.5.1) Any suggestion on what I have screwed up? OK, I found Bug 336158 (http://bugs.gentoo.org/show_bug.cgi?id=336158). Sorry for the noise. -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] Up-/Down-grade of KDE
Dan Johansson dan.johans...@dmj.nu writes: On Sunday 12 September 2010 12.11:14 Dan Johansson wrote: Yesterday my ~x86 Gentoo box got KDE upgraded to 4.5.1 and today portage want to downgrade it again to 4.4.5 and I can not figure out why. My emerge --update --deep --verbose --reinstall changed-use world --pretend gives a lot of output for KDE-components like this: ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua) (-kdeprefix) 0 kB [uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix) [blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base/kdebase- meta:4.5[-kdeprefix] is blocking kde-base/kdebase-meta-4.4.5) [blocks b ] kde-base/kdebase-meta:4.4[-kdeprefix] (kde-base/kdebase- meta:4.4[-kdeprefix] is blocking kde-base/kdebase-meta-4.5.1) Any suggestion on what I have screwed up? OK, I found Bug 336158 (http://bugs.gentoo.org/show_bug.cgi?id=336158). Unfortunately that bug gives absolutely no indication as why it was re-masked.
[gentoo-user] Re: KDE password
econti wrote: So . . . I unmerged all the single app, unmerged kdebase-kioslaves and emerged kdebase. Now all works as before. Wait, I don't get it. You have the single, all-in-one kdebase package installed (which, to the best of my knowledge, includes all kdebase-* packages), yet you emerge kdebase-kioslaves? Why? With KDE, either you go for the all-in-one-big-honking-package approach (kdebase proper), or you cherry pick what you need from the split packages (the kdebase-* packages). Same goes for the other kde core packages. If you want to switch from one big package to several small ones to save on recompiles for small updates, use kdebase-meta, which installs all of the kdebase split packages. Installing both the big kdebase package and the split packages makes no sense, IIRC. Me, I have all kdebase-* packages installed, but not kdebase. Anno. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] kde-meta minus toys, games, etc
$ ls /usr/portage/kde-base/ | grep meta kdeaccessibility-meta kdeaddons-meta kdeadmin-meta kdeartwork-meta kdebase-meta kdebindings-meta kdeedu-meta kdegames-meta kdegraphics-meta kde-meta kdemultimedia-meta kdenetwork-meta kdepim-meta kdesdk-meta kdetoys-meta kdeutils-meta kdewebdev-meta On Saturday, 3 June 2006 6:13, Mick wrote: On 02/06/06, Raymond Lewis Rebbeck [EMAIL PROTECTED] wrote: They're the same as the monolithic packages but with -meta on the end. Easiest way to see what is in them: # emerge -pv foo-meta Thanks. Where's the complete list of available meta packages? -- Regards, Mick -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
Daniel D Jones wrote: Currently running KDE 3.3. I get the following: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khelpcenter-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcontrol-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebugdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksysguard-3.4.1-r1) And lots more, of course. Do I really have to uninstall 3.3 to install 3.4? It's saying that you need to unmerge =kde-base/kdebase-3.4* because that package is split into the other ones you see there. You can fool portage into thinking it's not installed with mv /var/db/pkg/kde-base/kdebase-3.4* /tmp but do so at your own risk. Zac -- gentoo-user@gentoo.org mailing list
[gentoo-user] Update blocked by kdebase-startkde:4
Attempting to update/world this weekend I get: # emerge -uDv @world These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" have been masked. !!! One of the following masked packages is required to complete your request: - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: package.mask, ~amd64 keyword) - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask) (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" [ebuild]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) I have all of KDE:5 masked since I think installing it sounds too risky. Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on kde- apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a solution to this? Thanks Robin -- -- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling -- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: [gentoo-user] KDM and portage
On Wed, 8 Feb 2006, Daniel D Jones wrote: Can someone either explain or give me a pointer to an explanation for the following: [EMAIL PROTECTED]:/ # emerge --pretend kdm These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kdm-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/libkonq-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kicker-3.5.1-r1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kdebase-data-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/khotkeys-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kdesu-3.5.0) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kcontrol-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/khelpcenter-3.5.1) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kcminit-3.5.0) [ebuild N] kde-base/libkonq-3.5.1 [ebuild N] kde-base/kdebase-data-3.5.1 [ebuild N] kde-base/kicker-3.5.1-r1 [ebuild N] kde-base/khotkeys-3.5.1 [ebuild N] kde-base/kdesu-3.5.0 [ebuild N] kde-base/khelpcenter-3.5.1 [ebuild N] kde-base/kcminit-3.5.0 [ebuild N] kde-base/kcontrol-3.5.1 [ebuild N] kde-base/kdm-3.5.1 Particularly, what does the 3.5* mean? [EMAIL PROTECTED]:/ # equery list kdebase [ Searching for package 'kdebase' in all categories among: ] * installed packages [I--] [ ] kde-base/kdebase-pam-6 (0) [I--] [ ] kde-base/kdebase-3.5.1-r1 (3.5) I have kdebase-3.5.1-r1 installed. Why is kdm-3.5.1 blocked? Surely kdebase is a requirement for kdm, and it makes no sense to say that kdm-3.5.1 needs an earlier version of kdebase, does it? I'm probably missing some fundamental understanding of what's going on here. Thanks for any assistance. You installed one of the meta packages instead of what's inside. While covienient for time, it sometimes makes it a pain to individually manage packages. My favorored way is emerge -pv kdebase-meta, then individually installing the things in there. kdm is a dependancy of kdesktop, so it should already be on there. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem emerging kde-meta
On Thursday 01 March 2007 18:06:47 Turi Tropea wrote: hi everyone, after a fresh installation of gentoo (using the minimal cd) i try to emerge kde-meta kde-i18n kdm but an error was occured, 41 package blocks the emerge there is the output of the emerge --pretend and package.keyword .use and .unmask. [blocks B ] =kde-base/kwin-3.5* (is blocking kde-base/kdebase-3.5.5-r3) Apparently you have monolithic kdebase installed while trying to install split kdebase-meta (contains kde-base/kdm and is a dependency of kde-meta). Just unmerge kdebase and you should be able to proceed... http://www.gentoo.org/doc/en/kde-split-ebuilds.xml -- Bo Andresen pgpc63vR36G4x.pgp Description: PGP signature
Re: [gentoo-user] Update blocked by kdebase-startkde:4
On Saturday 09 Jul 2016 20:52:46 Robin Atwood wrote:
> Attempting to update/world this weekend I get:
>
> # emerge -uDv @world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" have
> been masked.
> !!! One of the following masked packages is required to complete your
> request: - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by:
> package.mask, ~amd64 keyword)
> - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask)
>
> (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo"
> [ebuild])
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
>
> I have all of KDE:5 masked since I think installing it sounds too risky.
> Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on kde-
> apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a solution
> to this?
Yes, I got it too, even going straight to rsync.gentoo.org instead of my usual
UK mirror. I tried adding to package.mask:
>=kde-base/kdebase-startkde-4.11.22-r1
>=kde-base/kactivities-4.13.3-r2
but that only caused another failure because those package versions weren't
available.
I was hoping this was a part-update problem, in which the devs hadn't released
all the packages involved in whatever change they're making. I'm still
inclined to think that, because:
$ diff $(equery w =kde-base/kdebase-startkde-4.11.22-r1) $(equery w
=kde-base/kdebase-startkde-4.11.22)
12c12
< KEYWORDS="~amd64 ~arm ~x86 ~amd64-linux ~x86-linux"
---
> KEYWORDS="amd64 ~arm x86 ~amd64-linux ~x86-linux"
51d50
< "${FILESDIR}/${PN}-kwalletd-pam.patch"
$
...and that patch file has no mention of kde-apps/kdebase-runtime-meta:5.
This is an ~amd64 box, by the way, so I'm not affected by the change of
keyword in -r1.
--
Rgds
Peter
[gentoo-user] Upgrading KDE
Currently running KDE 3.3. I get the following: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khelpcenter-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcontrol-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebugdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksysguard-3.4.1-r1) And lots more, of course. Do I really have to uninstall 3.3 to install 3.4? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Best route forward?
Jesús Guerrero wrote: There are two kind of kde installs, or three, if you ask me. You can install kde. That will pull into your system the big packages just like they are released by the kde team. That means, several big monoliths, like kdebase, kdenetwork, kdegraphics and so on. You can install using split ebuilds as well. For example, instead of installing kdebase, you only need a couple of programs. So, you just install, let's say, konqueror and konsole, instead of kdebase. Of course, you can install all the pieces of kdebase using split ebuilds, and both installs would be equivalent. The downside is that you would need to install lots of small packages, instead of a big monolithic one. That way you save some space, but, what's more important for me, you save hours of compilation for things that you will never use. The other solution is to use meta-ebuilds. For example, you can install kdebase-meta, instead of kdebase. This is kind of an hybrid approach. When you emerge kdebase-meta, you end with the same that you would get by installing kdebase, but it will be done using split ebuilds. The good thing is that you will still get the modulatiry, without having to install all the split ebuilds by hand, because the meta-package pulls all of the components of kdebase but using split ebuilds as dependencies. So, you already know why you are getting that big list of packages to install: you are not going to get anything more if you install those packages, because they are a split version of the big kde packages you already installed. The blockers are simple to understand: you can't have kdebase and kdebase-meta installed at the same time. They are equivalent, it would be a nonsense anyway. So, all the components of a given meta- package, block the matching monolithic package. That way portage can prevent weird things like the one you were trying to do :) I hope it made sense, if not, ask for clarification. Regards. Could he just unmerge kdebase then emerge kdebase-meta? I don't mean to uninstall all the KDE stuff he has already compiled but just the little one that pulls in all the other packages. Dale :-) :-) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Update blocked by kdebase-startkde:4
On Sunday 10 Jul 2016 04:08:36 Michael Palimaka wrote: > On 09/07/16 23:52, Robin Atwood wrote: > > Attempting to update/world this weekend I get: > > > > > > > > > > > > # emerge -uDv @world > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > Calculating dependencies... done! > > > > > > > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" > > have been masked. > > > > !!! One of the following masked packages is required to complete your > > request: > > > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: > > package.mask, ~amd64 keyword) > > > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask) > > > > > > > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" > > [ebuild]) > > > > (dependency required by "@selected" [set]) > > > > (dependency required by "@world" [argument]) > > > > > > > > I have all of KDE:5 masked since I think installing it sounds too risky. > > Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on > > kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a > > solution to this? > > > > > > > > Thanks > > > > Robin > > Hi Robin, > > This change is correct - we're in the process of cleaning up some old > ebuilds at the moment. > > In this case kde-apps/kdebase-runtime-meta:5 doesn't imply anything > KF5-based - it has just been ported to use a newer eclass. It still just > pulls in the old KDE4-based kde-runtime packages. That's good news. Now, how does one allow that package to be installed while keeping the rest of KF5 masked? # cat /etc/portage/package.mask kde-plasma/* kde-frameworks/*:5 kde-apps/*:5 kde-misc/*:5 >=kde-apps/kde4-l10n-16.04.1 We seem to need an analogue of CONFIG_PROTECT and CONFIG_PROTECT_MASK, in which we could mask all kde-apps/*:5 while allowing kde-apps/kdebase-runtime- meta:5 to be installed. Can that be done? I hope there's an easier way than masking all 122 apps separately. -- Rgds Peter
Re: [gentoo-user] Installing KDE 3.4.1
Roy Wright wrote: First unmask the top level package, example: echo kde-base/kdebase-meta ~x86 /etc/portage/package.keywords Then just run this script, example: unmask.pl kdebase-meta You might want to save a copy of package.keywords then compare the two for sanity before emerging. Thanks! This does it. Have fun, Roy I will :) -- - Janne Vänttinen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Best route forward?
On Wed, 2 Jan 2008 13:40:11 -0800 (PST) BRM [EMAIL PROTECTED] wrote: I installed KDE yesterday via emerge kde -vuD, and just remembered today about kde-meta, which installs a lot more. In running emerge kde-meta -vuD, I get 250 new packages, and 245 blocks, with 1 upgrade. What is the _best_ path forward? Should I just stick with my current build of kde? Or is there an easy way to remove all the blocks and then push in kde-meta? Is it worth it? TIA, Ben -- [EMAIL PROTECTED] mailing list There are two kind of kde installs, or three, if you ask me. You can install kde. That will pull into your system the big packages just like they are released by the kde team. That means, several big monoliths, like kdebase, kdenetwork, kdegraphics and so on. You can install using split ebuilds as well. For example, instead of installing kdebase, you only need a couple of programs. So, you just install, let's say, konqueror and konsole, instead of kdebase. Of course, you can install all the pieces of kdebase using split ebuilds, and both installs would be equivalent. The downside is that you would need to install lots of small packages, instead of a big monolithic one. That way you save some space, but, what's more important for me, you save hours of compilation for things that you will never use. The other solution is to use meta-ebuilds. For example, you can install kdebase-meta, instead of kdebase. This is kind of an hybrid approach. When you emerge kdebase-meta, you end with the same that you would get by installing kdebase, but it will be done using split ebuilds. The good thing is that you will still get the modulatiry, without having to install all the split ebuilds by hand, because the meta-package pulls all of the components of kdebase but using split ebuilds as dependencies. So, you already know why you are getting that big list of packages to install: you are not going to get anything more if you install those packages, because they are a split version of the big kde packages you already installed. The blockers are simple to understand: you can't have kdebase and kdebase-meta installed at the same time. They are equivalent, it would be a nonsense anyway. So, all the components of a given meta- package, block the matching monolithic package. That way portage can prevent weird things like the one you were trying to do :) I hope it made sense, if not, ask for clarification. Regards. -- Jesús Guerrero [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] pam fixed now it's tcpdump
On Thursday 31 January 2008, maxim wexler wrote: --- Alan McKinnon [EMAIL PROTECTED] wrote: startkde is not in your $PATH. It's normal location is /usr/kde/3.5/bin/startkde Either use an explicit full path to the binary or update your PATH Actually, startkde doe not exist on my machine. Probably cause I'm in the midst of upgrading kde via -uD world and having a rough time of it ;( It's installed by kdebase-startkde I you use the -meta kde packages, get it by emerging kdebase-meta (I can't think of a reason why anyone wouldn't want all of kdebase so there's no need to emerge startkde explicitly) If you use the monolithic kde packages then emerge kdebase. If you want all of kde, then emerge kdebase or kdebase-meta as appropriate and when it's done, startkde will be present -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] seg fault emerging abiword
On Wednesday 30 May 2007 20:01:43 Bo Ørsted Andresen wrote: [...] By the way I installed kdebase-meta I believe [...] [SNIP] And why are you installing either of those at all when they have already been pulled in by kde-meta? Heh, I somehow read kdebase-meta as kde-meta... Disregard that question then.. -- Bo Andresen signature.asc Description: This is a digitally signed message part.
[gentoo-user] self-referential blocks...
I am ready to update my system and a problem has crept up that I thought I'd solved previously. When I do an emerge -Duva world, I get kdebase is blocking konsole and then later down the list I have konsole is blocking kdebase. I understand that kde-base/kdebase is a monolithic package and I actually only want individual packages on my system, so I didn't install it. However, something is now trying to pull it in. eix -e of kdebase and kde shows that neither is installed (not the monolithic nor the meta package). equery depends kdebase lists: app-cdr/k3b-0.12.4a kde-base/kdm-3.4.1 kde-base/kcheckpass-3.4.1 kde-base/kdebase-meta-3.4.1 but emerge -Duvp k3b kdm kcheckpass kdebase-meta doesn't show the blockage problem. emerge -tuvp world shows that kdegames is the culprit, but it is installed now and doesn't have kde-base. Should I remove kdegames and put in kdegames-meta instead? What is the difference between kde, kdebase, and kdebase-meta? All three have version 3.5.0, so it's apparent that none supercede the others... Thanks! -- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Best route forward?
--- Jesús Guerrero [EMAIL PROTECTED] wrote: On Wed, 2 Jan 2008 13:40:11 -0800 (PST) BRM [EMAIL PROTECTED] wrote: What is the _best_ path forward? Should I just stick with my current build of kde? Or is there an easy way to remove all the blocks and then push in kde-meta? Is it worth it? There are two kind of kde installs, or three, if you ask me. You can install kde. That will pull into your system the big packages just like they are released by the kde team. That means, several big monoliths, like kdebase, kdenetwork, kdegraphics and so on. You can install using split ebuilds as well. For example, instead of installing kdebase, you only need a couple of programs. So, you just install, let's say, konqueror and konsole, instead of kdebase. Of course, you can install all the pieces of kdebase using split ebuilds, and both installs would be equivalent. The downside is that you would need to install lots of small packages, instead of a big monolithic one. That way you save some space, but, what's more important for me, you save hours of compilation for things that you will never use. The other solution is to use meta-ebuilds. For example, you can install kdebase-meta, instead of kdebase. This is kind of an hybrid approach. When you emerge kdebase-meta, you end with the same that you would get by installing kdebase, but it will be done using split ebuilds. The good thing is that you will still get the modulatiry, without having to install all the split ebuilds by hand, because the meta-package pulls all of the components of kdebase but using split ebuilds as dependencies. So, you already know why you are getting that big list of packages to install: you are not going to get anything more if you install those packages, because they are a split version of the big kde packages you already installed. The blockers are simple to understand: you can't have kdebase and kdebase-meta installed at the same time. They are equivalent, it would be a nonsense anyway. So, all the components of a given meta- package, block the matching monolithic package. That way portage can prevent weird things like the one you were trying to do :) I hope it made sense, if not, ask for clarification. Thanks, and yes it does. I haven't vested much in the install yet, and the more modular approach seems nicer to me, so I think I'll switch it over now before its too costly. Thanks! Ben -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: depclean wants to wipe out KDE3
Nikos Chantziaras wrote:
Willie Wong wrote:
On Mon, Dec 22, 2008 at 02:18:27AM +0200, Penguin Lover Nikos
Chantziaras squawked:
Nikos Chantziaras wrote:
kde-base/kate
kde-base/kdebase-startkde
kde-base/ksmserver
These were dependencies and therefore were not in my world file.
If they get unmerge, things will break. KDevelop will break
without Kate, and KDE 3.5 itself will break without the other two. :P
OK, now I'm really curious; turns out they are NOT dependencies :P
I just checked with equery and nothing depends on them. Is that
normal? I mean, startkde for example is crucial to even start KDE 3
and it's not a dependency?
Hum, that is bizarre. I just tried emerge -pvt kde-meta, and it shows
that kde-meta depends on kdebase-meta depends on kdebase-startkde
(all version 3.5.9)
Checking all the ebuilds currently in the tree (versions 3.5.9,
3.5.10, 4.1.2 and 4.1.3), shows that all versions of kdebase-meta
depend on their corresponding versions of kdebase-startkde (they all
contain the line
=kde-base/kdebase-startkde-${PV}:${SLOT}
which picks the right slot). So something is probably broken on your
system. Check the contents of the various ebuilds for the versions you
installed to see what's wrong.
I'm not using -meta packages. Many packages they pulled in was stuff
I don't wanted (like PIM). I emerged KDE packages one-by-one and went
with what got pulled in as dependencies.
If he is going to use KDE as his GUI, doesn't he need to start with at
least kdebase then add onto that? On my system, kdebase brings in
startkde. If he emerges that and it gets added to the world file, would
that help with the current problem?
I only use KDE here but from what I have read you can install Konqueror
and still use some other GUI without KDE being installed and possibly no
startkde. Could this be confusing portage into thinking he is doing
this? Maybe?
Dale
:-) :-)
[gentoo-user] Re: Update blocked by kdebase-startkde:4
On 09/07/16 23:52, Robin Atwood wrote: > Attempting to update/world this weekend I get: > > > > > > # emerge -uDv @world > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" > have been masked. > > !!! One of the following masked packages is required to complete your > request: > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: > package.mask, ~amd64 keyword) > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask) > > > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" > [ebuild]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > > > > I have all of KDE:5 masked since I think installing it sounds too risky. > Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on > kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a > solution to this? > > > > Thanks > > Robin Hi Robin, This change is correct - we're in the process of cleaning up some old ebuilds at the moment. In this case kde-apps/kdebase-runtime-meta:5 doesn't imply anything KF5-based - it has just been ported to use a newer eclass. It still just pulls in the old KDE4-based kde-runtime packages. Kind regards, Michael
[gentoo-user] KDE 4.0.0
Hi folks, after the painful and time-consuming creation of /etc/portage/package.unmask for KDE 4, emerge --pretend --verbose =kde-base/kde-meta-4.0.0 tells me: [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I cannot unemerge 3.5.7. How can I work around this? Uwe -- If a man speaks in a forest, and no woman listens to him, is he still lying? -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] KDE 4 Blocked packages
On Tue, 22 Jan 2008 19:22:57 -0500 sean [EMAIL PROTECTED] wrote: Trying to emerge KDE 4 and have the following packages blocked. [...snip...] I feel like I am missing something obvious. Is anyone able to shed some light? Thanks Sean You have both monolithic and split packages installed (kdebase is monolithic, whereas phonon and such are split). You can either install kdebase-meta instead or uninstall the split blockers (installing kdebase will replace them). Brian signature.asc Description: PGP signature
Re: [gentoo-user] seg fault emerging abiword
On Wednesday 30 May 2007 19:26, Bo Ørsted Andresen wrote:
On Wednesday 30 May 2007 21:16:18 Mat Harris wrote:
Don't use --nodeps. That would just make a mess out of [your] system.
If you've installed split kde (kde-meta) then why are you trying to
install monolithic kde packages? I.e. why are you trying to install
kdebase rather than kdebase-meta and kdepim rather than kdepim-meta?
And why are you installing either of those at all when they have
already been pulled in by kde-meta?
http://www.gentoo.org/doc/en/kde-split-ebuilds.xml
Aah ok well the howto i found on google didn't mention anything about
using meta packages for the apps once i had the base installed. This
could explain why I have spent the last week compiling stuff for kde ;)
Well, you only need meta packages if you want to install everything that
ships together upstream. You could just emerge the split packages you want
such as e.g. konqueror, kcontrol, etc..
Ok i'll probably re-install unless there's some easy way to clean up.
There certainly is an easier way than reinstalling for this issue. What
you've posted thus far actually suggests that you haven't made a mess out
of your system yet as it showed kdepim and kdebase as not yet installed. In
that case you just need to stop trying to install monolithic packages.
I have stopped as soon as I read that last email :)
Otherwise you need to unmerge the monolithic packages you've installed
with --nodeps and remerge the split packages that they've overwritten. Code
Listing 3.1 in the above document shows you how to get the name of the
packages any monolithic package would overwrite.
I am don't seem to have installed many monlithic packages, mainly just trying
to do kdepim, i did have kdegames but i've got rid of that.
So from now on I should always install a package with -meta if its from kde
(providing one is available eg. kdevelop)?
E.g. if you've emerged kdebase-meta and kdebase at the same time and you
want to stick with split packages you can do this:
# emerge -Cva kdebase
# function die() { echo $@; }
# source $(portageq portdir)/eclass/kde-functions.eclass
# emerge --oneshot -va $(get-child-packages kde-base/kdebase)
I don't have kdebase, just kdebase-meta. But i've spent a while compiling kde
stuff. I will keep checking for others.
Thanks
Mat Harris
pgpuCSD0L7Hs2.pgp
Description: PGP signature
Re: [gentoo-user] problem emerging kde-meta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bo Ørsted Andresen ha scritto: Apparently you have monolithic kdebase installed while trying to install split kdebase-meta (contains kde-base/kdm and is a dependency of kde-meta). Just unmerge kdebase and you should be able to proceed... http://www.gentoo.org/doc/en/kde-split-ebuilds.xml the kde related packages was installed by beryl and aquamarine...so if i unmerge them can i cause that beryl does not work? or how i can have a functional kde environment using the monolithic ebuild? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5x69pidk8BrvGZARAq+rAKDPmNJFeKXsMvkPLN9xQRvMiGrVjQCgr1q+ D1jYJ3vaWI9gY/bdDTehXeY= =ALfi -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Issues with Dependencies
localhost ~ # emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-kioslaves-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kdegraphics-kfile-plugins-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kgamma-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kmrml-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kpdf-3.4.3-r4) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kolourpaint-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kcoloredit-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/ksnapshot-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kghostview-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kiconedit-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/ksvg-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kfax-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kviewshell-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kuickshow-3.4.1) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kview-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kdvi-3.4.3) [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kruler-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kate-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khelpcenter-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcontrol-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.3-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebugdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kreadconfig-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/knetattach-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdepasswd-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kfind-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksysguard-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcheckpass-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksplashml-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/klipper-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksystraycmd-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kwin-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesktop-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kstart-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kxkb-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksmserver-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/nsplugins-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ktip-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdeprint-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdcop-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kpager-3.4.2) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kmenuedit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kpersonalizer-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-startkde-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/drkonqi-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/konqueror-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/konsole-3.4.3) No. Still doesn't like me. I never know about the meta packages, so I could be on Gnome for a little while until I get this sorted out, huh? On 3/31/06, Bo Andresen [EMAIL PROTECTED] wrote: On Saturday 01 April 2006 01:52, Lord Sauron wrote: Hi, I'm having a bit more trouble. I'm trying to re-compile KDE so that maybe some functionality which didn't compile right the first time will work. However, it says I've got some broken dependencies
Re: [gentoo-user] Still kde problems with monolithic-split
On Sunday 05 October 2008 10:10:33 [EMAIL PROTECTED] wrote: solfire:/rootemerge kde-meta Calculating dependencies -!!! Digest verification failed: !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4061 !!! Expected: 4064 ... done! Verifying ebuild Manifests... !!! Digest verification failed: !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4061 !!! Expected: 4064 Run 'emerge --sync' again You got a woopsie! copy on the last try -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: Do we have to build gcc with fortran now?
On Thursday 23 June 2011 13:09:53 Neil Bothwick did opine thusly: On Thu, 23 Jun 2011 05:49:45 -0500, Dale wrote: My question was why are you installing cantor if you don't need it? Oh, I see. It was pulled in by kde-meta. I know I can have KDE other ways but it is much easier to emerge kde-meta than to emerge some huge amount of packages . If you consider spending a couple of days farting around with fortran to be much easier... :P I use sets for this. I want KDE but not all of it, so I have a set with just the -meta packages I want: $ cat /etc/portage/sets/alan-kde kde-base/kdeadmin-meta kde-base/kdeartwork-meta kde-base/kdebase-meta kde-base/kdebase-runtime-meta kde-base/kdegraphics-meta kde-base/kdemultimedia-meta kde-base/kdenetwork-meta kde-base/kdepim-meta kde-base/kdeutils-meta -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] problem emerging kde-meta
On Thursday 01 March 2007, Turi Tropea [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] problem emerging kde-meta': Bo Ørsted Andresen ha scritto: Just unmerge kdebase and you should be able to proceed... the kde related packages was installed by beryl and aquamarine...so if i unmerge them can i cause that beryl does not work? or how i can have a functional kde environment using the monolithic ebuild? Monolithic or split ebuilds provide a functional kde environment and split ebuilds are the new hotness that should, at least IMO, be used by default. When (e.g.) all the split ebuilds pulled in by kdebase-meta are installed you have the same functionality as installing kdebase; so if beryl (or others) have a hard dependency on a monolithic package that package is broken and need to be fixed to work with the split ebuilds. (Changing the 'kde-base/kdebase' atom to '|| ( kde-base/kdebase-meta kdebase/kdebase)' is a start...) Your problem is that you are trying to mix them. That is difficult or impossible and is AFAIK not supported. Either remove all your monolithic packages and install the split equivalents (the -meta packages help here) or remove all your split packages and install all the monolithic packages you need. It's possible you may need to run revdep-rebuild (from the gentoolkit package) and/or reinstall keryl after you fix your kde issues for it to work. -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/ New GPG Key! Old key expires 2007-03-25. Upgrade NOW! pgp7zPu8Ji8OH.pgp Description: PGP signature
Re: [gentoo-user] is kde 3.5 stable enough?
On 2/14/06, Ryan Holt [EMAIL PROTECTED] wrote: If I were to setup a KDE 3.5 environment, what packages aside from kde-base should I setup with the ~amd64 exception in my /etc/portage/package.keywords ? ACCEPT_KEYWORDS=~amd64 emerge -pv kde-base/kdebase-meta I highly recommend using the -meta builds for kdebase, and emerging whatever other KDE applications you want, rather than using the monolithic packages. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] KDE 3.4 - where is plastik?
Robert S wrote: I have just installed kde3.4 using split ebuilds. I installed the kdebase-meta package and the kdebase-startkde and kdegraphics-meta ebuilds, but I only get a choice of about 5 grotty styles CDE default). My favorite plastik is gone! Can anybody help me remedy this? I've experienced the same problem with qt-3.3.4-r4 and qt-3.3.4-r5 (some styles missing when I run qtconfig). No problems with stable qt-3.3.4-r3 though. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] KDE 4 Blocked packages
Brian Marshall wrote: On Tue, 22 Jan 2008 19:22:57 -0500 sean [EMAIL PROTECTED] wrote: Trying to emerge KDE 4 and have the following packages blocked. [...snip...] I feel like I am missing something obvious. Is anyone able to shed some light? Thanks Sean You have both monolithic and split packages installed (kdebase is monolithic, whereas phonon and such are split). You can either install kdebase-meta instead or uninstall the split blockers (installing kdebase will replace them). Brian Thanks Brian and Ken. Knew it was something simple but just having a brain skip. Started kde-meta. Sean -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Update blocked by kdebase-startkde:4
On Tuesday 12 July 2016, Andrés Becerra Sandoval wrote: > 2016-07-09 8:52 GMT-05:00 Robin Atwood <ro...@binro.org>: > > Attempting to update/world this weekend I get: > > > > > > > > > > > > # emerge -uDv @world > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > Calculating dependencies... done! > > > > > > > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" have > > been masked. > > > > !!! One of the following masked packages is required to complete your > > request: > > > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: package.mask, > > ~amd64 keyword) > > > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask) > > > > > > > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" > > [ebuild]) > > > > (dependency required by "@selected" [set]) > > > > (dependency required by "@world" [argument]) > > > > > > > > I have all of KDE:5 masked since I think installing it sounds too risky. > > Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on > > kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a > > solution to this? > > Robin, > > My ugly hack on this to keep on kde4 withouth pulling frameworks 5: > > 1) use a local overlay > 2) locate kactivitymanagerd-4.13.3-r1.ebuild (in > /var/db/pkg/kde-plasma/kactivitymanagerd-4.13.3-r1) > 3) put the kactivitymanagerd-4.13.3-r1.ebuild into > /usr/local/portage/kde-plasma/kactivitymanagerd/ > 4) add a > SLOT="5" > line to the ebuild > 5) add a unmask line > =kde-plasma/kactivitymanagerd-4.13.3-r1 > to /etc/package.unmask > > I need 5) because I mask all kde-plasma/* packages Andrés- That did the trick! Thanks very much. Until the next time... :( Cheers Robin -- -- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling -- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: [gentoo-user] Update blocked by kdebase-startkde:4
2016-07-09 8:52 GMT-05:00 Robin Atwood <ro...@binro.org>: > Attempting to update/world this weekend I get: > > > > > > # emerge -uDv @world > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" have > been masked. > > !!! One of the following masked packages is required to complete your > request: > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: package.mask, > ~amd64 keyword) > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: package.mask) > > > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" > [ebuild]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > > > > I have all of KDE:5 masked since I think installing it sounds too risky. > Checking the kdebase-startkde-4.11.22-r1 ebuild it has a dependency on > kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has anyone found a > solution to this? > > > > Thanks > > Robin > > -- > > -- > > Robin Atwood. > > > > "Ship me somewheres east of Suez, where the best is like the worst, > > Where there ain't no Ten Commandments an' a man can raise a thirst" > > from "Mandalay" by Rudyard Kipling > > -- > > Robin, My ugly hack on this to keep on kde4 withouth pulling frameworks 5: 1) use a local overlay 2) locate kactivitymanagerd-4.13.3-r1.ebuild (in /var/db/pkg/kde-plasma/kactivitymanagerd-4.13.3-r1) 3) put the kactivitymanagerd-4.13.3-r1.ebuild into /usr/local/portage/kde-plasma/kactivitymanagerd/ 4) add a SLOT="5" line to the ebuild 5) add a unmask line =kde-plasma/kactivitymanagerd-4.13.3-r1 to /etc/package.unmask I need 5) because I mask all kde-plasma/* packages -- Andrés Becerra Sandoval
[gentoo-user] Re: depclean wants to wipe out KDE3
Willie Wong wrote:
On Mon, Dec 22, 2008 at 02:18:27AM +0200, Penguin Lover Nikos Chantziaras
squawked:
Nikos Chantziaras wrote:
kde-base/kate
kde-base/kdebase-startkde
kde-base/ksmserver
These were dependencies and therefore were not in my world file. If they
get unmerge, things will break. KDevelop will break without Kate, and KDE
3.5 itself will break without the other two. :P
OK, now I'm really curious; turns out they are NOT dependencies :P I just
checked with equery and nothing depends on them. Is that normal? I mean,
startkde for example is crucial to even start KDE 3 and it's not a
dependency?
Hum, that is bizarre. I just tried emerge -pvt kde-meta, and it shows
that kde-meta depends on kdebase-meta depends on kdebase-startkde
(all version 3.5.9)
Checking all the ebuilds currently in the tree (versions 3.5.9,
3.5.10, 4.1.2 and 4.1.3), shows that all versions of kdebase-meta
depend on their corresponding versions of kdebase-startkde (they all
contain the line
=kde-base/kdebase-startkde-${PV}:${SLOT}
which picks the right slot). So something is probably broken on your
system. Check the contents of the various ebuilds for the versions you
installed to see what's wrong.
I'm not using -meta packages. Many packages they pulled in was stuff I
don't wanted (like PIM). I emerged KDE packages one-by-one and went
with what got pulled in as dependencies.
Re: [gentoo-user] KDE 4.2 and 3.5
On Sun, 01 Feb 2009 12:41:35 -0600, Dale wrote: emerge -C kde emerge --depclean -a emerge -av kde-meta That's what I was afraid of. Sigh. Thanks. Could he just emerge -C kde then re-emerge whatever he wanted without having to reinstall all of KDE? Isn't packages like Konqueror just a dependency pulled in by the original emerge kde? No,because he's installed from the monolithic builds. He might just get away with emerge -C kde kdebase emerge -1av kdebase-meta Then repeat for each of the other meta packages, finally emerging kde-meta which will keep world correct. -- Neil Bothwick Random access is the optimum of the mass storages. signature.asc Description: PGP signature
[gentoo-user] kde-base/kdebugdialog-3.5.2 emerge error
Hi, I am trying to upgrade to kde 3.5.2 specifically because my current KDE was installed with emerge kde-meta I have added the appropriate dependencies to /etc/portage/package.keywords kde-base/arts ~x86 kde-base/kdelibs ~x86 kde-base/ksysguard ~x86 kde-base/kdebase-meta ~x86 kde-base/kde-meta ~x86 However I end up with the following error emerge: there are no ebuilds to satisfy ~kde-base/kdebugdialog-3.5.2.(dependency required by kde-base/kdebase-meta-3.5.2 [ebuild]) Which the protage database says that the most recent version is 3.5.0 Anyway to fix this? -- Pete Pardoe
Re: [gentoo-user] kde-meta minus toys, games, etc
On Fri, 2 Jun 2006 21:11:52 +, Mick wrote: Is emerging kdebase-meta meant to pull in 45 packages, or are there any old kde apps in my system pulling them in as I am trying to emerge my new split KDE? Something like that number. From the log: === 1149285323: *** emerge --update --deep --verbose kdebase-meta 1149285332: emerge (1 of 45) kde-base/kdelibs-3.5.2-r6 to / 1149285332: === (1 of 45) Cleaning Try emerge --ask --tree --verbose kde-meta to see what is pulling in the packages. -- Neil Bothwick Is it possible to be totally partial? signature.asc Description: PGP signature
Re: [gentoo-user] seg fault emerging abiword
On Wednesday 30 May 2007 21:16:18 Mat Harris wrote:
Don't use --nodeps. That would just make a mess out of [your] system. If
you've installed split kde (kde-meta) then why are you trying to install
monolithic kde packages? I.e. why are you trying to install kdebase
rather than kdebase-meta and kdepim rather than kdepim-meta? And why are
you installing either of those at all when they have already been pulled
in by kde-meta?
http://www.gentoo.org/doc/en/kde-split-ebuilds.xml
Aah ok well the howto i found on google didn't mention anything about using
meta packages for the apps once i had the base installed. This could
explain why I have spent the last week compiling stuff for kde ;)
Well, you only need meta packages if you want to install everything that ships
together upstream. You could just emerge the split packages you want such as
e.g. konqueror, kcontrol, etc..
Ok i'll probably re-install unless there's some easy way to clean up.
There certainly is an easier way than reinstalling for this issue. What you've
posted thus far actually suggests that you haven't made a mess out of your
system yet as it showed kdepim and kdebase as not yet installed. In that case
you just need to stop trying to install monolithic packages.
Otherwise you need to unmerge the monolithic packages you've installed
with --nodeps and remerge the split packages that they've overwritten. Code
Listing 3.1 in the above document shows you how to get the name of the
packages any monolithic package would overwrite.
E.g. if you've emerged kdebase-meta and kdebase at the same time and you want
to stick with split packages you can do this:
# emerge -Cva kdebase
# function die() { echo $@; }
# source $(portageq portdir)/eclass/kde-functions.eclass
# emerge --oneshot -va $(get-child-packages kde-base/kdebase)
--
Bo Andresen
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: depclean wants to wipe out KDE3
On Mon, Dec 22, 2008 at 02:18:27AM +0200, Penguin Lover Nikos Chantziaras
squawked:
Nikos Chantziaras wrote:
kde-base/kate
kde-base/kdebase-startkde
kde-base/ksmserver
These were dependencies and therefore were not in my world file. If they
get unmerge, things will break. KDevelop will break without Kate, and KDE
3.5 itself will break without the other two. :P
OK, now I'm really curious; turns out they are NOT dependencies :P I just
checked with equery and nothing depends on them. Is that normal? I mean,
startkde for example is crucial to even start KDE 3 and it's not a
dependency?
Hum, that is bizarre. I just tried emerge -pvt kde-meta, and it shows
that kde-meta depends on kdebase-meta depends on kdebase-startkde
(all version 3.5.9)
Checking all the ebuilds currently in the tree (versions 3.5.9,
3.5.10, 4.1.2 and 4.1.3), shows that all versions of kdebase-meta
depend on their corresponding versions of kdebase-startkde (they all
contain the line
=kde-base/kdebase-startkde-${PV}:${SLOT}
which picks the right slot). So something is probably broken on your
system. Check the contents of the various ebuilds for the versions you
installed to see what's wrong.
W
--
For the relative problem is one in which the relative radius vectors...from
one to the other? So, actually, I was wrong. Kepler was right after all.
~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 745 days, 44 min
Re: [gentoo-user] seg fault emerging abiword
On Wednesday 30 May 2007 18:01, Bo Ørsted Andresen wrote: On Wednesday 30 May 2007 19:34:49 Mat Harris wrote: It appears I may have more of a problem than I thought. By the way I installed kdebase-meta I believe (as the kde howto suggested) but now when trying to install most kde apps I have to do --nodeps otherwise i get this: Calculating dependencies... done! [ebuild N ] kde-base/kdebase-3.5.5-r4 USE=arts cups opengl pam ssl -debug -hal -ieee1394 -java -kdeenablefinal -kdehiddenvisibility -ldap -lm_sensors -logitech-mouse -openexr -samba -xcomposite -xinerama -xscreensaver -zeroconf 0 kB [ebuild N ] kde-base/kdepim-3.5.5-r4 USE=arts crypt -debug -gnokii -kdeenablefinal -pda -xinerama 0 kB [blocks B ] =kde-base/kcheckpass-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [SNIP] =kde-base/libkdenetwork-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [SNIP] Don't use --nodeps. That would just make a mess out of just system. If you've installed split kde (kde-meta) then why are you trying to install monolithic kde packages? I.e. why are you trying to install kdebase rather than kdebase-meta and kdepim rather than kdepim-meta? And why are you installing either of those at all when they have already been pulled in by kde-meta? http://www.gentoo.org/doc/en/kde-split-ebuilds.xml Aah ok well the howto i found on google didn't mention anything about using meta packages for the apps once i had the base installed. This could explain why I have spent the last week compiling stuff for kde ;) Ok i'll probably re-install unless there's some easy way to clean up. Thanks Mat Harris pgpkZDJDHKFM4.pgp Description: PGP signature
Re: [gentoo-ppc-user] emerging kdebase-kioslaves
You are trying to emerge one of the packages in the modular build of KDE. You would first need to uninstall the monolithic buiild as it has the same packages but builds them at the same time. The monolithic build may be more stable once done, that is unclear, but the modular is easier to update. To install the modular kde use the kde-meta packages. You may want to wait on that until 3.5.x goes to stable, as it takes a long time. On Friday 05 May 2006 6:35 am, Mark Hart wrote: I am trying to emerge kdebase-kioslaves as per the instructions in HOWTO D-BUS, HAL, KDE media:/ When I try to emerge -pvt kdebase-kioslaves, I get the following: mac2 / # emerge -pvt kdebase-kioslaves These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-kioslaves-3.4.3) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdialog-3.4.1) [ebuild N] kde-base/kdebase-kioslaves-3.4.3 +arts -debug +hal -kdeenablefinal +ldap -openexr -samba -xinerama 0 kB [ebuild N] kde-base/kdialog-3.4.1 +arts -debug -kdeenablefinal -kdexdeltas -xinerama 21,907 kB Total size of downloads: 21,907 kB Being new to this, I don't know what to do next. Thanks! Mark M. Hart -- Kmail on Gentoo/PPC -- gentoo-ppc-user@gentoo.org mailing list
Re: [gentoo-user] seg fault emerging abiword
On Wednesday 30 May 2007 10:22, Benno Schulenberg wrote: Mat Harris wrote: My only little problem is that when I try to emerge AbiWord (2.4.5-r1), it compiles fine but when it tries to install to files into the real filesystem it segfaults like so: [...] /usr/share/AbiSuite-2.4/AbiWord/glade/ap_UnixDialog_Options.glade /usr/share/AbiSuite-2.4/AbiWord/glade/ap_UnixDialog_WordCount.glade /usr/share/AbiSuite-2.4/AbiWord/glade/ap_UnixDialog_Styles.glade Segmentation fault This is repeatable? That is, it happens every time at the same spot when you try to emerge abiword? If not, it sounds like an overheating problem. Also look in your syslog for disk errors. Yes it happens at the same place every time (I have tried to merge it about 3 times just now). Nothing appears in the logfiles to indicate any disc based problems. Otherwise, try removing /usr/share/AbiSuite-2.4 and then fsck'ing your file system before attempting a merge again. And check there is enough space left on the device. I was about to try that then I found that kdepim which I left last night to compile has seg faulted too but not in the same place: i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../libkcal -I../libemailfunctions -I.. -I../libkdepim -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i686 -pipe -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o konsolekalendarvariables.o konsolekalendarvariables.cpp i686-pc-linux-gnu-g++: Internal error: Segmentation fault (program cc1plus) Please submit a full bug report. See URL:http://bugs.gentoo.org/ for instructions. make[3]: *** [konsolekalendardelete.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: Leaving directory `/var/tmp/portage/kde-base/kdepim-3.5.5-r4/work/kdepim-3.5.5/konsolekalendar' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kde-base/kdepim-3.5.5-r4/work/kdepim-3.5.5/konsolekalendar' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kde-base/kdepim-3.5.5-r4/work/kdepim-3.5.5' make: *** [all] Error 2 It appears I may have more of a problem than I thought. By the way I installed kdebase-meta I believe (as the kde howto suggested) but now when trying to install most kde apps I have to do --nodeps otherwise i get this: Calculating dependencies... done! [ebuild N] kde-base/kdebase-3.5.5-r4 USE=arts cups opengl pam ssl -debug -hal -ieee1394 -java -kdeenablefinal -kdehiddenvisibility -ldap -lm_sensors -logitech-mouse -openexr -samba -xcomposite -xinerama -xscreensaver -zeroconf 0 kB [ebuild N] kde-base/kdepim-3.5.5-r4 USE=arts crypt -debug -gnokii -kdeenablefinal -pda -xinerama 0 kB [blocks B ] =kde-base/kcheckpass-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kwin-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/konqueror-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/ksmserver-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/ksysguard-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kicker-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/konsole-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/libkdenetwork-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/kontact-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/kcontrol-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/ksplashml-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kdepim-kioslaves-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/kreadconfig-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kxkb-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kdm-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kdesu-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/ktip-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/kappfinder-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/libkcal-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/mimelib-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/klipper-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/libkpgp-3.5* (is blocking kde-base/kdepim-3.5.5-r4) [blocks B ] =kde-base/kdebase-data-3.5* (is blocking kde-base/kdebase-3.5.5-r4) [blocks B ] =kde-base/ktnef-3.5* (is blocking kde-base/kdepim
Re: [gentoo-user] kde-meta minus toys, games, etc
On 6/2/06, Mick [EMAIL PROTECTED] wrote: Hi All, Apologies if this has been asked before. I uninstalled my monolithic KDE and am ready to install the split KDE ebuilds. I want to install everything except toys, games and educational packages. Since the DO_NOT_COMPILE is not meant to be used anymore, how would you suggest I go about it? -- Regards, Mick Install kdebase-meta, kdeutils-meta, kdeadmin-meta, etc. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Is there and Alternative to compiling kde?
On Sat, 10 Dec 2005 07:49:30 -0600, Harry Putnam wrote: When did I say meta... I was differentiating what you did say `kdebase' with the full blown kde-meta and noting I was somewhere in the middle with an emerge -v kde. kde-base/kde is a meta package, it pulls in all the monolithic KDE builds. If you are concerned about installation compile times, you should not be trying to build the whole of KDE. Do you really need all of kdegames, kdeedu and kdetoys to get your system running? Stick with kde-base/kdebase or kde-base/kdebase-meta, you can cancel your current emerge and merge one of these instead, then add the rest of what you want once the system is running. -- Neil Bothwick Joystick: (n.) a device essential for performing business tasks and training exercises esp. favored by pilots, tank commanders, riverboat gamblers, and medieval warlords. signature.asc Description: PGP signature
Re: [gentoo-user] Upgrading KDE
On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. -- Neil Bothwick This virus requires Microsoft Windows XP pgpZX7fhiEEdB.pgp Description: PGP signature
Re: [gentoo-user] Still kde problems with monolithic-split
Am Sonntag, 5. Oktober 2008 10:10:33 schrieb [EMAIL PROTECTED]: solfire:/rootemerge kde-meta Calculating dependencies -!!! Digest verification failed: !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4061 !!! Expected: 4064 ... done! Hmm, mine has a size of 4066, after this mornings sync. Try to re-sync your tree. Bye... Dirk
Re: [gentoo-user] Packages I like are blocking a package I don't want? (kdebase)
On 4/10/06, Daniel [EMAIL PROTECTED] wrote: I installed the kde meta-packages because I didn't want to be burdened with stuff I didn't need. Unfortunately, I had to add these packages to /etc/portage/packages.keywords in order to get them to install and everything was fine for about 2days. And then this happened: # emerge --pretend --update --deep world Add the --tree and --verbose options to see why portage wants to merge kdebase. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -u world won't update kde metapackages
* Robert Persson ([EMAIL PROTECTED]) wrote: I emerged kde 3.4 using the metapackages (kdebase-meta, kdeaddons-meta etc.). However I now find that emerge -u world fails to update any of the component try: emerge -uD world -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde-base/kdebugdialog-3.5.2 emerge error
On 4/9/06, Pete Pardoe [EMAIL PROTECTED] wrote: Richard The problem is that there is no ebuild for kde-base/kdebugdialog-3.5.2 it is not a ~x86 problem. Ah, sorry, I missed that. But the problem still remains that you need to add extra stuff to package.keywords. kdebase-meta-3.5.2 can actually depend on any version of kdebugdialog between 3.5.0 and 3.5.2. See this from the ebuild: $(deprange 3.5.0 $MAXKDEVER kde-base/kdebugdialog) kdebugdialog 3.5.0 is also ~x86, so again, you need to add kde-base/kdebugdialog to package.keywords in order to merge kde 3.5.2. As proof that I am not completely full of shit: carcharias kde-base # emerge -Duvp kdebase-meta These are the packages that would be merged, in order: Calculating dependencies | emerge: there are no ebuilds to satisfy ~kde-base/kdebugdialog-3.5.2. (dependency required by kde-base/kdebase-meta-3.5.2 [ebuild]) carcharias kde-base # echo kde-base/kdebugdialog ~x86 /etc/portage/package.keywords carcharias kde-base # emerge -Duvp kdebase-meta These are the packages that would be merged, in order: Calculating dependencies - !!! All ebuilds that could satisfy ~kde-base/libkonq-3.5.2 have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/libkonq-3.5.2 (masked by: ~x86 keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by kde-base/kdebase-meta-3.5.2 [ebuild]) Run the commands I gave you earlier, and you will allow the ~x86 keyword for all base KDE packages. Or you can continue to do them one at a time. Your choice. -Richard -- gentoo-user@gentoo.org mailing list
[gentoo-user] Packages I like are blocking a package I don't want? (kdebase)
I installed the kde meta-packages because I didn't want to be burdened with stuff I didn't need. Unfortunately, I had to add these packages to /etc/portage/packages.keywords in order to get them to install and everything was fine for about 2days. And then this happened: # emerge --pretend --update --deep world These are the packages that I would merge, in order: Calculating world dependencies ...done! [blocks B ] =kde-base/konsole-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/ksmserver-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/khelpcenter-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kmenuedit-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kicker-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kcontrol-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/ksysguard-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/nsplugins-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdebase-data-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/klipper-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/ksplashml-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdm-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kwin-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kcheckpass-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/konqueror-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdebase-kioslaves-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kate-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kfind-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdebase-startkde-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/khotkeys-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdesktop-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kpersonalizer-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kxkb-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kcminit-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdesu-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kdialog-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kstart-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/libkonq-3.5* (is blocking kde-base/kdebase-3.5.2) [blocks B ] =kde-base/kreadconfig-3.5* (is blocking kde-base/kdebase-3.5.2) [ebuild U ] sys-devel/binutils-config-1.8-r7 [1.8-r6] [ebuild U ] sys-apps/man-pages-2.28 [2.20] [ebuild U ] sys-apps/baselayout-1.11.14-r7 [1.11.14-r6] [ebuild U ] x11-libs/cairo-1.0.4 [1.0.2] [ebuild U ] kde-base/kdelibs-3.5.2-r2 [3.5.2] [ebuild U ] net-fs/samba-3.0.22 [3.0.21b] [ebuild U ] sys-apps/busybox-1.1.0 [1.00-r4] [ebuild U ] app-arch/tar-1.15.1-r1 [1.15.1] [ebuild U ] media-video/lsdvd-0.16 [0.15] [ebuild U ] sys-apps/hdparm-6.3 [5.9] [ebuild U ] sys-apps/kbd-1.12-r6 [1.12-r5] [ebuild NS ] media-libs/gstreamer-0.10.4 [ebuild U ] dev-libs/liboil-0.3.8 [0.3.6] [ebuild N] media-libs/gst-plugins-base-0.10.4-r1 [ebuild NS ] media-plugins/gst-plugins-alsa-0.10.4 [ebuild N] media-plugins/gst-plugins-xvideo-0.10.4-r1 [ebuild N] media-plugins/gst-plugins-x-0.10.4 [ebuild N] media-libs/libmp4v2-1.4.1 [ebuild N] dev-ruby/ruby-config-0.3.1 [ebuild N] dev-lang/ruby-1.8.4-r1 [ebuild N] media-libs/libgpod-0.3.0 [ebuild N] media-libs/faad2-2.0-r3 [ebuild U ] media-sound/amarok-1.4_beta3 [1.3.9] [ebuild U ] kde-base/kwin-3.5.2-r1 [3.5.2] [ebuild U ] kde-base/ksysguard-3.5.2-r1 [3.5.2] [ebuild U ] app-text/poppler-0.5.1-r1 [0.5.1] [ebuild N] kde-base/kdebase-3.5.2 [ebuild U ] app-text/poppler-bindings-0.5.1-r1 [0.5.1] [ebuild U ] sys-process/psmisc-22.1 [21.9] [ebuild U ] kde-base/konq-plugins-3.5.2-r1 [3.5.2] [ebuild U ] media-sound/sox-12.17.9 [12.17.7-r1] Can someone explain what's going on? -- We understand that you can't transform people who don't have internal drive and desire to create. But we also know it doesn't work to urge people to think outside the box without giving them the tools to climb out. - Laurie Dunnavant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: emerge -DuvatN world doesn't show all upgradeable packages
On Tuesday 08 April 2008, Michael Schmarck wrote: Alan McKinnon [EMAIL PROTECTED] wrote: The other option is to use the kde*meta ebuilds, which do directly depend on the sub-ordinate packages. This is what I do and I don't get the effect you observed. Thanks. I think I removed kde-meta, because it installs too much stuff, that I don't need (like kppp). It would be nice, if the kde-meta ebuild would be more like the gst-plugins-meta package, in that it sould allow the user to specify what he wants to get installed and what not. It shouldn't be an all or nothing approach, IMO. Michael [EMAIL PROTECTED] ~ $ ls -1d /var/portage/kde-base/*meta /var/portage/kde-base/kdeaccessibility-meta /var/portage/kde-base/kdeaddons-meta /var/portage/kde-base/kdeadmin-meta /var/portage/kde-base/kdeartwork-meta /var/portage/kde-base/kdebase-meta /var/portage/kde-base/kdebindings-meta /var/portage/kde-base/kdeedu-meta /var/portage/kde-base/kdegames-meta /var/portage/kde-base/kdegraphics-meta /var/portage/kde-base/kde-meta /var/portage/kde-base/kdemultimedia-meta /var/portage/kde-base/kdenetwork-meta /var/portage/kde-base/kdepim-meta /var/portage/kde-base/kdesdk-meta /var/portage/kde-base/kdetoys-meta /var/portage/kde-base/kdeutils-meta /var/portage/kde-base/kdewebdev-meta Use these instead of kde-meta. If you want only some stuff in one of those and not everything, omit the -meta, look inside it's ebuild and install the DEPENDS you do want. Same result as what you asked for, different means of achieving it. -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Re: Is there and Alternative to compiling kde?
Did you check out the Gentoo docs on kde split ebuilds? It has a lot of good info. I started to emerge with the kde and then decided to go with the meta so per the instructions I had to remove some stuff - it shows up as blocked. On Saturday 10 December 2005 11:31, Harry Putnam wrote: Neil Bothwick [EMAIL PROTECTED] writes: kde-base/kde is a meta package, it pulls in all the monolithic KDE builds. If you are concerned about installation compile times, you should not be trying to build the whole of KDE. Do you really need all of kdegames, kdeedu and kdetoys to get your system running? Stick with kde-base/kdebase or kde-base/kdebase-meta, you can cancel your current emerge and merge one of these instead, then add the rest of what you want once the system is running. I'm confused here. (even more..) Before starting the compile: I ran a comparision of `emerge -v -p kde' and emerge -v -p kde-meta The last showed a much larger pile of dependancies than the former. So I ran the former. I've now canceled as suggested and running `emerge kde-base/kdebase' It only showed the main kde-3.4X as dependancy. But with all the screwups I've managed to get these kde packages installed: (And don't need several of them) kde-base/kdegraphics-3.4.1-r1 * kde-base/kdelibs-3.4.1-r1 * kde-base/kdebase-pam-6 * kde-base/kde-env-3-r4 * kde-base/arts-3.4.1-r2 * kde-base/kdebase-3.4.1-r1 * kde-base/kdeartwork-3.4.1 * kde-base/kdepim-3.4.1-r2 * kde-base/kdegames-3.4.1 * kde-base/kdeutils-3.4.1 * kde-base/kdenetwork-3.4.1-r1 * kde-base/kdeedu-3.4.1-r1 * -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Best route forward?
On Mittwoch, 2. Januar 2008, BRM wrote: I installed KDE yesterday via emerge kde -vuD, and just remembered today about kde-meta, which installs a lot more. In running emerge kde-meta -vuD, I get 250 new packages, and 245 blocks, with 1 upgrade. What is the _best_ path forward? Should I just stick with my current build of kde? Or is there an easy way to remove all the blocks and then push in kde-meta? Is it worth it? TIA, Ben kde and kde-meta install the same apps. One is in monolith packages, the other one uses the split ebuilds. If you install everything, monolith is a lot faster. But some important useflags are only used and the features enabled with split ebuilds (g). Like kdenetworkkopete. With kdenetwork kopete emerges without the history plugin, even if all useflags are set (which sucks greatly). With split ebuilds, kopete gets its history plugin (there is no logic behind this - but the devs decided it this way...). You don't have to unmerge kde first. You can do it in a more 'gradual' way. For example: first unmerge kdenetwork, then emerge kdenetwork-meta. Unmerge kdebase, emerge kdebase-meta and so on. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] kde-meta minus toys, games, etc
On 02/06/06, Neil Bothwick [EMAIL PROTECTED] wrote: On Fri, 2 Jun 2006 19:46:07 +, Mick wrote: Apologies if this has been asked before. I uninstalled my monolithic KDE and am ready to install the split KDE ebuilds. I want to install everything except toys, games and educational packages. Install kdebase-meta, kdenetwork-meta, kdepim-meta etc. kde-meta is for those that want to install everything. Thanks for all the replies. What's the best way to find out what -meta packages exist and what they contain? -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Still kde problems with monolithic-split
solfire:/rootemerge kde-meta Calculating dependencies -!!! Digest verification failed: !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4061 !!! Expected: 4064 ... done! Verifying ebuild Manifests... !!! Digest verification failed: !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4061 !!! Expected: 4064 Dirk Heinrichs [EMAIL PROTECTED] [08-10-05 09:02]: Am Sonntag, 5. Oktober 2008 07:19:37 schrieb [EMAIL PROTECTED]: It getting more confused: This morning I did a [...] emerge -pv kde Now I am confused. Thought you wanted to install kde-meta??? still reports: Calculating dependencies... done! [ebuild N] kde-base/kdebase-3.5.9-r3 USE=branding cups hal ldap opengl pam -arts -debug -ieee1394 -java -joystick -kdeenablefinal -kdehiddenvisibility -lm_sensors -logitech-mouse -openexr -samba -xcomposite -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdemultimedia-3.5.9 USE=alsa encode gstreamer mp3 vorbis -akode -arts -audiofile -debug -flac -kdeenablefinal -theora -xine -xinerama 0 kB [ebuild N] app-crypt/qca-1.0-r3 0 kB [ebuild N] kde-base/kdeedu-3.5.9 USE=-arts -debug -kdeenablefinal -kig-scripting -solver -xinerama 0 kB [ebuild N] kde-base/kdetoys-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdewebdev-3.5.9 USE=-arts -debug -doc -kdeenablefinal -tidy -xinerama 0 kB [ebuild N] kde-base/kdegames-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdepim-3.5.9-r1 USE=-arts -debug -gnokii -kdeenablefinal -pda -xinerama 0 kB [ebuild N] kde-base/kdenetwork-3.5.9 USE=ssl -arts -debug -jingle -kdeenablefinal -kdehiddenvisibility -rdesktop -sametime -slp -wifi -xinerama 0 kB [ebuild N] kde-base/kdeartwork-3.5.9 USE=opengl -arts -debug -kdeenablefinal -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdeutils-3.5.9-r1 USE=crypt -arts -debug -kdeenablefinal -kdehiddenvisibility (-pbbuttonsd) -snmp -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdeadmin-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdegraphics-3.5.9 USE=opengl pdf -arts -debug -gphoto2 -imlib -kdeenablefinal -kpathsea -openexr -povray -scanner -xinerama 0 kB [ebuild N] kde-base/kdeaddons-3.5.9 USE=berkdb sdl -arts -debug -kdeenablefinal -xinerama 0 kB [ebuild N] kde-base/kde-3.5.9 USE=-accessibility 0 kB [blocks B ] kde-base/khelpcenter:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcminit:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcontrol:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdesktop:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kdesktop-3.5.9-r1, kde-base/khelpcenter-3.5.9, kde-base/kdialog-3.5.9-r1, kde-base/kdepasswd-3.5.9, kde-base/kcontrol-3.5.9, kde-base/kicker-3.5.9, kde-base/kdesu-3.5.9, kde-base/kcheckpass-3.5.9, kde-base/kdm-3.5.9, kde-base/konqueror-3.5.9, kde-base/kcminit-3.5.9) [blocks B ] kde-base/kdm:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdesu:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdialog:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcheckpass:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/konqueror:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdepasswd:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kicker:3.5 (is blocking kde-base/kdebase-3.5.9-r3) it reports packages of kde to be updated Nope, not updated. It shows new installs (N). In addition, it shows that you already have some split ebuilds installed which block the monolithic ones. I would suggest that you simply install kde-meta first this should solve your problems. HTH... Dirk -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] KDE 4.0.0
On 19 January 2008, Dale wrote: Uwe Thiem wrote: Hi folks, after the painful and time-consuming creation of /etc/portage/package.unmask for KDE 4, emerge --pretend --verbose =kde-base/kde-meta-4.0.0 tells me: [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I cannot unemerge 3.5.7. How can I work around this? Uwe For future reference, check out autounmask. I found out about it the other day. I have not used it yet but I'm hopeful it works. I'll have look into autounmask. Also, there is a thread on the forums about this, I think you have to have 3.5.8* version to do this. Not sure why tho. Isn't KDE 4.0 slotted? Can't you have 3.5 AND 4.0 installed and select which version you want to log into? Exactly. So why is kdebase-3.5.7-r6 (which is not even installed here) blocking kdelibs-4.0.0? Uwe -- If a man speaks in a forest, and no woman listens to him, is he still lying? -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] kde install mess
2008/10/28 Helmut Jarausch [EMAIL PROTECTED]: Hi, anyhow I managed to get a mess of blockings when trying to emerge kde packages. (might be that has something to do with the recent downgrade from 3.5.10-r* to 3.5.9) Just one example: trying to emerge e.g. konsole:3.5 I get kde-base/kdebase-kioslaves:3.5 is blocking kde-base/kdebase-3.5.9-r4 but I cannot see any negative DEPEND either in the ebuilds of kdebase-kioslaves nor kdebase-3.5.9-r4 So, what went wrong here? Many thanks for a hint, Do you have any package which belongs kde-meta with ~x86 keywords? I remember I wanted to reemerge few package on my system few weeks ago and I had some kde package with ~x86 and I got lot of blocking message. The solution: I don't use kde package with ~x86. I hope I could help. András -- - - -- Csanyi Andras -- http://sayusi.hu -- Sayusi Ando -- Bízzál Istenben és tartsd szárazon a puskaport!.-- Cromwell
[gentoo-user] what's happening with kde ebuilds?
Hi, Coming back from the holidays I sync'd and when I try to emerge world, I find messages like that: Calculating world dependencies \ !!! All ebuilds that could satisfy ~kde-base/kdm-3.5.7 have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/kdm-3.5.7 (masked by: ~x86 keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by kde-base/kdebase-meta-3.5.7 [ebuild]) I synced a couple of times but these messages related to kde updates reappear, although related to different packages. Is there some trouble in the version synchronization of the new kde ebuilds? Why does stable kdebase-meta require an unstable package? m. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Installing KDE 3.4.1
First unmask the top level package, example: echo kde-base/kdebase-meta ~x86 /etc/portage/package.keywords Then just run this script, example: unmask.pl kdebase-meta You might want to save a copy of package.keywords then compare the two for sanity before emerging. Have fun, Roy Janne Vänttinen wrote: Is there any easier way to make Portage to install KDE 3.4.1 to a stable system than to add every single installed package to /etc/portage/package.keywords? I wouldn't mind to have the entire kde-base -category use test packages but I would like to keep the rest of the system on stable ground. So PACKAGE_KEYWORDS is not a good solution. I tried to define packages with wildcards (like kde-base/* ~x86), with no luck. Is this possible? Thanks beforehand, unmask.pl Description: Perl program
[gentoo-user] Re: Is there and Alternative to compiling kde?
Neil Bothwick [EMAIL PROTECTED] writes: kde-base/kde is a meta package, it pulls in all the monolithic KDE builds. If you are concerned about installation compile times, you should not be trying to build the whole of KDE. Do you really need all of kdegames, kdeedu and kdetoys to get your system running? Stick with kde-base/kdebase or kde-base/kdebase-meta, you can cancel your current emerge and merge one of these instead, then add the rest of what you want once the system is running. I'm confused here. (even more..) Before starting the compile: I ran a comparision of `emerge -v -p kde' and emerge -v -p kde-meta The last showed a much larger pile of dependancies than the former. So I ran the former. I've now canceled as suggested and running `emerge kde-base/kdebase' It only showed the main kde-3.4X as dependancy. But with all the screwups I've managed to get these kde packages installed: (And don't need several of them) kde-base/kdegraphics-3.4.1-r1 * kde-base/kdelibs-3.4.1-r1 * kde-base/kdebase-pam-6 * kde-base/kde-env-3-r4 * kde-base/arts-3.4.1-r2 * kde-base/kdebase-3.4.1-r1 * kde-base/kdeartwork-3.4.1 * kde-base/kdepim-3.4.1-r2 * kde-base/kdegames-3.4.1 * kde-base/kdeutils-3.4.1 * kde-base/kdenetwork-3.4.1-r1 * kde-base/kdeedu-3.4.1-r1 * -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] KDE 4.2 and 3.5
On Sun, Feb 1, 2009 at 3:07 PM, Daniel D Jones ddjo...@riddlemaster.org wrote: On Sunday 01 February 2009 15:40:29 Norberto Bensa wrote: On Sun, Feb 1, 2009 at 1:38 PM, Daniel D Jones ddjo...@riddlemaster.org wrote: I have KDE 3.5 and 4.1 installed and am trying to upgrade to 4.2. I'm getting the following: You'll need kde-3.5.10 (or kdebase-startkde at least) Look in the archives, a similar question was posted a few days ago. Thanks for your response. I did search the archives and did not find anything relevant. I saw and read a thread where a block was occurring: =kde-base/kdebase-startkde-3.5.10 is blocking kde-base/kdelibs-4.2.0 It wasn't clear to me that this was the same problem, since that block referenced a 3.5.10 package and mine referenced a 3.5.9 package. since the block is: =kde-base/kdebase-startkde-3.5.10 is blocking kde-base/kdelibs-4.2.0 and 3.5.9 = 3.5.10, then yes, the mail applies to you You'll need kdebase-startkde 3.5.10 (3.5.10-r5 is available in portage) However, upgrading to 3.5.10 raises another issue. For 3.5, I didn't install the meta package, I installed the KDE base package: Uhm... Do you mean monolitich (base) vs. modules (meta)? 3.5.10 is available under the meta package system but not under the KDE package. Do I have to switch to the meta package to go to 3.5.10? (Without, that is, manually unblocking lots and lots of packages.) Can I simply install the meta package over the base package or will that create blocks or other issues? I don't know. Perhaps another user can answer that question. I moved to modules as soon as it was made available. Regards, Norberto
Re: [gentoo-user] kde-meta minus toys, games, etc
On Fri, 2 Jun 2006 19:46:07 +, Mick wrote: Apologies if this has been asked before. I uninstalled my monolithic KDE and am ready to install the split KDE ebuilds. I want to install everything except toys, games and educational packages. Install kdebase-meta, kdenetwork-meta, kdepim-meta etc. kde-meta is for those that want to install everything. -- Neil Bothwick Give a man a fish and you feed him for a day; Teach him to use the Net and he won't bother you for weeks. signature.asc Description: PGP signature
Re: [gentoo-user] Update blocked by kdebase-startkde:4
On Friday 15 July 2016, Robin Atwood wrote: > On Tuesday 12 July 2016, Andrés Becerra Sandoval wrote: > > 2016-07-09 8:52 GMT-05:00 Robin Atwood <ro...@binro.org>: > > > Attempting to update/world this weekend I get: > > > > > > > > > > > > > > > > > > # emerge -uDv @world > > > > > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > > > > > Calculating dependencies... done! > > > > > > > > > > > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5" > > > have been masked. > > > > > > !!! One of the following masked packages is required to complete your > > > request: > > > > > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by: > > > package.mask, ~amd64 keyword) > > > > > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by: > > > package.mask) > > > > > > > > > > > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo" > > > [ebuild]) > > > > > > (dependency required by "@selected" [set]) > > > > > > (dependency required by "@world" [argument]) > > > > > > > > > > > > I have all of KDE:5 masked since I think installing it sounds too > > > risky. Checking the kdebase-startkde-4.11.22-r1 ebuild it has a > > > dependency on kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has > > > anyone found a solution to this? > > > > Robin, > > > > My ugly hack on this to keep on kde4 withouth pulling frameworks 5: > > > > 1) use a local overlay > > 2) locate kactivitymanagerd-4.13.3-r1.ebuild (in > > /var/db/pkg/kde-plasma/kactivitymanagerd-4.13.3-r1) > > 3) put the kactivitymanagerd-4.13.3-r1.ebuild into > > /usr/local/portage/kde-plasma/kactivitymanagerd/ > > 4) add a > > SLOT="5" > > line to the ebuild > > 5) add a unmask line > > =kde-plasma/kactivitymanagerd-4.13.3-r1 > > to /etc/package.unmask > > > > I need 5) because I mask all kde-plasma/* packages > > Andrés- > That did the trick! Thanks very much. Until the next time... :( And the next problem: !!! All ebuilds that could satisfy "kde-plasma/plasma-workspace-wallpapers:5" have been masked. !!! One of the following masked packages is required to complete your request: - kde-plasma/plasma-workspace-wallpapers-5.7.3::gentoo (masked by: package.mask, ~amd64 keyword) - kde-plasma/plasma-workspace-wallpapers-5.6.5::gentoo (masked by: package.mask) (dependency required by "kde-base/kdebase-startkde-4.11.22- r2::gentoo[wallpapers]" [installed]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) Why does kdebase-startkde:4 want plasma-workspace-wallpapers:5? has anyone solved this yet? Thanks Robin -- -- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling -- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: [gentoo-user] kde update
Apparently, though unproven, at 17:27 on Tuesday 31 May 2011, Mark Knecht did opine thusly: On Tue, May 31, 2011 at 8:11 AM, Paul Hartman paul.hartman+gen...@gmail.com wrote: On Mon, May 30, 2011 at 11:45 AM, Alain DIDIERJEAN alain.didierj...@free.fr wrote: Trying to update from kde4.5 to kde4.6 I find that it is easier to unmerge old version :4.5 KDE, then emerge the new version :4.6. Upgrade always seems to be a mess like that. Probably there's no real problem but I think in my recent machines if I've chosen the KDE profile and try something like emerge -Cp kde-meta then there are lots of warning messages about how I'm removing parts of @system. It's unlikely (in my mind anyway) that anything would be removed that stops one from doing the 4.6 emerge, but if one goes this way they should look very carefully at what's getting taken out just to make sure. You must have something badly wrong with your @system. kde-meta depends on: RDEPEND= $(add_kdebase_dep kate) $(add_kdebase_dep kdeadmin-meta) $(add_kdebase_dep kdeartwork-meta) $(add_kdebase_dep kdebase-meta) $(add_kdebase_dep kdeedu-meta) $(add_kdebase_dep kdegames-meta) $(add_kdebase_dep kdegraphics-meta) $(add_kdebase_dep kdemultimedia-meta) $(add_kdebase_dep kdenetwork-meta) $(add_kdebase_dep kdeplasma-addons) $(add_kdebase_dep kdetoys-meta) $(add_kdebase_dep kdeutils-meta) accessibility? ( $(add_kdebase_dep kdeaccessibility-meta) ) nls? ( $(add_kdebase_dep kde-l10n) ) sdk? ( $(add_kdebase_dep kdebindings-meta) $(add_kdebase_dep kdesdk-meta) $(add_kdebase_dep kdewebdev-meta) ) semantic-desktop? ( || ( ( $(add_kdebase_dep kdepim-meta '' 4.5.93) ) ( $(add_kdebase_dep kdepim-meta '' 4.4.9) ) ) ) A few extra packages and a lot of other meta packages. emerge -Cp will remove only that one package, it won;t even remove the deps. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kde-base/kdebugdialog-3.5.2 emerge error
Richard OK, no I told you so's please - you were right! Thanks for the help! Now for the next question. How do I get my system to load kde 3.5 instead of kde 3.4? Thanks in advance. PeteOn 4/9/06, Richard Fish [EMAIL PROTECTED] wrote: On 4/9/06, Pete Pardoe [EMAIL PROTECTED] wrote: RichardThe problem is that there is no ebuild for kde-base/kdebugdialog-3.5.2 it is not a ~x86 problem. Ah, sorry, I missed that.But the problem still remains that you needto add extra stuff to package.keywords.kdebase-meta-3.5.2 can actually depend on any version of kdebugdialogbetween 3.5.0 and 3.5.2 .See this from the ebuild:$(deprange 3.5.0 $MAXKDEVER kde-base/kdebugdialog)kdebugdialog 3.5.0 is also ~x86, so again, you need to addkde-base/kdebugdialog to package.keywords in order to merge kde 3.5.2 .As proof that I am not completely full of shit:carcharias kde-base # emerge -Duvp kdebase-metaThese are the packages that would be merged, in order:Calculating dependencies |emerge: there are no ebuilds to satisfy ~kde-base/kdebugdialog- 3.5.2.(dependency required by kde-base/kdebase-meta-3.5.2 [ebuild])carcharias kde-base # echo kde-base/kdebugdialog ~x86/etc/portage/package.keywordscarcharias kde-base # emerge -Duvp kdebase-meta These are the packages that would be merged, in order:Calculating dependencies -!!! All ebuilds that could satisfy ~kde-base/libkonq-3.5.2 have been masked.!!! One of the following masked packages is required to complete your request: - kde-base/libkonq-3.5.2 (masked by: ~x86 keyword)For more information, see MASKED PACKAGES section in the emerge man page orrefer to the Gentoo Handbook.(dependency required by kde-base/kdebase- meta-3.5.2 [ebuild])Run the commands I gave you earlier, and you will allow the ~x86keyword for all base KDE packages.Or you can continue to do them oneat a time.Your choice.-Richard --gentoo-user@gentoo.org mailing list-- Pete Pardoe
Re: [gentoo-user] Finer grained kde*-meta packages
On Sat, 16 Jun 2007 06:08:52 -0500, Boyd Stephen Smith Jr. wrote: Well, but as kdenetwork-meta is a dependency of kde-meta, this solution means, that about 300 packages should be manually listed, just because one package is not wanted. No, because as I covered in my other reply, you can still use kdebase-meta, kdepim-meta, etc. to pull is all the packages from those parts of kde and only list individual applications from the parts you don't want everything from (in your case you should be able to use every kdefoo-meta 'cept for kdenetwork-meta). For your particular use case it's still 30 packages, not 300. It's less than that, because the KDE split ebuilds contain a number of packages that should never need to be installed directly. One already mentioned in this thread is dcoprss, which is pulled in by packages that need it. I'm not sure USE flags for the meta packages are a good idea, they could add a lot of confusion. The meta packages are supposed to install everything, if you don't want that, don't use them. -- Neil Bothwick Ultimate memory manager; Windows, it manages to use it all.. signature.asc Description: PGP signature
[gentoo-user] emerge -u world won't update kde metapackages
I emerged kde 3.4 using the metapackages (kdebase-meta, kdeaddons-meta etc.). However I now find that emerge -u world fails to update any of the component packages to their latest versions, which should all be 3.4.1(-r2/r3/etc). I end up emerging newer versions individually (e.g. emerge kopete) when I think I have a bug problem, which is obviously a clumsy way to do things. I know I can emerge kdebase-meta kdeaddons-meta kdeblahblahblah to get things up to date, but is there a way to get portage to actually deal with kde nicely like it used to? Many thanks Robert -- Robert Persson Don't use nuclear weapons to troubleshoot faults. (US Air Force Instruction 91-111, 1 Oct 1997) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -u world won't update kde metapackages
Robert Persson wrote: I emerged kde 3.4 using the metapackages (kdebase-meta, kdeaddons-meta etc.). However I now find that emerge -u world fails to update any of the component packages to their latest versions, which should all be 3.4.1(-r2/r3/etc). I end up emerging newer versions individually (e.g. emerge kopete) when I think I have a bug problem, which is obviously a clumsy way to do things. I know I can emerge kdebase-meta kdeaddons-meta kdeblahblahblah to get things up to date, but is there a way to get portage to actually deal with kde nicely like it used to? Many thanks Robert Use the --deep option. emerge -uD world. see man emerge for more information. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] kde-meta minus toys, games, etc
On 02/06/06, Raymond Lewis Rebbeck [EMAIL PROTECTED] wrote: $ ls /usr/portage/kde-base/ | grep meta Thanks. Last question: Is emerging kdebase-meta meant to pull in 45 packages, or are there any old kde apps in my system pulling them in as I am trying to emerge my new split KDE? From the log: === 1149285323: *** emerge --update --deep --verbose kdebase-meta 1149285332: emerge (1 of 45) kde-base/kdelibs-3.5.2-r6 to / 1149285332: === (1 of 45) Cleaning (kde-base/kdelibs-3.5.2-r6::/usr/portage/kde-base/kdelibs/kdelibs-3.5.2-r6.ebuild) 1149285341: === (1 of 45) Compiling/Merging (kde-base/kdelibs-3.5.2-r6::/usr/portage/kde-base/kdelibs/kdelibs-3.5.2-r6.ebuild) === -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde-meta minus toys, games, etc
Yes, that is normal. The KDE ebuilds are 'split' now, one monolithic ebuild is equivalent to a few dozen split ebuilds. Each individual app or library has it's own ebuild. On Saturday, 3 June 2006 6:41, Mick wrote: On 02/06/06, Raymond Lewis Rebbeck [EMAIL PROTECTED] wrote: $ ls /usr/portage/kde-base/ | grep meta Thanks. Last question: Is emerging kdebase-meta meant to pull in 45 packages, or are there any old kde apps in my system pulling them in as I am trying to emerge my new split KDE? From the log: === 1149285323: *** emerge --update --deep --verbose kdebase-meta 1149285332: emerge (1 of 45) kde-base/kdelibs-3.5.2-r6 to / 1149285332: === (1 of 45) Cleaning (kde-base/kdelibs-3.5.2-r6::/usr/portage/kde-base/kdelibs/kdelibs-3.5.2-r6. ebuild) 1149285341: === (1 of 45) Compiling/Merging (kde-base/kdelibs-3.5.2-r6::/usr/portage/kde-base/kdelibs/kdelibs-3.5.2-r6. ebuild) === -- Regards, Mick -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 21:16:51 BST Dale wrote: > I went through this a few years ago. I had some large programs > installed that I didn't use, Kmail and others. I wanted to clean them > out but at the time I had installed KDE with kde-meta. Basically, that > installs everything KDE, wanted or not. I uninstalled that and went > these instead: According to the current wiki page these days the kde-meta has been replaced with plasma-meta. This is how I have configured plasma-meta: Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser- integration crypt desktop-portal display-manager elogind handbook legacy- systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk - networkmanager -plymouth -pulseaudio -sdk -systemd) BUT ... I am thinking of uninstalling it, deplclean-ing my world and installing kde-plasma/plasma-desktop which is the slim version, while keeping some select kde-meta packages I need/want. > root@fireball / # equery list *kde*meta* > * Searching for *kde*meta* ... > [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 I have this installed too. > [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 I think the kdebase-meta was meant to be a transitional package from KDE4 to plasma/KDE5. I suspect this has been superseded by kde-plasma/plasma-meta, but I'm not sure. In any case, I do not have this installed. > [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 I have this installed too. > [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 No games for me, thanks. > [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 > [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 I have these two installed, plus: [IP-] [ ] kde-apps/kdenetwork-meta-18.12.3:5 [IP-] [ ] kde-apps/kdepim-meta-18.12.3:5 [IP-] [ ] kde-apps/kdeutils-meta-18.12.3:5 > This is one of the things I like about Gentoo, being able to cut off or > get rid of things I don't want. USE flags help with that a lot. > > Glad you got it sorted out. Sadly I'm not there yet. I've got to figure out how to get back my Suspend to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing NetworkManager, or at least without having it being started by powerdevil. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] re-emerging kde-meta's??
On Fri, 22 Apr 2005 13:25:47 -0400, Michael W. Holdeman wrote: What is theg correct procedure for rebuilding kde segments like kdebase- meta, or teh whole thing as in kde-meta? qpkg -I -nc -g kde-base | xargs emerge --verbos --oneshot --pretend Review the output and run again without --pretend. -- Neil Bothwick teG I sdrawkcaB eroM ehT oG I sdrawroF eroM ehT pgpAqaLxqTOj1.pgp Description: PGP signature
Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling
On Tuesday 06 February 2007, Dale wrote: I don't understand portage and ebuilds well enough to do that. How about this. Is there a way to just tell emerge to emerge each separate package and get rid of kde-meta? kde-meta is, well, as meta package. All it does is tell portage to emerge all the dependencies, and that turns out to be all 300 individual kde ebuilds. kdebase-meta is the same thing on a smaller scale and only for the basic stuff. You could 'emerge -avC kde-meta' and all that would happen is the -meta package gets removed, leaving the deps in place. However, they aren't in world so your next 'emerge --depclean' will want to remove them. Few people actually use all of KDE, so a good compromise is to figure out what you actually do use and emerge just those ebuilds Have you read the kde split-ebuilds HOWTO at gentoo.org/doc lately? It's all in there, but it's a lot of info so it's useful to refresh the old memory every now and again I don't know, equery list kde then poke them in one by one. Would that let it leave kate and kdelibs where it is without masking all of kde? I just tried this test: masked kate-3.5.6 unmerged kdebase-meta emerge -pD world and it went crazy with blockers. Portage wanted to emerge kdebase-3.5.5 (not the -meta) one and that was bloked by all the kdebase packages at version 3.5.6. So it would seem there are some hard coded blocks in place, which is sensible as mixing KDE app and lib versions willy-nilly is probably not a good idea... Thanks for the reply though. At least I can open the file and read it and it is not just me having this problem. alan -- Optimists say the glass is half full, Pessimists say the glass is half empty, Developers say wtf is the glass twice as big as it needs to be? Alan McKinnon alan at linuxholdings dot co dot za +27 82, double three seven, one nine three five -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Lost KDE
On Wednesday 04 July 2007 18:44, Kevin O'Gorman wrote: It was missing, but I can't emerge kdebase because there are about 20 packages that are blocking it. Maybe that's the problem. This looks odd. You haven't mixed monolithic and meta packages by any chance? I would probably remove the blockers and try to re-emerge the required meta packages, but you may want to wait for a smarter suggestion. -- Regards, Mick pgp1VPcCyTOoC.pgp Description: PGP signature
Re: [gentoo-user] emerge -u world won't update kde metapackages
On Saturday 22 October 2005 04:07 pm, Robert Persson wrote: I know I can emerge kdebase-meta kdeaddons-meta kdeblahblahblah to get things up to date, but is there a way to get portage to actually deal with kde nicely like it used to? Just emerge kde, you don't need to work with the meta packages themselves. The kde is itself a meta package and will ensure the sub-packages are kept up to date (at least that's how it's been working on my box). Dave -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] pam fixed now it's tcpdump
On Thursday 31 January 2008 21:44:19 Alan McKinnon wrote: I can't think of a reason why anyone wouldn't want all of kdebase so there's no need to emerge startkde explicitly I did install startkde on this box. Six packages would now be installed if I were to emerge kdebase-meta, namely kdebugdialog, ksysguard, ktip, klipper, knetattach and kpager. I don't miss any of those, so what do you think I'm losing by not installing them? I think that installing startkde is the first step on the road to a lean system, which I imagine is its purpose. Long may it continue! -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] KDE 4.2 and 3.5
On Sun, Feb 1, 2009 at 3:50 PM, Daniel D Jones ddjo...@riddlemaster.org wrote: Uh, someone's confused here. It may very well be me but I'm not following you at all. The other post concerned startkde blocking kdelibs. Yes. I'm sorry. You're using monolithic KDE. I don't remember if startkde was part of kdebase. Maybe that's where your problem is. My block is kdebase 3.5 blocking kdelibs 4.2. There's no mention of startkde bocking anything on my system. So I don't follow why you're telling me that I need startkde 3.5.10. My bad. I'm sorry. Neil says you'll need to remove kde and emerge kde-meta. Follow his advice. Regards, Norberto
Re: [gentoo-user] Java (Blackdown) and Konqueror
On Thu, 16 Jun 2005 01:54:32 +0300, Zac Medico [EMAIL PROTECTED] wrote: Martins wrote: i did emerge kdebase, and i belive i put java flag. how to check was it aplied to konqueror part? I dont want to go back to kde-meta 'cause kdebase is very fast and stable In /var/db/pkg the USE files contain the use flags that each package was compiled with. all kde pakages was built with java USE flag ang good news are konqueror now loads aplets except Java ControlPanel. Only change between trys was halt - sleep - boot ;) thanx for help Martins -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] cups printing error
This is an aspect of Gentoo that I don't understand very well. the various kioslaves block other packages and vice-versa. For example, kdepim blocks kdepim-kioslaves, and kdebase blocks kdebase-kioslaves. Same goes for kdemultimedia and kdemultimedia-kioslaves. As a test, I unmerged kdepim and emerged kdepim-kioslaves and now my kmail is messed up. Thing is I cannot emerge both at the same time. Well, by looking on the forums it seems you have a mixed system. kdepim is a monolithic package. kdepim-kioslaves is a package of the kde split packages. Try unmerging kdepim and emerging kdepim-meta, and anyways be sure of having a kde relying on split packages (that's the way to go in the future) http://forums.gentoo.org/viewtopic-t-355389.html m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde-meta minus toys, games, etc
They're the same as the monolithic packages but with -meta on the end. Easiest way to see what is in them: # emerge -pv foo-meta On Saturday, 3 June 2006 5:51, Mick wrote: On 02/06/06, Neil Bothwick [EMAIL PROTECTED] wrote: On Fri, 2 Jun 2006 19:46:07 +, Mick wrote: Apologies if this has been asked before. I uninstalled my monolithic KDE and am ready to install the split KDE ebuilds. I want to install everything except toys, games and educational packages. Install kdebase-meta, kdenetwork-meta, kdepim-meta etc. kde-meta is for those that want to install everything. Thanks for all the replies. What's the best way to find out what -meta packages exist and what they contain? -- Regards, Mick -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] KDE 4.0.0
Uwe Thiem wrote: Hi folks, after the painful and time-consuming creation of /etc/portage/package.unmask for KDE 4, emerge --pretend --verbose =kde-base/kde-meta-4.0.0 tells me: [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I cannot unemerge 3.5.7. How can I work around this? Uwe For future reference, check out autounmask. I found out about it the other day. I have not used it yet but I'm hopeful it works. Also, there is a thread on the forums about this, I think you have to have 3.5.8* version to do this. Not sure why tho. Isn't KDE 4.0 slotted? Can't you have 3.5 AND 4.0 installed and select which version you want to log into? Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] KDE 4.0.0
On Sat, 19 Jan 2008 17:42:55 +0200, Dale [EMAIL PROTECTED] wrote: Uwe Thiem wrote: Hi folks, after the painful and time-consuming creation of /etc/portage/package.unmask for KDE 4, emerge --pretend --verbose =kde-base/kde-meta-4.0.0 tells me: [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I cannot unemerge 3.5.7. How can I work around this? Uwe For future reference, check out autounmask. I found out about it the other day. I have not used it yet but I'm hopeful it works. Also, there is a thread on the forums about this, I think you have to have 3.5.8* version to do this. Not sure why tho. Isn't KDE 4.0 slotted? Can't you have 3.5 AND 4.0 installed and select which version you want to log into? Dale :-) :-) Autounmask looks to work, but some packets with ~86 I think need manual check. -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] KDE split ebuilds broken
When I first upgraded to 3.4 I was unaware of the new split ebuilds, so I just emerged normally getting (I assume) the old monolithic ebuilds. When I finally got around to trying to use 3.4 (which was a few months later) KDE came up with the taskbar not able to start, and as such I couldn't see any minimized tasks. In researching I discovered the new split ebuilds, read the KDE split ebuilds howto, and decided to see if using the split ebuilds would solve my problem. So I unmerged kdebase and then emerged kdebase-meta. After doing that not only does taskbar not work, but the pager and the clock won't run and give me similar error messages when I start kde. The howto says that I should be OK having kdebase using split ebuilds and others KDE parts using th old monolithic way. Is this working for anyone? Anyone else run into similar problems or have ideas about what the heck is going wrong? I tried removing all my old ~/.kde dirs but that didn't fix it. Appreciate any pointers. -Wes -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
David Corbin wrote: On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote: On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. What's the best way to find out what all the split ebuilds are? David The kde-meta ebuild should cover all of the split ebuilds. If you read that you will discover that it depends on other meta packages. Read the ebuilds of those meta packages to find out what they depend on, and so on. $ equery which kde-meta /usr/portage/kde-base/kde-meta/kde-meta-3.4.2.ebuild Unfortunately, equery depgraph does not seem to be very helpful for this type of query. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem emerging kde-meta
On Thursday 01 March 2007 22:54:43 Boyd Stephen Smith Jr. wrote: Your problem is that you are trying to mix them. That is difficult or impossible and is AFAIK not supported. Either remove all your monolithic packages and install the split equivalents (the -meta packages help here) or remove all your split packages and install all the monolithic packages you need. Quoting [1]: Split and monolithic ebuilds can be mixed freely. The only restriction is that a monolithic ebuild can't be installed at the same time as a split ebuild deriving from it. There are blocking dependencies in the ebuilds that enforce this, so you can do anything emerge allows you to do. So emerging say kdebase (monolithic) and kpdf (split but not from kdebase) at the same time is quite supported. It just prevents you from emerging either of kde-meta or kde since they are all split or all monolithic respectively. I'm in favour of removing the monolithic ebuilds too though. They seem to cause more confusion than they are worth. :) [1] http://www.gentoo.org/doc/en/kde-split-ebuilds.xml -- Bo Andresen pgplMG0g8jBk7.pgp Description: PGP signature
Re: [gentoo-user] Issues with Dependencies
On Saturday 01 April 2006 02:25, Lord Sauron wrote: localhost ~ # emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdialog-3.4.1) [SNIP] [blocks B ] =kde-base/kdegraphics-3.4* (is blocking kde-base/kdegraphics-kfile-plugins-3.4.3) [SNIP] No. Still doesn't like me. I never know about the meta packages, so I could be on Gnome for a little while until I get this sorted out, huh? Seems you have a mixture of monolithic and split. Like I said before I recommend the split packages. To get those you have to unmerge the monolithic packages. So: # emerge --unmerge --ask --verbose kdebase kdegraphics # emerge --ask --verbose kde-meta It is all explained at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2chap=1#doc_chap4 And please learn to cut out anything you don't reply to and reply below that which you do reply to. -- Bo Andresen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde-base/kdebugdialog-3.5.2 emerge error
Richard The problem is that there is no ebuild for kde-base/kdebugdialog-3.5.2 it is not a ~x86 problem. That version of the program does not exist in portage there is only kde-base/kdebugdialog-3.5.0. The error was: emerge: there are no ebuilds to satisfy ~kde-base/kdebugdialog-3.5.2. (dependency required by kde-base/kdebase-meta-3.5.2 [ebuild]) PeteOn 4/8/06, Richard Fish [EMAIL PROTECTED] wrote: On 4/8/06, Pete Pardoe [EMAIL PROTECTED] wrote: Hi,I am trying to upgrade to kde 3.5.2specifically because my current KDE was installed with emerge kde-meta I have added the appropriate dependencies to /etc/portage/package.keywordsNo you haven't.package.keywords doesn't get applied to dependanciesautomatically.As the message indicates, kdebase-meta-3.5.2 dependson kdebugdialog-3.5.2, which you didn't add to package.keywordsaccording to your post.If you want the ~x86 version of KDE, without going fully ~x86, you can try:# cd /usr/portage# for x in kde-base/* ; do #echo $x ~x86 /etc/portage/package.keywords# doneThis will allow the ~x86 keywords for _all_ base KDE applications.You may still have to add qt or other dependancies manually however. -Richard--gentoo-user@gentoo.org mailing list-- Pete Pardoe
Re: [gentoo-user] Upgrading KDE
On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote: On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. What's the best way to find out what all the split ebuilds are? David -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] KDE 4.0.0
On 19 January 2008, Paul Salters wrote: On Saturday 19 January 2008 16:52:45 Δημήτριος Ροπόκης wrote: On Sat, 19 Jan 2008 17:42:55 +0200, Dale [EMAIL PROTECTED] wrote: Uwe Thiem wrote: Hi folks, after the painful and time-consuming creation of /etc/portage/package.unmask for KDE 4, emerge --pretend --verbose =kde-base/kde-meta-4.0.0 tells me: [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I cannot unemerge 3.5.7. How can I work around this? Uwe For future reference, check out autounmask. I found out about it the other day. I have not used it yet but I'm hopeful it works. Also, there is a thread on the forums about this, I think you have to have 3.5.8* version to do this. Not sure why tho. Isn't KDE 4.0 slotted? Can't you have 3.5 AND 4.0 installed and select which version you want to log into? Dale :-) :-) Autounmask looks to work, but some packets with ~86 I think need manual check. hi, you need to unmask kde-base/kdebase-3.5.7-r6 and emerge that. should work :) ??? According to emerge, kdebase-3.5.7-r6 is *blocking* kdelibs-4.0.0. See my original post. Uwe -- If a man speaks in a forest, and no woman listens to him, is he still lying? -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] KDE4.0?
The above keeps coming up over and over. So, I'll have to leave it here until I get more info. -mw more info: I ran # autounmask kde-base/kde-meta-4.0.0 again and this time these blocks appeared. [blocks B ] app-admin/eselect-esd (is blocking media-sound/esound-0.2.36-r1) [blocks B ] kde-base/kdebase-3.5.7-r6 (is blocking kde-base/kdelibs-4.0.0) [blocks B ] app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) [blocks B ] media-sound/esound-0.2.36-r2 (is blocking app-admin/eselect-esd-20060719) [blocks B ] =app-admin/eselect-1.0.3 (is blocking app-admin/eselect-opengl-1.0.3) From the gentoo-kde4-faq: Q: You said I could install KDE 3.5 and KDE 4.0, but they block each other! A: You will need to install the latest revision (not version) of kde-base/kdebase (if you use monolithic ebuilds) or kde-base/kdebase-startkde (if you use split ebuilds). These versions include patches to allow multiple versions of KDE to coexist. So I autounmasked kdebase-startkde * done! and tried: # emerge -avD kde-base/kdebase-startkde:kde-4 But was met with the same blockers despite what it says in the faq. Or am I missing something else? -mw Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] FIXED: Re: KDE3 removal
On Thursday 26 November 2009 19:20:26 Alan McKinnon wrote: On Thursday 26 November 2009 19:34:34 James wrote: kde-4.3.1 went smooth, except for I have to manually removed all the kde-3.5 packages. It had kde-meta-3.5.10. Is there some syntax or a better method to insure all the kde-3.5.x packages are removed, without a manual sweep? grep kde /var/lib/portage/world and eyeball the output. There should only be -meta packages, and individual packages for which you have NOT installed the -meta package, in there. vi the world file and remove the stuff that shouldn't be there, then That's a good point ... over the years I have accumulated all sorts of packages I am not sure I need (by forgetting to use --oneshot). Should these be in there? kde-base/akregator kde-base/ark kde-base/drkonqi kde-base/kaddressbook kde-base/kappfinder kde-base/kate kde-base/kcalc kde-base/kcharselect kde-base/kcheckpass kde-base/kcminit kde-base/kcontrol kde-base/kcron kde-base/kdeadmin-meta --Yes kde-base/kdeartwork-emoticons kde-base/kdeartwork-iconthemes kde-base/kdeartwork-kscreensaver kde-base/kdeartwork-meta --Yes kde-base/kdeartwork-sounds kde-base/kdeartwork-styles kde-base/kdeartwork-wallpapers kde-base/kdebase-data kde-base/kdebase-kioslaves kde-base/kdebase-meta --Yes kde-base/kdebase-startkde kde-base/kdebugdialog kde-base/kdegraphics-meta --Yes kde-base/kdelibs kde-base/kdemultimedia-kioslaves kde-base/kdemultimedia-meta --Yes kde-base/kdenetwork-filesharing kde-base/kdenetwork-meta --Yes kde-base/kdepasswd kde-base/kdepim-meta --Yes kde-base/kdesu kde-base/kdeutils-meta --Yes kde-base/kdewebdev-meta --Yes kde-base/kdf kde-base/kdialog kde-base/kdm kde-base/kdnssd kde-base/kfilereplace kde-base/kfloppy kde-base/kgamma kde-base/kget kde-base/kghostview kde-base/kgpg kde-base/khelpcenter kde-base/khotkeys kde-base/kicker kde-base/kimagemapeditor kde-base/kjots kde-base/klinkstatus kde-base/klipper kde-base/kmail kde-base/kmenuedit kde-base/kmix kde-base/knetattach kde-base/knetworkconf kde-base/kolourpaint kde-base/kommander kde-base/konqueror kde-base/konsole kde-base/kontact kde-base/kopete kde-base/kppp kde-base/krdc kde-base/kreadconfig kde-base/krfb kde-base/kruler kde-base/kscd kde-base/kscreensaver kde-base/ksmserver kde-base/ksnapshot kde-base/kstart kde-base/ksysguard kde-base/ksystraycmd kde-base/ktimer kde-base/kuser kde-base/kweather kde-base/kwin kde-base/kxsldbg kde-base/libkcddb kde-base/libkdepim kde-base/libkonq kde-base/nsplugins Other than the metas which I have marked with --Yes I'm not sure I need the rest. Shall I blow them away? emerge -C all-kde3.5-meta-packages-in-world emerge -a --depclean -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] KDE4.0?
--- Justin [EMAIL PROTECTED] wrote: maxim wexler schrieb: Hi group, $eix kde gives: did you do an update-eix? yes kde-4 ist masked. THink thats why it doesn show up. What does ls /usr/portage/kde-base/ says? [EMAIL PROTECTED] ~ $ ls /usr/portage/kde-base/ akregatorkdeartwork-styles kimagemapeditor ksmiletris amor kdeartwork-wallpapers kitchensync ksmserver ark kdebase kiten ksnake arts kdebase-data kjots ksnapshot artsplugin-akode kdebase-kioslaves kjsembed ksokoban artsplugin-audiofile kdebase-meta kjumpingcube kspaceduel artsplugin-mpeglib kdebase-pam klaptopdaemon ksplashml artsplugin-mpg123kdebase-startkde klatinkspy artsplugin-xine kdebindings-meta klettres kstars atlantik kdebugdialog klickety kstart atlantikdesigner kdeedu klinesksvg blinken kdeedu-applnk klinkstatus ksync certmanager kdeedu-meta klipper ksysguard cervisia kdegames kmag ksystraycmd dcopckdegames-meta kmahjongg ksysv dcopjava kdegraphics kmail ktalkd dcopperl kdegraphics-kfile-plugins kmailcvt kteatime dcoppython kdegraphics-meta kmenuedit ktimer dcoprss kdejava kmid ktip drkonqi kdelibs kmilo ktnef eyesapplet kdelirc kminesktouch fifteenappletkdemultimedia kmix ktron juk kdemultimedia-arts kmoon kttsd kaboodle kdemultimedia-kappfinder-data kmousetool ktuberling kaddressbook kdemultimedia-kfile-pluginskmouth kturtle kaddressbook-plugins kdemultimedia-kioslaves kmplotktux kalarm kdemultimedia-meta kmrml kuickshow kalyptus kdenetwork kmtrace kuiviewer kalzium kdenetwork-filesharing knetattachkuser kamera kdenetwork-kfile-plugins knetwalk kverbos kanagram kdenetwork-meta knewsticker kview kandykdepasswd knewsticker-scripts kviewshell kappfinder kdepim knode kvoctrain kapptemplate kdepim-kioslaves knoteskwalletmanager karm kdepim-kresources kode kweather kasteroids kdepim-meta kodo kwifimanager kate kdepim-wizards kolf kwin kate-plugins kdeprint kolourpaint kwin4 katomic kdesdk kommander kwordquiz kaudiocreatorkdesdk-kfile-plugins kompare kworldclock kbabel kdesdk-kioslaves konq-plugins kxkb kbackgammon kdesdk-meta konqueror kxsldbg kbattleship kdesdk-misc konqueror-akregator libkcal kblackboxkdesdk-scripts konquest libkcddb kbounce kdesktop konsole libkdeedu kbruch kdesu konsolekalendar libkdegames kbstateappletkdetoys kontact libkdenetwork kbugbuster kdetoys-meta kontact-specialdates libkdepim kcachegrind kdeutils kooka libkholidays kcalckdeutils-meta kopetelibkmime kcharselect kdewebdev korganizerlibkonq kcheckpass kdewebdev-meta korn
Re: [gentoo-user] Still kde problems with monolithic-split
Am Sonntag, 5. Oktober 2008 07:19:37 schrieb [EMAIL PROTECTED]: It getting more confused: This morning I did a [...] emerge -pv kde Now I am confused. Thought you wanted to install kde-meta??? still reports: Calculating dependencies... done! [ebuild N] kde-base/kdebase-3.5.9-r3 USE=branding cups hal ldap opengl pam -arts -debug -ieee1394 -java -joystick -kdeenablefinal -kdehiddenvisibility -lm_sensors -logitech-mouse -openexr -samba -xcomposite -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdemultimedia-3.5.9 USE=alsa encode gstreamer mp3 vorbis -akode -arts -audiofile -debug -flac -kdeenablefinal -theora -xine -xinerama 0 kB [ebuild N] app-crypt/qca-1.0-r3 0 kB [ebuild N] kde-base/kdeedu-3.5.9 USE=-arts -debug -kdeenablefinal -kig-scripting -solver -xinerama 0 kB [ebuild N] kde-base/kdetoys-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdewebdev-3.5.9 USE=-arts -debug -doc -kdeenablefinal -tidy -xinerama 0 kB [ebuild N] kde-base/kdegames-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdepim-3.5.9-r1 USE=-arts -debug -gnokii -kdeenablefinal -pda -xinerama 0 kB [ebuild N] kde-base/kdenetwork-3.5.9 USE=ssl -arts -debug -jingle -kdeenablefinal -kdehiddenvisibility -rdesktop -sametime -slp -wifi -xinerama 0 kB [ebuild N] kde-base/kdeartwork-3.5.9 USE=opengl -arts -debug -kdeenablefinal -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdeutils-3.5.9-r1 USE=crypt -arts -debug -kdeenablefinal -kdehiddenvisibility (-pbbuttonsd) -snmp -xinerama -xscreensaver 0 kB [ebuild N] kde-base/kdeadmin-3.5.9 USE=-arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama 0 kB [ebuild N] kde-base/kdegraphics-3.5.9 USE=opengl pdf -arts -debug -gphoto2 -imlib -kdeenablefinal -kpathsea -openexr -povray -scanner -xinerama 0 kB [ebuild N] kde-base/kdeaddons-3.5.9 USE=berkdb sdl -arts -debug -kdeenablefinal -xinerama 0 kB [ebuild N] kde-base/kde-3.5.9 USE=-accessibility 0 kB [blocks B ] kde-base/khelpcenter:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcminit:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcontrol:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdesktop:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] =kde-base/kdebase-3.5* (is blocking kde-base/kdesktop-3.5.9-r1, kde-base/khelpcenter-3.5.9, kde-base/kdialog-3.5.9-r1, kde-base/kdepasswd-3.5.9, kde-base/kcontrol-3.5.9, kde-base/kicker-3.5.9, kde-base/kdesu-3.5.9, kde-base/kcheckpass-3.5.9, kde-base/kdm-3.5.9, kde-base/konqueror-3.5.9, kde-base/kcminit-3.5.9) [blocks B ] kde-base/kdm:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdesu:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdialog:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kcheckpass:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/konqueror:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kdepasswd:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B ] kde-base/kicker:3.5 (is blocking kde-base/kdebase-3.5.9-r3) it reports packages of kde to be updated Nope, not updated. It shows new installs (N). In addition, it shows that you already have some split ebuilds installed which block the monolithic ones. I would suggest that you simply install kde-meta first this should solve your problems. HTH... Dirk
Re: [gentoo-user] Plasma teething problems - Part II
On 2019.06.24 16:54, Mick wrote: On Monday, 24 June 2019 21:40:07 BST you wrote: > On Monday, 24 June 2019 21:16:51 BST Dale wrote: > > I went through this a few years ago. I had some large programs > > installed that I didn't use, Kmail and others. I wanted to clean them > > out but at the time I had installed KDE with kde-meta. Basically, that > > installs everything KDE, wanted or not. I uninstalled that and went > > > these instead: > According to the current wiki page these days the kde-meta has been replaced > with plasma-meta. This is how I have configured plasma-meta: > > Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser- > integration crypt desktop-portal display-manager elogind handbook legacy- > systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk - > networkmanager -plymouth -pulseaudio -sdk -systemd) > > BUT ... I am thinking of uninstalling it, deplclean-ing my world and > installing kde-plasma/plasma-desktop which is the slim version, while > keeping some select kde-meta packages I need/want. > > > root@fireball / # equery list *kde*meta* > > > > * Searching for *kde*meta* ... > > > > [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 > > I think the kdebase-meta was meant to be a transitional package from KDE4 to > plasma/KDE5. I suspect this has been superseded by kde-plasma/plasma-meta, > but I'm not sure. In any case, I do not have this installed. > > > [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 > > No games for me, thanks. > > > [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 > > [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 > > I have these two installed, plus: > > [IP-] [ ] kde-apps/kdenetwork-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdepim-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdeutils-meta-18.12.3:5 > > > This is one of the things I like about Gentoo, being able to cut off or > > get rid of things I don't want. USE flags help with that a lot. > > > > Glad you got it sorted out. > > Sadly I'm not there yet. I've got to figure out how to get back my Suspend > to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing > NetworkManager, or at least without having it being started by powerdevil. Hmm ... plasma-desktop was already installed, dragged in by plasma-meta. So no need to reinstall it. Sadly trying to depclean after removing plasma-meta will get rid of a lot of packages, something I'm not keen to do: >>> These are the packages that would be unmerged: [snip long list of packages] I just chose the specific packages I wanted and explicitly emerged them. You can just add them to your world file (either manually, or with "emerge --noreplace package" so they won't be depcleaned. I have lots of kde stuff (37 items from grep kde worldfile) but kdecore-meta and kdegraphics-meta are the only meta packages in my world file. Jack
Re: [gentoo-user] FIXED: Re: KDE3 removal
That's a good point ... over the years I have accumulated all sorts of packages I am not sure I need (by forgetting to use --oneshot). Should these be in there? kde-base/akregator kde-base/ark kde-base/drkonqi kde-base/kaddressbook kde-base/kappfinder kde-base/kate kde-base/kcalc kde-base/kcharselect kde-base/kcheckpass kde-base/kcminit kde-base/kcontrol kde-base/kcron kde-base/kdeadmin-meta--Yes kde-base/kdeartwork-emoticons kde-base/kdeartwork-iconthemes kde-base/kdeartwork-kscreensaver kde-base/kdeartwork-meta--Yes kde-base/kdeartwork-sounds kde-base/kdeartwork-styles kde-base/kdeartwork-wallpapers kde-base/kdebase-data kde-base/kdebase-kioslaves kde-base/kdebase-meta--Yes kde-base/kdebase-startkde kde-base/kdebugdialog kde-base/kdegraphics-meta--Yes kde-base/kdelibs kde-base/kdemultimedia-kioslaves kde-base/kdemultimedia-meta--Yes kde-base/kdenetwork-filesharing kde-base/kdenetwork-meta--Yes kde-base/kdepasswd kde-base/kdepim-meta--Yes kde-base/kdesu kde-base/kdeutils-meta--Yes kde-base/kdewebdev-meta--Yes kde-base/kdf kde-base/kdialog kde-base/kdm kde-base/kdnssd kde-base/kfilereplace kde-base/kfloppy kde-base/kgamma kde-base/kget kde-base/kghostview kde-base/kgpg kde-base/khelpcenter kde-base/khotkeys kde-base/kicker kde-base/kimagemapeditor kde-base/kjots kde-base/klinkstatus kde-base/klipper kde-base/kmail kde-base/kmenuedit kde-base/kmix kde-base/knetattach kde-base/knetworkconf kde-base/kolourpaint kde-base/kommander kde-base/konqueror kde-base/konsole kde-base/kontact kde-base/kopete kde-base/kppp kde-base/krdc kde-base/kreadconfig kde-base/krfb kde-base/kruler kde-base/kscd kde-base/kscreensaver kde-base/ksmserver kde-base/ksnapshot kde-base/kstart kde-base/ksysguard kde-base/ksystraycmd kde-base/ktimer kde-base/kuser kde-base/kweather kde-base/kwin kde-base/kxsldbg kde-base/libkcddb kde-base/libkdepim kde-base/libkonq kde-base/nsplugins Other than the metas which I have marked with --Yes I'm not sure I need the rest. Shall I blow them away? I have a rather bloated kde install and this is mine: r...@smoker / # grep kde /var/lib/portage/world kde-base/kde-meta kde-base/kde-meta:3.5 kde-misc/youtube-servicemenu r...@smoker / # You can always remove those things, run -p --depclean and add back with the -n option what you want to keep. Dale :-) :-) P. S. Upgraded to Seamonkey 2.0 and I got to adjust a few settings here. :/ It looks good on the screen but the quoting part . . . . sucks.
Re: [gentoo-user] kde update
Alan McKinnon wrote: Apparently, though unproven, at 17:27 on Tuesday 31 May 2011, Mark Knecht did opine thusly: On Tue, May 31, 2011 at 8:11 AM, Paul Hartman paul.hartman+gen...@gmail.com wrote: On Mon, May 30, 2011 at 11:45 AM, Alain DIDIERJEAN alain.didierj...@free.fr wrote: Trying to update from kde4.5 to kde4.6 I find that it is easier to unmerge old version :4.5 KDE, then emerge the new version :4.6. Upgrade always seems to be a mess like that. Probably there's no real problem but I think in my recent machines if I've chosen the KDE profile and try something like emerge -Cp kde-meta then there are lots of warning messages about how I'm removing parts of @system. It's unlikely (in my mind anyway) that anything would be removed that stops one from doing the 4.6 emerge, but if one goes this way they should look very carefully at what's getting taken out just to make sure. You must have something badly wrong with your @system. kde-meta depends on: RDEPEND= $(add_kdebase_dep kate) $(add_kdebase_dep kdeadmin-meta) $(add_kdebase_dep kdeartwork-meta) $(add_kdebase_dep kdebase-meta) $(add_kdebase_dep kdeedu-meta) $(add_kdebase_dep kdegames-meta) $(add_kdebase_dep kdegraphics-meta) $(add_kdebase_dep kdemultimedia-meta) $(add_kdebase_dep kdenetwork-meta) $(add_kdebase_dep kdeplasma-addons) $(add_kdebase_dep kdetoys-meta) $(add_kdebase_dep kdeutils-meta) accessibility? ( $(add_kdebase_dep kdeaccessibility-meta) ) nls? ( $(add_kdebase_dep kde-l10n) ) sdk? ( $(add_kdebase_dep kdebindings-meta) $(add_kdebase_dep kdesdk-meta) $(add_kdebase_dep kdewebdev-meta) ) semantic-desktop? ( || ( ( $(add_kdebase_dep kdepim-meta '' 4.5.93) ) ( $(add_kdebase_dep kdepim-meta '' 4.4.9) ) ) ) A few extra packages and a lot of other meta packages. emerge -Cp will remove only that one package, it won;t even remove the deps. Does anyone remember the discussion I had about kde packages being in the system set when doing a emerge -e system? If I for example unmerge kde-meta then run --depclean, I bet I would get the error about system packages being removed. It may be because of USE flags but this was what I was concerned about during the last discussion. Having GUI packages, especially KDE, included in the system set, even if because of USE flags, is going to lead to problems at some point. Or maybe I am reading all this wrong? Dale :-) :-)
Re: [gentoo-user] what's happening with kde ebuilds?
On Sunday 19 August 2007 13:26:46 b.n. wrote: Coming back from the holidays I sync'd and when I try to emerge world, I find messages like that: Calculating world dependencies \ !!! All ebuilds that could satisfy ~kde-base/kdm-3.5.7 have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/kdm-3.5.7 (masked by: ~x86 keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by kde-base/kdebase-meta-3.5.7 [ebuild]) I synced a couple of times but these messages related to kde updates reappear, although related to different packages. Is there some trouble in the version synchronization of the new kde ebuilds? Why does stable kdebase-meta require an unstable package? kdm-3.5.7 has been stable for 8 days. Most likely an overlay is overshadowing it (xeffects?). Complain to the maintainer of said overlay. -- Bo Andresen signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: want to ditch kopete
On Thu, 19 Oct 2006 01:29:47 +0200, Harm Geerts wrote: So to point it out once more, this is a workaround! It doesn't solve the problem, it only hides it! Agreed, my first suggestion was the correct solution, but this is far less work. I use it to stop kdebase-meta bringing in kpersonalizer. -- Neil Bothwick PC DOS Error #03: Windows not found: (C)heer (P)arty (D)ance signature.asc Description: PGP signature
Re: [gentoo-user] Pain of migrating to plasma5
On Sunday 15 May 2016 17:50:31 J. Roeleveld wrote: > For 1: check useflags. I remember reading about one when I did the upgrade. > (No access to Gentoo atm) Aha! I had a quick look, the versions which have the +oldwallet flag set are not stable yet. Perhaps the next versions of kde-apps/kdebase-runtime-meta and kde-plasma/kwallet-pam ought to fix the kdwallet migration problem. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
