Bug#880337: php-sabre-vobject-3: FTBFS: Test failures

[Adrian Bunk]

Control: tags -1 - buster sid
Control: retitle -1 php-sabre-vobject-3: timezome Canada/East-Saskatchewan is 
removed in tzdata 2017c

On Mon, Oct 30, 2017 at 09:10:01PM +0100, Lucas Nussbaum wrote:
>...
> > There was 1 error:
> > 
> > 1) Sabre\VObject\TimezoneUtilTest::testTimeZoneBCIdentifiers with data set 
> > #52 ('Canada/East-Saskatchewan')
> > Exception: DateTimeZone::__construct(): Unknown or bad timezone 
> > (Canada/East-Saskatchewan)
>...

Thanks for your report.

The root cause is that the timezome Canada/East-Saskatchewan is removed 
in tzdata 2017c and should therefore be removed from php-bc.php

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#880337: php-sabre-vobject-3: FTBFS: Test failures

[Lucas Nussbaum]

Source: php-sabre-vobject-3
Version: 3.5.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> ...E. 1403 / 1483 ( 
> 94%)
> . 1464 / 1483 ( 
> 98%)
> ...   1483 / 1483 
> (100%)
> 
> Time: 564 ms, Memory: 16.00MB
> 
> There was 1 error:
> 
> 1) Sabre\VObject\TimezoneUtilTest::testTimeZoneBCIdentifiers with data set 
> #52 ('Canada/East-Saskatchewan')
> Exception: DateTimeZone::__construct(): Unknown or bad timezone 
> (Canada/East-Saskatchewan)
> 
> /<>/tests/VObject/TimeZoneUtilTest.php:181
> 
> ERRORS!
> Tests: 1483, Assertions: 2185, Errors: 1.
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2017/10/30/php-sabre-vobject-3_3.5.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.