When I did an emerge kde-meta to get 3.5.2 built, when I got to kmail I found out that libkpgp hadn't been built. I could see libkpgp in /usr/kde/3.4/lib but didn't see one in /usr/kde/3.5/lib. I did an emerge of libkpgp by hand and emerged kmail and it worked.
All ebuilds depend on the same major version and kmail depends on certmanager, which depends on libkpgp. Local problem.
I tried this on a second machine with a completely fresh installation and it happened again. So what is the "local problem" - local to what? To 2006.0? Or what?
"Local" in the sense that I can't reproduce this and the dependency chain ensures libkpgp will always be built before kmail. The only way I can think of to break it is via a broken ebuild in your overlay.
This now happened twice from a 2006.0 fresh install. I didn't add any overlay. I followed the installation instructions for 2006.0 and AMD64. When it came to install kde I did emerge kde-meta and walked away.
(In reply to comment #4) > This now happened twice from a 2006.0 fresh install. Well, even if the dependencies should be broken on the release media (looking at the ChangeLogs, I doubt it) there's no time machine to change this. As soon as you run `emerge --sync` you have the current tree and correct dependencies.
Of course I did an emerge --sync; that is part of the procedure! Let's just drop it...it is apparent you aren't going to figure out the problem.
Chuck, it's not that simple to remotely figure out what's going wrong, when you can't reproduce it yourself and we get more invalid bug reports than you might think of. That doesn't mean that it's not worth it, if there really is a problem. Point is, the dependencies fulfill that libkpgp gets built before kmail. Even if I add libkpgp directly as a dependency to the kmail ebuild (which wouldn't be wrong, but is unnecessary), it wouldn't help to find out what the problem is. Raking a bit more: What Portage version are you using?
I know the problem is difficult and I am betting it has more to do with 2006.0 than with kde. I have encountered a number of issues in 2006.0; one big one is that it creates /lib, /lib32 and /lib64 and they are all different! I just don't quite know where to post this bloody issue. All I can tell you is on two different AMD64 ssytems I followed the 2006.0 guide and had the same problem. I know under 2005.2 I didn't see the problem. Past that I don't have a clue.
Cant add anything else....
Once again, Chuck: Stop resolving bugs.
I can't reproduce this either, please reopen with emerge --info if it's still a problem.
No longer a problem.
