From: robin_listas@es.invalid   
      
   On 19/10/2021 12.28, Andrew wrote:   
   > Carlos E. R. wrote:   
   >> On 23/09/2021 14.44, Andrew wrote:   
   >>> I have four systems for various purposes, all of them are currently   
   >>> running Leap 15.3.  Updates are applied directly (the Software Updates   
   >>> process after logging in) or via a "zypper up" using ssh-as-root from   
   >>> another machine.   
   >>> This works fine for three of the systems, it is the other one which is   
   >>> confusing me.   
   >>>   
   >>> A remote "zypper up" just applied 15 updates, repeating it showed   
   >>> "Nothing to do".  The trouble is, the message:   
   >>>> The following 101 package updates will NOT be installed:   
   >>   
   >> It is not a problem.   
   >> It just tells you.   
   >> There is nothing to do.   
   >>   
   >>>   
   >>> A remote yast -> Online Update also finds nothing to do.   
   >>   
   >> Obviously, as it is equivalent to "zypper patch", not "zypper up".   
   >>   
   >>>   
   >>> Logging in there locally and letting Software Update run, it comes up   
   >>> with an additional 20 updates.  Applying these - with all the updates of   
   >>> affected packages and libraries - reduces the "will NOT be installed"   
   >>> list to just 5 entries, implying that the 20 + dependencies expanded to   
   >>> 96 - pretty much normal.   
   >>> Any ideas why "zypper up" ignored those 20/96 packages?  This behaviour   
   >>> is normal for this one machine.   
   >>   
   >> Because the priorities and repositories you have defined mandate that   
   >> result.   
   >>   
   >>   
   >> For example suppose I add a repository named "things" that includes   
   >> WonderfulOffice, which I click on it to install, but it also includes   
   >> Thunderbird version 1999, brought from the future, which I do not click   
   >> on it.   
   >>   
   >> "zypper up" will update WonderfulOffice, but not Thunderbird, because   
   >> you told the system you want TH from oss repo, not from "things".   
   >>   
   >> Zypper will not switch "vendor" on your back.   
   >>   
   >   
   > Well, weeks later (it took that long to accumulate enough updates to do   
   > some decent testing)   
   > If I follow "zypper patch" with "zypper up", the second process can   
   > still find something to do.  This is not the case after running   
   > "Software Updates".   
      
   Absolutely normal and expected.   
      
   I don't see any problem whatsoever. The only problem is you expecting   
   something different :-P   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)