mqttwarn: [FreeBSD] ModuleNotFoundError: No module named 'versioningit'

When building on FreeBSD 13.1 on amd64, I get this error. I can’t figure out what versioningit is.

===>   py39-mqttwarn-0.34.0 depends on file: /usr/local/bin/python3.9 - found
===========================================================================
=======================<phase: lib-depends    >============================
===========================================================================
=>> Recording filesystem state for prebuild... done
=======================<phase: configure      >============================
===>   py39-mqttwarn-0.34.0 depends on package: py39-setuptools>=63.1.0 - found
===>   py39-mqttwarn-0.34.0 depends on file: /usr/local/bin/python3.9 - found
===>  Configuring for py39-mqttwarn-0.34.0
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "setup.py", line 7, in <module>
    from versioningit import get_cmdclasses
ModuleNotFoundError: No module named 'versioningit'
*** Error code 1

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 37 (37 by maintainers)

Most upvoted comments

Thanks also for your efforts to bring versioningit to the FreeBSD ports tree, so people have more choices other than setuptools-scm.

/cc @jwodder

pep517 instead of distutils works.

Rest assured we will definitively not go that route, and keep proper release and bundle management. The user should surely not be concerned to pull or clone from any Git repository at all. But it’s a different thing for package builders or distributors. Apologies that this currently causes troubles for FreeBSD.

Maybe we can discover other Python packages already using build-time dependencies like setuptools-scm or versioningit, (or versioneer or vcversioner), in order to learn how they are doing it to overcome the Git vs. Tarball barrier.

I think my first step would be creating a FreeBSD port for python-versioningit 😉