Bug#952038: nanoc: FTBFS: ERROR: Test "ruby2.5" failed: Failure/Error: it { is_expected.to eql output }
Source: nanoc
Version: 4.11.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: it { is_expected.to eql output }
>
>expected: "before\n class=\"rouge-table\">\nfoo\n class=\"k\">end\n\nafter\n"
> got: "before\n class=\"rouge-table\">\n\n class=\"k\">end\n\n\nafter\n"
>
>(compared using eql?)
>
>Diff:
>@@ -4,7 +4,8 @@
> 2
>
> def class="nf">foo
>- end
>+ end
>+
>
> after
> # ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:151:in `block
> (5 levels) in '
> # ./common/spec/spec_helper_foot.rb:27:in `block (4 levels) in (required)>'
> #
> ./debian/nanoc/usr/share/rubygems-integration/all/gems/nanoc-4.11.0/lib/nanoc/spec.rb:10:in
> `chdir'
> # ./common/spec/spec_helper_foot.rb:27:in `block (3 levels) in (required)>'
> # ./common/spec/spec_helper_foot.rb:26:in `block (2 levels) in (required)>'
> # ./common/spec/spec_helper_foot.rb:16:in `block (2 levels) in (required)>'
>
> Finished in 40.95 seconds (files took 1.31 seconds to load)
> 2716 examples, 4 failures, 7 pending
>
> Failed examples:
>
> rspec ./nanoc/spec/nanoc/cli/commands/check_spec.rb:13 #
> Nanoc::CLI::Commands::Check#run without options and arguments no issues for
> any checks succeeds
> rspec ./nanoc/spec/nanoc/cli/commands/check_spec.rb:24 #
> Nanoc::CLI::Commands::Check#run without options and arguments issues for
> deploy check fails
> rspec ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:72 #
> Nanoc::Filters::ColorizeSyntax with Rouge with legacy with line number is
> expected to eql "before\n class=\"rouge-table\">\nfoo\n class=\"k\">end\n\nafter\n"
> rspec ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:151 #
> Nanoc::Filters::ColorizeSyntax with Rouge with formater with table is
> expected to eql "before\n class=\"rouge-table\">\nfoo\n class=\"k\">end\n\nafter\n"
>
> /usr/bin/ruby2.5
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern ./nanoc/spec/\*\*/\*_spec.rb --exclude-pattern
> ./nanoc/spec/nanoc/\{filters/less_spec.rb,cli/commands/view_spec.rb\} -r
> ./nanoc/spec/spec_helper.rb --color failed
> ERROR: Test "ruby2.5" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/nanoc_4.11.0-3_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.
Bug#952033: ruby-fog-aliyun: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-fog-aliyun Version: 0.3.2-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `expect' for > # >Did you mean? exec > # ./spec/fog/aliyun_spec.rb:11:in `block (2 levels) in ' > > Finished in 0.00111 seconds (files took 0.22475 seconds to load) > 2 examples, 2 failures > > Failed examples: > > rspec ./spec/fog/aliyun_spec.rb:6 # Fog::Aliyun has a version number > rspec ./spec/fog/aliyun_spec.rb:10 # Fog::Aliyun does something useful > > /usr/bin/ruby2.5 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.5" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-fog-aliyun_0.3.2-3_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.
Bug#952027: ruby-declarative: FTBFS: ERROR: Test "ruby2.5" failed: Invalid gemspec in [declarative.gemspec]: No such file or directory - git
Source: ruby-declarative Version: 0.0.10-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Invalid gemspec in [declarative.gemspec]: No such file or directory - git > GEM_PATH=/<>/debian/ruby-declarative/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -e gem\ \"declarative\" > > ┌──┐ > │ Run tests for ruby2.5 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-declarative/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-declarative/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.5 -w -I"test" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/defaults_test.rb" > "test/definitions_test.rb" "test/heritage_test.rb" "test/schema_test.rb" > "test/variables_test.rb" "test/test_helper.rb" -v > Run options: -v --seed 45730 > > # Running: > > multiple Defaults#merge!#test_0001_merges arrays automatically = DEPRECATED: > global use of must_equal from /<>/test/defaults_test.rb:68. Use > _(obj).must_equal instead. This will fail in Minitest 6. > 0.00 s = . > multiple Defaults#merge!#test_0002_what = DEPRECATED: global use of > must_equal from /<>/test/defaults_test.rb:76. Use > _(obj).must_equal instead. This will fail in Minitest 6. > 0.00 s = . > DefinitionTest#test_0001_#merge does return deep copy = DEPRECATED: global > use of must_equal from /<>/test/definitions_test.rb:93. Use > _(obj).must_equal instead. This will fail in Minitest 6. > 0.00 s = . > with only dynamic property options#test_0001_anonymous = DEPRECATED: global > use of must_equal from /<>/test/defaults_test.rb:32. Use > _(obj).must_equal instead. This will fail in Minitest 6. > 0.00 s = . > deprecation#test_0001_prints deprecation twice = 0.00 s = F > DSLOptionsTest#test_0006_creates new array if original not existent = > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:63. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s = . > DSLOptionsTest#test_0001_merges Merge over original = DEPRECATED: global use > of must_equal from /<>/test/variables_test.rb:19. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s = . > DSLOptionsTest#test_0004_creates new hash if original not existent = > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:44. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s = . > DSLOptionsTest#test_0005_appends to Array = DEPRECATED: global use of > must_equal from /<>/test/variables_test.rb:54. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s = . > DSLOptionsTest#test_0002_accepts Procs = DEPRECATED: global use of must_equal > from /<>/test/variables_test.rb:28. Use _(obj).must_equal > instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s = . > DSLOptionsTest#test_0003_overrides original without Merge = DEPRECATED: > global use of must_equal from /<>/test/variables_test.rb:35. Use > _(obj).must_equal instead. This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/variables_test.rb:9. Use _(obj).must_equal instead. > This will fail in Minitest 6. > 0.00 s
Bug#952037: ruby-jekyll-sass-converter: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-jekyll-sass-converter Version: 1.5.2-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `expect' for > # > Did you mean? exec > # ./spec/sass_converter_spec.rb:43:in `block (3 levels) in (required)>' > > Finished in 0.05707 seconds (files took 0.351 seconds to load) > 36 examples, 36 failures > > Failed examples: > > rspec ./spec/scss_converter_spec.rb:255 # Jekyll::Converters::Scss importing > from internal libraries unsafe mode expands globs > rspec ./spec/scss_converter_spec.rb:278 # Jekyll::Converters::Scss importing > from internal libraries safe mode ignores external load paths > rspec ./spec/scss_converter_spec.rb:274 # Jekyll::Converters::Scss importing > from internal libraries safe mode allows local load paths > rspec ./spec/scss_converter_spec.rb:282 # Jekyll::Converters::Scss importing > from internal libraries safe mode does not allow traversing outside source > directory > rspec ./spec/scss_converter_spec.rb:228 # Jekyll::Converters::Scss importing > from external libraries safe mode ensures the sass_dir is the entire load path > rspec ./spec/scss_converter_spec.rb:224 # Jekyll::Converters::Scss importing > from external libraries safe mode ignores the new load path > rspec ./spec/scss_converter_spec.rb:189 # Jekyll::Converters::Scss importing > from external libraries unsafe mode brings in the grid partial > rspec ./spec/scss_converter_spec.rb:181 # Jekyll::Converters::Scss importing > from external libraries unsafe mode recognizes the new load path > rspec ./spec/scss_converter_spec.rb:185 # Jekyll::Converters::Scss importing > from external libraries unsafe mode ensures the sass_dir is still in the load > path > rspec ./spec/scss_converter_spec.rb:207 # Jekyll::Converters::Scss importing > from external libraries unsafe mode with the sass_dir specified twice ensures > the sass_dir only occurrs once in the load path > rspec ./spec/scss_converter_spec.rb:61 # Jekyll::Converters::Scss when > building configurations set the load paths to the _sass dir relative to site > source > rspec ./spec/scss_converter_spec.rb:57 # Jekyll::Converters::Scss when > building configurations allow caching in unsafe mode > rspec ./spec/scss_converter_spec.rb:65 # Jekyll::Converters::Scss when > building configurations allow for other styles > rspec ./spec/scss_converter_spec.rb:71 # Jekyll::Converters::Scss when > building configurations when specifying sass dirs when the sass dir exists > allow the user to specify a different sass dir > rspec ./spec/scss_converter_spec.rb:77 # Jekyll::Converters::Scss when > building configurations when specifying sass dirs when the sass dir exists > not allow sass_dirs outside of site source > rspec ./spec/scss_converter_spec.rb:110 # Jekyll::Converters::Scss when > building configurations in safe mode only contains :syntax, :cache, :style, > and :load_paths keys > rspec ./spec/scss_converter_spec.rb:97 # Jekyll::Converters::Scss when > building configurations in safe mode forces load_paths to be just the local > load path > rspec ./spec/scss_converter_spec.rb:93 # Jekyll::Converters::Scss when > building configurations in safe mode does not allow caching > rspec ./spec/scss_converter_spec.rb:101 # Jekyll::Converters::Scss when > building configurations in safe mode allows the user to specify the style > rspec ./spec/scss_converter_spec.rb:106 # Jekyll::Converters::Scss when > building configurations in safe mode defaults style to :compact > rspec ./spec/scss_converter_spec.rb:51 # Jekyll::Converters::Scss determining > the output file extension always outputs the .css file extension > rspec ./spec/scss_converter_spec.rb:41 # Jekyll::Converters::Scss matching > file extensions matches .scss files > rspec ./spec/scss_converter_spec.rb:45 # Jekyll::Converters::Scss matching > file extensions does not match .sass files > rspec ./spec/scss_converter_spec.rb:128 # Jekyll::Converters::Scss converting > SCSS removes byte order mark from compressed SCSS > rspec ./spec/scss_converter_spec.rb:121 # Jekyll::Converters::Scss converting > SCSS includes the syntax error line in the syntax error message > rspec ./spec/scss_converter_spec.rb:117 # Jekyll::Converters::Scss converting > SCSS produces CSS > rspec ./spec/scss_converter_spec.rb:134 # Jekyll::Converters::Scss converting > SCSS does not include the charset unless asked to > rspec ./spec/scss_converter_spec.rb:153 # Jekyll::Converters::Scss importing > partials uses a compressed style > rspec ./spec/scss_converter_spe
Bug#952032: ruby-jekyll-feed: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-jekyll-feed Version: 0.13.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `expect' for > # > Did you mean? exec > # ./spec/jekyll-feed_spec.rb:345:in `block (3 levels) in (required)>' > > Finished in 3.43 seconds (files took 0.75967 seconds to load) > 54 examples, 54 failures > > Failed examples: > > rspec ./spec/jekyll-feed_spec.rb:82 # JekyllFeed uses last_modified_at where > available > rspec ./spec/jekyll-feed_spec.rb:45 # JekyllFeed puts all the posts in the > feed.xml file > rspec ./spec/jekyll-feed_spec.rb:53 # JekyllFeed does not include assets or > any static files that aren't .html > rspec ./spec/jekyll-feed_spec.rb:32 # JekyllFeed has no layout > rspec ./spec/jekyll-feed_spec.rb:66 # JekyllFeed supports post author name as > a string > rspec ./spec/jekyll-feed_spec.rb:40 # JekyllFeed doesn't have multiple new > lines or trailing whitespace > rspec ./spec/jekyll-feed_spec.rb:70 # JekyllFeed does not output author tag > no author is provided > rspec ./spec/jekyll-feed_spec.rb:78 # JekyllFeed converts markdown posts to > HTML > rspec ./spec/jekyll-feed_spec.rb:36 # JekyllFeed creates a feed.xml file > rspec ./spec/jekyll-feed_spec.rb:58 # JekyllFeed preserves linebreaks in > preformatted text in posts > rspec ./spec/jekyll-feed_spec.rb:90 # JekyllFeed renders Liquid inside posts > rspec ./spec/jekyll-feed_spec.rb:62 # JekyllFeed supports post author name as > an object > rspec ./spec/jekyll-feed_spec.rb:74 # JekyllFeed does use author reference > with data from _data/authors.yml > rspec ./spec/jekyll-feed_spec.rb:86 # JekyllFeed replaces newlines in posts > to spaces > rspec ./spec/jekyll-feed_spec.rb:398 # JekyllFeed categories with > collection-level post categories outputs the category feed > rspec ./spec/jekyll-feed_spec.rb:390 # JekyllFeed categories with > collection-level post categories outputs the primary feed > rspec ./spec/jekyll-feed_spec.rb:367 # JekyllFeed categories with top-level > post categories outputs the category feed > rspec ./spec/jekyll-feed_spec.rb:359 # JekyllFeed categories with top-level > post categories outputs the primary feed > rspec ./spec/jekyll-feed_spec.rb:499 # JekyllFeed excerpt_only flag when > site.excerpt_only flag is true should not set any contents > rspec ./spec/jekyll-feed_spec.rb:519 # JekyllFeed excerpt_only flag when > post.excerpt_only flag is true should not be in contents > rspec ./spec/jekyll-feed_spec.rb:489 # JekyllFeed excerpt_only flag backward > compatibility for no excerpt_only flag should be in contents > rspec ./spec/jekyll-feed_spec.rb:509 # JekyllFeed excerpt_only flag when > site.excerpt_only flag is false should be in contents > rspec ./spec/jekyll-feed_spec.rb:213 # JekyllFeed smartify processes site > title with SmartyPants > rspec ./spec/jekyll-feed_spec.rb:338 # JekyllFeed with site.lang set should > set the language > rspec ./spec/jekyll-feed_spec.rb:323 # JekyllFeed changing the file path via > collection meta renders the feed meta with custom feed path > rspec ./spec/jekyll-feed_spec.rb:319 # JekyllFeed changing the file path via > collection meta should write to atom.xml > rspec ./spec/jekyll-feed_spec.rb:479 # JekyllFeed collections with a custom > path should write to the custom path > rspec ./spec/jekyll-feed_spec.rb:451 # JekyllFeed collections with categories > outputs the collection category feed > rspec ./spec/jekyll-feed_spec.rb:423 # JekyllFeed collections when > initialized as an array outputs the collection feed > rspec ./spec/jekyll-feed_spec.rb:300 # JekyllFeed changing the feed path > renders the feed meta with custom feed path > rspec ./spec/jekyll-feed_spec.rb:296 # JekyllFeed changing the feed path > should write to atom.xml > rspec ./spec/jekyll-feed_spec.rb:330 # JekyllFeed feed stylesheet includes > the stylesheet > rspec ./spec/jekyll-feed_spec.rb:219 # JekyllFeed validation validates > rspec ./spec/jekyll-feed_spec.rb:106 # JekyllFeed images included media > content for mail templates (Mailchimp) > rspec ./spec/jekyll-feed_spec.rb:100 # JekyllFeed images includes the item > image > rspec ./spec/jekyll-feed_spec.rb:260 # JekyllFeed with a baseurl renders the > feed meta > rspec ./spec/jekyll-feed_spec.rb:254 # JekyllFeed with a baseurl correctly > adds the baseurl to the posts > rspec ./spec/jekyll-feed_spec.rb:144 # JekyllFeed parsing includes the item's > excerpt > rspec ./spec/jekyll-feed_spec.rb:149 # JekyllFeed parsing doesn't include the > item's excerpt i
Bug#952028: gist: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: subject.filename.should be filename
Source: gist
Version: 5.0.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: subject.filename.should be filename
>
> NameError:
>uninitialized constant RSpec::Support::Differ
> # ./spec/auth_token_file_spec.rb:26:in `block (4 levels) in (required)>'
>
> Finished in 0.06116 seconds (files took 0.78733 seconds to load)
> 25 examples, 2 failures
>
> Failed examples:
>
> rspec ./spec/auth_token_file_spec.rb:12 # Gist::AuthTokenFile::filename with
> default GITHUB_URL is ~/.gist
> rspec ./spec/auth_token_file_spec.rb:24 # Gist::AuthTokenFile::filename with
> custom GITHUB_URL is ~/.gist.{custom_github_url}
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/gist_5.0.0-3_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.
Bug#952030: ruby-listen: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: rel_path = path.relative_path_from(dir).to_s
Source: ruby-listen
Version: 3.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: rel_path = path.relative_path_from(dir).to_s
>
> TypeError:
>no implicit conversion of RSpec::Mocks::InstanceVerifyingDouble into
> String
> # ./lib/listen/adapter/linux.rb:48:in `_process_event'
> # ./lib/listen/adapter/base.rb:42:in `block (2 levels) in configure'
> # ./spec/lib/listen/adapter/linux_spec.rb:99:in `block (5 levels) in
> '
> # ./spec/lib/listen/adapter/linux_spec.rb:98:in `each'
> # ./spec/lib/listen/adapter/linux_spec.rb:98:in `block (4 levels) in
> '
> # ./spec/lib/listen/adapter/linux_spec.rb:118:in `block (3 levels) in
> '
>
> Finished in 2 minutes 17.5 seconds (files took 0.25371 seconds to load)
> 316 examples, 3 failures, 1 pending
>
> Failed examples:
>
> rspec ./spec/lib/listen/adapter/linux_spec.rb:121 # Listen::Adapter::Linux
> _callback recognizes moved_from as moved_from
> rspec ./spec/lib/listen/adapter/linux_spec.rb:111 # Listen::Adapter::Linux
> _callback recognizes close_write as modify
> rspec ./spec/lib/listen/adapter/linux_spec.rb:116 # Listen::Adapter::Linux
> _callback recognizes moved_to as moved_to
>
> Randomized with seed 44939
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --exclude-pattern
> ./spec/lib/listen/adapter/\{darwin,windows\}_spec.rb --format documentation
> failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-listen_3.1.5-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.
Bug#952036: ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `[]=' for nil:NilClass
Source: ruby-fakefs Version: 0.20.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: undefined method `[]=' for nil:NilClass > /usr/lib/ruby/2.7.0/tempfile.rb:128:in `block in initialize' > /<>/lib/fakefs/dir.rb:210:in `create' > /usr/lib/ruby/2.7.0/tempfile.rb:127:in `initialize' > /usr/lib/ruby/2.7.0/tempfile.rb:287:in `new' > /usr/lib/ruby/2.7.0/tempfile.rb:287:in `open' > /usr/lib/ruby/vendor_ruby/minitest/assertions.rb:67:in `diff' > /usr/lib/ruby/vendor_ruby/minitest/assertions.rb:217:in `block in > assert_equal' > /usr/lib/ruby/vendor_ruby/minitest/assertions.rb:602:in `block in message' > /usr/lib/ruby/vendor_ruby/minitest/assertions.rb:182:in `assert' > /usr/lib/ruby/vendor_ruby/minitest/assertions.rb:218:in `assert_equal' > /<>/test/fakefs_test.rb:1764:in `block in > test_file_utils_cp_allows_verbose_option' > /<>/test/fakefs_test.rb:35:in > `perform_with_both_string_paths_and_pathnames' > /<>/test/fakefs_test.rb:1762:in > `test_file_utils_cp_allows_verbose_option' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 705 runs, 1414 assertions, 0 failures, 6 errors, 1 skips > > You have skipped tests. Run with --verbose for details. > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-fakefs_0.20.1-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.
Bug#952026: ruby-handlebars-assets: FTBFS: ERROR: Test "ruby2.5" failed: Invalid gemspec in [handlebars_assets.gemspec]: No such file or directory - git
Source: ruby-handlebars-assets Version: 2:0.23.3+dfsg-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Invalid gemspec in [handlebars_assets.gemspec]: No such file or directory - > git > GEM_PATH=/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -e gem\ \"handlebars_assets\" > > ┌──┐ > │ Run tests for ruby2.5 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -S rake -f debian/ruby-tests.rake > Run options: --seed 61834 > > # Running: > > .EEE.E.E > > Finished in 23.198956s, 1.2070 runs/s, 0.3448 assertions/s. > > 1) Error: > HandlebarsAssets::CompilingTest#test_patching_handlebars: > ExecJS::ProgramError: ReferenceError: Handlebars is not defined > (execjs):2:71486 > (execjs):19:14 > (execjs):1:40 > Object. ((execjs):1:58) > Module._compile (internal/modules/cjs/loader.js:778:30) > Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) > Module.load (internal/modules/cjs/loader.js:653:32) > tryModuleLoad (internal/modules/cjs/loader.js:593:12) > Function.Module._load (internal/modules/cjs/loader.js:585:3) > Function.Module.runMain (internal/modules/cjs/loader.js:831:12) > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:39:in `exec' > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:14:in `initialize' > /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:44:in `new' > /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:44:in `compile' > /usr/lib/ruby/vendor_ruby/execjs/module.rb:27:in `compile' > /<>/lib/handlebars_assets/handlebars.rb:31:in `context' > /<>/lib/handlebars_assets/handlebars.rb:10:in `precompile' > /<>/test/handlebars_assets/compiling_test.rb:26:in > `test_patching_handlebars' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 2) Error: > HandlebarsAssets::HamlbarsTest#test_render_haml: > ExecJS::ProgramError: ReferenceError: Handlebars is not defined > eval (eval at ((execjs):2:8), :1:1) > (execjs):2:8 > (execjs):8:14 > (execjs):1:40 > Object. ((execjs):1:58) > Module._compile (internal/modules/cjs/loader.js:778:30) > Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) > Module.load (internal/modules/cjs/loader.js:653:32) > tryModuleLoad (internal/modules/cjs/loader.js:593:12) > Function.Module._load (internal/modules/cjs/loader.js:585:3) > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:39:in `exec' > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:21:in `eval' > /usr/lib/ruby
Bug#952034: ruby-jekyll-sitemap: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-jekyll-sitemap Version: 1.4.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `expect' for > # > Did you mean? exec > # ./spec/jekyll-sitemap_spec.rb:56:in `block (3 levels) in (required)>' > > Finished in 1.53 seconds (files took 0.36077 seconds to load) > 39 examples, 39 failures > > Failed examples: > > rspec ./spec/jekyll-sitemap_spec.rb:48 # Jekyll::JekyllSitemap puts all the > posts in the sitemap.xml file > rspec ./spec/jekyll-sitemap_spec.rb:34 # Jekyll::JekyllSitemap doesn't have > multiple new lines or trailing whitespace > rspec ./spec/jekyll-sitemap_spec.rb:44 # Jekyll::JekyllSitemap only strips > 'index.html' from end of permalink > rspec ./spec/jekyll-sitemap_spec.rb:39 # Jekyll::JekyllSitemap puts all the > pages in the sitemap.xml file > rspec ./spec/jekyll-sitemap_spec.rb:95 # Jekyll::JekyllSitemap does include > assets or any static files with .xhtml and .htm extensions > rspec ./spec/jekyll-sitemap_spec.rb:82 # Jekyll::JekyllSitemap puts all the > static HTML files in the sitemap.xml file > rspec ./spec/jekyll-sitemap_spec.rb:26 # Jekyll::JekyllSitemap has no layout > rspec ./spec/jekyll-sitemap_spec.rb:86 # Jekyll::JekyllSitemap does not > include assets or any static files that aren't .html > rspec ./spec/jekyll-sitemap_spec.rb:118 # Jekyll::JekyllSitemap does not > include posts that have set 'sitemap: false' > rspec ./spec/jekyll-sitemap_spec.rb:113 # Jekyll::JekyllSitemap does not > include any static files that have set 'sitemap: false' > rspec ./spec/jekyll-sitemap_spec.rb:109 # Jekyll::JekyllSitemap does not > include any static files that have set 'sitemap: false' > rspec ./spec/jekyll-sitemap_spec.rb:30 # Jekyll::JekyllSitemap creates a > sitemap.xml file > rspec ./spec/jekyll-sitemap_spec.rb:122 # Jekyll::JekyllSitemap does not > include pages that have set 'sitemap: false' > rspec ./spec/jekyll-sitemap_spec.rb:130 # Jekyll::JekyllSitemap correctly > formats timestamps of static files > rspec ./spec/jekyll-sitemap_spec.rb:91 # Jekyll::JekyllSitemap converts > static index.html files to permalink version > rspec ./spec/jekyll-sitemap_spec.rb:76 # Jekyll::JekyllSitemap generates the > correct date for each of the posts > rspec ./spec/jekyll-sitemap_spec.rb:134 # Jekyll::JekyllSitemap includes the > correct number of items > rspec ./spec/jekyll-sitemap_spec.rb:100 # Jekyll::JekyllSitemap does include > assets or any static files with .pdf extension > rspec ./spec/jekyll-sitemap_spec.rb:126 # Jekyll::JekyllSitemap does not > include the 404 page > rspec ./spec/jekyll-sitemap_spec.rb:104 # Jekyll::JekyllSitemap does not > include any static files named 404.html > rspec ./spec/jekyll-sitemap_spec.rb:167 # Jekyll::JekyllSitemap with a > baseurl adds baseurl to robots.txt > rspec ./spec/jekyll-sitemap_spec.rb:161 # Jekyll::JekyllSitemap with a > baseurl correctly adds the baseurl to the posts > rspec ./spec/jekyll-sitemap_spec.rb:148 # Jekyll::JekyllSitemap with a > baseurl correctly adds the baseurl to the static files > rspec ./spec/jekyll-sitemap_spec.rb:156 # Jekyll::JekyllSitemap with a > baseurl correctly adds the baseurl to the pages > rspec ./spec/jekyll-sitemap_spec.rb:152 # Jekyll::JekyllSitemap with a > baseurl correctly adds the baseurl to the collections > rspec ./spec/jekyll-sitemap_spec.rb:187 # Jekyll::JekyllSitemap with urls > that needs URI encoding does not double-escape urls > rspec ./spec/jekyll-sitemap_spec.rb:178 # Jekyll::JekyllSitemap with urls > that needs URI encoding performs URI encoding of site url > rspec ./spec/jekyll-sitemap_spec.rb:202 # Jekyll::JekyllSitemap with urls > that needs URI encoding readme renders liquid > rspec ./spec/jekyll-sitemap_spec.rb:194 # Jekyll::JekyllSitemap with urls > that needs URI encoding readme has no layout > rspec ./spec/jekyll-sitemap_spec.rb:198 # Jekyll::JekyllSitemap with urls > that needs URI encoding readme creates a robots.txt file > rspec ./spec/jekyll-sitemap_spec.rb:243 # Jekyll::JekyllSitemap with > user-defined robots.txt as a page at root doesn't override the robots file > rspec ./spec/jekyll-sitemap_spec.rb:251 # Jekyll::JekyllSitemap with > user-defined robots.txt as a page with permalink in a subdir doesn't override > the robots file > rspec ./spec/jekyll-sitemap_spec.rb:227 # Jekyll::JekyllSitemap with > user-defined robots.txt as a static-file at source-root doesn't override the > robots file > rspec ./spec/jekyll-sitemap_spec.rb:235 # Jekyll::JekyllSitemap with > us
Bug#952029: ruby-mathml: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: e.rest << @scanner.rest.to_s
Source: ruby-mathml
Version: 0.14-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: e.rest << @scanner.rest.to_s
>
> FrozenError:
> can't modify frozen String: ""
> # ./lib/math_ml/latex.rb:459:in `rescue in parse_into'
> # ./lib/math_ml/latex.rb:450:in `parse_into'
> # ./lib/math_ml/latex.rb:392:in `parse'
> # ./lib/math_ml/util.rb:331:in `parse_eqnarray'
> # ./spec/math_ml/util_spec.rb:639:in `block (3 levels) in (required)>'
> # ./lib/math_ml/util.rb:170:in `encode'
> # ./spec/math_ml/util_spec.rb:638:in `block (2 levels) in (required)>'
> # --
> # --- Caused by: ---
> # MathML::LaTeX::ParseError:
> # Need more column.
> # ./lib/math_ml/latex.rb:1045:in `env_array_row'
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/math_ml/element_spec.rb:5:in `block (2 levels) in (required)>'.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 0.48445 seconds (files took 0.13909 seconds to load)
> 105 examples, 14 failures
>
> Failed examples:
>
> rspec ./spec/math_ml/latex/macro_spec.rb:27 # MathML::LaTeX::Macro #parse
> rspec ./spec/math_ml/latex/macro_spec.rb:63 # MathML::LaTeX::Macro #commands
> rspec ./spec/math_ml/latex/macro_spec.rb:69 # MathML::LaTeX::Macro
> #expand_command
> rspec ./spec/math_ml/latex/macro_spec.rb:80 # MathML::LaTeX::Macro
> #environments
> rspec ./spec/math_ml/latex/macro_spec.rb:87 # MathML::LaTeX::Macro
> #expand_environment
> rspec ./spec/math_ml/latex/macro_spec.rb:99 # MathML::LaTeX::Macro
> #expand_with_options
> rspec ./spec/math_ml/latex/parser_spec.rb:135 # MathML::LaTeX::Parser#parse
> should process sqrt
> rspec ./spec/math_ml/latex/parser_spec.rb:214 # MathML::LaTeX::Parser#parse
> should process array
> rspec ./spec/math_ml/latex/parser_spec.rb:380 # MathML::LaTeX::Parser#parse
> can be used with macro
> rspec ./spec/math_ml/latex/parser_spec.rb:446 # MathML::LaTeX::Parser#parse
> can be used with macro with option
> rspec ./spec/math_ml/latex/parser_spec.rb:484 # MathML::LaTeX::Parser#parse
> can be used in safe mode
> rspec ./spec/math_ml/latex/scanner_spec.rb:159 # MathML::LaTeX::Scanner
> #scan_option
> rspec ./spec/math_ml/latex/scanner_spec.rb:181 # MathML::LaTeX::Scanner
> #check_option
> rspec ./spec/math_ml/util_spec.rb:618 # MathML::Util::SimpleLaTeX parse
> eqnarray
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-mathml_0.14-4_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.
Bug#952031: ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.7" failed.
Source: ruby-active-model-serializers Version: 0.10.8-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-active-model-serializers/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" > "test/action_controller/adapter_selector_test.rb" > "test/action_controller/explicit_serializer_test.rb" > "test/action_controller/json/include_test.rb" > "test/action_controller/json_api/deserialization_test.rb" > "test/action_controller/json_api/errors_test.rb" > "test/action_controller/json_api/fields_test.rb" > "test/action_controller/json_api/linked_test.rb" > "test/action_controller/json_api/transform_test.rb" > "test/action_controller/lookup_proc_test.rb" > "test/action_controller/namespace_lookup_test.rb" > "test/action_controller/serialization_scope_name_test.rb" > "test/action_controller/serialization_test.rb" > "test/active_model_serializers/adapter_for_test.rb" > "test/active_model_serializers/json_pointer_test.rb" > "test/active_model_serializers/logging_test.rb" > "test/active_model_serializers/model_test.rb" > "test/active_model_serializers/test/serializer_test.rb" > "test/active_record_test.rb" "test/adapter/attributes_test.rb" > "test/adapter/deprecation_test.rb" "test/adapter/json/belongs_to_test.rb" > "test/adapter/json/collection_test.rb" "test/adapter/json/has_many_test.rb" > "test/adapter/json/transform_test.rb" > "test/adapter/json_api/belongs_to_test.rb" > "test/adapter/json_api/collection_test.rb" > "test/adapter/json_api/errors_test.rb" "test/adapter/json_api/fields_test.rb" > "test/adapter/json_api/has_many_explicit_serializer_test.rb" > "test/adapter/json_api/has_many_test.rb" > "test/adapter/json_api/has_one_test.rb" > "test/adapter/json_api/include_data_if_sideloaded_test.rb" > "test/adapter/json_api/json_api_test.rb" > "test/adapter/json_api/linked_test.rb" "test/adapter/json_api/links_test.rb" > "test/adapter/json_api/parse_test.rb" > "test/adapter/json_api/relationship_test.rb" > "test/adapter/json_api/resource_meta_test.rb" > "test/adapter/json_api/toplevel_jsonapi_test.rb" > "test/adapter/json_api/transform_test.rb" > "test/adapter/json_api/type_test.rb" "test/adapter/json_test.rb" > "test/adapter/null_test.rb" "test/adapter/polymorphic_test.rb" > "test/adapter_test.rb" "test/array_serializer_test.rb" "test/cache_test.rb" > "test/collection_serializer_test.rb" > "test/generators/scaffold_controller_generator_test.rb" > "test/generators/serializer_generator_test.rb" "test/lint_test.rb" > "test/logger_test.rb" "test/poro_test.rb" > "test/serializable_resource_test.rb" > "test/serializers/association_macros_test.rb" > "test/serializers/associations_test.rb" "test/serializers/attribute_test.rb" > "test/serializers/attributes_test.rb" > "test/serializers/configuration_test.rb" "test/serializers/fieldset_test.rb" > "test/serializers/meta_test.rb" "test/serializers/options_test.rb" > "test/serializers/read_attribute_for_serialization_test.rb" > "test/serializers/reflection_test.rb" "test/serializers/root_test.rb" > "test/serializers/serialization_test.rb" > "test/serializers/serializer_for_test.rb" > "test/serializers/serializer_for_with_namespace_test.rb" -v > Running without SimpleCov > /u
Bug#952035: ruby-ridley: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError:
Source: ruby-ridley Version: 5.1.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ArgumentError: >extra arguments > # ./lib/ridley/connection.rb:148:in `block in stream' > # ./lib/ridley/connection.rb:147:in `stream' > # (celluloid):0:in `remote procedure call' > # (celluloid):0:in `remote procedure call' > # ./lib/ridley/chef_objects/cookbook_object.rb:140:in `download_file' > # ./lib/ridley/chef_objects/cookbook_object.rb:90:in `block (2 levels) > in download' > # ./lib/ridley/chef_objects/cookbook_object.rb:87:in `each' > # ./lib/ridley/chef_objects/cookbook_object.rb:87:in `block in download' > # ./lib/ridley/chef_objects/cookbook_object.rb:84:in `each' > # ./lib/ridley/chef_objects/cookbook_object.rb:84:in `download' > # ./lib/ridley/resources/cookbook_resource.rb:84:in `download' > # (celluloid):0:in `remote procedure call' > # ./spec/acceptance/cookbook_resource_spec.rb:18:in `block (4 levels) in > ' > > Deprecation Warnings: > > RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= > is deprecated, it is now set to true as default and setting it to false has > no effect. > > Using `stub` from rspec-mocks' old `:should` syntax without explicitly > enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly > enable `:should` instead. Called from > /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:26:in `public_send'. > > > If you need more of the backtrace for any of these deprecations to > identify where to make the necessary changes, you can configure > `config.raise_errors_for_deprecations!`, and it will turn the > deprecation warnings into errors, giving you the full backtrace. > > 2 deprecation warnings total > > Finished in 4.85 seconds (files took 1.96 seconds to load) > 461 examples, 1 failure, 18 pending > > Failed examples: > > rspec ./spec/acceptance/cookbook_resource_spec.rb:20 # Client API operations > downloading a cookbook when the cookbook of the name/version is found > downloads the cookbook to the destination > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-ridley_5.1.1-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.
Bug#952020: ruby-roxml: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError:
Source: ruby-roxml Version: 4.0.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `new' for BigDecimal:Class > # ./lib/roxml/definition.rb:179:in `block (3 levels) in block_shorthands' > # ./lib/roxml/definition.rb:127:in `block in all' > # ./lib/roxml/definition.rb:126:in `map' > # ./lib/roxml/definition.rb:126:in `all' > # ./lib/roxml/definition.rb:178:in `block (2 levels) in block_shorthands' > # ./spec/definition_spec.rb:301:in `block (6 levels) in ' > > Finished in 0.39464 seconds (files took 1.68 seconds to load) > 213 examples, 4 failures, 19 pending > > Failed examples: > > rspec ./spec/definition_spec.rb:283 # ROXML::Definition :as for block > shorthand BigDecimal should translate text to decimal numbers > rspec ./spec/definition_spec.rb:290 # ROXML::Definition :as for block > shorthand BigDecimal should raise on non-decimal values > rspec ./spec/definition_spec.rb:295 # ROXML::Definition :as for block > shorthand BigDecimal should extract what it can > rspec ./spec/definition_spec.rb:300 # ROXML::Definition :as for block > shorthand BigDecimal when passed an array should translate the array elements > to integer > > /usr/bin/ruby2.7 -Iexamples > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > ./spec/definition_spec.rb ./spec/examples/active_record_spec.rb > ./spec/examples/amazon_spec.rb ./spec/examples/current_weather_spec.rb > ./spec/examples/dashed_elements_spec.rb ./spec/examples/library_spec.rb > ./spec/examples/library_with_fines_spec.rb ./spec/examples/person_spec.rb > ./spec/examples/post_spec.rb ./spec/examples/search_query_spec.rb > ./spec/examples/twitter_spec.rb ./spec/reference_spec.rb ./spec/roxml_spec.rb > ./spec/xml/array_spec.rb ./spec/xml/attributes_spec.rb > ./spec/xml/encoding_spec.rb ./spec/xml/namespace_spec.rb > ./spec/xml/namespaces_spec.rb ./spec/xml/object_spec.rb > ./spec/xml/parser_spec.rb ./spec/xml/text_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-roxml_4.0.0-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.
Bug#952025: ruby-grape: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: spec = parsers(**options)[api_format]
Source: ruby-grape
Version: 1.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: spec = parsers(**options)[api_format]
>
>Grape::Parser received :parsers with unexpected arguments
> expected: ({})
> got: (no args)
>Diff:
>@@ -1,2 +1,2 @@
>-[{}]
>+[]
> # ./lib/grape/parser.rb:19:in `parser_for'
> # ./spec/grape/parser_spec.rb:46:in `block (3 levels) in (required)>'
>
> Finished in 2.8 seconds (files took 1.45 seconds to load)
> 1792 examples, 2 failures, 1 pending
>
> Failed examples:
>
> rspec ./spec/grape/exceptions/validation_spec.rb:4 #
> Grape::Exceptions::Validation fails when params are missing
> rspec ./spec/grape/parser_spec.rb:44 # Grape::Parser.parser_for calls .parsers
>
> [33m[Coveralls] Outside the CI environment, not sending data.[0m
> SimpleCov failed with exit 1
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> ./spec/grape/api/custom_validations_spec.rb
> ./spec/grape/api/deeply_included_options_spec.rb
> ./spec/grape/api/inherited_helpers_spec.rb
> ./spec/grape/api/invalid_format_spec.rb
> ./spec/grape/api/namespace_parameters_in_route_spec.rb
> ./spec/grape/api/nested_helpers_spec.rb
> ./spec/grape/api/optional_parameters_in_route_spec.rb
> ./spec/grape/api/parameters_modification_spec.rb
> ./spec/grape/api/patch_method_helpers_spec.rb
> ./spec/grape/api/recognize_path_spec.rb
> ./spec/grape/api/required_parameters_in_route_spec.rb
> ./spec/grape/api/required_parameters_with_invalid_method_spec.rb
> ./spec/grape/api/shared_helpers_exactly_one_of_spec.rb
> ./spec/grape/api/shared_helpers_spec.rb ./spec/grape/api_spec.rb
> ./spec/grape/dsl/callbacks_spec.rb ./spec/grape/dsl/configuration_spec.rb
> ./spec/grape/dsl/desc_spec.rb ./spec/grape/dsl/headers_spec.rb
> ./spec/grape/dsl/helpers_spec.rb ./spec/grape/dsl/inside_route_spec.rb
> ./spec/grape/dsl/logger_spec.rb ./spec/grape/dsl/middleware_spec.rb
> ./spec/grape/dsl/parameters_spec.rb ./spec/grape/dsl/request_response_spec.rb
> ./spec/grape/dsl/routing_spec.rb ./spec/grape/dsl/settings_spec.rb
> ./spec/grape/dsl/validations_spec.rb ./spec/grape/endpoint_spec.rb
> ./spec/grape/exceptions/body_parse_errors_spec.rb
> ./spec/grape/exceptions/invalid_accept_header_spec.rb
> ./spec/grape/exceptions/invalid_formatter_spec.rb
> ./spec/grape/exceptions/invalid_versioner_option_spec.rb
> ./spec/grape/exceptions/missing_mime_type_spec.rb
> ./spec/grape/exceptions/missing_option_spec.rb
> ./spec/grape/exceptions/unknown_options_spec.rb
> ./spec/grape/exceptions/unknown_validator_spec.rb
> ./spec/grape/exceptions/validation_errors_spec.rb
> ./spec/grape/exceptions/validation_spec.rb
> ./spec/grape/extensions/param_builders/hash_spec.rb
> ./spec/grape/extensions/param_builders/hash_with_indifferent_access_spec.rb
> ./spec/grape/extensions/param_builders/hashie/mash_spec.rb
> ./spec/grape/integration/global_namespace_function_spec.rb
> ./spec/grape/integration/rack_sendfile_spec.rb
> ./spec/grape/integration/rack_spec.rb ./spec/grape/loading_spec.rb
> ./spec/grape/middleware/auth/base_spec.rb
> ./spec/grape/middleware/auth/dsl_spec.rb
> ./spec/grape/middleware/auth/strategies_spec.rb
> ./spec/grape/middleware/base_spec.rb ./spec/grape/middleware/error_spec.rb
> ./spec/grape/middleware/exception_spec.rb
> ./spec/grape/middleware/formatter_spec.rb
> ./spec/grape/middleware/globals_spec.rb ./spec/grape/middleware/stack_spec.rb
> ./spec/grape/middleware/versioner/accept_version_header_spec.rb
> ./spec/grape/middleware/versioner/header_spec.rb
> ./spec/grape/middleware/versioner/param_spec.rb
> ./spec/grape/middleware/versioner/path_spec.rb
> ./spec/grape/middleware/versioner_spec.rb ./spec/grape/parser_spec.rb
> ./spec/grape/path_spec.rb ./spec/grape/presenters/presenter_spec.rb
> ./spec/grape/request_spec.rb ./spec/grape/util/inheritable_setting_spec.rb
> ./spec/grape/util/inheritable_values_spec.rb
> ./spec/grape/util/reverse_stackable_values_spec.rb
> ./spec/grape/util/stackable_values_spec.rb
> ./spec/grape/util/strict_hash_configuration_spec.rb
> ./spec/grape/validations/attributes_iterator_spec.rb
> ./spec/grape/validations/instance_behaivour_spec.rb
> ./spec/grape/validations/params_scope_spec.rb
> ./spec/grape/validations/types_spec.rb
> ./spec/grape/validations/validators/all_or_none_spec.
Bug#952023: ruby-jekyll-redirect-from: FTBFS: ERROR: Test "ruby2.5" failed: LoadError:
Source: ruby-jekyll-redirect-from
Version: 0.16.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> LoadError:
> cannot load such file -- rspec/expectations
> # ./spec/spec_helper.rb:10:in `block in '
> # ./spec/spec_helper.rb:6:in `'
> Run options: include {:focus=>true}
>
> All examples were filtered out; ignoring {:focus=>true}
> No examples found.
>
>
> Finished in 0.2 seconds (files took 0.27874 seconds to load)
> 0 examples, 0 failures, 1 error occurred outside of examples
>
> /usr/bin/ruby2.5
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.5" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-jekyll-redirect-from_0.16.0-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.
Bug#952016: ruby-graffiti: FTBFS: ERROR: Test "ruby2.7" failed.
Source: ruby-graffiti
Version: 2.3.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-graffiti/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-graffiti/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
> ruby2.7 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> F
> ===
> Failure: test_dangling_blank_node(TC_Storage):
> SquishSelect initialization raised FrozenError: can't modify frozen String:
> "".
>is not true.
> /<>/test/ts_graffiti.rb:365:in `rescue in test_squish_select'
> /<>/test/ts_graffiti.rb:362:in `test_squish_select'
> /<>/test/ts_graffiti.rb:153:in `test_dangling_blank_node'
> 150: INNER JOIN resource AS b ON (a.part_of_subproperty = b.id) AND
> (b.uriref = 't' AND b.label =
> 'http://www.nongnu.org/samizdat/rdf/schema#inReplyTo')
> 151: WHERE (a.id IS NOT NULL)"
> 152:
> => 153: test_squish_select(squish, sql) do |query|
> 154: assert_equal %w[?msg], query.nodes
> 155: assert query.pattern.include?(["#{@ns['s']}inReplyTo",
> "?msg", "?parent", nil, false])
> 156: assert_equal @ns['s'], query.ns['s']
> ===
> F
> ===
> Failure: test_except(TC_Storage):
> SquishSelect initialization raised FrozenError: can't modify frozen String:
> "".
>is not true.
> /<>/test/ts_graffiti.rb:365:in `rescue in test_squish_select'
> /<>/test/ts_graffiti.rb:362:in `test_squish_select'
> /<>/test/ts_graffiti.rb:206:in `test_except'
> 203: AND (d.id IS NULL)
> 204: ORDER BY a.published_date DESC"
> 205:
> => 206: test_squish_select(squish, sql)
> 207: end
> 208:
> 209: def test_except_group_by
> ===
> ..F
> ===
> Failure: test_external_resource_no_self_join(TC_Storage):
> SquishSelect initialization raised FrozenError: can't modify frozen String:
> "".
>is not true.
> /<>/test/ts_graffiti.rb:365:in `rescue in test_squish_select'
> /<>/test/ts_graffiti.rb:362:in `test_squish_select'
> /<>/test/ts_graffiti.rb:168:in
> `test_external_resource_no_self_join'
> 165: WHERE (a.id IS NOT NULL)
> 166: AND ((a.uriref = 't' AND a.label =
> 'http://www.nongnu.org/samizdat/rdf/tag#Translation'))"
> 167:
> => 168: test_squish_select(squish, sql) do |query|
> 169: assert_equal %w[?id], query.nodes
> 170: assert query.pattern.include?(["#{@ns['s']}id",
> "#{@ns['tag']}Translation", "?id", nil, false])
> 171: assert_equal @ns['s'], query.ns['s']
> ===
> .F
> ===
> Failure: test_optional(TC_Storage):
> SquishSelect initialization raised FrozenError: can't modify frozen String:
> "".
>is not true.
> /<>/test/ts_graffiti.rb:365:in `rescue in test_squish_select'
> /<>/test/ts_graffiti.rb:362:in `test_squish_select'
> /<>/test/ts_graffiti.rb:259:in `test_optional'
> 256: WHERE (a.published_date IS NOT NULL)
> 257: AND ((a.id = 1))"
> 258:
> => 259: test_squish_select(squish, sql)
> 260: end
> 261:
> 262: def test_except_optional_transitive
> ===
> F
> ===
> Failure: test_query_assert(TC_Storage):
> SquishAssert initializ
Bug#952018: ruby-http-accept-language: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-http-accept-language Version: 2.1.1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `expect' for > # > Did you mean? exec > # ./spec/parser_spec.rb:62:in `block (2 levels) in ' > > Finished in 0.01261 seconds (files took 0.12149 seconds to load) > 18 examples, 18 failures > > Failed examples: > > rspec ./spec/auto_locale_spec.rb:37 # HttpAcceptLanguage::AutoLocale > available languages includes accept_languages take a suitable locale > rspec ./spec/auto_locale_spec.rb:50 # HttpAcceptLanguage::AutoLocale > available languages do not include accept_languages set the locale to default > rspec ./spec/auto_locale_spec.rb:65 # HttpAcceptLanguage::AutoLocale default > locale is ja set the locale to default > rspec ./spec/middleware_spec.rb:31 # Rack integration handles reuse of the > env instance > rspec ./spec/middleware_spec.rb:42 # Rack integration decodes the > HTTP_ACCEPT_LANGUAGE header > rspec ./spec/middleware_spec.rb:47 # Rack integration finds the first > available language > rspec ./spec/parser_spec.rb:9 # HttpAcceptLanguage::Parser should return > empty array > rspec ./spec/parser_spec.rb:14 # HttpAcceptLanguage::Parser should properly > split > rspec ./spec/parser_spec.rb:18 # HttpAcceptLanguage::Parser should ignore > jambled header > rspec ./spec/parser_spec.rb:23 # HttpAcceptLanguage::Parser should properly > respect whitespace > rspec ./spec/parser_spec.rb:28 # HttpAcceptLanguage::Parser should find first > available language > rspec ./spec/parser_spec.rb:32 # HttpAcceptLanguage::Parser should find first > compatible language > rspec ./spec/parser_spec.rb:37 # HttpAcceptLanguage::Parser should find first > compatible from user preferred > rspec ./spec/parser_spec.rb:42 # HttpAcceptLanguage::Parser should accept > symbols as available languages > rspec ./spec/parser_spec.rb:47 # HttpAcceptLanguage::Parser should accept and > ignore wildcards > rspec ./spec/parser_spec.rb:52 # HttpAcceptLanguage::Parser should sanitize > available language names > rspec ./spec/parser_spec.rb:56 # HttpAcceptLanguage::Parser should accept > available language names as symbols and return them as strings > rspec ./spec/parser_spec.rb:60 # HttpAcceptLanguage::Parser should find most > compatible language from user preferred > > /usr/bin/ruby2.5 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.5" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-http-accept-language_2.1.1-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.
Bug#952024: ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
Source: ruby-rspec-puppet
Version: 2.7.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> LoadError:
> libfacter was not found. Please make sure it was installed to the expected
> location.
> cannot load such file -- libfacter.so
> # ./lib/rspec-puppet.rb:1:in `'
> # ./spec/spec_helper.rb:11:in `'
> # ./spec/unit/monkey_patches_spec.rb:1:in `'
> # --
> # --- Caused by: ---
> # LoadError:
> # cannot load such file -- libfacter.so
> # ./lib/rspec-puppet.rb:1:in `'
>
> Finished in 0.4 seconds (files took 2.18 seconds to load)
> 0 examples, 0 failures, 87 errors occurred outside of examples
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-rspec-puppet_2.7.8-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.
Bug#952019: ruby-json-schema: FTBFS: ERROR: Test "ruby2.7" failed.
Source: ruby-json-schema Version: 2.8.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-json-schema/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"json-schema\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-json-schema/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" > "test/all_of_ref_schema_test.rb" "test/any_of_ref_schema_test.rb" > "test/bad_schema_ref_test.rb" "test/caching_test.rb" > "test/common_test_suite_test.rb" "test/custom_format_test.rb" > "test/draft1_test.rb" "test/draft2_test.rb" "test/draft3_test.rb" > "test/draft4_test.rb" "test/extended_schema_test.rb" > "test/extends_nested_test.rb" "test/files_test.rb" > "test/fragment_resolution_test.rb" > "test/fragment_validation_with_ref_test.rb" "test/full_validation_test.rb" > "test/initialize_data_test.rb" "test/list_option_test.rb" > "test/load_ref_schema_test.rb" "test/merge_missing_values_test.rb" > "test/min_items_test.rb" "test/one_of_test.rb" > "test/relative_definition_test.rb" "test/ruby_schema_test.rb" > "test/schema_reader_test.rb" "test/schema_validation_test.rb" > "test/stringify_test.rb" "test/type_attribute_test.rb" > "test/uri_parsing_test.rb" "test/uri_util_test.rb" > "test/validator_schema_reader_test.rb" "test/support/test_helper.rb" -v > /usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:370: warning: assigned but > unused variable - pathlen > /usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:51: warning: method > redefined; discarding old initialize > /usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: warning: method > redefined; discarding old add_cert > /usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: warning: method > redefined; discarding old add_file > /usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: warning: method > redefined; discarding old add_path > /usr/lib/ruby/vendor_ruby/em-socksify/errors.rb:5: warning: parentheses after > method name is interpreted as an argument list, not a decomposed argument > /usr/lib/ruby/vendor_ruby/cookiejar/cookie.rb:183: warning: mismatched > indentations at 'end' with 'else' at 181 > /usr/lib/ruby/vendor_ruby/cookiejar/jar.rb:225: warning: mismatched > indentations at 'end' with 'else' at 223 > Run options: -v --seed 26552 > > # Running: > > FilesTest#test_both_from_file = 0.01 s = . > FilesTest#test_data_from_json_v4 = 0.01 s = . > FilesTest#test_file_extends = 0.02 s = . > FilesTest#test_data_from_file_v4 = 0.01 s = . > FilesTest#test_data_from_file_v3 = 0.01 s = . > FilesTest#test_file_ref = 0.01 s = . > FilesTest#test_schema_from_file = 0.01 s = . > FilesTest#test_data_from_json_v3 = 0.01 s = . > ExtendsNestedTest#test_invalid_inner = 0.02 s = . > ExtendsNestedTest#test_valid_inner = 0.02 s = . > ExtendsNestedTest#test_valid_outer_extended = 0.02 s = . > ExtendsNestedTest#test_invalid_outer = 0.01 s = . > ExtendsNestedTest#test_valid_outer = 0.02 s = . > SchemaValidationTest#test_draft04_validation = 0.01 s = . > SchemaValidationTest#test_validate_just_schema_draft03 = 0.01 s = . > SchemaValidationTest#test_validate_schema_with_symbol_keys = 0.01 s = . > SchemaValidationTest#test_schema_validation_from_different_directory = 0.01 s > = . > Sch
Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
Source: ruby-puppet-syntax Version: 2.6.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > libfacter was not found. Please make sure it was installed to the expected > location. > cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > # ./lib/puppet-syntax.rb:3:in `' > # ./spec/spec_helper.rb:2:in `' > # ./spec/puppet-syntax_spec.rb:1:in `' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > No examples found. > > Finished in 0.3 seconds (files took 0.19211 seconds to load) > 0 examples, 0 failures, 5 errors occurred outside of examples > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-puppet-syntax_2.6.1-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.
Bug#952017: ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-jekyll-commonmark Version: 1.3.1-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `expect' for > # >Did you mean? exec > # ./spec/jekyll_commonmark_spec.rb:41:in `block (3 levels) in (required)>' > > Finished in 0.01494 seconds (files took 0.35144 seconds to load) > 9 examples, 9 failures > > Failed examples: > > rspec ./spec/jekyll_commonmark_spec.rb:84 # > Jekyll::Converters::Markdown::CommonMark with autolink enabled links urls > rspec ./spec/jekyll_commonmark_spec.rb:74 # > Jekyll::Converters::Markdown::CommonMark with nobreaks enabled treats > newlines as a single space > rspec ./spec/jekyll_commonmark_spec.rb:64 # > Jekyll::Converters::Markdown::CommonMark with hardbreaks enabled treats > newlines as hardbreaks > rspec ./spec/jekyll_commonmark_spec.rb:54 # > Jekyll::Converters::Markdown::CommonMark with SmartyPants enabled makes > quotes curly > rspec ./spec/jekyll_commonmark_spec.rb:44 # > Jekyll::Converters::Markdown::CommonMark with default configuration does not > link urls > rspec ./spec/jekyll_commonmark_spec.rb:26 # > Jekyll::Converters::Markdown::CommonMark with default configuration does not > treat newlines as hardbreaks > rspec ./spec/jekyll_commonmark_spec.rb:20 # > Jekyll::Converters::Markdown::CommonMark with default configuration produces > the correct script tag > rspec ./spec/jekyll_commonmark_spec.rb:32 # > Jekyll::Converters::Markdown::CommonMark with default configuration treats > double linebreaks as a new paragraph > rspec ./spec/jekyll_commonmark_spec.rb:38 # > Jekyll::Converters::Markdown::CommonMark with default configuration escapes > quotes > > Randomized with seed 25228 > > /usr/bin/ruby2.5 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.5" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-jekyll-commonmark_1.3.1-3_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.
Bug#952021: ruby-omniauth-wordpress: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
Source: ruby-omniauth-wordpress Version: 0.2.2-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `double' for > # > # ./spec/omniauth/strategies/wordpress_spec.rb:9:in `block (2 levels) in > ' > > Finished in 0.00311 seconds (files took 0.15456 seconds to load) > 8 examples, 8 failures > > Failed examples: > > rspec ./spec/omniauth/strategies/wordpress_spec.rb:26 # > OmniAuth::Strategies::Wordpress#client should be initialized with symbolized > client_options > rspec ./spec/omniauth/strategies/wordpress_spec.rb:31 # > OmniAuth::Strategies::Wordpress#client has correct Wordpress site > rspec ./spec/omniauth/strategies/wordpress_spec.rb:35 # > OmniAuth::Strategies::Wordpress#client has correct authorize url > rspec ./spec/omniauth/strategies/wordpress_spec.rb:39 # > OmniAuth::Strategies::Wordpress#client has correct token url > rspec ./spec/omniauth/strategies/wordpress_spec.rb:45 # > OmniAuth::Strategies::Wordpress#authorize_params should include any authorize > params passed in the :authorize_params option > rspec ./spec/omniauth/strategies/wordpress_spec.rb:51 # > OmniAuth::Strategies::Wordpress#authorize_params should include top-level > options that are marked as :authorize_options > rspec ./spec/omniauth/strategies/wordpress_spec.rb:59 # > OmniAuth::Strategies::Wordpress#token_params should include any authorize > params passed in the :authorize_params option > rspec ./spec/omniauth/strategies/wordpress_spec.rb:65 # > OmniAuth::Strategies::Wordpress#token_params should include top-level options > that are marked as :authorize_options > > /usr/bin/ruby2.5 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.5" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-omniauth-wordpress_0.2.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.
Bug#952006: drf-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7" --system=custom "--test-args=PYTHONPATH='.:tests_app' {interpreter} /usr/bin/django-a
Source: drf-extensions
Version: 0.4.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="PYTHONPATH='.:tests_app'
> {interpreter} /usr/bin/django-admin test --settings=settings tests_app"
> I: pybuild base:217: PYTHONPATH='.:tests_app' python3.8 /usr/bin/django-admin
> test --settings=settings tests_app
> nosetests tests_app --processes=4 --process-timeout=100 --nocapture
> --verbosity=1
> Creating test database for alias 'default'...
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84,
> in _execute
> return self.cursor.execute(sql, params)
> File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py",
> line 383, in execute
> return Database.Cursor.execute(self, query, params)
> sqlite3.IntegrityError: UNIQUE constraint failed:
> auth_permission.content_type_id, auth_permission.codename
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
> File "/usr/bin/django-admin", line 5, in
> management.execute_from_command_line()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 381, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 375, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 23, in run_from_argv
> super().run_from_argv(argv)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 323, in run_from_argv
> self.execute(*args, **cmd_options)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 364, in execute
> output = self.handle(*args, **options)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 53, in handle
> failures = test_runner.run_tests(test_labels)
> File "/usr/lib/python3/dist-packages/django_nose/runner.py", line 308, in
> run_tests
> result = self.run_suite(nose_argv)
> File "/usr/lib/python3/dist-packages/django_nose/runner.py", line 244, in
> run_suite
> nose.core.TestProgram(argv=nose_argv, exit=False,
> File "/usr/lib/python3/dist-packages/nose/core.py", line 118, in __init__
> unittest.TestProgram.__init__(
> File "/usr/lib/python3.8/unittest/main.py", line 101, in __init__
> self.runTests()
> File "/usr/lib/python3/dist-packages/nose/core.py", line 207, in runTests
> result = self.testRunner.run(self.test)
> File "/usr/lib/python3/dist-packages/nose/plugins/multiprocess.py", line
> 356, in run
> wrapper = self.config.plugins.prepareTest(test)
> File "/usr/lib/python3/dist-packages/nose/plugins/manager.py", line 99, in
> __call__
> return self.call(*arg, **kw)
> File "/usr/lib/python3/dist-packages/nose/plugins/manager.py", line 167, in
> simple
> result = meth(*arg, **kw)
> File "/usr/lib/python3/dist-packages/django_nose/plugin.py", line 82, in
> prepareTest
> self.old_names = self.runner.setup_databases()
> File "/usr/lib/python3/dist-packages/django_nose/runner.py", line 495, in
> setup_databases
> return super(NoseTestSuiteRunner, self).setup_databases()
> File "/usr/lib/python3/dist-packages/django/test/runner.py", line 552, in
> setup_databases
> return _setup_databases(
> File "/usr/lib/python3/dist-packages/django/test/utils.py", line 170, in
> setup_databases
> connection.creation.create_test_db(
> File "/usr/lib/python3/dist-packages/django/db/backends/base/creation.py",
> line 67, in create_test_db
> call_command(
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 148, in call_command
> return command.execute(*args, **defaults)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 364, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 83, in wrapped
> res = handle_func(*args, **kwargs)
> File
> "/usr/lib/python3/dist-packages/django/co
Bug#952011: bitstruct: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} setup.py test" returned exit code 13
Source: bitstruct
Version: 3.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
> I: pybuild base:217: python3.8 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> writing bitstruct.egg-info/PKG-INFO
> writing dependency_links to bitstruct.egg-info/dependency_links.txt
> writing top-level names to bitstruct.egg-info/top_level.txt
> reading manifest file 'bitstruct.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'bitstruct.egg-info/SOURCES.txt'
> running build_ext
> test_bad_float_size (tests.test_bitstruct.BitStructTest)
> Test of bad float size. ... ok
> test_bad_format (tests.test_bitstruct.BitStructTest)
> Test of bad format. ... ok
> test_byte_order (tests.test_bitstruct.BitStructTest)
> Test pack/unpack with byte order information in the format string. ... ok
> test_byte_order_format (tests.test_bitstruct.BitStructTest)
> Test of a format with only byte order informationx. ... ok
> test_byteswap (tests.test_bitstruct.BitStructTest)
> Byte swap. ... ok
> test_calcsize (tests.test_bitstruct.BitStructTest)
> Calculate size. ... ok
> test_compile (tests.test_bitstruct.BitStructTest) ... ok
> test_empty_format (tests.test_bitstruct.BitStructTest)
> Test of empty format type. ... ok
> test_endianness (tests.test_bitstruct.BitStructTest)
> Test pack/unpack with endianness information in the format string. ... ok
> test_pack (tests.test_bitstruct.BitStructTest)
> Pack values. ... FAIL
> test_pack_unpack (tests.test_bitstruct.BitStructTest)
> Pack and unpack values. ... ok
> test_performance_integers (tests.test_bitstruct.BitStructTest)
> Test pack/unpack performance with integers. ... ok
> test_performance_mixed_types (tests.test_bitstruct.BitStructTest)
> Test pack/unpack performance with mixed types. ... ok
> test_signed_integer (tests.test_bitstruct.BitStructTest)
> Pack and unpack signed integer values. ... ok
> test_unpack (tests.test_bitstruct.BitStructTest)
> Unpack values. ... ok
> test_unsigned_integer (tests.test_bitstruct.BitStructTest)
> Pack and unpack unsigned integer values. ... ok
>
> ==
> FAIL: test_pack (tests.test_bitstruct.BitStructTest)
> Pack values.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_bitstruct.py", line 94, in test_pack
> pack('r5', 1.0)
> TypeError: cannot convert 'float' object to bytearray
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/<>/tests/test_bitstruct.py", line 97, in test_pack
> self.assertEqual(
> AssertionError: "cannot convert 'float' object to bytearray" != "'float'
> object is not iterable"
> - cannot convert 'float' object to bytearray
> + 'float' object is not iterable
>
>
> --
> Ran 16 tests in 3.015s
>
> FAILED (failures=1)
> Test failed:
>
> pack time: 0.4917159940014244 s (9.834319880028488e-06 s/pack)
> pack time compiled: 0.19851595500222174 s (3.970319100044435e-06 s/pack)
> unpack time: 0.4506532360028359 s (9.013064720056718e-06 s/unpack)
> unpack time compiled: 0.16778694900131086 s (3.3557389800262172e-06 s/unpack)
>
> pack time: 0.5904734639989329 s (1.1809469279978658e-05 s/pack)
> pack time compiled: 0.2874713269993663 s (5.7494265399873255e-06 s/pack)
> unpack time: 0.5556427190022077 s (1.1112854380044155e-05 s/unpack)
> unpack time compiled: 0.2673477409989573 s (5.346954819979146e-06 s/unpack)
> error: Test failed: failures=1>
> E: pybuild pybuild:341: test: plugin custom failed with: exit code=1:
> python3.8 setup.py test
> dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7"
> --system=custom "--test-args={interpreter} setup.py test" returned exit code
> 13
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/bitstruct_3.7.0-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.
Bug#952010: flask-oauthlib: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7" returned exit code 13
Source: flask-oauthlib Version: 0.9.5-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py config > running config > I: pybuild base:217: python3.7 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/__init__.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/client.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/utils.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib > creating > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/oauth1.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/__init__.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/oauth2.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider > creating > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib > copying flask_oauthlib/contrib/cache.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib > copying flask_oauthlib/contrib/apps.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib > copying flask_oauthlib/contrib/__init__.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib > copying flask_oauthlib/contrib/oauth2.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib > creating > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/application.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/__init__.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/descriptor.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/exceptions.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/signals.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > copying flask_oauthlib/contrib/client/structure.py -> > /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client > running egg_info > creating Flask_OAuthlib.egg-info > writing Flask_OAuthlib.egg-info/PKG-INFO > writing dependency_links to Flask_OAuthlib.egg-info/dependency_links.txt > writing requirements to Flask_OAuthlib.egg-info/requires.txt > writing top-level names to Flask_OAuthlib.egg-info/top_level.txt > writing manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt' > reading manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt' > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/__init__.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/client.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib > copying flask_oauthlib/utils.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib > creating > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/oauth1.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/__init__.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib/provider > copying flask_oauthlib/provider/oauth2.py -> > /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib/provider > creating > /<>/.pybuild/cpython3_3.7_flask-
Bug#952008: numpy: FTBFS: ./_configtest.c:6: undefined reference to `exp'
Source: numpy Version: 1:1.17.4-5 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: _configtest.o: in function `main': > ./_configtest.c:6: undefined reference to `exp' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/numpy_1.17.4-5_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.
Bug#952001: ndcube: FTBFS: NameError: name 'intersphinx_mapping' is not defined
Source: ndcube
Version: 1.1.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.8 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> copying ndcube/ndcube.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> copying ndcube/__init__.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> copying ndcube/ndcube_sequence.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> copying ndcube/version.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> copying ndcube/_sunpy_init.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube
> creating /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils
> copying ndcube/utils/wcs.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils
> copying ndcube/utils/__init__.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils
> copying ndcube/utils/sequence.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils
> copying ndcube/utils/cube.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils
> creating /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcubesequence.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_sequence_plotting.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/helpers.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_plotting.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_utils_cube.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/setup_package.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcube.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_utils_wcs.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> copying ndcube/tests/test_utils_sequence.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> creating /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/mixins
> copying ndcube/mixins/__init__.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/mixins
> copying ndcube/mixins/plotting.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/mixins
> copying ndcube/mixins/sequence_plotting.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/mixins
> copying ndcube/mixins/ndslicing.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/mixins
> creating
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils/tests
> copying ndcube/utils/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/utils/tests
> creating /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/data
> copying ndcube/data/README.rst ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/data
> copying ndcube/tests/coveragerc ->
> /<>/.pybuild/cpython3_3.8_ndcube/build/ndcube/tests
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161:
> AstropyDeprecationWarning: The package argument to generate_version_py has
> been deprecated and will be removed in future. Specify the package name in
> setup.cfg instead
> warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166:
> AstropyDeprecationWarning: The version argument to generate_version_py has
> been deprecated and will be removed in future. Specify the version number in
> setup.cfg instead
> warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:171:
> AstropyDeprecationWarning: The release argument to generate_version_py has
> been deprecated and will be removed in future. We now use the presence of the
> "dev" string in the version to determine whether this is a release
> warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:186:
> AstropyDeprecationWarning: Specifying the package name using the
> "package_name" option in setup.cfg is deprecated - use the "name" option
> i
Bug#952007: veyon: FTBFS: ld: final link failed: bad value
Source: veyon Version: 4.3.1+repack1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): > relocation R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be > used when making a shared object; recompile with -fPIC > /usr/bin/ld: final link failed: bad value > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/veyon_4.3.1+repack1-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.
Bug#952012: colobot: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'
Source: colobot Version: 0.1.12-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_cf8d5.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/colobot_0.1.12-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.
Bug#952014: freedink: FTBFS: input.cpp:94:15: error: ‘SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH’ was not declared in this scope
Source: freedink Version: 109.6-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -DHAVE_CONFIG_H -I. -I.. -DBUILD_DATA_DIR=\"/usr/share/games\" > -I../gnulib/lib -I../gnulib/lib -DLOCALEDIR=\"/usr/share/locale\" -I../intl > -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wno-write-strings -Wall > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -D_REENTRANT -I/usr/include/SDL2 > -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -c -o paths.o > paths.cpp > input.cpp: In function ‘void input_init()’: > input.cpp:94:15: error: ‘SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH’ was not > declared in this scope >94 | SDL_SetHint(SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH, "0"); > | ^ > make[3]: *** [Makefile:2101: input.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/freedink_109.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.
Bug#952000: qtbase-opensource-src-gles: FTBFS: > ./config.tests/libdl/main.cpp:7: undefined reference to `dlopen'
Source: qtbase-opensource-src-gles Version: 5.12.5+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -o "../bin/qmake" main.o meta.o option.o project.o property.o ioutils.o > proitems.o qmakebuiltins.o qmakeevaluator.o qmakeglobals.o qmakeparser.o > qmakevfs.o pbuilder_pbx.o makefile.o makefiledeps.o metamakefile.o > projectgenerator.o unixmake2.o unixmake.o mingw_make.o msbuild_objectmodel.o > msvc_nmake.o msvc_objectmodel.o msvc_vcproj.o msvc_vcxproj.o winmakefile.o > xmloutput.o qutfcodec.o qendian.o qglobal.o qlogging.o qmalloc.o qnumeric.o > qoperatingsystemversion.o qrandom.o qabstractfileengine.o qbuffer.o > qdatastream.o qdebug.o qdir.o qdiriterator.o qfile.o qfiledevice.o > qfileinfo.o qfilesystemengine.o qfilesystementry.o qfsfileengine.o > qfsfileengine_iterator.o qiodevice.o qsettings.o qtemporaryfile.o > qtextstream.o qjsonarray.o qjson.o qjsondocument.o qjsonobject.o > qjsonparser.o qjsonvalue.o qmetatype.o qsystemerror.o qvariant.o quuid.o > qarraydata.o qbitarray.o qbytearray.o qbytearraymatcher.o > qcryptographichash.o qdatetime.o qhash.o qlinkedlist.o qlist.o qlocale.o > qlocale_tools.o qmap.o qregexp.o qringbuffer.o qstringbuilder.o > qstring_compat.o qstring.o qstringlist.o qversionnumber.o qvsnprintf.o > qxmlstream.o qxmlutils.o qcore_unix.o qfilesystemengine_unix.o > qfilesystemiterator_unix.o qfsfileengine_unix.o qlocale_unix.o > qlibraryinfo.o -Wl,-z,relro -Wl,--as-needed -Wl,--gc-sections > make[2]: Leaving directory '/<>/qmake' > Info: creating cache file /<>/.qmake.cache > Command line: -confirm-license -prefix /usr -bindir /usr/lib/qt5/bin -libdir > /usr/lib/x86_64-linux-gnu -docdir /usr/share/qt5/doc -headerdir > /usr/include/x86_64-linux-gnu/qt5 -datadir /usr/share/qt5 -archdatadir > /usr/lib/x86_64-linux-gnu/qt5 -plugindir > /usr/lib/x86_64-linux-gnu/qt5/plugins -importdir > /usr/lib/x86_64-linux-gnu/qt5/imports -translationdir > /usr/share/qt5/translations -hostdatadir /usr/lib/x86_64-linux-gnu/qt5 > -sysconfdir /etc/xdg -examplesdir /usr/lib/x86_64-linux-gnu/qt5/examples > -opensource -plugin-sql-mysql -plugin-sql-odbc -plugin-sql-psql > -plugin-sql-sqlite -no-sql-sqlite2 -plugin-sql-tds -system-sqlite -platform > linux-g++ -system-harfbuzz -system-zlib -system-libpng -system-libjpeg > -system-doubleconversion -system-pcre -openssl -no-rpath -verbose > -optimized-qmake -dbus-linked -no-strip -no-separate-debug-info -qpa xcb -xcb > -glib -icu -accessibility -no-directfb -no-use-gold-linker -opengl es2 > -no-sql-ibase 'QMAKE_CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 ' 'QMAKE_CXXFLAGS=-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 ' > 'QMAKE_LFLAGS=-Wl,-z,relro -Wl,--as-needed' > Info: creating stash file /<>/.qmake.stash > > This is the Qt Open Source Edition. > > You have already accepted the terms of the Open Source license. > > Running configuration tests... > Checking for machine tuple... > + g++ -dumpmachine > > x86_64-linux-gnu > test config.qtbase.tests.machineTuple succeeded > Checking for valid makespec... > + cd /<>/config.tests/verifyspec && /<>/bin/qmake > "CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG += shared > warn_off console single_arch" 'QMAKE_CFLAGS=-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 ' 'QMAKE_CXXFLAGS=-g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 ' > 'QMAKE_LFLAGS=-Wl,-z,relro -Wl,--as-needed' > /<>/config.tests/verifyspec > > Info: creating stash file /<>/config.tests/.qmake.stash > + cd /<>/config.tests/verifyspec && MAKEFLAGS= /usr/bin/make > > make[2]: Entering directory '/<>/config.tests/verifyspec' > > g++ -c -g -O2 -fdebug-prefix-map=/<>=. > > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > > -D_FORTIFY_SOURCE=2 -O2 -w -fPIC -I. -I/<>/mkspecs/linux-g++ > > -o verifyspec.o verifyspec.cpp > > g++ -Wl,-z,relro -Wl,--as-needed -Wl,-O1 -o verifyspec verifyspec.o > > make[2]: Leaving directory '/<>/config.tests/verifyspec' > test config.qtbase.tests.verifyspec succeeded > Checking for target architecture... > + cd /<>/config.tests/arch && /<
Bug#952013: cogl: FTBFS: configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 wayland-client >= 1.0.0 gbm libdrm wayland-
Source: cogl Version: 1.22.4-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for GNU gettext in libc... yes > checking whether to use NLS... yes > checking where the gettext function comes from... libc > checking for linguas... an ar as ast be bg bs ca ca@valencia cs da de el > en_CA en_GB eo es eu fa fr fur gl he hi hr hu id it ja km kn ko lt lv ml nb > ne nl oc or pa pl pt pt_BR ro ru sk sl sr sr@latin sv ta te th tr ug uk vi > zh_CN zh_HK zh_TW > checking for COGL_DEP... no > configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 > gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 > wayland-client >= 1.0.0 gbm libdrm wayland-server >= 1.1.90 egl x11 xext > xfixes >= 3 xdamage xcomposite >= 0.4 xrandr >= 1.2) were not met > > No package 'libdrm' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables COGL_DEP_CFLAGS > and COGL_DEP_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/cogl_1.22.4-3_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.
Bug#951991: bali-phy: FTBFS: detected.hpp:52:7: error: invalid use of incomplete type ‘struct nlohmann::detail::detector
Source: bali-phy
Version: 3.4.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> c++ -Isrc/25a6634@@bali-phy@exe -Isrc -I../src -I. -I../
> -I/usr/include/eigen3 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64
> -std=c++14 -DHAVE_CONFIG_H -Wall -Wextra -Wno-sign-compare
> -Woverloaded-virtual -Wstrict-aliasing -Wno-unknown-pragmas
> -Wno-maybe-uninitialized -DNDEBUG -DNDEBUG_DP -O3 -funroll-loops -ffast-math
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ
> 'src/25a6634@@bali-phy@exe/util_ptree.cc.o' -MF
> 'src/25a6634@@bali-phy@exe/util_ptree.cc.o.d' -o
> 'src/25a6634@@bali-phy@exe/util_ptree.cc.o' -c ../src/util/ptree.cc
> In file included from /usr/include/nlohmann/detail/meta/type_traits.hpp:11,
> from
> /usr/include/nlohmann/detail/conversions/from_json.hpp:19,
> from /usr/include/nlohmann/adl_serializer.hpp:5,
> from /usr/include/nlohmann/json.hpp:51,
> from ../src/util/json.hh:3,
> from ../src/util/ptree.H:12,
> from ../src/util/ptree.cc:1:
> /usr/include/nlohmann/detail/meta/detected.hpp: In substitution of
> ‘template class Op, class ... Args> using
> is_detected_exact = std::is_same nlohmann::detail::detector ...>::type> [with Expected = void; Op = nlohmann::detail::to_json_function;
> Args = {nlohmann::basic_json<>::json_serializer,
> nlohmann::basic_json std::char_traits, std::allocator >, bool, long int, long unsigned
> int, double, std::allocator, nlohmann::adl_serializer>&, ptree}]’:
> /usr/include/nlohmann/detail/meta/type_traits.hpp:121:27: required from
> ‘constexpr const bool nlohmann::detail::has_to_json,
> ptree, void>::value’
> /usr/include/nlohmann/detail/meta/type_traits.hpp:353:27: required from
> ‘constexpr const bool
> nlohmann::detail::is_compatible_type_impl, ptree,
> void>::value’
> /usr/include/nlohmann/json.hpp:1299:55: required by substitution of
> ‘template nlohmann::detail::is_basic_json::value) &&
> nlohmann::detail::is_compatible_type, U>::value),
> int>::type > nlohmann::basic_json<>::basic_json(CompatibleType&&)
> [with CompatibleType = ptree; U = ptree; typename std::enable_if<((!
> nlohmann::detail::is_basic_json::value) &&
> nlohmann::detail::is_compatible_type, U>::value),
> int>::type = ]’
> /usr/include/c++/9/type_traits:883:12: required from ‘struct
> std::is_constructible, ptree>’
> /usr/include/nlohmann/detail/conversions/to_json.hpp:305:123: required by
> substitution of ‘template std::enable_if<(std::is_constructible CompatibleNumberIntegerType>::value && std::is_constructible T2>::value), int>::type > void
> nlohmann::detail::to_json(BasicJsonType&, const std::pair<_Tp1, _Tp2>&) [with
> BasicJsonType = nlohmann::basic_json<>; T1 =
> std::__cxx11::basic_string; T2 = ptree; typename
> std::enable_if<(std::is_constructible CompatibleNumberIntegerType>::value && std::is_constructible T2>::value), int>::type = ]’
> /usr/include/nlohmann/detail/conversions/to_json.hpp:335:24: [ skipping 12
> instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ]
> /usr/include/nlohmann/adl_serializer.hpp:43:36: required by substitution of
> ‘template static decltype
> ((nlohmann::{anonymous}::to_json(j, forward(val)), void()))
> nlohmann::adl_serializer::to_json ValueType>(BasicJsonType&, ValueType&&) [with BasicJsonType =
> nlohmann::basic_json<>; ValueType = ptree]’
> /usr/include/nlohmann/detail/meta/detected.hpp:52:7: recursively required
> by substitution of ‘template class Op,
> class ... Args> struct nlohmann::detail::detector nlohmann::detail::make_void >::type, Op, Args ...> [with Default
> = nlohmann::detail::nonesuch; Op = nlohmann::detail::to_json_function; Args =
> {nlohmann::adl_serializer, nlohmann::basic_json std::vector, std::__cxx11::basic_string,
> std::allocator >, bool, long int, long unsigned int, double,
> std::allocator, nlohmann::adl_serializer>&, ptree}]’
> /usr/include/nlohmann/detail/meta/detected.hpp:52:7: required by
> substitution of ‘template class Op, class
> ... Args> using is_detected_exact = std::is_same nlohmann::detail::detector ...>::type> [with Expected = void; Op = nlohmann::detail::to_json_function;
> Args = {nlohmann::basic_json<>::json_serializer,
> nlohmann::basic_json std::ch
Bug#951996: gitlint: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: gitlint Version: 0.12.0-0.1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYBUILD_SYSTEM=custom dh_auto_test > I: pybuild base:217: python3.8 -m coverage run > --omit='/usr/*,/<>/gitlint/tests/*,/<>/gitlint/qa/*' > -m unittest discover -v -s /<>/gitlint/tests > test_contrib_rule_instantiated (contrib.test_contrib_rules.ContribRuleTests) > Tests that all contrib rules can be instantiated without errors. ... ok > test_contrib_rule_naming_conventions > (contrib.test_contrib_rules.ContribRuleTests) > Tests that contrib rules follow certain naming conventions. ... ok > test_contrib_rule_uniqueness (contrib.test_contrib_rules.ContribRuleTests) > Tests that all contrib rules have unique identifiers. ... ok > test_contrib_tests_exist (contrib.test_contrib_rules.ContribRuleTests) > Tests that every contrib rule file has an associated test file. ... ok > test_conventional_commits > (contrib.test_conventional_commit.ContribConventionalCommitTests) ... ok > test_enable (contrib.test_conventional_commit.ContribConventionalCommitTests) > ... ok > test_enable (contrib.test_signedoff_by.ContribSignedOffByTests) ... ok > test_signedoff_by (contrib.test_signedoff_by.ContribSignedOffByTests) ... ok > test_body_changed_file_mention (rules.test_body_rules.BodyRuleTests) ... ok > test_body_first_line_empty (rules.test_body_rules.BodyRuleTests) ... ok > test_body_min_length (rules.test_body_rules.BodyRuleTests) ... ok > test_body_missing (rules.test_body_rules.BodyRuleTests) ... ok > test_body_missing_merge_commit (rules.test_body_rules.BodyRuleTests) ... ok > test_hard_tabs (rules.test_body_rules.BodyRuleTests) ... ok > test_max_line_length (rules.test_body_rules.BodyRuleTests) ... ok > test_trailing_whitespace (rules.test_body_rules.BodyRuleTests) ... ok > test_ignore_by_body (rules.test_configuration_rules.ConfigurationRuleTests) > ... ok > test_ignore_by_title (rules.test_configuration_rules.ConfigurationRuleTests) > ... ok > test_author_valid_email_rule (rules.test_meta_rules.MetaRuleTests) ... ok > test_author_valid_email_rule_custom_regex > (rules.test_meta_rules.MetaRuleTests) ... ok > test_hard_tabs (rules.test_title_rules.TitleRuleTests) ... ok > test_leading_whitespace (rules.test_title_rules.TitleRuleTests) ... ok > test_max_line_length (rules.test_title_rules.TitleRuleTests) ... ok > test_regex_matches (rules.test_title_rules.TitleRuleTests) ... ok > test_title_must_not_contain_word (rules.test_title_rules.TitleRuleTests) ... > ok > test_trailing_punctuation (rules.test_title_rules.TitleRuleTests) ... ok > test_trailing_whitespace (rules.test_title_rules.TitleRuleTests) ... ok > test_assert_valid_rule_class (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative (rules.test_user_rules.UserRuleTests) > ... ok > test_assert_valid_rule_class_negative_id > (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative_name > (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative_option_spec > (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative_parent > (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative_target > (rules.test_user_rules.UserRuleTests) ... ok > test_assert_valid_rule_class_negative_validate > (rules.test_user_rules.UserRuleTests) ... ok > test_empty_user_classes (rules.test_user_rules.UserRuleTests) ... ok > test_extra_path_specified_by_file (rules.test_user_rules.UserRuleTests) ... ok > test_failed_module_import (rules.test_user_rules.UserRuleTests) ... ok > test_find_rule_classes (rules.test_user_rules.UserRuleTests) ... ok > test_find_rule_classes_nonexisting_path (rules.test_user_rules.UserRuleTests) > ... ok > test_rules_from_init_file (rules.test_user_rules.UserRuleTests) ... ok > test_config_file (test_cli.CLITests) > Test for --config option ... ok > test_config_file_negative (test_cli.CLITests) > Negative test for --config option ... ok > test_contrib (test_cli.CLITests) ... ok > test_contrib_negative (test_cli.CLITests) ... ok > test_debug (test_cli.CLITests) > Test for --debug option ... FAIL > test_extra_path (test_cli.CLITests) > Test for --extra-path flag ... ok > test_generate_config (test_cli.CLITests) > Test for the generate-config subcommand ... ok > test_generate_config_negative (test_cli.CLITests) > Negative test for the generate-config subcommand ... ok > test_git_error (test_cli.CLITests) > Tests that the cli handles git errors properly ...
Bug#951998: xfe: FTBFS: configure: error: Cannot find x11-xcb
Source: xfe Version: 1.43.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for startup notification... yes > checking for xcb... yes > checking for xcb_aux... yes > checking for xcb_event... yes > checking for x11_xcb... no > configure: error: Cannot find x11-xcb > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/xfe_1.43.1-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.
Bug#952009: c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
Source: c-icap-modules Version: 1:0.5.3-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE > -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall > -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module > -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath > /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo > libtool: link: gcc -shared -fPIC -DPIC .libs/clamd_mod_la-clamd_mod.o-g > -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro > -Wl,-z -Wl,now -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so > In file included from /usr/include/clamav.h:69, > from clamav_mod.c:27: > clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant > 108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE]; > | ^~ > clamav_mod.c: In function ‘clamav_set_versions’: > clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’ > 645 | CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0'; > | ^~ > make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-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.
Bug#951994: ayatana-indicator-messages: FTBFS: im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror]
Source: ayatana-indicator-messages Version: 0.6.0-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/accountsservice-1.0 -I../common -Wall > -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror > -Wno-error=deprecated-declarations > -DG_LOG_DOMAIN=\"Ayatana-Indicator-Messages\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o > ayatana_indicator_messages_service-im-accounts-service.o `test -f > 'im-accounts-service.c' || echo './'`im-accounts-service.c > im-accounts-service.c: In function ‘im_accounts_service_class_init’: > im-accounts-service.c:54:2: warning: ‘g_type_class_add_private’ is deprecated > [-Wdeprecated-declarations] >54 | g_type_class_add_private (klass, sizeof (ImAccountsServicePrivate)); > | ^~~~ > In file included from /usr/include/glib-2.0/gobject/gobject.h:24, > from /usr/include/glib-2.0/gobject/gbinding.h:29, > from /usr/include/glib-2.0/glib-object.h:23, > from > /usr/include/accountsservice-1.0/act/act-user-enum-types.h:7, > from /usr/include/accountsservice-1.0/act/act.h:24, > from im-accounts-service.c:24: > /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here > 1308 | void g_type_class_add_private (gpointer > g_class, > | ^~~~ > im-accounts-service.c: In function ‘im_accounts_service_init’: > im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror] >63 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(self); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_dispose’: > im-accounts-service.c:81:13: error: G_ADD_PRIVATE [-Werror] >81 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(object); > | ^~~ > im-accounts-service.c: In function ‘user_changed’: > im-accounts-service.c:107:13: error: G_ADD_PRIVATE [-Werror] > 107 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘security_privacy_ready’: > im-accounts-service.c:138:13: error: G_ADD_PRIVATE [-Werror] > 138 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘on_user_manager_loaded’: > im-accounts-service.c:149:13: error: G_ADD_PRIVATE [-Werror] > 149 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_set_draws_attention’: > im-accounts-service.c:183:13: error: G_ADD_PRIVATE [-Werror] > 183 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_get_show_on_greeter’: > im-accounts-service.c:209:13: error: G_ADD_PRIVATE [-Werror] > 209 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); > | ^~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/accountsservice-1.0 -I../common -Wall > -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror > -Wno-error=deprecated-declarations > -DG_LOG_DOMAIN=\"Ayatana-Indicator-Messages\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o ayatana_indicator_messages_service-im-menu.o > `test -f 'im-menu.c' || echo './'`im-menu.c > cc1: all warnings being treated as errors > make[3]: *** [Makefile:621: > ayatana_indicator_messages_service-im-accounts-service.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/ayatana-indicator-messages_0.6.0-3_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.
Bug#951988: libplacebo: FTBFS: (.text+0x8ee): undefined reference to `spvContextCreate'
Source: libplacebo Version: 1.7.0-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libSPIRV.a(SpvTools.cpp.o): > in function `glslang::SpirvToolsValidate(glslang::TIntermediate const&, > std::vector >&, > spv::SpvBuildLogger*, bool)': > (.text+0x8ee): undefined reference to `spvContextCreate' > /usr/bin/ld: (.text+0x918): undefined reference to `spvValidatorOptionsCreate' > /usr/bin/ld: (.text+0x92b): undefined reference to > `spvValidatorOptionsSetRelaxBlockLayout' > /usr/bin/ld: (.text+0x936): undefined reference to > `spvValidatorOptionsSetBeforeHlslLegalization' > /usr/bin/ld: (.text+0x94b): undefined reference to `spvValidateWithOptions' > /usr/bin/ld: (.text+0xafc): undefined reference to > `spvValidatorOptionsDestroy' > /usr/bin/ld: (.text+0xb06): undefined reference to `spvDiagnosticDestroy' > /usr/bin/ld: (.text+0xb0e): undefined reference to `spvContextDestroy' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/libplacebo_1.7.0-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.
Bug#952004: jhbuild: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: jhbuild Version: 3.35.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > make[3]: Nothing to be done for 'check-am'. > make[3]: Leaving directory '/<>' > python3 -bb -m unittest discover -v -t . -s ./tests > test_build (tests.test_main.AutotoolsModTypeTestCase) > Building a autotools module ... ok > test_build_check (tests.test_main.AutotoolsModTypeTestCase) > Building a autotools module, with checks ... ok > test_build_check_error (tests.test_main.AutotoolsModTypeTestCase) > Building a autotools module, with an error in make check ... ok > test_build_clean_and_check (tests.test_main.AutotoolsModTypeTestCase) > Building a autotools module, with cleaning and checks ... ok > test_build_no_network (tests.test_main.AutotoolsModTypeTestCase) > Building a autotools module, without network ... ok > test_update (tests.test_main.AutotoolsModTypeTestCase) > Updating a autotools module ... ok > test_policy_all (tests.test_main.BuildPolicyTestCase) > Building an uptodate module with build policy set to "all" ... ok > test_policy_all_with_no_network (tests.test_main.BuildPolicyTestCase) > Building an uptodate module with "all" policy, without network ... ok > test_policy_updated (tests.test_main.BuildPolicyTestCase) > Building an uptodate module with build policy set to "updated" ... ok > test_policy_updated_with_no_network (tests.test_main.BuildPolicyTestCase) > Building an uptodate module with "updated" policy, without network ... ok > test_to_sxml (tests.test_main.CMakeModuleTest) ... ok > test_pprint_output (tests.test_main.CmdTestCase) ... ok > test_autotools (tests.test_main.EndToEndTest) ... ok > test_autotools_with_libtool (tests.test_main.EndToEndTest) ... ok > test_distutils (tests.test_main.EndToEndTest) ... ERROR > test_dependency_chain_after (tests.test_main.ModuleOrderingTestCase) > A dividing chain of dependencies with an module ... ok > test_dependency_chain_bi (tests.test_main.ModuleOrderingTestCase) > A dividing chain of dependencies ... ok > test_dependency_chain_missing_after (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a missing module ... ok > test_dependency_chain_missing_dependencies > (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a missing module ... ok > test_dependency_chain_missing_suggests > (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a missing module ... ok > test_dependency_chain_recursive_after (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a recursively defined module ... ok > test_dependency_chain_recursive_after_dependencies > (tests.test_main.ModuleOrderingTestCase) > A chain dependency with an module depending on an inversed relation > ... ok > test_dependency_chain_straight (tests.test_main.ModuleOrderingTestCase) > A straight chain of dependencies ... ok > test_dependency_chain_straight_skip (tests.test_main.ModuleOrderingTestCase) > A straight chain of dependencies, with a module to skip ... ok > test_dependency_chain_suggests (tests.test_main.ModuleOrderingTestCase) > A dividing chain of dependencies with an module ... ok > test_dependency_cycle (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a cycle ... ok > test_dependency_cycle_after (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a cycle caused by an module ... ok > test_dependency_cycle_suggests (tests.test_main.ModuleOrderingTestCase) > A chain of dependencies with a cycle caused by an module ... ok > test_standalone_one (tests.test_main.ModuleOrderingTestCase) > A standalone module ... ok > test_standalone_two (tests.test_main.ModuleOrderingTestCase) > Two standalone modules ... ok > test_sys_deps (tests.test_main.ModuleOrderingTestCase) > deps ommitted because satisfied by system dependencies ... ok > test_dtd (tests.test_main.ModulesetXMLTest) ... ok > test_relaxng (tests.test_main.ModulesetXMLTest) ... ok > test_build (tests.test_main.TwoModulesTestCase) > Building two autotools module ... ok > test_build_failure_dependent_modules (tests.test_main.TwoModulesTestCase) > Building two dependent autotools modules, with failure in first ... ok > test_build_failure_dependent_modules_nopoison > (tests.test_main.TwoModulesTestCase) > Building two dependent autotools modules, with failure, but nopoison ... ok > test_build_failure_independent_modules (tests.test_main.TwoModulesTestCase) > Building two independent autotools modules, with failure in first ...
Bug#951992: deepin-screen-recorder: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209
Source: deepin-screen-recorder Version: 5.0.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu -o deepin-screen-recorder main.o > main_window.o record_process.o settings.o utils.o record_button.o > record_option_panel.o countdown_tooltip.o constant.o event_monitor.o > start_tooltip.o button_feedback.o process_tree.o qrc_deepin-screen-recorder.o > moc_main_window.o moc_record_process.o moc_settings.o moc_record_button.o > moc_record_option_panel.o moc_countdown_tooltip.o moc_event_monitor.o > moc_start_tooltip.o moc_button_feedback.o moc_process_tree.o -lX11 -lXext > -lXtst -Llibprocps -lprocps -lxcb-util -lxcb -ldtkwidget -ldtkwm -ldtkcore > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so > /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so > /usr/lib/x86_64-linux-gnu/libQt5Gui.so > /usr/lib/x86_64-linux-gnu/libQt5Network.so > /usr/lib/x86_64-linux-gnu/libQt5DBus.so > /usr/lib/x86_64-linux-gnu/libQt5Core.so /usr/lib/x86_64-linux-gnu/libGL.so > -lpthread > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): > undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209' > /usr/bin/ld: /lib/x86_64-linux-gnu/libsystemd.so.0: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/deepin-screen-recorder_5.0.0-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.
Bug#951999: mpqc: FTBFS: messmpi.cc:203:21: error: call to 'MPI_Errhandler_set' declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use MPI_Comm_set_errhandler instead.
Source: mpqc Version: 2.3.1-19 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/sh ../../../../libtool --mode=compile mpic++ -DHAVE_CONFIG_H > -D_REENTRANT -I../../../../src/lib -I/<>/include > -I/<>/src/lib -I/usr/include/mpi -O2 -c messmpi.cc -o messmpi.lo > mpic++ -DHAVE_CONFIG_H -D_REENTRANT -I../../../../src/lib > -I/<>/include -I/<>/src/lib -I/usr/include/mpi -O2 > -c messmpi.cc -fPIC -DPIC -o .libs/messmpi.o > messmpi.cc: In member function 'void sc::MPIMessageGrp::init(MPI_Comm, int*, > char***)': > messmpi.cc:203:21: error: call to 'MPI_Errhandler_set' declared with > attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use > MPI_Comm_set_errhandler instead. > 203 | MPI_Errhandler_set(commgrp, MPI_ERRORS_ARE_FATAL); > | ~~^~~ > messmpi.cc: In constructor 'sc::MPIMessageGrp::MPIMessageGrp(const > sc::Ref&)': > messmpi.cc:132:25: error: call to 'MPI_Errhandler_set' declared with > attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use > MPI_Comm_set_errhandler instead. > 132 | MPI_Errhandler_set(commgrp, MPI_ERRORS_RETURN); > | ~~^~~~ > make[5]: *** > [/<>/src/lib/util/group/../../../../lib/GlobalRules:177: > messmpi.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/mpqc_2.3.1-19_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.
Bug#951995: sopt: FTBFS: core.h:266: undefined reference to `fmt::v6::internal::assert_fail(char const*, int, char const*)'
Source: sopt Version: 3.0.1-10 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/common_catch_main_object.dir/common_catch_main.cc.o: > in function `std::make_unsigned::type > fmt::v6::internal::to_unsigned(long)': > /usr/include/spdlog/fmt/bundled/core.h:266: undefined reference to > `fmt::v6::internal::assert_fail(char const*, int, char const*)' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/sopt_3.0.1-10_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.
Bug#952003: relion: FTBFS: src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use MPI_Comm_set_errhandler instead.
Source: relion Version: 1.4+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CXX --mode=compile mpicxx.openmpi > -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fpic -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o src/autopicker_mpi.lo src/autopicker_mpi.cpp > libtool: compile: mpicxx.openmpi -DHAVE_CONFIG_H -I. -Wdate-time > -D_FORTIFY_SOURCE=2 -fpic -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c > src/autopicker_mpi.cpp -fPIC -DPIC -o src/.libs/autopicker_mpi.o > src/mpi.cpp: In constructor ‘MpiNode::MpiNode(int&, char**)’: > src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with > attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use > MPI_Comm_set_errhandler instead. >56 | MPI_Errhandler_set(MPI_COMM_WORLD, MPI_ERRORS_RETURN); > | ~~^~~ > make[3]: *** [Makefile:1305: src/mpi.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/relion_1.4+dfsg-4_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.
Bug#951985: inputplug: FTBFS: ./inputplug.c:459: undefined reference to `XCloseDisplay'
Source: inputplug Version: 0.3~hg20150512-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: inputplug.o: in function `main': > ./inputplug.c:459: undefined reference to `XCloseDisplay' > /usr/bin/ld: ./inputplug.c:391: undefined reference to `XIQueryDevice' > /usr/bin/ld: ./inputplug.c:407: undefined reference to `XIFreeDeviceInfo' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/inputplug_0.3~hg20150512-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.
Bug#951989: gnome-calculator: FTBFS: ../lib/math-equation.vala:829.53-829.56: error: Argument 1: Cannot pass value to reference or output parameter
Source: gnome-calculator Version: 3.34.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > [7/115] cc -Igcalc/35aae3b@@gcalc-1@sha -Igcalc -I../gcalc -I. -I../ > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 > -I/usr/include/libsoup-2.4 -I/usr/include/gee-0.8 -fdiagnostics-color=always > -pipe -D_FILE_OFFSET_BITS=64 -w -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -pthread -include > /<>/obj-x86_64-linux-gnu/gcalc/config.h -MD -MQ > 'gcalc/35aae3b@@gcalc-1@sha/meson-generated_gcalc-constant.c.o' -MF > 'gcalc/35aae3b@@gcalc-1@sha/meson-generated_gcalc-constant.c.o.d' -o > 'gcalc/35aae3b@@gcalc-1@sha/meson-generated_gcalc-constant.c.o' -c > 'gcalc/35aae3b@@gcalc-1@sha/gcalc-constant.c' > [8/115] valac -C --pkg posix --pkg posix /<>/vapi/mpfr.vapi > /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg > gtksourceview-4 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' > --pkg glib-2.0 --pkg gio-2.0 --color=always --directory > lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header > lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 > ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala > ../lib/equation-parser.vala ../lib/financial.vala > ../lib/function-manager.vala ../lib/math-equation.vala > ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala > ../lib/serializer.vala ../lib/unit.vala gcalc/mpfrg.vapi > FAILED: lib/76b5a35@@calculator@sta/currency.c > lib/76b5a35@@calculator@sta/equation.c > lib/76b5a35@@calculator@sta/equation-lexer.c > lib/76b5a35@@calculator@sta/equation-parser.c > lib/76b5a35@@calculator@sta/financial.c > lib/76b5a35@@calculator@sta/function-manager.c > lib/76b5a35@@calculator@sta/math-equation.c > lib/76b5a35@@calculator@sta/math-function.c > lib/76b5a35@@calculator@sta/math-variables.c > lib/76b5a35@@calculator@sta/number.c lib/76b5a35@@calculator@sta/serializer.c > lib/76b5a35@@calculator@sta/unit.c lib/calculator.h lib/calculator.vapi > valac -C --pkg posix --pkg posix /<>/vapi/mpfr.vapi > /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg > gtksourceview-4 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' > --pkg glib-2.0 --pkg gio-2.0 --color=always --directory > lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header > lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 > ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala > ../lib/equation-parser.vala ../lib/financial.vala > ../lib/function-manager.vala ../lib/math-equation.vala > ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala > ../lib/serializer.vala ../lib/unit.vala gcalc/mpfrg.vapi > ../lib/math-equation.vala:327.21-327.51: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (this as Gtk.TextBuffer).insert (ref iter, > serializer.get_thousands_separator ().to_string (), -1); > ^^^ > ../lib/math-equation.vala:829.17-829.50: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (this as Gtk.TextBuffer).backspace (iter, true, true); > ^^ > ../lib/math-equation.vala:829.53-829.56: error: Argument 1: Cannot pass value > to reference or output parameter > (this as Gtk.TextBuffer).backspace (iter, true, true); > > ../lib/math-equation.vala:843.17-843.50: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (this as Gtk.TextBuffer).backspace (iter, true, true); > ^^ > ../lib/math-equation.vala:843.53-843.56: error: Argument 1: Cannot pass value > to reference or output parameter > (this as Gtk.TextBuffer).backspace (iter, true, true); > > ../lib/math-equation.vala:857.17-857.50: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (this as Gtk.TextBuffer).backspace (iter, true, true); > ^^ > ../lib/math-equation.vala:857.53-857.56: error: Argument 1: Cannot pass value > to reference or output parameter &
Bug#951993: astroplan: FTBFS: NameError: name 'intersphinx_mapping' is not defined
Source: astroplan
Version: 0.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.8 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/scheduling.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/__init__.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/target.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/_astropy_init.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/observer.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/constraints.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/conftest.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/version.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/exceptions.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/periodic.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/setup_package.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/utils.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> copying astroplan/moon.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan
> creating
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_moon.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_utils.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_periodic.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_constraints.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_target.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_observer.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> copying astroplan/tests/test_scheduling.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> creating
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> copying astroplan/plots/sky.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> copying astroplan/plots/__init__.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> copying astroplan/plots/mplstyles.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> copying astroplan/plots/time_dependent.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> copying astroplan/plots/finder.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots
> creating
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots/tests
> copying astroplan/plots/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots/tests
> copying astroplan/plots/tests/test_sky.py ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots/tests
> copying astroplan/tests/coveragerc ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/tests
> creating
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots/tests/baseline_images
> copying astroplan/plots/tests/baseline_images/test_image_example.png ->
> /<>/.pybuild/cpython3_3.8_astroplan/build/astroplan/plots/tests/baseline_images
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161:
> AstropyDeprecationWarning: The package argument to generate_version_py has
> been deprecated and will be removed in future. Specify the package name in
> setup.cfg instead
> warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166:
> AstropyDeprecationWarning: The version argument to generate_version_py has
> been deprecated and will be removed in future. Specify the version number in
> setup.cfg
Bug#951984: tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead."
Source: tree-puzzle
Version: 5.2-11
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now sgamma.o sml1.o
> sml2.o smlparam.o smodel1.o smodel2.o spuzzle1.o spuzzle2.o spstep.o sutil.o
> sconsensus.o streesort.o streetest.o -lsprng -lm -o puzzle
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./gamma.c && mv
> gamma.o pgamma.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./ml1.c && mv
> ml1.o pml1.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./ml2.c && mv
> ml2.o pml2.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./mlparam.c &&
> mv mlparam.o pmlparam.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./model1.c &&
> mv model1.o pmodel1.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./model2.c &&
> mv model2.o pmodel2.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c ./puzzle1.c &&
> mv puzzle1.o ppuzzle1.o
> ./puzzle1.c: In function ‘readallquarts’:
> ./puzzle1.c:294:3: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 294 | fscanf(ifp, "TREE-PUZZLE\n");
> | ^~~~
> ./puzzle1.c:295:3: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 295 | fscanf(ifp, "%s\n\n", dummyversion);
> | ^~~
> ./puzzle1.c:297:3: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 297 | fscanf(ifp, "species: %d\n", );
> | ^~~
> ./puzzle1.c:298:3: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 298 | fscanf(ifp, "quartets: %lu\n", );
> | ^~~~
> ./puzzle1.c:299:3: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 299 | fscanf(ifp, "bytes: %lu\n\n", );
> | ^~
> ./puzzle1.c:322:6: warning: ignoring return value of ‘fscanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 322 | fscanf(ifp, "%s\n", dummyname);
> | ^~
> ./puzzle1.c:335:3: warning: ignoring return value of ‘fread’, declared with
> attribute warn_unused_result [-Wunused-result]
> 335 | fread(&(quartetinfo[0]), sizeof(char), blocklen, ifp);
> | ^
> ./puzzle1.c: In function ‘setoptions’:
> ./puzzle1.c:718:8: warning: ignoring return value of ‘scanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 718 |scanf("%d", );
> |^
> ./puzzle1.c:776:8: warning: ignoring return value of ‘scanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 776 |scanf("%lf", );
> |^~
> ./puzzle1.c:795:8: warning: ignoring return value of ‘scanf’, declared with
> attribute warn_unused_result [-Wunused-result]
> 795 |scanf("%lf", );
> |^~~
> ./puzzle1.c:813:8: warning: ignoring return value of ‘scanf’, declared with
> attribute warn_unused_result [-Wunused-result]
Bug#951982: tqdm: FTBFS: ImportError: cannot import name 'PanelGroupBy' from 'pandas.core.groupby' (/usr/lib/python3/dist-packages/pandas/core/groupby/__init__.py)
Source: tqdm Version: 4.30.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # tests/ dir is not copied, so we do that, else we cant run the tests in the > build dir > cp -r /<>/tqdm/tests/ /<>/build/lib/tqdm/ > # run perf tests in a separate, non-failing, line > nosetests3 --verbose -Itests_perf.py build/lib/tqdm/ > Test command line pipes ... > Test CLI: 0it [00:00, ?it/s] > Test CLI: 123it [00:00, 463521.47it/s] > > Test CLI pipes: 0.00it [00:00, ?it/s] > Test CLI pipes: 123it [00:00, 889kit/s] > ok > Test CLI --manpath ... SKIP > Test CLI Exceptions ... ok > Test tqdm.pandas() ... /<>/build/lib/tqdm/_tqdm.py:596: > FutureWarning: The Panel class is removed from pandas. Accessing it from the > top-level namespace will also be removed in the next version > from pandas import Panel > ERROR > Test pandas.(Series|DataFrame).(rolling|expanding) ... ERROR > Test pandas.Series.progress_apply and .progress_map ... ERROR > Test pandas.DataFrame.progress_apply and .progress_applymap ... ERROR > Test pandas.DataFrame.groupby(...).progress_apply ... ERROR > Test pandas with `leave=True` ... ERROR > Test warning info in ... ERROR > ERROR > Test bar object instance as argument deprecation ... ERROR > ERROR > Test dummy monitoring thread ... ok > Test for stalled tqdm instance and monitor deletion ... ok > Test on multiple bars, one not needing miniters adjustment ... ok > Test multiprocessing.Pool ... SKIP > Test time interval format ... ok > Test number format ... ok > Test statistics and progress bar formatting ... ok > Test stripping of ANSI escape codes ... ok > Test SI unit prefixes ... ok > Test default kwargs ... > Test default kwargs ... ok > Test csv iterator ... ok > Test output to arbitrary file-like objects ... ok > Test `leave=True` always prints info about the last iteration ... ok > Test trange ... ok > Test mininterval ... ok > Test maxinterval ... ok > Test miniters ... ok > Test purely dynamic miniters (and manual updates and __del__) ... ok > Test large mininterval ... ok > Test smoothed dynamic miniters ... ok > Test smoothed dynamic miniters with mininterval ... ok > Test that importing tqdm does not create multiprocessing objects. ... ok > Test disable ... ok > Test treatment of infinite total ... ok > Test SI unit prefix ... ok > Test ascii/unicode bar ... ok > Test manual creation and updates ... ok > Test manual creation and closure and n_instances ... ok > Test exponential weighted average smoothing ... ok > Test nested progress bars ... ok > Test custom bar formatting ... ok > Test adding additional derived format arguments ... ok > Test unpause ... ok > Test positioned progress bars ... ok > Test set description ... ok > Test internal GUI properties ... ok > Test comparison functions ... ok > Test representation ... ok > Test clearing bar display ... ok > Test clearing bar display ... ok > Test refresh bar display ... ok > Test refresh bar display ... ok > Test write messages ... ok > Test advance len (numpy array shape) ... ok > Test autodisable will disable on non-TTY ... ok > Test autodisable will not disable on TTY ... ok > tests_tqdm.test_deprecation_exception ... ok > Test postfix ... ok > Test directly assigning non-str objects to postfix ... ok > Test redirection of output ... ok > Test external write mode ... ok > Test numeric `unit_scale` ... ok > Test multiprocess/thread-realted features ... ok > Test boolean cast ... ok > Test auto fallback ... > 0%| | 0/1337 [00:00 > 0%| | 0/1337 [00:00 ok > Test version string ... ok > > == > ERROR: Test tqdm.pandas() > -- > Traceback (most recent call last): > File "/<>/build/lib/tqdm/_tqdm.py", line 604, in pandas > from pandas.core.groupby.groupby import DataFrameGroupBy, \ > ImportError: cannot import name 'DataFrameGroupBy' from > 'pandas.core.groupby.groupby' > (/usr/lib/python3/dist-packages/pandas/core/groupby/groupby.py) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest > self.test(*self.arg) > File "/<>/build/lib/tqdm/tests/tests_pandas.py", line 16, in > test_pandas_setup > tqdm.pandas(file=our_file, leave=True, ascii=True,
Bug#951990: willow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: willow Version: 1.1-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_willow/build/willow > copying willow/registry.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow > copying willow/__init__.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow > copying willow/image.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow > creating /<>/.pybuild/cpython3_3.8_willow/build/willow/utils > copying willow/utils/__init__.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/utils > copying willow/utils/deprecation.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/utils > creating /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins > copying willow/plugins/__init__.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins > copying willow/plugins/opencv.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins > copying willow/plugins/pillow.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins > copying willow/plugins/wand.py -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins > running egg_info > creating Willow.egg-info > writing Willow.egg-info/PKG-INFO > writing dependency_links to Willow.egg-info/dependency_links.txt > writing top-level names to Willow.egg-info/top_level.txt > writing manifest file 'Willow.egg-info/SOURCES.txt' > reading manifest file 'Willow.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found anywhere > in distribution > warning: no previously-included files matching '*.py[co]' found anywhere in > distribution > warning: no previously-included files matching '*.swp' found anywhere in > distribution > writing manifest file 'Willow.egg-info/SOURCES.txt' > creating /<>/.pybuild/cpython3_3.8_willow/build/willow/data > creating > /<>/.pybuild/cpython3_3.8_willow/build/willow/data/cascades > copying willow/data/cascades/haarcascade_frontalface_alt2.xml -> > /<>/.pybuild/cpython3_3.8_willow/build/willow/data/cascades > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.7_willow/build/willow > copying willow/registry.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow > copying willow/__init__.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow > copying willow/image.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow > creating /<>/.pybuild/cpython3_3.7_willow/build/willow/utils > copying willow/utils/__init__.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/utils > copying willow/utils/deprecation.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/utils > creating /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins > copying willow/plugins/__init__.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins > copying willow/plugins/opencv.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins > copying willow/plugins/pillow.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins > copying willow/plugins/wand.py -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins > running egg_info > writing Willow.egg-info/PKG-INFO > writing dependency_links to Willow.egg-info/dependency_links.txt > writing top-level names to Willow.egg-info/top_level.txt > reading manifest file 'Willow.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found anywhere > in distribution > warning: no previously-included files matching '*.py[co]' found anywhere in > distribution > warning: no previously-included files matching '*.swp' found anywhere in > distribution > writing manifest file 'Willow.egg-info/SOURCES.txt' > creating /<>/.pybuild/cpython3_3.7_willow/build/willow/data > creating > /<>/.pybuild/cpython3_3.7_willow/build/willow/data/cascades > copying willow/data/cascades/haarcascade_frontalface_alt2.xml -> > /<>/.pybuild/cpython3_3.7_willow/build/willow/data/cascades > PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs/ > build/html # HTML generator > Running Sphinx v1.8.5 > Initializing Spelling Checker >
Bug#951981: xfce4-sntray-plugin: FTBFS: libxfce4panel-2.0.vapi:104.9-104.47: error: overriding method `Xfce.PanelPlugin.remote_event' is incompatible with base method `bool Xfce.PanelPluginProvider.re
Source: xfce4-sntray-plugin Version: 0.4.12-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 60%] Generating vala-panel-sntray-applet.c > [ 60%] Generating sntray-applet-budgie.c > [ 64%] Generating mate-sntray-applet.c > [ 64%] Generating xfce4-sntray-applet.c > cd /<>/obj-x86_64-linux-gnu/src/panels && /usr/bin/valac -C -b > /<>/src/panels -d > /<>/obj-x86_64-linux-gnu/src/panels --pkg=gtk+-3.0 > --pkg=budgie-1.0 --vapidir=/<>/src/panels/vapi > --vapidir=/<>/obj-x86_64-linux-gnu/src/panels --target-glib=2.44 > --gresources=/<>/.gresource.xml -g > /<>/src/panels/sntray-applet-budgie.vala > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi > /<>/src/sntray-backend.vapi > cd /<>/obj-x86_64-linux-gnu/src/panels && /usr/bin/valac -C -b > /<>/src/panels -d > /<>/obj-x86_64-linux-gnu/src/panels --pkg=gtk+-3.0 > --pkg=libpeas-1.0 --pkg=vala-panel --vapidir=/<>/src/panels/vapi > --vapidir=/<>/obj-x86_64-linux-gnu/src/panels --target-glib=2.44 > --gresources=/<>/.gresource.xml -g > /<>/src/panels/vala-panel-sntray-applet.vala > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi > /<>/src/sntray-backend.vapi > cd /<>/obj-x86_64-linux-gnu/src/panels && /usr/bin/valac -C -b > /<>/src/panels -d > /<>/obj-x86_64-linux-gnu/src/panels --pkg=gdk-3.0 --pkg=gtk+-3.0 > --pkg=libmatepanelapplet-4.0 --vapidir=/<>/vapi > --vapidir=/<>/obj-x86_64-linux-gnu/src/panels --target-glib=2.44 > --gresources=/<>/src/panels/.gresource.xml -g > /<>/src/panels/mate-sntray-applet.vala > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi > /<>/src/sntray-backend.vapi > cd /<>/obj-x86_64-linux-gnu/src/panels && /usr/bin/valac -C -b > /<>/src/panels -d > /<>/obj-x86_64-linux-gnu/src/panels --pkg=gtk+-3.0 > --pkg=libxfce4panel-2.0 --pkg=libxfconf-0 --vapidir=/<>/vapi > --vapidir=/<>/obj-x86_64-linux-gnu/src/panels --target-glib=2.44 > --gresources=/<>/src/panels/.gresource.xml -g > /<>/src/panels/xfce4-sntray-applet.vala > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi > /<>/src/sntray-backend.vapi > vala-panel.vapi:88.3-88.15: warning: Creation method of abstract class cannot > be public. > public Applet (ValaPanel.Toplevel top, GLib.Settings? s, string > uuid); > ^ > libxfce4panel-2.0.vapi:104.9-104.47: error: overriding method > `Xfce.PanelPlugin.remote_event' is incompatible with base method `bool > Xfce.PanelPluginProvider.remote_event (string, GLib.Value, uint)': too few > parameters. > public virtual signal bool remote_event (string name, GLib.Value > value); > ^^^ > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi:53.3-53.43: > warning: DBus methods are recommended to throw at least `GLib.Error' or > `GLib.DBusError, GLib.IOError' > public void register_status_notifier_item (string service, > GLib.BusName sender); > ^ > Compilation failed: 1 error(s), 1 warning(s) > /<>/src/panels/vala-panel-sntray-applet.vala:32.9-32.93: > warning: Access to possible `null'. Perform a check or use an unsafe cast. > (this.action_group.lookup_action(AppletAction.CONFIGURE) as > SimpleAction).set_enabled(true); > > ^ > /<>/obj-x86_64-linux-gnu/src/vala-panel-sntray.vapi:53.3-53.43: > warning: DBus methods are recommended to throw at least `GLib.Error'make[3]: > *** [src/panels/CMakeFiles/sntray-xfce.dir/build.make:76: > src/panels/sntray-xfce_valac.stamp] Error 1 > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > or `GLib.DBusError, GLib.IOError'make[2]: *** [CMakeFiles/Makefile2:551: > src/panels/CMakeFiles/sntray-xfce.dir/all] Error 2 > > make[2]: *** Waiting for unfinished jobs > public void register_status_notifier_item (string service, > GLib.BusName sender); > ^ > /<>/src/panels/mate-sntray-applet.vala:66.32-66.46: warning: > Gtk.ActionGroup has been deprecated since 3.10 > /<>/src/panels/mate-sntray-applet.vala:68.28-68.37: warning: > Gtk.Action has been de
Bug#951983: git-buildpackage: FTBFS: ImportError: No module named cachecontrol
Source: git-buildpackage Version: 0.9.18 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > mkdir -p build > pydoctor -v --config=.pydoctor.cfg > Traceback (most recent call last): > File "/usr/bin/pydoctor", line 10, in > from pydoctor.driver import main > File "/usr/lib/python2.7/dist-packages/pydoctor/driver.py", line 5, in > > from pydoctor import model, zopeinterface > File "/usr/lib/python2.7/dist-packages/pydoctor/model.py", line 19, in > > from pydoctor.sphinx import SphinxInventory > File "/usr/lib/python2.7/dist-packages/pydoctor/sphinx.py", line 10, in > > from cachecontrol import CacheControl > ImportError: No module named cachecontrol > make[3]: *** [Makefile:29: apidocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/git-buildpackage_0.9.18_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.
Bug#952002: nip2: FTBFS: configure: error: Package requirements (gmodule-2.0 gthread-2.0 gtk+-2.0 >= 2.4.9 libxml-2.0 vips >= 7.30) were not met
Source: nip2 Version: 8.7.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for catalogs to be installed... en_GB > checking whether yyleng is yy_size_t... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for REQUIRED_PACKAGES... no > configure: error: Package requirements (gmodule-2.0 gthread-2.0 gtk+-2.0 >= > 2.4.9 libxml-2.0 vips >= 7.30) were not met > > Package 'imagequant', required by 'vips', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables REQUIRED_PACKAGES_CFLAGS > and REQUIRED_PACKAGES_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. The full build log is available from: http://qa-logs.debian.net/2020/02/22/nip2_8.7.0-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.
Bug#951986: feedreader: FTBFS: ../src/Backend/FeedServer.vala:60.98-60.148: error: The name `COLLECTION_CREATE_NONE' does not exist in the context of `Secret.CollectionCreateFlags' (libsecret-1)
Source: feedreader Version: 2.10.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > meson builddir > The Meson build system > Version: 0.53.1 > Source dir: /<> > Build dir: /<>/builddir > Build type: native build > Project name: feedreader > Project version: 2.10.0 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-29) 9.2.1 > 20200220") > C linker for the host machine: cc GNU ld.bfd 2.34 > Vala compiler for the host machine: valac (valac 0.47.91) > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program afl-fuzz found: NO > Program gtester found: YES (/usr/bin/gtester) > Found pkg-config: /usr/bin/pkg-config (0.29) > Run-time dependency gdk-pixbuf-2.0 found: YES 2.40.0 > Run-time dependency gee-0.8 found: YES 0.20.3 > Run-time dependency glib-2.0 found: YES 2.62.4 > Run-time dependency goa-1.0 found: YES 3.34.1 > Run-time dependency gstreamer-1.0 found: YES 1.16.2 > Run-time dependency gstreamer-pbutils-1.0 found: YES 1.16.2 > Run-time dependency gtk+-3.0 found: YES 3.24.13 > Run-time dependency gumbo found: YES 0.10.1 > Run-time dependency json-glib-1.0 found: YES 1.4.4 > Library curl found: YES > Run-time dependency libnotify found: YES 0.7.8 > Run-time dependency libpeas-1.0 found: YES 1.22.0 > Run-time dependency libsecret-1 found: YES 0.19.1 > Run-time dependency libsoup-2.4 found: YES 2.68.2 > Run-time dependency libxml-2.0 found: YES 2.9.10 > Library linux found: YES > Library posix found: YES > Run-time dependency rest-0.7 found: YES 0.8.1 > Run-time dependency sqlite3 found: YES 3.31.1 > Run-time dependency webkit2gtk-4.0 found: YES 2.26.4 > Run-time dependency webkit2gtk-web-extension-4.0 found: YES 2.26.4 > Found CMake: /usr/bin/cmake (3.16.3) > Appending CXXFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Run-time dependency unity found: NO (tried pkgconfig and cmake) > Configuring @basename@ using configuration > Library webkit2gtk-web-extension-4.0 found: YES > Found pkg-config: /usr/bin/pkg-config (0.29) > Program desktop-file-validate found: NO > Program appstream-util found: NO > Library gd-1.0 found: YES > Library gtkimageview found: YES > Library htmlclean found: YES > Library rss-glib-1.0 found: YES > Library m found: YES > Message: libUnity support OFF > Message: Backend Plugin: bazqux ON > Message: Backend Plugin: decsync ON > Message: Backend Plugin: feedbin ON > Message: Backend Plugin: feedhq ON > Message: Backend Plugin: feedly ON > Message: Backend Plugin: fresh ON > Message: Backend Plugin: inoreader ON > Message: Backend Plugin: local ON > Message: Backend Plugin: oldreader ON > Message: Backend Plugin: owncloud ON > Message: Backend Plugin: ttrss ON > Message: Share Plugin: Browser ON > Message: Share Plugin: Email ON > Message: Share Plugin: Instapaper ON > Message: Share Plugin: Pocket ON > Message: Share Plugin: Telegram ON > Message: Share Plugin: Twitter ON > Message: Share Plugin: Wallabag ON > Program build-aux/meson_post_install.py found: YES > (/<>/build-aux/meson_post_install.py) > Build targets in project: 81 > > Found ninja-1.10.0 at /usr/bin/ninja > ninja -C builddir > ninja: Entering directory `builddir' > [1/316] Compiling C object > 'libraries/htmlclean/3f54707@@htmlclean@sta/htmlclean.c.o'. > [2/316] Linking static target libraries/htmlclean/libhtmlclean.a. > [3/316] Compiling Vala source ../libraries/libIvy/Extractor.vala > ../libraries/libIvy/Frame.vala ../libraries/libIvy/Printer.vala > ../libraries/libIvy/Stacktrace.vala. > [4/316] Compiling C object > 'libraries/htmlclean/3f54707@@htmlclean_main@exe/main.c.o'. > [5/316] Compiling C object > 'libraries/libgd/2e95fbe@@gd@s
Bug#951976: rbdoom3bfg: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'
Source: rbdoom3bfg Version: 1.2.0+dfsg~git20191014-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_f9626.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/rbdoom3bfg_1.2.0+dfsg~git20191014-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.
Bug#951973: auctex: FTBFS: configure: error: Cannot find the texmf directory!
Source: auctex Version: 11.91-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > "" > checking for TDS-compliant directory... ./configure: line 3413: kpsepath: > command not found > no > checking for TeX directory hierarchy... no > checking for TeX input directory... no > configure: error: Cannot find the texmf directory! > Please use --with-texmf-dir=dir to specify where the preview tex files go > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/auctex_11.91-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.
Bug#951971: gxneur: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Source: gxneur
Version: 0.20.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..
> -DPACKAGE_PIXMAPS_DIR=\""/usr/share/gxneur/pixmaps"\"
> -DLOCALEDIR=\""/usr/share/locale"\"
> -DPACKAGE_UI_FILE_DIR=\""/usr/share/gxneur/ui"\"
> -DXNEUR_PLUGIN_DIR=\""/usr/lib/x86_64-linux-gnu/xneur"\" -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
> -I/usr/include/fribidi -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
> -I/usr/include/freetype2 -I/usr/include/libpng16 -Wall -Wextra -Werror -g0
> -fPIC -std=gnu99 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c -o gxneur-misc.o
> `test -f 'misc.c' || echo './'`misc.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from configuration.c:26:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
> deprecated [-Werror=deprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from callbacks.c:20:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
> deprecated [-Werror=deprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from main.c:24:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
> deprecated [-Werror=deprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:23,
> from /usr/include/glib-2.0/gio/gioenums.h:28,
> from /usr/include/glib-2.0/gio/giotypes.h:28,
> from /usr/include/glib-2.0/gio/gio.h:26,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from callbacks.c:20:
> /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
> 679 | {
> | ^
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:23,
> from /usr/include/glib-2.0/gio/gioenums.h:28,
> from /usr/include/glib-2.0/gio/giotypes.h:28,
> from /usr/include/glib-2.0/gio/gio.h:26,
> from /u
Bug#951977: flake8-polyfill: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.7" returned exit code 13
Source: flake8-polyfill Version: 1.0.2-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py config > running config > I: pybuild base:217: python3.7 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.8_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/__init__.py -> > /<>/.pybuild/cpython3_3.8_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/options.py -> > /<>/.pybuild/cpython3_3.8_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/stdin.py -> > /<>/.pybuild/cpython3_3.8_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/version.py -> > /<>/.pybuild/cpython3_3.8_flake-polyfill/build/flake8_polyfill > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.7_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/__init__.py -> > /<>/.pybuild/cpython3_3.7_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/options.py -> > /<>/.pybuild/cpython3_3.7_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/stdin.py -> > /<>/.pybuild/cpython3_3.7_flake-polyfill/build/flake8_polyfill > copying src/flake8_polyfill/version.py -> > /<>/.pybuild/cpython3_3.7_flake-polyfill/build/flake8_polyfill >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:217: cd > /<>/.pybuild/cpython3_3.8_flake-polyfill/build; python3.8 -m > pytest tests > Traceback (most recent call last): > File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main > return _run_code(code, main_globals, None, > File "/usr/lib/python3.8/runpy.py", line 86, in _run_code > exec(code, run_globals) > File "/usr/lib/python3/dist-packages/pytest.py", line 102, in > raise SystemExit(pytest.main()) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 63, > in main > config = _prepareconfig(args, plugins) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 206, > in _prepareconfig > return pluginmanager.hook.pytest_cmdline_parse( > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__ > return self._hookexec(self, self.get_hookimpls(), kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in > _hookexec > return self._inner_hookexec(hook, methods, kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in > > self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 203, in > _multicall > gen.send(outcome) > File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 94, in > pytest_cmdline_parse > config = outcome.get_result() > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in > get_result > raise ex[1].with_traceback(ex[2]) > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in > _multicall > res = hook_impl.function(*args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 739, > in pytest_cmdline_parse > self.parse(args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 947, > in parse > self._preparse(args, addopts=addopts) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 881, > in _preparse > self._initini(args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 808, > in _initini > r = determine_setup( > File "/usr/lib/python3/dist-packages/_pytest/config/findpaths.py", line > 127, in determine_setup > rootdir, inifile, inicfg = getcfg([ancestor], config=config) > File "/usr/lib/python3/dist-packages/_pytest/config/findpaths.py", line 49, > in getcfg > fail( > File "/usr/lib/python3/dist-packages/_pytest
Bug#951980: sigrok-cli: FTBFS: configure: error: Package requirements (glib-2.0 >= 2.32.0 libsigrok >= 0.5.0 libsigrokdecode >= 0.5.0) were not met
Source: sigrok-cli Version: 0.7.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking compiler flag for C99... -std=c99 > checking which C compiler warning flags to use... -Wall -Wextra > checking for special C compiler options needed for large files... no > checking for _FILE_OFFSET_BITS value needed for large files... no > checking for SIGROK_CLI... no > configure: error: Package requirements (glib-2.0 >= 2.32.0 libsigrok >= 0.5.0 > libsigrokdecode >= 0.5.0) were not met > > Package 'hidapi-hidraw', required by 'libsigrok', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables SIGROK_CLI_CFLAGS > and SIGROK_CLI_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/sigrok-cli_0.7.1-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.
Bug#951975: fava: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: fava Version: 1.11-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/application.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/cli.py -> /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/template_filters.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/serialisation.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava > copying fava/json_api.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava > creating /<>/.pybuild/cpython3_3.8_fava/build/fava/util > copying fava/util/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/util > copying fava/util/date.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/util > copying fava/util/ranking.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/util > copying fava/util/excel.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/util > creating /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/extensions.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/ingest.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/watcher.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/tree.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/fava_options.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/helpers.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/misc.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/budgets.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/query_shell.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/attributes.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/file.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/number.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/charts.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/filters.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > copying fava/core/inventory.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/core > creating /<>/.pybuild/cpython3_3.8_fava/build/fava/ext > copying fava/ext/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/ext > copying fava/ext/auto_commit.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/ext > creating /<>/.pybuild/cpython3_3.8_fava/build/fava/help > copying fava/help/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/help > creating > /<>/.pybuild/cpython3_3.8_fava/build/fava/ext/portfolio_list > copying fava/ext/portfolio_list/__init__.py -> > /<>/.pybuild/cpython3_3.8_fava/build/fava/ext/portfolio_list > running egg_info > writing fava.egg-info/PKG-INFO > writing dependency_links to fava.egg-info/dependency_links.txt > writing entry points to fava.egg-info/entry_points.txt > writing requirements to fava.egg-info/requires.txt > writing top-level names to fava.egg-info/top_level.txt > reading manifest file 'fava.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files found matching '.editorconfig' > warning: no previously-included files found matching '.gitignore' > warning: no previously-included files found matching '.travis.yml' > warning: no previously-included files found matching 'appveyor.yml' > warning: no previously-included files found matching > 'fava/translations/babel.conf' > warning: no previously-included files matching '*.po' found anywhere in > distribution > warning: no previously-included files matching '*.py[co]' found anywhere in > distribution > warning: no previously-included files matching '*.orig' found anywhere in > distribution > warning: no previously-included files matching '__pycache__' found anywhere > in distribution > warning: no previousl
Bug#951962: fife: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'
Source: fife Version: 0.4.2-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_dbfd9.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/fife_0.4.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.
Bug#951957: reprounzip: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: reprounzip Version: 1.0.10-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py config > running config > I: pybuild base:217: python3.7 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/__init__.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/parameters.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/pack_info.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/common.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/main.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/signals.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/utils.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > copying reprounzip/orderedset.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip > creating > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/default.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/__init__.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/graph.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers > creating > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/x11.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/__init__.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/misc.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/packages.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/unpackers/common > creating > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/plugins > copying reprounzip/plugins/__init__.py -> > /<>/.pybuild/cpython3_3.8_reprounzip/build/reprounzip/plugins > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/__init__.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/parameters.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/pack_info.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/common.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/main.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/signals.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/utils.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > copying reprounzip/orderedset.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip > creating > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/default.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/__init__.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers > copying reprounzip/unpackers/graph.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers > creating > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/x11.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/__init__.py -> > /<>/.pybuild/cpython3_3.7_reprounzip/build/reprounzip/unpackers/common > copying reprounzip/unpackers/common/misc.py ->
Bug#951974: spring: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'
Source: spring Version: 104.0+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_7fd61.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/spring_104.0+dfsg-4_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.
Bug#951978: vala-panel: FTBFS: ./obj-x86_64-linux-gnu/../util/misc.c:100: multiple definition of `vala_panel_reset_schema_with_children'; util/gtk/libutil-gtk.a(misc.c.o):./obj-x86_64-linux-gnu/../uti
Source: vala-panel Version: 0.4.91+dfsg1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: util/libutil.a(misc.c.o): in function > `vala_panel_reset_schema_with_children': > ./obj-x86_64-linux-gnu/../util/misc.c:100: multiple definition of > `vala_panel_reset_schema_with_children'; > util/gtk/libutil-gtk.a(misc.c.o):./obj-x86_64-linux-gnu/../util/misc.c:100: > first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/vala-panel_0.4.91+dfsg1-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.
Bug#951964: gkrellm-tz: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Source: gkrellm-tz
Version: 0.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Making gkrellm-tz version 0.8
> CC list.o
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from list.c:34:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
> deprecated [-Werror=deprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:23,
> from /usr/include/glib-2.0/gio/gioenums.h:28,
> from /usr/include/glib-2.0/gio/giotypes.h:28,
> from /usr/include/glib-2.0/gio/gio.h:26,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from list.c:34:
> /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
> 679 | {
> | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
> from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtk.h:126,
> from list.c:34:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: error: ‘GTimeVal’ is deprecated:
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>73 | GTimeVal last_popdown;
> | ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
> from /usr/include/glib-2.0/glib.h:30,
> from list.c:33:
> /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
> 551 | struct _GTimeVal
> |^
> cc1: all warnings being treated as errors
> make[2]: *** [Makefile:56: list.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/gkrellm-tz_0.8-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.
Bug#951969: social-auth-app-django: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} ./manage.py test" returned exit code 13
Source: social-auth-app-django
Version: 3.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} ./manage.py test"
> I: pybuild base:217: python3.8 ./manage.py test
> Creating test database for alias 'default'...
> ..E
> ==
> ERROR: test_html (tests.test_strategy.TestStrategy)
> --
> Traceback (most recent call last):
> File "/<>/tests/test_strategy.py", line 73, in test_html
> result = self.strategy.render_html(html='xoxo')
> File "/<>/social_django/strategy.py", line 98, in render_html
> template = loader.get_template(tpl)
> File "/usr/lib/python3/dist-packages/django/template/loader.py", line 15,
> in get_template
> return engine.get_template(template_name)
> File "/usr/lib/python3/dist-packages/django/template/backends/django.py",
> line 34, in get_template
> return Template(self.engine.get_template(template_name), self)
> File "/usr/lib/python3/dist-packages/django/template/engine.py", line 143,
> in get_template
> template, origin = self.find_template(template_name)
> File "/usr/lib/python3/dist-packages/django/template/engine.py", line 125,
> in find_template
> template = loader.get_template(name, skip=skip)
> File "/usr/lib/python3/dist-packages/django/template/loaders/cached.py",
> line 54, in get_template
> template = super().get_template(template_name, skip)
> File "/usr/lib/python3/dist-packages/django/template/loaders/base.py", line
> 18, in get_template
> for origin in self.get_template_sources(template_name):
> File "/usr/lib/python3/dist-packages/django/template/loaders/cached.py",
> line 65, in get_template_sources
> yield from loader.get_template_sources(template_name)
> File
> "/usr/lib/python3/dist-packages/django/template/loaders/filesystem.py", line
> 36, in get_template_sources
> name = safe_join(template_dir, template_name)
> File "/usr/lib/python3/dist-packages/django/utils/_os.py", line 32, in
> safe_join
> final_path = abspath(join(base, *paths))
> File "/usr/lib/python3.8/posixpath.py", line 90, in join
> genericpath._check_arg_types('join', a, *p)
> File "/usr/lib/python3.8/genericpath.py", line 152, in _check_arg_types
> raise TypeError(f'{funcname}() argument must be str, bytes, or '
> TypeError: join() argument must be str, bytes, or os.PathLike object, not
> 'NoneType'
>
> --
> Ran 55 tests in 0.642s
>
> FAILED (errors=1)
> Destroying test database for alias 'default'...
> System check identified no issues (0 silenced).
> E: pybuild pybuild:341: test: plugin custom failed with: exit code=1:
> python3.8 ./manage.py test
> dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7"
> --system=custom "--test-args={interpreter} ./manage.py test" returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/social-auth-app-django_3.1.0-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.
Bug#951979: antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory
Source: antimony Version: 0.9.3-1.1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/lib/graph && /usr/bin/c++ > -I/<>/lib/graph/inc -Wall -Wextra -g -Werror=switch -O3 > -DRELEASE -std=gnu++11 -o CMakeFiles/SbGraph.dir/src/datum.cpp.o -c > /<>/lib/graph/src/datum.cpp > In file included from /<>/lib/graph/src/datum.cpp:1: > /<>/lib/graph/inc/graph/datum.h:3:10: fatal error: Python.h: No > such file or directory > 3 | #include > | ^~ > compilation terminated. > make[3]: *** [lib/graph/CMakeFiles/SbGraph.dir/build.make:66: > lib/graph/CMakeFiles/SbGraph.dir/src/datum.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/antimony_0.9.3-1.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.
Bug#951968: vala-panel-appmenu: FTBFS: libxfce4panel-2.0.vapi:104.9-104.47: error: overriding method `Xfce.PanelPlugin.remote_event' is incompatible with base method `bool Xfce.PanelPluginProvider.rem
Source: vala-panel-appmenu Version: 0.7.3+dfsg1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > I: vala-panel-appmenu_0.7.3+dfsg1 > dh_auto_build --buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v > [1/49] glib-compile-resources ../lib/libappmenu.gresource.xml --sourcedir > ../lib/. --sourcedir ../lib --c-name lib --internal --generate --target > lib/lib.c --dependency-file lib/lib.c.d > [2/49] glib-compile-resources ../lib/libappmenu.gresource.xml --sourcedir > ../lib/. --sourcedir ../lib --c-name lib --internal --generate --target > lib/lib.h > [3/49] /usr/bin/gdbus-codegen --c-generate-autocleanup all --interface-prefix > com.canonical --c-namespace DBusMenu --header --output > lib/dbusmenu-importer/dbusmenu-interface.h > ../lib/dbusmenu-importer/com.canonical.dbusmenu.xml > [4/49] /usr/bin/gdbus-codegen --c-generate-autocleanup all --interface-prefix > com.canonical --c-namespace DBusMenu --body --output > lib/dbusmenu-importer/dbusmenu-interface.c > ../lib/dbusmenu-importer/com.canonical.dbusmenu.xml > [5/49] /usr/bin/meson --internal vcstagger ../data/appmenu.plugin.desktop.in > data/appmenu.plugin.in 0.7.1 /<>/data @VERSION@ '(.*)' > /<>/data/git describe --tags > [6/49] /usr/bin/meson --internal msgfmthelper data/appmenu-mate.desktop.in > data/org.vala-panel.appmenu.mate-panel-applet desktop /<>/po -- > --keyword=Name --keyword=Description --keyword=Comment --keyword=Help > [7/49] /usr/bin/meson --internal exe --capture > lib/dbusmenu-importer/importer-enums.h -- /usr/bin/glib-mkenums --template > /<>/obj-x86_64-linux-gnu/../lib/dbusmenu-importer/importer-enums.h.template > /<>/obj-x86_64-linux-gnu/../lib/dbusmenu-importer/definitions.h > [8/49] /usr/bin/meson --internal msgfmthelper data/appmenu.plugin.in > data/org.valapanel.appmenu.plugin desktop /<>/po -- > --keyword=Name --keyword=Description --keyword=Comment --keyword=Help > [9/49] /usr/bin/meson --internal msgfmthelper ../data/appmenu.desktop.in > data/appmenu.desktop desktop /<>/po -- --keyword=Name > --keyword=Description --keyword=Comment --keyword=Help > [10/49] /usr/bin/meson --internal exe --capture > lib/dbusmenu-importer/importer-enums.c -- /usr/bin/glib-mkenums --template > /<>/obj-x86_64-linux-gnu/../lib/dbusmenu-importer/importer-enums.c.template > /<>/obj-x86_64-linux-gnu/../lib/dbusmenu-importer/definitions.h > [11/49] cc -Ilib/dbusmenu-importer/30b68b3@@importer@sta > -Ilib/dbusmenu-importer -I../lib/dbusmenu-importer > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/gdk-pixbuf-2.0 -fdiagnostics-color=always -pipe > -D_FILE_OFFSET_BITS=64 -std=gnu11 -fstack-protector > '-DGETTEXT_PACKAGE="vala-panel-appmenu"' -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD > -MQ > 'lib/dbusmenu-importer/30b68b3@@importer@sta/meson-generated_.._importer-enums.c.o' > -MF > 'lib/dbusmenu-importer/30b68b3@@importer@sta/meson-generated_.._importer-enums.c.o.d' > -o > 'lib/dbusmenu-importer/30b68b3@@importer@sta/meson-generated_.._importer-enums.c.o' > -c lib/dbusmenu-importer/importer-enums.c > [12/49] valac -C --vapidir /<>/vapi --pkg posix --pkg > libwnck-3.0 --pkg posix --pkg libbamf3 --pkg gtk+-3.0 --pkg gio-unix-2.0 > --color=always --directory lib/76b5a35@@libappmenu@sta --basedir ../lib > --library libappmenu --header lib/libappmenu.h --vapi ../libappmenu.vapi > ../lib/launcher.vapi ../lib/dbus-menu-importer.vapi ../lib/matcher.vapi > ../lib/appmenu-abstractions.vala ../lib/appmenu-bamf.vala > ../lib/registrar.vala ../lib/menu-widget.vala ../lib/helper-desktop.vala > ../lib/helper-dbus.vala ../lib/helper-dbusmenu.vala > ../lib/helper-menumodel.vala config.vala > ../lib/helper-menumodel.vala:57.17-57.53: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (appmenu as > GLib.Menu).append_submenu(title,DBusMenuModel.get(dbusconn,gtk_unique_bus_name,app_menu_path)); > ^ > ../lib/helper-dbus.vala:131.95-131.107: warning: Posix.SIGQUIT has been > deprecated since vala-0.40. Use Posix.Signal.QUIT > ../lib/helper-dbus.vala:74.17-74.80: warning: Access to possible `null'. > Perform a check or use an unsafe cast. > (configurator.lookup
Bug#951970: gnuplot: FTBFS: configure: error: texdir is not given and there is no kpsexpand, please tell where to install
Source: gnuplot Version: 5.2.8+dfsg1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for dvips... dvips > checking for troff... troff > checking for latex2html... latex2html > checking for kpsexpand... no > checking for texhash... texhash > configure: error: texdir is not given and there is no kpsexpand, please > tell where to install > make[1]: *** [debian/rules:46: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/02/22/gnuplot_5.2.8+dfsg1-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.
Bug#951966: kio-extras: FTBFS: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to `sftp_lstat'
Source: kio-extras Version: 4:19.08.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/kio_sftp.dir/kio_sftp.cpp.o: in function > `sftpProtocol::sftpGet(QUrl const&, int&, long long, int)': > ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to > `sftp_lstat' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1522: undefined > reference to `sftp_attributes_free' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1506: undefined > reference to `sftp_attributes_free' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1519: undefined > reference to `sftp_open' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1527: undefined > reference to `sftp_read' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1541: undefined > reference to `sftp_rewind' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1499: undefined > reference to `sftp_get_error' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1562: undefined > reference to `sftp_seek64' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/kio-extras_19.08.1-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.
Bug#951967: pyro4: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: pyro4 Version: 4.76-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d ../build/sphinx/doctrees source ../build/sphinx/html > Running Sphinx v1.8.5 > making output directory... > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 30 source files that are out of date > updating environment: 30 added, 0 changed, 0 removed > reading sources... [ 3%] alternative > reading sources... [ 6%] api > reading sources... [ 10%] api/config > reading sources... [ 13%] api/constants > reading sources... [ 16%] api/core > reading sources... [ 20%] api/echoserver > reading sources... [ 23%] api/errors > reading sources... [ 26%] api/flame > reading sources... [ 30%] api/futures > reading sources... [ 33%] api/main > reading sources... [ 36%] api/message > reading sources... [ 40%] api/naming > reading sources... [ 43%] api/socketserver > reading sources... [ 46%] api/util > reading sources... [ 50%] changelog > reading sources... [ 53%] clientcode > reading sources... [ 56%] commandline > reading sources... [ 60%] config > reading sources... [ 63%] errors > reading sources... [ 66%] flame > reading sources... [ 70%] index > reading sources... [ 73%] install > reading sources... [ 76%] intro > reading sources... [ 80%] license > reading sources... [ 83%] nameserver > reading sources... [ 86%] pyrolite > reading sources... [ 90%] security > reading sources... [ 93%] servercode > reading sources... [ 96%] tipstricks > reading sources... [100%] tutorials > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > writing output... [ 3%] alternative > writing output... [ 6%] api > writing output... [ 10%] api/config > writing output... [ 13%] api/constants > writing output... [ 16%] api/core > writing output... [ 20%] api/echoserver > writing output... [ 23%] api/errors > writing output... [ 26%] api/flame > writing output... [ 30%] api/futures > writing output... [ 33%] api/main > writing output... [ 36%] api/message > writing output... [ 40%] api/naming > writing output... [ 43%] api/socketserver > writing output... [ 46%] api/util > writing output... [ 50%] changelog > writing output... [ 53%] clientcode > writing output... [ 56%] commandline > writing output... [ 60%] config > writing output... [ 63%] errors > writing output... [ 66%] flame > writing output... [ 70%] index > writing output... [ 73%] install > writing output... [ 76%] intro > writing output... [ 80%] license > writing output... [ 83%] nameserver > writing output... [ 86%] pyrolite > writing output... [ 90%] security > writing output... [ 93%] servercode > writing output... [ 96%] tipstricks > writing output... [100%] tutorials > > generating indices... genindex > writing additional pages... search > copying images... [ 33%] _static/flammable.png > copying images... [ 66%] _static/pyro-large.png > copying images... [100%] _static/tf_pyrotaunt.png > > copying static files... done > copying extra files... done > dumping search index in English (code: en) ... done > dumping object inventory... done > build succeeded. > > The HTML pages are in ../build/sphinx/html. > > Build finished. The HTML pages are in ../build/sphinx/html. > make[2]: Leaving directory '/<>/docs' > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py test > Pyro version = 4.76 > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating src/Pyro4.egg-info > writing src/Pyro4.egg-info/PKG-INFO > writing dependency_links to src/Pyro4.egg-info/dependency_links.txt > writing entry points to src/Pyro4.egg-info/entry_points.txt > writing requirements to src/Pyro4.egg-info/requires.txt > writing top-level names to src/Pyro4.egg-info/top_level.txt > writing manifest file 'src/Pyro4.egg-info/SOURCES.txt' > reading manifest file 'src/Pyro4.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '*/.svn/*' found anywhere in > distribution > warning: no previously-included files matching '*/.idea/*' found anywhere in > distribution > warning: no previously-included files matching '*.clas
Bug#951972: libwildmagic: FTBFS: ld: cannot find -lXext
Source: libwildmagic Version: 5.13-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/g++ -L ../../SDK/Library/DebugDynamic DebugDynamic/BspTree2.o > DebugDynamic/Edge2.o DebugDynamic/BspPolygon2.o DebugDynamic/Boolean2D.o -o > Boolean2D.DebugDynamic -lWm5Applications -lWm5Graphics -lWm5Imagics > -lWm5Physics -lWm5Mathematics -lWm5Core -lX11 -lXext -lGL -lGLU -lpthread -lm > /usr/bin/ld: cannot find -lXext > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/libwildmagic_5.13-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.
Bug#951965: cimg: FTBFS: ../CImg.h:413:10: fatal error: cv.h: No such file or directory
Source: cimg Version: 2.4.5+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -o CImg_demo CImg_demo.cpp -I.. -Wall -Wextra -Wfatal-errors > -Werror=unknown-pragmas -Werror=unused-label -Ofast -mtune=generic > -Dcimg_use_vt100 -Dcimg_display=1 -Dcimg_use_xrandr -Dcimg_use_tiff > -Dcimg_use_openexr -I/usr/include/OpenEXR -Dcimg_use_png -Dcimg_use_jpeg > -Dcimg_use_zlib -Dcimg_use_curl -Dcimg_use_opencv -I/usr/include/opencv > -I/usr/include/opencv -Dcimg_use_magick -I/usr/include/GraphicsMagick > -Dcimg_use_fftw3 -lm -lX11 -lpthread -lXrandr -ltiff -ltiffxx -lIlmImf > -lHalf -lpng -lz -ljpeg -lz -lcurl -lopencv_core -lopencv_highgui > -lGraphicsMagick++ -lGraphicsMagick -lfftw3 -lfftw3_threads > In file included from CImg_demo.cpp:48: > ../CImg.h:413:10: fatal error: cv.h: No such file or directory > 413 | #include "cv.h" > | ^~ > compilation terminated. > make[3]: *** [Makefile:304: CImg_demo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/cimg_2.4.5+dfsg-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.
Bug#951958: gimp-gap: FTBFS: ld: gap_mov_exec.o: undefined reference to symbol 'atan@@GLIBC_2.2.5'
Source: gimp-gap Version: 2.6.0+dfsg-5 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -fPIC -lm -Wl,-z,relro -o gap_plugins > gap_base_ops.o gap_bluebox.o gap_dbbrowser_utils.o gap_filter_codegen.o > gap_filter_pdb.o gap_lastvaldesc.o gap_main.o gap_mod_layer.o > gap_mod_layer_dialog.o gap_mov_dialog.o gap_mov_exec.o gap_mov_render.o > gap_navi_activtable.o gap_range_ops.o gap_resi_dialog.o gap_split.o > libgimpgap.a ../libgapbase/libgapbase.a -lgimpui-2.0 -lgimpwidgets-2.0 > -lgimpmodule-2.0 -lgimp-2.0 -lgimpmath-2.0 -lgimpconfig-2.0 -lgimpcolor-2.0 > -lgimpbase-2.0 -lgegl-0.4 -lgegl-npd-0.4 -Wl,--export-dynamic -lgmodule-2.0 > -pthread -ljson-glib-1.0 -lbabl-0.1 -lgtk-x11-2.0 -lgdk-x11-2.0 > -lpangocairo-1.0 -latk-1.0 -lcairo -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 > -lfontconfig -lfreetype -lgimpthumb-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 > -lglib-2.0 > /usr/bin/ld: gap_mov_exec.o: undefined reference to symbol 'atan@@GLIBC_2.2.5' > /usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/gimp-gap_2.6.0+dfsg-5_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.
Bug#951963: fauhdlc: FTBFS: FAUhdlParser.yy:12.10-15: error: invalid version requirement: 2.1a
Source: fauhdlc Version: 20180504-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/frontend/newparser' > bison FAUhdlParser.yy > flex FAUhdlScanner.l > FAUhdlParser.yy:12.10-15: error: invalid version requirement: 2.1a >12 | %require "2.1a" /* need this for c++ skeleton */ > | ^~ > make[2]: *** [Makefile:683: FAUhdlParser.tab.cc] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/fauhdlc_20180504-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.
Bug#951961: androguard: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7" returned exit code 13
Source: androguard
Version: 3.3.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="LC_ALL=C.UTF-8 {interpreter} -m nose
> --verbose" dh_auto_test
> I: pybuild base:217: LC_ALL=C.UTF-8 python3.8 -m nose --verbose
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Test def use with the GCD function above. ... ok
> testDefUseIfBool (dataflow_test.DataflowTest) ... ok
> testGroupVariablesGCD (dataflow_test.DataflowTest) ... ok
> testGroupVariablesIfBool (dataflow_test.DataflowTest) ... ok
> testReachDefGCD (dataflow_test.DataflowTest) ... ok
> testSplitVariablesGCD (dataflow_test.DataflowTest) ... ok
> testSplitVariablesIfBool (dataflow_test.DataflowTest) ... ok
> testCrossGraph (dominator_test.DominatorTest) ... ok
> testFifthGraph (dominator_test.DominatorTest) ... ok
> testFirstGraph (dominator_test.DominatorTest) ... ok
> testFourthGraph (dominator_test.DominatorTest) ... ok
> testLinearVitGraph (dominator_test.DominatorTest) ... ok
> testSecondGraph (dominator_test.DominatorTest) ... ok
> testTVerifyGraph (dominator_test.DominatorTest) ... ok
> testTarjanGraph (dominator_test.DominatorTest) ... ok
> testThirdGraph (dominator_test.DominatorTest) ... ok
> testCrossGraph (rpo_test.RpoTest) ... ok
> testFifthGraph (rpo_test.RpoTest) ... ok
> testFirstGraph (rpo_test.RpoTest) ... ok
> testFourthGraph (rpo_test.RpoTest) ... ok
> testLinearVitGraph (rpo_test.RpoTest) ... ok
> testSecondGraph (rpo_test.RpoTest) ... ok
> testTVerifyGraph (rpo_test.RpoTest) ... ok
> testTarjanGraph (rpo_test.RpoTest) ... ok
> testThirdGraph (rpo_test.RpoTest) ... ok
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> testAndroidManifest (test_axml.AXMLTest) ... ok
> Test if wrong arsc headers are rejected ... ok
> Test if weird namespace constelations cause problems ... ok
> Test if extra namespaces cause problems ... ok
> Compare the binary version of a file with the plain text ... ok
> Assert that Namespaces which are used in a tag and the tag is closed ... ok
> Test if a single header without string pool is rejected ... ok
> testNonManifest (test_axml.AXMLTest) ... ok
> Test if non-null terminated strings are detected. ... ok
> Test if a nonzero style offset in the string section causes problems ... ok
> Assert that Strings with nullbytes are handled correctly ... ok
> Assert that Packed files are read ... ok
> Test that the replacements for attributes, names and values are working ... ok
> Test for Text chunks containing XML ... ok
> Test if a very short file is rejected ... ok
> Assert that files with a broken filesize are not parsed ... ok
> Test if a wrong header size is rejected ... ok
> Test if a wrong header type is rejected ... ok
> Test if a wrong string pool header size is rejected ... ok
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
>
> ==
> ERROR: Failure: ModuleNotFoundError (No module named 'asn1crypto')
> --
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
> File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in
> loadTestsFromName
> module = self.importer.importFromPath(
> File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in
> importFromPath
> return self.importFromDir(dir_path, fqname)
> File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in
> importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
> File &q
Bug#951947: decopy: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: decopy
Version: 0.2.4.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> LC_ALL=C.UTF-8 dh_auto_test
> I: pybuild base:217: python3.8 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> creating Decopy.egg-info
> writing Decopy.egg-info/PKG-INFO
> writing dependency_links to Decopy.egg-info/dependency_links.txt
> writing entry points to Decopy.egg-info/entry_points.txt
> writing top-level names to Decopy.egg-info/top_level.txt
> writing manifest file 'Decopy.egg-info/SOURCES.txt'
> reading manifest file 'Decopy.egg-info/SOURCES.txt'
> writing manifest file 'Decopy.egg-info/SOURCES.txt'
> running build_ext
> WARNING:root:command exiftool not found, using generic parser as fallback
> testCleanComments (tests.matchers_test.TestMatchers) ... ok
> testParseBsd (tests.matchers_test.TestMatchers) ... ok
> testParseCCBY (tests.matchers_test.TestMatchers) ... ok
> testParseCopyright (tests.matchers_test.TestMatchers) ... ok
> testParseGFDL (tests.matchers_test.TestMatchers) ... ok
> testParseGPL (tests.matchers_test.TestMatchers) ... ok
> testParseHolders (tests.matchers_test.TestMatchers) ... ok
> testParseHoldersMultiline (tests.matchers_test.TestMatchers) ... ok
> testParseHoldersMultilineYears (tests.matchers_test.TestMatchers) ... ok
> testParseLGPL (tests.matchers_test.TestMatchers) ... ok
> testParseLPPL (tests.matchers_test.TestMatchers) ... ok
> testParseMIT (tests.matchers_test.TestMatchers) ... ok
> testParseZPL (tests.matchers_test.TestMatchers) ... ok
> testAddTwoPeople (tests.tree_test.TestCopyrightGroup) ... ok
> testMergeEmails (tests.tree_test.TestCopyrightGroup) ... ok
> testMergeNames (tests.tree_test.TestCopyrightGroup) ... ok
> testMergeNamesWithYears (tests.tree_test.TestCopyrightGroup) ... ok
> testMergeYears (tests.tree_test.TestCopyrightGroup) ... ok
> testCommonPathEmpty (tests.tree_test.TestFileGroup) ... ok
> testCommonPathOneDirTwoFiles (tests.tree_test.TestFileGroup) ... ok
> testCommonPathOneFile (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsEmptyGroup (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsOneDirOneFile (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsOneFile (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsRoot (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsSeparateGroups (tests.tree_test.TestFileGroup) ... ok
> testGetPatternsSeparateGroupsMoreFiles (tests.tree_test.TestFileGroup) ... ok
> testFullname (tests.tree_test.TestFileInfo) ... ok
> testGetLicenses (tests.tree_test.TestFileInfo) ... ok
> testIncluded (tests.tree_test.TestFileInfo) ... ok
> testSplittingPath (tests.tree_test.TestFileInfo) ... ok
> testTally (tests.tree_test.TestFileInfo) ... ok
> testCopyrightedTree (tests.tree_test.TestRootInfo)
> Parses a tree with licensed & copyrighted files (testdata/two). ...
> testDebianizedTree (tests.tree_test.TestRootInfo)
> Parses a tree that contains a debian/copyright (testdata/three). ...
> /usr/lib/python3/dist-packages/debian/copyright.py:654: UserWarning: Fixing
> Format URL
> warnings.warn('Fixing Format URL')
> ok
> testSimpleTree (tests.tree_test.TestRootInfo)
> Parses a tree with licensed files (testdata/one). ... ok
> testTreeExclude (tests.tree_test.TestRootInfo)
> Parse a tree with an exclusion expresion (testdata/three). ... ok
> testProcessComplex (tests.dep5_test.TestCopyright)
> Parses a debian/copyright with many entries (testdata/three). ... ok
> testProcessEmpty (tests.dep5_test.TestCopyright)
> Parses a tree with no debian/copyright file. ... ok
> testProcessMalformed (tests.dep5_test.TestCopyright)
> Parses a tree with a malformed debian/copyright file. ... ok
> testProcessSimple (tests.dep5_test.TestCopyright)
> Parses a debian/copyright with two entries (testdata/four). ... ok
> testRemoveMisplaced (tests.dep5_test.TestCopyright)
> Removes files from copyright if they were wrong (testdata/three). ... ok
> testRemoveMisplacedCopyright (tests.dep5_test.TestCopyright)
> Removes files if they were wrong, grouping by copyright. ... ok
> testRemoveMisplacedPartial (tests.dep5_test.TestCopyright)
> Removes files if they were wrong, grouping by copyright. ... ok
> testUnknownLicense (tests.dep5_test.TestGroup) ... ok
> testSpdxA (tests.matchers_spdx_test.TestSpdx) ... ok
> testSpdxB (tests.matchers_spdx_test.TestSpdx) ... ok
> testSpdxC (tests.matchers_spdx_tes
Bug#951960: purify: FTBFS: ld: ../purify/libpurify.so.2.0.0: undefined reference to `fmt::v6::internal::basic_data::signs'
Source: purify Version: 2.0.0-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wl,-z,relro -rdynamic > CMakeFiles/test_purify_fitsio.dir/purify_fitsio.cc.o > CMakeFiles/common_catch_main_object.dir/__/__/common_catch_main.cc.o -o > test_purify_fitsio > -Wl,-rpath,/<>/obj-x86_64-linux-gnu/cpp/purify:/usr/lib/x86_64-linux-gnu/openmpi/lib > ../purify/libpurify.so.2.0.0 /usr/lib/x86_64-linux-gnu/libfftw3_omp.so > /usr/lib/x86_64-linux-gnu/libfftw3.so -lCCfits -lcfitsio > /usr/lib/x86_64-linux-gnu/libsopt.so.3.0.1 -ltiff > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so > /usr/lib/x86_64-linux-gnu/libcasa_ms.so > /usr/lib/x86_64-linux-gnu/libcasa_measures.so > /usr/lib/x86_64-linux-gnu/libcasa_tables.so > /usr/lib/x86_64-linux-gnu/libcasa_scimath.so > /usr/lib/x86_64-linux-gnu/libcasa_scimath_f.so > /usr/lib/x86_64-linux-gnu/libcasa_casa.so -fopenmp > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data::signs' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `vtable for > fmt::v6::format_error' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::snprintf_float(double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::assert_fail(char const*, int, char const*)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::error_handler::on_error(char const*)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char > fmt::v6::internal::decimal_point_impl(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data::zero_or_powers_of_10_32' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char > fmt::v6::internal::thousands_sep_impl(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `typeinfo > for fmt::v6::format_error' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `std::__cxx11::basic_string, > std::allocator > > fmt::v6::internal::grouping_impl(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::format_float(long double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::snprintf_float(long double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::format_error::~format_error()' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data::hex_digits' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data::digits' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::format_float(double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data::zero_or_powers_of_10_64' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/purify_2.0.0-4_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.
Bug#951945: cramfsswap: FTBFS: cramfsswap.c:348: undefined reference to `crc32'
Source: cramfsswap Version: 1.4.1-1.1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/cc4uCS9T.o: in function `main': > /<>/cramfsswap.c:348: undefined reference to `crc32' > /usr/bin/ld: /<>/cramfsswap.c:350: undefined reference to `crc32' > /usr/bin/ld: /<>/cramfsswap.c:350: undefined reference to `crc32' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/cramfsswap_1.4.1-1.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.
Bug#951959: megaglest: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'
Source: megaglest Version: 3.13.0-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_ce1cd.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/megaglest_3.13.0-4_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.
Bug#951943: blockattack: FTBFS: SagoDataHolder.hpp:26:10: fatal error: SDL_mixer.h: No such file or directory
Source: blockattack Version: 2.5.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DLOCALEDIR=\"/usr//usr/share/locale/\" > -DSHAREDIR=\"/usr/share/games/blockattack\" > -I/usr/include/x86_64-linux-gnu/SDL2 > -I/<>/source/code/Libs/include > -I/<>/source/code/Libs/include/cereal/external -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra > -std=c++11 -Wno-implicit-fallthrough -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra > -std=c++11 -O3 -DNDEBUG -O2 -o > CMakeFiles/blockattack.dir/source/code/HelpAboutState.cpp.o -c > /<>/source/code/HelpAboutState.cpp > In file included from /<>/source/code/sago/SagoTextField.hpp:28, > from /<>/source/code/HelpGamepadState.hpp:28, > from /<>/source/code/HelpGamepadState.cpp:24: > /<>/source/code/sago/SagoDataHolder.hpp:26:10: fatal error: > SDL_mixer.h: No such file or directory >26 | #include //Used for sound & music > | ^ > compilation terminated. > In file included from /<>/source/code/sago/SagoTextBox.hpp:28, > from /<>/source/code/HelpAboutState.hpp:28, > from /<>/source/code/HelpAboutState.cpp:24: > /<>/source/code/sago/SagoDataHolder.hpp:26:10: fatal error: > SDL_mixer.h: No such file or directory >26 | #include //Used for sound & music > | ^ > compilation terminated. > make[4]: *** [CMakeFiles/blockattack.dir/build.make:105: > CMakeFiles/blockattack.dir/source/code/HelpGamepadState.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/blockattack_2.5.0-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.
Bug#951953: python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: python-django-imagekit Version: 4.0.2-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/registry.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/generatorlibrary.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/lib.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/pkgmeta.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/conf.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/hashers.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/compat.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/admin.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/exceptions.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/signals.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/utils.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > copying imagekit/files.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/forms > copying imagekit/forms/fields.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/forms > copying imagekit/forms/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/forms > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/models > copying imagekit/models/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/models > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > copying imagekit/processors/resize.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > copying imagekit/processors/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > copying imagekit/processors/crop.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > copying imagekit/processors/base.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > copying imagekit/processors/utils.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/processors > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/specs > copying imagekit/specs/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/specs > copying imagekit/specs/sourcegroups.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/specs > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/templatetags > copying imagekit/templatetags/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/templatetags > copying imagekit/templatetags/imagekit.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/templatetags > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/backends.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/strategies.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/namers.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/cachefiles > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/management > copying imagekit/management/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/management > creating > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/models/fields > copying imagekit/models/fields/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-imagekit/build/imagekit/models/fields > copying imagekit/models/f
Bug#951937: php-pecl-http: FTBFS: configure: error: please install and enable pecl/raphf
Source: php-pecl-http Version: 3.2.1+2.6.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking whether/where to check for libidnkit2... yes > checking for libidnkit2... no > checking whether/where to check for libidnkit... yes > checking for libidnkit... no > checking whether ext/raphf is enabled... no > configure: error: please install and enable pecl/raphf > cd build-7.4 && tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/php-pecl-http_3.2.1+2.6.0-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.
Bug#951939: contextfree: FTBFS: src-common/cfdg.cpp:75:71: error: no matching function for call to ‘find(std::array, 18>::const_iterator, std::array
Source: contextfree
Version: 3.2+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Isrc-common -Isrc-unix -Iobjs
> -Isrc-common/agg-extras -Isrc-ffmpeg/include -I/usr/local/include -O2 -Wall
> -Wextra -Wno-parentheses -std=c++14 -g -D_GLIBCXX_USE_C99_MATH=1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -DNDEBUG -c -o objs/cfdgimpl.o src-common/cfdgimpl.cpp
> src-common/cfdg.cpp: In static member function ‘static CFG
> CFDG::lookupCfg(const string&)’:
> src-common/cfdg.cpp:75:71: error: no matching function for call to
> ‘find(std::array, 18>::const_iterator,
> std::array, 18>::const_iterator, const
> string&)’
>75 | auto nameIt = std::find(ParamNames.begin(), ParamNames.end(),
> name);
> |
> ^
> In file included from /usr/include/c++/9/bits/locale_facets.h:48,
> from /usr/include/c++/9/bits/basic_ios.h:37,
> from /usr/include/c++/9/ios:44,
> from /usr/include/c++/9/ostream:38,
> from /usr/include/c++/9/iostream:39,
> from objs/location.hh:41,
> from src-common/cfdg.h:40,
> from src-common/cfdg.cpp:31:
> /usr/include/c++/9/bits/streambuf_iterator.h:373:5: note: candidate:
> ‘template typename
> __gnu_cxx::__enable_if::__value,
> std::istreambuf_iterator<_CharT> >::__type
> std::find(std::istreambuf_iterator<_CharT>, std::istreambuf_iterator<_CharT>,
> const _CharT2&)’
> 373 | find(istreambuf_iterator<_CharT> __first,
> | ^~~~
> /usr/include/c++/9/bits/streambuf_iterator.h:373:5: note: template argument
> deduction/substitution failed:
> src-common/cfdg.cpp:75:71: note: mismatched types
> ‘std::istreambuf_iterator<_CharT>’ and ‘const value_type*’ {aka ‘const
> std::__cxx11::basic_string*’}
>75 | auto nameIt = std::find(ParamNames.begin(), ParamNames.end(),
> name);
> |
> ^
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Isrc-common -Isrc-unix -Iobjs
> -Isrc-common/agg-extras -Isrc-ffmpeg/include -I/usr/local/include -O2 -Wall
> -Wextra -Wno-parentheses -std=c++14 -g -D_GLIBCXX_USE_C99_MATH=1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -DNDEBUG -c -o objs/renderimpl.o
> src-common/renderimpl.cpp
> make[1]: *** [Makefile:207: objs/cfdg.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/contextfree_3.2+dfsg1-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.
Bug#951946: intel-gpu-tools: FTBFS: ld: final link failed: bad value
Source: intel-gpu-tools Version: 1.24-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libprocps.a(readproc.o): relocation > R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used when > making a shared object; recompile with -fPIC > /usr/bin/ld: final link failed: bad value > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/intel-gpu-tools_1.24-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.
Bug#951948: vdirsyncer: FTBFS: LookupError: setuptools-scm was unable to detect version for '/<>'.
Source: vdirsyncer Version: 0.16.7-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > /usr/share/sphinx/scripts/python3/sphinx-build -b man -d _build/doctrees . > _build/man > Running Sphinx v1.8.5 > > Configuration error: > There is a programmable error in your configuration file: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sphinx/config.py", line 368, in > eval_config_file > execfile_(filename, namespace) > File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in > execfile_ > exec_(code, _globals) > File "/<>/docs/conf.py", line 19, in > release = setuptools_scm.get_version(root='..', relative_to=__file__) > File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 150, > in get_version > parsed_version = _do_parse(config) > File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 113, > in _do_parse > "use git+https://github.com/user/proj.git#egg=proj; % config.absolute_root > LookupError: setuptools-scm was unable to detect version for > '/<>'. > > Make sure you're either building from a fully intact git repository or PyPI > tarballs. Most other sources (such as GitHub's tarballs, a git checkout > without the .git folder) don't contain the necessary metadata and will not > work. > > For example, if you're using pip, instead of > https://github.com/user/proj/archive/master.zip use > git+https://github.com/user/proj.git#egg=proj > > make[2]: *** [Makefile:131: man] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/vdirsyncer_0.16.7-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.
Bug#951932: icecream-sundae: FTBFS: (.text+0x8a78): undefined reference to `ZSTD_decompress'
Source: icecream-sundae Version: 1.0.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libicecc.a(libicecc_la-comm.o): in > function `MsgChannel::readcompressed(unsigned char**, unsigned long&, > unsigned long&)': > (.text+0x8a78): undefined reference to `ZSTD_decompress' > /usr/bin/ld: (.text+0x8a85): undefined reference to `ZSTD_isError' > /usr/bin/ld: (.text+0x8bc6): undefined reference to `ZSTD_getErrorName' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/icecream-sundae_1.0.0-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.
Bug#951952: hdf5: FTBFS: ../../../src/H5Smpio.c:1503:9: error: call to ‘MPI_Type_extent’ declared with attribute error: MPI_Type_extent was removed in MPI-3.0. Use MPI_Type_get_extent instead.
Source: hdf5 Version: 1.10.4+repack-10 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link mpicc.openmpi -std=c99 > -pedantic -Wall -Wextra -Wbad-function-cast -Wc++-compat -Wcast-align > -Wcast-qual -Wconversion -Wdeclaration-after-statement > -Wdisabled-optimization -Wfloat-equal -Wformat=2 -Winit-self -Winvalid-pch > -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes > -Wnested-externs -Wold-style-definition -Wpacked -Wpointer-arith > -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum > -Wundef -Wunused-macros -Wunsafe-loop-optimizations -Wwrite-strings > -finline-functions -s -Wno-inline -Wno-aggregate-return > -Wno-missing-format-attribute -Wno-missing-noreturn -O -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,--version-script,../../../debian/map_mpi.ver > -Wl,-z,relro -o H5make_libsettings H5make_libsettings.o -lsz -lz -ldl -lm > ../../../src/H5Smpio.c:1503:9: error: call to ‘MPI_Type_extent’ declared with > attribute error: MPI_Type_extent was removed in MPI-3.0. Use > MPI_Type_get_extent instead. > 1503 | MPI_Type_extent (old_type, _extent); > | ^~~ > ../../../src/H5Smpio.c: In function ‘H5S_mpio_hyper_type’: > ../../../src/H5Smpio.c:882:13: error: call to ‘MPI_Type_extent’ declared with > attribute error: MPI_Type_extent was removed in MPI-3.0. Use > MPI_Type_get_extent instead. > 882 | MPI_Type_extent (inner_type, _extent); > | ^~~ > make[4]: *** [Makefile:1603: H5Smpio.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/hdf5_1.10.4+repack-10_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.
Bug#951951: gzip: FTBFS: stdio.h:366: undefined reference to `__chk_fail'
Source: gzip Version: 1.9-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/builddir-indep' > CC bits.o > CC deflate.o > CC gzip.o > CC inflate.o > CC lzw.o > CC trees.o > CC unlzh.o > CC unlzw.o > CC unpack.o > CC unzip.o > CC util.o > CC zip.o > CC version.o > AR libver.a > CCLD gzip.exe > /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy': > /usr/share/mingw-w64/include/string.h:228: undefined reference to > `__memcpy_chk' > /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: > undefined reference to `__strcpy_chk' > /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: > undefined reference to `__memcpy_chk' > /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: > undefined reference to `__stpcpy_chk' > /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcat': > /usr/share/mingw-w64/include/string.h:234: undefined reference to > `__memcpy_chk' > /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy': > /usr/share/mingw-w64/include/string.h:228: undefined reference to > `__strcpy_chk' > /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: > undefined reference to `__stpcpy_chk' > /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcat': > /usr/share/mingw-w64/include/string.h:234: undefined reference to > `__strcpy_chk' > /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:234: > undefined reference to `__strcpy_chk' > /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy': > /usr/share/mingw-w64/include/string.h:228: undefined reference to > `__memcpy_chk' > /usr/bin/i686-w64-mingw32-ld: lib/libgzip.a(openat-proc.o): in function > `sprintf': > /usr/share/mingw-w64/include/stdio.h:366: undefined reference to `__chk_fail' > /usr/bin/i686-w64-mingw32-ld: lib/libgzip.a(vasnprintf.o): in function > `sprintf': > /usr/share/mingw-w64/include/stdio.h:366: undefined reference to `__chk_fail' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/gzip_1.9-3_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.
Bug#951941: slop: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:11: undefined reference to `pthread_create'
Source: slop Version: 7.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_26376.dir/src.cxx.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/slop_7.4-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.
Bug#951955: grantlee5: FTBFS: c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -st
Source: grantlee5
Version: 5.1.0-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
> "Unix Makefiles" /<> /<>/textdocument/lib
> /<>/obj-x86_64-linux-gnu
> /<>/obj-x86_64-linux-gnu/textdocument/lib
> /<>/obj-x86_64-linux-gnu/textdocument/lib/CMakeFiles/Grantlee_TextDocument.dir/DependInfo.cmake
> --color=
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:925:9: error: no
> declaration matches ‘QString QStringView::toString() const’
> 925 | QString QStringView::toString() const
> | ^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:925:9: note: no functions
> named ‘QString QStringView::toString() const’
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:54,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from
> /<>/templates/tests/pluginpointertest/myobject.h:24,
> from
> /<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/myplugin_autogen/EWIEGA46WW/moc_myobject.cpp:9,
> from
> /<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/myplugin_autogen/mocs_compilation.cpp:2:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringview.h:104:7: note: ‘class
> QStringView’ defined here
> 104 | class QStringView
> | ^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h: In instantiation of
> ‘QFlags QFlags::operator|(Enum) const [with Enum =
> QString::SectionFlag]’:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1420:1: required from
> here
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:140:108: error: ‘Int’ was
> not declared in this scope; did you mean ‘int’?
> 140 | Q_DECL_CONSTEXPR inline QFlags operator|(Enum other) const
> Q_DECL_NOTHROW { return QFlags(QFlag(i | Int(other))); }
> |
> ~~~^~~
> |
> int
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from
> /<>/templates/tests/pluginpointertest/myobject.h:24,
> from
> /<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/myplugin_autogen/EWIEGA46WW/moc_myobject.cpp:9,
> from
> /<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/myplugin_autogen/mocs_compilation.cpp:2:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:975:16: error: no
> declaration matches ‘QString QString::arg(int, int, int, QChar) const’
> 975 | inline QString QString::arg(int a, int fieldWidth, int base, QChar
> fillChar) const
> |^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:975:16: note: no functions
> named ‘QString QString::arg(int, int, int, QChar) const’
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:218:21: note: ‘class
> QString’ defined here
> 218 | class Q_CORE_EXPORT QString
> | ^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:977:16: error: no
> declaration matches ‘QString QString::arg(uint, int, int, QChar) const’
> 977 | inline QString QString::arg(uint a, int fieldWidth, int base, QChar
> fillChar) const
> |^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:977:16: note: no functions
> named ‘QString QString::arg(uint, int, int, QChar) const’
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:218:21: note: ‘class
> QString’ defined here
> 218 | class Q_CORE_EXPORT QString
> | ^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:979:16: error: no
> declaration matches ‘QString QString::arg(long int, int, int, QChar) const’
> 979 | inline QString QString::arg(long a, int fieldWidth, int base, QChar
> fillChar) const
> |^~~
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:979:16: note: no functions
> named ‘QString QString::arg(long int, int, int, QChar) const’
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:218:21: note: ‘class
> QString’ defined here
> 218 | class Q_CORE_EXPO
Bug#951950: pyregion: FTBFS: NameError: name 'intersphinx_mapping' is not defined
Source: pyregion Version: 2.0-9 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > cython3 pyregion/_region_filter.pyx > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: /<>/pyregion/_region_filter.pyx > tree = Parsing.p_module(s, pxd, full_module_name) > dh_auto_build > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/core.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/__init__.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/physical_coordinate.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/mpl_helper.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/ds9_region_parser.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/_astropy_init.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/wcs_helper.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/wcs_converter.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/cython_version.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/parser_helper.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/conftest.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/version.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/region_numbers.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/ds9_attr_parser.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/region_to_filter.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > creating /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_ds9_attr_parser.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/__init__.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_region.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_wcs.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_cube.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_ds9_region_parser.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_parser_helper.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_get_mask.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/setup_package.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/tests/test_region_numbers.py -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > copying pyregion/_region_filter.c -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/_compiler.c -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion > copying pyregion/tests/coveragerc -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests > creating > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test03_icrs.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test02_1_img.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test03_ciao_physical.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test01_gal.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test01_ds9_physical.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/tests/data/test01_ciao_physical.reg -> > /<>/.pybuild/cpython3_3.8_pyregion/build/pyregion/tests/data > copying pyregion/t
Bug#951949: ironic: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpvywf2zgw/tmpsv87ez1t'
Source: ironic
Version: 1:13.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ==
> FAIL:
> ironic.tests.unit.drivers.modules.ibmc.test_utils.IBMCUtilsTestCase.test_parse_driver_info_default_scheme_with_port
> ironic.tests.unit.drivers.modules.ibmc.test_utils.IBMCUtilsTestCase.test_parse_driver_info_default_scheme_with_port
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File
> "/<>/ironic/tests/unit/drivers/modules/ibmc/test_utils.py", line
> 56, in test_parse_driver_info_default_scheme_with_port
> response = utils.parse_driver_info(self.node)
> File "/<>/ironic/drivers/modules/ibmc/utils.py", line 89, in
> parse_driver_info
> {'address': address, 'node': node.uuid})
> ironic.common.exception.InvalidParameterValue: Invalid iBMC address
> example.com:42 set in driver_info/ibmc_address on node
> 1be26c0b-03f2-4d2e-ae87-c02d7f33c123
>
>
> --
> Ran 5999 tests in 182.107s
>
> FAILED (failures=1, skipped=12)
> make[1]: *** [debian/rules:31: override_dh_install] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ironic_13.0.1-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.
Bug#951920: python-igraph: FTBFS: ld: cannot find -llzma
Source: python-igraph Version: 0.8.0-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CXX --mode=link g++ > -I/<>/vendor/source/igraph/include -I../include -Wall > -I/<>/vendor/source/igraph/optional/glpk > -I/<>/vendor/source/igraph/src/prpack -DPRPACK_IGRAPH_SUPPORT -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fPIC -O3 -no-undefined -Wl,-z,relro -Wl,-z,now -o > libigraph.la -rpath /usr/local/lib libigraph_la-basic_query.lo > libigraph_la-games.lo libigraph_la-cocitation.lo libigraph_la-iterators.lo > libigraph_la-structural_properties.lo libigraph_la-components.lo > libigraph_la-layout.lo libigraph_la-structure_generators.lo > libigraph_la-conversion.lo libigraph_la-type_indexededgelist.lo > libigraph_la-spanning_trees.lo libigraph_la-igraph_error.lo > libigraph_la-interrupt.lo libigraph_la-other.lo libigraph_la-foreign.lo > libigraph_la-random.lo libigraph_la-attributes.lo > libigraph_la-foreign-ncol-parser.lo libigraph_la-foreign-ncol-lexer.lo > libigraph_la-foreign-lgl-parser.lo libigraph_la-foreign-lgl-lexer.lo > libigraph_la-foreign-pajek-parser.lo libigraph_la-foreign-pajek-lexer.lo > libigraph_la-foreign-gml-parser.lo libigraph_la-foreign-gml-lexer.lo > libigraph_la-dqueue.lo libigraph_la-heap.lo libigraph_la-igraph_heap.lo > libigraph_la-igraph_stack.lo libigraph_la-igraph_strvector.lo > libigraph_la-igraph_trie.lo libigraph_la-matrix.lo libigraph_la-vector.lo > libigraph_la-vector_ptr.lo libigraph_la-memory.lo libigraph_la-adjlist.lo > libigraph_la-visitors.lo libigraph_la-igraph_grid.lo libigraph_la-atlas.lo > libigraph_la-topology.lo libigraph_la-motifs.lo libigraph_la-progress.lo > libigraph_la-operators.lo libigraph_la-igraph_psumtree.lo > libigraph_la-array.lo libigraph_la-igraph_hashtable.lo > libigraph_la-foreign-graphml.lo libigraph_la-flow.lo > libigraph_la-igraph_buckets.lo libigraph_la-NetDataTypes.lo > libigraph_la-NetRoutines.lo libigraph_la-clustertool.lo > libigraph_la-pottsmodel_2.lo libigraph_la-spectral_properties.lo > libigraph_la-cores.lo libigraph_la-igraph_set.lo libigraph_la-cliques.lo > libigraph_la-walktrap.lo libigraph_la-walktrap_heap.lo > libigraph_la-walktrap_graph.lo libigraph_la-walktrap_communities.lo > libigraph_la-infomap.lo libigraph_la-infomap_Greedy.lo > libigraph_la-infomap_Node.lo libigraph_la-infomap_FlowGraph.lo > libigraph_la-spmatrix.lo libigraph_la-community.lo > libigraph_la-fast_community.lo libigraph_la-community_leiden.lo > libigraph_la-gml_tree.lo bliss/libigraph_la-orbit.lo > bliss/libigraph_la-defs.lo bliss/libigraph_la-uintseqhash.lo > bliss/libigraph_la-partition.lo bliss/libigraph_la-graph.lo > bliss/libigraph_la-bliss_heap.lo bliss/libigraph_la-utils.lo > libigraph_la-bliss.lo libigraph_la-cattributes.lo libigraph_la-zeroin.lo > libigraph_la-bfgs.lo libigraph_la-math.lo libigraph_la-forestfire.lo > libigraph_la-microscopic_update.lo libigraph_la-blas.lo > libigraph_la-arpack.lo libigraph_la-centrality.lo libigraph_la-drl_layout.lo > libigraph_la-drl_parse.lo libigraph_la-drl_graph.lo > libigraph_la-DensityGrid.lo libigraph_la-gengraph_box_list.lo > libigraph_la-gengraph_degree_sequence.lo > libigraph_la-gengraph_graph_molloy_hash.lo > libigraph_la-gengraph_graph_molloy_optimized.lo > libigraph_la-gengraph_mr-connected.lo libigraph_la-gengraph_powerlaw.lo > libigraph_la-gengraph_random.lo libigraph_la-decomposition.lo > libigraph_la-bipartite.lo libigraph_la-drl_layout_3d.lo > libigraph_la-drl_graph_3d.lo libigraph_la-DensityGrid_3d.lo > libigraph_la-foreign-dl-parser.lo libigraph_la-foreign-dl-lexer.lo > cs/libigraph_la-cs_add.lo cs/libigraph_la-cs_happly.lo > cs/libigraph_la-cs_pvec.lo cs/libigraph_la-cs_amd.lo > cs/libigraph_la-cs_house.lo cs/libigraph_la-cs_qr.lo > cs/libigraph_la-cs_chol.lo cs/libigraph_la-cs_ipvec.lo > cs/libigraph_la-cs_qrsol.lo cs/libigraph_la-cs_cholsol.lo > cs/libigraph_la-cs_leaf.lo cs/libigraph_la-cs_randperm.lo > cs/libigraph_la-cs_compress.lo cs/libigraph_la-cs_load.lo > cs/libigraph_la-cs_reach.lo cs/libigraph_la-cs_counts.lo > cs/libigraph_la-cs_lsolve.lo cs/libigraph_la-cs_scatter.lo > cs/libigraph_la-cs_cumsum.lo cs/libigraph_la-cs_ltsolve.lo > cs/libigraph_la-cs_scc.lo cs/libigraph_la-cs_dfs.lo cs/libigraph_la-cs_lu.lo > cs/libigraph_la-cs_schol.lo cs/libigraph_la-cs_dmperm.lo > cs/libigraph_la-cs_lusol.lo cs/libigraph_la-cs_spsolve.lo > cs/libigraph_la-cs_droptol.lo cs/libigraph_la-cs_malloc.lo > cs/libigraph_la-cs_sqr.lo cs/libigraph_la-cs_dropzer
Bug#951922: advi: FTBFS: configure: error: kpsexpand not found, check your PATH
Source: advi Version: 1.10.2-5 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking X11/extensions/Xinerama.h usability... yes > checking X11/extensions/Xinerama.h presence... yes > checking for X11/extensions/Xinerama.h... yes > checking for XineramaQueryScreens in -lXinerama... yes > checking for kpsexpand... no > configure: error: kpsexpand not found, check your PATH > make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/02/22/advi_1.10.2-5_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.
Bug#951930: flickcurl: FTBFS: configure: error: Please install version 2.6.8 or newer
Source: flickcurl Version: 1.26-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for echo... echo > checking for pkg-config... pkg-config > checking for xml2-config... xml2-config > checking for xmlCreatePushParserCtxt... no > checking for libxml via xml2-config... no - not found > configure: error: Please install version 2.6.8 or newer > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/flickcurl_1.26-4_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.
Bug#951934: autoradio: FTBFS: ImportError: cannot import name 'permalink' from 'django.db.models' (/usr/lib/python3/dist-packages/django/db/models/__init__.py)
Source: autoradio
Version: 3.1-6
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:217: python3.7 setup.py clean
> django_extensions is not installed; I do not use it
> Traceback (most recent call last):
> File "setup.py", line 17, in
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, in
> populate
> app_config.import_models()
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in
> import_models
> self.models_module = import_module(models_module_name)
> File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1006, in _gcd_import
> File "", line 983, in _find_and_load
> File "", line 967, in _find_and_load_unlocked
> File "", line 677, in _load_unlocked
> File "", line 728, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/<>/autoradio/programs/models.py", line 9, in
> from django.db.models import permalink
> ImportError: cannot import name 'permalink' from 'django.db.models'
> (/usr/lib/python3/dist-packages/django/db/models/__init__.py)
> E: pybuild pybuild:341: clean: plugin distutils failed with: exit code=1:
> python3.7 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.7 returned exit
> code 13
> make[1]: *** [debian/rules:10: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/autoradio_3.1-6_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.
Bug#951924: diodon: FTBFS: testcase.vala:32.5-32.19: error: Creation method of abstract class cannot be public.
Source: diodon Version: 1.8.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./waf build --nocache --prefix=/usr > Waf: Entering directory `/<>/_build_' > [ 1/70] po: po/bg.po -> _build_/po/bg.mo > [ 2/70] po: po/ca.po -> _build_/po/ca.mo > [ 3/70] po: po/cs.po -> _build_/po/cs.mo > [ 4/70] po: po/de.po -> _build_/po/de.mo > [ 5/70] po: po/en_GB.po -> _build_/po/en_GB.mo > [ 6/70] po: po/es.po -> _build_/po/es.mo > [ 7/70] po: po/et.po -> _build_/po/et.mo > [ 8/70] po: po/fi.po -> _build_/po/fi.mo > [ 9/70] po: po/fr.po -> _build_/po/fr.mo > [10/70] po: po/gl.po -> _build_/po/gl.mo > [11/70] po: po/hu.po -> _build_/po/hu.mo > [12/70] po: po/it.po -> _build_/po/it.mo > [13/70] po: po/ja.po -> _build_/po/ja.mo > [14/70] po: po/lt.po -> _build_/po/lt.mo > [15/70] po: po/nb.po -> _build_/po/nb.mo > [16/70] po: po/nl.po -> _build_/po/nl.mo > [17/70] po: po/pl.po -> _build_/po/pl.mo > [18/70] po: po/pt.po -> _build_/po/pt.mo > [19/70] po: po/pt_BR.po -> _build_/po/pt_BR.mo > [20/70] po: po/ro.po -> _build_/po/ro.mo > [21/70] po: po/ru.po -> _build_/po/ru.mo > [22/70] po: po/se.po -> _build_/po/se.mo > [23/70] po: po/sk.po -> _build_/po/sk.mo > [24/70] po: po/sv.po -> _build_/po/sv.mo > [25/70] po: po/tr.po -> _build_/po/tr.mo > [26/70] po: po/uk.po -> _build_/po/uk.mo > [27/70] po: po/zh_CN.po -> _build_/po/zh_CN.mo > [28/70] subst: data/net.launchpad.Diodon.gschema.xml.in.in -> > _build_/data/net.launchpad.Diodon.gschema.xml.in > [29/70] intltool: data/diodon.desktop.in -> _build_/data/diodon.desktop > [30/70] intltool: data/diodon-autostart.desktop.in -> > _build_/data/diodon-autostart.desktop > [31/70] subst_pc: data/diodon.pc.in -> _build_/data/diodon.pc > [32/70] valac: libdiodon/clipboard-configuration.vala > libdiodon/clipboard-item.vala libdiodon/clipboard-manager.vala > libdiodon/clipboard-menu-item.vala libdiodon/clipboard-menu.vala > libdiodon/clipboard-type.vala libdiodon/controller.vala > libdiodon/file-clipboard-item.vala libdiodon/image-clipboard-item.vala > libdiodon/preferences-view.vala libdiodon/primary-clipboard-manager.vala > libdiodon/text-clipboard-item.vala libdiodon/utility.vala > libdiodon/zeitgeist-clipboard-storage.vala -> _build_/libdiodon/diodon.h > _build_/libdiodon/diodon.vapi _build_/libdiodon/Diodon-1.0.gir > _build_/libdiodon/diodon.deps _build_/libdiodon/clipboard-configuration.c > _build_/libdiodon/clipboard-item.c _build_/libdiodon/clipboard-manager.c > _build_/libdiodon/clipboard-menu-item.c _build_/libdiodon/clipboard-menu.c > _build_/libdiodon/clipboard-type.c _build_/libdiodon/controller.c > _build_/libdiodon/file-clipboard-item.c > _build_/libdiodon/image-clipboard-item.c _build_/libdiodon/preferences-view.c > _build_/libdiodon/primary-clipboard-manager.c > _build_/libdiodon/text-clipboard-item.c _build_/libdiodon/utility.c > _build_/libdiodon/zeitgeist-clipboard-storage.c > [33/70] intltool: plugins/indicator/indicator.plugin.in -> > _build_/plugins/indicator/indicator.plugin > [34/70] intltool: _build_/data/net.launchpad.Diodon.gschema.xml.in -> > _build_/data/net.launchpad.Diodon.gschema.xml > [35/70] glib_validate_schema: _build_/data/net.launchpad.Diodon.gschema.xml > -> _build_/data/net.launchpad.Diodon.gschema.xml.valid > /<>/libdiodon/utility.vala:151.40-151.63: warning: > Gdk.Screen.get_active_window has been deprecated since 3.22 > /<>/libdiodon/utility.vala:153.43-153.55: warning: Gdk.X11Window > has been deprecated since vala-0.24. Use Gdk.X11.Window > /<>/libdiodon/zeitgeist-clipboard-storage.vala:33.6-33.42: > warning: DBus methods are recommended to throw at least `GLib.Error' or > `GLib.DBusError, GLib.IOError' > /<>/libdiodon/zeitgeist-clipboard-storage.vala:528.40-528.64: > warning: GLib.DateTime.from_timeval_utc has been deprecated since 2.62 > /<>/libdiodon/zeitgeist-clipboard-storage.vala:371.36-371.42: > warning: GLib.TimeVal has been deprecated since 2.62 > /<>/libdiodon/primary-clipboard-manager.vala:88.33-88.58: > warning: Gdk.Display.get_device_manager has been deprecated since 3.20. > /<>/libdiodon/primary-clipboard-manager.vala:88.33-88.79: > warning: Gdk.DeviceManager.get_client_pointer has been deprecated since 3.20 > /<>/libdiodon/clipboard-menu.vala:104.13-104.17: warning: > Gtk.Menu.popup has been deprecated since 3.22 > /<>/libdiodon/clipboard-menu.vala:72.43-72.59: warning: > Gtk.ImageMenuItem
Bug#951918: django-housekeeping: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Source: django-housekeeping Version: 1.1-1.1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py config > running config > I: pybuild base:217: python3.7 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.8 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/tests.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/models.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/toposort.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/task.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/run.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > copying django_housekeeping/report.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping > creating > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management > copying django_housekeeping/management/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management > creating > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands > copying django_housekeeping/management/commands/__init__.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands > copying django_housekeeping/management/commands/housekeeping.py -> > /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/tests.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/models.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/__init__.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/toposort.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/task.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/run.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > copying django_housekeeping/report.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping > creating > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management > copying django_housekeeping/management/__init__.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management > creating > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands > copying django_housekeeping/management/commands/__init__.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands > copying django_housekeeping/management/commands/housekeeping.py -> > /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:217: cd > /<>/.pybuild/cpython3_3.8_django-housekeeping/build; python3.8 > -m unittest discover -v > test_skipstage (django_housekeeping.tests.TestDependencies) ... ERROR > test_run (django_housekeeping.tests.TestHousekeeping) ... ERROR > test_report (django_housekeeping.tests.TestReport) ... ERROR > test_real (django_housekeeping.tests.TestToposort) ... ok > test_simple (django_housekeeping.tests.TestToposort) ... ok > test_stage_without_tasks (django_housekeeping.tests.TestToposort) ... ok > >
Bug#951940: open-vm-tools: FTBFS: ld: cannot find -llzma
Source: open-vm-tools Version: 2:11.0.5-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=link gcc -fPIC > -Wno-error=deprecated-declarations -Wno-error=address-of-packed-member -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Werror -Wno-pointer-sign -Wno-unused-value > -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized > -Wno-deprecated-declarations -Wno-unused-const-variable > -Wno-unused-but-set-variable -Wl,-z,relro -o VGAuthService > VGAuthService-main.o VGAuthService-fileLogger.o VGAuthService-gio.o > VGAuthService-log.o VGAuthService-servicePosix.o VGAuthService-signalSource.o > VGAuthService-alias.o VGAuthService-file.o VGAuthService-filePosix.o > VGAuthService-netPosix.o VGAuthService-proto.o VGAuthService-random.o > VGAuthService-saml-xmlsec1.o VGAuthService-service.o VGAuthService-ticket.o > VGAuthService-verify.o VGAuthService-audit.o VGAuthService-certverify.o > VGAuthService-i18n.o VGAuthService-prefs.o VGAuthService-usercheck.o > VGAuthService-VGAuthLog.o VGAuthService-VGAuthUtil.o VGAuthService-vmxlog.o > -lglib-2.0 -lgthread-2.0 -pthread -lglib-2.0 -L/usr/lib/x86_64-linux-gnu > -lxmlsec1-openssl -lxmlsec1 -lz -llzma -licui18n -licuuc -licudata -ldl > -lxslt -lxml2 -lm -lssl -lcrypto -lssl -lcrypto -lssl -lcrypto > libtool: link: gcc -fPIC -Wno-error=deprecated-declarations > -Wno-error=address-of-packed-member -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Werror -Wno-pointer-sign -Wno-unused-value > -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized > -Wno-deprecated-declarations -Wno-unused-const-variable > -Wno-unused-but-set-variable -Wl,-z -Wl,relro -o VGAuthService > VGAuthService-main.o VGAuthService-fileLogger.o VGAuthService-gio.o > VGAuthService-log.o VGAuthService-servicePosix.o VGAuthService-signalSource.o > VGAuthService-alias.o VGAuthService-file.o VGAuthService-filePosix.o > VGAuthService-netPosix.o VGAuthService-proto.o VGAuthService-random.o > VGAuthService-saml-xmlsec1.o VGAuthService-service.o VGAuthService-ticket.o > VGAuthService-verify.o VGAuthService-audit.o VGAuthService-certverify.o > VGAuthService-i18n.o VGAuthService-prefs.o VGAuthService-usercheck.o > VGAuthService-VGAuthLog.o VGAuthService-VGAuthUtil.o VGAuthService-vmxlog.o > -pthread -lgthread-2.0 -lglib-2.0 -L/usr/lib/x86_64-linux-gnu > /usr/lib/x86_64-linux-gnu/libxmlsec1-openssl.so > /usr/lib/x86_64-linux-gnu/libxmlsec1.so -lz -llzma -licui18n -licuuc > -licudata -ldl -lxslt -lxml2 -lm -lssl -lcrypto -pthread > /usr/bin/ld: cannot find -llzma > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/open-vm-tools_11.0.5-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.
