On 19 January 2008, Paul Salters wrote: > On Saturday 19 January 2008 16:52:45 Δημήτριος Ροπόκης wrote: > > On Sat, 19 Jan 2008 17:42:55 +0200, Dale <[EMAIL PROTECTED]> wrote: > > > Uwe Thiem wrote: > > >> Hi folks, > > >> > > >> after the painful and time-consuming creation of > > >> /etc/portage/package.unmask > > >> for KDE 4, <emerge --pretend --verbose "=kde-base/kde-meta-4.0.0" > > >> tells me: > > >> [blocks B ] <kde-base/kdebase-3.5.7-r6 (is blocking > > >> kde-base/kdelibs-4.0.0) > > >> > > >> I do not have emerge kdebase-3.5.7 but kdebase-3.5.8. The3refore, I > > >> cannot > > >> unemerge 3.5.7. How can I work around this? > > >> > > >> Uwe > > > > > > For future reference, check out autounmask. I found out about it the > > > other day. I have not used it yet but I'm hopeful it works. > > > > > > Also, there is a thread on the forums about this, I think you have to > > > have 3.5.8* version to do this. Not sure why tho. Isn't KDE 4.0 > > > slotted? Can't you have 3.5 AND 4.0 installed and select which version > > > you want to log into? > > > > > > Dale > > > > > > :-) :-) > > > > Autounmask looks to work, > > but some packets with ~86 I think need manual check. > > hi, > > you need to unmask kde-base/kdebase-3.5.7-r6 and emerge that. > should work :)
??? According to emerge, kdebase-3.5.7-r6 is *blocking* kdelibs-4.0.0. See my original post. Uwe -- If a man speaks in a forest, and no woman listens to him, is he still lying? -- gentoo-user@lists.gentoo.org mailing list
