Am 02.04.22 um 11:28 schrieb Mathias Homann:

Am Samstag, 2. April 2022, 11:22:05 CEST schrieb Daniel Bauer:

...

Are the programmers of those sites stupid or is my OS 15.1 so very outdated?

in short: yes long form: yes, the most supported version is 15.3, so you are TWO releases behind. By the way, 15.3 has firefox 91 so your FF 78 is outdated all on its own...

cheers MH

oh, technology moves faster than I :-) so it seems that it is time for the feared upgrades.... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

On 2022-04-02 15:26, jdd@dodin.org wrote:

Le 02/04/2022 à 12:27, Daniel Bauer a écrit :

...

oh, technology moves faster than I :-) so it seems that it is time for the feared upgrades....

yes. I still have to accept the change from ifconfig to ip :-(.

ifconfig is in package "net-tools-deprecated-2.0", so you still can use it if you wish. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

On 2022-04-02 19:59, jdd@dodin.org wrote:

Le 02/04/2022 à 19:53, Carlos E. R. a écrit :

...

On 2022-04-02 15:26, jdd@dodin.org wrote:

...

Le 02/04/2022 à 12:27, Daniel Bauer a écrit :

...

oh, technology moves faster than I :-) so it seems that it is time for the feared upgrades....

yes. I still have to accept the change from ifconfig to ip :-(.

ifconfig is in package "net-tools-deprecated-2.0", so you still can use it if you wish.

but not available as default in most distro, so unusable when fixing problems on alien machines :-)

Oh, I see. I just like the print format of "ifconfig" with no parameters, I don't use it for anything else.

and I *have* to follow, and ip is not that new anymore, but I had a hard time learning ifconfig and ip is hard also :-)

-- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Am 02.04.22 um 21:14 schrieb Dave Howorth:

On Sat, 02 Apr 2022 11:28:29 +0200 Mathias Homann wrote:

...

Am Samstag, 2. April 2022, 11:22:05 CEST schrieb Daniel Bauer:

...

Are the programmers of those sites stupid or is my OS 15.1 so very outdated?

in short: yes long form: yes, the most supported version is 15.3, so you are TWO releases behind. By the way, 15.3 has firefox 91 so your FF 78 is outdated all on its own...

yes isn't really an answer to a question that says Is it A or B!!!! :)

Assuming you meant B is correct, I'd disagree (but that's my humble opinion). I don't mind mozilla producing lots of upgrades. I do mind web site designers depending on those new upgrades and not providing a means of graceful degradation to older releases! And the notion of graceful degradation has been around for so long that it seems reasonable to me to call people who don't follow it 'stupid'.

It is not just features, which were added to new firefox releases, updates also fix security holes which could "... execute arbitrary code on compromised systems ...". e.g. https://thehackernews.com/2022/03/2-new-mozilla-firefox-0-day-bugs-under.htm.... You decide, how important that is. Peter

Am 02.04.22 um 12:16 schrieb Carlos E. R.:

On 2022-04-02 11:22, Daniel Bauer wrote:

...

Using Firefox 78.7.0esr (64 bit) on Opensuse 15.1 on several websites (tumblr, a bank, some others) I get a message like

"You are using an unsupported browser and things might not work as intended. Please make sure you're using the latest version of Chrome, Firefox, Safari, or Edge."

Are the programmers of those sites stupid or is my OS 15.1 so very outdated?

I think there have been changes in the encryption protocols (for https). Besides that, there have been found many security holes in that time that have been plugged.

Maybe you can get a modern version directly from the firefox site that works.

...

(I restrain from updating/upgrading because of the huge amount of work that a new install brings with it [direct upgrades haven't worked for me in the past, left a lot of confusion in /home in app properties of changed versions etc., and because of some missing programs in the new versions, like support for my many reiserfs backup disks)

Well, upgrades in Leap from one minor version to the next are minimal. The longer you wait, the jump size and the pain increases.

The upgrades never touch the home partition, anyway.

About reiserfs, it was going to happen one day. You should not have any problem reading them, though.

There is another issue, though: encryption system change with the years, you should consider to reformat those disks with modernized encryption. It is possible that older disks are vulnerable.

I have a similar problem, though: I have reiserfs backups on DVDs.

thanks. so I will put my time his weekend into upgrade to 15.2 then to 15.3, hoping to follow (and understand) the correct how-to I find on the web :-) I am updating the complete backup's right now, before I start. Knock on wood.... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

Am 02.04.22 um 13:02 schrieb Carlos E. R.:

On 2022-04-02 12:26, Daniel Bauer wrote:

...

Am 02.04.22 um 12:16 schrieb Carlos E. R.:

...

On 2022-04-02 11:22, Daniel Bauer wrote:

...

thanks. so I will put my time his weekend into upgrade to 15.2 then to 15.3, hoping to follow (and understand) the correct how-to I find on the web :-)

I am updating the complete backup's right now, before I start.

Knock on wood....

Ask me, I have upgraded all the way since SuSE 6.2 :-D

You can upgrade using zypper dup (online upgrade) or rebooting from DVD and choosing upgrade (offline upgrade). I recommend the later, but it will not tolerate any reiserfs present in fstab.

https://en.opensuse.org/SDB:System_upgrade

https://en.opensuse.org/SDB:Offline_upgrade

I wrote the later (most of it), so ask me ;-)

Ha! I followed this (https://en.opensuse.org/SDB:System_upgrade) with a strange result: after rebooting I am still on 15.1... It downloaded approx. 5200 files, at the end of the download it said "end with error". I rebooted. There is one repository (graphics) that is outdated. I deactivated it prior to all the rest and said "ignore" for the warnings during the downloads. I did everything in a virtual console (ctrl-alt-F1) on runlevel 5. (I have no internet on level 3) - the repo-upate of 15.1 is enabled - zypper --releasever=15.2 refresh - zypper --releasever=15.2 dup --download-in-advance it downloaded and ended as described. What now? Do the same again? -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

Am 02.04.22 um 20:22 schrieb Carlos E. R.:

On Saturday, 2022-04-02 at 14:55 +0200, Daniel Bauer wrote:

...

Am 02.04.22 um 13:02 schrieb Carlos E. R.:

...

On 2022-04-02 12:26, Daniel Bauer wrote:

...

Am 02.04.22 um 12:16 schrieb Carlos E. R.:

...

On 2022-04-02 11:22, Daniel Bauer wrote:

...

...

You can upgrade using zypper dup (online upgrade) or rebooting from DVD and choosing upgrade (offline upgrade). I recommend the later, but it will not tolerate any reiserfs present in fstab.

https://en.opensuse.org/SDB:System_upgrade

https://en.opensuse.org/SDB:Offline_upgrade

I wrote the later (most of it), so ask me ;-)

...

Ha! I followed this (https://en.opensuse.org/SDB:System_upgrade) with a strange result: after rebooting I am still on 15.1...

...

It downloaded approx. 5200 files, at the end of the download it said "end with error". I rebooted.

...

There is one repository (graphics) that is outdated. I deactivated it prior to all the rest and said "ignore" for the warnings during the downloads.

Nono, you could have left it. The entire 15.2 is outdated, it doesn't matter. Disabling a repository that contains packages not in the main distro means those packages are deleted.

...

I did everything in a virtual console (ctrl-alt-F1) on runlevel 5. (I have no internet on level 3)

Oh. Using wifi, perhaps? Network manager?

There is a command line interface to network manager you can use in text mode to get internet: nmcli.

...

- the repo-upate of 15.1 is enabled

Ok, I see. I interpreted the text on the web-page so that I must leave this.

This is the culprit.

...

- zypper --releasever=15.2 refresh - zypper --releasever=15.2 dup --download-in-advance

...

it downloaded and ended as described.

...

What now? Do the same again?

I am not fully sure that 15.1 supported the "releasever" variable, maybe yes, but something was wrong. The test is doing:

zypper lr --details | less

all pointed to 15.1

Or rather:

zypper --releasever=15.2 lr --details | less

and carefully examine the results, so that ALL the active URLS point, in your case, to 15.2. If one is wrong, go to directory "/etc/zypp/repos.d/" and edit the bad file so that it either has the correct $releasever variable or the correct number.

I've seen now that only some had the $releasever variable. In one I could replace /15.1/ by /$releasever/ but others had URLS like http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.1/ and I don't know how to change them to a $releasever-URL... so I just changed the number.

Repeat till the output is clean 15.2, then do:

zypper --releasever=15.2 refresh zypper --releasever=15.2 dup --download-in-advance

Ok, that worked. Thank you, Carlos! I had a minor problem, though. I have an nvidia-card and once I marked the nvidia drivers as "do not change" (because I've read somewhere that updates may disturb). So they were not updated, and the screen showed in a lower resolution, distorted to the different side ratio... I updated those "blocked" NVidia drivers, and here I am. Now memorizing your hints for continuing to 15.3. Knock on wood! -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

Am 02.04.22 um 22:41 schrieb Carlos E. R.:

On 2022-04-02 22:27, Daniel Bauer wrote:

...

...

I am not fully sure that 15.1 supported the "releasever" variable, maybe yes, but something was wrong. The test is doing:

zypper lr --details | less

all pointed to 15.1

...

Or rather:

zypper --releasever=15.2 lr --details | less

...

and carefully examine the results, so that ALL the active URLS point, in your case, to 15.2. If one is wrong, go to directory "/etc/zypp/repos.d/" and edit the bad file so that it either has the correct $releasever variable or the correct number.

I've seen now that only some had the $releasever variable. In one I could replace /15.1/ by /$releasever/ but others had URLS like http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.1/ and I don't know how to change them to a $releasever-URL...

so I just changed the number.

baseurl=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_${releasever}/

Actually, I am using the number, not the variable. I had problems somewhere forgotten.

...

...

Repeat till the output is clean 15.2, then do:

zypper --releasever=15.2 refresh zypper --releasever=15.2 dup --download-in-advance

Ok, that worked. Thank you, Carlos!

Welcome :-)

...

I had a minor problem, though. I have an nvidia-card and once I marked the nvidia drivers as "do not change" (because I've read somewhere that updates may disturb). So they were not updated, and the screen showed in a lower resolution, distorted to the different side ratio...

I updated those "blocked" NVidia drivers, and here I am.

You can lock the nvidia drivers only while staying on the same release, but once you upgrade the release and the kernel, the drivers need to be updated as well.

...

Now memorizing your hints for continuing to 15.3. Knock on wood!

I can light a candle ;-p

Your candle helped a lot Carlos :-) Upgrade from 15.2 to 15.3 went easy and straight forward. Still, the NVidia drivers were obviously not updated during the upgrade and after boot into 15.3 I had the small resolution desktop again. When I opened Yast it showed me two NVidia packets needing update, so I did that and rebooted. Still wrong resolution and Nvidia not used. I searched for all Nvidia in Yast and updated all of them again. After reboot now I have Nvidia working and the screen looks good :-) Thanks again for the help! -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

Am 03.04.22 um 12:34 schrieb Carlos E. R.:

On 2022-04-03 11:47, Daniel Bauer wrote:

...

Still, the NVidia drivers were obviously not updated during the upgrade

Why obviously not upgraded? Did you lock them, or not include the repo?

I don't know. No, they were not locked (I unlocked them using OS 15.2) and the NVidia repo was/is included. When starting Yast (without Nvidia and the wrong resolution) for the first time, Yast showed two Nvidia packages to update. But updating them/reboot did not solve the problem. there are 4 Nvidia packages installed. I updated all of them (although to the same version, so more a re-install than an update) and that solved the problem after reboot. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

Daniel Bauer composed on 2022-04-02 22:27 (UTC+0200):

I've seen now that only some had the $releasever variable. In one I could replace /15.1/ by /$releasever/ but others had URLS like http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.1/ and I don't know how to change them to a $releasever-URL...

so I just changed the number.

I have around 30 15.2, 30 15.3, and 20 15.4 installations. Most at one time were 15.1 or 15.0 or older, and upgraded with zypper to get to where they are. All their .repo files include the literal version number within the URI lines. The vast majority are actually using copies of the very same files. At first installation of an alpha I create a "standard" .repo file set. Each set gets copied to wherever needed over the LAN. At release, each gets a new timestamp to match the release date, so e.g. for 15.3 they now show up like so: # ls -Gg /etc/zypp/repos.d/*repo -rw-r--r-- 1 246 Jun 2 2021 /etc/zypp/repos.d/KDE3.repo -rw-r--r-- 1 137 Jun 2 2021 /etc/zypp/repos.d/Libdvdcss.repo -rw-r--r-- 1 260 Jun 2 2021 /etc/zypp/repos.d/Mozilla.repo -rw-r--r-- 1 153 Jun 2 2021 /etc/zypp/repos.d/NonOSS.repo -rw-r--r-- 1 143 Jun 2 2021 /etc/zypp/repos.d/OSS.repo -rw-r--r-- 1 235 Jun 2 2021 /etc/zypp/repos.d/Packman.repo -rw-r--r-- 1 255 Jun 2 2021 /etc/zypp/repos.d/PackmanE.repo -rw-r--r-- 1 129 Jun 2 2021 /etc/zypp/repos.d/Update.repo -rw-r--r-- 1 240 Jul 27 2021 /etc/zypp/repos.d/UpdateBP.repo -rw-r--r-- 1 145 Jun 2 2021 /etc/zypp/repos.d/UpdateNonOSS.repo -rw-r--r-- 1 135 Jun 2 2021 /etc/zypp/repos.d/UpdateSLE.repo For the first six months following release, these listings included TOD, which for 15.3 was 15.03. There's one date/time stamp exception for 15.3, since all ultimate defaults didn't exist on the release date. I use OFMs, so file listings the vast majority of the time resemble the above list. As a result, changes to standards I typically notice on visit to various config directories, leading to question why, and whether I want it to stick. Note the names each contain only one instance of the string ".repo". -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata