Hi, On Sat, Sep 01, 2018 at 02:54:25PM +0300, Adrian Bunk wrote: > Control: reassign -1 src:python-dateutil 2.7.3-1 > Control: retitle -1 python-dateutil: RRULE UNTIL values must be specified in > UTC when DTSTART is timezone-aware > Control: severity -1 serious > Control: affects -1 python-dateutil python3-dateutil src:python-vobject > src:python-icalendar
Thanks! > > On Fri, Aug 31, 2018 at 09:41:32PM +0200, Paul Gevers wrote: > > Source: python-dateutil, python-vobject > > Control: found -1 python-dateutil/2.7.3-1 > > Control: found -1 python-vobject/0.9.5-2 > > X-Debbugs-CC: debian...@lists.debian.org > > User: debian...@lists.debian.org > > Usertags: breaks needs-update > > > > Dear maintainers, > > > > With a recent upload of python-dateutil the autopkgtest of > > python-vobject started to fail in testing. I copied some of the output > > below. > >... > > This also causes FTBFS, the first two seen are: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-icalendar.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-vobject.html > > I strongly suspect that there will also be runtime issues with other > packages using python-dateutil currently in stretch and buster, so even > in case this is considered a bug in reverse dependencies there will > still be Breaks required in python{,3}-dateutil against packages in > stretch and buster that got broken (unless it was only a broken test). This was broken by efba12d3 due to https://github.com/dateutil/dateutil/issues/620 so we likely want reverse deps to catch up and fix this. Cheers, -- Guido
