https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #14 from Sven Brauch ---
Sorry -- the backporting happened to 22.12.2, not .1 of course.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #13 from Sven Brauch ---
Hi, I backported Python 3.11 support to 22.12, so it should be in 22.12.1.
I also fixed the original crash which caused this issue. That fix is on master
and will be in KDE Gear 23.04 (together with the feature it f
https://bugs.kde.org/show_bug.cgi?id=463802
Pino Toscano changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #11 from Sven Brauch ---
Hi, yes, I completely missed the 3.11 release, we were still busy with getting
3.10 working. Sorry for that.
As said I understand your situation. I think the easiest change to improve the
situation the next time som
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #10 from Pino Toscano ---
(In reply to Sven Brauch from comment #9)
> Hi, I think ideally in this case you would have notified me that you needed
> Python 3.11 support in Gear 22.12. I would have backported it there.
While that is true, I t
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #9 from Sven Brauch ---
Hi, I think ideally in this case you would have notified me that you needed
Python 3.11 support in Gear 22.12. I would have backported it there.
Of course I see the problem that not all maintainers (including me) wil
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #8 from Pino Toscano ---
(In reply to Sven Brauch from comment #6)
> The maintainers of the respective applications have the best judgement of
> which feature is ready to be included in a release and which isn't, and
> these decisions should
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #7 from Jan Kriho ---
I have built the package without the c4ec40a9cac patch, and it fixes the crash
for me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #6 from Sven Brauch ---
Hi Pino, first of all, thanks a lot for your work in packaging kdev-python and
sorry for the chaos it always causes.
Of course I will fix this crash, but also that fix should not be backported.
The maintainers of the
https://bugs.kde.org/show_bug.cgi?id=463802
Pino Toscano changed:
What|Removed |Added
CC||p...@kde.org
--- Comment #5 from Pino Toscano -
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #4 from Sven Brauch ---
Thanks a lot. That 4bcec08fb400b was picked is understandable, it fixes build
with 3.11, which I didn't anticipate was required so quickly.
Including c4ec40a9cac is odd though, it is the commit that introduced the cr
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #3 from Jan Kriho ---
Debian bug as promised:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027845
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #2 from Jan Kriho ---
Hi, after some digging, I believe it was caused because of Python 3.11
transition, as described in a Debian bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008694
They have included some of the patches from the
https://bugs.kde.org/show_bug.cgi?id=463802
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
14 matches
Mail list logo
