Your message dated Mon, 21 Jul 2025 22:05:52 +0100
with message-id <ah6rsbw2b0rmr...@riva.ucam.org>
and subject line Re: python3-icalendar: Depends on a transitional package
has caused the Debian Bug report #1104638,
regarding python3-icalendar: Depends on a transitional package
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.)
--
1104638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-icalendar
Version: 6.0.1-1
Severity: normal
Hi!
python3-icalendar depends on python3-tz, which is a transitional package.
It should be updated to python3-pytz.
Thanks!
Best regards,
Nelson
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'unstable-debug'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-icalendar depends on:
ii python3 3.13.3-1
ii python3-dateutil 2.9.0-4
ii python3-tz 2025.2-2
python3-icalendar recommends no packages.
python3-icalendar suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jul 21, 2025 at 10:20:14PM +0200, Santiago Vila wrote:
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.
An effect of my change was to drop "Depends: python3-tz" from
python3-icalendar. That can cause new FTBFS issues in other packages if
they were implicitly relying on "Build-Depends: python3-icalendar" to
cause the pytz module to exist, rather than directly build-depending on
python3-pytz (or python3-tz) themselves.
I think the python-icalendar change was correct: python-icalendar
doesn't really need pytz any more (it just has some affordances for the
case where pytz is installed), and the cases that broke all imported
pytz directly.
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
I've fixed python-recurring-ical-events, python-x-wr-timezone, and
todoman, all of which were buggy in the way described above. The others
look unrelated to this: python3-icalendar doesn't get installed as part
of their build-dependencies.
Thanks for the heads-up!
--
Colin Watson (he/him) [cjwat...@debian.org]
--- End Message ---
