Attachments (0)
Nordic Case Info
  • Case ID: 328570
Options

pip install pynrfjprog -- fails with inconsistent names

Achim Kraus

pip install pynrfjprog fails - details

Ubuntu 22.04.4 LTS
Python 3.10.12
pip 22.0.2

pip install pynrfjprog

fails with:

Defaulting to user installation because normal site-packages is not writeable
Collecting pynrfjprog
  Downloading pynrfjprog-10.24.2.tar.gz (47.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 47.6/47.6 MB 5.6 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package pynrfjprog produced metadata for project name unknown. Fix your #egg=pynrfjprog fragments.
Discarding files.pythonhosted.org/.../pynrfjprog-10.24.2.tar.gz (from pypi.org/.../) (requires-python:>=3.7): Requested unknown from files.pythonhosted.org/.../pynrfjprog-10.24.2.tar.gz has inconsistent name: filename has 'pynrfjprog', but metadata has 'unknown'
  Downloading pynrfjprog-10.24.1.tar.gz (47.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 47.6/47.6 MB 5.6 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package pynrfjprog produced metadata for project name unknown. Fix your #egg=pynrfjprog fragments.
Discarding files.pythonhosted.org/.../pynrfjprog-10.24.1.tar.gz (from pypi.org/.../) (requires-python:>=3.7): Requested unknown from files.pythonhosted.org/.../pynrfjprog-10.24.1.tar.gz has inconsistent name: filename has 'pynrfjprog', but metadata has 'unknown'
  Downloading pynrfjprog-10.24.0.tar.gz (46.6 MB)
...
Parents
  • 0

    Hi,

    Please take a look at this forum discussion. Hope this helps.

    Regards,

    Priyanka

  • 0 in reply to Priyanka

    Hi Priyanka!

    I also ran into this issue and while your suggestion worked (adding -use-deprecated=legacy-resolver to the pip install command, thank you for that!

    It would be good if we didn't have to resort to workarounds to install the package. Could you please contact the ones responsible for the package and ask them to figure out the metadata issue?

Reply
  • 0 in reply to Priyanka

    Hi Priyanka!

    I also ran into this issue and while your suggestion worked (adding -use-deprecated=legacy-resolver to the pip install command, thank you for that!

    It would be good if we didn't have to resort to workarounds to install the package. Could you please contact the ones responsible for the package and ask them to figure out the metadata issue?

Children
Terms of service