home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 138,037 of 138,051   
   R Daneel Olivaw to Carlos E.R.   
   Re: Updating with zypper   
   20 Nov 25 20:34:17   
   
   From: Danni@hyperspace.vogon.gov.invalid   
      
   Carlos E.R. wrote:   
   > On 2025-11-20 13:25, R Daneel Olivaw wrote:   
   >> Carlos E.R. wrote:   
   >>> On 2025-11-19 18:04, R Daneel Olivaw wrote:   
   >   
   >   
   >   
   >>> The problem should happen no matter the tool you use, as long as you   
   >>> ask the same thing of them.   
   >>>   
   >>> What I have never seen is a conflict with files from the same patch   
   >>> as appears you get. Maybe you have some repo defined twice. You could   
   >>> post the result of "zypper lr --details" trying to avoid line wrap.   
   >>>   
   >>> Otherwise, ask in the mail list.   
   >>>   
   >>>   
   >>   
   >> This is a tough one - avoiding the line wrap on "zypper lr --details"   
   >> is extremely difficult, but I have a good guess as to what I'm going   
   >> to see (YaST2 shows me what Repos I have, but not in a "text" form).   
   >   
   > Your post had no line wrap :-)   
   >   
   > I use an addon on Thunderbird that can disable or enable line wrap on   
   > the current post being edited.   
   >   
   >>   
   >> The system where this happened yesterday does have some repos defined   
   >> twice, that came from my upgrade to Leap 16.0 followed by an "upgrade"   
   >> to 15.6 a few days later.  There is some 16.0 process which adds repos   
   >> if it thinks they are missing and several are in there twice - one   
   >> "natural" and one from this process.  Deleting the extra ones does no   
   >> good, the process shows up and enters them again.  Maybe I should   
   >> delete the "natural" ones.   
   >   
   > Ah, you have to find and remove that process. The description rings a   
   > bell, but I don't remember what it is.   
   >   
      
   When I list the Repositories in YaST2, the extra ones have "openSUSE" in   
   the Service column, and the url has "?mediahandler=curl2" tacked on the end.   
   They are:   
   - repo-non-oss   
   - repo-non-oss-debug (is not enabled)   
   - repo-openh264   
   - repo-oss   
   - repo-oss-debug (not enabled)   
   - repo-oss-source (not enabled)   
   - update-backports   
   - update-backports-debug (not enabled)   
   - update-non-oss   
   - update-non-oss-debug (not enabled)   
   - update-oss   
   - update-oss-debug  (not enabled)   
   - update-sle   
   - update-sle-debug (not enabled)   
      
   I have cleaned things up by removing the "enabled" flag from all of my   
   previous repositories except packman and mozilla-test, they appear to be   
   duplicates.  I'll see how this pans out over the next couple of days.   
   >   
   >>   
   >> On the other hand, this also happens on my main system, and that one   
   >> never saw 16.0.  I applied the same updates yesterday on the main   
   >> system but without complaints.  This problem does occur on that   
   >> system, just not yesterday.   
   >   
   > I can try updating my laptop, see if there is something. This desktop   
   > was updated four days ago, no issues. But I use YaST.   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca