Hi.

I've noticed that "todoman" does not build in unstable.
A debbisect tells me this:

bisection finished successfully
  last good timestamp: 20250712T233653Z
  first bad timestamp: 20250713T022514Z
only one package differs: python3-icalendar 6.0.1-2 -> 6.0.1-3

Are you sure that the changes in 6.0.1-3 are correct?

Usually when one replaces a dummy package in depends or build-depends
by the package actually having the functionality, no new FTBFS issues
should be expected.

This is a list of packages which FTBFS in unstable today but they were
never reported yet, and I fear that python3-icalendar is also to blame
for some of them:

ecbuild
glance
mistral
python-idasen-ha
python-oslo.concurrency
python-oslo.messaging
python-recurring-ical-events
python-x-wr-timezone
resvg
todoman

Did not have time to look in detail, but at least two of them have
failing autopkgtests here:

https://qa.debian.org/excuses.php?package=python-icalendar

Thanks.

Reply via email to