Conversation with Axel

Hello Lubos,Am Montag, 10. Mai 2021, 14:03:40 CEST schrieben Sie:

Comment:

Rejecting as we need to re-submit this to SLE-15:Update after we

have
approved ECO. It can't be done earlier, as otherwise the SR gets
rejected
by maint team.

What is ECO?

I thought I did reference the wiki page in SR text. Let me link it
https://en.opensuse.org/ECOAh, that explains, thanks> What I'll need to know is some sort of simplified justification. We
need this to do x.y.z. Ideally it should make people understand why is
this needed now, and not in 12 months.I'm preparing Tryton 6 (ERP System), which is an LTS version with 5yr support,
and it needs a newer pycairo.I can keep the newer pycairo in the A:E:T repo for the time being, and plan
for the next Leap release for this> If you won't attend the meeting in an hour, then we'll discuss it with
Neal. But I already know that it's going to be bit tricky because of
the package rename. That would classify it a new package request, which
is typically not done in maintenance request.I dont have a meeting in my calendar, and will be in calls with my customer
:-)> Hope it helps.Yes, thank you!
Axel

Hello I did talk to Engineering TL for the team who would be implementing the change and we'll do it in SP4 as it's quite risky.

Hi Lubos, it looks risky to me. The obviously significant package name change will probably bring dependency issues unless we have a full review of all affected packages and do a full testing in ECO cycle (so it needs more changes than the python-cairo package itself). On the other hand the dropping of python2 support will probably bring troubles as well, eg python-gtk on SLE-15-SPx seems compatible with python2 (and requires python2-cairo) https://build.suse.de/package/binary/SUSE:SLE-15-SP2:GA/python-gtk/standard/x86_64/python-gtk-2.24.0-8.27.x86_64.rpm

Same as OPENSUSE-22

I'm personally having an effort to define process of updating packages with undefined maintainer.

Until that happens, we're blocked.