See https://copr.fedorainfracloud.org/coprs/g/python/python3.8/package/vdirsyncer/ for actual logs. This report is automated and not very verbose, but feel free to ping me for help.
This is now blocked by bz1697439. Error: Problem: cannot install the best candidate for the job - nothing provides python3.8dist(oauthlib) >= 3 needed by python3-requests-oauthlib-1.2.0-1.fc31.noarch
Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/sphinx/config.py", line 361, in eval_config_file execfile_(filename, namespace) File "/usr/lib/python3.8/site-packages/sphinx/util/pycompat.py", line 86, in execfile_ exec(code, _globals) File "/builddir/build/BUILD/vdirsyncer-0.16.7/docs/conf.py", line 19, in <module> release = setuptools_scm.get_version(root='..', relative_to=__file__) File "/usr/lib/python3.8/site-packages/setuptools_scm/__init__.py", line 150, in get_version parsed_version = _do_parse(config) File "/usr/lib/python3.8/site-packages/setuptools_scm/__init__.py", line 105, in _do_parse raise LookupError( LookupError: setuptools-scm was unable to detect version for '/builddir/build/BUILD/vdirsyncer-0.16.7'. 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 This also fails in Fedora rawhide with Python 3.7. Could you please fix this?
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag. If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead: on branch master: $ fedpkg build --target=f32-python To wait for a build to show up in the side tag, do: $ koji wait-repo f32-python --build=<nvr> Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32. An updated mock config is posted at: http://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away. Thanks. Let us know if you need up to date info, or if you have any questions. PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual: on branch f31: $ fedpkg build
The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.)
(Python 3.8 has landed in the rawhide buildroot.)
This issue is blocking the Python 3.8 rebuilds. If this package won't build with 3.8, it won't be installable, along with all its dependent packages, in Fedora 32. Furthermore, as it fails to install, its dependent packages will fail to install and/or build as well. Could you please look into this?
Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule
Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule
This package is now orphaned according to the Fedora's Fails To Build From Source policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The effort was coordinated in https://pagure.io/releng/issue/8917 If you believe this was done in an error, please describe why exactly is that so in the releng issue linked above this line. If you want to unorphan the package, please do so via the process described in https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package Replying here is not a way to unorphan the package. This comment was mass posted to all the affected bugzillas and I am not subscribed to comments here. Note that this process is semi-automated and based on a policy, it is not my personal initiative.
FEDORA-2019-b09e948d76 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b09e948d76
vdirsyncer-0.16.7-6.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b09e948d76
vdirsyncer-0.16.7-6.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.