i just did a 'zypper up' on my 42.3 installation and it seemed to go fine -- is there a time (soon?) when it will fail? On Thu, Jul 4, 2019 at 7:29 AM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 04/07/2019 00.29, David C. Rankin wrote:
On 07/03/2019 12:49 PM, Anton Aylward wrote:
So, perhaps, updating all and I mean ALL my repos from 42.3 to 15.0 (after establishing that exists for each and every one of them) and doing the "dup" for all of them might be the best way to preserve things. That is, not starting with a zapped RPM database.
Yes, amazingly, all these years I've just done fresh installs, never trusting this (Voodoo) of duping to another release -- But... if it works, I would save hours of getting everything going and I suspect with --no-recommends set, it should be a sane package for (existing package) update.
Be sure to run, after done, this:
rpmconfigcheck
It produces an output like this:
Telcontar:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/usr.lib.dovecot.auth.rpmnew /etc/apparmor.d/usr.lib.dovecot.config.rpmnew /etc/apparmor.d/usr.lib.dovecot.dovecot-lda.rpmnew /etc/apparmor.d/usr.sbin.smbd.rpmnew /etc/my.cnf.rpmnew /etc/pam.d/login.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/rsyslog.conf.rpmnew /etc/ssh/ssh_config.rpmnew /etc/ssh/sshd_config.rpmnew Telcontar:~ #
The procedure then is to verify each of those against the config file, like this:
meld /etc/ssh/sshd_config.rpmnew /etc/ssh/sshd_config &
And see what changes I want to apply or keep.
For example, the first line is:
# $OpenBSD: sshd_config,v 1.101 2017/03/14 07:19:07 djm Exp $
compared to
# $OpenBSD: sshd_config,v 1.98 2016/02/17 05:29:04 djm Exp $
So I overwrite. Just a mouse click. Finish review of the file, and save.
Repeat for all the files, till the list is empty.
Like I wrote in response to Carlos, worst case scenario, it all goes to hell and I reformat / and roll /home back in when done.
Yes, having a full backup is a good thing at this point. I recomend it.
My biggest concern in the Nvidia drivers. The rest is just vanilla 42.3, so from the threads over the past year or so, the base zypper dup seems OK for most (minus a network connection problem, etc..), but if the Nvidia drives don't get updated, I can see being left without X until I can get that sorted (which will be fine as long as I have a full mult-user target to make the repairs in)
Normally, you simply have the NVidia repo enabled, and it is updated just fine. The problem was specific to 15.1.
In case of problems, my recommendation is to repeat the upgrade of each nvidia rpm by hand (command rpm) and watch carefully the output. I hit a problem where the script failed, but the rpm command is not told about it and claims success.
-- Cheers / Saludos,
Carlos E. R. (from 15.0 x86_64 at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org