Bug#917656: libnet-server-mail-perl: FTBFS (failing tests)
Le 29/12/2018 à 22:39, Santiago Vila a écrit : > Package: src:libnet-server-mail-perl > Version: 0.25-4 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...] > ok 10 > ok > # Error: Can't call method "peerhost" on an undefined value at t/starttls.t > line 131. > # kill 9, 1658 (server) Hi all, SSL randomly timeout error is back. Do I have to disable the relevant test ?
Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64
On Wed, Dec 12, 2018 at 01:56:11PM +0100, Andreas Beckmann wrote:
> You you get the compile flags from Kbuild, or do you reinvent them on
> your own?
---end quoted text---
This is the DKMS build line:
MAKE[0]="cd ${dkms_tree}/sl-modem/#MODULE_VERSION#/build; make -C drivers USB=1
KERNEL_DIR=$kernel_source_dir KERNEL_VER=$kernelver; make -C ungrab-winmodem
KERNEL_DIR=$kernel_source_dir KERNEL_VER=$kernelver; cd .."
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761
8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
signature.asc
Description: PGP signature
Bug#895500: marked as done (ruby-slim FTBFS with ruby-tilt 2.0.8-1)
Your message dated Sun, 30 Dec 2018 07:04:11 + with message-id and subject line Bug#895500: fixed in ruby-slim 4.0.1-1 has caused the Debian Bug report #895500, regarding ruby-slim FTBFS with ruby-tilt 2.0.8-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 895500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-slim Version: 3.0.7-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-slim.html ... 1) Error: TestSlimEmbeddedEngines#test_render_with_builder: NameError: undefined local variable or method `xml' for # (__TEMPLATE__):3:in `block in singleton class' (__TEMPLATE__):-2:in `instance_eval' (__TEMPLATE__):-2:in `singleton class' (__TEMPLATE__):-5:in `__tilt_47056743556540' /usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in `call' /usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in `evaluate' /usr/lib/ruby/vendor_ruby/tilt/template.rb:109:in `render' /build/1st/ruby-slim-3.0.7/test/core/helper.rb:24:in `render' /build/1st/ruby-slim-3.0.7/test/core/helper.rb:47:in `assert_html' /build/1st/ruby-slim-3.0.7/test/core/test_embedded_engines.rb:102:in `test_render_with_builder' /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map' /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run' /usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun' 281 runs, 425 assertions, 0 failures, 1 errors, 0 skips /usr/lib/ruby/vendor_ruby/rake/testtask.rb:130:in `block (3 levels) in define': Command failed with status (1): [ruby -w -I"lib:lib:test/core" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/core/test_code_blocks.rb" "test/core/test_code_escaping.rb" "test/core/test_code_evaluation.rb" "test/core/test_code_output.rb" "test/core/test_code_structure.rb" "test/core/test_commands.rb" "test/core/test_embedded_engines.rb" "test/core/test_encoding.rb" "test/core/test_erb_converter.rb" "test/core/test_html_attributes.rb" "test/core/test_html_escaping.rb" "test/core/test_html_structure.rb" "test/core/test_parser_errors.rb" "test/core/test_pretty.rb" "test/core/test_ruby_errors.rb" "test/core/test_slim_template.rb" "test/core/test_tabs.rb" "test/core/test_text_interpolation.rb" "test/core/test_thread_options.rb" "test/core/test_unicode.rb" ] (RuntimeError) from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:57:in `sh' from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:105:in `ruby' from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:117:in `block (2 levels) in define' from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:59:in `verbose' from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:111:in `block in define' from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `block in execute' from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `each' from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `execute' from /usr/lib/ruby/vendor_ruby/rake/task.rb:213:in `block in invoke_with_call_chain' from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize' from /usr/lib/ruby/vendor_ruby/rake/task.rb:193:in `invoke_with_call_chain' from /usr/lib/ruby/vendor_ruby/rake/task.rb:237:in `block in invoke_prerequisites' from
Processed: tagging 915584
Processing commands for cont...@bugs.debian.org: > tags 915584 + help Bug #915584 [dicoweb] dicoweb: fails to install with python 3.7 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 915584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912398: marked as done (ruby-loofah: CVE-2018-16468)
Your message dated Sun, 30 Dec 2018 07:04:04 + with message-id and subject line Bug#912398: fixed in ruby-loofah 2.2.3-1 has caused the Debian Bug report #912398, regarding ruby-loofah: CVE-2018-16468 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 912398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-loofah Version: 2.2.2-1 Severity: important Tags: security upstream Forwarded: https://github.com/flavorjones/loofah/issues/154 Hi, The following vulnerability was published for ruby-loofah. CVE-2018-16468[0]: | In the Loofah gem for Ruby, through v2.2.2, unsanitized JavaScript may | occur in sanitized output when a crafted SVG element is republished. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-16468 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16468 [1] https://github.com/flavorjones/loofah/issues/154 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ruby-loofah Source-Version: 2.2.3-1 We believe that the bug you reported is fixed in the latest version of ruby-loofah, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated ruby-loofah package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 30 Dec 2018 15:46:23 +0900 Source: ruby-loofah Binary: ruby-loofah Architecture: source Version: 2.2.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Hideki Yamane Description: ruby-loofah - manipulation and transformation of HTML/XML documents and fragmen Closes: 912398 Changes: ruby-loofah (2.2.3-1) unstable; urgency=medium . * Team upload . * New upstream version 2.2.3 (Closes: #912398) (CVE-2018-16468) * debian/watch - update to use gemwatch.debian.net * debian/control - set Standards-Version: 4.3.0 - use dh12 * debian/compat - drop it Checksums-Sha1: bfd1ab97e4953db2ec41e59a32e369f151674729 2194 ruby-loofah_2.2.3-1.dsc d4fd14de1fe1674639b21740e716decb00c2bae2 63626 ruby-loofah_2.2.3.orig.tar.gz 02dd5d67af5803bee4e9653473a08760d86de2c0 3320 ruby-loofah_2.2.3-1.debian.tar.xz a2d74f1617c0c576893de71a2457efb5d767b06e 9149 ruby-loofah_2.2.3-1_amd64.buildinfo Checksums-Sha256: d0ca4e240151ac9bc929b80bf85616bdc78459b87b79183e91b86e04ab796695 2194 ruby-loofah_2.2.3-1.dsc 522b20f21123e5275e620e6590f549acca442da34c647a1509fafb3248547a50 63626 ruby-loofah_2.2.3.orig.tar.gz 92dad8a6a76eddc984a58e73e61f0d286183970a19774b8dd7dd1ea4609a2eee 3320 ruby-loofah_2.2.3-1.debian.tar.xz 57d01d085ae1f32cda5dab184404412d3d75396e15c0ac1dc2fe208aa627317e 9149 ruby-loofah_2.2.3-1_amd64.buildinfo Files: 92a61d4d1f24b3e543810c8b1f546a85 2194 ruby optional ruby-loofah_2.2.3-1.dsc 57080866881ec74e76ae01ffa8bfec2e 63626 ruby optional ruby-loofah_2.2.3.orig.tar.gz ca0a5aa92bcbbbe455cec3e2f7a0ef7e 3320 ruby optional ruby-loofah_2.2.3-1.debian.tar.xz 433f32bf142b1489b1716402bc683f6a 9149 ruby optional ruby-loofah_2.2.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAlwoajoACgkQXTKNCCqq sUAbKA/8CNtg3L2XspQcRDTAYJOnClU6pE0Yfbe5w8zYeLnAWZLoBRea3n4QilV2 9tRfJH0IlcOVvLXUlMHUygjuGmcJrz1NCSF+RDz2y79tTnbcA/Y67c3nbjfxZb0h 8V3vDZXNTKEjnsDOvPWA3MQsB0oJyWSF0jmbOqh+93pjWR02WRVWSXhyOTZav5hz mZ9xwkmiByTkYajRK5LyPZvdLxipfkB2OJZvWDjHtOfaKUVzmrv5Er7Ypo7aK5gJ cj9TxqlHWgo2gbb43K75m1vDPNhWk7GeQJCdqXPUAoQOmWHGdiQuX/qHVhcYM6Dj IKgSXZgQ4eQT1yPskblzwLN/2gmlFjmpccZfbkCQRxvCrgX5WZFmlyru69R2IwER AuCeqOvtUkXwO1WedMcpMWaGhtHb1bL7tAFzECpj6jZVe4Vi2DgAP2X8capY+Rs9 4Zj+EmCeFDEKttgSPS0xAUeLyQU2A/XOTHZv6k4CVPa9w8DA8xkmadoU4iMuEo9b H1Y16gpv3D5JkOGJPbYXwyZPfkF0jTGrTVCxoUZ9aUDS2n2QFWcUrpLLLRdunMab 2PHCbj/8l4sIByNjiGqSnkgALkRR168e3VUbOKBhETlBX9ADCDLzMCz0YRrikfhI
Processed: tagging 916034
Processing commands for cont...@bugs.debian.org: > tags 916034 + help Bug #916034 [sl-modem-dkms] sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 916034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917661: marked as done (ryu: FTBFS: tests failed)
Your message dated Sun, 30 Dec 2018 06:20:20 +
with message-id
and subject line Bug#917661: fixed in ryu 4.26+dfsg1-3
has caused the Debian Bug report #917661,
regarding ryu: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ryu
Version: 4.26+dfsg1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ==
> ERROR: Failure: AttributeError ('functools.partial' object has no attribute
> '__qualname__')
> --
> 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 417, in
> loadTestsFromName
> addr.filename, addr.module)
> 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 "/usr/lib/python3.7/imp.py", line 234, in load_module
> return load_source(name, filename, file)
> File "/usr/lib/python3.7/imp.py", line 171, in load_source
> module = _load(spec)
> File "", line 696, in _load
> File "", line 677, in _load_unlocked
> File "", line 728, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/<>/ryu-4.26+dfsg1/ryu/tests/unit/ofproto/test_parser.py",
> line 311, in
> _add_tests()
> File "/<>/ryu-4.26+dfsg1/ryu/tests/unit/ofproto/test_parser.py",
> line 308, in _add_tests
> set(unittest.defaultTestLoader.getTestCaseNames(Test_Parser)))
> File "/usr/lib/python3.7/unittest/loader.py", line 235, in getTestCaseNames
> testFnNames = list(filter(shouldIncludeMethod, dir(testCaseClass)))
> File "/usr/lib/python3.7/unittest/loader.py", line 232, in
> shouldIncludeMethod
> fullName = '%s.%s' % (testCaseClass.__module__, testFunc.__qualname__)
> AttributeError: 'functools.partial' object has no attribute '__qualname__'
>
> --
> Ran 121541 tests in 47.838s
>
> FAILED (SKIP=2, errors=1)
> make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/ryu_4.26+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.
--- End Message ---
--- Begin Message ---
Source: ryu
Source-Version: 4.26+dfsg1-3
We believe that the bug you reported is fixed in the latest version of
ryu, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated ryu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Dec 2018 06:01:35 +0100
Source: ryu
Binary: python-ryu-doc python3-ryu ryu-bin
Architecture: source all
Version: 4.26+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Description:
python-ryu-doc - software defined networking framework (ryu do
Bug#917661: Bug #917661 in ryu marked as pending
Control: tag -1 pending Hello, Bug #917661 in ryu reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/ryu/commit/b58d25be46593b12f606b8bee6293c29e00a02f7 * Removed Python 2 support. * Add fix-ut-when-running-in-python-3.7-env.patch (Closes: #917661). (this message was generated automatically) -- Greetings https://bugs.debian.org/917661
Processed: Bug #917661 in ryu marked as pending
Processing control commands: > tag -1 pending Bug #917661 [src:ryu] ryu: FTBFS: tests failed Added tag(s) pending. -- 917661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911869: marked as done (ruby-sinatra-contrib FTBFS: tests fail during dh_ruby --install)
Your message dated Sun, 30 Dec 2018 05:49:31 +
with message-id
and subject line Bug#911869: fixed in ruby-sinatra-contrib 2.0.5-1
has caused the Debian Bug report #911869,
regarding ruby-sinatra-contrib FTBFS: tests fail during dh_ruby --install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
911869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sinatra-contrib
Version: 1.4.7-1
Severity: serious
Tags: ftbfs
ruby-sinatra-contrib fails to build from source. Apparently it runs
tests during dh_ruby --install and fails doing so:
| Failures:
|
| 1) Sinatra::Cookies include? checks response cookies
| Failure/Error: jar.should include(:foo)
|
|expected {"foo" => "bar"} to include :foo
|Diff:
|@@ -1,2 +1,2 @@
|-[:foo]
|+"foo" => "bar",
| # ./spec/cookies_spec.rb:553:in `block (3 levels) in '
|
| 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
/build/1st/ruby-sinatra-contrib-1.4.7/spec/capture_spec.rb:26:in `block (3
levels) in '.
|
| `failure_message_for_should` is deprecated. Use `failure_message` instead.
Called from /build/1st/ruby-sinatra-contrib-1.4.7/spec/decompile_spec.rb:10:in
`block in '.
|
|
| 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 5.13 seconds (files took 1.41 seconds to load)
| 837 examples, 1 failure
|
| Failed examples:
|
| rspec ./spec/cookies_spec.rb:550 # Sinatra::Cookies include? checks response
cookies
|
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install
/build/1st/ruby-sinatra-contrib-1.4.7/debian/ruby-sinatra-contrib returned exit
code 1
| make: *** [debian/rules:4: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
Helmut
--- End Message ---
--- Begin Message ---
Source: ruby-sinatra-contrib
Source-Version: 2.0.5-1
We believe that the bug you reported is fixed in the latest version of
ruby-sinatra-contrib, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hideki Yamane (supplier of updated ruby-sinatra-contrib
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 30 Dec 2018 13:58:53 +0900
Source: ruby-sinatra-contrib
Binary: ruby-sinatra-contrib
Architecture: source
Version: 2.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Hideki Yamane
Description:
ruby-sinatra-contrib - collection of useful extensions to the Sinatra web
framework
Closes: 911869
Changes:
ruby-sinatra-contrib (2.0.5-1) unstable; urgency=medium
.
* Team upload
.
* New upstream version 2.0.5 (Closes: #911869)
* debian/watch
- move to https://gemwatch.debian.net and use version 4
* debian/control
- move Vcs-* to salsa.debian.org
- set Standards-Version: 4.3.0
- use dh12 (set Build-Depends: debhelper (>= 12), debhelper-compat (= 12)
- add "Testsuite: autopkgtest-pkg-ruby"
* debian/compat
- drop it
* debian/copyright
- use https
* debian/patches
- refresh
- add version.patch
* add debian/gitlab-ci.yml
Checksums-Sha1:
5bcd6b6205d457b6d0d0f9378b536f8045336b1f 2427 ruby-sinatra-contrib_2.0.5-1.dsc
4c8bb98cfd6c42b204e32a88b586ebc87ebc0e65 29157
ruby-sinatra-contrib_2.0.5.orig.tar.gz
54bdb3fa46449949476245ff0e1efc74ad503304 4848
ruby-sinatra-contrib_2.0.5-1.debian.tar.xz
74fd78ef84ae7b9ddebe45b7ee51413c916c52c5 10339
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> tags 917717 + fixed
Bug #917717 [src:pylint-django] pylint-django: FTBFS: dh_auto_test: pybuild
--test --test-pytest -i python{version} -p 3.7 returned exit code 13
Added tag(s) fixed.
> --
Stopping processing here.
Please contact me if you need assistance.
--
917717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13
Hi, This is because upstream deleted the "YES" alias from astroid on https://github.com/PyCQA/astroid/commit/36fa294e9b84885d95a03b1fbc07da63e6d6a79b This issue was opened on pylint-django ( https://github.com/PyCQA/pylint-django/issues/201) They resolve the issue adding on setup.py the requirement of astroid == 2.0.4. I've push to salsa a patch adding the 'YES' alias on pylint-django ( https://salsa.debian.org/python-team/modules/pylint-django/commit/c3f38068cda75d4125b4e6274598a8f4acd892bd#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2 ) Cheers -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Bug#917678: marked as done (python-pbr: FTBFS: ImportError: No module named install)
Your message dated Sun, 30 Dec 2018 05:04:07 + with message-id and subject line Bug#917678: fixed in python-pbr 4.2.0-5 has caused the Debian Bug report #917678, regarding python-pbr: FTBFS: ImportError: No module named install to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pbr Version: 4.2.0-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > pyversions: missing X(S)-Python-Version in control file, fall back to > debian/pyversions > pyversions: missing debian/pyversions file, fall back to supported versions > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_test > 'pbr\.tests(?!.*test_packaging\.TestRequirementParsing\.test_requirement_parsing.*)' > + PKGOS_USE_PY2=yes > + PKGOS_USE_PY3=yes > + PKGOS_TEST_PARALLEL=yes > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + [ yes = yes ] > + PYTHONS=2.7 > + [ yes = yes ] > + py3versions -vr > + PYTHON3S=3.7 > + [ yes = no ] > + [ 2.7 = disabled ] > + echo 2.7 > + cut -d. -f1 > + PYMAJOR=2 > + echo ===> Testing with python (python2) > ===> Testing with python (python2) > + [ 2 = 3 ] > + [ 2 = 2 ] > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + rm -rf .stestr > + PYTHON=python2.7 python2-stestr+ runsubunit2pyunit > --subunit > pbr\.tests(?!.*test_packaging\.TestRequirementParsing\.test_requirement_parsing.*) > > = > Failures during discovery > = > --- import errors --- > Failed to import test module: pbr.tests.test_integration > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in > _find_test_path > module = self._get_module_from_name(name) > File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in > _get_module_from_name > __import__(name) > File "pbr/tests/test_integration.py", line 23, in > from pbr.tests import test_packaging > File "pbr/tests/test_packaging.py", line 59, in > import wheel.install > ImportError: No module named install > > Failed to import test module: pbr.tests.test_packaging > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in > _find_test_path > module = self._get_module_from_name(name) > File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in > _get_module_from_name > __import__(name) > File "pbr/tests/test_packaging.py", line 59, in > import wheel.install > ImportError: No module named install > > > The above traceback was encountered during test discovery which imports all > the found test modules in the specified test_path. > > -- > Ran 0 tests in 0.378s > > OK > + python2-stestr slowest > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 3 The full build log is available from: http://aws-logs.debian.net/2018/12/29/python-pbr_4.2.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. --- End Message --- --- Begin Message --- Source: python-pbr Source-Version: 4.2.0-5 We believe that the bug you reported is fixed in the latest version of python-pbr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the main
Bug#917678: Bug #917678 in python-pbr marked as pending
Control: tag -1 pending Hello, Bug #917678 in python-pbr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-pbr/commit/faf5a225ead298247d2c8d38e3b9820b414bdcef * Add patches to fix FTBFS (Closes: #917678): - fix-wheel.install.py-doesnt-exist-anymore.patch - no-WheelFile.zipfile-methode.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/917678
Processed: Bug #917678 in python-pbr marked as pending
Processing control commands: > tag -1 pending Bug #917678 [src:python-pbr] python-pbr: FTBFS: ImportError: No module named install Added tag(s) pending. -- 917678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917749: marked as done (python-periodictable: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives'))
Your message dated Sun, 30 Dec 2018 03:19:44 + with message-id and subject line Bug#917749: fixed in python-periodictable 1.5.0-7 has caused the Debian Bug report #917749, regarding python-periodictable: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives') to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-periodictable Version: 1.5.0-6 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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/python setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/activation.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/fasta.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/plot.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/mass.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/cromermann.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/covalent_radius.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/__init__.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/core.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/crystal_structure.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/constants.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/util.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/density.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/chemicals.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/magnetic_ff.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/formulas.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/nsf.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/xsf.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > running egg_info > creating periodictable.egg-info > writing requirements to periodictable.egg-info/requires.txt > writing periodictable.egg-info/PKG-INFO > writing top-level names to periodictable.egg-info/top_level.txt > writing dependency_links to periodictable.egg-info/dependency_links.txt > writing manifest file 'periodictable.egg-info/SOURCES.txt' > reading manifest file 'periodictable.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'doc' > no previously-included directories found matching 'doc/sphinx/_build' > no previously-included directories found matching 'doc/sphinx/build' > warning: no previously-included files found matching 'build' > warning: no previously-included files found matching 'dist' > warning: no previously-included files found matching '*.pyc' > writing manifest file 'periodictable.egg-info/SOURCES.txt' > copying periodictable/activation.dat -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > creating > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ac.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ag.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/al.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ar.nff ->
Bug#906619: marked as done (netgen builds with -march=native)
Your message dated Sat, 29 Dec 2018 20:28:18 -0600 with message-id <7002159f-729b-fa40-c16f-7d0b1ad1d...@gmail.com> and subject line Bug#906619: fixed in netgen 6.2.1804+dfsg1-2 has caused the Debian Bug report #906619, regarding netgen builds with -march=native to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netgen Version: 6.2.1804+dfsg1-1 Severity: serious -march=native must not be used since the resulting code will only run on machines compatible with whatever buildd built the package. --- End Message --- --- Begin Message --- Source: netgen Source-Version: 6.2.1804+dfsg1-2 Use cmake flag -DUSE_NATIVE_ARCH=OFF to disable -march=native usage--- End Message ---
Bug#917428: [Debian-science-sagemath] Python 2 matplotlib package required for sagemath
> You are right, I didn't notice the new matplotlib2 package and sagemath > failed to build due to the missing matplotlibrc in python-matplotlib-data. this should be fixed, does sagemath build fine now? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#907998: gimp: Gimp does not load or crashes quickly
On Tue, Sep 4, 2018 at 7:57 PM Michael Biebl wrote: > On 9/5/18 01:08, Attila Kinali wrote: > > Package: gimp > > Version: 2.10.6-2 > > Severity: grave > > Justification: renders package unusable > > > > Hi, > > > > No matter what I do, Gimp does not load properly. Most times it > > just gets stuck on some routine on boot up. If it successfully > > loads, then it crashes within a few operations. There does not > > seem a pattern, at least not one that I could descern. > > > > When it crashes, what's the output on stdout/stderr? There has been no reply in nearly 3 months. Therefore, we will be closing this bug soon since there is not enough information for us to be able to do anything here. Thanks, Jeremy Bicha
Bug#917598: marked as done (petsc4py FTBFS error: ‘SNESTEST’ undeclared)
Your message dated Sun, 30 Dec 2018 01:50:56 + with message-id and subject line Bug#917598: fixed in petsc4py 3.10.0-4 has caused the Debian Bug report #917598, regarding petsc4py FTBFS error: ‘SNESTEST’ undeclared to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: petsc4py version: 3.10.0-2 severity: serious While trying to get the petsc/slepc/etc stack in raspbian buster into a consistent state I ran into the following error with petsc4py. I was also able to reproduce this in a Debian sid amd64 environment, so it's not raspbian specific. mpicc -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DPETSC_DIR=/usr/lib/petscdir/petsc3.10/arm-linux-gnueabihf-real -I/usr/include/scotch -I/usr/include/hdf5/openmpi -I/usr/include/hypre -I/usr/include/superlu-dist -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/lib/petscdir/petsc3.10/arm-linux-gnueabihf-real/include -Isrc/include -I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 -c src/PETSc.c -o build/temp.linux-armhf-2.7/src/PETSc.o In file included from src/PETSc.c:4: src/petsc4py.PETSc.c: In function 'initPETSc': src/petsc4py.PETSc.c:284319:43: error: 'SNESTEST' undeclared (first use in this function); did you mean 'SNESType'? __pyx_t_7 = __pyx_f_8petsc4py_5PETSc_S_(SNESTEST); if (unlikely(!__pyx_t_7)) __PYX_ERR(37, 7, __pyx_L1_error) ^~~~ SNESType src/petsc4py.PETSc.c:284319:43: note: each undeclared identifier is reported only once for each function it appears in error: command 'mpicc' failed with exit status 1 Searching for SNESTEST on codesearch.debian.net reveals the following in the dolfin changelog. * create patch PETSc_3.10_SNESTEST_removed.patch to work with *PETSc 3.10 (SNESTEST has been removed). Thanks Jed Brown. Presumablly a similar fix is needed in petsc4py. * --- End Message --- --- Begin Message --- Source: petsc4py Source-Version: 3.10.0-4 We believe that the bug you reported is fixed in the latest version of petsc4py, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated petsc4py package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Dec 2018 02:03:07 +0100 Source: petsc4py Binary: python-petsc4py python3-petsc4py python3-petsc4py-real python3-petsc4py-complex python-petsc4py-docs Architecture: source Version: 3.10.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Description: python-petsc4py - Python 2 bindings for PETSc libraries python-petsc4py-docs - Python bindings for PETSc libraries: documentation and examples python3-petsc4py - Python 3 bindings for PETSc libraries python3-petsc4py-complex - Python 3 bindings for PETSc libraries (complex numbers) python3-petsc4py-real - Python 3 bindings for PETSc libraries (real numbers) Closes: 917598 Changes: petsc4py (3.10.0-4) unstable; urgency=medium . * force regeneration of cython .c files (--force option for build [build_src] action). Closes: #917598. Checksums-Sha1: 1692df5c2e66331412cd318eae5b165f7a220104 2662 petsc4py_3.10.0-4.dsc 81a9e106a442ec9caeb7887fe472bbbf4c44ef2f 10392 petsc4py_3.10.0-4.debian.tar.xz Checksums-Sha256: 9645d26828374b01b21b124c67bde2beb391f9fce68938ab6808489f2b360953 2662 petsc4py_3.10.0-4.dsc d5a6bd7215e5c45076a3b8d2aa6bbb7623d34908f2023a2af89782f14055 10392 petsc4py_3.10.0-4.debian.tar.xz Files: 080a8ba5177c39e204b8515b997a9995 2662 python optional petsc4py_3.10.0-4.dsc 3eb8d0e09c9cd9bbd76db547748e5726 10392 python optional petsc4py_3.10.0-4.debian.tar.xz -BEGIN PGP SIGNATURE-
Processed: reassign 917719 to src:t-coffee, forcibly merging 917143 917719
Processing commands for cont...@bugs.debian.org: > reassign 917719 src:t-coffee 12.00.7fb08c2-1 Bug #917719 [t-coffee] libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 Bug reassigned from package 't-coffee' to 'src:t-coffee'. No longer marked as found in versions t-coffee/12.00.7fb08c2-1. Ignoring request to alter fixed versions of bug #917719 to the same values previously set Bug #917719 [src:t-coffee] libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 Marked as found in versions t-coffee/12.00.7fb08c2-1. > forcemerge 917143 917719 Bug #917143 [src:t-coffee] t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP Bug #917719 [src:t-coffee] libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 Severity set to 'normal' from 'serious' Added indication that 917719 affects libbio-tools-run-alignment-tcoffee-perl Bug #917143 [src:t-coffee] t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP Added tag(s) buster and sid. Merged 917143 917719 > thanks Stopping processing here. Please contact me if you need assistance. -- 917143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917143 917719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)
On 2018-12-23 01:14, Aurelien Jarno wrote: > control: reassign -1 nocache > control: tag -1 + patch > > On 2018-12-14 07:44, Aurelien Jarno wrote: > > control: forwarded -1 https://github.com/Feh/nocache/issues/34 > > > > On 2018-12-14 13:33, Paul Wise wrote: > > > Package: nocache/1.0-1,libc6/2.28-2 > > > Severity: critical > > > Justification: breaks unrelated software > > > Usertags: hang > > > > > > The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs, > > > when run under it (but not all of them), hang in a call to read/futex: > > > > I haven't looked at it in details, but at least accorded to the upstream > > bug, it seems to be an issue on the nocache side: > > > > https://github.com/Feh/nocache/issues/34 > > There is now an upstream commit fixing the issue on the nocache side: > > https://github.com/Feh/nocache/commit/e4e77a48528739188dccbdbd8b4d2d2d49aa0d99 > And a new upstream version 1.1 which includes this patch. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Processed (with 1 error): Re: Bug#917719: libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2
Processing control commands: > reassign -1 t-coffee 12.00.7fb08c2-1 Bug #917719 [src:libbio-tools-run-alignment-tcoffee-perl] libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 Bug reassigned from package 'src:libbio-tools-run-alignment-tcoffee-perl' to 't-coffee'. No longer marked as found in versions libbio-tools-run-alignment-tcoffee-perl/1.7.4-1. Ignoring request to alter fixed versions of bug #917719 to the same values previously set Bug #917719 [t-coffee] libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 Marked as found in versions t-coffee/12.00.7fb08c2-1. > forcemerge 917143 -1 Bug #917143 [src:t-coffee] t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP Unable to merge bugs because: package of #917719 is 't-coffee' not 'src:t-coffee' Failed to forcibly merge 917143: Did not alter merged bugs. -- 917143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917143 917719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917719: libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2
Control: reassign -1 t-coffee 12.00.7fb08c2-1 Control: forcemerge 917143 -1 On Sat, 29 Dec 2018 23:06:16 +0100, Lucas Nussbaum wrote: > Source: libbio-tools-run-alignment-tcoffee-perl > Version: 1.7.4-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: buster sid > Usertags: ftbfs-20181229 ftbfs-buster > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. That's #917143 in t-coffee which affects libbio-tools-run-alignment-tcoffee-perl Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Rolling Stones: Out-of-time signature.asc Description: Digital Signature
Bug#917771: python-pywebview: Incomplete debian/copyright?
Source: python-pywebview Version: 2.2.1+dfsg-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Jochen Sprickerhof , ftpmas...@debian.org Hi, I just ACCEPTed python-pywebview from NEW but noticed it was missing attribution in debian/copyright for at least examples/todos/README. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. (Please also clarify in debian/rules why you disable the testsuite there.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#917628: marked as done (poezio: please drop the tight dependency on python3.6)
Your message dated Sun, 30 Dec 2018 00:19:33 + with message-id and subject line Bug#917628: fixed in poezio 0.12.1-2 has caused the Debian Bug report #917628, regarding poezio: please drop the tight dependency on python3.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: poezio Version: 0.12.1-1 Severity: serious Control: block 916817 by -1 Dear maintainer, poezio has a dependency on python3.6:any, python3:any most likely caused by a shabang in /usr/bin having python3.6 in it instead of just python3. Usually this is taken care of by pybuild, which you are not using. If you can't move to the pybuild build system, then please consider adding a override_dh_python3 to specify --shebang=/usr/bin/python3 to force a shebang rewrite at the end of the build. If you are unhappy about both the solution, then please just issue a rebuild, which will cause the dependency to change to python3.7, bearing in mind that you'll most likely get a similar bug next year while we are moving to python 3.8. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: poezio Source-Version: 0.12.1-2 We believe that the bug you reported is fixed in the latest version of poezio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. W. Martin Borgert (supplier of updated poezio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Dec 2018 23:07:38 + Source: poezio Binary: poezio python3-poezio-poopt Architecture: source all amd64 Version: 0.12.1-2 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: W. Martin Borgert Description: poezio - Console-based XMPP client python3-poezio-poopt - Console-based XMPP client (binary module) Closes: 917628 Changes: poezio (0.12.1-2) unstable; urgency=medium . * use pybuild to drop tight dependency on Python 3.6 (Closes: #917628) Checksums-Sha1: efda2905d3da5b054b79f2b00703881bd7c27508 2164 poezio_0.12.1-2.dsc 74f2aa650490d5fb614ee972911408866ad67628 7540 poezio_0.12.1-2.debian.tar.xz 70ef1162e42e59fd46d521cc4c27280d7b1e1cff 612420 poezio_0.12.1-2_all.deb 22812b247367135fdc1abb9dbad74f07f7260037 8330 poezio_0.12.1-2_amd64.buildinfo 385d372a9cb1a1b04d1a6291abb246ec7d888d18 16608 python3-poezio-poopt-dbgsym_0.12.1-2_amd64.deb 9844d1a9eaefea2e37d525f34b94d3f06af1b6b3 13512 python3-poezio-poopt_0.12.1-2_amd64.deb Checksums-Sha256: d24f12a2b8473d1387b7340eec8f694b3cf916150c841db9644db23ed0aa39b9 2164 poezio_0.12.1-2.dsc 8531c80b2dd0c3cca889bad05b8bed047561abdc07d0c68be2a22117df4a94b7 7540 poezio_0.12.1-2.debian.tar.xz 4c54937965288e3ceb6815b6987fb42bd591c7283d255100f9bf63dbd86c3c78 612420 poezio_0.12.1-2_all.deb 90b9c7a10796b9d9fa077a9095f20d1137a144e16b12860d7f65d02af2441fe8 8330 poezio_0.12.1-2_amd64.buildinfo c708f353f19e53143e61ee8163bbf04967f8b98b3b3cb6225bec2bea99c34a22 16608 python3-poezio-poopt-dbgsym_0.12.1-2_amd64.deb 219ae1a2503bb9fd65da27c20b56509a7fedb63a63bd425a005ecba392b57775 13512 python3-poezio-poopt_0.12.1-2_amd64.deb Files: 538ed334d02db1890274c129bf93cd7a 2164 net optional poezio_0.12.1-2.dsc 2f4fd8d70babfde722ce797726bf3364 7540 net optional poezio_0.12.1-2.debian.tar.xz 6a827ee7250c206e762d31e12262f0eb 612420 net optional poezio_0.12.1-2_all.deb 37b47d5ddd558b57dfd89711d862062a 8330 net optional poezio_0.12.1-2_amd64.buildinfo 6acb534c2041c5d03c3a036fb06fbf9c 16608 debug optional python3-poezio-poopt-dbgsym_0.12.1-2_amd64.deb 06f7f61e69359684acd0a67ad746b117 13512 net optional python3-poezio-poopt_0.12.1-2_amd64.deb -BEGIN PGP
Processed: Re: Bug#917598 closed by Drew Parsons (Bug#917598: fixed in petsc4py 3.10.0-3)
Processing commands for cont...@bugs.debian.org:
> Found 917598 3.10.0-3
Bug #917598 {Done: Drew Parsons } [petsc4py] petsc4py
FTBFS error: ‘SNESTEST’ undeclared
There is no source info for the package 'petsc4py' at version '3.10.0-3' with
architecture ''
Unable to make a source version for version '3.10.0-3'
Marked as found in versions 3.10.0-3; no longer marked as fixed in versions
petsc4py/3.10.0-3 and reopened.
> thanks.
Stopping processing here.
Please contact me if you need assistance.
--
917598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#917598: closed by Drew Parsons (Bug#917598: fixed in petsc4py 3.10.0-3)
Found 917598 3.10.0-3 thanks. Unfortunately it seems it still fails with the same error. On 29/12/18 20:21, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the petsc4py package: #917598: petsc4py FTBFS error: ‘SNESTEST’ undeclared It has been closed by Drew Parsons . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Drew Parsons by replying to this email.
Processed: tagging 916415
Processing commands for cont...@bugs.debian.org: > tags 916415 + fixed-upstream Bug #916415 [nocache] nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL) Ignoring request to alter tags of bug #916415 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 916415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917692: [Pkg-electronics-devel] Bug#917692: sdcc: FTBFS: LaTeX Error: File `footnotehyper.sty' not found.
On Sat, Dec 29, 2018 at 10:39:07PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
...
> > ! LaTeX Error: File `footnotehyper.sty' not found.
> >
> > Type X to quit or to proceed,
> > or enter new name. (Default extension: sty)
> >
> > Enter file name:
> > ! Emergency stop.
> >
> >
> > l.22 \usepackage
> > {amstext}^^M
> > No pages of output.
> > Transcript written on sdccman.log.
> > make[1]: *** [Makefile:67: sdccman.dvi] Error 1
Looks like lyx has changed again; we now need a build-dep on
texlive-latex-extra for this (lyx only recommends it).
J.
--
No program done by a hacker will | .''`. Debian GNU/Linux Developer
work unless he is on the system. | : :' : Happy to accept PGP signed
| `. `' or encrypted mail - RSA
| `-key on the keyservers.
Bug#917752: lintian: FTBFS: tests failed
[Adding felix.lech...@lease-up.com to CC] Hi Lucas, Looks like we have a number of issues here. > > +I: changes-upstream-signature-not-missing source: > > public-upstream-key-unusable upstream/signing-key.asc cannot be processed Felix, not sure your MR/branch handles this one? > > -W: debhelper-compat-experimental source: > > package-needs-versioned-debhelper-build-depends 12 I assume it addresses this one in an ongoing/sustainable manner. > > -W: manpages-general: manpage-has-errors-from-man > > usr/share/man/man1/test.1p.gz 14: warning: macro `dep' not defined > > (possibly missing space after `de') I don't recall seeing one for these. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#917654: bacula-doc: FTBFS (LaTeX Error: Missing begin{document})
Control: merge 917654 917735 Hi, I'm sorry for having used your time by not reporting this myself. As far as I can say, one of the last TeX updates introduced this FTBFS. I have yet to find the exact cause. Regards, Carsten
Processed: Re: Bug#917654: bacula-doc: FTBFS (LaTeX Error: Missing begin{document})
Processing control commands:
> merge 917654 917735
Bug #917654 [src:bacula-doc] bacula-doc: FTBFS (LaTeX Error: Missing
begin{document})
Bug #917654 [src:bacula-doc] bacula-doc: FTBFS (LaTeX Error: Missing
begin{document})
Added tag(s) sid and buster.
Bug #917735 [src:bacula-doc] bacula-doc: FTBFS: ! LaTeX Error: Missing
\begin{document}.
Added tag(s) ftbfs.
Merged 917654 917735
--
917654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917654
917735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 912249 is forwarded to https://github.com/flori/file-tail/issues/12
Processing commands for cont...@bugs.debian.org: > forwarded 912249 https://github.com/flori/file-tail/issues/12 Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails Set Bug forwarded-to-address to 'https://github.com/flori/file-tail/issues/12'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917757: node-object-path: FTBFS: tests failed
Source: node-object-path
Version: 0.11.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> mocha test.js -R spec
>
>
> get
> ✓ should return the value using unicode key
> ✓ should return the value using dot in key
> ✓ should return the value under shallow object
> ✓ should work with number path
> ✓ should return the value under deep object
> ✓ should return the value under array
> ✓ should return the value under array deep
> ✓ should return undefined for missing values under object
> ✓ should return undefined for missing values under array
> ✓ should return the value under integer-like key
> ✓ should return the default value when the key doesnt exist
> ✓ should return the default value when path is empty
> ✓ should return the default value when object is null or undefined
> ✓ should not fail on an object with a null prototype
> ✓ should skip non own properties
>
> set
> ✓ should set the value using unicode key
> ✓ should set the value using dot in key
> 1) should set value under shallow object
> 2) should set value using number path
> 3) should set value under deep object
> 4) should set value under array
> 5) should create intermediate objects
> 6) should create intermediate arrays
> ✓ should set value under integer-like key
> ✓ should set value under empty array
>
> push
> 7) should push value to existing array using unicode key
> ✓ should push value to existing array using dot key
> 8) should push value to existing array
> 9) should push value to new array
> 10) should push value to existing array using number path
>
> ensureExists
> 11) should create the path if it does not exists
> ✓ should return the object if path is empty
> ✓ Issue #26
>
> coalesce
> ✓ should return the first non-undefined value
> ✓ should work with falsy values (null, 0, '', false)
> ✓ returns defaultValue if no paths found
> ✓ works with unicode and dot keys
>
> empty
> ✓ should ignore invalid arguments safely
> ✓ should empty each path according to their types
>
> del
> ✓ should work with number path
> 12) should delete deep paths
> ✓ should remove items from existing array
>
> insert
> 13) should insert value into existing array
> 14) should create intermediary array
> 15) should insert in another index
> ✓ should handle sparse array
>
> has
> ✓ should return false for empty object
> ✓ should handle empty paths properly
> ✓ should test under shallow object
> ✓ should work with number path
> ✓ should test under deep object
> ✓ should test value under array
> ✓ should test the value under array deep
> ✓ should test the value under integer-like key
> ✓ should distinct nonexistent key and key = undefined
> ✓ should work with deep undefined/null values
>
> bind object
> ✓ should return the value under shallow object
> 16) should set value under shallow object
> 17) should push value to existing array
> 18) should create the path if it does not exists
> ✓ should return the first non-undefined value
> ✓ should empty each path according to their types
> 19) should delete deep paths
> 20) should insert value into existing array
> ✓ should test under shallow object
>
> Don't access not own properties [default]
> ✓ should not get a not own property
> ✓ should set a not own property on the instance (not the prototype)
> ✓ has should return false on a not own property
> ✓ empty should not empty on a not own property
> ✓ del should not delete not own property
>
> Access own properties [optional]
> ✓ should get a not own property
> ✓ should set a deep not own property on the prototype (if exists)
> ✓ has should return true on a not own property
> ✓ empty should empty a not own property
> ✓ del should delete a not own property
>
>
> 55 passing (37ms)
> 20 failing
>
> 1) set
>should set value under shallow object:
> AssertionError: expected { Object (a, b, ...) } to have deep property
> 'c.m'
> at Context. (test.js:164:30)
> at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
> at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
> at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
&
Bug#917749: python-periodictable: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')
Source: python-periodictable Version: 1.5.0-6 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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/python setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/activation.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/fasta.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/plot.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/mass.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/cromermann.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/covalent_radius.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/__init__.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/core.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/crystal_structure.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/constants.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/util.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/density.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/chemicals.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/magnetic_ff.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/formulas.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/nsf.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > copying periodictable/xsf.py -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > running egg_info > creating periodictable.egg-info > writing requirements to periodictable.egg-info/requires.txt > writing periodictable.egg-info/PKG-INFO > writing top-level names to periodictable.egg-info/top_level.txt > writing dependency_links to periodictable.egg-info/dependency_links.txt > writing manifest file 'periodictable.egg-info/SOURCES.txt' > reading manifest file 'periodictable.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'doc' > no previously-included directories found matching 'doc/sphinx/_build' > no previously-included directories found matching 'doc/sphinx/build' > warning: no previously-included files found matching 'build' > warning: no previously-included files found matching 'dist' > warning: no previously-included files found matching '*.pyc' > writing manifest file 'periodictable.egg-info/SOURCES.txt' > copying periodictable/activation.dat -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable > creating > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ac.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ag.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/al.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ar.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/as.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/at.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/au.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/b.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/ba.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/be.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf/bi.nff -> > /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf > copying periodictable/xsf
Bug#917756: astropy-healpix: FTBFS: tests failed
Source: astropy-healpix Version: 0.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > python3.7 setup.py test -vv --args "-vv" > running test > running install > running build > running build_py > creating build/lib.linux-x86_64-3.7 > creating build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/setup_package.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/healpy.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/__init__.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/core.py -> build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/version.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/high_level.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/conftest.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/_astropy_init.py -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/bench.py -> build/lib.linux-x86_64-3.7/astropy_healpix > creating build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/test_core.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/setup_package.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/six.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/__init__.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/test_high_level.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/test_bench.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/tests/test_healpy.py -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > copying astropy_healpix/interpolation.c -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/_compiler.c -> > build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/_core.c -> build/lib.linux-x86_64-3.7/astropy_healpix > copying astropy_healpix/tests/coveragerc -> > build/lib.linux-x86_64-3.7/astropy_healpix/tests > running build_ext > building 'astropy_healpix._compiler' extension > creating build/temp.linux-x86_64-3.7 > creating build/temp.linux-x86_64-3.7/astropy_healpix > x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.7m -c astropy_healpix/_compiler.c -o > build/temp.linux-x86_64-3.7/astropy_healpix/_compiler.o > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.7/astropy_healpix/_compiler.o > -o > build/lib.linux-x86_64-3.7/astropy_healpix/_compiler.cpython-37m-x86_64-linux-gnu.so > building 'astropy_healpix._core' extension > creating build/temp.linux-x86_64-3.7/cextern > creating build/temp.linux-x86_64-3.7/cextern/astrometry.net > x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/lib/python3/dist-packages/numpy/core/include -Icextern/astrometry.net > -Iastropy_healpix -Icextern/lalsuite -Icextern/numpy > -I/usr/include/python3.7m -c cextern/astrometry.net/bl.c -o > build/temp.linux-x86_64-3.7/cextern/astrometry.net/bl.o -O2 > cextern/astrometry.net/bl.c: In function 'sl_appendvf': > cextern/astrometry.net/bl.c:1218:9: warning: implicit declaration of function > 'vasprintf'; did you mean 'vsprintf'? [-Wimplicit-function-declaration] > if (vasprintf(, format, va) == -1) > ^ > vsprintf > x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/lib/python3/dist-packages/numpy/core/include -Icextern/astrometry.net > -Iastropy_healpix -Icextern/lalsuite -Icextern/numpy > -I/usr/include/python3.7m -c cextern/astrometry.net/healpix-utils.c -o > build/temp.linux-x86_64-3.7/cextern/astrometry.net/healpix-utils.o -
Bug#917755: phpmyadmin: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/test/PMATestCase.php:14
Source: phpmyadmin
Version: 4:4.6.6-5
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> # We exclude:
> # - selenium tests as the setup would be too complex
> # - some network based tests
> LC_ALL=en_US.UTF-8 phpunit --config phpunit.xml.nocoverage --exclude-group
> selenium --exclude-group network
> No headers testing.
> Please install runkit and enable runkit.internal_override!
> PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not
> found in /<>/test/PMATestCase.php:14
> Stack trace:
> #0 /<>/test/classes/AdvisorTest.php(13): require_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(57):
> include_once('/build/phpmyadm...')
> #2 /usr/share/php/PHPUnit/Util/FileLoader.php(45):
> PHPUnit\Util\FileLoader::load('/build/phpmyadm...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(540):
> PHPUnit\Util\FileLoader::checkAndLoad('/build/phpmyadm...')
> #4 /usr/share/php/PHPUnit/Framework/TestSuite.php(618):
> PHPUnit\Framework\TestSuite->addTestFile('/build/phpmyadm...')
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(1137):
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #6 /usr/share/php/PHPUnit/Util/Configuration.php(1003):
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(902):
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #8 /usr/share/php/PHPUnit in /<>/test/PMATestCase.php on line 14
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 255
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/phpmyadmin_4.6.6-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#917763: hoel: FTBFS: dh_auto_configure fails
Source: hoel
Version: 1.4.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>/build/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o
> /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Werror-o
> CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o -c
> /<>/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
> Linking C executable cmTC_2220a
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2220a.dir/link.txt
> --verbose=1
> /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Werror -Wl,-z,relro -Wl,-z,now
> CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o -o cmTC_2220a
> make[3]: Leaving directory '/<>/build/CMakeFiles/CMakeTmp'
> make[2]: Leaving directory '/<>/build/CMakeFiles/CMakeTmp'
>
> File /<>/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
> /* */
> #include
>
> int main(int argc, char** argv)
> {
> (void)argv;
> #ifndef __GNU_LIBRARY__
> return ((int*)(&__GNU_LIBRARY__))[argc];
> #else
> (void)argc;
> return 0;
> #endif
> }
>
> dh_auto_configure: cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu --no-warn-unused-cli .. returned
> exit code 1
> make[1]: *** [debian/rules:24: override_dh_auto_configure] Error 2
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/hoel_1.4.8-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#917748: octave-msh: FTBFS: tests failed
Source: octave-msh
Version: 1.0.10-5
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>/src'
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2 mshm_refine.cc
> -Wl,-z,relro
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2
> mshm_dolfin_read.cc -Wl,-z,relro
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 mshm_refine.cc -o mshm_refine.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 mshm_dolfin_read.cc -o mshm_dolfin_read.o
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -shared
> -Wl,-Bsymbolic -Wdate-time -o mshm_refine.oct mshm_refine.o -Wl,-z,relro
> -L/usr/lib/x86_64-linux-gnu/octave/4.4.1 -L/usr/lib/x86_64-linux-gnu
> -loctinterp -loctave -Wl,-z,relro
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -shared
> -Wl,-Bsymbolic -Wdate-time -o mshm_dolfin_read.oct mshm_dolfin_read.o
> -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/octave/4.4.1
> -L/usr/lib/x86_64-linux-gnu -loctinterp -loctave -Wl,-z,relro
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2
> mshm_dolfin_write.cc -Wl,-z,relro
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 mshm_dolfin_write.cc -o mshm_dolfin_write.o
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -shared
> -Wl,-Bsymbolic -Wdate-time -o mshm_dolfin_write.oct mshm_dolfin_write.o
> -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/octave/4.4.1
> -L/usr/lib/x86_64-linux-gnu -loctinterp -loctave -Wl,-z,relro
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/mshm_dolfin_read.oct
> /<>/./src/mshm_dolfin_write.oct
> /<>/./src/mshm_refine.oct
> /<>/./inst/x86_64-pc-linux-gnu-api-v52
> For information about changes from previous versions of the msh package, run
> 'news msh'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Checking m files ...
> [inst/msh2m_submesh.m]
> >>>>> /<>/inst/msh2m_submesh.m
> * test
> [mesh1] = msh2m_structured_mesh(0:.5:1, 0:.5:1, 1, 1:4, 'left');
> [mesh2] = msh2m_structured_mesh(1:.5:2, 0:.5:1, 1, 1:4, 'left');
> [mesh] = msh2m_join_structured_mesh(mesh1,mesh2,2,4);
> [omesh,nodelist,elementlist] = msh2m_submesh(mesh,[],2);
> p = [1.0 1.0 1.0 1.5 1.5 1.5 2.0
> 2.0 2.0
> 0.0 0.5 1.0 0.0 0.5 1.0 0.0
> 0.5 1.0];
> e = [1 1 2 3 4 6 7 8
> 2 4 3 6 7 9 8 9
> 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0
> 2 5 2 7 5 7 6 6
> 2 0 2 0 0 0 0 0
> 1 2 1 2 2 2 2 2];
> t = [1 2 4 5 2 3 5 6
> 4 5 7 8 4 5 7 8
> 2 3 5 6 5 6 8 9
> 2 2 2 2 2 2 2 2];
> nl = [789 10 11 12 13 14 15];
> el = [9 10 11 12 13 14 15 16];
> toll = 1e-4;
> assert(omesh.p,p,toll);
> assert(omesh.e,e);
> assert(omesh.t,t);
> assert(nodelist,nl);
> assert(elementlist,el);
> * demo
> name = [tmpnam ".geo"];
> fid = fopen (name, "w");
> fputs (fid, "Point(1) = {0, 0, 0, .1};\n");
> fputs (fid, "Point(2) = {1, 0, 0, .1};\n");
> fputs (fid, "Point(3) = {1, 0.5, 0, .1};\n");
> fputs (fid, "Point(4) = {1, 1, 0, .1};\n");
> fputs (fid, "
Bug#917759: openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13
Source: openhft-chronicle-wire Version: 1.1.13-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-wire-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] -< net.openhft:chronicle-wire > >- > [INFO] Building OpenHFT/Chronicle-Wire 1.1.13 > [INFO] ---[ bundle > ]--- > [WARNING] The POM for org.easymock:easymock:jar:debian is missing, no > dependency information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 1.064 s > [INFO] Finished at: 2018-12-29T13:59:39Z > [INFO] > > [ERROR] Failed to execute goal on project chronicle-wire: Could not resolve > dependencies for project net.openhft:chronicle-wire:bundle:1.1.13: Cannot > access central (https://repo.maven.apache.org/maven2) in offline mode and the > artifact org.easymock:easymock:jar:debian has not been downloaded from it > before. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:4: build] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/openhft-chronicle-wire_1.1.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#917750: node-redis: FTBFS: tests failed
Source: node-redis
Version: 0.12.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> NODE_DISABLE_COLORS=1 nodejs test.js
> [redis-server] 31493:C 29 Dec 2018 13:29:06.704 # oO0OoO0OoO0Oo Redis is
> starting oO0OoO0OoO0Oo
> 31493:C 29 Dec 2018 13:29:06.704 # Redis version=5.0.3, bits=64,
> commit=, modified=0, pid=31493, just started
> 31493:C 29 Dec 2018 13:29:06.704 # Configuration loaded
> 31493:M 29 Dec 2018 13:29:06.705 * Running mode=standalone, port=6379.
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING: The TCP backlog setting of 511
> cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower
> value of 128.
> 31493:M 29 Dec 2018 13:29:06.705 # Server initialized
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING overcommit_memory is set to 0!
> Background save may fail under low memory condition. To fix this issue add
> 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the
> command 'sysctl vm.overcommit_memory=1' for this to take effect.
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING you have Transparent Huge Pages
> (THP) support enabled in your kernel. This will create latency and memory
> usage issues with Redis. To fix this issue run the command 'echo never >
> /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your
> /etc/rc.local in order to retain the setting after a reboot. Redis must be
> restarted after THP is disabled.
> 31493:M 29 Dec 2018 13:29:06.705 * Ready to accept connections
> 31493:M 29 Dec 2018 13:29:06.705 * The server is now ready to accept
> connections at /tmp/redis.sock
>
> Connected to 127.0.0.1:6379, Redis server version 5.0.3
>
> Using reply parser javascript
> - ipv4:(node:31487) [DEP0026] DeprecationWarning: util.print is deprecated.
> Use console.log instead.
> Connected to 127.0.0.1:6379, Redis server version 5.0.3
>
> Using reply parser javascript
> - ipv6:Connected to ::1:6379, Redis server version 5.0.3
>
> Using reply parser javascript
> - unix_socket:Connected to /tmp/redis.sock, Redis server version 5.0.3
>
> Using reply parser javascript
> - flushdb: 1 ms
> - incr: 0 ms
> - multi_1: 2 ms
> - multi_2: 0 ms
> - multi_3: 1 ms
> - multi_4: 0 ms
> - multi_5: 1 ms
> - multi_6: 0 ms
> - multi_7: 1 ms
> - multi_exception_1: 1 ms
> - multi_8: 1 ms
> - fwd_errors_1:incoming
> 151 ms
> - eval_1: 5 ms
> - script_load: 0 ms
> - client_list:id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=N db=15
> sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r
> cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0
> multi=-1 qbuf=26 qbuf-free=32742 obl=0 oll=0 omem=0 events=r cmd=client
>
> id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0
> multi=1 qbuf=14 qbuf-free=32754 obl=4 oll=0 omem=0 events=r cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0
> multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client
>
> id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0
> multi=1 qbuf=55 qbuf-free=32713 obl=18 oll=0 omem=0 events=r cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0
> multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client
>
> 1 ms
> - watch_multi: 0 ms
> - watch_transaction: 0 ms
> - detect_buffers: 2 ms
> - socket_nodelay: 2 ms
> - reconnect:reconnecting: { delay: 255, attempt: 2 }
> 257 ms
> - reconnect_select_db_after_pubsub:reconnecting: { delay: 255, attempt: 2 }
> 258 ms
> - select_error_e
Bug#917760: php-zeta-console-tools: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33
Source: php-zeta-console-tools
Version: 1.7-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> phpunit --exclude-group interactive
> PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/argument_test.php(34):
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57):
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45):
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540):
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618):
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137):
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996):
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMEleme in
> /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/php-zeta-console-tools_1.7-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#917762: python-xarray: FTBFS: tests failed
Source: python-xarray Version: 0.11.0-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > for p in python3.7; do \ > PY3VERNUM=`echo $p | sed -e 's/python//' `; \ > pybuild --test --test-pytest -i $p -p $PY3VERNUM ; \ > done > I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_xarray/build; > python3.7 -m pytest > = test session starts > == > platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 > rootdir: /<>, inifile: setup.cfg > collected 6537 items / 1 skipped > > xarray/tests/test_accessors.py . [ > 0%] > .. [ > 1%] > xarray/tests/test_backends.py .. [ > 2%] > [ > 3%] > ..ss [ > 4%] > [ > 5%] > [ > 6%] > ..ss [ > 7%] > [ > 8%] > ..X. [ > 9%] > sss. [ > 11%] > .... [ > 12%] > ..ss [ > 13%] > ...s.. [ > 13%] > xarray/tests/test_backends_api.py . [ > 14%] > xarray/tests/test_backends_file_manager.py . [ > 14%] > xarray/tests/test_backends_locks.py .[ > 14%] > xarray/tests/test_backends_lru_cache.py [ > 14%] > xarray/tests/test_cftime_offsets.py [ > 15%] > [ > 16%] > [ > 17%] > [ > 18%] > [ > 19%] > [ > 20%] > [ > 21%] > [ > 22%] > [ > 23%] > [ > 24%] > [ > 26%] > [ > 27%] > [ > 28%] > [ > 29%] > [ > 30%] > [ > 31%] > [ > 32%] > [ > 33%] > [ > 34%] > [ > 35%] > .[ > 36%] > xarray/tests/test_cftimeindex.py ... [ > 37%] > [ > 38%] > [ > 39%] > [ > 40%] > [ > 41%] > [ > 43%] > .
Bug#917764: postgresql-11: FTBFS: pg_regress: initdb failed
Source: postgresql-11 Version: 11.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>/build/contrib/spi' > make[3]: Nothing to be done for 'all'. > make[3]: Leaving directory '/<>/build/contrib/spi' > rm -rf ./testtablespace > mkdir ./testtablespace > PATH="/<>/build/tmp_install/usr/lib/postgresql/11/bin:$PATH" > LD_LIBRARY_PATH="/<>/build/tmp_install/usr/lib/x86_64-linux-gnu" > ../../../src/test/regress/pg_regress --temp-instance=./tmp_check > --inputdir=/<>/build/../src/test/regress --bindir= > --port=10015 --dlpath=. --max-concurrent-tests=20 --port=10015 > --schedule=/<>/build/../src/test/regress/parallel_schedule > == creating temporary instance== > == initializing database system == > > pg_regress: initdb failed > Examine /<>/build/src/test/regress/log/initdb.log for the reason. > Command was: "initdb" -D > "/<>/build/src/test/regress/./tmp_check/data" --no-clean > --no-sync > "/<>/build/src/test/regress/log/initdb.log" 2>&1 > make[2]: *** [GNUmakefile:132: check] Error 2 The full build log is available from: http://aws-logs.debian.net/2018/12/29/postgresql-11_11.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#917761: php-monolog: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/tests/Monolog/ErrorHandlerTest.php:16
Source: php-monolog
Version: 1.23.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> phpunit --bootstrap autoload.php --include-path src
> PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not
> found in /<>/tests/Monolog/ErrorHandlerTest.php:16
> Stack trace:
> #0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(45):
> PHPUnit\Util\FileLoader::load('/build/php-mono...')
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540):
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-mono...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618):
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-mono...')
> #4 /usr/share/php/PHPUnit/Util/Configuration.php(1137):
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(996):
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(902):
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(173):
> PHPUnit\TextUI\Command->handleArguments(Array)
> #8 /usr/share/php/PHPUnit in
> /<>/tests/Monolog/ErrorHandlerTest.php on line 16
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/php-monolog_1.23.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#917754: statsmodels: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')
Source: statsmodels Version: 0.8.0-7 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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' > Make static directory for images > mkdir -p build/html/_static > # generate the examples rst files > Generating reST from examples folder > #../tools/examples_rst.py > Generating datasets from installed statsmodels.datasets > python3 ../tools/dataset_rst.py > /<>/.pybuild/cpython3_3.7_statsmodels/build/statsmodels/compat/pandas.py:56: > FutureWarning: The pandas.core.datetools module is deprecated and will be > removed in a future version. Please use the pandas.tseries module instead. > from pandas.core import datetools > Generating notebooks from examples/notebooks folder > python3 ../tools/nbgenerate.py --execute=True --allow_errors=True > RUNNING THE L-BFGS-B CODE > >* * * > > Machine precision = 2.220D-16 > N =4 M = 10 > This problem is unconstrained. > > At X0 0 variables are exactly at the bounds > > At iterate0f= 4.23082D+00|proj g|= 4.24640D-03 > > At iterate5f= 4.23081D+00|proj g|= 4.05724D-04 > > At iterate 10f= 4.23081D+00|proj g|= 1.30108D-04 > > At iterate 15f= 4.23080D+00|proj g|= 1.31695D-03 > >* * * > > Tit = total number of iterations > Tnf = total number of function evaluations > Tnint = total number of segments explored during Cauchy searches > Skip = number of BFGS updates skipped > Nact = number of active bounds at final generalized Cauchy point > Projg = norm of the final projected gradient > F = final function value > >* * * > >NTit Tnf Tnint Skip Nact ProjgF > 4 19 23 1 0 0 3.347D-06 4.231D+00 > F = 4.2308031361514127 > > CONVERGENCE: NORM_OF_PROJECTED_GRADIENT_<=_PGTOL > > Cauchytime 0.000E+00 seconds. > Subspace minimization time 0.000E+00 seconds. > Line search time 0.000E+00 seconds. > > Total User time 0.000E+00 seconds. > > RUNNING THE L-BFGS-B CODE > >* * * > > Machine precision = 2.220D-16 > N =5 M = 10 > This problem is unconstrained. > > At X0 0 variables are exactly at the bounds > > At iterate0f= 4.22237D+00|proj g|= 5.01920D-03 > > At iterate5f= 4.22236D+00|proj g|= 2.92744D-04 > > At iterate 10f= 4.22235D+00|proj g|= 2.35973D-04 > > At iterate 15f= 4.22234D+00|proj g|= 1.81119D-03 > > At iterate 20f= 4.22234D+00|proj g|= 4.50080D-05 > >* * * > > Tit = total number of iterations > Tnf = total number of function evaluations > Tnint = total number of segments explored during Cauchy searches > Skip = number of BFGS updates skipped > Nact = number of active bounds at final generalized Cauchy point > Projg = norm of the final projected gradient > F = final function value > >* * * > >NTit Tnf Tnint Skip Nact ProjgF > 5 20 23 1 0 0 4.501D-05 4.222D+00 > F = 4.2223359703293983 > > CONVERGENCE: REL_REDUCTION_OF_F_<=_FACTR*EPSMCH > > Cauchytime 0.000E+00 seconds. > Subspace minimization time 0.000E+00 seconds. > Line search time 0.000E+00 seconds. > > Total User time 0.000E+00 seconds. > > RUNNING THE L-BFGS-B CODE > >* * * > > Machine precision = 2.220D-16 > N =3 M = 12 > This problem is unconstrained. > > At X0 0 variables are exactly at the bounds > > At iterate0f= 4.23082D+00|proj g|= 8.41904D-04 > > At iterate5f= 4.23082D+00|proj g|= 2.53486D-04 > > At iterate 10f= 4.23080D+00|proj g|= 3.19123D-04 > > At iterate 15f= 4.23080D+00|proj g|= 0.0D+00 > >* * * > > Tit = total number of iterations > Tnf = total number of function evaluations > Tnint = total number of segments explored during Cauchy searches > Skip = number of BFGS updates skipped > Nact = number of active bounds at final generalized Cauchy point > Projg = norm of the final projected gradient > F = final function value > >* * * > >NTit Tnf Tnint Skip Nact ProjgF > 3 15 19 1 0 0 0.000D+00
Bug#917758: jabberd2: FTBFS: mysql-related errors
Source: jabberd2 Version: 2.6.1-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>/storage' > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time > -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > libstorage_la-storage.lo `test -f 'storage.c' || echo './'`storage.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time > -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > libstorage_la-object.lo `test -f 'object.c' || echo './'`object.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > authreg_anon.lo authreg_anon.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > authreg_db.lo authreg_db.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > storage_db.lo storage_db.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > storage_fs.lo storage_fs.c > [01m[Kstorage_fs.c:[m[K In function '[01m[K_st_fs_put[m[K': > [01m[Kstorage_fs.c:173:64:[m[K [01;35m[Kwarning: [m[Kcast from > pointer to integer of different size [[01;35m[K-Wpointer-to-int-cast[m[K] > fprintf(f, "%s %d %d\n", key, ot, > ([01;35m[K([m[Kint)val != 0) ? 1 : 0); > > [01;35m[K^[m[K > [01m[Kstorage_fs.c:177:63:[m[K [01;35m[Kwarning: [m[Kcast from > pointer to integer of different size [[01;35m[K-Wpointer-to-int-cast[m[K] > fprintf(f, "%s %d %d\n", key, ot, > [01;35m[K([m[Kint) val); > > [01;35m[K^[m[K > [01m[Kstorage_fs.c:[m[K In function '[01m[K_st_fs_delete[m[K': > [01m[Kstorage_fs.c:383:34:[m[K [01;35m[Kwarning: > [m[K'[01m[K%s[m[K' directive output may be truncated writing up to 255 > bytes into a region of size between 0 and 1023 > [[01;35m[K-Wformat-truncation=[m[K] > snprintf(file, 1024, "%s/[01;35m[K%s[m[K", path, dirent->d_name); > [01;35m[K^~[m[K > In file included from [01m[K/usr/include/stdio.h:873[m[K, > from [01m[K../util/util.h:27[m[K, > from [01m[Kstorage.h:38[m[K, > from [01m[Kstorage_fs.c:36[m[K: > [01m[K/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10:[m[K > [01;36m[Knote: [m[K'[01m[K__builtin___snprintf_chk[m[K' output > between 2 and 1280 bytes into a destination of size 1024 >return [01;36m[K__builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL > - 1,[m[K > > [01;36m[K^~~~[m[K > [01;36m[K __bos (__s), __fmt, __va_arg_pack ())[m[K; > [01;36m[K~[m[K > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > authreg_ldap.lo authreg_ldap.c > [01m[Kstorage_fs.c:[m[K In function '[01m[K_st_fs_get
Bug#917751: ccdproc: FTBFS: tests failed
Source: ccdproc Version: 1.3.0-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 > python3.7 setup.py test -vv --args -v > running test > running install > running build > running build_py > creating build > creating build/lib > creating build/lib/ccdproc > copying ccdproc/log_meta.py -> build/lib/ccdproc > copying ccdproc/__init__.py -> build/lib/ccdproc > copying ccdproc/core.py -> build/lib/ccdproc > copying ccdproc/ccddata.py -> build/lib/ccdproc > copying ccdproc/version.py -> build/lib/ccdproc > copying ccdproc/conftest.py -> build/lib/ccdproc > copying ccdproc/_astropy_init.py -> build/lib/ccdproc > copying ccdproc/image_collection.py -> build/lib/ccdproc > copying ccdproc/combiner.py -> build/lib/ccdproc > creating build/lib/ccdproc/utils > copying ccdproc/utils/__init__.py -> build/lib/ccdproc/utils > copying ccdproc/utils/slices.py -> build/lib/ccdproc/utils > creating build/lib/ccdproc/tests > copying ccdproc/tests/setup_package.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_ccdproc_logging.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_bitfield.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_rebin.py -> build/lib/ccdproc/tests > copying ccdproc/tests/__init__.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_ccdmask.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_wrapped_external_funcs.py -> > build/lib/ccdproc/tests > copying ccdproc/tests/test_keyword.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_image_collection.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_ccdproc.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_combiner.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_ccddata.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_cosmicray.py -> build/lib/ccdproc/tests > copying ccdproc/tests/test_gain.py -> build/lib/ccdproc/tests > copying ccdproc/tests/pytest_fixtures.py -> build/lib/ccdproc/tests > creating build/lib/ccdproc/extern > copying ccdproc/extern/__init__.py -> build/lib/ccdproc/extern > copying ccdproc/extern/bitfield.py -> build/lib/ccdproc/extern > creating build/lib/ccdproc/utils/tests > copying ccdproc/utils/tests/__init__.py -> build/lib/ccdproc/utils/tests > copying ccdproc/utils/tests/test_slices.py -> build/lib/ccdproc/utils/tests > copying ccdproc/tests/coveragerc -> build/lib/ccdproc/tests > creating build/lib/ccdproc/tests/data > copying ccdproc/tests/data/a8280271.fits -> build/lib/ccdproc/tests/data > copying ccdproc/tests/data/sip-wcs.fit -> build/lib/ccdproc/tests/data > running install_lib > creating /tmp/ccdproc-test-m_j8ygd0/lib > creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7 > creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages > creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc > copying build/lib/ccdproc/log_meta.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc > creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils > copying build/lib/ccdproc/utils/__init__.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils > creating > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests > copying build/lib/ccdproc/utils/tests/__init__.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests > copying build/lib/ccdproc/utils/tests/test_slices.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests > copying build/lib/ccdproc/utils/slices.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils > copying build/lib/ccdproc/__init__.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc > copying build/lib/ccdproc/core.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc > creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests > copying build/lib/ccdproc/tests/setup_package.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests > copying build/lib/ccdproc/tests/coveragerc -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests > copying build/lib/ccdproc/tests/test_ccdproc_logging.py -> > /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests > copying build/lib/ccdproc/tests/test_bitfield.py ->
Bug#917752: lintian: FTBFS: tests failed
Source: lintian Version: 2.5.118 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > running tests > mkdir -p "/<>/debian/test-out" > t/runtests -k -j 2 t "/<>/debian/test-out" > Host architecture is amd64. > Latest policy version is 4.3.0 from Sun, 23 Dec 2018 10:17:55 + > > Environment: > DEB_HOST_ARCH=amd64 > DUMP_LOGS=yes > HARNESS_EPOCH=1545583328 > IPCRUNDEBUG=none > LC_ALL=C > LINTIAN_DPLINT_FRONTEND=/<>/frontend/dplint > LINTIAN_FRONTEND=/<>/frontend/lintian > LINTIAN_ROOT=/<> > LINTIAN_TEST_INSTALLED=no > LINTIAN_TEST_ROOT=/<> > NO_PKG_MANGLE=true > > PATH=/<>/t/helpers/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > POLICY_EPOCH=1545560275 > POLICY_VERSION=4.3.0 > > Test scripts: > /<>/t/scripts/01-critic/checks.t ... > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/collection.t ... > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/commands.t . > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/docs-examples.t > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/frontend.t . > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/helpers.t .. > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/lib.t .. > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/private.t .. > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/01-critic/test-scripts.t . > skipped: Only UNRELEASED versions are criticised > /<>/t/scripts/02-minimum-version/collection.t .. ok > /<>/t/scripts/02-minimum-version/commands.t ok > /<>/t/scripts/02-minimum-version/docs-examples.t ... ok > /<>/t/scripts/02-minimum-version/frontend.t ok > /<>/t/scripts/02-minimum-version/helpers.t . ok > /<>/t/scripts/02-minimum-version/checks.t .. ok > /<>/t/scripts/02-minimum-version/lib.t . ok > /<>/t/scripts/02-minimum-version/private.t . ok > /<>/t/scripts/02-minimum-version/test-scripts.t ok > /<>/t/scripts/03-strict/collection.t ... ok > /<>/t/scripts/03-strict/commands.t . ok > /<>/t/scripts/03-strict/docs-examples.t ok > /<>/t/scripts/03-strict/frontend.t . ok > /<>/t/scripts/03-strict/helpers.t .. ok > /<>/t/scripts/03-strict/checks.t ... ok > /<>/t/scripts/03-strict/private.t .. ok > /<>/t/scripts/03-strict/lib.t .. ok > /<>/t/scripts/Lintian/DepMap/01add-select-satisfy.t ok > /<>/t/scripts/Lintian/DepMap/03pending.t ... ok > /<>/t/scripts/Lintian/DepMap/04satisfiability.t ok > /<>/t/scripts/Lintian/DepMap/05multi-add.t . ok > /<>/t/scripts/Lintian/DepMap/06parents.t ... ok > /<>/t/scripts/Lintian/DepMap/08initialise.t ok > /<>/t/scripts/Lintian/DepMap/08initialise2.t ... ok > /<>/t/scripts/Lintian/DepMap/09unlink.t ok > /<>/t/scripts/Lintian/DepMap/10circular.t .. ok > /<>/t/scripts/Lintian/DepMap/11prefix.t ok > /<>/t/scripts/Lintian/DepMap/12done.t .. ok > /<>/t/scripts/Lintian/DepMap/Properties/00construct.t .. ok > /<>/t/scripts/Lintian/Lab/Manifest/01-basic.t .. ok > /<>/t/scripts/Lintian/Lab/Manifest/02-io.t . ok > /<>/t/scripts/Lintian/Lab/Manifest/03-diff.t ... ok > /<>/t/scripts/Lintian/Lab/auto-repair.t ok > /<>/t/scripts/Lintian/Lab/repair.t . ok > /<>/t/scripts/Lintian/Relation/01-basic.t .. ok > /<>/t/scripts/Lintian/Relation/02-architecture.t ... ok > /<>/t/scripts/Lintian/Relation/03-duplicates.t . ok > /<>/t/scripts/Lintian/Relation/04-multiarch.t .. ok > /<>/t/scripts/Lintian/Relation/
Bug#917747: golang-github-rackspace-gophercloud: FTBFS: tests failed
Source: golang-github-rackspace-gophercloud Version: 1.0.0+git20161013.1012.e00690e8-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 > '/<>/golang-github-rackspace-gophercloud-1.0.0+git20161013.1012.e00690e8' > (export GOPATH=`pwd`/obj-x86_64-linux-gnu; \ > cd $GOPATH/src/$DH_GOPKG/; \ > go test -v -tags=fixtures ./...) > go: disabling cache (/sbuild-nonexistent/.cache/go-build) due to > initialization failure: mkdir /sbuild-nonexistent: permission denied > === RUN TestApplyDefaultsToEndpointOpts > --- PASS: TestApplyDefaultsToEndpointOpts (0.00s) > === RUN TestMaybeString > --- PASS: TestMaybeString (0.00s) > === RUN TestMaybeInt > --- PASS: TestMaybeInt (0.00s) > === RUN TestBuildQueryString > --- PASS: TestBuildQueryString (0.00s) > === RUN TestBuildHeaders > --- PASS: TestBuildHeaders (0.00s) > === RUN TestIsZero > --- PASS: TestIsZero (0.00s) > === RUN TestQueriesAreEscaped > --- PASS: TestQueriesAreEscaped (0.00s) > === RUN TestAuthenticatedHeaders > --- PASS: TestAuthenticatedHeaders (0.00s) > === RUN TestUserAgent > --- PASS: TestUserAgent (0.00s) > === RUN TestServiceURL > --- PASS: TestServiceURL (0.00s) > === RUN TestWaitFor > --- PASS: TestWaitFor (1.00s) > === RUN TestNormalizeURL > --- PASS: TestNormalizeURL (0.00s) > === RUN TestNormalizePathURL > --- PASS: TestNormalizePathURL (0.00s) > PASS > okgithub.com/rackspace/gophercloud1.004s > ? github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v1 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v2 > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v2/extensions > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/compute/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/db/v1 [no > test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/identity/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/identity/v3 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/imageservice/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/openstack/networking/v2 > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/fwaas > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas_v2 > [no test files] > ? > github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/portsbinding > [no test files] > ? github.com/rackspace/gophercloud/acceptance/rackspace [no test files] > ? github.com/rackspace/gophercloud/acceptance/rackspace/compute/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/rackspace/db/v1 [no > test files] > ? github.com/rackspace/gophercloud/acceptance/rackspace/identity/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/rackspace/networking/v2 > [no test files] > ? github.com/rackspace/gophercloud/acceptance/tools [no test files] > === RUN TestAuthenticatedClientV3 > --- PASS: TestAuthenticatedClientV3 (0.00s) > === RUN TestAuthenticatedClientV2 > --- PASS: TestAuthenticatedClientV2 (0.00s) > === RUN TestNewClient > --- PASS: TestNewClient (0.00s) > === RUN TestV2EndpointExact > --- PASS: TestV2EndpointExact (0.00s) > === RUN TestV2EndpointNone > --- PASS: TestV2EndpointNone (0.00s) > === RUN TestV2EndpointMultiple > --- PASS: TestV2EndpointMultiple (0.00s) > === RUN TestV2EndpointBadAvailability > --- PASS: TestV2EndpointBadAvailability (0.00s) > === RUN TestV3EndpointExact > --- PASS: TestV3EndpointExact (0.00s) > === RUN TestV3EndpointNone > --- PASS: TestV3EndpointNone (0.00s) > === RUN TestV3EndpointMultiple > --- PASS: TestV3EndpointMultiple (0.00s) > === RUN TestV3EndpointBadAvailability > --- PASS: TestV3EndpointBadAvailability (0.00s) > PASS > okgithub.com/rackspace/gophercloud/openstack 0.014s > === RUN TestListVersions > --- PASS: TestListVersions (0.00s) > === RUN TestAPI
Bug#917745: cross-toolchain-base: FTBFS: applying patches fails
Source: cross-toolchain-base Version: 30 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > linux: 4.19.12-1 / 4.18.20-2cross2 > glibc: 2.28-4 / 2.28-2cross2 > > old linux version: 4.18.20-2 / 2 > old glibc version: 2.28-2 / 2 > > new linux version: 4.19.12-1cross1 > new glibc version: 2.28-4cross1 > START stamp-dir/init-glibc > rm -rf glibc-2.28 > tar -x -f /usr/src/glibc/glibc-2.28.tar.xz > cp -a /usr/src/glibc/debian/ glibc-2.28 > cd glibc-2.28 ; \ > QUILT_PATCHES=/<>/debian/patches/glibc/debian quilt --quiltrc > /dev/null push -a && \ > rm -rf .pc/ > Applying patch dpkg-shlibs.patch > patching file debian/rules.d/debhelper.mk > > Applying patch local-kill-locales.patch > patching file debian/rules > patching file localedata/SUPPORTED > > Applying patch glibc-build-tools.diff > patching file debian/rules > > Applying patch gcc-8-armel.diff > patching file debian/sysdeps/armel.mk > Hunk #1 FAILED at 1. > 1 out of 1 hunk FAILED -- rejects in file debian/sysdeps/armel.mk > Patch gcc-8-armel.diff does not apply (enforce with -f) > make: *** [debian/rules:436: stamp-dir/init-glibc] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/cross-toolchain-base_30_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#917744: php-zeta-base: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33
Source: php-zeta-base
Version: 1.9-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> phpunit
> PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/base_init_test.php(34):
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57):
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45):
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540):
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618):
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137):
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996):
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #9 /u in /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 255
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/php-zeta-base_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#917743: clj-time-clojure: FTBFS: tests failed
Source: clj-time-clojure Version: 0.14.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > (cd test && find . -name '*.clj' | \ > xargs --verbose clojure -cp > /<>/clj-time.jar:/usr/share/java/clojure.jar:/usr/share/java/joda-time.jar:/usr/share/java/java.jdbc.jar) > clojure -cp > /<>/clj-time.jar:/usr/share/java/clojure.jar:/usr/share/java/joda-time.jar:/usr/share/java/java.jdbc.jar > ./clj_time/local_test.clj ./clj_time/predicates_test.clj > ./clj_time/types_test.clj ./clj_time/jdbc_test.clj ./clj_time/core_test.clj > ./clj_time/periodic_test.clj ./clj_time/coerce_test.clj > ./clj_time/format_test.clj > Exception in thread "main" java.io.FileNotFoundException: Could not locate > clj_time/core_test__init.class or clj_time/core_test.clj on classpath. Please > check that namespaces with dashes use underscores in the Clojure file name., > compiling:(/<>/test/./clj_time/local_test.clj:1:1) > at clojure.lang.Compiler.load(Compiler.java:7526) > at clojure.lang.Compiler.loadFile(Compiler.java:7452) > at clojure.main$load_script.invokeStatic(main.clj:278) > at clojure.main$script_opt.invokeStatic(main.clj:338) > at clojure.main$script_opt.invoke(main.clj:333) > at clojure.main$main.invokeStatic(main.clj:424) > at clojure.main$main.doInvoke(main.clj:387) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.lang.Var.applyTo(Var.java:702) > at clojure.main.main(main.java:37) > Caused by: java.io.FileNotFoundException: Could not locate > clj_time/core_test__init.class or clj_time/core_test.clj on classpath. Please > check that namespaces with dashes use underscores in the Clojure file name. > at clojure.lang.RT.load(RT.java:463) > at clojure.lang.RT.load(RT.java:426) > at clojure.core$load$fn__9115.invoke(core.clj:6046) > at clojure.core$load.invokeStatic(core.clj:6045) > at clojure.core$load.doInvoke(core.clj:6029) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at clojure.core$load_one.invokeStatic(core.clj:5848) > at clojure.core$load_one.invoke(core.clj:5843) > at clojure.core$load_lib$fn__9060.invoke(core.clj:5888) > at clojure.core$load_lib.invokeStatic(core.clj:5887) > at clojure.core$load_lib.doInvoke(core.clj:5868) > at clojure.lang.RestFn.applyTo(RestFn.java:142) > at clojure.core$apply.invokeStatic(core.clj:659) > at clojure.core$load_libs.invokeStatic(core.clj:5925) > at clojure.core$load_libs.doInvoke(core.clj:5909) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.core$apply.invokeStatic(core.clj:659) > at clojure.core$require.invokeStatic(core.clj:5947) > at clojure.core$require.doInvoke(core.clj:5947) > at clojure.lang.RestFn.invoke(RestFn.java:436) > at > clj_time.local_test$eval2694$loading__9001__auto2695.invoke(local_test.clj:1) > at clj_time.local_test$eval2694.invokeStatic(local_test.clj:1) > at clj_time.local_test$eval2694.invoke(local_test.clj:1) > at clojure.lang.Compiler.eval(Compiler.java:7062) > at clojure.lang.Compiler.eval(Compiler.java:7051) > at clojure.lang.Compiler.load(Compiler.java:7514) > ... 9 more > make[1]: *** [debian/rules:29: override_dh_auto_test] Error 123 The full build log is available from: http://aws-logs.debian.net/2018/12/29/clj-time-clojure_0.14.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#917742: ca-cacert: FTBFS: tests failed
Source: ca-cacert
Version: 2011.0523-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> #find . -maxdepth 1 -type f -name "*.crt" -exec openssl verify "{}" \;
> certtool --verify --load-ca-certificate root.crt --infile class3.crt
> Loaded CAs (1 available)
> Subject: CN=CAcert Class 3 Root,OU=http://www.CAcert.org,O=CAcert Inc.
> Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing
> Authority,OU=http://www.cacert.org,O=Root CA
> Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing
> Authority,OU=http://www.cacert.org,O=Root CA
> Signature algorithm: RSA-SHA256
> Output: Verified. The certificate is trusted.
>
> Chain verification output: Verified. The certificate is trusted.
>
> certtool --verify --load-ca-certificate root.crt --infile root.crt
> Loaded CAs (1 available)
> Subject: EMAIL=supp...@cacert.org,CN=CA Cert Signing
> Authority,OU=http://www.cacert.org,O=Root CA
> Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing
> Authority,OU=http://www.cacert.org,O=Root CA
> Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing
> Authority,OU=http://www.cacert.org,O=Root CA
> Signature algorithm: RSA-MD5
> Output: Not verified. The certificate is NOT trusted.
>
> Chain verification output: Not verified. The certificate is NOT trusted.
>
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/ca-cacert_2011.0523-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#917746: uglifyjs: FTBFS: tests failures
Source: uglifyjs Version: 2.8.29-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > test -x debian/rules > mkdir -p "." > NODE_PATH=lib help2man --no-info bin/uglifyjs | sed \ > -e 's/[[:space:]]*\[string\]$/ This parameter is a string./g' \ > -e 's/[[:space:]]*\[boolean\]$/ This parameter is a boolean./g' \ > -e 's/[[:space:]]*\[array\]$/ This parameter is an array./g'> > debian/uglifyjs.1 > NODE_PATH=lib nodejs test/run-tests.js > *** Entering [compress] > --- angular-inject.js > Running test [ng_inject_defun] > Running test [ng_inject_assignment] > Running test [ng_inject_inline] > --- arrays.js > Running test [holes_and_undefined] > Running test [constant_join] > Running test [constant_join_2] > Running test [constant_join_3] > Running test [for_loop] > --- ascii.js > Running test [ascii_only_true] > Running test [ascii_only_false] > --- asm.js > Running test [asm_mixed] > --- assignment.js > Running test [op_equals_left_local_var] > Running test [op_equals_right_local_var] > Running test [op_equals_left_global_var] > Running test [op_equals_right_global_var] > --- blocks.js > Running test [remove_blocks] > Running test [keep_some_blocks] > --- collapse_vars.js > Running test [collapse_vars_side_effects_1] > Running test [collapse_vars_side_effects_2] > Running test [collapse_vars_issue_721] > Running test [collapse_vars_properties] > Running test [collapse_vars_if] > Running test [collapse_vars_while] > Running test [collapse_vars_do_while] > Running test [collapse_vars_do_while_drop_assign] > Running test [collapse_vars_seq] > Running test [collapse_vars_throw] > Running test [collapse_vars_switch] > Running test [collapse_vars_assignment] > Running test [collapse_vars_lvalues] > Running test [collapse_vars_lvalues_drop_assign] > Running test [collapse_vars_misc1] > Running test [collapse_vars_self_reference] > Running test [collapse_vars_repeated] > Running test [collapse_vars_closures] > Running test [collapse_vars_unary] > Running test [collapse_vars_try] > Running test [collapse_vars_array] > Running test [collapse_vars_object] > Running test [collapse_vars_eval_and_with] > Running test [collapse_vars_constants] > Running test [collapse_vars_arguments] > Running test [collapse_vars_short_circuit] > Running test [collapse_vars_short_circuited_conditions] > Running test [collapse_vars_regexp] > Running test [issue_1537] > Running test [issue_1562] > Running test [issue_1605_1] > Running test [issue_1605_2] > Running test [issue_1631_1] > Running test [issue_1631_2] > Running test [issue_1631_3] > Running test [var_side_effects_1] > Running test [var_side_effects_2] > Running test [var_side_effects_3] > Running test [reassign_const_1] > Running test [reassign_const_2] > --- comparing.js > Running test [keep_comparisons] > Running test [keep_comparisons_with_unsafe_comps] > Running test [dont_change_in_or_instanceof_expressions] > --- concat-strings.js > Running test [concat_1] > Running test [concat_2] > Running test [concat_3] > Running test [concat_4] > Running test [concat_5] > Running test [concat_6] > Running test [concat_7] > Running test [concat_8] > --- conditionals.js > Running test [ifs_1] > Running test [ifs_2] > Running test [ifs_3_should_warn] > Running test [ifs_4] > Running test [ifs_5] > Running test [ifs_6] > Running test [cond_1] > Running test [cond_2] > Running test [cond_3] > Running test [cond_4] > Running test [cond_5] > Running test [cond_7] > Running test [cond_7_1] > Running test [cond_8] > Running test [cond_8b] > Running test [cond_8c] > Running test [ternary_boolean_consequent] > Running test [ternary_boolean_alternative] > Running test [trivial_boolean_ternary_expressions] > Running test [issue_1154] > Running test [no_evaluate] > Running test [equality_conditionals_false] > Running test [equality_conditionals_true] > Running test [issue_1645_1] > Running test [issue_1645_2] > Running test [condition_symbol_matches_consequent] > Running test [delete_conditional_1] > Running test [delete_conditional_2] > --- const.js &
Bug#917741: globus-xio-gridftp-driver: FTBFS: tests failed
Source: globus-xio-gridftp-driver Version: 3.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/test' > FAIL: globus_gridftp_driver_test.pl > >globus_xio_gridftp_driver 3.1: test/test-suite.log > > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: globus_gridftp_driver_test.pl > === > > #./globus_gridftp_driver_test.pl > 1..8 > not ok 1 - globus_gridftp_driver_test -r exits with 6 > # Failed test 'globus_gridftp_driver_test -r exits with 6' > # at ./globus_gridftp_driver_test.pl line 53. > not ok 2 - File compares with remote original > # Failed test 'File compares with remote original' > # at ./globus_gridftp_driver_test.pl line 54. > not ok 3 - globus_gridftp_driver_test -w exits with 6 > # Failed test 'globus_gridftp_driver_test -w exits with 6' > # at ./globus_gridftp_driver_test.pl line 72. > not ok 4 - File compares with remote > # Failed test 'File compares with remote' > # at ./globus_gridftp_driver_test.pl line 73. > not ok 5 - globus_gridftp_driver_test -a exits with 6 > # Failed test 'globus_gridftp_driver_test -a exits with 6' > # at ./globus_gridftp_driver_test.pl line 91. > not ok 6 - File compares with remote > # Failed test 'File compares with remote' > # at ./globus_gridftp_driver_test.pl line 92. > not ok 7 - 2nd globus_gridftp_driver_test -a exits with 6 > # Failed test '2nd globus_gridftp_driver_test -a exits with 6' > # at ./globus_gridftp_driver_test.pl line 112. > # > not ok 8 - File compares with appended remote > # Failed test 'File compares with appended remote' > # at ./globus_gridftp_driver_test.pl line 113. > # > # Looks like you failed 8 tests of 8. > # Test exited with 2048 > FAIL globus_gridftp_driver_test.pl (exit status: 1) > > > Testsuite summary for globus_xio_gridftp_driver 3.1 > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See test/test-suite.log > Please report to https://github.com/gridcf/gct/issues > > make[4]: *** [Makefile:709: test-suite.log] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/globus-xio-gridftp-driver_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.
Processed: Setting fixed version...
Processing commands for cont...@bugs.debian.org:
> fixed 917709 3.1-1
Bug #917709 {Done: Ole Streicher } [src:astropy] astropy:
FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7
returned exit code 13
Marked as fixed in versions astropy/3.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Reassign skimage bugs
Processing commands for cont...@bugs.debian.org:
> reassign 917720 python3-skimage 0.14.1-2
Bug #917720 [src:sunpy] sunpy: FTBFS: dh_auto_test: pybuild --test
--test-pytest -i python{version} -p 3.7 returned exit code 13
Bug reassigned from package 'src:sunpy' to 'python3-skimage'.
No longer marked as found in versions sunpy/0.9.5-1.
Ignoring request to alter fixed versions of bug #917720 to the same values
previously set
Bug #917720 [python3-skimage] sunpy: FTBFS: dh_auto_test: pybuild --test
--test-pytest -i python{version} -p 3.7 returned exit code 13
Marked as found in versions skimage/0.14.1-2.
> reassign 917683 python3-skimage 0.14.1-2
Bug #917683 [src:hipspy] hipspy: FTBFS: ImportError: cannot import name
'_validate_lengths' from 'numpy.lib.arraypad'
(/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Bug reassigned from package 'src:hipspy' to 'python3-skimage'.
No longer marked as found in versions hipspy/0.2-1.
Ignoring request to alter fixed versions of bug #917683 to the same values
previously set
Bug #917683 [python3-skimage] hipspy: FTBFS: ImportError: cannot import name
'_validate_lengths' from 'numpy.lib.arraypad'
(/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Marked as found in versions skimage/0.14.1-2.
> forcemerge 917353 917720 917683
Bug #917353 [python3-skimage] [python3-skimage] Cannot import skimage with new
numpy
Bug #917353 [python3-skimage] [python3-skimage] Cannot import skimage with new
numpy
Added tag(s) buster and sid.
Bug #917720 [python3-skimage] sunpy: FTBFS: dh_auto_test: pybuild --test
--test-pytest -i python{version} -p 3.7 returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/scikit-image/scikit-image/issues/3551'.
Added tag(s) patch.
Bug #917683 [python3-skimage] hipspy: FTBFS: ImportError: cannot import name
'_validate_lengths' from 'numpy.lib.arraypad'
(/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Set Bug forwarded-to-address to
'https://github.com/scikit-image/scikit-image/issues/3551'.
Added tag(s) patch.
Merged 917353 917683 917720
> affects 917353 src:sunpy src:hipspy src:aplpy
Bug #917353 [python3-skimage] [python3-skimage] Cannot import skimage with new
numpy
Bug #917683 [python3-skimage] hipspy: FTBFS: ImportError: cannot import name
'_validate_lengths' from 'numpy.lib.arraypad'
(/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Bug #917720 [python3-skimage] sunpy: FTBFS: dh_auto_test: pybuild --test
--test-pytest -i python{version} -p 3.7 returned exit code 13
Added indication that 917353 affects src:sunpy, src:hipspy, and src:aplpy
Added indication that 917683 affects src:sunpy, src:hipspy, and src:aplpy
Added indication that 917720 affects src:sunpy, src:hipspy, and src:aplpy
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917353
917683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917683
917720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#917734: flexpart: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory
Source: flexpart Version: 9.02-19 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > par_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > com_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > conv_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > hanna_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > interpol_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > cmapf_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > unc_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > oh_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > xmass_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > flux_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > point_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > outg_mod.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > writeheader.f90 > gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium -O2 > -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include > assignland.f90 > assignland.f90:181:16: > >do l=1,numbnests > 2 > do ix=0,nxn(l)-1 > 1 > Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2) > assignland.f90:182:18: > > assignland.f90:180:18: > >do l=1,numbnests > 2 > assignland.f90:182:18: > >do jy=0,nyn(l)-1 > 1 > Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2) > assignland.f90:185:28: > > assignland.f90:180:18: > >do l=1,numbnests > 2 > assignland.f90:185:28: > >xlandusen(ix,jy,k,l)=0. > 1 > Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2) > assignland.f90:185:20: > > assignland.f90:181:20: > > do ix=0,nxn(l)-1 > 2 > assignland.f90:185:20: > >xlandusen(ix,jy,k,l)=0. > 1 > Warning: Array reference at (1) out of bounds (0 > -1) in loop beginning at > (2) > assignland.f90:185:23: > > assignland.f90:182:22: > >do jy=0,nyn(l)-1 > 2 > assignland.f90:185:23: > >xlandusen(ix,jy,k,l)=0. >1 > Warning: Array reference at (1) out of bounds (0 > -1) in loop beginning at > (2) > assignland.f90:188:47: > > assignland.f90:180:18: > >do l=1,numbnests > 2 > assignland.f90:188:47: > > xlon=(ix+(iix-1)/real(nrefine))*dxn(l)+xlon0n(l) >1 > Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2) > assignland.f90:188:57: > > assignland.f90:180:18: > >do l=1,numbnests > 2 > assignland.f90:188:57: > > xlon=(ix+(iix-1)/real(nrefine))*dxn(l)+xlon0n(l) > 1 > Warning: Array reference at (1)
Bug#917728: flextra: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory
Source: flextra Version: 5.0-10 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o caldate.o caldate.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o openoutput.o openoutput.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o checklimits.o checklimits.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o coordtrafo.o coordtrafo.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o orolininterpol.o orolininterpol.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o etatrafo.o etatrafo.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o petters.o petters.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o eta.ecmwf.o eta.ecmwf.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o FLEXTRA.o FLEXTRA.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o pp.ecmwf.o pp.ecmwf.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o geteta.o geteta.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o getfields.o getfields.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o pvinterpol.o pvinterpol.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o getheight.o getheight.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o random.o random.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o readavailable.o readavailable.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o getwind.o getwind.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o readcommand.o readcommand.f > gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC -fconvert=little-endian > -frecord-marker=4 -I/usr/include -c -o gridcheck.o gridcheck.f > gridcheck.f:52:9: > >use grib_api > 1 > Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No > such file or directory > compilation terminated. > make[2]: *** [: gridcheck.o] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/flextra_5.0-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#917737: ocaml-qtest: FTBFS: dh_install: missing files, aborting
Source: ocaml-qtest Version: 2.9-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > mkdir -p '/<>/debian/tmp/usr/lib/ocaml' > jbuilder install --prefix=/<>/debian/tmp/usr > --libdir=/<>/debian/tmp/usr/lib/ocaml --verbose > # Workspace root: /<> > Running[0]: /usr/bin/nproc > /tmp/dune98b49a.output 2> /dev/null > # # Workspace root: /<> > # Auto-detected concurrency: 2 > Running[1]: /usr/bin/ocamlc.opt -config > /tmp/dune3af626.output > # # # Workspace root: /<> > # # Auto-detected concurrency: 2 > # Dune context: > # ((name default) > # (kind default) > # (profile release) > # (merlin true) > # (for_host ()) > # (build_dir (In_build_dir default)) > # (toplevel_path ()) > # (ocaml_bin (External /usr/bin)) > # (ocaml (External /usr/bin/ocaml)) > # (ocamlc (External /usr/bin/ocamlc.opt)) > # (ocamlopt ((External /usr/bin/ocamlopt.opt))) > # (ocamldep (External /usr/bin/ocamldep.opt)) > # (ocamlmklib (External /usr/bin/ocamlmklib.opt)) > # (env > #((CAML_LD_LIBRARY_PATH > # /<>/_build/install/default/lib/stublibs) > # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt) > # (INSIDE_DUNE 1) > # (MANPATH > # /<>/_build/install/default/bin) > # (OCAMLFIND_IGNORE_DUPS_IN > # /<>/_build/install/default/lib) > # (OCAMLPATH > # /<>/_build/install/default/lib))) > # (findlib_path ((External /usr/lib/ocaml))) > # (arch_sixtyfour true) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (opam_vars ()) > # (ocaml_config > #((version 4.05.0) > # (standard_library_default /usr/lib/ocaml) > # (standard_library /usr/lib/ocaml) > # (standard_runtime /usr/bin/ocamlrun) > # (ccomp_type cc) > # (c_compiler gcc) > # (ocamlc_cflags > # (-O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (ocamlopt_cflags > # (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT)) > # (bytecomp_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread)) > # (native_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT)) > # (native_c_libraries (-lm -ldl)) > # (cc_profile (-pg)) > # (architecture amd64) > # (model default) > # (int_size 63) > # (word_size 64) > # (system linux) > # (asm (as)) > # (asm_cfi_supported true) > # (with_frame_pointers false) > # (ext_exe ) > # (ext_obj .o) > # (ext_asm .s) > # (ext_lib .a) > # (ext_dll .so) > # (os_type Unix) > # (default_executable_name a.out) > # (systhread_supported true) > # (host x86_64-pc-linux-gnu) > # (target x86_64-pc-linux-gnu) > # (profiling true) > # (flambda false) > # (spacetime false) > # (safe_string false) > # (exec_magic_number Caml1999X011) > # (cmi_magic_number Caml1999I021) > # (cmo_magic_number Caml1999O011) > # (cma_magic_number Caml1999A012) > # (cmx_magic_number Caml1999Y015) > # (cmxa_magic_number Caml1999Z014) > # (ast_impl_magic_number Caml1999M020) > # (ast_intf_magic_number Caml1999N018) > # (cmxs_magic_number Caml2007D002) > # (cmt_magic_number Caml2012T009) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (windows_unicode false))) > # (which > #((ocaml ((External /usr/bin/ocaml))) > # (ocamlc ((External /usr/bin/ocamlc.opt)) > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/META > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtest.lib.dune > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.a > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cma > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmi > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmt > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmx > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmxa > Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmxs > Installing /<>/d
Bug#917725: python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
Source: python-acora Version: 2.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > rm -f acora/_acora.c acora/_cacora.c > dh_auto_clean > I: pybuild base:217: python2.7 setup.py clean > WARNING: Generated .c files are missing, enabling Cython compilation > Building with Cython 0.28.4 > Compiling acora/_acora.py because it changed. > Compiling acora/_cacora.pyx because it changed. > [1/2] Cythonizing acora/_acora.py > [2/2] Cythonizing acora/_cacora.pyx > running clean > removing '/<>/.pybuild/cpython2_2.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-2.7' does not exist -- can't clean it > I: pybuild base:217: python3.7 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-3.7' does not exist -- can't clean it > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-acora using existing > ./python-acora_2.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > python-acora-2.1/acora/_acora.c > python-acora-2.1/acora/_acora.html > python-acora-2.1/acora/_cacora.c > python-acora-2.1/acora/_cacora.html > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-acora_2.1-1.diff.T8mOsr > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2018-12-29T12:29:03Z The full build log is available from: http://aws-logs.debian.net/2018/12/29/python-acora_2.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#917732: openhft-chronicle-bytes: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[78,48] cannot find symbol
Source: openhft-chronicle-bytes Version: 1.1.15-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-bytes-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] < net.openhft:chronicle-bytes > >- > [INFO] Building OpenHFT/Chronicle-Bytes 1.1.15 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > chronicle-bytes --- > [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ > chronicle-bytes --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 52 source files to /<>/target/classes > [INFO] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[23,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[23,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[24,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[27,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[42,76] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[60,27] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[68,27] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[337,33] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[142,22] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/mai
Bug#917738: openhft-chronicle-threads: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32] cannot find symbol
Source: openhft-chronicle-threads Version: 1.1.6-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-threads-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] ---< net.openhft:chronicle-threads > > > [INFO] Building OpenHFT/Chronicle-Threads 1.1.6 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > chronicle-threads --- > [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ > chronicle-threads --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 14 source files to /<>/target/classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[28,20] > package javax.xml.ws does not exist > [ERROR] > /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32] > cannot find symbol > symbol: class WebServiceException > location: class net.openhft.chronicle.threads.MonitorEventLoop > [INFO] 2 errors > [INFO] - > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.117 s > [INFO] Finished at: 2018-12-29T13:57:53Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project chronicle-threads: Compilation failure: > Compilation failure: > [ERROR] > /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[28,20] > package javax.xml.ws does not exist > [ERROR] > /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32] > cannot find symbol > [ERROR] symbol: class WebServiceException > [ERROR] location: class net.openhft.chronicle.threads.MonitorEventLoop > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>
Bug#917733: ocaml-atd: FTBFS: dh_install: missing files, aborting
Source: ocaml-atd Version: 2.0.0-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > mkdir -p '/<>/debian/tmp/usr/bin' > mkdir -p '/<>/debian/tmp//usr/lib/ocaml' > jbuilder install --destdir=/<>/debian/tmp/usr > --libdir=/<>/debian/tmp//usr/lib/ocaml --verbose > # Workspace root: /<> > Running[0]: /usr/bin/nproc > /tmp/dune9c2993.output 2> /dev/null > # # Workspace root: /<> > # Auto-detected concurrency: 2 > Running[1]: /usr/bin/ocamlc.opt -config > /tmp/dune80f501.output > # # # Workspace root: /<> > # # Auto-detected concurrency: 2 > # Dune context: > # ((name default) > # (kind default) > # (profile release) > # (merlin true) > # (for_host ()) > # (build_dir (In_build_dir default)) > # (toplevel_path ()) > # (ocaml_bin (External /usr/bin)) > # (ocaml (External /usr/bin/ocaml)) > # (ocamlc (External /usr/bin/ocamlc.opt)) > # (ocamlopt ((External /usr/bin/ocamlopt.opt))) > # (ocamldep (External /usr/bin/ocamldep.opt)) > # (ocamlmklib (External /usr/bin/ocamlmklib.opt)) > # (env > #((CAML_LD_LIBRARY_PATH > # /<>/_build/install/default/lib/stublibs) > # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt) > # (INSIDE_DUNE 1) > # (MANPATH > # /<>/_build/install/default/bin) > # (OCAMLFIND_IGNORE_DUPS_IN > # /<>/_build/install/default/lib) > # (OCAMLPATH > # /<>/_build/install/default/lib))) > # (findlib_path ((External /usr/lib/ocaml))) > # (arch_sixtyfour true) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (opam_vars ()) > # (ocaml_config > #((version 4.05.0) > # (standard_library_default /usr/lib/ocaml) > # (standard_library /usr/lib/ocaml) > # (standard_runtime /usr/bin/ocamlrun) > # (ccomp_type cc) > # (c_compiler gcc) > # (ocamlc_cflags > # (-O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (ocamlopt_cflags > # (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT)) > # (bytecomp_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread)) > # (native_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT)) > # (native_c_libraries (-lm -ldl)) > # (cc_profile (-pg)) > # (architecture amd64) > # (model default) > # (int_size 63) > # (word_size 64) > # (system linux) > # (asm (as)) > # (asm_cfi_supported true) > # (with_frame_pointers false) > # (ext_exe ) > # (ext_obj .o) > # (ext_asm .s) > # (ext_lib .a) > # (ext_dll .so) > # (os_type Unix) > # (default_executable_name a.out) > # (systhread_supported true) > # (host x86_64-pc-linux-gnu) > # (target x86_64-pc-linux-gnu) > # (profiling true) > # (flambda false) > # (spacetime false) > # (safe_string false) > # (exec_magic_number Caml1999X011) > # (cmi_magic_number Caml1999I021) > # (cmo_magic_number Caml1999O011) > # (cma_magic_number Caml1999A012) > # (cmx_magic_number Caml1999Y015) > # (cmxa_magic_number Caml1999Z014) > # (ast_impl_magic_number Caml1999M020) > # (ast_intf_magic_number Caml1999N018) > # (cmxs_magic_number Caml2007D002) > # (cmt_magic_number Caml2012T009) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (windows_unicode false))) > # (which > #((ocaml ((External /usr/bin/ocaml))) > # (ocamlc ((External /usr/bin/ocamlc.opt)) > Running[2]: /usr/bin/opam config var prefix > /tmp/dune68e10c.output > Output[2]: > [WARNING] Running as root is not recommended > [ERROR] Opam has not been initialised, please run `opam init' > Warning: Command [2] exited with code 50, but I'm ignoring it, hope that's OK. > Installing > /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/META > Installing > /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/annot.ml > Installing > /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/annot.mli > Installing > /<>/debian/tmp/usr/<>/debia
Bug#917731: ocaml-rope: FTBFS: dh_install: missing files, aborting
Source: ocaml-rope Version: 0.6.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > mkdir -p '/<>/debian/tmp/usr/lib/ocaml' > jbuilder install --destdir=/<>/debian/tmp > --libdir=/<>/debian/tmp/usr/lib/ocaml --verbose > # Workspace root: /<> > Running[0]: /usr/bin/nproc > /tmp/dunef1a789.output 2> /dev/null > # # Workspace root: /<> > # Auto-detected concurrency: 2 > Running[1]: /usr/bin/ocamlc.opt -config > /tmp/duneab278c.output > # # # Workspace root: /<> > # # Auto-detected concurrency: 2 > # Dune context: > # ((name default) > # (kind default) > # (profile release) > # (merlin true) > # (for_host ()) > # (build_dir (In_build_dir default)) > # (toplevel_path ()) > # (ocaml_bin (External /usr/bin)) > # (ocaml (External /usr/bin/ocaml)) > # (ocamlc (External /usr/bin/ocamlc.opt)) > # (ocamlopt ((External /usr/bin/ocamlopt.opt))) > # (ocamldep (External /usr/bin/ocamldep.opt)) > # (ocamlmklib (External /usr/bin/ocamlmklib.opt)) > # (env > #((CAML_LD_LIBRARY_PATH > # /<>/_build/install/default/lib/stublibs) > # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt) > # (INSIDE_DUNE 1) > # (MANPATH > # /<>/_build/install/default/bin) > # (OCAMLFIND_IGNORE_DUPS_IN > # /<>/_build/install/default/lib) > # (OCAMLPATH > # /<>/_build/install/default/lib))) > # (findlib_path ((External /usr/lib/ocaml))) > # (arch_sixtyfour true) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (opam_vars ()) > # (ocaml_config > #((version 4.05.0) > # (standard_library_default /usr/lib/ocaml) > # (standard_library /usr/lib/ocaml) > # (standard_runtime /usr/bin/ocamlrun) > # (ccomp_type cc) > # (c_compiler gcc) > # (ocamlc_cflags > # (-O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (ocamlopt_cflags > # (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT)) > # (bytecomp_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT > # -fPIC)) > # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread)) > # (native_c_compiler > # (gcc > # -O2 > # -fno-strict-aliasing > # -fwrapv > # -D_FILE_OFFSET_BITS=64 > # -D_REENTRANT)) > # (native_c_libraries (-lm -ldl)) > # (cc_profile (-pg)) > # (architecture amd64) > # (model default) > # (int_size 63) > # (word_size 64) > # (system linux) > # (asm (as)) > # (asm_cfi_supported true) > # (with_frame_pointers false) > # (ext_exe ) > # (ext_obj .o) > # (ext_asm .s) > # (ext_lib .a) > # (ext_dll .so) > # (os_type Unix) > # (default_executable_name a.out) > # (systhread_supported true) > # (host x86_64-pc-linux-gnu) > # (target x86_64-pc-linux-gnu) > # (profiling true) > # (flambda false) > # (spacetime false) > # (safe_string false) > # (exec_magic_number Caml1999X011) > # (cmi_magic_number Caml1999I021) > # (cmo_magic_number Caml1999O011) > # (cma_magic_number Caml1999A012) > # (cmx_magic_number Caml1999Y015) > # (cmxa_magic_number Caml1999Z014) > # (ast_impl_magic_number Caml1999M020) > # (ast_intf_magic_number Caml1999N018) > # (cmxs_magic_number Caml2007D002) > # (cmt_magic_number Caml2012T009) > # (natdynlink_supported true) > # (supports_shared_libraries true) > # (windows_unicode false))) > # (which > #((ocaml ((External /usr/bin/ocaml))) > # (ocamlc ((External /usr/bin/ocamlc.opt)) > Running[2]: /usr/bin/opam config var prefix > /tmp/dunec6d5c6.output > Output[2]: > [WARNING] Running as root is not recommended > [ERROR] Opam has not been initialised, please run `opam init' > Warning: Command [2] exited with code 50, but I'm ignoring it, hope that's OK. > Installing > /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/META > Installing > /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/opam > Installing > /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/rope.a > Installing > /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/rope.cma > Installing > /<>/debian/tm
Bug#917736: openhft-chronicle-core: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/core/io/IOTools.java:[32,27] cannot find symbol
Source: openhft-chronicle-core Version: 1.1.8-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-core-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] -< net.openhft:chronicle-core > >- > [INFO] Building OpenHFT/Chronicle-Core 1.1.8 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > chronicle-core --- > [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ > chronicle-core --- > [INFO] Changes detected - recompiling the module! > [WARNING] File encoding has not been set, using platform encoding > ANSI_X3.4-1968, i.e. build is platform dependent! > [INFO] Compiling 58 source files to /<>/target/classes > [INFO] > /<>/src/main/java/net/openhft/chronicle/core/util/ObjectUtils.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/net/openhft/chronicle/core/util/ObjectUtils.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[20,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/OS.java:[21,18] > sun.nio.ch.FileChannelImpl is internal proprietary API and may be removed in > a future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[26,12] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[32,48] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[33,27] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[265,34] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/core/OS.java:[273,29] > sun.nio.ch.FileChannelImpl is internal proprietary API and may be removed in > a future release > [INFO] 7 warnings > [INFO] - > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/net/openhft/chronicle/core/io/IOTools.j
Bug#917730: caffeine: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
Source: caffeine Version: 2.9.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3,bash-completion --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:217: python3.7 setup.py clean > Compiling for Locale: bg > Compiling for Locale: ro > Compiling for Locale: pl > Compiling for Locale: en_GB > Compiling for Locale: ru > Compiling for Locale: gl > Compiling for Locale: fr > Compiling for Locale: it > Compiling for Locale: nl > Compiling for Locale: lt > Compiling for Locale: pt > Compiling for Locale: sv > Compiling for Locale: da > Compiling for Locale: ms > Compiling for Locale: he > Compiling for Locale: no > Compiling for Locale: ar > Compiling for Locale: pt_BR > Compiling for Locale: eu > Compiling for Locale: xh > Compiling for Locale: eo > Compiling for Locale: tr > Compiling for Locale: bs > Compiling for Locale: fi > Compiling for Locale: vi > Compiling for Locale: uk > Compiling for Locale: sk > Compiling for Locale: es > Compiling for Locale: de > Compiling for Locale: zh_TW > Compiling for Locale: el > Compiling for Locale: th > Compiling for Locale: ja > Compiling for Locale: hu > Compiling for Locale: ca > Compiling for Locale: cs > running clean > removing '/<>/.pybuild/cpython3_3.7_caffeine/build' (and > everything under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-3.7' does not exist -- can't clean it >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building caffeine using existing > ./caffeine_2.9.4.orig.tar.gz > dpkg-source: warning: ignoring deletion of file > translations/caffeine-indicator.pot, use --include-removal to override > dpkg-source: error: cannot represent change to > share/locale/ar/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/ar/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/bg/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/bg/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/bs/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/bs/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/ca/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/ca/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/cs/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/cs/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/da/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/da/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/de/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/de/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/el/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/el/LC_MESSAGES/caffeine-indicator.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > share/locale/en_GB/LC_MESSAGES/caffeine-indicator.mo: binary file contents > changed > dpkg-source: error: add share/locale/en_GB/LC_MESSAGES/caff
Bug#917735: bacula-doc: FTBFS: ! LaTeX Error: Missing \begin{document}.
Source: bacula-doc
Version: 9.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>/manuals/en/misc'
>
> Making output directories...
> echo "Output directories done"
> Output directories done
>
> Building external references for misc
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./misc.tex
> LaTeX2e <2018-12-01>
> (../../../latex/borgmanual.cls
> Document Class: borgmanual 2014/03/02 v1.0 Standard bacula.org Book LaTeX
> docum
> ent class
> (/usr/share/texlive/texmf-dist/tex/latex/eso-pic/eso-pic.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/atbegshi.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (../../../latex/atxy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texmf/tex/latex/html/html.sty
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) (./bacula.sty
> (/usr/share/texlive/texmf-dist/tex/latex/carlisle/ltxtable.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/varioref.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/xr-hyper.sty
>
> Package xr-hyper Warning: Load package `hyperref' after `xr-hyper'.
>
> ) (/usr/share/texlive/texmf-dist/tex/latex/tools/xr.sty)
> (../../../latex/external-references.tex
>
> Package xr Warning:
> No file ../main/sqlite.aux
> LABELS NOT IMPORTED.
> on input line 26.
>
>
> Package xr Warning:
> No file ../main/fileset.aux
> LABELS NOT IMPORTED.
> on input line 54.
>
>
> ! LaTeX Error: Missing \begin{document}.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H for immediate help.
> ...
>
> l.55 \externaldocument[main-]{../main/main}
>
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on ../pdf-and-html/misc/misc.log.
> make[2]: *** [Makefile:116: external-references] Error 1
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/bacula-doc_9.4.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#917726: globus-gass-copy: FTBFS: tests failed
Source: globus-gass-copy Version: 10.3-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/test' > FAIL: guc-fw.pl > FAIL: guc-pp-cc.pl > FAIL: guc-stack.pl > FAIL: guc-cc.pl > FAIL: guc-cc-fast.pl > FAIL: guc-cc-p2.pl > FAIL: guc-cc-p4.pl > FAIL: guc-cc-stripe.pl > FAIL: guc-cc-stripe-p4.pl > >globus_gass_copy 10.3: test/test-suite.log > > > # TOTAL: 9 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 9 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: guc-fw.pl > === > > # Started server at port 45897 > 1..32 > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 1 - guc fw -nodcau exits with 0 > # Failed test 'guc fw -nodcau exits with 0' > # at ./guc-fw.pl line 121. > not ok 2 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 3 - guc fw exits with 0 > # Failed test 'guc fw exits with 0' > # at ./guc-fw.pl line 121. > not ok 4 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 5 - guc fw -dcsafe exits with 0 > # Failed test 'guc fw -dcsafe exits with 0' > # at ./guc-fw.pl line 121. > not ok 6 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 7 - guc fw -dcpriv exits with 0 > # Failed test 'guc fw -dcpriv exits with 0' > # at ./guc-fw.pl line 121. > not ok 8 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 9 - guc fw -fast -nodcau exits with 0 > # Failed test 'guc fw -fast -nodcau exits with 0' > # at ./guc-fw.pl line 121. > not ok 10 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 11 - guc fw -fast exits with 0 > # Failed test 'guc fw -fast exits with 0' > # at ./guc-fw.pl line 121. > not ok 12 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 13 - guc fw -fast -dcsafe exits with 0 > # Failed test 'guc fw -fast -dcsafe exits with 0' > # at ./guc-fw.pl line 121. > not ok 14 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 15 - guc fw -fast -dcpriv exits with 0 > # Failed test 'guc fw -fast -dcpriv exits with 0' > # at ./guc-fw.pl line 121. > not ok 16 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. > > # > not ok 17 - guc fw -p 2 -nodcau exits with 0 > # Failed test 'guc fw -p 2 -nodcau exits with 0' > # at ./guc-fw.pl line 121. > not ok 18 - guc-fw data compare > # Failed test 'guc-fw data compare' > # at ./guc-fw.pl line 124. > # stderr: > # > # error: globus_ftp_client: the server responded with an error > # 530 Login incorrect. : Access denied, user's system account is disabled. >
Bug#917729: weresync: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
Source: weresync Version: 1.0.7-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3,sphinxdoc --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:217: python3.7 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.7/build' (and everything under > it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-3.7' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building weresync using existing > ./weresync_1.0.7.orig.tar.gz > dpkg-source: error: cannot represent change to > src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo: binary file > contents changed > dpkg-source: error: add > src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2018-12-29T12:40:29Z The full build log is available from: http://aws-logs.debian.net/2018/12/29/weresync_1.0.7-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#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85,13] cannot find symbol
Source: openhft-lang Version: 6.7.6-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-lang-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] OpenHFT/Java-Lang/lang > [bundle] > [INFO] Java Lang Parent > [pom] > [INFO] > [INFO] --< net.openhft:lang > >-- > [INFO] Building OpenHFT/Java-Lang/lang 6.7.6 > [1/2] > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ lang > --- > [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory > /<>/lang/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lang --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 165 source files to /<>/lang/target/classes > [INFO] > /<>/lang/src/main/java/net/openhft/lang/model/DataValueClassCache.java: > Some input files use or override a deprecated API. > [INFO] > /<>/lang/src/main/java/net/openhft/lang/model/DataValueClassCache.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/lang/src/main/java/net/openhft/lang/locks/NativeAtomicAccess.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/lang/src/main/java/net/openhft/lang/locks/NativeAtomicAccess.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/NativeBytes.java:[22,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/ChronicleUnsafe.java:[20,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/MappedMemory.java:[21,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/DirectByteBufferBytes.java:[18,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/MappedNativeBytes.java:[21,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/lang/src/main/java/net/openhft/lang/io/VanillaMappedBytes.java:[19,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNIN
Bug#917720: sunpy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13
Source: sunpy Version: 0.9.5-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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.7 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy > copying sunpy/__init__.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy > copying sunpy/version.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy > copying sunpy/conftest.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy > creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/aia.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/rhessi.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/goes.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/lyra.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/__init__.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > copying sunpy/instr/fermi.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr > creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/mapcube.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/mapbase.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/__init__.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/map_factory.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/compositemap.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > copying sunpy/map/mapsequence.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map > creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/xml.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/create.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/cond_dispatch.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/sysinfo.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/multimethod.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/__init__.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/scraper.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/metadata.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/config.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/exceptions.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/net.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/datatype_factory_base.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/progressbar.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/decorators.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > copying sunpy/util/util.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util > creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/wcs_utils.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/offset_frame.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/frames.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/__init__.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/utils.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/frameattributes.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/ephemeris.py -> > /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates > copying sunpy/coordinates/transformations.py -> >
Bug#917715: openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2
Source: openconnect Version: 7.08-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/tests' > FAIL: auth-username-pass > FAIL: auth-certificate > FAIL: id-test > FAIL: auth-pkcs11 > PASS: seqtest > PASS: lzstest > >openconnect 7.08: tests/test-suite.log > > > # TOTAL: 6 > # PASS: 2 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 4 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: auth-username-pass > > > Testing certificate auth... > warning: skipping unknown option 'cookie-validity' > Parsing plain auth method subconfig using legacy format > note: setting 'plain' as primary authentication method > note: setting 'file' as supplemental config option > listening (TCP) on 0.0.0.0:443... > listening (TCP) on [::]:443... > listening (UDP) on 0.0.0.0:443... > listening (UDP) on [::]:443... > ocserv[13182]: main: not using control unix socket > ocserv[13182]: main: initialized ocserv 0.12.1 > ocserv[13186]: sec-mod: reading supplemental config from files > ocserv[13186]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.51a94d1b) > Connecting to obtain cookie... ocserv[13221]: GnuTLS error (at > worker-vpn.c:795): No supported cipher suites have been found. > Failure: Could not receive cookie from server > ocserv[13182]: main: termination request received; waiting for children to die > ocserv[13182]: main:127.0.0.2:23190 user disconnected (reason: unspecified, > rx: 0, tx: 0) > FAIL auth-username-pass (exit status: 1) > > FAIL: auth-certificate > == > > Testing certificate auth... > warning: skipping unknown option 'cookie-validity' > Parsing plain auth method subconfig using legacy format > note: setting 'certificate+plain' as primary authentication method > note: setting 'file' as supplemental config option > listening (TCP) on 0.0.0.0:443... > listening (TCP) on [::]:443... > listening (UDP) on 0.0.0.0:443... > listening (UDP) on [::]:443... > ocserv[13184]: main: not using control unix socket > ocserv[13184]: main: initialized ocserv 0.12.1 > ocserv[13187]: sec-mod: reading supplemental config from files > ocserv[13187]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.6c6705ae) > Connecting to obtain cookie (with key user-key-pkcs1.pem)... ocserv[13220]: > GnuTLS error (at worker-vpn.c:795): No supported cipher suites have been > found. > ocserv[13184]: main:127.0.0.2:23193 user disconnected (reason: unspecified, > rx: 0, tx: 0) > SSL connection failure: The TLS connection was non-properly terminated. > Failed to open HTTPS connection to 127.0.0.2 > Failed to obtain WebVPN cookie > Failure: Could not connect with key user-key-pkcs1.pem! > ocserv[13184]: main: termination request received; waiting for children to die > FAIL auth-certificate (exit status: 1) > > FAIL: id-test > = > > Testing certificate auth... > Connecting with legacy hash... Failure: Could not receive cookie from server > FAIL id-test (exit status: 1) > > FAIL: auth-pkcs11 > = > > Testing PKCS#11 auth... > warning: skipping unknown option 'cookie-validity' > Parsing plain auth method subconfig using legacy format > note: setting 'certificate+plain' as primary authentication method > note: setting 'file' as supplemental config option > listening (TCP) on 0.0.0.0:443... > listening (TCP) on [::]:443... > listening (UDP) on 0.0.0.0:443... > listening (UDP) on [::]:443... > ocserv[13242]: main: not using control unix socket > ocserv[13242]: main: initialized ocserv 0.12.1 > ocserv[13245]: sec-mod: reading supplemental config from files > ocserv[13245]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.ea41c786) > Connecting to obtain cookie (token openconnect-test key object=RSA)... > ocserv[13281]: GnuTLS error (at worker-vpn.c:795): No supported cipher suites > have been found. > SSL connection failure: The TLS connection was non-properly terminated. > ocserv[13242]: main:127.0.0.2:23259 user disconnected (reason: unspecified, > rx: 0, tx: 0) > Failed to open HTTPS connection to 127.0.0.2 > Failed to obtain WebVPN cookie > Failure: Could not connect with token openconnect-test key object=RSA! > ocserv[13242]: main: termination request received; waiting for children to die > FAIL auth-pkcs11 (exit status: 1) > >
Bug#917719: libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2
Source: libbio-tools-run-alignment-tcoffee-perl Version: 1.7.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/00-compile.t ... > 1..1 > ok 1 - Bio/Tools/Run/Alignment/TCoffee.pm loaded ok > ok > t/author-eol.t ... skipped: these tests are for testing by the author > t/author-mojibake.t .. skipped: these tests are for testing by the author > t/author-no-tabs.t ... skipped: these tests are for testing by the author > t/author-pod-coverage.t .. skipped: these tests are for testing by the author > t/author-pod-syntax.t skipped: these tests are for testing by the author > > > * > *FULL TRACE BACK PID: 16494 > > 16518 -- ERROR: COREDUMP: T-COFFEE Version_12.00.7fb08c2 (2018-12-11 09:27:12 > - Revision 7fb08c2 - Build 211) > * > > ** > * Abnormal Termination > * Job NOT Completed:[T-COFFEE, Version_12.00.7fb08c2] > * Please CHECK: > * -1 The format of your Input Files > * -2 The parameters > * -3 The use of special characters in sequence names: > *(@, |, %...) > * -4 The Online Doc (http://www.tcoffee.org) > * -5 re-run your CL (see below) with the -debug option. This will > produce a debug file you can send us. > * > * NO > * to: > * cedric.notred...@gmail.com > * If you run T-Coffee over the WEB: > * Windows Cut and Paste is sometimes erratic and > * it can loose carriage returns. If you suspect this, > * try to cut and paste through an intermediate application > * (word pad) and inspect the results > > > * CONFIDENTIALITY: > * The File NO may contain your personal DATA > * Remove ALL confidential DATA from this file BEFORE sending it > ** > # Command Line: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix > blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile > /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet [PROGRAM:T-COFFEE] > > # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 16494 ppid 16412 > #CL: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix blosum > -method lalign_id_pair clustalw_pair -ktuple 3 -outfile > /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet > ERROR: /var/tmp/tco/tcouusjjsfj16494/9295616514392 FILE is NOT a supported > format [ERROR] > # Failed test at t/TCoffee.t line 74. > # died: > # - EXCEPTION - > # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee > -profile=C3uHd27Vnl -seq=rKVo1aRtb4 -matrix=blosum > -method=lalign_id_pair,clustalw_pair -ktuple=3 > -outfile=/tmp/D_LRrJQoYx/TbKy3eG8L7 -output=clustalw -quiet] > # > # STACK Bio::Root::RootI::warn /usr/share/perl5/Bio/Root/RootI.pm:150 > # STACK Bio::Tools::Run::Alignment::TCoffee::_run > /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:272 > # STACK Bio::Tools::Run::Alignment::TCoffee::profile_align > /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:198 > # STACK Test::Exception::lives_ok t/TCoffee.t:74 > # STACK toplevel t/TCoffee.t:74 > # - > # Failed test 'no T-COFFEE errors' > # at t/TCoffee.t line 76. > sh: 1: cannot create /var/tmp/tco/tcouusjjsfj16494/9295616494252: Directory > nonexistent > > --COULD NOT READ > /<>/debian/build//.t_coffee//cache//var/tmp/tco/tcouusjjsfj16494//9295616494252 > > --ERROR: FORCED EXIT (NON INTERACTIVE MODE pid 16516) > > COULD NOT Append anything to /var/tmp/tco/tcouusjjsfj16494//9295616513411 > > --COULD NOT READ > /<>/debian/build//.t_coffee//cache//var/tmp/tco/tcouusjjsfj16494//9295616513411 > > --ERROR: FORCED EXIT (NON INTERACTIVE MODE pid 16513) > > COULD NOT Append
Bug#917721: libbiod: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1
Source: libbiod Version: 0.2.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dpkg-query: no packages found matching gdc > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.49.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: BioD > Project version: 0.2.2 > Appending DFLAGS from environment: '-O -g -release -wi' > Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now' > Native D compiler: ldc2 (llvm 1.12.0 "LDC - the LLVM D compiler (1.12.0):") > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29) > Dependency undead found: YES 1.0.7 > Dependency zlib found: YES 1.2.11 > Build targets in project: 2 > Found ninja-1.8.2 at /usr/bin/ninja >dh_auto_build > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v > [1/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_bai_bin.d.o' -c > ../bio/bam/bai/bin.d > [2/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic > -of='biod@sha/bio_bam_abstractreader.d.o' -c ../bio/bam/abstractreader.d > [3/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_baifile.d.o' -c > ../bio/bam/baifile.d > [4/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_baseinfo.d.o' -c > ../bio/bam/baseinfo.d > [5/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_cigar.d.o' -c > ../bio/bam/cigar.d > [6/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_constants.d.o' -c > ../bio/bam/constants.d > [7/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_bai_indexing.d.o' > -c ../bio/bam/bai/indexing.d > [8/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic > -of='biod@sha/bio_bam_iontorrent_flowindex.d.o' -c > ../bio/bam/iontorrent/flowindex.d > [9/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_md_core.d.o' -c > ../bio/bam/md/core.d > [10/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic > -of='biod@sha/bio_bam_iontorrent_flowcall.d.o' -c > ../bio/bam/iontorrent/flowcall.d > [11/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_md_operation.d.o' > -c ../bio/bam/md/operation.d > [12/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic > -of='biod@sha/bio_bam_md_reconstruct.d.o' -c ../bio/bam/md/reconstruct.d > [13/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_md_parse.d.o' -c > ../bio/bam/md/parse.d > [14/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_pileup.d.o' -c > ../bio/bam/pileup.d > [15/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic > -of='biod@sha/bio_bam_randomaccessmanager.d.o' -c > ../bio/bam/randomaccessmanager.d > [16/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_multireader.d.o' > -c ../bio/bam/multireader.d > [17/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_read.d.o' -c > ../bio/bam/read.d > [18/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g > -release -wi -relocation-model=pic -of='biod@sha/bio_bam_readrange.d.o' -c > ../bio/bam/readrange.d > [19/177] ldc2 -I=biod@sha -I=.
Bug#917714: lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirec
Source: lizzie Version: 0.6+dfsg1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>/lizzie-0.6+dfsg1' > HOME=/<>/lizzie-0.6+dfsg1/debian/runtest xvfb-run -a dh_auto_test > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian > -Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo > --batch-mode test > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] -< featurecat:lizzie > >-- > [INFO] Building lizzie 0.6 > [INFO] [ jar > ]- > [WARNING] The artifact org.json:json:jar:debian-latest has been relocated to > org.json:json:jar:debian > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > lizzie --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 7 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lizzie --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) > @ lizzie --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /<>/lizzie-0.6+dfsg1/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ > lizzie --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ lizzie --- > [INFO] > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running featurecat.lizzie.rules.SGFParserTest > Creating config file /home/user42/.config/leela-zero/lizzie-config.txt > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.072 > s <<< FAILURE! - in featurecat.lizzie.rules.SGFParserTest > [ERROR] run(featurecat.lizzie.rules.SGFParserTest) Time elapsed: 0.03 s <<< > ERROR! > java.io.IOException: No such file or directory > at featurecat.lizzie.rules.SGFParserTest.run(SGFParserTest.java:24) > > [INFO] Running featurecat.lizzie.analysis.MoveDataTest > [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 > s - in featurecat.lizzie.analysis.MoveDataTest > [INFO] > [INFO] Results: > [INFO] > [ERROR] Errors: > [ERROR] SGFParserTest.run:24 ? IO No such file or directory > [INFO] > [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 > [INFO] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 11.280 s > [INFO] Finished at: 2018-12-29T12:16:43Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test (default-test) on > project lizzie: There are test failures. > [ERROR] > [ERROR] Please refer to > /<>/lizzie-0.6+dfsg1/target/surefire-reports for the individual > test results. > [ERROR] Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
Bug#917722: pybind11: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 check ARGS\+=-j2 returned exit code 2
Source: pybind11 Version: 2.2.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/tests && /usr/bin/python3.7 -m pytest test_buffers.py > test_builtin_casters.py test_call_policies.py test_callbacks.py > test_chrono.py test_class.py test_constants_and_functions.py > test_copy_move.py test_docstring_options.py test_eigen.py test_enum.py > test_eval.py test_exceptions.py test_factory_constructors.py test_iostream.py > test_kwargs_and_defaults.py test_local_bindings.py > test_methods_and_attributes.py test_modules.py test_multiple_inheritance.py > test_numpy_array.py test_numpy_dtypes.py test_numpy_vectorize.py > test_opaque_types.py test_operator_overloading.py test_pickling.py > test_pytypes.py test_sequences_and_iterators.py test_smart_ptr.py test_stl.py > test_stl_binders.py test_virtual_functions.py > [100%] Built target test_cmake_build > = test session starts > == > platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 > rootdir: /<>/tests, inifile: pytest.ini > collected 298 items > > test_buffers.py [ > 1%] > test_builtin_casters.py s. [ > 6%] > test_call_policies.py . [ > 9%] > test_callbacks.py ...[ > 11%] > test_chrono.py ... [ > 13%] > test_class.py ...[ > 18%] > test_constants_and_functions.py [ > 20%] > test_copy_move.py s..[ > 22%] > test_docstring_options.py . [ > 22%] > test_eigen.py F [ > 31%] > test_enum.py . [ > 32%] > test_eval.py . [ > 33%] > test_exceptions.py ... [ > 35%] > test_factory_constructors.py . [ > 38%] > test_iostream.py [ > 42%] > test_kwargs_and_defaults.py .[ > 44%] > test_local_bindings.py ..[ > 47%] > test_methods_and_attributes.py [ > 54%] > test_modules.py .[ > 56%] > test_multiple_inheritance.py ... [ > 59%] > test_numpy_array.py .[ > 70%] > test_numpy_dtypes.py [ > 74%] > test_numpy_vectorize.py ... [ > 77%] > test_opaque_types.py .. [ > 77%] > test_operator_overloading.py ... [ > 78%] > test_pickling.py [ > 80%] > test_pytypes.py ... [ > 83%] > test_sequences_and_iterators.py .. [ > 85%] > test_smart_ptr.py ...[ > 89%] > test_stl.py ...ss. [ > 94%] > test_stl_binders.py .[ > 97%] > test_virtual_functions.py > [100%] > > === FAILURES > === > _ test_sparse > __ > > @pytest.requires_eigen_and_scipy > def test_sparse(): > > assert_sparse_equal_ref(m.sparse_r()) > > test_eigen.py:646: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > /usr/lib/python3/dist-packages/scipy/sparse/__init__.py:231: in > from .lil import * > /usr/lib/python3/dist-packages/scipy/sparse/lil.py:19: in > from . import _csparsetools > _ _ _ _
Bug#917718: libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
Source: libuv1 Version: 1.24.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > 1..343 > ok 1 - platform_output > # Output from process `platform_output`: > # uv_get_process_title: /<>/test/.libs/run-tests > # uv_cwd: /<> > # uv_resident_set_memory: 1069056 > # uv_uptime: 7932.00 > # uv_getrusage: > # user: 0 sec 0 microsec > # system: 0 sec 0 microsec > # page faults: 0 > # maximum resident set size: 1044 > # uv_cpu_info: > # model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz > # speed: 2500 > # times.sys: 6262800 > # times.user: 60641700 > # times.idle: 10290400 > # times.irq: 0 > # times.nice: 0 > # model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz > # speed: 2500 > # times.sys: 6210200 > # times.user: 59260500 > # times.idle: 11656300 > # times.irq: 0 > # times.nice: 0 > # uv_interface_addresses: > # name: lo > # internal: 1 > # physical address: 00:00:00:00:00:00 > # address: 127.0.0.1 > # netmask: 255.0.0.0 > # name: eth0 > # internal: 0 > # physical address: 06:c0:2d:38:cd:2c > # address: 172.31.2.71 > # netmask: 255.255.240.0 > # name: lo > # internal: 1 > # physical address: 00:00:00:00:00:00 > # address: ::1 > # netmask: ::::::: > # name: eth0 > # internal: 0 > # physical address: 06:c0:2d:38:cd:2c > # address: fe80::4c0:2dff:fe38:cd2c > # netmask: ::::: > # uv_os_get_passwd: > # euid: 1001 > # gid: 1001 > # username: user42 > # shell: > # home directory: /home/user42 > # uv_os_getpid: 14358 > # uv_os_getppid: 14344 > ok 2 - active > ok 3 - async > ok 4 - async_null_cb > ok 5 - async_ref > ok 6 - barrier_1 > ok 7 - barrier_2 > ok 8 - barrier_3 > ok 9 - barrier_serial_thread > ok 10 - barrier_serial_thread_single > ok 11 - callback_stack > ok 12 - check_ref > ok 13 - close_fd > ok 14 - close_order > ok 15 - closed_fd_events > ok 16 - condvar_1 > ok 17 - condvar_2 > ok 18 - condvar_3 > ok 19 - condvar_4 > ok 20 - condvar_5 > ok 21 - connect_unspecified > ok 22 - connection_fail > ok 23 - connection_fail_doesnt_auto_close > ok 24 - cwd_and_chdir > ok 25 - default_loop_close > ok 26 - delayed_accept > ok 27 - dlerror > ok 28 - eintr_handling > ok 29 - embed > ok 30 - emfile > ok 31 - env_vars > ok 32 - error_message > ok 33 - fork_fs_events_child > ok 34 - fork_fs_events_child_dir > ok 35 - fork_fs_events_file_parent_child > ok 36 - fork_signal_to_child > ok 37 - fork_signal_to_child_closed > ok 38 - fork_socketpair > ok 39 - fork_socketpair_started > ok 40 - fork_threadpool_queue_work_simple > ok 41 - fork_timer > ok 42 - fs_access > ok 43 - fs_async_dir > ok 44 - fs_async_sendfile > ok 45 - fs_chmod > ok 46 - fs_chown > ok 47 - fs_copyfile > ok 48 - fs_event_close_in_callback > ok 49 - fs_event_close_with_pending_event > ok 50 - fs_event_error_reporting > ok 51 - fs_event_getpath > ok 52 - fs_event_immediate_close > ok 53 - fs_event_no_callback_after_close > ok 54 - fs_event_no_callback_on_close > ok 55 - fs_event_ref > ok 56 - fs_event_start_and_close > ok 57 - fs_event_watch_dir > ok 58 - fs_event_watch_dir_recursive # SKIP Recursive directory watching not > supported on this platform. > ok 59 - fs_event_watch_file > ok 60 - fs_event_watch_file_current_dir > ok 61 - fs_event_watch_file_exact_path > ok 62 - fs_event_watch_file_twice > ok 63 - fs_event_watch_invalid_path > ok 64 - fs_file_async > ok 65 - fs_file_loop > ok 66 - fs_file_nametoolong > ok 67 - fs_file_noent > ok 68 - fs_file_open_append > ok 69 - fs_file_pos_after_op_with_offset > ok 70 - fs_file_sync > ok 71 - fs_file_write_null_buffer > ok 72 - fs_fstat > ok 73 - fs_futime > ok 74 - fs_mkdtemp > ok 75 - fs_null_req > ok 76 - fs_open_dir > ok 77 - fs_partial_read > ok 78 - fs_partial_write > ok 79 - fs_poll > ok 80 - fs_poll_getpath > ok 81 - fs_poll_ref > ok 82 - fs_read_dir > ok 83 - fs_read_file_eof > ok 84 - fs_read_write_null_arguments > ok 85 - fs_readlink > ok 86 - fs_realpath > ok 87 - fs_rename_to_existing_file > ok 88 - fs_scandir_empty_dir > ok 89 - fs_scandir_file > ok 90 - fs_scandir_non_existent_dir > ok 91 - fs_stat_missing_path > ok 92 - fs_symlink > ok 93 - fs_symlink_dir > ok 94 - fs_unlink_readonly > ok 95 - fs_utime > ok 96 - fs_write_alotof_bufs > ok 97 - fs_write_alotof_bufs_with_offs
Bug#917713: pyscanfcs: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
Source: pyscanfcs Version: 0.3.2+ds-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>/pyscanfcs-0.3.2+ds' > cd doc && \ > ( faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex \ > bibtex PyScanFCS_doc.aux \ > faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex \ > faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex \ > ) > This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./PyScanFCS_doc.tex > LaTeX2e <2018-12-01> > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls > Document Class: scrartcl 2018/03/30 v3.25 KOMA-Script document class (article) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize12pt.clo) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def)) > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > (/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def) > (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def > (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def > (/usr/share/texlive/texmf-dist/tex/latex/SIstyle/sistyle.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty > For additional information on amsmath, use the `?' option. > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) > (/usr/share/texlive/texmf-dist/tex/latex/cite/cite.sty) > (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty) > (/usr/share/texlive/texmf-dist/tex/latex/subfig/subfig.sty > (/usr/share/texlive/texmf-dist/tex/latex/caption/caption.sty > (/usr/share/texlive/texmf-dist/tex/latex/caption/caption3.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def)) > (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/svgnam.def)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty) > (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg) > > Package hyperref Warning: Unexpected value for option `pdftex' > (hyperref)is ignored on input line 4393. > > ) (/usr/share
Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13
Source: pylint-django
Version: 2.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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="PYTHONDONTWRITEBYTECODE=1
> PYTHONPATH=. {interpreter} pylint_django/tests/test_func.py" dh_auto_test
> I: pybuild base:217: PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7
> pylint_django/tests/test_func.py
> = test session starts
> ==
> platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>, inifile:
> collected 0 items / 1 errors
>
> ERRORS
>
> __ ERROR collecting pylint_django/tests/test_func.py
> ___
> ImportError while importing test module
> '/<>/pylint_django/tests/test_func.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> pylint_django/__init__.py:6: in
> from pylint_django import plugin
> pylint_django/plugin.py:5: in
> from pylint_django.checkers import register_checkers
> pylint_django/checkers/__init__.py:3: in
> from pylint_django.checkers.models import ModelChecker
> pylint_django/checkers/models.py:11: in
> from pylint_django.utils import node_is_subclass, PY3
> pylint_django/utils.py:4: in
> from astroid.util import YES
> E ImportError: cannot import name 'YES' from 'astroid.util'
> (/usr/lib/python3/dist-packages/astroid/util.py)
> !!! Interrupted: 1 errors during collection
>
> === 1 error in 0.07 seconds
>
> E: pybuild pybuild:338: test: plugin custom failed with: exit code=2:
> PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7
> pylint_django/tests/test_func.py
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned
> exit code 13
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/pylint-django_2.0.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.
Processed: severity of 913631 is serious
Processing commands for cont...@bugs.debian.org: > severity 913631 serious Bug #913631 [src:libapache2-mod-auth-openidc] FTBFS: libapache2-mod-auth-openidc on multiple arches Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 913631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#879538: mandos: (tries to) use GnuTLS OpenPGP support
Processing commands for cont...@bugs.debian.org: > severity 879538 grave Bug #879538 [mandos] mandos: (tries to) use GnuTLS OpenPGP support Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 879538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917711: grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2
Source: grantlee5 Version: 5.1.0-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j2 > Test project /<>/obj-x86_64-linux-gnu > Start 1: testsafestring > Start 2: testbuiltins > 1/12 Test #1: testsafestring ... Passed0.00 sec > Start 3: testloadertags > 2/12 Test #3: testloadertags ... Passed0.02 sec > Start 4: testdefaulttags > 3/12 Test #2: testbuiltins . Passed0.04 sec > Start 5: testcachingloader > 4/12 Test #5: testcachingloader Passed0.01 sec > Start 6: testfilters > 5/12 Test #6: testfilters ..***Failed0.03 sec > * Start testing of TestFilters * > Config: Using QtTest library 5.11.3, Qt 5.11.3 (x86_64-little_endian-lp64 > shared (dynamic) release build; by GCC 8.2.0) > PASS : TestFilters::initTestCase() > PASS : TestFilters::testDateBasedFilters(filter-timesince01) > PASS : TestFilters::testDateBasedFilters(filter-timesince02) > PASS : TestFilters::testDateBasedFilters(filter-timesince03) > PASS : TestFilters::testDateBasedFilters(filter-timesince04) > PASS : TestFilters::testDateBasedFilters(filter-timesince05) > PASS : TestFilters::testDateBasedFilters(filter-timesince07) > PASS : TestFilters::testDateBasedFilters(filter-timesince08) > PASS : TestFilters::testDateBasedFilters(filter-timesince09) > PASS : TestFilters::testDateBasedFilters(filter-timesince10) > PASS : TestFilters::testDateBasedFilters(filter-timesince17) > PASS : TestFilters::testDateBasedFilters(filter-timesince18) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil01) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil02) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil03) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil04) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil05) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil06) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil07) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil08) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil09) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil12) > PASS : TestFilters::testDateBasedFilters(filter-timeuntil13) > FAIL! : TestFilters::testDateBasedFilters(date01) Compared values are not > the same >Actual (result): "" >Expected (output): "01" >Loc: [/<>/templates/tests/testfilters.cpp(117)] > FAIL! : TestFilters::testDateBasedFilters(date02) Compared values are not > the same >Actual (result): "" >Expected (output): "Jan. 1, 2008" >Loc: [/<>/templates/tests/testfilters.cpp(117)] > PASS : TestFilters::testDateBasedFilters(date03) > PASS : TestFilters::testStringFilters(filter-addslash01) > PASS : TestFilters::testStringFilters(filter-addslash02) > PASS : TestFilters::testStringFilters(filter-capfirst01) > PASS : TestFilters::testStringFilters(filter-capfirst02) > PASS : TestFilters::testStringFilters(filter-fix_ampersands01) > PASS : TestFilters::testStringFilters(filter-fix_ampersands02) > PASS : TestFilters::testStringFilters(filter-floatformat01) > PASS : TestFilters::testStringFilters(filter-floatformat02) > PASS : TestFilters::testStringFilters(filter-linenumbers01) > PASS : TestFilters::testStringFilters(filter-linenumbers02) > PASS : TestFilters::testStringFilters(filter-lower01) > PASS : TestFilters::testStringFilters(filter-lower02) > PASS : TestFilters::testStringFilters(filter-make_list01) > PASS : TestFilters::testStringFilters(filter-make_list02) > PASS : TestFilters::testStringFilters(filter-make_list03) > PASS : TestFilters::testStringFilters(filter-make_list04) > PASS : TestFilters::testStringFilters(filter-slugify01) > PASS : TestFilters::testStringFilters(filter-slugify02) > PASS : TestFilters::testStringFilters(filter-slugify03) > PASS : TestFilters::testStringFilters(escapejs01) > PASS : TestFilters::testStringFilters(escapejs02) > PASS : TestFilters::testStringFilters(filter-stringformat01) > PASS : TestFilters::testStringFilters(filter-stringformat02) > PASS : TestFilters::testStringFilters(filter-stringformat03) > PASS : TestFilters::testStringFilters(filter-stringformat04) > PASS : TestFilters::testStringFilters(filter-title01) > P
Bug#917710: bolt: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1
Source: bolt Version: 0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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_configure -- \ > --libexecdir=/usr/lib/bolt \ > -Dman=true \ > -Dprivileged-group=sudo > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/bolt -Dman=true > -Dprivileged-group=sudo > The Meson build system > Version: 0.49.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: bolt > Project version: 0.5 > 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 -Wl,-z,defs > -Wl,--as-needed' > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.2.0-13) 8.2.0") > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Compiler for C supports arguments -fstack-protector-strong: YES > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Wunused: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-nonliteral: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers > -Wdiscarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers > -Wmissing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-aliasing -Wstrict-aliasing: YES > Compiler for C supports arguments -Wno-suggest-attribute=format > -Wsuggest-attribute=format: YES > Compiler for C supports arguments -Wno-unused-parameter -Wunused-parameter: > YES > Compiler for C supports arguments -Wold-style-definition: YES > Compiler for C supports arguments -Woverride-init: YES > Compiler for C supports arguments -Wpointer-arith: YES > Compiler for C supports arguments -Wredundant-decls: YES > Compiler for C supports arguments -Wreturn-type: YES > Compiler for C supports arguments -Wshadow: YES > Compiler for C supports arguments -Wsign-compare: YES > Compiler for C supports arguments -Wstrict-aliasing: YES > Compiler for C supports arguments -Wstrict-prototypes: YES > Compiler for C supports arguments -Wtype-limits: YES > Compiler for C supports arguments -Wundef: YES > Compiler for C supports arguments -Wuninitialized: YES > Compiler for C supports arguments -Wunused-but-set-variable: YES > Compiler for C supports arguments -Wwrite-strings: YES > Found pkg-config: /usr/bin/pkg-config (0.29) > Dependency glib-2.0 found: YES 2.58.1 > Dependency gio-2.0 found: YES 2.58.1 > Dependency libudev found: YES 240 > Dependency gio-unix-2.0 found: YES 2.58.1 > Dependency udev found: YES 240 > Dependency polkit-gobject-1 found: YES 0.105 > Dependency umockdev-1.0 found: YES 0.12.1 > Program git found: NO > Program a2x found: YES (/usr/bin/a2x) > Dependency systemd found: YES 240 > Checking for function "explicit_bzero" : YES > Checking for function "getrandom" : YES > Configuring config.h using configuration > Configuring org.freedesktop.bolt.service using configuration > Configuring org.freedesktop.bolt.rules using configuration > Configuring org.freedesktop.bolt.policy using configuration > Configuring bolt.service using conf
Bug#917708: gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1
Source: gnome-settings-daemon
Version: 3.30.1.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 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 '/<>'
> xvfb-run dh_auto_test
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test
> [0/1] Running all tests.
> 1/3 gcm-self-test FAIL 0.02 s (killed by signal
> 6 SIGABRT)
> 2/3 test-power OK 0.12 s
> 3/3 test-xsettings OK 0.12 s
>
> Ok:2
> Expected Fail: 0
> Fail: 1
> Unexpected Pass: 0
> Skipped: 0
> Timeout: 0
>
>
> The output from the failed tests:
>
> 1/3 gcm-self-test FAIL 0.02 s (killed by signal
> 6 SIGABRT)
>
> --- command ---
> GSETTINGS_SCHEMA_DIR='/<>/obj-x86_64-linux-gnu/data'
> /<>/obj-x86_64-linux-gnu/plugins/color/gcm-self-test
> --- stdout ---
> /color/edid:
> --- stderr ---
> **
> ERROR:../plugins/color/gcm-self-test.c:243:gcm_test_edid_func: assertion
> failed (gcm_edid_get_vendor_name (edid) == "Goldstar Company Ltd"): ("LG
> Electronics" == "Goldstar Company Ltd")
> ---
>
> Full log written to
> /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
> FAILED: meson-test
> /usr/bin/meson test --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2
> ninja test returned exit code 1
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/gnome-settings-daemon_3.30.1.2-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.
Processed: severity of 907713 is serious
Processing commands for cont...@bugs.debian.org: > # FTBFS on AMD64 > severity 907713 serious Bug #907713 [src:golang-github-fsouza-go-dockerclient] golang-github-fsouza-go-dockerclient: FTBFS in buster/sid (failing tests) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 907713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917707: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/gin
Source: golang-github-gin-gonic-gin Version: 1.3.0+dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install > -gcflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\" > > -asmflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\" > -v -p 2 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json > github.com/gin-gonic/gin/render > errors > internal/race > internal/cpu > runtime/internal/atomic > runtime/internal/sys > sync/atomic > unicode > runtime > unicode/utf8 > crypto/subtle > math > strconv > encoding > internal/testlog > unicode/utf16 > math/bits > container/list > crypto/internal/cipherhw > crypto/rc4 > vendor/golang_org/x/crypto/cryptobyte/asn1 > internal/nettrace > runtime/cgo > vendor/golang_org/x/crypto/poly1305 > vendor/golang_org/x/crypto/curve25519 > sync > io > reflect > bytes > bufio > syscall > time > encoding/binary > encoding/base64 > strings > internal/poll > sort > os > hash > hash/crc32 > crypto/cipher > crypto/aes > fmt > path/filepath > io/ioutil > internal/syscall/unix > math/rand > crypto > encoding/xml > encoding/json > compress/flate > context > math/big > compress/gzip > crypto/des > crypto/sha512 > crypto/hmac > crypto/md5 > crypto/sha1 > crypto/sha256 > encoding/hex > crypto/rand > crypto/elliptic > encoding/asn1 > crypto/rsa > crypto/ecdsa > crypto/dsa > crypto/x509/pkix > encoding/pem > vendor/golang_org/x/crypto/cryptobyte > internal/singleflight > net > net/url > vendor/golang_org/x/crypto/chacha20poly1305/internal/chacha20 > vendor/golang_org/x/crypto/chacha20poly1305 > vendor/golang_org/x/net/http2/hpack > vendor/golang_org/x/text/transform > log > vendor/golang_org/x/text/unicode/bidi > vendor/golang_org/x/text/secure/bidirule > vendor/golang_org/x/text/unicode/norm > vendor/golang_org/x/net/idna > mime > mime/quotedprintable > net/http/internal > path > github.com/gin-gonic/gin/json > github.com/golang/protobuf/proto > crypto/x509 > crypto/tls > vendor/golang_org/x/net/lex/httplex > vendor/golang_org/x/net/proxy > net/textproto > mime/multipart > encoding/gob > net/http/httptrace > net/http > html > text/template/parse > text/template > html/template > regexp/syntax > regexp > gopkg.in/go-playground/validator.v8 > github.com/gin-contrib/sse > net/rpc > gopkg.in/yaml.v2 > github.com/ugorji/go/codec > github.com/mattn/go-isatty > net/http/httputil > github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/render > github.com/gin-gonic/gin > github.com/gin-gonic/gin/ginS >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 > github.com/gin-gonic/gin github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json > github.com/gin-gonic/gin/render > === RUN TestBasicAuth > --- PASS: TestBasicAuth (0.00s) > === RUN TestBasicAuthFails > --- PASS: TestBasicAuthFails (0.00s) > === RUN TestBasicAuthSearchCredential > --- PASS: TestBasicAuthSearchCredential (0.00s) > === RUN TestBasicAuthAuthorizationHeader > --- PASS: TestBasicAuthAuthorizationHeader (0.00s) > === RUN TestBasicAuthSecureCompare > --- PASS: TestBasicAuthSecureCompare (0.00s) > === RUN TestBasicAuthSucceed > --- PASS: TestBasicAuthSucceed (0.00s) > === RUN TestBasicAuth401 > --- PASS: TestBasicAuth401 (0.00s) > === RUN TestBasicAuth401WithCustomRealm > --- PASS: TestBasicAuth401WithCustomRealm (0.00s) > === RUN TestContextFormFile > --- PASS: TestContextFormFile (0.00s) > === RUN TestContextMultipartForm > --- PASS: TestContextMultipartForm (0.00s) > === RUN TestSaveUploadedOpenFailed > --- PASS: TestSaveUploadedOpenFailed (0.00s) > === RUN TestSaveUploadedCreateFailed > --- PASS: TestSaveUploadedCreateFailed (0.00s) > === RUN TestContextReset > --- PASS: TestContextReset (0.00s) > === RUN TestContextHandlers > --- PASS: TestContextHandlers (0.00s) > === RUN TestContextSetG
Bug#917712: gitano: FTBFS: dh_auto_test: make -j1 test returned exit code 2
Source: gitano Version: 1.1.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 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 '/<>' > NOTE: Coverage gathering is not enabled > /usr/bin/luac5.1 -p plugins/rsync.lua plugins/archive.lua > plugins/git-annex.lua plugins/testing-hooks.lua plugins/demo.lua > plugins/git-multimail.lua > for PLUGIN in plugins/rsync.lua plugins/archive.lua plugins/git-annex.lua > plugins/testing-hooks.lua plugins/demo.lua; do \ > env LUA_PATH="/<>/lib/?.lua;;" /usr/bin/lua5.1 $PLUGIN; \ > done > Running full yarns in 'ssh' mode > Parsing scenario file testing/library.yarn > Parsing scenario file testing/01-basics.yarn > Parsing scenario file testing/01-hooks.yarn > Parsing scenario file testing/02-commands-as.yarn > Parsing scenario file testing/02-commands-config.yarn > Parsing scenario file testing/02-commands-copy.yarn > Parsing scenario file testing/02-commands-count-objects.yarn > Parsing scenario file testing/02-commands-create.yarn > Parsing scenario file testing/02-commands-destroy.yarn > Parsing scenario file testing/02-commands-fsck.yarn > Parsing scenario file testing/02-commands-gc.yarn > Parsing scenario file testing/02-commands-graveyard.yarn > Parsing scenario file testing/02-commands-git-upload-archive.yarn > Parsing scenario file testing/02-commands-group.yarn > Parsing scenario file testing/02-commands-help.yarn > Parsing scenario file testing/02-commands-keyring.yarn > Parsing scenario file testing/02-commands-ls.yarn > Parsing scenario file testing/02-commands-rename.yarn > Parsing scenario file testing/02-commands-rsync.yarn > Parsing scenario file testing/02-commands-sshkey.yarn > Parsing scenario file testing/02-commands-user.yarn > Parsing scenario file testing/02-commands-whoami.yarn > Parsing scenario file testing/03-cgit-support.yarn > Parsing scenario file testing/03-shallow-push.yarn > Parsing scenario file testing/03-treedelta-rules.yarn > Parsing scenario file testing/03-force-pushing.yarn > Parsing scenario file testing/03-dangling-HEAD.yarn > Parsing scenario file testing/03-config-user-whitelist.yarn > No shell libraries defined > Found 66 scenarios > Running scenario Verification of basic behaviour > DATADIR is /tmp/tmpSdYDTe/Verification_of_basic_behaviour/datadir > HOME for tests is > /tmp/tmpSdYDTe/Verification_of_basic_behaviour/datadir/HOME > Running step "GIVEN a standard instance" > ERROR: In scenario "Verification of basic behaviour" > step "GIVEN a standard instance" failed, > with exit code 2: > Standard output from shell command: > > Standard error from shell command: > + /<>/testing/gitano-test-tool createunixuser testinstance > + /<>/testing/gitano-test-tool createsshkey testinstance > adminkey > + /<>/testing/gitano-test-tool createsshkey testinstance > bypasskey > + /<>/testing/gitano-test-tool setupstandard testinstance > adminkey bypasskey > [gitano-setup] Welcome to the Gitano setup process > [gitano-setup] Performing system checks > [gitano-setup] ... Checking supple sandboxing > [gitano-setup] System checks out > [gitano-setup] Step 1: Determine everything > [gitano-setup] Step 2: Gather required content > [gitano-setup] Step 3: Write out paths and gitano-admin.git > [gitano-setup] Set project.description to administration repository> > [gitano-setup] Set project.owner to > [gitano-setup] SSH authorised key file updated > /tmp/tmpmJlbny: 8: /tmp/tmpmJlbny: Syntax error: "&" unexpected > > Running step "FINALLY the instance is torn down" > Running scenario whoami shows the gitano-admin group > DATADIR is /tmp/tmpxu9J3I/whoami_shows_the_gitano-admin_group/datadir > HOME for tests is > /tmp/tmpxu9J3I/whoami_shows_the_gitano-admin_group/datadir/HOME > Running step "GIVEN a standard instance" > ERROR: In scenario "whoami shows the gitano-admin group" > step "GIVEN a standard instance" failed, > with exit code 2: > Standard output from shell command: > > Standard error from shell command: > + /<>/testing/gitano-test-tool createunixuser testinstance > + /<>/testing/gitano-test-tool createsshkey testinstance > adminkey > + /<>/testing/gitano-test-tool createsshkey testinstance > bypasskey > + /<>/testing/gitano-test-tool setupstandard testinstance > adminkey bypasskey > [gitano-setup] Welcome to the Gitano setup process > [git
Bug#917600: puppetlabs-ring-middleware-clojure: FTBFS (failing tests)
On 29/12/2018 18:47, Cyril Brulebois wrote: > I've been contacted by Elana, and an MR is in progress for this package; > if it passes review, I'll submit other MRs for the remaining packages > (as fixes are almost identical), or I can push to the Java repositories > directly, as you folks prefer. Great, for the clojure packages it's good to have Elana to review them first. For the other Java packages you can send a MR or push directly to the repositories if you feel confident. Emmanuel Bourg
Bug#917704: ppx-deriving-yojson: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0)
Source: ppx-deriving-yojson Version: 3.1-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-ocaml, ocaml-nox (>= 4.02), > libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 4.0) > Filtered Build-Depends: debhelper (>= 11), dh-ocaml, ocaml-nox (>= 4.02), > libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 4.0) > dpkg-deb: building package 'sbuild-build-depends-ppx-deriving-yojson-dummy' > in > '/<>/resolver-so827s/apt_archive/sbuild-build-depends-ppx-deriving-yojson-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-ppx-deriving-yojson-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-so827s/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-so827s/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-so827s/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-so827s/apt_archive ./ Sources [546 B] > Get:5 copy:/<>/resolver-so827s/apt_archive ./ Packages [627 B] > Fetched 2136 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install ppx-deriving-yojson build dependencies (apt-based resolver) > --- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-ppx-deriving-yojson-dummy : Depends: > libppx-deriving-ocaml-dev (>= 4.0) but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/ppx-deriving-yojson_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#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)
Hi! On 2018-12-29 at 13:54 (+01), Andreas Metzler wrote: [...] > I do not understand your reasoning at all. What part of these argument > chain do you disagree with? > > 1. libilmbase23 2.3.0-3 is rc buggy because it does not contain the > library its name claims. If one installs libilmbase23 2.3.0-3 e.g. hugin > will stop working. SONAME bump in IlmBase/OpenEXR libraries is extremely weird and doesn't reflect the numbering in library name. Strange, but still. Check numbering and SONAME versioning for ilmbase actually in unstable and testing. You'll see how there's a pattern for that. > 2. We have Debian bug tracking system for tracking bugs in packages in > Debian. Opening bug reports against packages in experimental which are part of a transition is useless, in my view. Opening bug reports against packages in unstable/sid which breaks stuff... that's a real thing. > 3. libilmbase23 2.3.0-3 is a package in Debian. Yes, it's a package in Debian... experimental suite, which is not supposed to be used by users other than developers working on bleeding-edge/easily-breaking piece of software. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A signature.asc Description: PGP signature
Bug#917705: ipywidgets: FTBFS: build-dependency not installable: python-jupyter-sphinx-theme
Source: ipywidgets Version: 6.0.0-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), dh-python, node-recast, > libjs-jquery, libjs-jquery-ui, node-backbone, node-d3-format, > node-es6-promise, node-semver, node-typescript, node-typescript-types, > node-underscore, patch, python-all, python-pytest, python-setuptools (>= 28), > python-coverage, python-ipython, python-ipykernel, > python-jupyter-sphinx-theme, python-nose, python-traitlets, python-sphinx, > python-sphinx-rtd-theme, python3-all, python3-pytest, python3-setuptools (>= > 28), python3-coverage, python3-ipython, python3-ipykernel, > python3-jupyter-sphinx-theme, python3-nose, python3-traitlets, > python3-sphinx, python3-sphinx-rtd-theme, pandoc, m4 > Filtered Build-Depends: debhelper (>= 10), dh-python, node-recast, > libjs-jquery, libjs-jquery-ui, node-backbone, node-d3-format, > node-es6-promise, node-semver, node-typescript, node-typescript-types, > node-underscore, patch, python-all, python-pytest, python-setuptools (>= 28), > python-coverage, python-ipython, python-ipykernel, > python-jupyter-sphinx-theme, python-nose, python-traitlets, python-sphinx, > python-sphinx-rtd-theme, python3-all, python3-pytest, python3-setuptools (>= > 28), python3-coverage, python3-ipython, python3-ipykernel, > python3-jupyter-sphinx-theme, python3-nose, python3-traitlets, > python3-sphinx, python3-sphinx-rtd-theme, pandoc, m4 > dpkg-deb: building package 'sbuild-build-depends-ipywidgets-dummy' in > '/<>/resolver-8cqdG0/apt_archive/sbuild-build-depends-ipywidgets-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-ipywidgets-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-8cqdG0/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-8cqdG0/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-8cqdG0/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-8cqdG0/apt_archive ./ Sources [705 B] > Get:5 copy:/<>/resolver-8cqdG0/apt_archive ./ Packages [781 B] > Fetched 2449 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install ipywidgets build dependencies (apt-based resolver) > -- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-ipywidgets-dummy : Depends: python-jupyter-sphinx-theme > but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/ipywidgets_6.0.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#917697: ocaml-visitors: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0)
Source: ocaml-visitors Version: 20180306-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-ocaml (>= 0.9~), ocaml-nox (>= > 4.02.2), libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= > 4.0), texlive-latex-base, latexmk, lmodern, texlive-fonts-recommended, > texlive-latex-extra, ocp-indent > Filtered Build-Depends: debhelper (>= 11), dh-ocaml (>= 0.9~), ocaml-nox (>= > 4.02.2), libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= > 4.0), texlive-latex-base, latexmk, lmodern, texlive-fonts-recommended, > texlive-latex-extra, ocp-indent > dpkg-deb: building package 'sbuild-build-depends-ocaml-visitors-dummy' in > '/<>/resolver-k7rZ5R/apt_archive/sbuild-build-depends-ocaml-visitors-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-ocaml-visitors-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-k7rZ5R/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-k7rZ5R/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-k7rZ5R/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-k7rZ5R/apt_archive ./ Sources [613 B] > Get:5 copy:/<>/resolver-k7rZ5R/apt_archive ./ Packages [687 B] > Fetched 2263 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install ocaml-visitors build dependencies (apt-based resolver) > -- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-ocaml-visitors-dummy : Depends: > libppx-deriving-ocaml-dev (>= 4.0) but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/ocaml-visitors_20180306-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#917703: golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev
Source: golang-gopkg-macaroon.v2 Version: 0.0~git20171017.bed2a42-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), dh-golang, golang-any, > golang-github-juju-testing-dev, golang-golang-x-crypto-dev, > golang-gopkg-check.v1-dev > Filtered Build-Depends: debhelper (>= 10), dh-golang, golang-any, > golang-github-juju-testing-dev, golang-golang-x-crypto-dev, > golang-gopkg-check.v1-dev > dpkg-deb: building package > 'sbuild-build-depends-golang-gopkg-macaroon.v2-dummy' in > '/<>/resolver-3WmOKm/apt_archive/sbuild-build-depends-golang-gopkg-macaroon.v2-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-golang-gopkg-macaroon.v2-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-3WmOKm/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-3WmOKm/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-3WmOKm/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-3WmOKm/apt_archive ./ Sources [550 B] > Get:5 copy:/<>/resolver-3WmOKm/apt_archive ./ Packages [638 B] > Fetched 2151 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install golang-gopkg-macaroon.v2 build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-golang-gopkg-macaroon.v2-dummy : Depends: > golang-github-juju-testing-dev but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/golang-gopkg-macaroon.v2_0.0~git20171017.bed2a42-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#917695: mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16)
Source: mbtserver Version: 0.11-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > Filtered Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > dpkg-deb: building package 'sbuild-build-depends-mbtserver-dummy' in > '/<>/resolver-LNLJQQ/apt_archive/sbuild-build-depends-mbtserver-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-mbtserver-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-LNLJQQ/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-LNLJQQ/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-LNLJQQ/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-LNLJQQ/apt_archive ./ Sources [563 B] > Get:5 copy:/<>/resolver-LNLJQQ/apt_archive ./ Packages [647 B] > Fetched 2173 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install mbtserver build dependencies (apt-based resolver) > - > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-mbtserver-dummy : Depends: libtimbl4-dev (>= 6.4.8) but > it is not going to be installed > Depends: libtimblserver4-dev (>= > 1.11) but it is not going to be installed > Depends: libmbt1-dev (>= 3.2.16) but > it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/mbtserver_0.11-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#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev
Source: dimbl Version: 0.15-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11~), pkg-config, libxml2-dev, > libticcutils2-dev | libticcutils-dev, libtimbl4-dev | libtimbl-dev > Filtered Build-Depends: debhelper (>= 11~), pkg-config, libxml2-dev, > libticcutils2-dev, libtimbl4-dev > dpkg-deb: building package 'sbuild-build-depends-dimbl-dummy' in > '/<>/resolver-2TunP4/apt_archive/sbuild-build-depends-dimbl-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-dimbl-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-2TunP4/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-2TunP4/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-2TunP4/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-2TunP4/apt_archive ./ Sources [529 B] > Get:5 copy:/<>/resolver-2TunP4/apt_archive ./ Packages [602 B] > Fetched 2094 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install dimbl build dependencies (apt-based resolver) > - > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-dimbl-dummy : Depends: libtimbl4-dev but it is not > going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/dimbl_0.15-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#917694: nuitka: FTBFS: build-dependency not installable: python-imaging
Source: nuitka Version: 0.6.0.6+ds-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-python | base-files (<< 9.6), > python (>= 2.6.6-2), python-all-dbg (>= 2.6.6-2), python-all-dev (>= > 2.6.6-2), python-setuptools, rst2pdf (>= 0.14-2), python-imaging | > python-pil, scons (>= 2.0.0), python3-all-dev (>= 3.2), python3-all-dbg (>= > 3.2), python3-setuptools, python-appdirs | base-files (<< 7.2), > python3-appdirs | base-files (<< 7.2), strace, chrpath, gdb > Filtered Build-Depends: debhelper (>= 9), dh-python, python (>= 2.6.6-2), > python-all-dbg (>= 2.6.6-2), python-all-dev (>= 2.6.6-2), python-setuptools, > rst2pdf (>= 0.14-2), python-imaging, scons (>= 2.0.0), python3-all-dev (>= > 3.2), python3-all-dbg (>= 3.2), python3-setuptools, python-appdirs, > python3-appdirs, strace, chrpath, gdb > dpkg-deb: building package 'sbuild-build-depends-nuitka-dummy' in > '/<>/resolver-kOsmDm/apt_archive/sbuild-build-depends-nuitka-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-nuitka-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-kOsmDm/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-kOsmDm/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-kOsmDm/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-kOsmDm/apt_archive ./ Sources [620 B] > Get:5 copy:/<>/resolver-kOsmDm/apt_archive ./ Packages [678 B] > Fetched 2261 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install nuitka build dependencies (apt-based resolver) > -- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-nuitka-dummy : Depends: python-imaging but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/nuitka_0.6.0.6+ds-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#917698: libg15render: FTBFS: build-dependency not installable: libg15-dev
Source: libg15render Version: 1.3.0~svn316-2.4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 5), autotools-dev, libtool, > automake1.11, libg15-dev, libusb-dev, libfreetype6-dev, pkg-config, quilt > Filtered Build-Depends: cdbs, debhelper (>= 5), autotools-dev, libtool, > automake1.11, libg15-dev, libusb-dev, libfreetype6-dev, pkg-config, quilt > dpkg-deb: building package 'sbuild-build-depends-libg15render-dummy' in > '/<>/resolver-VTfJtN/apt_archive/sbuild-build-depends-libg15render-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-libg15render-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-VTfJtN/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-VTfJtN/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-VTfJtN/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-VTfJtN/apt_archive ./ Sources [542 B] > Get:5 copy:/<>/resolver-VTfJtN/apt_archive ./ Packages [626 B] > Fetched 2131 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install libg15render build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-libg15render-dummy : Depends: libg15-dev but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/libg15render_1.3.0~svn316-2.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.
