wierd dependancy problem.

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

Something wierd is going on with the state of emerge on my system. I'm trying to install kde. I've done an "emerge kde" but I get the following response:

humpback · Posted: Tue Feb 04, 2003 6:08 pm Post subject:

try emerge rsync and then try again.. kdelibs 3.1 is nolonger masked either by packages.ask or in the ebuild.
_________________
Gustavo Felisberto
Humpback @ #gentoo-pt
------------
It's most certainly GNU/Linux, not Linux. Read more at
http://www.gnu.org/gnu/why-gnu-linux.html .
-------------

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

Still no go

At this point, I believe I have manually installed all the things that kdebase needs and have done an emerge --nodeps kdebase. Its been compiling for about 3 hours now, without any problems, so I might be safe. We'll see. I wonder if I'll run into that problem down the road though. (this is on sparc platform with ~sparc, in my ACCEPT_KEYWORDS, btw)

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

I think that I might be on to something here, but I'm not sure how to fix it.

aja · Posted: Tue Feb 04, 2003 9:28 pm Post subject:

Have you done the suggested

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

yes, multiple times

aja · Posted: Tue Feb 04, 2003 9:53 pm Post subject:

Maybe it's mine that is out of date. I can'r re-sync from where I am, and mine is from about 20 hours ago. But I am showing v.3.1 (no rc stuff) for that library, and I have it installed. So yours seems older than mine unless the package has been downgraded or masked.

Anyone know if the package has been downgraded in the last day or so or can confirm current version in portage?

Did you try ACCEPT_KEYWORDS="~x86" emerge -p kdelibs ? (Be careful, that environment puts you into 'unstable' mode).

What server are you rsyncing from?

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

It seems to pick a different rsync server everytime I do it.

Anyway, I can't figure out why its doing that.

I found this to work though:

pilla · Posted: Tue Feb 04, 2003 10:26 pm Post subject:

the keyword for sparc is ~sparc, I think, not ~x86.

It is masked as unstable for sparc.
_________________
"I'm just very selective about the reality I choose to accept." -- Calvin

aja · Posted: Tue Feb 04, 2003 10:28 pm Post subject:

Whoa....

I've been assuming you were on x86 (my bad). The problem might be that KDE3.1 has not been declared stable for your platform.

DO NOT USE ~X86 ON A NON X86 PLATFORM

Use your own flag (check out man emerge - near the end), which should be ~sparc or ~sparc64, IIRC. If KDE3.1 shows up, then it is masked for sparc - use at your own risk. Might want to check out bugs.gentoo.org to see if there is something outstanding that you should worry about.

//edit - fixed URL

aja · Posted: Tue Feb 04, 2003 10:33 pm Post subject:

https://bugs.gentoo.org/show_bug.cgi?id=14837

Seems to offer hope... :-)

mrgalihad · Tux's lil' helper Joined: 30 Jan 2003 Posts: 91

well, the fact that the ebuilds for kde3.1 are there for ~sparc, and all its depenacies (includeing kdelibs) make me thing it should work. Its just not seeing the ebuild file for libs. so doing the build pretending that its an x86 just for KDE shouldn't hurt anything, besides, the worst that can happen is it doesn't build. I'm not to terribly worried about it at this time, as its just a "play toy" I'm just wondering if I didn't stumble onto a portage bug....