bkbilly / lnxlink

🖥 Effortlessly manage your Linux machine using MQTT.

Home Page:https://bkbilly.gitbook.io/lnxlink

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

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

ScottG489 opened this issue · comments

What type of installation are you running?

Desktop

Which Linux OS are you using?

Ubuntu 22.04

Which version of LNXLink has the issue?

2023.6.1

The problem

Went through the most recent installation docs and came across this error. Not sure what else to mention, but here's some potentially helpful version information:

$ uname -a
Linux scott-desktop-linux 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ python3 --version
Python 3.11.0rc1
$ pip3 --version
pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)

Logs

$ pip3 install -U lnxlink
Defaulting to user installation because normal site-packages is not writeable
Collecting lnxlink
  Using cached lnxlink-2023.6.1-py3-none-any.whl (28 kB)
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.

You could try installing the latest version of PIP:

sudo pip3 install -U pip

Then try installing lnxlink again.

That did the trick! Thanks!

Gonna close this, but perhaps it would be a good idea to mention a minimum pip3 version to the install docs?

It never occurred to me that it would be a problem, but I will add it as an installation procedure