device-tree-compiler FTBFS in Kinetic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
device-tree-compiler (Debian) |
Fix Released
|
Unknown
|
|||
device-tree-compiler (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I've copied what I hope is the relevant part of the log below.
python3 ./setup.py build_ext --build-
Traceback (most recent call last):
File "/<<PKGBUILDDIR
setup(
File "/usr/lib/
return distutils.
File "/usr/lib/
_setup_
File "/usr/lib/
_Distributi
File "/usr/lib/
self.
File "/usr/lib/
ep(self)
File "/usr/lib/
ep.load()(self, ep.name, value)
File "/usr/lib/
_assign_
File "/usr/lib/
_version_
File "/usr/lib/
raise LookupError(
LookupError: setuptools-scm was unable to detect version for /<<PKGBUILDDIR>>.
Make sure you're either building from a fully intact git repository or PyPI tarballs. Most other sources (such as GitHub's tarballs, a git checkout without the .git folder) don't contain the necessary metadata and will not work.
For example, if you're using pip, instead of https:/
tags: | added: patch |
Changed in device-tree-compiler (Debian): | |
status: | Unknown → New |
Changed in device-tree-compiler (Debian): | |
status: | New → Fix Released |
I'm not sure how this ever built; the issue is that the override d/rules uses to tell setuptools-scm what the version should be is:
export SETUPTOOLS_ SCM_PRETEND_ VERSION= $(DEB_VERSION_ UPSTREAM)
However, DEB_VERSION_ UPSTREAM is blank because pkg-info.mk hasn't been imported. I'll open a PR upstream in salsa but I'm attaching a patch here for us to workaround the issue in the meantime.