On 4/27/20 7:38 AM, Tomas Chvatal wrote:
Robert Schweikert píše v Po 27. 04. 2020 v 07:16 -0400:
On 4/27/20 5:16 AM, Dirk Müller wrote:
Hi Tomas,
But you are right, it seem not to propagate :/ I would recommend asking maint-coord team whats going on.
Well, the maintenance team released it only for SLE_15_SP1, not for SLE_15, not for SP2, not for Leap (and it is being removed from leap 15.2 because of factory dropping it)
so the problem is only on non-maintained distributions..
Well, that very much depends on the definition of "non-maintained", SLE_15 because of ESPOS is in at least semi-maintained state until the end of 2022.
The current system of breaking stuff for the sake of chasing the tip certainly creates a lot of extra work for many people, we should think about his some more.
You need latest python code stack in LTSS supported codestream?
Not the whole stack, but we have a reasonably large number of Python packages that get maintained in OBS and then on a more or less regular basis we copy/import these packages verbatim into SLE (SLE 15 and SLE 12). So if builds get broken we have to do extra work to figure out what builds where and what extra steps we might have to take.
We are supposed to do only minimal and security changes there anyway...
Different modules have different policies. The idea that whatever is in the common code base only gets minimal and basically backport fixes has long gone out the window.
Note that we prepared it on 15SP1 because the pytest was forked there otherwise we would prepare the stack on 15GA, like we prepared it for the SLE12 on SP3+.
Afaik the backports generator reads whitelist and you can simply add more packages to the dlpy:backports and put them into whitelist and maintain them as long as you wish/need (if I am wrong the script can be extended for that too).
Tom �{.n�+������������+a���˛���m�)z{.��+�:�{Zr�az�'z��j)h���ǩ��h��0�����Ǩ�
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Engineer LINUX Technical Team Lead Public Cloud rjschwei@suse.com IRC: robjo