Your message dated Sun, 05 Dec 2021 04:18:32 +0000
with message-id <e1mtiyu-0004xx...@fasolo.debian.org>
and subject line Bug#997497: fixed in vdirsyncer 0.18.0-1
has caused the Debian Bug report #997497,
regarding vdirsyncer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.9 returned exit code 13
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 ow...@bugs.debian.org
immediately.)


-- 
997497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdirsyncer
Version: 0.16.8-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> LC_ALL=C.UTF-8 \
> DETERMINISTIC_TESTS=false \
> CI=false \
> REMOTESTORAGE_SERVER=skip \
> DAV_SERVER=skip \
> RADICALE_BACNEND=filesystem \
> dh_auto_test
> I: pybuild base:232: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_vdirsyncer/build; python3.9 -m pytest 
> tests
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<<PKGBUILDDIR>>, configfile: setup.cfg
> plugins: hypothesis-5.43.3, localserver-0.5.0
> collected 483 items
> 
> tests/storage/test_filesystem.py ....................................... [  
> 8%]
> .......sss......ss.......                                                [ 
> 13%]
> tests/storage/test_http.py .....                                         [ 
> 14%]
> tests/storage/test_http_with_singlefile.py ............................. [ 
> 20%]
> .........sssssss....sssss.ss                                             [ 
> 26%]
> tests/storage/test_memory.py ......................................sssss [ 
> 34%]
> ss....sss...ss                                                           [ 
> 37%]
> tests/storage/test_singlefile.py ....................................... [ 
> 45%]
> .............ss.ss                                                       [ 
> 49%]
> tests/storage/dav/test_caldav.py sssssssssssssssssssssssssssssssssssssss [ 
> 57%]
> sssssssssssssss                                                          [ 
> 60%]
> tests/storage/dav/test_carddav.py ssssssssssssssssssssssssss             [ 
> 66%]
> tests/storage/dav/test_main.py .................................         [ 
> 73%]
> tests/system/cli/test_config.py .........                                [ 
> 74%]
> tests/system/cli/test_discover.py FFFFF                                  [ 
> 75%]
> tests/system/cli/test_fetchparams.py F                                   [ 
> 76%]
> tests/system/cli/test_repair.py .....                                    [ 
> 77%]
> tests/system/cli/test_sync.py FFFF.FFFFFFFFFFFF                          [ 
> 80%]
> tests/system/cli/test_utils.py ..                                        [ 
> 81%]
> tests/system/utils/test_main.py .sss.                                    [ 
> 82%]
> tests/unit/test_exceptions.py .                                          [ 
> 82%]
> tests/unit/test_metasync.py .........                                    [ 
> 84%]
> tests/unit/test_repair.py ..........                                     [ 
> 86%]
> tests/unit/cli/test_config.py .                                          [ 
> 86%]
> tests/unit/cli/test_discover.py ......                                   [ 
> 87%]
> tests/unit/cli/test_fetchparams.py .........                             [ 
> 89%]
> tests/unit/sync/test_status.py .                                         [ 
> 89%]
> tests/unit/sync/test_sync.py ...............................             [ 
> 96%]
> tests/unit/utils/test_vobject.py ..................                      
> [100%]
> 
> =================================== FAILURES 
> ===================================
> ____________________________ test_discover_command 
> _____________________________
> tests/system/cli/test_discover.py:38: in test_discover_command
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ___________________ test_discover_different_collection_names 
> ___________________
> tests/system/cli/test_discover.py:91: in 
> test_discover_different_collection_names
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> __________________________ test_discover_direct_path 
> ___________________________
> tests/system/cli/test_discover.py:134: in test_discover_direct_path
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> __________________ test_null_collection_with_named_collection 
> __________________
> tests/system/cli/test_discover.py:161: in 
> test_null_collection_with_named_collection
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ___________________________ test_collection_required 
> ___________________________
> tests/system/cli/test_discover.py:180: in test_collection_required
>     ???
> tests/system/cli/test_discover.py:213: in test_collection_required
>     assert \
> E   assert "One or more storages don't support `collections = null`." in 
> "error: Unknown error occurred: unmatched ')' (<string>, line 1)\nerror: Use 
> `-vdebug` to see the full traceback.\n"
> E    +  where "error: Unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: Use `-vdebug` to see the full traceback.\n" = <Result 
> SystemExit(1)>.output
> ---------------------------------- Hypothesis 
> ----------------------------------
> Falsifying example: test_collection_required(
>     a_requires=False,
>     b_requires=True,
>     tmpdir=local('/tmp/pytest-of-user42/pytest-4/test_collection_required0'),
>     runner=<cli.conftest._CustomRunner at 0x7fd29aca9a60>,
>     monkeypatch=<_pytest.monkeypatch.MonkeyPatch at 0x7fd29aca98e0>,
> )
> 
> You can reproduce this example by temporarily adding 
> @reproduce_failure('5.43.3', b'AAAB') as a decorator on your test case
> ________________________ test_get_password_from_command 
> ________________________
> tests/system/cli/test_fetchparams.py:32: in test_get_password_from_command
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> _______________________________ test_simple_run 
> ________________________________
> tests/system/cli/test_sync.py:33: in test_simple_run
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> __________________________ test_sync_inexistant_pair 
> ___________________________
> tests/system/cli/test_sync.py:49: in test_sync_inexistant_pair
>     assert 'pair foo does not exist.' in result.output.lower()
> E   assert 'pair foo does not exist.' in "error: unknown error occurred: 
> unmatched ')' (<string>, line 1)\nerror: use `-vdebug` to see the full 
> traceback.\n"
> E    +  where "error: unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: use `-vdebug` to see the full traceback.\n" = <built-in method 
> lower of str object at 0x7fd29ac18df0>()
> E    +    where <built-in method lower of str object at 0x7fd29ac18df0> = 
> "error: Unknown error occurred: unmatched ')' (<string>, line 1)\nerror: Use 
> `-vdebug` to see the full traceback.\n".lower
> E    +      where "error: Unknown error occurred: unmatched ')' (<string>, 
> line 1)\nerror: Use `-vdebug` to see the full traceback.\n" = <Result 
> SystemExit(1)>.output
> ____________________________ test_debug_connections 
> ____________________________
> tests/system/cli/test_sync.py:74: in test_debug_connections
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ______________________________ test_empty_storage 
> ______________________________
> tests/system/cli/test_sync.py:105: in test_empty_storage
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> _____________________ test_collections_cache_invalidation 
> ______________________
> tests/system/cli/test_sync.py:156: in test_collections_cache_invalidation
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ________________________ test_invalid_pairs_as_cli_arg 
> _________________________
> tests/system/cli/test_sync.py:229: in test_invalid_pairs_as_cli_arg
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> _____________________________ test_ident_conflict 
> ______________________________
> tests/system/cli/test_sync.py:262: in test_ident_conflict
>     assert not result.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ________________________ test_unknown_storage[foo-bar] 
> _________________________
> tests/system/cli/test_sync.py:297: in test_unknown_storage
>     assert (
> E   assert "Storage 'bar' not found. These are the configured storages: 
> ['foo']" in "error: Unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: Use `-vdebug` to see the full traceback.\n"
> E    +  where "Storage 'bar' not found. These are the configured storages: 
> ['foo']" = <built-in method format of str object at 
> 0x7fd29b718f60>(missing='bar', existing='foo')
> E    +    where <built-in method format of str object at 0x7fd29b718f60> = 
> "Storage '{missing}' not found. These are the configured storages: 
> ['{existing}']".format
> E    +  and   "error: Unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: Use `-vdebug` to see the full traceback.\n" = <Result 
> SystemExit(1)>.output
> ________________________ test_unknown_storage[bar-foo] 
> _________________________
> tests/system/cli/test_sync.py:297: in test_unknown_storage
>     assert (
> E   assert "Storage 'foo' not found. These are the configured storages: 
> ['bar']" in "error: Unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: Use `-vdebug` to see the full traceback.\n"
> E    +  where "Storage 'foo' not found. These are the configured storages: 
> ['bar']" = <built-in method format of str object at 
> 0x7fd29b718f60>(missing='foo', existing='bar')
> E    +    where <built-in method format of str object at 0x7fd29b718f60> = 
> "Storage '{missing}' not found. These are the configured storages: 
> ['{existing}']".format
> E    +  and   "error: Unknown error occurred: unmatched ')' (<string>, line 
> 1)\nerror: Use `-vdebug` to see the full traceback.\n" = <Result 
> SystemExit(1)>.output
> ________________________ test_no_configured_pairs[sync] 
> ________________________
> tests/system/cli/test_sync.py:309: in test_no_configured_pairs
>     assert result.output == 'critical: Nothing to do.\n'
> E   AssertionError: assert 'error: Unkno... traceback.\n' == 'critical: 
> Nothing to do.\n'
> E     - critical: Nothing to do.
> E     + error: Unknown error occurred: unmatched ')' (<string>, line 1)
> E     + error: Use `-vdebug` to see the full traceback.
> ______________________ test_no_configured_pairs[metasync] 
> ______________________
> tests/system/cli/test_sync.py:309: in test_no_configured_pairs
>     assert result.output == 'critical: Nothing to do.\n'
> E   AssertionError: assert 'error: Unkno... traceback.\n' == 'critical: 
> Nothing to do.\n'
> E     - critical: Nothing to do.
> E     + error: Unknown error occurred: unmatched ')' (<string>, line 1)
> E     + error: Use `-vdebug` to see the full traceback.
> _ 
> test_conflict_resolution[resolution0-UID:lol\nf\xf6\xf6content-UID:lol\nf\xf6\xf6content]
>  _
> tests/system/cli/test_sync.py:344: in test_conflict_resolution
>     assert not r.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ___________________________ test_partial_sync[error] 
> ___________________________
> tests/system/cli/test_sync.py:388: in test_partial_sync
>     assert not r.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> __________________________ test_partial_sync[ignore] 
> ___________________________
> tests/system/cli/test_sync.py:388: in test_partial_sync
>     assert not r.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> __________________________ test_partial_sync[revert] 
> ___________________________
> tests/system/cli/test_sync.py:388: in test_partial_sync
>     assert not r.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> ___________________________ test_partial_sync[None] 
> ____________________________
> tests/system/cli/test_sync.py:388: in test_partial_sync
>     assert not r.exception
> E   assert not SystemExit(1)
> E    +  where SystemExit(1) = <Result SystemExit(1)>.exception
> =============================== warnings summary 
> ===============================
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_filesystem.py::TestFilesystemStorage::test_metadata_normalization
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_filesystem.py::TestFilesystemStorage::test_metadata_normalization
>  uses the 'requires_metadata' fixture, which is reset between function calls 
> but not between test cases generated by `@given(...)`.  You can change it to 
> a module- or session-scoped fixture if it is safe to reuse; if not we 
> recommend using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_filesystem.py::TestFilesystemStorage::test_metadata_normalization
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_filesystem.py::TestFilesystemStorage::test_metadata_normalization
>  uses the 's' fixture, which is reset between function calls but not between 
> test cases generated by `@given(...)`.  You can change it to a module- or 
> session-scoped fixture if it is safe to reuse; if not we recommend using a 
> context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_memory.py::TestMemoryStorage::test_metadata_normalization
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_memory.py::TestMemoryStorage::test_metadata_normalization
>  uses the 'requires_metadata' fixture, which is reset between function calls 
> but not between test cases generated by `@given(...)`.  You can change it to 
> a module- or session-scoped fixture if it is safe to reuse; if not we 
> recommend using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_memory.py::TestMemoryStorage::test_metadata_normalization
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/storage/test_memory.py::TestMemoryStorage::test_metadata_normalization
>  uses the 's' fixture, which is reset between function calls but not between 
> test cases generated by `@given(...)`.  You can change it to a module- or 
> session-scoped fixture if it is safe to reuse; if not we recommend using a 
> context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py: 9 
> warnings
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_fetchparams.py: 
> 1 warning
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_sync.py: 16 
> warnings
>   /usr/lib/python3/dist-packages/click_threading/monkey.py:44: 
> DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
> `signature` and the `Signature` object directly
>     signature = inspect.formatargspec(*argspec) \
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>  uses the 'tmpdir' fixture, which is reset between function calls but not 
> between test cases generated by `@given(...)`.  You can change it to a 
> module- or session-scoped fixture if it is safe to reuse; if not we recommend 
> using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>  uses the 'runner' fixture, which is reset between function calls but not 
> between test cases generated by `@given(...)`.  You can change it to a 
> module- or session-scoped fixture if it is safe to reuse; if not we recommend 
> using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/system/cli/test_discover.py::test_collection_required
>  uses the 'monkeypatch' fixture, which is reset between function calls but 
> not between test cases generated by `@given(...)`.  You can change it to a 
> module- or session-scoped fixture if it is safe to reuse; if not we recommend 
> using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/unit/cli/test_fetchparams.py::test_fuzzing
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/unit/cli/test_fetchparams.py::test_fuzzing
>  uses the 'mystrategy' fixture, which is reset between function calls but not 
> between test cases generated by `@given(...)`.  You can change it to a 
> module- or session-scoped fixture if it is safe to reuse; if not we recommend 
> using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/unit/sync/test_status.py::test_legacy_status[SqliteStatus]
>   /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170: 
> HypothesisDeprecationWarning: 
> .pybuild/cpython3_3.9_vdirsyncer/build/tests/unit/sync/test_status.py::test_legacy_status[SqliteStatus]
>  uses the 'new_status' fixture, which is reset between function calls but not 
> between test cases generated by `@given(...)`.  You can change it to a 
> module- or session-scoped fixture if it is safe to reuse; if not we recommend 
> using a context manager inside your test function.  See 
> https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details 
> on fixture scope.
>     note_deprecation(
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> =========================== short test summary info 
> ============================
> FAILED tests/system/cli/test_discover.py::test_discover_command - assert not 
> ...
> FAILED 
> tests/system/cli/test_discover.py::test_discover_different_collection_names
> FAILED tests/system/cli/test_discover.py::test_discover_direct_path - assert 
> ...
> FAILED 
> tests/system/cli/test_discover.py::test_null_collection_with_named_collection
> FAILED tests/system/cli/test_discover.py::test_collection_required - assert 
> "...
> FAILED tests/system/cli/test_fetchparams.py::test_get_password_from_command
> FAILED tests/system/cli/test_sync.py::test_simple_run - assert not 
> SystemExit(1)
> FAILED tests/system/cli/test_sync.py::test_sync_inexistant_pair - assert 
> 'pai...
> FAILED tests/system/cli/test_sync.py::test_debug_connections - assert not 
> Sys...
> FAILED tests/system/cli/test_sync.py::test_empty_storage - assert not 
> SystemE...
> FAILED tests/system/cli/test_sync.py::test_collections_cache_invalidation - 
> a...
> FAILED tests/system/cli/test_sync.py::test_invalid_pairs_as_cli_arg - assert 
> ...
> FAILED tests/system/cli/test_sync.py::test_ident_conflict - assert not 
> System...
> FAILED tests/system/cli/test_sync.py::test_unknown_storage[foo-bar] - assert 
> ...
> FAILED tests/system/cli/test_sync.py::test_unknown_storage[bar-foo] - assert 
> ...
> FAILED tests/system/cli/test_sync.py::test_no_configured_pairs[sync] - 
> Assert...
> FAILED tests/system/cli/test_sync.py::test_no_configured_pairs[metasync] - 
> As...
> FAILED 
> tests/system/cli/test_sync.py::test_conflict_resolution[resolution0-UID:lol\nf\xf6\xf6content-UID:lol\nf\xf6\xf6content]
> FAILED tests/system/cli/test_sync.py::test_partial_sync[error] - assert not 
> S...
> FAILED tests/system/cli/test_sync.py::test_partial_sync[ignore] - assert not 
> ...
> FAILED tests/system/cli/test_sync.py::test_partial_sync[revert] - assert not 
> ...
> FAILED tests/system/cli/test_sync.py::test_partial_sync[None] - assert not 
> Sy...
> ========== 22 failed, 343 passed, 118 skipped, 35 warnings in 26.75s 
> ===========
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_vdirsyncer/build; python3.9 -m pytest 
> tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/vdirsyncer_0.16.8-3_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: vdirsyncer
Source-Version: 0.18.0-1
Done: Jonas Smedegaard <d...@jones.dk>

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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <d...@jones.dk> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 05 Dec 2021 04:00:56 +0100
Source: vdirsyncer
Architecture: source
Version: 0.18.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Jonas Smedegaard <d...@jones.dk>
Closes: 994119 997497
Changes:
 vdirsyncer (0.18.0-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release
     + several improvements to testsuite;
       closes: bug#994119, #997497,
       thanks to Benedikt Tuchen and Lucas Nussbaum
 .
   [ Jonas Smedegaard ]
   * add myself as uploader
   * update git-buildpackage config:
     + enable pristine-tar
     + enable signed tags
     + filter-out any .git* file
     + use DEP14 branches debian/latest and upstream/latest
   * update watch file:
     + track Github source
     + mangle upstream prerelease versions
     + add usage comment
   * drop patches 1 4 5 8,
     seemingly obsoleted by upstream testsuite improvements
   * drop patches 6 7, adopted upstream
   * tighten, update and renumber remaining patches,
     and add debian/patches/README file
     documenting patch numbering micro-policy
   * add source helper script copyright-check
   * update copyright info:
     + update coverage
     + license my contributions as GPL-3+
     + add related lintian overrides
   * add patch 2002 to relax dependency on Python module click-log
   * tighten build-dependencies
     on python3-click python3-click-threading python3-requests
   * declare compliance with Debian Policy 4.6.0
   * cleanup autogenerated version file
   * fix use debhelper buildsystem pybuild
     (not accidentally makefile)
   * build-depend on python3-pytest-cov
   * avoid installing misplaced .coverage files
Checksums-Sha1:
 82520d52876b88157ffa90f998415fd30f8de896 2617 vdirsyncer_0.18.0-1.dsc
 5a631dcb64392d1169c2b64d3610d22e7b39e577 311855 vdirsyncer_0.18.0.orig.tar.gz
 c5a2b35b8c4073dec0b0bcd96f14e8593ea49585 8200 vdirsyncer_0.18.0-1.debian.tar.xz
 a6796d3aa75133e8cd365ec908959caa532a1170 9048 
vdirsyncer_0.18.0-1_amd64.buildinfo
Checksums-Sha256:
 59ce300f332a5047996cb2eca4a1210295f8444cdf4d272bcbf826b40b20d9ab 2617 
vdirsyncer_0.18.0-1.dsc
 32d0176e52a9f70c709e4232a329184a8e1bc47cc23c7fce492f7f0fd2bb6ab4 311855 
vdirsyncer_0.18.0.orig.tar.gz
 2bb2d1c18ac4c3ef01445475c4f1fa3a059264a5a718c4f52eec48604bf751f7 8200 
vdirsyncer_0.18.0-1.debian.tar.xz
 142c0ed4a2723022b4cb0bb43f5f0bda4d79594419071d21251465f7fb744749 9048 
vdirsyncer_0.18.0-1_amd64.buildinfo
Files:
 275c0998a972ea567d14beae1c67ff3e 2617 utils optional vdirsyncer_0.18.0-1.dsc
 eb98a5d740576284fb7f275157274de0 311855 utils optional 
vdirsyncer_0.18.0.orig.tar.gz
 c9829878ce26b83346b57ff873d60e67 8200 utils optional 
vdirsyncer_0.18.0-1.debian.tar.xz
 06d0d5d4239e35a3316f2d5295f85759 9048 utils optional 
vdirsyncer_0.18.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGsOjcACgkQLHwxRsGg
ASGdBA//bdYOUoMe3bWoUHnI+5pJv843nQ6+TrTpZPM+4BUs3t/NsPB2OntUqTns
DleQU+wJxYDGAJKN0OxfAmN1h8OyAXbaGpBfSHhkCILrm/ljkpixCbpzaQ93RtbR
kjzAZYVbM7Nr0B2weV/+crxiscROgoztqOw8XCMM/1MJFfPKJuASa7cGTt8m0ILU
O2tfS1SS/VppW3WfE6uBoVTgPIHwv74kS9CmYgnNh6+jvOk7BY3Y10KsR4lRSG9r
LmXbypciIDk3u0Fqj0P0POeUETXry0tCt2CgPIsh+IwjrwI/CYrMrbUi8ihTnQlr
UWE9xsp1qGbK+ugFt5RWkDz++QpcseLRzbIrTtdaPR3EZrbpvvJ2mlg/K54enAZN
vg50Y/A8rtfZA3ub8wXbcPmDT65k5DywE2oYh6NlRM/7oUzAWYFPsi1YDpyNG30N
8158S0IXL/fC13XHU2fyY5H87e9YuTXs1UX/do9f7xFrdxfE9okqYpIkyFKLfTUa
Bg00x6Hcptzod8peTV5Q79Ry5hIQMYrnjYHcwdpd8risfQFom+Rpyt+Cafto28/J
DBDA5FAKVV8+MjWDdosgGQN8imwuL23U1/rHFzSPyG1d2BFZV/EvcpS/sSvfSKAB
MXWbKjYVSQ8GTjxPvOnln/kaMwtgO2xvbydsX1Zhfwj9z6PM38M=
=60//
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to