Alan McKinnon wrote: > On Tuesday 06 February 2007, Dale wrote: > >> Dale wrote: >> > > First off, I get the same behaviour this end. kwrite borks out on > emerge.log which is about 8M. On a machine with 2G ram this should not > happen. It does the same thing as a kpart in konqueror > > >> Well, I'm trying to mask this so it will not upgrade when I do >> updates. I must be missing something here. When I did the pretend >> downgrade it pulled kdelibs down one version too. So I want to make >> it so that kdelibs and kate will stay at 3.5.5 versions. This is >> what I added to >> >> package.mask: >> >>> =kde-base/kate >>> -3.5.6 >>> =kde-base/kdelibs-3.5.6-r2 >>> > > That will mask those versions, and only those versions. The next upgrade > of either will be emerged. Is this what you want? >
I think so. I just want kate to stay at that version because it is borked. Since kdelibs is a dependancy, I assumed I needed to mask it too. > >> That way if there is a new release it will upgrade and hopefully it >> will >> >> be fixed. However, this is what happens when I check for updates: >> >>> [EMAIL PROTECTED] / # emerge -uvDp world >>> >>> These are the packages that would be merged, in order: >>> >>> Calculating world dependencies \ >>> !!! All ebuilds that could satisfy "~kde-base/kate-3.5.6" have been >>> masked. >>> !!! One of the following masked packages is required to complete >>> your request: >>> - kde-base/kate-3.5.6 (masked by: package.mask) >>> >>> For more information, see MASKED PACKAGES section in the emerge man >>> page or >>> refer to the Gentoo Handbook. >>> (dependency required by "kde-base/kdebase-meta-3.5.6" [ebuild]) >>> > > See this line above? It says that kdebase-meta-3.5.6 requires kate-3.5.6 > but that can't be fulfilled because you masked it. > > I see two viable options: > > 1. Put up with it and use vi instead (this is the recommended one...) > 2. Make your own local copy of kdebase-meta-3.5.6.ebuild and put it in > your overlay. Modify the ebuild the use any kdelibs and kate > 3.5.5, > this should satisfy the dependedcies. > > The other option is to downgrade all of kde to 3.5.5 but that's just > overkill :-) > > > alan > > Well, I like nano better but not if I can use something GUI. ;-) That option is not exactly what I am hoping to use. I don't understand portage and ebuilds well enough to do that. How about this. Is there a way to just tell emerge to emerge each separate package and get rid of kde-meta? I don't know, equery list kde then poke them in one by one. Would that let it leave kate and kdelibs where it is without masking all of kde? Thanks for the reply though. At least I can open the file and read it and it is not just me having this problem. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
