n952162 wrote: > On 2020-06-07 21:30, Rich Freeman wrote: >> On Sun, Jun 7, 2020 at 2:56 PM n952162 <[email protected]> wrote: >> >>> The emerge that I used was this: >>> >>> emerge -auDv --verbose-conflicts --changed-use --keep-going --with-bdeps=y >>> --changed-deps --backtrack=100 @system >> Yeah, you might have to include the other packages that need readline >> if portage complains. >> >> > > This, indeed, seems to have been the magic. > > By specifying *both* @system and @world, two of my machines that I > worried were lost-causes are now updating - hundreds of packages, but > that's okay, I've been pulling my hair out for months. >
For future reference, @world includes @system. My updates tend to work like this: eix-sync && emerge -uaDN world I have the following options in make.conf as defaults. EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5 --quiet-build=n -1 --unordered-display" Emerge applies those as is appropriate. First it syncs the tree and any overlays that are enabled. Then emerge starts building the list of packages that need to be updated. Sometimes if you try to do system by itself, it can cause problems because something in world may depend on something that system is wanting a upgrade. Thing is, that creates a conflict and emerge won't be able to upgrade. If however you upgrade world, which includes all packages, then emerge can include the packages in world and figure out how to update both sets, system and world. Unless you have a really good reason to do so, you shouldn't try to update system by itself. It limits emerge and can lead to issues. The easiest way is to update world and let emerge update everything at once. There may be exceptions to that at times but they are not that often. Hope that helps. Dale :-) :-)
