openrazer-meta: update to 3.10.1.

[dmarto]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)

[dmarto]

I was worried this may happen.

   PYTHON: py3:openrazer-daemon <-> UNKNOWN PKG PLEASE FIX!

@classabbyamp any tips on the new py/check/provides, I just built twice locally to have it not complain, what would be the proper setup?

p.s I saw there is noverifypydeps=yes, seems a bit extreme? Tried adding explicit provides="py:..", but no dice.

[classabbyamp]

add the provides= and put it in depends

[dmarto]

I don't follow;

I have tried multiple combination of explicit provides:

• provides="py3:openrazer-daemon"
• provides="py3:openrazer-daemon-${version}_${revision}"

on the subpkg and/or on the sourcepkg - neither works.

Adding py3:openrazer-daemon (or with version) in any depends throw an error target dependency 'py3:openrazer-daemon' does not exist (regardless of provides).

Looking into the scripts, I don't think this will work, the provides are collected from the repo db, and the checks are in the pre-pkg step. I will add noverifypydeps=yes to the subpkg.

[classabbyamp]

put the provides in openrazer-daemon and add it to the depends of this package

[dmarto]

Ok, but it still ends up as PYTHON: py3:openrazer-daemon <-> UNKNOWN PKG PLEASE FIX! on my end, lets see on CI.

[jonpikum]

This PR worked for me locally on x86_64.
I rebased to master, updated the version to 3.10.2, xgensum -i'd, pkg'd and installed without error.

[Duncaen]

please update

[dmarto]

@Duncaen no problem, but I don't know how to make CI happy, none of the things I tried with the new python provides makes it pass. Is noverifypydeps=yes going to be accepted?

[Duncaen]

merged a1717a2