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,111 of 138,051    |
|    Carlos E.R. to Batchman    |
|    Re: Update problems    |
|    04 Nov 20 00:47:34    |
      From: robin_listas@es.invalid              On 03/11/2020 22.06, Batchman wrote:       > On Tue, 3 Nov 2020 03:55:24 +0100, Carlos E.R. wrote:       >       >> [snip]       >> Or, keeping the packman repo may avoid a lot of question by zypper about       >> changing this or that package or not, and avoid later work.       >>       > Have retained your information for the future, thanks.       >       > Summary of contents of `rpmlist' output file from your clever code...       >       > Lines referring to version 15.2 = 3075       > Lines referring to version 15.1 = 89,       > of these 37 were applied by the 15.1 -> 15.2 update.       >       > Those 37 items comprise 6 packages and Samba & Gvfs comprise 31 of those       items.       >       > The total lines (items) in the file = 3164       >              Ok. What I do (that command line concoction is on one of the wiki links,       because I wrote it ;-) ) is (I think it is also on the wiki):              Fire up:              su       yast2 --qt sw_single                     or yast and software module from the menu. You click on "search" and       type a faulty package name. Click on the version tab, and then select       the 15.2 version of that package which should show on the list below.              Boringly repeat for the hopefully less than a hundred lines :-)                            I guess that some of the 15.1 hits will be PGP signatures. Other may be       from repositories that do not follow the exact naming convention. Those       that are truly wrong you have to force the update, but beware that some       will not exist.              "Will not exist" maybe because the package is no longer available,       changed name, or something. You have to think about each one. Maybe you       have to abort and add some repository that was disabled during the       update - which is why I do not recommend to disable extra repositories.              Have luck :-D                     The only problem with the wiki is that we (the community) don't update       it so often, but there are no big changes, only details.              --       Cheers, Carlos.              --- 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