python 3.10-3.11 updates

[th0ma7]

Description

python 3.10-3.11 update + misc updates (xz, ncurses and svt-av1)

Fixes:

• xz sources no longer available from Debian
• python 3.10 + 3.11 no longer building due to cffi 1.17.0 and combination of newer setuptools + pip
• disable ffmpeg4
• migrate chromaprint to ffmpeg5

Re-divided into:

1. jackett (jackett: Update from version 0.20.3990 to 0.22.534 #6211)
2. native/libmysqlclient (native/libmysqlclient: Fix build by using legacy cmake version #6212)
3. xz (xz: Update from version 5.6.1+really5.4.5 to 5.6.2 #6210) → depends on 6211, 6212, co-depends on 6215
4. rutorrent (rutorrent: Update from version 4.1.5 to 4.3.6 #6215) → co-depends on 6210
5. ffmpeg4 + chromaprint (Misc updates ffmpeg related #6208) → depends on 6210
6. ncursesw (ncursesw: Update from version 6.4 to 6.5 #6209)
7. python311 (python 3.10-3.11 updates #6200) → depends on 6211, 6212, 6210, 6215, 6208
8. ffmpeg6 opencl ([WIP] Enable opencl on ffmpeg5-6 with DSM >= 7 #6166) → depends on 6210, 6208

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested
• Any needed documentation is updated/created

Type of change

• Bug fix
• New Package
• Package update
• Includes small framework changes
• This change requires a documentation update (e.g. Wiki)

[Safihre]

@th0ma7 I think I need your help.
I wanted to update SABnzbd last week, but I ran into the problem this PR fixes and also fixed it, but ran into the next problem.
It seems the building of the Python modules maturin (orjson) and pycparser suddenly broke. Strangely, not all archs fail at the same spot.
My build:
https://github.com/Safihre/spksrc/actions/runs/10557521724
6.2.4 fails at pycparser: https://github.com/Safihre/spksrc/actions/runs/10557521724/job/29245379175
7.1 fails at maturin: https://github.com/Safihre/spksrc/actions/runs/10557521724/job/29245380034

As you can see I tried to add the semantic-version package to the python-cross package, but it doesn't seem to help. I also tried putting it as part of python-native in another build, but that also didn't work.

Thoughts? :)

[th0ma7]

@Safihre There is this new issue that came up with inline assembly (tukaani-project/xz#121) for which there is already a fix available at tukaani-project/xz#136 that I ported into this PR. This will most likely be included in the next 5.6.3 release of ncurses.

That should already help so feel free to test this up.

[th0ma7]

@Safihre having any PR opened so I can have a look at your changes for sabnzbd?

[th0ma7]

I'm unable to trigger the python build errors using by Debian 12 container, merging #6183 and rebasing.

[th0ma7]

@hgy59 and @Safihre I am unable to reproduce the issue locally. Further I'm unable to download the logs, it always fails before ending the download. Although, while trying to look at raw logs online I was able to notice (before my browser crashed) something related to cffi==1.15.1 requested for install in the crossenv vs a cffi==1.17.0 needed by cryptography. So shot at the dark at updating them both, which built ok locally...

Also, in order to limit build time I've killed-off ffmpeg4 as I have no intention at maintaining it any longer.

Wait-and-see ... 🤷

[hgy59]

@th0ma7 what about a dedicated PR with the xz fix?
This would fix the build of some other packages and decouple from this PR with the neverending python dependency drama...

Another dedicated PR could update ncurses if mandatory...

[th0ma7]

Excellent idea, I'll divide and conquer... And hopefully solve the python drama indeed.

[th0ma7]

This would fix the build of some other packages and decouple from this PR with the neverending python dependency drama...

Another dedicated PR could update ncurses if mandatory...

That's what I did with #6208, #6209 and #6210

Although, to be confirmed, but I'm guessing they may end-up being co-dependent to xz download issue, which ended-up heading to this rabbit hole.

[hgy59]

Although, to be confirmed, but I'm guessing they may end-up being co-dependent to xz download issue, which ended-up heading to this rabbit hole.

Yes, xz must be merged before the others

And ncurses (AFAICR) triggers too many packages to complete within 5 hrs....