On Mon, 2021-01-18 at 11:18 +0100, John Paul Adrian Glaubitz wrote:
Hello!
On 1/18/21 11:09 AM, Lubos Kocman wrote:
Well keep in mind that even in Leap 15.2 updates to packages with SLE origin had to be submitted from SLE-side. So I don't see much of a change to be honest.
Yes, I'm aware of that. But if I understand correctly, updates now always have to go through SLE if the package exists both in SLE and Leap.
Before that, we could update packages either in SLE or Leap, couldn't we?
So the change of origin required an an approval of Release Team member. Generally packages with SLE origin were really updated through SLE. The project SLE Workarounds was usually holding fork only temporarily, until the request got into SLE. The effort was to have sources as close as possible. So I would not say that there was an intention to diverge. I see that 15.2 already disappeared from http://tanana.suse.de/, but if there was a source divergence it was reported as feature against SLE. There was about 11 of them. The way I see it as that before we were waiting for sources from SLE, that we could temporarily fork in order to resolve build issues. Now we're waiting for binaries that we can also temporarily fork if it blocks larger amount of submissions. We'll try to have up2date version of everything in backports. Which is where our focus should be
My fear is that some Leap users may find the update cadence for individual key packages too slow. The original idea of Leap was to have a SLE base but with key packages like Firefox being kept up to date.
Adrian
-- Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic