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:
> 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
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
It was a bit less than tidy. Now it is not. I have not had any
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
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
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?
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.