On 2/26/07, Alan McKinnon <[EMAIL PROTECTED]> wrote:
On Sunday 25 February 2007, Mark Knecht wrote:
> Hi,
> I've been cleaning up a machine trying to fix a problem with
> Evolution crashing. I'm down to the point where all the dependencies
> (emerge -DuN and revdep-rebuild) are clean but when I run emerge
> --depclean wants remove packages that would break dependencies.
Hi Mark,
OK, so I read this thread and you and Bo both seem to have gotten way
off track...
No, not really, at least for me. I've got multiple problems here:
1) Evolution crashes
2) emerge --depclean wants to remove things that seem to be
dependencies for installed programs
3) While building things to get up to date I get all these libtool
warning messages which I started to think might be somehow the root
cause of #1 or #2 above.
I'd like to fix all three and to Bo's credit he's doing everything he
can to help a poor old user type like me.
You have a bunch of packages that --depclean wants to remove. It looks
like they should not be removed. This screams two questions at me:
1. Did you emerge -avC gnome?
No. The machine is 4 years old. It ran fluxbox for about a year and
then has run Gnome ever since. Evolution has been used in both
environments and worked perfectly until moving from Gnome-2.14 to 2.16
a week or so ago. The gcc-4.1 upgrade was done at Christmas and
Gnome-2.14 and Evolution-2.4 worked fine after that upgrade but not
now. I'm currently looking for the root cause if these crashes.
Not being a developer the first thing I thought to do was look to see
if all the dependencies were clean so basically I did:
eix-sync
emerge -pvDuN world
revdep-rebuild
until everything looked good. I then look a look at emerge --depclean
and saw that there were about 60 packages that it wanted to remove. I
worked my way through each and every one doing an equery depends,
removing it if there were no dependencies, and then every so often
running revdep-rebuild again. However what I started finding as I got
to the end of the process was that out of the 60 packages ot be
removed 15 showed that something at the application level - Gnome,
Evolution, spamassasin, etc., that needed something that --depclean
wanted to remove.
For kicked I did an emerge -C on one package and then immediately did
a revdep-rebuild. The system emerged what I just removed. That's when
I contacted the list.
2. If you never had gnome installed but did have evo installed, then
removed evo, everything looks proper.
So, let --depclean do it's thing. Then emerge -uND world and run
revder-rebuild to fix anything that remains.
Based on my response above should I be doing this? From the info I
posted earlier if I emerge -C jasper, as --depclean wants to do, then
it seems it will just be emerged again at emerge -DuN world.
I'm happy to do it if it's the right thing to do. I'm just not
understanding why it should fix things.
Thanks much,
Mark
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
--
gentoo-user@gentoo.org mailing list