| View previous topic :: View next topic |
| Author |
Message |
theRealMorpheu5
l33t
Joined: 26 Feb 2004
Posts: 841
Location: Vicenza, IT
|
 Posted: Fri Sep 14, 2007 11:23 am Post subject: [solved] kdelibs-3.5.7 complains about everything |
 |
|
Hello.
I'm not sure this is the right place to post this issue since it involves xeffects-overlay but I feel it is better to post here than elsewhere. My problem in fact is about an ebuild coming from portage main tree when since yesterday it was from xeffects.
Here's what I was confronted by while upgrading. (Watch out, it's about 3,5M).
I couldn't find mentions of this on Google nor on this forum. What can I do? Any ideas?
Last edited by theRealMorpheu5 on Mon Sep 17, 2007 3:48 pm; edited 2 times in total |
|
| Back to top |
|
 |
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Sep 14, 2007 3:43 pm Post subject: |
|
|
| Are you sure they're the same ebuild? And by that I DON'T mean "Do they have the same version name?" The ebuild in the tree could be different because the ebuild in the overlay is probably tweaked to work with the other bleeding edge stuff that's in the overlay. Then they might've tweaked it again to make it instead work with the stuff that's in the portage tree. |
|
| Back to top |
|
|
IvanMajhen
Guru
Joined: 10 Jun 2006
Posts: 392
Location: Croatia
|
| Posted: Fri Sep 14, 2007 3:48 pm Post subject: |
|
|
OMG! I have the same problem. Last updates borked something. I can't compile any kde-packages.
It looks like linker doesn't see symbols in qt lib.
I'm emerging world with -e flag. This is just stupid... |
|
| Back to top |
|
|
theRealMorpheu5
l33t
Joined: 26 Feb 2004
Posts: 841
Location: Vicenza, IT
|
| Posted: Fri Sep 14, 2007 4:31 pm Post subject: |
|
|
| slycordinator wrote: | | Are you sure they're the same ebuild? |
Nope, not sure. What I don't understand is why Portage is now trying to emerge kdelibs from the main tree instead of taking the overlay. It explicitly says it's doing it: [1=>0] where 1 is xeffects and 0 is main.
If noone has a solution, I can just hope to resync in the next days and find it magically working, but I don't expect it to... |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Sep 14, 2007 4:43 pm Post subject: |
|
|
| theRealMorpheu5 wrote: | Nope, not sure. What I don't understand is why Portage is now trying to emerge kdelibs from the main tree instead of taking the overlay. It explicitly says it's doing it: [1=>0] where 1 is xeffects and 0 is main.
If noone has a solution, I can just hope to resync in the next days and find it magically working, but I don't expect it to... |
Look at your output. Namely the version numbers being installed.
The version in the portage tree is higher than the one in the overlay.
edit: So you can try and mask the portage version then it'll keep the version from the overlay. |
|
| Back to top |
|
|
theRealMorpheu5
l33t
Joined: 26 Feb 2004
Posts: 841
Location: Vicenza, IT
|
| Posted: Fri Sep 14, 2007 5:04 pm Post subject: |
|
|
| That's a workaround, but what about the solution? Is it to just wait and see? |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Sep 14, 2007 5:26 pm Post subject: |
|
|
Maybe you should talk to the xeffects people because this problem appears to be entirely related to it.
Portage (and any other package manager for that matter) defaults to installing the most recent version of a package that's available. And it just so happens that the newest version of that package is in the portage tree. It also happens to be that you installed other stuff from an overlay that this portage tree package isn't compatible with.
This is what happens when you mix bleeding edge stuff with stuff that's not.
In short: If you shoot yourself in the foot you should look at the gun. |
|
| Back to top |
|
|
IvanMajhen
Guru
Joined: 10 Jun 2006
Posts: 392
Location: Croatia
|
| Posted: Fri Sep 14, 2007 9:56 pm Post subject: |
|
|
| Sync portage. It was problem with libtool.eclass. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Sep 14, 2007 10:11 pm Post subject: |
|
|
| Well there we have it. |
|
| Back to top |
|
|
theRealMorpheu5
l33t
Joined: 26 Feb 2004
Posts: 841
Location: Vicenza, IT
|
| Posted: Mon Sep 17, 2007 3:48 pm Post subject: |
|
|
It seems that's working now.
Side question: how can I get rid of everything coming from xeffects overlay? I'm not using Compiz anymore so I don't need special ebuilds. Do I just have to remove the overlay and wait for the next upgrades? |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Mon Sep 17, 2007 4:28 pm Post subject: |
|
|
| theRealMorpheu5 wrote: | It seems that's working now.
Side question: how can I get rid of everything coming from xeffects overlay? I'm not using Compiz anymore so I don't need special ebuilds. Do I just have to remove the overlay and wait for the next upgrades? |
1) Remove the overlay
2) Do | Code: | | emerge world --update --deep --newuse |
In this step anything that's in the portage tree that's older than a version from xeffects will be reinstalled (and if you use "--pretend" it'll show that it's a downgrade, installing older version than the installed one).
3) Then do
That'll get rid of the packages that are from xeffects that aren't needed anymore.
4) And in case the previous step screwed up any linking do
That's what I'd do. |
|
| Back to top |
|
|
theRealMorpheu5
l33t
Joined: 26 Feb 2004
Posts: 841
Location: Vicenza, IT
|
| Posted: Mon Sep 17, 2007 5:44 pm Post subject: |
|
|
| Thank you very much. |
|
| Back to top |
|
|
|
Unsupported Software
