Abhay Kedia schreef: > On Sunday 29 January 2006 06:41, Ian wrote: >> unmask all of the packages im building in package.keywords. >> > You seem to have added them to package.unmask as well. Don't do that. > > > Just as a note, there doesn't seem to be a choice in this regard (i.e., you have to add kdewhatever-3.5.1 to package.unmask). If I don't add it to package.unmask, I get a halt from Portage because some of the dependent packages that [ nomerge ] packages want to emerge are masked. The only way I've found around it in the past three days is to just go ahead and unmask them, let Portage fail to download then tarballs, and then do a --resume --skipfirst to proceed.
I could of course not --deep the update, but that covers everything, which I don't want. I also upgraded Portage to see if it was a Portage problem, but that didn't help either. It's odd, imo... Portage shouldn't really consider masked packages for updates, but in this case I can't seem to get it to stop. I was also wondering if it was a bug, and in what (KDE, Portage... something). It seems to me that the devs have done this before (put a package in the tree just before it was available, masked), and I can't figure out why its not working this time the way it has in the past. If its something I've done, I can't figure out what But I've been busy, so I've only had time to be annoyed by it, not investigate it. Holly -- gentoo-user@gentoo.org mailing list
