Bug#1088043: marked as done (vdirsyncer: FTBFS: E AssertionError: assert '0' == '1')

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2024 21:35:51 +0000
with message-id <e1tp78z-00b3su...@fasolo.debian.org>
and subject line Bug#1088043: fixed in vdirsyncer 0.19.3-2
has caused the Debian Bug report #1088043,
regarding vdirsyncer: FTBFS: E AssertionError: assert '0' == '1'
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.)


-- 
1088043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Package: src:vdirsyncer
Version: 0.19.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules binary
dh binary --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build" 
module
I: pybuild base:311: python3.13 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_vdirsyncer
* Building wheel...
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml 
does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
 line 36, in read_pyproject
    section = defn.get("tool", {})[tool_name]
              ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^

[... snipped ...]


Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   assert '0' == "'\U000a95f5"
E
E     - '򩗵
E     + 0

Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   assert '0' == "'"
E
E     - '
E     + 0

Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
tests/unit/utils/test_vobject.py:334: in add_prop
    assert c[key] == value
E   AssertionError: assert '0' == '1'
E
E     - 1
E     + 0

Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
Trying example:
=============================== warnings summary 
===============================
tests/conftest.py:48
  
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_vdirsyncer/build/tests/conftest.py:48: 
HypothesisDeprecationWarning: `HealthCheck.all()` is deprecated; use `list(HealthCheck)` 
instead.
      The `hypothesis codemod` command-line tool can automatically refactor 
your code to fix this warning.
    suppress_health_check=HealthCheck.all(),

../../../../../../usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255
  /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255: PytestDeprecationWarning: 
aio_connector is asynchronous and explicitly requests the "event_loop" fixture. 
Asynchronous fixtures and test functions should use "asyncio.get_running_loop()" instead.
    warnings.warn(

../../../../../../usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255
  /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255: PytestDeprecationWarning: 
aio_session is asynchronous and explicitly requests the "event_loop" fixture. 
Asynchronous fixtures and test functions should use "asyncio.get_running_loop()" instead.
    warnings.warn(

../../../../../../usr/lib/python3/dist-packages/_hypothesis_pytestplugin.py:442
  /usr/lib/python3/dist-packages/_hypothesis_pytestplugin.py:442: 
PytestRemovedIn9Warning: Marks applied to fixtures have no effect
  See docs: 
https://docs.pytest.org/en/stable/deprecations.html#applying-a-mark-to-a-fixture-function
    return _orig_call(self, function)

../../../../../../usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255
  /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:255: PytestDeprecationWarning: 
conflict_state is asynchronous and explicitly requests the "event_loop" fixture. 
Asynchronous fixtures and test functions should use "asyncio.get_running_loop()" instead.
    warnings.warn(

tests/unit/test_repair.py:20
  
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_vdirsyncer/build/tests/unit/test_repair.py:20:
 HypothesisDeprecationWarning: `HealthCheck.all()` is deprecated; use `list(HealthCheck)` 
instead.
      The `hypothesis codemod` command-line tool can automatically refactor 
your code to fix this warning.
    @settings(suppress_health_check=HealthCheck.all())

tests/unit/test_repair.py:43
  
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_vdirsyncer/build/tests/unit/test_repair.py:43:
 HypothesisDeprecationWarning: `HealthCheck.all()` is deprecated; use `list(HealthCheck)` 
instead.
      The `hypothesis codemod` command-line tool can automatically refactor 
your code to fix this warning.
    @settings(suppress_health_check=HealthCheck.all())

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info 
============================
FAILED 
tests/unit/utils/test_vobject.py::TestVobjectMachine::runTest - 
AssertionError: assert '0' == '1'

  + 0
Falsifying example:
state = VobjectMachine()
unparsed_0 = state.get_unparsed_lines(encoded=False, joined=False)
parsed_0 = state.parse(unparsed=unparsed_0)
state.add_prop_raw(c=parsed_0, key='0', params=[], value='0')
state.add_prop_raw(c=parsed_0, key='0', params=[], value='0')
state.add_prop(c=parsed_0, key='0', value='1')
state.teardown()

You can reproduce this example by temporarily adding 
@reproduce_failure('6.119.3', 
b'AXicY2BgZAABNhDBAiKYGSBCEHFUHphiZGCC0owMAAQyAB0=') as a decorator on your 
test case
= 1 failed, 405 passed, 161 skipped, 2 
deselected, 2 xfailed, 7 warnings in 114.29s 
(0:01:54) =
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_vdirsyncer/build; python3.12 -m pytest 
-k 'not test_fuzzing'
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.13 
3.12" returned exit code 13
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:38: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202411/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

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.

- 1
--- End Message ---

--- Begin Message ---

Source: vdirsyncer
Source-Version: 0.19.3-2
Done: Colin Watson <cjwat...@debian.org>

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

Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (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: SHA256

Format: 1.8
Date: Sat, 21 Dec 2024 21:09:37 +0000
Source: vdirsyncer
Architecture: source
Version: 0.19.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1088043
Changes:
 vdirsyncer (0.19.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix _Component.__delitem__ with adjacent identical keys (closes:
     #1088043).
Checksums-Sha1:
 31fd5542c79958c822cc554a00941dd51e822101 2857 vdirsyncer_0.19.3-2.dsc
 75f8f3df7bb71d6abaa5825640194c5d98454e68 10132 
vdirsyncer_0.19.3-2.debian.tar.xz
 f5c45ebb3e9287aa7e4e9de7af802468b1e64875 9888 
vdirsyncer_0.19.3-2_source.buildinfo
Checksums-Sha256:
 fe43bf6d2e42de749036b178559ad57e1981aa89ca11060e75ea3bd6f659c14b 2857 
vdirsyncer_0.19.3-2.dsc
 c46cfba792f5fdef5d8a7f9bd273d7584a099860b59f42063360612d6ea83481 10132 
vdirsyncer_0.19.3-2.debian.tar.xz
 9181fdb418bcb0a813f2739fa3a958ae862217110805971dee5ef0a5a9b3bbd0 9888 
vdirsyncer_0.19.3-2_source.buildinfo
Files:
 d31c172d8eb6bb56a2f2f4a8c3c25d63 2857 utils optional vdirsyncer_0.19.3-2.dsc
 9158a488ac8932dd3aa56f0561fe0582 10132 utils optional 
vdirsyncer_0.19.3-2.debian.tar.xz
 01a620dbd4aff76c6c70cbeed1f99055 9888 utils optional 
vdirsyncer_0.19.3-2_source.buildinfo

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

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmdnLrcACgkQOTWH2X2G
UAtEEg/9HvFVF91Od5E8cB+fwG9O2R0qqhLx3tJU2kPANbOSvGkpuYtKTBNjdllA
6Q4HFlvwmWLuSnPLObpBhjr1rIwyfTzoORzuF6IKZCoAUEenrmVK2e8ekoojhZok
BU4MwOtTUnZSbMSdgJ8768c8zDyJ5HUKV3U+UUtMoXdP2rGyLPxOEEHEHlreuunU
80m0z30OHI/CbE7U4Y0Q/vdkz1NZ7UL9XlQcnfbChFNYwKbwiRexiy5sFrIUpSq+
9hLygPvu5tfU9KZ06h1hX03wmg6PWYFkaw+LxZDmEqGQ16kdp1l0hL2AiyEx2AC3
UV+dYemjGZwhCK5nuAr5PIrSa8nxBjLLtPkBUWOgsuxwFyiN+mVCGRoRfXfe1xLa
W5ETKTptSnV0Bg/RLluU45WonT6Y8WClsLsgKwpGHnTKQ/ZItlnqYpsjAe5ZB2g5
Hd7RyXuMakAS6wcsFcayUzUqXJxqBJ/9FwghyPh7zrXd1dsB/dMPQlamHHjSqnDT
wS0A65hWBlvVMlyUpZkV4HU+TWFgA1hnqwtsQJdzLbsaBcgR3IXq5N6k5wuCEUl6
hjP/tvCYXDr4BlmmLqmHS5hTl/IBsREW0T1OaNBlwmwXM1ulo1X3ctOtyBlh6Sn3
q92Kl5LZ6abTxIFsXLTTb0HuYVrUUl5VkVbslLZCug2DfGEyFnc=
=wZC9
-----END PGP SIGNATURE-----

pgp3Po802gJiE.pgp
Description: PGP signature

--- End Message ---