Willie Wong schreef: > On Tue, Dec 06, 2005 at 07:56:22PM +0100, Holly Bostick wrote: > >> Ernie Schroder schreef: >> >>> Calculating world dependencies !!! Problems have been detected >>> with your world file !!! Please run emaint --check world >>> >>> I checked for updates to world while I was updating KDE to 3.5 >>> and got the above message. Should I worry yet? >> >> Let's see... you expect one instance of Portage to give reliable >> output while another instance of Portage is updating the relevant >> data that the instance you're looking at is trying to read.... >> > > > Oh! That's what the OP meant... geez, my English parsing skill is a > disgrace to my education. ;-p > > But that's gotta be some very unlucky timing issue to have the read > and write of the world file collide, eh?
Oh, I dunno-- what actually happens to the world file (in terms of ownership/process ownership and locking) at the time that an emerge that affects the world file is being performed? There are reasons that major Portage processes are not supposed to be carried out concurrently. It's true that while I'm upgrading KDE, I probably could emerge... oh, mutt... at the same time in another instance, but checking the entire Portage tree (as in emerge -ua** world) is just not recommended, since Portage can't really be expected to know which updates are really valid (because it's currently performing some of them in another instance, with which it can't communicate). I mean, you could all be quite right, and I wrong, but Istr I got this message when I did something similarly unwise, and after the emerge actually finished, there was nothing wrong anymore (because the left hand knew what the right hand had done). Holly -- [email protected] mailing list
