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 137,346 of 138,051    |
|    Carlos E. R. to Andrew    |
|    Re: Updates, Zypper and other paths    |
|    23 Sep 21 19:16:02    |
      From: robin_listas@es.invalid              On 23/09/2021 16.27, 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.       >>       >       > You are saying that zypper uses a different repository set to "Software       > Update"? On this one system?              Nope, I did not say that.              I don't know what repos you have defined, so I used a fictional one as       example of what is going on.              Your question is an often asked one, and it simply is a misunderstanding       on your side of what "zypper up" should do.              Zypper up is doing the correct thing.              --       Cheers,        Carlos E.R.              --- 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