[gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies

[gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies

[Dale]

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

:-)  :-)

Re: [gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies

[Dale]

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

:-)  :-) 

Re: [gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies

[Michael]

[-- Attachment #1: Type: text/plain, Size: 3823 bytes --]

On Thursday 5 September 2024 08:36:46 BST Dale wrote:
> 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.

Allow 2G-3G of RAM per thread, assuming you have set MAKEOPTS to take 
advantage of all your cores and you do not use swap.  If you don't have enough 
RAM for large packages then a cheaper solution is to set a lower make --jobs 
threshold:

https://wiki.gentoo.org/wiki//etc/portage/package.env


> 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. 

You can blame Google, what with their Chrome browser built to replace your 
browser, online authentication mechanism, mail client, file manager, video 
player, desktop, etc., and if they had a say in this, even your OS.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies

[Dale]

Michael wrote:
> On Thursday 5 September 2024 08:36:46 BST Dale wrote:
>> 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.
> Allow 2G-3G of RAM per thread, assuming you have set MAKEOPTS to take 
> advantage of all your cores and you do not use swap.  If you don't have enough 
> RAM for large packages then a cheaper solution is to set a lower make --jobs 
> threshold:
>
> https://wiki.gentoo.org/wiki//etc/portage/package.env
>

I have mine set to what my system can handle, with both memory sticks of
course.  Since one decided to take a nap on me, now that is reduced. 
Still, one needs to be careful if overriding the defaults on that
package.  That thing is a monster for sure.  I think it sailed past LOo
long ago.  It used to be that LOo was the big one.  Pssst.  Don't tell
LOo or they will add stuff just to get the big one label back.  LOL   I
think one reason they lost that title, they split the package into pieces. 


>> 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. 
> You can blame Google, what with their Chrome browser built to replace your 
> browser, online authentication mechanism, mail client, file manager, video 
> player, desktop, etc., and if they had a say in this, even your OS.

Don't they have a pad thingy that is like a all in one thing? 

Just found a video that has a bad spot.  This is about the time I
noticed gkrellm was stuck too.  Found a good copy still in the QB section. 

Dale

:-)  :-)