[Python-apps-team] Bug#951948: vdirsyncer: FTBFS: LookupError: setuptools-scm was unable to detect version for '/<<PKGBUILDDIR>>'.

[Lucas Nussbaum]

Source: vdirsyncer
Version: 0.16.7-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/docs'
> /usr/share/sphinx/scripts/python3/sphinx-build -b man -d _build/doctrees   . _build/man
> Running Sphinx v1.8.5
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 368, in eval_config_file
>     execfile_(filename, namespace)
>   File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in execfile_
>     exec_(code, _globals)
>   File "/<<PKGBUILDDIR>>/docs/conf.py", line 19, in <module>
>     release = setuptools_scm.get_version(root='..', relative_to=__file__)
>   File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 150, in get_version
>     parsed_version = _do_parse(config)
>   File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 113, in _do_parse
>     "use git+https://github.com/user/proj.git#egg=proj" % config.absolute_root
> 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://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj
> 
> make[2]: *** [Makefile:131: man] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/vdirsyncer_0.16.7-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.