On 2021-07-20 8:35 p.m., TomasK wrote:

On Tue, 2021-07-20 at 17:22 -0600, Darryl Gregorash wrote:

...

...

More specifically, what do I have to do to set up the repositories for keeping Leap 15.3 properly updated (when I get around to installing it, that is)?

If you download the ISO image and write it to a USB stick, you won't have to do anything except click a few radio buttons. Grab the network install image, and when you boot to it, choose "update" instead of "new installation". During the update process, you will be asked to confirm if you want to keep or delete all your previous repositories -- the default is to delete them. You can let the update process remove/replace all the openSUSE repos, but may wish to keep others you've installed, such as Packman. If you keep any, you will need to edit them to make sure the URLs reflect the version upgrade. If you choose instead to use zypper for the upgrade (zypper dup....), you will need to edit all the repo URLs yourself.

Is that general advice how 15.3 suppose to be installed these days - after the announcement? Boot network image and update instead of install?

I did not get the comment about keeping repositories - from the installation media? Do I need to install 15.2 first for this new 15.3 installation process to work?

That certainly would be significant change worth describing in detail on the ISO download page.

-T

The OP spoke of updating, rather than doing a fresh install. It is always a good idea to do an update from the most recent previous version, ie. 15.1 to 15.2 to 15.3 for example. I certainly did not say that updating is preferred over doing a fresh install. If that is what you wish to do, then nothing of what I said applies to you. Finally, this is certainly *not* a "new" installation process. From the DVD/USB image, you have always had a choice to do a new installation, or to update a previously installed version. Description in detail is not necessary anywhere, because the choices are so obvious when you boot from a DVD/USB install image.

On 2021-07-20 9:41 p.m., Robin Klitscher wrote:

I could have been clearer I guess. My problem was worry about the repos to activate to keep 15.3 properly updated *after* a fresh install....

If you choose "upgrade" from from a USB installation image, you will be presented with a list of all your current repos, and will be asked if you wish to keep any of them. Any that you have installed yourself can be checked to be kept and you will be able at that time to edit the URLs to point to the 15.3 repos. I suggest you change all version numbers (e.g. 15.2) to $releasever, which Yast, zypper, etc will always translate to the proper number. If you do not believe me, go into YaST/Repositories right now and edit a repo to make that change. Then you will see that YaST properly interprets this as follows: URL: http://download.opensuse.org/distribution/leap/15.3/repo/oss/ Raw URL: http://download.opensuse.org/distribution/leap/$releasever/repo/oss/ (You may need to restart the repositories module to see this.) Then the proper repos for 15.3 will be used during the upgrade process, and you will not be faced with any after-install mess of re-installing those repos and updating all that software to reflect this. As I mentioned in another reply to you, I kept the Packman and libdvdcss repos when I did my upgrade, and all worked as intended.

On 2021-07-20 11:04 p.m., Robin Klitscher wrote:

...

(Even to the point of educating me. I had no idea of the "releasever" option - I guess because I first did it using the literal URLs more than 20 years ago and had been doing it that way, slavishly and unquestioned, ever since.)

I only discovered that quite recently, when I was about to upgrade to 15.3. It's mentioned somewhere in the release notes for that version, iirc. Before that, I was using the same brute force method you have been using.

On Wed, 2021-07-21 at 15:41 +1200, Robin Klitscher wrote:

On 21/07/2021 15:28, Darryl Gregorash wrote:

...

On 2021-07-20 8:35 p.m., TomasK wrote:

<........>

...

...

The OP spoke of updating, rather than doing a fresh install. It is always a good idea to do an update from the most recent previous version, ie. 15.1 to 15.2 to 15.3 for example. I certainly did not say that updating is preferred over doing a fresh install. If that is what you wish to do, then nothing of what I said applies to you. Finally, this is certainly *not* a "new" installation process. From the DVD/USB image, you have always had a choice to do a new installation, or to update a previously installed version. Description in detail is not necessary anywhere, because the choices are so obvious when you boot from a DVD/USB install image.

I could have been clearer I guess. My problem was worry about the repos to activate to keep 15.3 properly updated *after* a fresh install....

That is how I read it too - fresh install. Regardless, the confusion here speaks about the level of expectations regarding 15.3 I installed 15.3 on a test machine + bunch of VMs in them clouds - the update/patch repos seemed to be broken, at least for a while. I also had/have issues with PHP versions with web server/applications. It feels more than just the usual "change is pain" - some things cannot be easily worked around at the moment. Hopefully at least the repo/update/patch issues are settling down. I wonder if the disappearing mirrors and mirror updates are general linux world problem or another symptom of decay. This is not my thread - I will stop hijacking it and behave now. The Subject resonated with me.

On 21/07/2021 11:22, Darryl Gregorash wrote:

...

On 2021-07-20 4:56 p.m., Robin Klitscher wrote:

...

I've read the following announcement through multiple times:

https://news.opensuse.org/2021/07/19/leap-gains-maintenance-update-improveme...

but, being a bear of very little brain, I've failed to understand it.

What does it mean?

You are aware, of course, that Leap 15.3 and SLE are basically in lock-step now.

Indeed I am. But conversations in these lists and in other forums seem to suggest that the lock may be a little less than tidy. Hence the confusion. It was a bit less than tidy. Now it is not. I have not had any problems with miscreant patches for at least a week now.

There are now 2 new update repositories to deal with

...

this. Previously, the updates from SLE were being imported into separate repositories for 15.3, and it wasn't working. Now, it seems both are using the same ones.

"...seems...." seems a bit equivocal! And that's the nub. I can only give you my impression of what I read, including the URL you

On 2021-07-20 9:16 p.m., Robin Klitscher wrote: posted above.

For many years now I've installed successive opensuse (latterly Leap) versions clean, desktop KDE / Plasma, as new installations, never as updates or upgrades of existing. Does this mean I should change the habit of more than 20 years?

In your initial post, you spoke of updating to 15.3. You did not mention that you have always upgraded by doing a fresh installation. If you had, my entire post would have been "Just go ahead and do it, 15.3 is rock solid afaiac" I gave all that detail so you would have some idea of what you would be seeing *IF* you choose to go the upgrade route rather than a fresh install.

Invariably post-installation, I've also switched to the Packman repos, preferring yast and the GUI over zypper and the commandline. But I haven't been sure in the case of 15.3/SLE of the utility of continuing to do that.

In every repository URL that you have installed yourself, just change the actual version number to $releasever. Then you will never have to worry about getting that right ever again. YaST and zypper are smart enough to figure out what to do with it. In fact, you can do this in the upgrade, if you choose to do an upgrade rather than a new install.

In addition I've also been in the habit of using the various available "leading edge" repos for KDE/qt etc such as

All of the repos you mention have the version number in them. If you do as above, and replace the version numbers in the URL with $releasever, you can do a version upgrade from a USB stick with no problem whatsoever, and you will likely not have any questions about vendor changes. That is how I upgraded from 15.2, and I kept the Packman repo. There were absolutely no problems then, and none after.

But I'm unsure how this scenario would work out with 15.3 and compatibilities across necessary SLE resources as well as the familiar opensuse ones.

All I have read suggests that SLE and Leap now share the same codebase. I have no idea if there is anything else included in SLE that we don't get to see with Leap. The people to answer that question are here, and and all of them are working at SUSE. All those extra repos you mention are from the openSUSE list of additional repositories. I cannot for one moment imagine they are not all tested and vetted before being released into the wild. There is nothing in my experience so far with Leap 15.3 to suggest you will have any difficulty if you upgrade your system now. Besides which, you only have until November, when 15.2 officially goes out of support.

On 21.07.2021 07:05, Darryl Gregorash wrote:

...

On 2021-07-20 9:16 p.m., Robin Klitscher wrote:

...

On 21/07/2021 11:22, Darryl Gregorash wrote:

...

On 2021-07-20 4:56 p.m., Robin Klitscher wrote:

...

I've read the following announcement through multiple times:

https://news.opensuse.org/2021/07/19/leap-gains-maintenance-update-improveme...

but, being a bear of very little brain, I've failed to understand it.

What does it mean?

You are aware, of course, that Leap 15.3 and SLE are basically in lock-step now.

Indeed I am. But conversations in these lists and in other forums seem to suggest that the lock may be a little less than tidy. Hence the confusion. It was a bit less than tidy. Now it is not. I have not had any problems with miscreant patches for at least a week now.

What was the reason of problem before?

How was the problem fixed? I don't know the answers to these questions. The problem was that

On 2021-07-20 11:43 p.m., Andrei Borzenkov wrote: patches were showing up without any packages in them. This was a problem in YaST/update as well as in 'zypper patch' but not with 'zypper up'

What do users that installed earlier and presumably "untidy" configuration need to do to "tidy" their configuration?

Nothing, someone from SUSE posted here or another list that the problem with the patches was resolved. In my experience, it has been.

This is technical support list. All your answers so far amount to "and now all is well" which is pretty useless.

To the extent that "all is well" answers the questions posed in this thread, I have no idea why you are complaining. Do you think I should be answering every technical issue that exists with 15.3 in a thread that is limited to asking specific questions about updates to the release?

Quoting this article

"The openSUSE specific package repositories called oss and non-oss repositories changed. While these two repositories contained all the content of Leap 15.2 and older, they now contain only the branding and related setup packages."

That is not what I see on s.o.o. http://download.opensuse.org/distribution/leap/15.3/repo/oss/ contains full distribution.

That is not the question here. The question is whether or not there is any impediment to upgrading to 15.3, and I have given my opinion from my experience: There is not. If you have any issues with how all those web pages are worded vs. what you see in the repositories, I suggest you take the matter up with someone who can discuss this with you.

Hi, On Wed, Jul 21, 2021 at 08:43:22AM +0300, Andrei Borzenkov wrote:

On 21.07.2021 07:05, Darryl Gregorash wrote:

...

On 2021-07-20 9:16 p.m., Robin Klitscher wrote:

...

On 21/07/2021 11:22, Darryl Gregorash wrote:

...

On 2021-07-20 4:56 p.m., Robin Klitscher wrote:

...

I've read the following announcement through multiple times:

https://news.opensuse.org/2021/07/19/leap-gains-maintenance-update-improveme...

but, being a bear of very little brain, I've failed to understand it.

What does it mean?

You are aware, of course, that Leap 15.3 and SLE are basically in lock-step now.

Indeed I am. But conversations in these lists and in other forums seem to suggest that the lock may be a little less than tidy. Hence the confusion. It was a bit less than tidy. Now it is not. I have not had any problems with miscreant patches for at least a week now.

What was the reason of problem before?

The collection of updates for the SLE Update repository was what we call a "wild hack"... It included patchinformation for all SLE15 versions, which caused bad interactioons with SLE15 SP3 level openSUSE Leap 15.3.

How was the problem fixed?

We changed the method to our standard patch delivery method, forwarding content to the opensuse.org infrastructure. The repository now only include the meta information required for Leap 15.3 / SLE15 SP3, avoiding patch interactions with older SLE 15 service packs.

What do users that installed earlier and presumably "untidy" configuration need to do to "tidy" their configuration?

Nothing, as only patch metadata was incorrect and triggering errors, actual RPMs were fine.

What does it mean for me as *user of openSUSE*? Where do I see these modules? How do I use them? If I do not need to use them or know about them why I am told about them?

zypper lr will show you the update repositories. As user... you will now no longer get weird conflict warnings from the package update applets or zypper patch. Point of the article was to ensure our users that the situation is now under control and the update repositories are stable.

So I completely agree with original post - the announcement is too vague and it just results in more confusion.

Advice taken ... need to spend more hours on it next time. Ciao, Marcus

On 2021-07-21 3:03 a.m., Dave Howorth wrote:

On Tue, 20 Jul 2021 22:05:55 -0600 Darryl Gregorash wrote:

...

In your initial post, you spoke of updating to 15.3.

If you reread it, I think you will find he did not. He spoke of updating after doing a fresh install.

Actually, he didn't mention until later that he has always been doing fresh installs. But that doesn't really matter anyway, does it? He wanted to know how to get the 15.3 update repos set up properly, and I told him what I thought was the easiest way to do just that. Besides, "system update" can be accomplished by doing an upgrade in-place of an existing version, *or* by doing a fresh install.