On Fri, 12 May 2006 02:25:30 -0700, Richard Fish wrote: > > Which begs the question that if attempting to rebuild all the packages > > in a working system indicates blockers, how did the system get in that > > state and why did portage not indicate a blockage when the > > incompatible packages were installed or upgraded?
Because you are upgrading the packages. The versions you currently have installed are not blockers, but the new versions are different. > How are you doing your updates? If you are not using the --deep > option, I am not surprised that you never saw the blockers before, > because portage will consider _only_ those packages actually in world > for an update unless you use --deep. That's not necessarily true, depending on the command used to update world. "emerge world" only updates any packages in world and any forced dependency updates. "emerge --update world" also considers first level dependencies and updates those, even if the existing version satisfies the world packages' dependencies. As you say, "emerge --deep --update world" goes right down the tree. The only packages --deep misses are those that are not in world and not dependencies of world, i.e. non-dependent packages emerged with --oneshot. -- Neil Bothwick Facts are stubborn, but statistics are more pliable
signature.asc
Description: PGP signature
