#1151811 dirty-equals: FTBFS: E ImportError: Pydantic V2 is not installed, run `pip install dirty-equals[pydantic]`

#1151811#5
Date:
2026-10-23 16:44:26 UTC
From:
To:
Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

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

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 cannot 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 add an affects on src:dirty-equals, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
tests/test_other.py:307: in <module>
    ('https://example.com', IsUrl(scheme='https')),
                            ^^^^^^^^^^^^^^^^^^^^^
dirty_equals/_other.py:229: in __init__
    raise ImportError('Pydantic V2 is not installed, run `pip install dirty-equals[pydantic]`') from e
E   ImportError: Pydantic V2 is not installed, run `pip install dirty-equals[pydantic]`
=========================== short test summary info ============================
ERROR tests/test_other.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
=============================== 1 error in 0.21s ===============================
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=2: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.15/build; python3.15 -m pytest --ignore=tests/test_docs.py
I: pybuild base:383: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14/build; python3.14 -m pytest --ignore=tests/test_docs.py
============================= test session starts ==============================
platform linux -- Python 3.14.8, pytest-9.1.1, pluggy-1.6.0
rootdir: /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14/build
configfile: pyproject.toml
testpaths: tests
collected 551 items

tests/test_base.py ................................                      [  5%]
tests/test_boolean.py ............................................       [ 13%]
tests/test_datetime.py ................................................. [ 22%]
.                                                                        [ 22%]
tests/test_dict.py ..................................................... [ 32%]
.....                                                                    [ 33%]
tests/test_inspection.py ...........................                     [ 38%]
tests/test_list_tuple.py ............................................... [ 46%]
...............................                                          [ 52%]
tests/test_numeric.py .................................................. [ 61%]
.................................                                        [ 67%]
tests/test_other.py ....................................x.x............. [ 76%]
....................................................................     [ 89%]
tests/test_strings.py .................................................. [ 98%]
.........                                                                [100%]

======================== 549 passed, 2 xfailed in 0.41s ========================
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.15 3.14" --parallel=2 returned exit code 13
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:5: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------

#1151811#10
Date:
2026-10-24 20:28:38 UTC
From:
To:
This will be fixed once pydantic-core has been binNMUed to add Python
3.15 as a supported version.  But AFAIK there isn't really a sensible
way to indicate that in the BTS metadata.

#1151811#15
Date:
2026-10-24 20:53:26 UTC
From:
To:
severity 1151811 important
thanks

Yes, I agree that bugs like this one are not actionable, so I'm stopping
FTBFS bug reporting altogether for now. Sorry for the inconvenience.

I suggest that any similar bug is downgraded to important until the
package can be rebuilt again, as I'm doing above. In my opinion, this
is marginally better than just closing the bug.

If you find any similar bug which I did not downgrade yesterday,
please downgrade them as well.

Thanks.