meson-python: error: Could not find meson version 0.63.3 or newer, found 0.61.2

[jsmif]

The front page says it was tested on Ubuntu 22.04. However, when I run the install instructions there, I get the following error:

Collecting dbus-python>=1.3.2
  Using cached dbus-python-1.3.2.tar.gz (605 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [3 lines of output]
      
      meson-python: error: Could not find meson version 0.63.3 or newer, found 0.61.2
      meson-python: error: .
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Note that meson 61.2 is the newers in Ubuntu 22.04 and even 22.10 only 63.2 is the newest, not 63.3. So did the dbus-python project update its requirements, subsequently breaking this?

I tried sudo pip3 install meson==0.63.3 and sudo pip3 install bluing (and yes I'm on Python > 3.10), but it still got the same error.

[jsmif]

I theoretically was able to work around this with the command mentioned in #32:

sudo -H pip install --no-dependencies bluing PyGObject docopt btsm btatt bluepy configobj btl2cap pkginfo xpycommon halo pyserial bthci btgatt log_symbols colorama spinners six termcolor

But then when I run a scan, I get the following error:

$ bluing le --scan
[ERROR] bluing.le.ui
        CalledProcessError: "Command 'rfkill unblock 0' returned non-zero exit status 1."

My version is

rfkill --version
rfkill from util-linux 2.37.2

Which is the latest for Ubuntu 22.04

[jcmcharro]

Hello, jsmif,
have you been able to suceed?
What has been the solution?
I am having the same issue on Ubuntu 20.04...

[jsmif]

@jcmcharro Unfortunately I haven't found a workaround. @fO-000 would have to say how to fix it. (I checked and it's still broken on my box. I used the workaround I mentioned above but I can't even LE scan currently, but I don't get that rfkill error)