Neil Bothwick wrote:
On Thu, 17 Dec 2009 15:12:19 -0600, Dale wrote:
You are both right. I tried installing a later version on the blockers
but not the packages that depended on them. So, I added the following
to my package.keyword and package.unmask files:
=app-portage/eix-0.18.3
=app-arch/libarchive-2.7.1
Portage is now happy. Every time I think I have figured out portage
and these blocker messages, I get thrown a curve ball. lol
Ah, the fun of running a mixed arch/~arch system :)
BTW ~ is usually better than = in this situation.
Well, this ain't working as well as I would like. I'm getting a lot of
failures. Something like this:
* subversion check out start -->
* repository: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk
svn: Network connection closed unexpectedly
* ERROR: kde-base/kate-9999 failed:
* subversion: can't fetch to
/usr/portage/distfiles/svn-src/kdesdk/kdesdk from
svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk.
I may just go back to a more stable setup. My network is working fine
for everything else. It's not just this one package, it is several of them.
Oh well. I just wish they had supported KDE 3 longer cause KDE 4 is
just not ready for what I do. I get a screen full of crap about KDE 3
being masked when updating too. Sort of bugs me.
Dale
:-) :-)
