Your message dated Mon, 21 Jan 2019 18:21:52 +0000 with message-id <[email protected]> and subject line Bug#909996: fixed in vdirsyncer 0.16.7-1 has caused the Debian Bug report #909996, regarding vdirsyncer: FTBFS (TypeError: 'NoneType' object is not iterable) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 909996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909996 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:vdirsyncer Version: 0.16.2-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: -------------------------------------------------------------------------------- [...] debian/rules build-indep dh build-indep --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python3.7 setup.py config running config /usr/lib/python3/dist-packages/setuptools_scm/version.py:191: UserWarning: meta invoked without explicit configuration, will use defaults where required. "meta invoked without explicit configuration," I: pybuild base:217: python3.6 setup.py config running config /usr/lib/python3/dist-packages/setuptools_scm/version.py:191: UserWarning: meta invoked without explicit configuration, will use defaults where required. "meta invoked without explicit configuration," debian/rules override_dh_auto_build [... snipped ...] tests/storage/test_singlefile.py ....................................... [ 49%] .............ss.ss [ 53%] tests/storage/dav/test_caldav.py sssssssssssssssssssssssssssssssssssssss [ 62%] sssssssssssssss [ 65%] tests/storage/dav/test_carddav.py ssssssssssssssssssssssssss [ 71%] tests/storage/dav/test_main.py . [ 71%] tests/system/cli/test_config.py ......... [ 73%] tests/system/cli/test_discover.py ..... [ 74%] tests/system/cli/test_fetchparams.py .......... [ 76%] tests/system/cli/test_repair.py ..... [ 77%] tests/system/cli/test_sync.py ................. [ 81%] tests/system/cli/test_utils.py .. [ 82%] tests/system/utils/test_main.py .sssF [ 83%] tests/unit/test_exceptions.py . [ 83%] tests/unit/test_metasync.py ......... [ 85%] tests/unit/test_repair.py .......... [ 87%] tests/unit/test_sync.py ............................... [ 94%] tests/unit/cli/test_config.py . [ 94%] tests/unit/cli/test_discover.py ...... [ 96%] tests/unit/utils/test_vobject.py .................. [100%] =================================== FAILURES =================================== ______________ TestFilesystemStorage.test_metadata_normalization _______________ tests/storage/__init__.py:301: in test_metadata_normalization st.none(), E hypothesis.errors.FailedHealthCheck: It looks like your strategy is filtering out a lot of data. Health check found 50 filtered examples but only 3 good ones. This will make your tests much slower, and also will probably distort the data generation quite a lot. You should adapt your strategy to filter less. This can also be caused by a low max_leaves parameter in recursive() calls E See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more information about this. If you want to disable just this health check, add HealthCheck.filter_too_much to the suppress_health_check settings for this test. ---------------------------------- Hypothesis ---------------------------------- You can add @seed(296577508032444947572819497154329054860) to this test or run pytest with --hypothesis-seed=296577508032444947572819497154329054860 to reproduce this failure. ________________ TestMemoryStorage.test_metadata_normalization _________________ tests/storage/__init__.py:301: in test_metadata_normalization st.none(), E hypothesis.errors.FailedHealthCheck: It looks like your strategy is filtering out a lot of data. Health check found 50 filtered examples but only 5 good ones. This will make your tests much slower, and also will probably distort the data generation quite a lot. You should adapt your strategy to filter less. This can also be caused by a low max_leaves parameter in recursive() calls E See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more information about this. If you want to disable just this health check, add HealthCheck.filter_too_much to the suppress_health_check settings for this test. ---------------------------------- Hypothesis ---------------------------------- You can add @seed(135387776198974078022358545371536932831) to this test or run pytest with --hypothesis-seed=135387776198974078022358545371536932831 to reproduce this failure. _________________________ test_open_graphical_browser __________________________ tests/system/utils/test_main.py:71: in test_open_graphical_browser iter(webbrowser._tryorder) E TypeError: 'NoneType' object is not iterable ============== 3 failed, 329 passed, 118 skipped in 59.71 seconds ============== E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.7_vdirsyncer/build; python3.7 -m pytest tests dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6" returned exit code 13 make[1]: *** [debian/rules:23: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:7: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 -------------------------------------------------------------------------------- The build was made in my autobuilder with "dpkg-buildpackage -A" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdirsyncer.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---Source: vdirsyncer Source-Version: 0.16.7-1 We believe that the bug you reported is fixed in the latest version of vdirsyncer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Filip Pytloun <[email protected]> (supplier of updated vdirsyncer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 27 Feb 2018 21:11:19 +0100 Source: vdirsyncer Binary: vdirsyncer vdirsyncer-doc Architecture: source Version: 0.16.7-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team <[email protected]> Changed-By: Filip Pytloun <[email protected]> Description: vdirsyncer - Synchronize calendars and contacts vdirsyncer-doc - Synchronize calendars and contacts - documentation Closes: 902669 909996 917092 Changes: vdirsyncer (0.16.7-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP * d/control: Remove ancient X-Python3-Version field . [ Filip Pytloun ] * New upstream release, Closes: #909996 * d/control: VCS urls are now fixed, Closes: #917092 * d/control: suggest vdirsyncer-doc, Closes: #902669 * d/patches: Update patches * d/control: Bump standards version * d/compat: Bump debhelper version Checksums-Sha1: b86e5a1a114d6fc498f2ab30b9c5beddf73c52b9 2559 vdirsyncer_0.16.7-1.dsc 25908d3f3c75245fb3a3e893c7585c753d6e4ed5 113649 vdirsyncer_0.16.7.orig.tar.gz 4a8dcb3ee8f07b1064fe699a78c241d355e2aa94 7092 vdirsyncer_0.16.7-1.debian.tar.xz f41552bf3145e854639efcb4f03bbde939e8fed2 7514 vdirsyncer_0.16.7-1_source.buildinfo Checksums-Sha256: 6fc37fb2c05b8695b75cf957ae2d092987db3c08ce28e8b90ba3468268f0e2c0 2559 vdirsyncer_0.16.7-1.dsc d77abb174d6ebf91b70887d3faf56bdb75d180f226a175e32f9e9647baa6dbfb 113649 vdirsyncer_0.16.7.orig.tar.gz c6f24a998f8ccf7c7339786a614e64f61671de30a9a988a215a51a6c192ea28e 7092 vdirsyncer_0.16.7-1.debian.tar.xz 422c648623a6b8ea2e7083ccbe559e0312db9c42d4a54eb738bcfe9765b98a64 7514 vdirsyncer_0.16.7-1_source.buildinfo Files: 5849921088bfeb661424d04be009536e 2559 utils optional vdirsyncer_0.16.7-1.dsc b50cd9431bd024262fc267f9857d9ec9 113649 utils optional vdirsyncer_0.16.7.orig.tar.gz 139745e96360c6745f89b53df93b8147 7092 utils optional vdirsyncer_0.16.7-1.debian.tar.xz b20117b63d5b1384b035f7ec20c3ed07 7514 utils optional vdirsyncer_0.16.7-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEEOAKTsWyox6BpW4soaAgjm5xy5hsFAlxGB1wRHGZpbGlwQHB5 dGxvdW4uY3oACgkQaAgjm5xy5hsu7Q//ZljN2Eo5DllK4K5LGuL0ZKp1dIZNUrwZ bD7rGaCPGcdE2qkFmhRwj3FfWzfujR3RIUC3hyK0VGDQ2CAf3KF/skPl8TBnvfTt QqclgGtSbMsk+y6cLcdX34go+YLHIX/296pEhStOZsmGwNrwUMII968j+neLSRAH MwU60kZgURGSFdvlOg6Ia1VMK8qPwFMsQYhy63DkLVDy+gCjvqbVcI/yIU/VsU0w 0RB6JSHPclWd8bdwgufi1q9WQ1UVeFoVqSEuQi11UHlNjcSTp7WPElHDJZlZCnfu O/SqcYoGPnQVqSexS2QP1qwm+Gd8LRQOnjEE4Nm2NmL15b3yFZcJZxVEnRazxtfO z/7xJM45NSIpsdA6m63UdDWroL717cPfP5REDQw9BgHScyiTLEzIFQtSvN/ePzMf fUo3CLDxOWYTILxUGHe1s/LSiTNL54jwcrUA5hHn8TwV9juLjTFGKpYBKKUG3rEM /z9Eg5Mzjh9628lySb1rwSWj5LZfo0e8pMjpA9gTcI277rqMzZIoT0ydt2QRsWZs XPtJKapDbdI1JLORuUaJceuQNMpk+26YBkROoGlyV+5sMVQYEw98hoMEGb8gU3he jnkfCLhYQvgPAmIZ7eJ7CgdCr9FotXDmRCTVIcH5w8V+8e5cGase6Am9VHfHUhCe Jyi8WEF+Lfg= =Mvbs -----END PGP SIGNATURE-----
--- End Message ---
