On 08/15/2016 06:02 PM, james wrote: > Well, > > I brought this up before. No need for argument, just test it out > for yourself. > > Multiple times (over the last few weeks) I have run 'emerge -uDNvp @world' > and there are issues to deal with manually. > > For example 'One or more updates/rebuilds have been skipped due to a > dependency conflict', type of fudd and other types of fudd is the result, not > all the time, but maybe 50% of the time. > > > Now, routinely, all I do is immediately issue this command > 'emerge -uDt @world' and go have a coffee. An AMD 8 core, 32G workstation > does it's thang, leaving me a with just a smile after the work is complete. > No other actions, nadda, ziltch. Immediately, I then run 'emerge -uDNvp > world' (again, and routinely I get:: > > "These are the packages that would be merged, in order: > > Calculating dependencies... done! > > Total: 0 packages, Size of downloads: 0 KiB" > > > Just try it for yourself. It's like clockwork now. Smooth. I have over 1500 > packages installed on a mostly stable but hacked out /usr/local/portage/ and > maybe 10% of the packages, that are much newer, but portage is sweet, sweet, > sweet now. There is inherent magic now, but, > I do not have time to ferret it out. Sure I can dive in, manually, > and I have done this to fix things, but, 'emerge -uDt @world' fixes things, > automagically; dozens of times as I update 3 or 4 times a week. > >
I don't know exactly what's going on but I think something is wrong so it's not so sweet. I think you got a conflict that's not being resolved and not being pulled by the second command. What happends if you add --with-bdeps=y --backtrack=30? Also try without the -p (I think it runs more code like autounmask etc so it may cause the extra output). Is clang/llvm stuff still popping up on the list of skipped packages? I remember a similar conflict around the time of your first post and it turned out that the latest stable clang blocks the latest stable libclc. So the tree is (still) broken. For most users it's not a problem because portage pulls the right version of clang but if you have clang on your world file it updates it to the latest and you get those conflicts. I fixed it by masking all versions of clang >3.6 -- Fernando Rodriguez
