From: robin_listas@es.invalid   
      
   On 2022-07-21 04:40, bad sector wrote:   
   > On 7/17/22 09:24, Carlos E. R. wrote:   
   >> On 14/07/2022 21.15, Andrew wrote:   
   >>> Carlos E. R. wrote:   
   >>>> On 17/06/2022 22.20, bad sector wrote:   
   >>>>> N.B. during upgrade, dependency check offered to replace many Leap-15.3   
   pacman packages with suse Leap-15.4 packages, offer accepted in view of recent   
   discussion to the effect that (zypper) knows which packages SHOULD be from   
   pacman.   
   >>>>   
   >>>> I don't remember.   
   >>>>   
   >>>> But you should have the pacman repo enabled (for the target distribution)   
   during the zypper dup procedure, and with a lower number priority.   
   >>>>   
   >>>> In that situation, zypper should know what to do.   
   >>>>   
   >>>   
   >>> As an aside, Leap 15.4 warns you that those priority numbers are now   
   ignored.   
   >>>   
   >>   
   >> AFAIK, that warning has been there for some years, but it was not true.   
   >>   
      
   >   
   > see what  mean?   
   >   
   > There's FAAAAAAR too many rumors and urban legends   
   > for a 'supposedly mature' distro.   
      
   It is not an urban legend, it is an actual error message from the   
   software that has been there for some years. The actual situation and   
   actual meaning is confusing.   
      
   > End users should   
   > not have to muck with ANY of this shit, even repo   
   > handling should be seamless and entirely transparent.   
   > Anyway, I'm back to where I was, got packman essentials   
   > as well as packman enabled, selected as to-be-used,   
   > and using only Yast as far as Leap is concerned. I'll   
   > use zypper in Tumbleweed, then revise everything once   
   > the future of Leap gets cleared up.   
   >   
   >   
   >   
   >   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)