Summary: | kdebase won't emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gabe Stevens <geekay_es> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | carlo |
Priority: | High | ||
Version: | 1.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kdebase emerge output
kdebase emerge terminal echo |
Description
Gabe Stevens
2003-10-04 21:32:00 UTC
Created attachment 18770 [details]
kdebase emerge output
I've been piping all my emerges into text files for later reference, this
is
the log of the failed kdebase emerge.
Created attachment 18771 [details]
kdebase emerge terminal echo
The previous attachment is the piped output from the emerge command, this
is
the terminal output which requested that I make this bug report. There is
a
whole lot of denied permissions trying to create a .kde in my /root directory.
This is generally an indication of too aggressive USE flags. Please scale them back and retry (especially -O3 -> -O2) For some reason I'll have to emerge kdebase _again_, but it fails with the same error. I don't think this problem has anything to do with USE flags. I don't have a clear idea why it fails, but I'll do some tests. O.k. - I think I got it: Because of Bug #30153 I had to unmerge i2c-2.7.0. That caused ksysguard to present a messegebox that it could not connect to localhost. I searched the forums and found the solution: "emerge kdebase again!". The problem is that kdebase-3.1.4 doesn't compile with the original linux headers, but only with the overwritten ones from the i2c ebuild (at least on my machine). Gabe: Could you please emerge i2c before kdebase and proof if I'm right or wrong!? You know, I guess I need to apologize for how poorly I followed up on this. I tried to emerge kdebase several times and finally just rebooted the computer. I ran emerge kdebase again and it installed just fine, and the rest of the packages in KDE installed just fine. I have no idea what caused the problem, or why rebooting fixed it. In desparation I ran an "emerge -e world" and let it run all day yesterday and things seem to be working just fine now. Looks like it's a worksforme thing now. |