Source: ruby-delayed-job Version: 4.0.6-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 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): > Failure/Error: Time.zone = 'US/Eastern' > > TZInfo::DataSourceNotFound: > No source of timezone data could be found. > Please refer to http://tzinfo.github.io/datasourcenotfound for help > resolving this error. > Shared Example Group: "a delayed_job backend" called from > ./spec/test_backend_spec.rb:4 > # ./lib/delayed/backend/shared_spec.rb:230:in `block (3 levels) in <top > (required)>' > # ------------------ > # --- Caused by: --- > # TZInfo::ZoneinfoDirectoryNotFound: > # None of the paths included in TZInfo::ZoneinfoDataSource.search_path > are valid zoneinfo directories. > # ./lib/delayed/backend/shared_spec.rb:230:in `block (3 levels) in > <top (required)>' > > Finished in 1.25 seconds (files took 0.96544 seconds to load) > 148 examples, 1 failure > > Failed examples: > > rspec './spec/test_backend_spec.rb[1:1:7:4]' # Delayed::Backend::Test::Job it > should behave like a delayed_job backend reserve reserves jobs scheduled for > the past when time zones are involved > > ERROR: Test "ruby2.3" failed: If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/01/ruby-delayed-job_4.0.6-2_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.
