From: paulrs@foxinternet.net   
      
   Lately the upgrades offered doing a 'zypper dup' come with numerous   
   problems. Choices made with 4 problems generate 6 or more as I start over   
   again with different choices.   
      
   Most of the problems generated deal with "xxxx" needs "yyyy" which cannot   
   be provided.  Why set forth an upgrade when a dependency cannot be   
   provided? I hesitate to use the "Break it" option, since in many cases I   
   do not know what the package is doing.   
      
   I usually select either "Keep the obsolete" or "deinstall."  Deinstalling   
   then creates problems with other packages using the (to be) deinstalled   
   package as a dependency.   
      
   I've had "Tumbleweed" since 7/2020 and regular "zypper dup(s)" have been   
   mostly straight forward.  It seems that this year, beginning in March,   
   these problems have intensified.   
      
   Sometimes I wish a choice was given: (x)Don't upgrade this if it will   
   generate a problem. The (c) option Cancels the whole upgrade so nothing   
   gets upgraded.   
   A second wish would be every (upgrade) package checks all it's   
   dependencies to see if they are available before being offered.   
      
   Any wise counsel?   
      
   Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)