Dale wrote: > Howdy, > > I don't do emerge -e world very often but this is weird. This is the > complaint emerge spits out: > > > > !!! The following update(s) have been skipped due to unsatisfied > dependencies > !!! triggered by backtracking: > > x11-drivers/nvidia-drivers:0 > x11-base/xorg-drivers:0 > x11-base/xorg-server:0 > x11-drivers/xf86-input-libinput:0 > xfce-base/xfce4-settings:0 > xfce-base/xfce4-meta:0 > x11-drivers/xf86-video-vesa:0 > x11-misc/sddm:0 > kde-plasma/plasma-meta:6 > > > I checked with equery, they all in the tree, installed even. What is > emerge trying to tell me? I also get this which may or may not be > related. > > > !!! Ebuilds for the following packages are either all > !!! masked or don't exist: > app-backup/mkstage4 kde-plasma/plasma-meta > sys-kernel/gentoo-sources:6.9.10 sys-kernel/gentoo-sources:6.9.4 > x11-drivers/nvidia-drivers x11-drivers/xf86-video-vesa xfce-base/xfce4-meta > > > I get the gentoo-sources and mkstage4. It always complains about > those. The others tho, what's emerge fussing about? > > Ideas? I emerge something weird to cause that? Is emerge going wonky > over nothing? > > Dale > > :-) :-) >
The solution to this came after emerge world finished. I did some checking to see what packages it skipped. It turns out that several packages were skipped. I have buildpkg set so all I had to do is look for a package with no binary available using emerge -aek world. I deleted all old binaries to make certain none that may be bad were used given my bad memory stick problem. Anyway, when I was going through those, I realized what emerge was telling me. I usually mask higher versions of gentoo-sources than what I want to keep. I remove the mask when I want to upgrade then reset. Either I forgot, very likely, or mistakenly masked all versions of gentoo-sources. That made emerge to have missing dependencies for a kernel. That meant some packages that require that had to be skipped. So, don't mask all versions of a kernel unless you want to have problems. I might add, I suspect that would affect updates as well as emerge -e world. Now when I do a emerge -aek world, I see that binaries are available for all packages and they should be good ones. That also means all packages have been installed with good memory. No failures either. Oh, I kinda kept a eye on memory usage when qtwebengine was compiling. It seems emerge wants 32GBs of space available when building that monster. As I was watching, at one point it reached 27GBs of memory usage. Now I was logged into KDE and with the little I have running, Seamonkey mostly, it uses about 3GBs. So, if one wants to override that requirement, it needs about 24 or 25GBs of space available. If your mobo only has 24GBs or less, I wouldn't risk it. Odds are, even running with no GUI at all and nothing else using memory, it will be a tight fit at the least. With my current 32GB stick, I had to create and enable some swap. I wonder, why don't they break that thing into two pieces or something???? That's massive. Now to reboot into a system with fresh package installs, built with good memory. Dale :-) :-)
