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
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
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
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
$ 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
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
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 maske
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
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
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 &qu
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
. 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
>
> > 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.
> >
> > !!
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
.
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
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
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
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
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
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
>
> !!! 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:
> pa
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
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
. 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
-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
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
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
-kde
kde-base/kdeadmin-meta
kde-base/kdeartwork-meta
kde-base/kdebase-meta
kde-base
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
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
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
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
> >
> > 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.
&
gt;
>
>
> !!! 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:
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
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
/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
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
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
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
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
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
/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
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
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
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
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
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
* 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
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
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
.
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
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
(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
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
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
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
/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
-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
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
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
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
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
> >
> > >
> > >
> > > # emerge -uDv @world
> > >
> > >
> > >
> > > These are the packages that would be merged, in order:
> > >
> > >
> > >
> > > Calculating dependencies... done!
> > >
> &g
.
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
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
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
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
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
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
/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
ich 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
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
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
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
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
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
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
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
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
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
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
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
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
-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
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
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
.
(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
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
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
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
-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
-data
kjots ksnapshot
artsplugin-akode kdebase-kioslaves
kjsembed ksokoban
artsplugin-audiofile kdebase-meta
kjumpingcube kspaceduel
artsplugin-mpeglib kdebase-pam
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
/ # 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
/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
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
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
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
e-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.
1 - 100 of 311 matches
Mail list logo
