Bug#920852: ...slightly odd choice of shell syntax in patch

[Chris West]

Package: binstats
Version: 1.08-8.2
Severity: normal

The patch for binstats adds this line to binstats. It ends up in the
resulting package It.. I.. I'm not sure what it is doing.

   if [ $USEMANPATH -eq 1 -a -n "^Type -p manpath" ];then

That's not a ^ and a T. That's an actual ctrl+t, ascii 0x14.

Even if it read [ -n "type -p manpath" ], that would always be true?

I noticed, as file(1)-like tools declare the patch and binstats as a
binary file, due to the presence of this non-printable junk.

Please remove it, and/or change the shell to do something meaningful?

Cheers,
Chris.

Bug#893388: "Unable to find javadoc command:" on openjdk-10

[Chris West]

Package: libmaven-javadoc-plugin
Version: 3.0.0-2
Priority: normal
User: debian-j...@lists.debian.org
Usertags: default-java10
Tags: buster sid

On OpenJDK 10, the plugin fails to find the javadoc command, and prints:

[ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli)
  on [..]:
MavenReportException: Error while generating Javadoc:
  Unable to find javadoc command:
The environment variable JAVA_HOME is not correctly set. -> [Help 1]

Please ensure that it can find the javadoc command, at least during
Debian package builds.


This issue is the same bug as https://bugs.debian.org/866929 but for a
different JDK release.

The patch for that issue,
https://anonscm.debian.org/cgit/pkg-java/maven-javadoc-plugin.git/tree/debian/patches/openjdk-9-javadoc-path.patch
, is using "is exactly JDK9", and apparently needs to be "is at least JDK9".


Cheers,
Chris.

Bug#890663: charybdis: Please package 4.x

[Chris West]

Source: charybdis
Version: 3.5.5-2
Severity: wishlist

Please package charybdis 4.x.

I've had a go here: https://salsa.debian.org/faux-guest/charybdis

Just imports the new tag, and fixes a rename and a missing build dep, and
it appears to build successfully.


Lintian has few outstanding warnings:
I: charybdis source: vcs-field-uses-insecure-uri vcs-git 
git://anonscm.debian.org/collab-maint/charybdis.git -b debian
I: charybdis source: vcs-field-uses-insecure-uri vcs-browser 
http://anonscm.debian.org/gitweb/?p=collab-maint/charybdis.git;a=summary
I: charybdis source: debian-rules-parses-dpkg-parsechangelog (line 50)
I: charybdis source: wildcard-matches-nothing-in-dep5-copyright 
src/ircd_signal.c (paragraph at line 45)
I: charybdis source: wildcard-matches-nothing-in-dep5-copyright src/match.c 
(paragraph at line 45)
I: charybdis source: wildcard-matches-nothing-in-dep5-copyright 
src/messages.tab (paragraph at line 45)
I: charybdis source: wildcard-matches-nothing-in-dep5-copyright ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
I: charybdis source: unused-file-paragraph-in-dep5-copyright paragraph at line 
118
W: charybdis source: out-of-date-standards-version 3.9.8 (current is 4.1.1)
I: charybdis source: testsuite-autopkgtest-missing

.. which you might want to fix before uploading a real package. :)

Chris.

Bug#888255: Investigations!

[Chris West]

Righty ho, I had a proper look at the above list.

Two packages have simple, direct dependencies on netty-3.x, and their
code is not easy to port to the netty-4.x API, and upstream haven't
cared. These are a big problem:

 * osmosis: https://trac.openstreetmap.org/ticket/5489
 * zookeeper: https://issues.apache.org/jira/browse/ZOOKEEPER-2399

activemq depends directly on zookeeper's client library (but not
otherwise on netty-3.x).


Three packages are fixed upstream, so could just do with a new package:

 * apache-curator. ..but nobody cares. RM? https://bugs.debian.org/890624
 * libgpars-groovy-java: recommended-only rdeps (groovy),
fixed upstream but not tagged. I've asked for a tag:
https://github.com/GPars/GPars/issues/60
 * bookkeeper: fixed upstream in 4.6.1:

https://github.com/apache/bookkeeper/commit/74f795136c1fff3badb29fc982d0cc2d43096b45
They label 4.5.0 as "stable", though.


These packages are not serious, maintained packages:

 * eclipse-aether: RM'd: https://bugs.debian.org/881608
 * elasticsearch: not going to be shipped, and probably fixed upstream
anyway: https://bugs.debian.org/803713


And then there's "aether", a utility library for maven repositories.
It's been deprecated, renamed, deprecated again, then merged into
maven-resolver. New enough maven-resolver is packaged, and our version
of maven (3.5) is new enough to not depend on aether. However, a couple
of libraries' upstreams maintain compatibility with older maven, which
involves supporting the aether names for classes. These are:

 * tycho, which is complicated and doesn't seem to have any rdeps, but
Luca seems to care about it still, so I'm not (yet!) going to start
yelling RM, RM, RM:
https://anonscm.debian.org/git/pkg-java/tycho.git/log/
 * maven-indexer, which is fixed upstream:

https://github.com/apache/maven-indexer/commit/ad07405c06b422cb529d3badaa1b6b376699c9c1
 * maven-common-artifact-filters, which looks simple but upstream have
told me is not, and they're almost certainly right:
https://issues.apache.org/jira/browse/MSHARED-683


And that's it, I think!

I'm going to continue attempting to port osmosis and zookeeper upstream,
but I've found it very challenging.

Bug#890624: RM? Outdated, no rdeps, broken deps

[Chris West]

Source: apache-curator
Version: 2.7.1-2
Severity: normal
Control: block 888255 by -1


apache-curator is a library for making it easier to write software, it
doesn't appear to have any purpose on its own. I can't see any rdeps, so
nothing in Debain is using it.

It's rather outdated; last packaged in 2015. Upstream are up to 4.0.1.

It depends on netty3.9, which I want to RM. (4.0.1 does not depend on
Netty, any version.).

Can we RM it?


Cheers,
Chris.

Bug#888255: RM? Upstream dropped support, security important, newer version packaged

[Chris West]

Source: netty-3.9
Version: 3.9.9.Final-1
Severity: normal

netty is complicated security code so needs support.

netty 3.x support was ended by upstream in Jun 2016[1].

netty 3.9 hasn't had an upstream commit/release since Jul 2015.

The latest version is packaged as "netty" and supported.

netty-3.9 needs a backport of the fix for https://bugs.debian.org/828451
which is blocking the openssl-1.0rm transition.


Current (build) rdeps:

activemq
aether
apache-curator
async-http-client
bookkeeper
eclipse-aether
elasticsearch
libgpars-groovy-java
maven-indexer
maven-resolver
osmosis
pomegranate-clojure
tycho
zookeeper


I do not think netty-3.9 should be released with Buster.

Can we start RMing it?


Cheers,
Chris.


 1: https://netty.io/news/2016/06/29/3-10-6-Final.html

Bug#888198: yard: FTBFS on ruby2.5: got: ("gem.deps.rb")

[Chris West (Faux)]

Source: yard
Version: 0.9.12-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) YARD::CLI::YRI#initialize loads search paths
 Failure/Error: Gem::Specification.find_all_by_name(*args)

   # received :file? with unexpected arguments
 expected: (/\/\.yard\/yri_cache$/)
  got: ("gem.deps.rb")
   Diff:
   @@ -1,2 +1,2 @@
   -[/\/\.yard\/yri_cache$/]
   +["gem.deps.rb"]
 # ./lib/yard/gem_index.rb:11:in `find_all_by_name'
 # ./lib/yard/registry.rb:54:in `yardoc_file_for_gem'
 # ./lib/yard/cli/yri.rb:165:in `block in add_gem_paths'
 # ./lib/yard/gem_index.rb:19:in `each'
 # ./lib/yard/cli/yri.rb:164:in `add_gem_paths'
 # ./lib/yard/cli/yri.rb:36:in `initialize'
 # ./spec/cli/yri_spec.rb:52:in `new'
 # ./spec/cli/yri_spec.rb:52:in `block (3 levels) in '
 # ./spec/spec_helper.rb:127:in `block (2 levels) in '

  2) YARD::CLI::YRI#initialize uses DEFAULT_SEARCH_PATHS prior to other paths
 Failure/Error: Gem::Specification.find_all_by_name(*args)

   # received :file? with unexpected arguments
 expected: (/\/\.yard\/yri_cache$/)
  got: ("gem.deps.rb")
   Diff:
   @@ -1,2 +1,2 @@
   -[/\/\.yard\/yri_cache$/]
   +["gem.deps.rb"]
 # ./lib/yard/gem_index.rb:11:in `find_all_by_name'
 # ./lib/yard/registry.rb:54:in `yardoc_file_for_gem'
 # ./lib/yard/cli/yri.rb:165:in `block in add_gem_paths'
 # ./lib/yard/gem_index.rb:19:in `each'
 # ./lib/yard/cli/yri.rb:164:in `add_gem_paths'
 # ./lib/yard/cli/yri.rb:36:in `initialize'
 # ./spec/cli/yri_spec.rb:64:in `new'
 # ./spec/cli/yri_spec.rb:64:in `block (3 levels) in '
 # ./spec/spec_helper.rb:127:in `block (2 levels) in '

...


Finished in 5.71 seconds (files took 2.77 seconds to load)
1865 examples, 2 failures, 5 pending

Failed examples:

rspec ./spec/cli/yri_spec.rb:47 # YARD::CLI::YRI#initialize loads search paths
rspec ./spec/cli/yri_spec.rb:58 # YARD::CLI::YRI#initialize uses 
DEFAULT_SEARCH_PATHS prior to other paths

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/yard-0.9.12/debian/tmp returned exit 
code 1
debian/rules:20: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/build/yard-0.9.12'
make: *** [binary] Error 2
debian/rules:10: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/yard.log

Please fix it!

Cheers,
Chris.

Bug#888196: ruby-sexp-processor: FTBFS on ruby2.5: BOOM GOES THE STACK

[Chris West (Faux)]

Source: ruby-sexp-processor
Version: 4.7.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

I'm hoping this is an intermittent failure. Praying, really.
But capturing in case it's rare.

Build log excerpt:


95 runs, 171 assertions, 0 failures, 0 errors, 14 skips

You have skipped tests. Run with --verbose for details.
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sexp-processor/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 24009

# Running:

..S./build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:293:
 [BUG] Stack consistency error (sp: 151, bp: 150)
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux-gnu]

-- Control frame information ---
c:0026 p:0616 s:0151 e:000149 BLOCK  
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:293
c:0025 p:0012 s:0141 e:000140 METHOD 
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:373
c:0024 p:0195 s:0136 e:000135 METHOD 
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:227
c:0023 p:0022 s:0127 e:000124 METHOD 
/build/ruby-sexp-processor-4.7.0/test/test_sexp_processor.rb:109
c:0022 p:0024 s:0119 e:000118 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107
c:0021 p:0002 s:0116 e:000115 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204
c:0020 p:0006 s:0111 e:000110 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104
c:0019 p:0014 s:0108 e:000107 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255
c:0018 p:0006 s:0103 e:000102 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103
c:0017 p:0029 s:0100 e:99 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:350
c:0016 p:0044 s:0092 E:001f68 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275
c:0015 p:0005 s:0085 E:000ef0 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102
c:0014 p:0010 s:0081 e:80 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:839
c:0013 p:0026 s:0074 e:72 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:324
c:0012 p:0011 s:0066 e:65 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:311 
[FINISH]
c:0011 p: s:0062 e:61 CFUNC  :each
c:0010 p:0007 s:0058 e:57 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:310
c:0009 p:0029 s:0055 e:54 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:350
c:0008 p:0029 s:0047 E:001178 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:337
c:0007 p:0109 s:0040 E:000898 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:309
c:0006 p:0010 s:0031 e:30 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:159 
[FINISH]
c:0005 p: s:0027 e:26 CFUNC  :map
c:0004 p:0038 s:0023 e:22 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:159
c:0003 p:0132 s:0014 e:13 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:136
c:0002 p:0059 s:0007 E:000358 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:63 
[FINISH]
c:0001 p: s:0003 E:000600 (none) [FINISH]

-- Ruby level backtrace information 
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block 

Bug#888197: ruby-yajl: FTBFS on ruby2.5: rb_cFixnum undefined

[Chris West (Faux)]

Source: ruby-yajl
Version: 1.2.0-3.1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-yajl-1.2.0 debian/ruby-yajl
"make clean"
make[1]: Entering directory '/build/ruby-yajl-1.2.0/ext/yajl'
make[1]: Leaving directory '/build/ruby-yajl-1.2.0/ext/yajl'
"make clean"
make[1]: Entering directory '/build/ruby-yajl-1.2.0/ext/yajl'
make[1]: Leaving directory '/build/ruby-yajl-1.2.0/ext/yajl'
current directory: /build/ruby-yajl-1.2.0/ext/yajl
/usr/bin/ruby2.5 -r ./siteconf20180123-364-1ppgeqs.rb extconf.rb
creating Makefile
current directory: /build/ruby-yajl-1.2.0/ext/yajl
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/build/ruby-yajl-1.2.0/ext/yajl'
rm -f 
rm -f yajl.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/build/ruby-yajl-1.2.0/ext/yajl'
current directory: /build/ruby-yajl-1.2.0/ext/yajl
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-yajl-1.2.0/ext/yajl'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
-funroll-loops  -o yajl.o -c yajl.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
-funroll-loops  -o yajl_alloc.o -c yajl_alloc.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
-funroll-loops  -o yajl_buf.o -c yajl_buf.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
-funroll-loops  -o yajl_encode.o -c yajl_encode.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
-funroll-loops  -o yajl_ext.o -c yajl_ext.c
yajl_ext.c: In function 'rb_yajl_parser_parse':
yajl_ext.c:472:17: warning: variable 'stat' set but not used 
[-Wunused-but-set-variable]
 yajl_status stat;
 ^~~~
yajl_ext.c: In function 'rb_yajl_encoder_enable_json_gem_ext':
yajl_ext.c:882:22: error: 'rb_cFixnum' undeclared (first use in this function); 
did you mean 'rb_isalnum'?
 rb_define_method(rb_cFixnum, "to_json", rb_yajl_json_ext_fixnum_to_json, 
-1);
  ^~
  rb_isalnum
yajl_ext.c:882:22: note: each undeclared identifier is reported only once for 
each function it appears in
Makefile:242: recipe for target 'yajl_ext.o' failed
make[1]: *** [yajl_ext.o] Error 1
make[1]: Leaving directory '/build/ruby-yajl-1.2.0/ext/yajl'
/usr/lib/ruby/2.5.0/rubygems/ext/builder.rb:92:in `run': make failed, exit code 
2 (Gem::InstallError)
from /usr/lib/ruby/2.5.0/rubygems/ext/builder.rb:52:in `block in make'
from /usr/lib/ruby/2.5.0/rubygems/ext/builder.rb:44:in `each'
from /usr/lib/ruby/2.5.0/rubygems/ext/builder.rb:44:in `make'
from /usr/lib/ruby/2.5.0/rubygems/ext/ext_conf_builder.rb:61:in `block 
in build'
from /usr/lib/ruby/2.5.0/tempfile.rb:295:in `open'
from /usr/lib/ruby/2.5.0/rubygems/ext/ext_conf_builder.rb:30:in `build'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:76:in 
`block in build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
`chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
`build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:108:in 
`block in build_all_extensions'
from 

Bug#888194: ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime

[Chris West (Faux)]

Source: ruby-safe-yaml
Version: 1.0.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Finished in 0.00114 seconds (files took 0.12105 seconds to load)
2 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-safe-yaml/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"safe_yaml\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-safe-yaml-1.0.4/debian/ruby-safe-yaml/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-safe-yaml/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
/build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:22:in `': 
uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)
Did you mean?  SafeYAML::Parse::Date::DATE_MATCHER
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:3:in 
`'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:2:in 
`'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/load.rb:14:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-safe-yaml-1.0.4/spec/spec_helper.rb:29:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-safe-yaml-1.0.4/spec/libyaml_checker_spec.rb:1:in 
`'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
Ruby 2.5.0, YAML: syck (3.0.2) (libyaml: N/A), Monkeypatch: true
debian/ruby-tests.rb:16:in `block in ': unhandled exception
from debian/ruby-tests.rb:14:in `each'
from debian/ruby-tests.rb:14:in `'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-safe-yaml-1.0.4/debian/ruby-safe-yaml returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-safe-yaml.log

Please fix it!

Cheers,
Chris.

Bug#888193: ruby-rmagick: FTBFS on ruby2.5: <FrozenError(<can't modify frozen Magick::Image>)>

[Chris West (Faux)]

Source: ruby-rmagick
Version: 2.16.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Super confusing build log excerpt:


Pending: (Failures listed here are expected and do not affect your suite's 
status)

  1) Magick::Draw#marshal_dump #marshal_load marshals without an error
 # this spec fails on some versions of ImageMagick
 # ./spec/rmagick/draw_spec.rb:82

Finished in 0.27725 seconds (files took 0.12424 seconds to load)
36 examples, 0 failures, 1 pending

/usr/bin/ruby2.5 -w  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_all_basic.rb" -v
/build/ruby-rmagick-2.16.0/test/Image2.rb:80: warning: assigned but unused 
variable - img
/build/ruby-rmagick-2.16.0/test/Image2.rb:305: warning: assigned but unused 
variable - format
/build/ruby-rmagick-2.16.0/test/Image2.rb:306: warning: assigned but unused 
variable - size
/build/ruby-rmagick-2.16.0/test/Image2.rb:307: warning: assigned but unused 
variable - geometry
/build/ruby-rmagick-2.16.0/test/Image2.rb:308: warning: assigned but unused 
variable - image_class
/build/ruby-rmagick-2.16.0/test/Image2.rb:401: warning: `-' after local 
variable or literal is interpreted as binary operator
/build/ruby-rmagick-2.16.0/test/Image2.rb:401: warning: even though it seems 
like unary operator
/build/ruby-rmagick-2.16.0/test/Image2.rb:536: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/Image2.rb:537: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/Image2.rb:538: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/Image2.rb:539: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/Image3.rb:683: warning: assigned but unused 
variable - img
/build/ruby-rmagick-2.16.0/test/ImageList1.rb:295: warning: assigned but unused 
variable - cur
/build/ruby-rmagick-2.16.0/test/ImageList1.rb:332: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/ImageList1.rb:333: warning: assigned but unused 
variable - res
/build/ruby-rmagick-2.16.0/test/Import_Export.rb:12: warning: assigned but 
unused variable - res
/build/ruby-rmagick-2.16.0/test/Magick.rb:312: warning: assigned but unused 
variable - img
2.5.0
String
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
Image1_UT: 
  test_adaptive_blur:   .: (0.002072)
  test_adaptive_blur_channel:   .: (0.002713)
  test_adaptive_resize: .: (0.000529)
  test_adaptive_sharpen:.: (0.000895)
  test_adaptive_sharpen_channel:.: (0.001748)
  test_adaptive_threshold:  .: (0.000333)
  test_add_compose_mask:.: (0.000255)
  test_add_noise:   .: (0.008137)
  test_add_noise_channel:   .: (0.007935)
  test_affine_matrix:   .: (0.001704)
  test_alpha:   F
===
Failure: test_alpha(Image1_UT)
/build/ruby-rmagick-2.16.0/test/Image1.rb:172:in `test_alpha'
 169: assert_nothing_raised { @img.alpha Magick::ResetAlphaChannel }
 170: assert_nothing_raised { @img.alpha Magick::SetAlphaChannel }
 171: @img.freeze
  => 172: assert_raise(FreezeError) { @img.alpha Magick::SetAlphaChannel }
 173:   end
 174: 
 175:   def test_auto_gamma

 expected but was
)>

diff:
? Ru   ntimeError 
? Froze  ()
===
: (0.052752)
  test_alpha_compat:.: (0.000186)
  test_auto_gamma:  .: (0.012168)
  test_auto_level:  .: (0.000255)
  test_auto_orient: .: (0.000143)
  test_bilevel_channel: .: (0.000527)
  test_black_threshold: .: (0.000445)



...



Finished in 42.696937665 seconds.
--
385 tests, 232948 assertions, 15 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
96.1039% passed
--
9.02 tests/s, 5455.85 assertions/s
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_all_basic.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.

Bug#888191: ruby-powerpack: FTBFS on ruby2.5: Error: expect([].sum).to be_nil

[Chris West (Faux)]

Source: ruby-powerpack
Version: 0.1.1-3
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) Enumerable#sum returns nil when invoked on an empty collection
 Failure/Error: expect([].sum).to be_nil

   expected: nil
got: 0
 # ./spec/powerpack/enumerable/sum_spec.rb:9:in `block (2 levels) in '

Finished in 0.05947 seconds (files took 0.21147 seconds to load)
102 examples, 1 failure

Failed examples:

rspec ./spec/powerpack/enumerable/sum_spec.rb:8 # Enumerable#sum returns nil 
when invoked on an empty collection

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-powerpack-0.1.1/debian/ruby-powerpack returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-powerpack.log

Please fix it!

Cheers,
Chris.

Bug#888192: ruby-prof: FTBFS on ruby2.5: ArgumentError: incomplete format specifier; use %%

[Chris West (Faux)]

Source: ruby-prof
Version: 0.16.2+dfsg-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


  1) Failure:
LineNumbersTest#test_function_line_no 
[/build/ruby-prof-0.16.2+dfsg/test/line_number_test.rb:37]:
Expected: 10
  Actual: 11

  2) Failure:
LineNumbersTest#test_c_function 
[/build/ruby-prof-0.16.2+dfsg/test/line_number_test.rb:65]:
Expected: 14
  Actual: 15

  3) Error:
RackTest#test_create_profile_reports:
ArgumentError: incomplete format specifier; use %% (double %) instead

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/graph_printer.rb:59:in
 `sprintf'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/graph_printer.rb:59:in
 `block in print_methods'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/graph_printer.rb:49:in
 `reverse_each'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/graph_printer.rb:49:in
 `print_methods'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/abstract_printer.rb:75:in
 `print_thread'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/abstract_printer.rb:69:in
 `block in print_threads'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/abstract_printer.rb:68:in
 `each'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/abstract_printer.rb:68:in
 `print_threads'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/printers/abstract_printer.rb:64:in
 `print'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:89:in
 `block (2 levels) in print'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:88:in
 `open'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:88:in
 `block in print'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:75:in
 `each'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:75:in
 `print'

/build/ruby-prof-0.16.2+dfsg/debian/ruby-prof/usr/lib/ruby/vendor_ruby/ruby-prof/rack.rb:36:in
 `call'
/build/ruby-prof-0.16.2+dfsg/test/rack_test.rb:42:in 
`test_create_profile_reports'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'


Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-prof.log

Please fix it!

Cheers,
Chris.

Bug#888190: ruby-mustermann19: FTBFS on ruby2.5: TypeError: Integer

[Chris West (Faux)]

Source: ruby-mustermann19
Version: 0.4.3+git20160621-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) Mustermann new invalid arguments raise a TypeError for unsupported types
 Failure/Error: expect { Mustermann.new(10) }.to 
raise_error(TypeError, "Fixnum can't be coerced into Mustermann::Pattern")
 
   expected TypeError with "Fixnum can't be coerced into 
Mustermann::Pattern", got # with backtrace:
 # 
/build/ruby-mustermann19-0.4.3+git20160621/lib/mustermann.rb:72:in `new'
 # 
/build/ruby-mustermann19-0.4.3+git20160621/spec/mustermann_spec.rb:49:in `block 
(5 levels) in '
 # 
/build/ruby-mustermann19-0.4.3+git20160621/spec/mustermann_spec.rb:49:in `block 
(4 levels) in '
 # 
/build/ruby-mustermann19-0.4.3+git20160621/spec/mustermann_spec.rb:49:in `block 
(4 levels) in '

Finished in 1.41 seconds (files took 1.08 seconds to load)
4484 examples, 1 failure

Failed examples:

rspec 
/build/ruby-mustermann19-0.4.3+git20160621/spec/mustermann_spec.rb:48 
# Mustermann new invalid arguments raise a TypeError for unsupported 
types

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-mustermann19-0.4.3\+git20160621/debian/ruby-mustermann19 returned 
exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-mustermann19.log

Please fix it!

Cheers,
Chris.

Bug#888189: ruby-innertube: FTBFS on ruby2.5: undefined method mock

[Chris West (Faux)]

Source: ruby-innertube
Version: 1.1.0-3
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

# terminated with exception (report_on_exception is true):
/usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing': undefined 
method `mock' for 
#
 (NoMethodError)
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in 
`method_missing'
from /build/ruby-innertube-1.1.0/spec/innertube_spec.rb:216:in `block 
(5 levels) in '
from /build/ruby-innertube-1.1.0/lib/innertube.rb:131:in `block in take'
from /build/ruby-innertube-1.1.0/lib/innertube.rb:127:in `synchronize'
from /build/ruby-innertube-1.1.0/lib/innertube.rb:127:in `take'
from /build/ruby-innertube-1.1.0/spec/innertube_spec.rb:227:in `block 
(6 levels) in '
# terminated with exception (report_on_exception is true):
/usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing': undefined 
method `mock' for 
#
 (NoMethodError)
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in 
`method_missing'
from /build/ruby-innertube-1.1.0/spec/innertube_spec.rb:216:in `block 
(5 levels) in '
from /build/ruby-innertube-1.1.0/lib/innertube.rb:131:in `block in take'
from /build/ruby-innertube-1.1.0/lib/innertube.rb:127:in `synchronize'
from /build/ruby-innertube-1.1.0/lib/innertube.rb:127:in `take'
from /build/ruby-innertube-1.1.0/spec/innertube_spec.rb:227:in `block 
(6 levels) in '
FF

Failures:

  1) Innertube::Pool threaded access stress test
 Failure/Error: RSpec.configuration.formatters.first.message(string)

 NoMethodError:
   undefined method `message' for "[103t:28r:11p:0.75833b] ":String
 # ./spec/support/verbose_formatter.rb:105:in `message'
 # ./spec/innertube_spec.rb:385:in `block (3 levels) in '
 # ./spec/support/timeout.rb:9:in `block (3 levels) in '
 # ./spec/support/timeout.rb:8:in `block (2 levels) in '

  2) Innertube::Pool threaded access iterates over a snapshot of all 
connections, even ones in use
 Failure/Error: RSpec.configuration.formatters.first.message(string)

 NoMethodError:
   undefined method `message' for "Waiting on 31 threads: ":String
 # ./spec/support/verbose_formatter.rb:105:in `message'
 # ./spec/innertube_spec.rb:7:in `wait_all'
 # ./spec/innertube_spec.rb:209:in `block (3 levels) in '
 # ./spec/support/timeout.rb:9:in `block (3 levels) in '
 # ./spec/support/timeout.rb:8:in `block (2 levels) in '

  3) Innertube::Pool threaded access iteration race-condition regression
 Failure/Error: RSpec.configuration.formatters.first.message(string)

 NoMethodError:
   undefined method `message' for "[24:2] ":String
 # ./spec/support/verbose_formatter.rb:105:in `message'
 # ./spec/innertube_spec.rb:310:in `block (3 levels) in '
 # ./spec/support/timeout.rb:9:in `block (3 levels) in '
 # ./spec/support/timeout.rb:8:in `block (2 levels) in '

  4) Innertube::Pool threaded access conditionally deleting members should 
remove them from the pool
 Failure/Error: n.times { message "X<#{q.pop}> " }

 Timeout::Error:
   execution expired
 # ./spec/innertube_spec.rb:280:in `pop'
 # ./spec/innertube_spec.rb:280:in `block (5 levels) in '
 # ./spec/innertube_spec.rb:280:in `times'
 # ./spec/innertube_spec.rb:280:in `block (4 levels) in '
 # ./spec/support/timeout.rb:9:in `block (3 levels) in '
 # ./spec/support/timeout.rb:8:in `block (2 levels) in '

  5) Innertube::Pool threaded access clearing the pool should remove all 
elements
 Failure/Error: n.times { message "S<#{q.pop}> " }

 Timeout::Error:
   execution expired
 # ./spec/innertube_spec.rb:238:in `pop'
 # ./spec/innertube_spec.rb:238:in `block (5 levels) in '
 # ./spec/innertube_spec.rb:238:in `times'
 # ./spec/innertube_spec.rb:238:in `block (4 levels) in '
 # ./spec/support/timeout.rb:9:in `block (3 levels) in '
 # ./spec/support/timeout.rb:8:in `block (2 levels) in '

  6) Innertube::Pool when BadResource is raised should remove the member from 
the pool
 Failure/Error:
   lambda do
 pool.take do |x|
   raise Innertube::Pool::BadResource
 end
   end.should raise_error(Innertube::Pool::BadResource)

   expected Innertube::Pool::BadResource, got #>
 with backtrace:
 # ./spec/innertube_spec.rb:87:in `block (4 levels) in '
 # ./lib/innertube.rb:131:in `block in take'
 # 

Bug#888188: ruby-hashie: FTBFS on ruby2.5: stack overflow around Integer

[Chris West (Faux)]

Source: ruby-hashie
Version: 3.4.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Failures:

  1) Hashie::Extensions::Coercion#coerce_value core types raises a 
CoercionError when coercion is not possible
 Failure/Error: if ABSTRACT_CORE_TYPES.key? from

 SystemStackError:
   stack level too deep
 # ./lib/hashie/extensions/coercion.rb:113:in `key?'
 # ./lib/hashie/extensions/coercion.rb:113:in `coerce_value'
 # ./lib/hashie/extensions/coercion.rb:115:in `block in coerce_value'
 # ./lib/hashie/extensions/coercion.rb:114:in `each'
 # ./lib/hashie/extensions/coercion.rb:114:in `coerce_value'
 # ./lib/hashie/extensions/coercion.rb:115:in `block in coerce_value'
 # ./lib/hashie/extensions/coercion.rb:114:in `each'

[... .. yes, lots of ...]

 # ./lib/hashie/extensions/coercion.rb:115:in `block in coerce_value'
 # ./lib/hashie/extensions/coercion.rb:114:in `each'
 # ./lib/hashie/extensions/coercion.rb:114:in `coerce_value'
 # ./lib/hashie/extensions/coercion.rb:115:in `block in coerce_value'
 # ./lib/hashie/extensions/coercion.rb:114:in `each'
 # ./lib/hashie/extensions/coercion.rb:114:in `coerce_value'
 # ./spec/hashie/extensions/coercion_spec.rb:587:in `block (4 levels) in 
'

Finished in 0.30331 seconds (files took 0.38196 seconds to load)
616 examples, 3 failures

Failed examples:

rspec ./spec/hashie/extensions/coercion_spec.rb:560 # 
Hashie::Extensions::Coercion#coerce_value core types raises a CoercionError 
when coercion is not possible
rspec ./spec/hashie/extensions/coercion_spec.rb:565 # 
Hashie::Extensions::Coercion#coerce_value core types coerces Integer to String
rspec ./spec/hashie/extensions/coercion_spec.rb:586 # 
Hashie::Extensions::Coercion#coerce_value core types coerces Numeric to String

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-hashie-3.4.4/debian/ruby-hashie 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-hashie.log

Please fix it!

Cheers,
Chris.

Bug#888186: ruby-fakefs: FTBFS on ruby2.5: pread method is not available in File :(

[Chris West (Faux)]

Source: ruby-fakefs
Version: 0.6.7-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:261: warning: constant ::Fixnum is 
deprecated
./build/ruby-fakefs-0.6.7/test/fakefs_test.rb:766: warning: 
FakeFS::File#write is outdated interface which accepts just one argument
/build/ruby-fakefs-0.6.7/test/fakefs_test.rb:766: warning: FakeFS::File#write 
is outdated interface which accepts just one argument
/build/ruby-fakefs-0.6.7/test/fakefs_test.rb:767: warning: FakeFS::File#write 
is outdated interface which accepts just one argument
/build/ruby-fakefs-0.6.7/test/fakefs_test.rb:767: warning: FakeFS::File#write 
is outdated interface which accepts just one argument
./build/ruby-fakefs-0.6.7/test/fakefs_test.rb:822: warning: 
setting Encoding.default_external
.../build/ruby-fakefs-0.6.7/test/fakefs_test.rb:2667: warning: 
FakeFS::File::new() does not take block; use FakeFS::File::open() instead
../build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:256: warning: 
constant ::Fixnum is deprecated
/build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:261: warning: constant ::Fixnum is 
deprecated
./build/ruby-fakefs-0.6.7/test/fakefs_test.rb:352: warning: 
global variable `$PID' not initialized
..F/build/ruby-fakefs-0.6.7/lib/fakefs/dir.rb:223:
 warning: global variable `$PID' not initialized
/build/ruby-fakefs-0.6.7/lib/fakefs/dir.rb:223: warning: global variable `$PID' 
not initialized
../build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:256: warning: 
constant ::Fixnum is deprecated
/build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:261: warning: constant ::Fixnum is 
deprecated
/build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:256: warning: constant ::Fixnum 
is deprecated
/build/ruby-fakefs-0.6.7/lib/fakefs/file.rb:261: warning: constant ::Fixnum is 
deprecated
./build/ruby-fakefs-0.6.7/lib/fakefs/dir.rb:168: 
warning: global variable `$PID' not initialized
../build/ruby-fakefs-0.6.7/lib/fakefs/dir.rb:168: warning: 
global variable `$PID' not initialized
.

Finished in 0.272047s, 1378.4389 runs/s, 2789.9604 assertions/s.

  1) Failure:
FakeFSTest#test_every_method_in_file_is_in_fake_fs_file 
[/build/ruby-fakefs-0.6.7/test/fakefs_test.rb:1218]:
pread method is not available in File :(

375 runs, 759 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1)

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-fakefs-0.6.7/debian/ruby-fakefs 
returned exit code 1
debian/rules:16: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-fakefs.log

Please fix it!

Cheers,
Chris.

Bug#888187: ruby-ffaker: FTBFS on ruby2.5: test_paragraphsLoremFR

[Chris West (Faux)]

Source: ruby-ffaker
Version: 2.2.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

  test_paragraph:   .: (0.000351)
  test_paragraphsLoremFR:   F
===
Failure:
   was expected to be =~
  <"Nostalgique nécessaires pays bolos paroles laissa. Purent mésusèrent vivent 
une. Lui lieues prevenant pointdexclamators une voyellie. Pourtant flancs 
agence désormais. Vers ressaisi approvisionne italiques exploitent retrait mit 
il voyellie. Lui règlalades larousse était sa. Désormais vaste puissante fût d 
prevenant la. Ce fois gravi lieu là pacqua déjà qu se. Était encoreloin 
paragraphe tout vils avait. Sournois et fourbes premiers prémâchées dernier 
semicolons au. Ipsum ses tout fourmillait.">.
test_paragraphsLoremFR(TestLoremFR)
/build/ruby-ffaker-2.2.0/test/test_lorem_fr.rb:19:in `test_paragraphsLoremFR'
 16:   end
 17: 
 18:   def test_paragraphsLoremFR
  => 19: assert_match /\A[ -.àâéèêîôùûa-z]+\z/i, 
FFaker::LoremFR.paragraphs.join(" ")
 20:   end
 21: 
 22:   def test_sentences
===
: (0.016718)
  test_phrase:  .: (0.000119)
  test_phrases: .: (0.000115)
  test_sentence:.: (0.71)


Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-ffaker.log

Please fix it!

Cheers,
Chris.

Bug#888185: rubocop: FTBFS on ruby2.5: Error: FileUtils.rmdir(attack_target_dir)

[Chris West (Faux)]

Source: rubocop
Version: 0.51.0+dfsg-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) RuboCop::ResultCache cached result that was saved with no command line 
option when no option is given when a symlink is present in the cache location 
and symlink attack protection is disabled permits caching and prints no warning
 Failure/Error: FileUtils.rmdir(attack_target_dir)

 Errno::ENOTEMPTY:
   Directory not empty @ dir_s_rmdir - /tmp/d20180123-1310-1kp5vxe
 # /build/rubocop-0.51.0+dfsg/spec/rubocop/result_cache_spec.rb:95:in 
`block (5 levels) in '
 # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:27:in 
`block (4 levels) in '
 # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:26:in 
`chdir'
 # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:26:in 
`block (3 levels) in '
 # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:8:in 
`block (2 levels) in '

Finished in 33.85 seconds (files took 3.52 seconds to load)
17503 examples, 1 failure, 1 pending

Failed examples:

rspec /build/rubocop-0.51.0+dfsg/spec/rubocop/result_cache_spec.rb:121 # 
RuboCop::ResultCache cached result that was saved with no command line option 
when no option is given when a symlink is present in the cache location and 
symlink attack protection is disabled permits caching and prints no warning

Randomized with seed 48248

/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/rubocop-0.51.0\+dfsg/debian/rubocop 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/rubocop.log

Please fix it!

Cheers,
Chris.

Bug#888174: ruby-whitequark-parser: FTBFS on ruby2.5: Update test_current for 2.5.0

[Chris West (Faux)]

Source: ruby-whitequark-parser
Version: 2.3.3.1-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Finished in 4.243802s, 201.7059 runs/s, 17410.8037 assertions/s.

  1) Failure:
TestCurrent#test_current 
[/build/ruby-whitequark-parser-2.3.3.1/test/test_current.rb:22]:
Update test_current for 2.5.0

856 runs, 73888 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/bug_163/test_runner_rewrite.rb" "test/test_base.rb" 
"test/test_current.rb" "test/test_diagnostic.rb" 
"test/test_diagnostic_engine.rb" "test/test_encoding.rb" "test/test_lexer.rb" 
"test/test_lexer_stack_state.rb" "test/test_parse_helper.rb" 
"test/test_parser.rb" "test/test_source_buffer.rb" 
"test/test_source_comment.rb" "test/test_source_comment_associator.rb" 
"test/test_source_map.rb" "test/test_source_range.rb" 
"test/test_source_rewriter.rb" "test/test_source_rewriter_action.rb" 
"test/test_static_environment.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-whitequark-parser-2.3.3.1/debian/ruby-whitequark-parser returned 
exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-whitequark-parser.log

Please fix it!

Cheers,
Chris.

Bug#888172: ruby-rspec-its: FTBFS on ruby2.5: Fixnum/Integer

[Chris West (Faux)]

Source: ruby-rspec-its
Version: 1.2.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) RSpec::Its#its with explicit subject when it responds to #[] [:b, "c", 4] 
should eq "Symbol: b; String: c; Fixnum: 4"
 Failure/Error: 
RSpec::Expectations::PositiveExpectationHandler.handle_matcher(__its_subject, 
matcher, message)

   expected: "Symbol: b; String: c; Fixnum: 4"
got: "Symbol: b; String: c; Integer: 4"

   (compared using ==)
 # ./spec/rspec/its_spec.rb:89:in `block (5 levels) in '

Finished in 0.02877 seconds (files took 0.09433 seconds to load)
34 examples, 1 failure

Failed examples:

rspec ./spec/rspec/its_spec.rb:89 # RSpec::Its#its with explicit subject when 
it responds to #[] [:b, "c", 4] should eq "Symbol: b; String: c; Fixnum: 4"

Randomized with seed 35708

/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/ruby-rspec-its-1.2.0/debian/ruby-rspec-its returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-rspec-its.log

Please fix it!

Cheers,
Chris.

Bug#888173: ruby-sawyer: FTBFS on ruby2.5: can't dump anonymous class

[Chris West (Faux)]

Source: ruby-sawyer
Version: 0.8.1-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


48 runs, 193 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-sawyer/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"sawyer\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-sawyer-0.8.1/debian/ruby-sawyer/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-sawyer/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
Run options: --seed 2029

# Running:

E..E

Finished in 0.805228s, 59.6105 runs/s, 239.6838 assertions/s.

  1) Error:
Sawyer::ResourceTest#test_handle_yaml_dump:
TypeError: can't dump anonymous class: 
#
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:343:in `visit_Class'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:136:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:546:in `block in dump_ivars'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:544:in `each'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:544:in `dump_ivars'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:163:in `visit_Object'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:136:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/yaml_tree.rb:118:in `push'
/usr/lib/ruby/2.5.0/psych.rb:441:in `dump'
/build/ruby-sawyer-0.8.1/test/resource_test.rb:172:in 
`test_handle_yaml_dump'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'

  2) Error:
Sawyer::AgentTest#test_handle_yaml_dump_and_load:
NoMethodError: undefined method `[]' for nil:NilClass
/usr/lib/ruby/vendor_ruby/faraday/utils.rb:48:in `[]='
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:362:in `block in revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each_slice'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:271:in `block in 
visit_Psych_Nodes_Mapping'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:268:in `each'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:268:in `each_slice'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:268:in 
`visit_Psych_Nodes_Mapping'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in `visit'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:32:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:338:in `block in revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each_slice'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:374:in `revive'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:208:in 
`visit_Psych_Nodes_Mapping'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in `visit'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:32:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:338:in `block in revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each_slice'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `revive_hash'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:374:in `revive'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:208:in 
`visit_Psych_Nodes_Mapping'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in `visit'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:32:in `accept'
/usr/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:311:in 
`visit_Psych_Nodes_Document'
/usr/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in 

Bug#888171: ruby-riot: FTBFS on ruby2.5: expected "\"hope\"", not "hope"

[Chris West (Faux)]

Source: ruby-riot
Version: 0.12.7-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt.

That minus sign means the test failed. What .. why.. ugh. Colours, ugh.



  + asserts that it is a kind of Riot::Message
  - asserts to_s: expected "should have \"hope\"", not should have "hope" 
kind of? Riot::Message send :to_s
An AssertionMacro instance receiving #expected_message
  + asserts that it is a kind of Riot::Message
  - asserts to_s: expected "expected \"hope\"", not expected "hope" kind 
of? Riot::Message send :to_s
AssertionMacro#fail
  + asserts that it includes 5
  + asserts that it includes "foo"
An assertion that is passing
  + asserts to_s
  + asserts :pass is returned when evaluated
An assertion that is failing
  + asserts to_s
  + asserts :fail and message are evaluated is equal to [:fail, "Expected 
non-false but got nil instead"]
An assertion that is erroring
  + asserts to_s
  + asserts :error and exception are evaluated
An assertion with no block to provide the actual value
  + should return a block that returns false is equal to [:fail, "Expected 
non-false but got false instead", nil, nil]
An assertion with block expectation
  + should use block returning topic as default is equal to [:pass, "is 
equal to \"hello\""]
  + asserts block expectation has access to the situation items is equal 
to [:pass, "is equal to \"hello\""]
An assertion with symbolic description
  + asserts upcase is equal to "FOO"
Executing setup with an error
  + asserts result is equal to :setup_error


395 passes, 4 failures, 0 errors in 0.020937 seconds
rake aborted!
Command failed with status (1)

Tasks: TOP => default => test:core
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-riot-0.12.7/debian/ruby-riot 
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-riot.log

Please fix it!

Cheers,
Chris.

Bug#888170: ruby-redcloth: FTBFS on ruby2.5: undefined method `load_documents' for Psych:Module

[Chris West (Faux)]

Source: ruby-redcloth
Version: 4.3.2-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Finished in 1.43 seconds (files took 0.86964 seconds to load)
5797 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-redcloth-4.3.2/debian/ruby-redcloth/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0:/build/ruby-redcloth-4.3.2/debian/ruby-redcloth/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-redcloth/usr/share/rubygems-integration/2.5.0:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
/build/ruby-redcloth-4.3.2/spec/spec_helper.rb:29:in `block in fixtures': 
undefined method `load_documents' for Psych:Module (NoMethodError)
Did you mean?  load_stream
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:26:in `each'
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:26:in `fixtures'
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:9:in 
`examples_from_yaml'
from 
/build/ruby-redcloth-4.3.2/spec/formatters/class_filtered_html_spec.rb:4:in 
`block in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:385:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:385:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:258:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:84:in `block (2 
levels) in expose_example_group_alias_globally'
from 
/build/ruby-redcloth-4.3.2/spec/formatters/class_filtered_html_spec.rb:3:in 
`'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-redcloth-4.3.2/debian/ruby-redcloth returned exit code 1
make: *** [binary] Error 1
debian/rules:15: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-redcloth.log

Please fix it!

Cheers,
Chris.

Bug#888168: ruby-redcarpet: FTBFS on ruby2.5: incompatible library version

[Chris West (Faux)]

Source: ruby-redcarpet
Version: 3.4.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition


It seems to build then fail to load its extension? Not seen this on
other packages.


Build log excerpt:


┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-redcarpet-3.4.0 debian/ruby-redcarpet
"make clean"
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
"make clean"
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
/usr/bin/ruby2.5 -r ./siteconf20180123-308-zr9kz6.rb extconf.rb
creating Makefile
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
rm -f 
rm -f redcarpet.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o autolink.o -c autolink.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o buffer.o -c buffer.c
buffer.c: In function 'bufcstr':
buffer.c:111:45: warning: passing argument 1 of 'bufgrow' discards 'const' 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  if (buf->size + 1 <= buf->asize || bufgrow(buf, buf->size + 1) == BUF_OK) {
 ^~~
buffer.c:60:1: note: expected 'struct buf *' but argument is of type 'const 
struct buf *'
 bufgrow(struct buf *buf, size_t neosz)
 ^~~
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o houdini_href_e.o -c houdini_href_e.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o houdini_html_e.o -c houdini_html_e.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o html.o -c html.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o html_smartypants.o -c html_smartypants.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o markdown.o -c markdown.c
markdown.c: In function 'sd_markdown_render':
markdown.c:2836:43: warning: passing argument 1 of 'is_codefence' discards 
'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
   if (codefences_enabled && (is_codefence(document + beg, doc_size - beg, 
NULL) != 0))
   ^~~~
markdown.c:1389:1: note: expected 'uint8_t * {aka unsigned 

Bug#888167: ruby-recursive-open-struct: FTBFS on ruby2.5: indifferent access overwriting values

[Chris West (Faux)]

Source: ruby-recursive-open-struct
Version: 1.0.2-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Failures:

  1) RecursiveOpenStruct indifferent access overwriting values when 
preserve_original_keys is enabled preserves the original keys after resetting 
value
 Failure/Error: expect(recursive.to_h).to eq modified_hash

   expected: {:foo=>[{"bar"=>[{"foo"=>:foo}]}]}
got: {:foo=>[{"bar"=>[{"foo"=>:bar, :foo=>:foo}]}]}

   (compared using ==)

   Diff:
   @@ -1,2 +1,2 @@
   -:foo => [{"bar"=>[{"foo"=>:foo}]}],
   +:foo => [{"bar"=>[{"foo"=>:bar, :foo=>:foo}]}],
 # ./spec/recursive_open_struct/indifferent_access_spec.rb:158:in `block (6 
levels) in '

Finished in 0.0499 seconds (files took 0.25849 seconds to load)
102 examples, 1 failure

Failed examples:

rspec ./spec/recursive_open_struct/indifferent_access_spec.rb:156 # 
RecursiveOpenStruct indifferent access overwriting values when 
preserve_original_keys is enabled preserves the original keys after resetting 
value

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-recursive-open-struct-1.0.2/debian/ruby-recursive-open-struct 
returned exit code 1
make: *** [binary] Error 1
debian/rules:6: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-recursive-open-struct.log

Please fix it!

Cheers,
Chris.

Bug#888166: ruby-rabl: FTBFS on ruby2.5: BSON:Module serialize

[Chris West (Faux)]

Source: ruby-rabl
Version: 0.13.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition


Looks very similar to this issue, fixed last year:
https://bugs.debian.org/849315

Build log excerpt:

ERROR
 Rabl::Engine with bson defaults #object asserts that it sets data source => 
undefined method `serialize' for BSON:Module occured
 at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block in run'
at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `each'
at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block (2 levels) in run'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in run_sub_contexts'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in run_sub_contexts'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:97:in `run'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `local_run'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `each'
at /usr/lib/ruby/vendor_ruby/riot/context.rb:109:in `block in local_run'
at /usr/lib/ruby/vendor_ruby/riot/rr.rb:33:in `run'
at /usr/lib/ruby/vendor_ruby/riot/assertion.rb:51:in `run'
at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `evaluate'
at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `instance_eval'
at /build/ruby-rabl-0.13.0/test/bson_engine_test.rb:22:in `block (4 levels) in 
'
at /usr/lib/ruby/vendor_ruby/tilt/template.rb:96:in `render'
at /build/ruby-rabl-0.13.0/lib/rabl/template.rb:15:in `evaluate'
at /build/ruby-rabl-0.13.0/lib/rabl/engine.rb:47:in `render'
at /build/ruby-rabl-0.13.0/lib/rabl/engine.rb:380:in `cache_results'
at /build/ruby-rabl-0.13.0/lib/rabl/engine.rb:48:in `block in render'
at /build/ruby-rabl-0.13.0/lib/rabl/engine.rb:154:in `to_bson'

ERROR
 Rabl::Engine with bson defaults #object asserts that it can set root node => 
undefined method `serialize' for BSON:Module occured
 at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'

...

166 passes, 0 failures, 142 errors in 0.540211 seconds
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-rabl-0.13.0/debian/ruby-rabl 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-rabl.log

Please fix it!

Cheers,
Chris.

Bug#888164: ruby-packable: FTBFS on ruby2.5: Illegal seek @ rb_io_tell

[Chris West (Faux)]

Source: ruby-packable
Version: 1.3.8-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


┌──┐
│ Run tests for ruby2.3 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-packable/usr/share/rubygems-integration/all:/root/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 55512

# Running:

/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:57:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
.

Finished in 0.006436s, 2641.5416 runs/s, 10721.5511 assertions/s.

17 runs, 69 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-packable/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
/usr/lib/ruby/vendor_ruby/backports/1.8.7/fixnum/div.rb:1: warning: constant 
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/backports/1.8.7/fixnum/fdiv.rb:1: warning: constant 
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/backports/2.1.0/bignum/bit_length.rb:1: warning: 
constant ::Bignum is deprecated
/usr/lib/ruby/vendor_ruby/backports/2.1.0/fixnum/bit_length.rb:1: warning: 
constant ::Fixnum is deprecated
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:86:in
 `pos': Illegal seek @ rb_io_tell -  (Errno::ESPIPE)
from 
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:86:in
 `pack_and_write'
from 
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:62:in
 `write_with_packing'
from /usr/lib/ruby/vendor_ruby/minitest.rb:580:in `puts'



Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-packable.log

Please fix it!

Cheers,
Chris.

Bug#888161: ruby-multimap: FTBFS on ruby2.5: error: void value not ignored as it ought to be

[Chris West (Faux)]

Source: ruby-multimap
Version: 1.1.2+gh-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


┌──┐
│ Build native extensions for ruby2.3  │
└──┘

/usr/bin/ruby2.3 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-multimap-1.1.2+gh debian/ruby-multimap
current directory: /build/ruby-multimap-1.1.2+gh/ext
/usr/bin/ruby2.3 -r ./siteconf20180123-295-zokl7l.rb extconf.rb
creating Makefile
current directory: /build/ruby-multimap-1.1.2+gh/ext
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
rm -f 
rm -f nested_multimap_ext.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'
current directory: /build/ruby-multimap-1.1.2+gh/ext
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.3-KwDbD6/ruby2.3-2.3.6=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o 
nested_multimap_ext.o -c nested_multimap_ext.c
nested_multimap_ext.c: In function 'rb_nested_multimap_aref':
nested_multimap_ext.c:16:3: warning: 'rb_hash_ifnone' is deprecated 
[-Wdeprecated-declarations]
   r = (i < argc) ? rb_hash_aref(h, argv[i]) : RHASH_IFNONE(h);
   ^
In file included from /usr/include/ruby-2.3.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.3.0/ruby.h:33,
 from nested_multimap_ext.c:1:
/usr/include/ruby-2.3.0/ruby/intern.h:534:18: note: declared here
 DEPRECATED(VALUE rb_hash_ifnone(VALUE));
  ^
/usr/include/x86_64-linux-gnu/ruby-2.3.0/ruby/config.h:126:52: note: in 
definition of macro 'DEPRECATED'
 #define DEPRECATED(x) __attribute__ ((deprecated)) x
^
rm -f nested_multimap_ext.so
gcc -shared -o nested_multimap_ext.so nested_multimap_ext.o -L. 
-L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -Wl,-z,now -fstack-protector 
-rdynamic -Wl,-export-dynamic-lruby-2.3  -lpthread -lgmp -ldl -lcrypt -lm   
-lc
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'
current directory: /build/ruby-multimap-1.1.2+gh/ext
make V=1 "DESTDIR=" install
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
/bin/mkdir -p . ./.gem.20180123-295-ko5yp8
exit > .RUBYARCHDIR.time
/usr/bin/install -c -m 0755 nested_multimap_ext.so ./.gem.20180123-295-ko5yp8
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'

┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-multimap-1.1.2+gh debian/ruby-multimap
"make clean"
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'
"make clean"
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'
current directory: /build/ruby-multimap-1.1.2+gh/ext
/usr/bin/ruby2.5 -r ./siteconf20180123-325-11zh9ye.rb extconf.rb
creating Makefile
current directory: /build/ruby-multimap-1.1.2+gh/ext
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
rm -f 
rm -f nested_multimap_ext.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/build/ruby-multimap-1.1.2+gh/ext'
current directory: /build/ruby-multimap-1.1.2+gh/ext
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-multimap-1.1.2+gh/ext'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o 
nested_multimap_ext.o -c nested_multimap_ext.c
nested_multimap_ext.c: In function 'rb_nested_multimap_aref':
nested_multimap_ext.c:16:3: warning: 'rb_hash_ifnone' is deprecated 
[-Wdeprecated-declarations]
   r = (i < argc) ? rb_hash_aref(h, argv[i]) : RHASH_IFNONE(h);
   ^
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from nested_multimap_ext.c:1:

Bug#888165: ruby-puppet-syntax: FTBFS on ruby2.5: OpenSSL::ASN1::ASN1Error: oid exists

[Chris West (Faux)]

Source: ruby-puppet-syntax
Version: 2.4.1-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) PuppetSyntax::Manifests should return nothing from a valid file with a 
class using tag parameter
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:21:in `block (2 levels) in '

  2) PuppetSyntax::Manifests should return an error from an invalid file
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:29:in `block (2 levels) in '

  3) PuppetSyntax::Manifests should return a warning from an invalid file
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:44:in `block (2 levels) in '

  4) PuppetSyntax::Manifests should ignore warnings about storeconfigs
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:55:in `block (2 levels) in '

  5) PuppetSyntax::Manifests should read more than one valid file
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:64:in `block (2 levels) in '

  6) PuppetSyntax::Manifests should continue after finding an error in the 
first file
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:72:in `block (2 levels) in '

  7) PuppetSyntax::Manifests deprecation notices on puppet 4.0.0 and above 
should instead be failures
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:96:in `block (4 levels) in '

  8) PuppetSyntax::Manifests app_management app_management = false (default) 
should fail to parse an application manifest
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:148:in `block (4 levels) in '

  9) PuppetSyntax::Manifests app_management app_management = true should 
successfully parse an application manifest on Puppet >= 4.3.0
 Failure/Error: Puppet::Test::TestHelper.initialize

 OpenSSL::ASN1::ASN1Error:
   oid exists
 # ./lib/puppet-syntax/manifests.rb:12:in `check'
 # ./spec/puppet-syntax/manifests_spec.rb:163:in `block (4 levels) in '

  10) PuppetSyntax::Manifests future_parser future_parser = false (default) 
should succeed on Puppet >= 4.0.0
  Failure/Error: Puppet::Test::TestHelper.initialize

  OpenSSL::ASN1::ASN1Error:
oid exists
  # ./lib/puppet-syntax/manifests.rb:12:in `check'
  # ./spec/puppet-syntax/manifests_spec.rb:201:in `block (4 levels) in '

Finished in 0.11609 seconds (files took 0.82926 seconds to load)
44 examples, 10 failures, 2 pending

Failed examples:

rspec ./spec/puppet-syntax/manifests_spec.rb:19 # PuppetSyntax::Manifests 
should return nothing from a valid file with a class using tag parameter
rspec ./spec/puppet-syntax/manifests_spec.rb:27 # PuppetSyntax::Manifests 
should return an error from an invalid file
rspec ./spec/puppet-syntax/manifests_spec.rb:42 # PuppetSyntax::Manifests 
should return a warning from an invalid file
rspec ./spec/puppet-syntax/manifests_spec.rb:53 # PuppetSyntax::Manifests 
should ignore warnings about storeconfigs
rspec ./spec/puppet-syntax/manifests_spec.rb:62 # PuppetSyntax::Manifests 
should read more than one valid file
rspec ./spec/puppet-syntax/manifests_spec.rb:70 # PuppetSyntax::Manifests 
should continue after finding an error in the first file
rspec ./spec/puppet-syntax/manifests_spec.rb:94 # PuppetSyntax::Manifests 
deprecation notices on puppet 4.0.0 and above should instead be failures
rspec ./spec/puppet-syntax/manifests_spec.rb:145 # PuppetSyntax::Manifests 
app_management app_management = false (default) should fail to parse an 
application manifest
rspec ./spec/puppet-syntax/manifests_spec.rb:159 # PuppetSyntax::Manifests 

Bug#888163: ruby-net-ssh: FTBFS on ruby2.5: OpenSSL::Digest::DSS1

[Chris West (Faux)]

Source: ruby-net-ssh
Version: 1:4.2.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Finished in 2.351047s, 628.2308 runs/s, 2105.0196 assertions/s.

  1) Error:
Authentication::TestAgent#test_add_dsa_cert_identity:
NameError: uninitialized constant OpenSSL::Digest::DSS1
/build/ruby-net-ssh-4.2.0/lib/net/ssh/transport/openssl.rb:117:in 
`ssh_do_sign'
/build/ruby-net-ssh-4.2.0/lib/net/ssh/authentication/certificate.rb:80:in 
`sign!'
/build/ruby-net-ssh-4.2.0/test/authentication/test_agent.rb:401:in 
`make_cert'
/build/ruby-net-ssh-4.2.0/test/authentication/test_agent.rb:258:in 
`test_add_dsa_cert_identity'
/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'


...

  2) Error:
Authentication::TestED25519#test_no_pwd_key:
RuntimeError: No ED25519 set NET_SSH_NO_RBNACL to ignore this test
/build/ruby-net-ssh-4.2.0/test/authentication/test_ed25519.rb:11:in `setup'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:105: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'
..

  3) Error:
Authentication::TestED25519#test_pwd_key:
RuntimeError: No ED25519 set NET_SSH_NO_RBNACL to ignore this test
/build/ruby-net-ssh-4.2.0/test/authentication/test_ed25519.rb:11:in `setup'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:105: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'
..


1477 runs, 4949 assertions, 0 failures, 3 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_all.rb" 
"test/test_buffer.rb" "test/test_buffered_io.rb" "test/test_config.rb" 
"test/test_key_factory.rb" "test/test_known_hosts.rb" "test/test_proxy_jump.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-net-ssh-4.2.0/debian/ruby-net-ssh returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-net-ssh.log

Please fix it!

Cheers,
Chris.

Bug#888160: ruby-memfs: FTBFS on ruby2.5: No such file or directory - /test-file

[Chris West (Faux)]

Source: ruby-memfs
Version: 0.5.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Failures:

  1) FileUtils.copy_entry when +src+ does not exist raises an exception
 Failure/Error: find(path) || fail(Errno::ENOENT, path)

 Errno::ENOENT:
   No such file or directory - /test-file
 # ./lib/memfs/file_system.rb:64:in `find!'
 # ./lib/memfs/file/stat.rb:56:in `initialize'
 # ./lib/memfs/file.rb:137:in `new'
 # ./lib/memfs/file.rb:137:in `lstat'
 # ./spec/fileutils_spec.rb:300:in `block (5 levels) in '
 # ./spec/spec_helper.rb:21:in `block (2 levels) in '
 # ./spec/fileutils_spec.rb:299:in `block (4 levels) in '

  2) FileUtils.rm_f calls rm with +:force+ set to true
 Failure/Error: described_class.rm_f('test')

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:886:in `block (3 levels) in '

  3) FileUtils.rm_rf calls rm with +:force+ set to true
 Failure/Error: described_class.rm_rf('test')

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:921:in `block (3 levels) in '

  4) FileUtils.rmdir when a directory is not empty ignores errors
 Failure/Error: expect { described_class.rmdir('/test-dir') }.not_to 
raise_error

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:946:in `block (4 levels) in '

  5) FileUtils.rmdir when a directory is not empty doesn't remove the directory
 Failure/Error: fail Errno::ENOTEMPTY, path unless directory.empty?

 Errno::ENOTEMPTY:
   Directory not empty - /test-dir
 # ./lib/memfs/file_system.rb:121:in `rmdir'
 # ./lib/memfs/dir.rb:84:in `rmdir'
 # ./spec/fileutils_spec.rb:950:in `block (4 levels) in '

Finished in 0.47079 seconds (files took 1.03 seconds to load)
784 examples, 5 failures, 7 pending

Failed examples:

rspec ./spec/fileutils_spec.rb:298 # FileUtils.copy_entry when +src+ does not 
exist raises an exception
rspec ./spec/fileutils_spec.rb:884 # FileUtils.rm_f calls rm with +:force+ set 
to true
rspec ./spec/fileutils_spec.rb:919 # FileUtils.rm_rf calls rm with +:force+ set 
to true
rspec ./spec/fileutils_spec.rb:945 # FileUtils.rmdir when a directory is not 
empty ignores errors
rspec ./spec/fileutils_spec.rb:949 # FileUtils.rmdir when a directory is not 
empty doesn't remove the directory

[Coveralls] Outside the CI environment, not sending data.
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-memfs-0.5.0/debian/ruby-memfs 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-memfs.log

Please fix it!

Cheers,
Chris.

Bug#888151: ruby-logging: FTBFS on ruby2.5: warning: constant ::Fixnum is deprecated

[Chris West (Faux)]

Source: ruby-logging
Version: 2.0.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


/usr/lib/ruby/vendor_ruby/test/unit/autorunner.rb:62:in `run'
/usr/lib/ruby/vendor_ruby/test/unit.rb:502:in `block (2 levels) in '
F
===
Failure:
   \[1,\ 2,\ 3,\ 4\]/> was expected to be =~
  <"/build/ruby-logging-2.0.0/lib/logging/appender.rb:141: warning: constant 
::Fixnum is deprecated\n">.
test_append(TestLogging::TestAppenders::TestSyslog)
/build/ruby-logging-2.0.0/test/appenders/test_syslog.rb:55:in `test_append'
 52:   Process.waitpid(pid)
 53: 
 54:   if defined?(::Syslog::LOG_PERROR)
  => 55: assert_match(%r/INFO  TestLogger :  #{Regexp.escape 
[1,2,3,4].to_s}/, stderr[0].gets)
 56: assert_match(%r/DEBUG  TestLogger : the big log message/, 
stderr[0].gets)
 57: assert_match(%r/WARN  TestLogger : this is your last warning/, 
stderr[0].gets)
 58:   end
===
Thread.exclusive is deprecated, use Thread::Mutex
/build/ruby-logging-2.0.0/lib/logging/diagnostic_context.rb:384:in 
`clear_diagnostic_contexts'

..

Finished in 8.999016755 seconds.
--
176 tests, 1093 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
98.8636% passed
--
19.56 tests/s, 121.46 assertions/s
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-logging-2.0.0/debian/ruby-logging returned exit code 1
make: *** [binary] Error 1
debian/rules:18: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-logging.log

Please fix it!

Cheers,
Chris.

Bug#888150: ruby-graphviz: FTBFS on ruby2.5: undefined method `graph' for nil

[Chris West (Faux)]

Source: ruby-graphviz
Version: 1.2.2-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


100 tests, 258 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
100% passed
--
9.15 tests/s, 23.62 assertions/s
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-graphviz-1.2.2/debian/ruby-graphviz/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-graphviz/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/output/dot/hello_test.rb" "test/output/dot/test_parse.rb" 
"test/output/rgv/test_rgv.rb" "test/test_dot_script.rb" "test/test_examples.rb" 
"test/test_graph.rb" "test/test_search.rb" "test/test_subgraph.rb" 
"test/test_theory.rb" "test/test_types.rb" "test/test_utils_colors.rb" -v
/build/ruby-graphviz-1.2.2/test/output/dot/hello_test.rb:6: warning: shadowing 
outer local variable - g
/build/ruby-graphviz-1.2.2/debian/ruby-graphviz/usr/lib/ruby/vendor_ruby/graphviz/dot2ruby.rb:51:
 warning: instance variable @_graph_eval not initialized
/build/ruby-graphviz-1.2.2/test/output/dot/hello_test.rb:18:in `': undefined method `graph' for nil:NilClass (NoMethodError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/output/dot/hello_test.rb" "test/output/dot/test_parse.rb" 
"test/output/rgv/test_rgv.rb" "test/test_dot_script.rb" "test/test_examples.rb" 
"test/test_graph.rb" "test/test_search.rb" "test/test_subgraph.rb" 
"test/test_theory.rb" "test/test_types.rb" "test/test_utils_colors.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-graphviz-1.2.2/debian/ruby-graphviz returned exit code 1
debian/rules:10: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-graphviz.log

Please fix it!

Cheers,
Chris.

Bug#888149: ruby-escape-utils: FTBFS on ruby2.5: property file encoding: UTF-8

[Chris West (Faux)]

Source: ruby-escape-utils
Version: 1.1.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


87 runs, 889 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-escape-utils-1.1.0/debian/ruby-escape-utils/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0:/build/ruby-escape-utils-1.1.0/debian/ruby-escape-utils/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-escape-utils/usr/share/rubygems-integration/2.5.0:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
Run options: --seed 52013

# Running:

...FF..

Finished in 0.077953s, 1116.0561 runs/s, 11378.6407 assertions/s.

  1) Failure:
UrlEscapeTest#test_cgi_stdlib_compatibility 
[/build/ruby-escape-utils-1.1.0/test/url/escape_test.rb:12]:
--- expected
+++ actual
@@ -1 +1,2 @@
-"~"
+# encoding: UTF-8
+"%7E"


  2) Failure:
UriComponentEscapeTest#test_cgi_equivalence 
[/build/ruby-escape-utils-1.1.0/test/uri_component/escape_test.rb:14]:
--- expected
+++ actual
@@ -1 +1,2 @@
-"~"
+# encoding: UTF-8
+"%7E"


87 runs, 887 assertions, 2 failures, 0 errors, 0 skips
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-escape-utils-1.1.0/debian/ruby-escape-utils returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-escape-utils.log

Please fix it!

Cheers,
Chris.

Bug#888148: ruby-certificate-authority: FTBFS on ruby2.5: CSR varies?

[Chris West (Faux)]

Source: ruby-certificate-authority
Version: 0.2.0~6dd483bf-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) CertificateAuthority::SigningRequest Generating CSRs should generate a CSR
 Failure/Error: expect(@csr.to_pem).to eq(expected)

   expected: "-BEGIN CERTIFICATE 
REQUEST-\nMIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay\nreDW940=\n-END
 CERTIFICATE REQUEST-\n"
got: "-BEGIN CERTIFICATE 
REQUEST-\nMIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...N1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+\ngPav58ePPg==\n-END
 CERTIFICATE REQUEST-\n"

   (compared using ==)

   Diff:

   @@ -1,11 +1,11 @@
-BEGIN CERTIFICATE REQUEST-
   -MIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
   +MIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
BQADgY0AMIGJAoGBALGIZV9Gt/3QIea9dr5dhYTibstnWyVzpzEhjIiBm5DlPwB6
pRqRvJhjjAxRHaBnikM+z9Yazx9brqrbeqYdKvVtDodovzOdsPtQv8iKLKJbwjXW
ituuGKYjHUDrTqqLz/SBBz4fznWDNS6x3nGAo/Zf6g/FjHdUbd2mSwuc0rUjAgMB
   -AAEwDQYJKoZIhvcNAQENBQADgYEAZWLXHmJJyHz+9AdWUJ3U3pLHR/ghA1f3Ihyu
   -2PuYvwqfnGfGTA8DUnQx7l7J6ATIn76SBadmOquBBbbuhJG05WfKZt0oqCAPdsIa
   -XBlLOqVQmWR7YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay
   -reDW940=
   +AAGgADANBgkqhkiG9w0BAQ0FAAOBgQANCCSnS9L5tUZrtysGF+uP+eSc6O76jRbL
   +9XueRH57ZIddHm/z3xK/01IjyKVlLK7azlL187K1JZwBCwREhodBRULoQJGumhRT
   +qh9RuoJtuzEmviAYN1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+
   +gPav58ePPg==
-END CERTIFICATE REQUEST-
 # ./spec/units/signing_request_spec.rb:137:in `block (3 levels) in '

Finished in 2.15 seconds (files took 0.57521 seconds to load)
196 examples, 1 failure, 3 pending

Failed examples:

rspec ./spec/units/signing_request_spec.rb:124 # 
CertificateAuthority::SigningRequest Generating CSRs should generate a CSR

[Coveralls] Outside the CI environment, not sending data.
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-certificate-authority-0.2.0\~6dd483bf/debian/ruby-certificate-authority
 returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-certificate-authority.log

Please fix it!

Cheers,
Chris.

Bug#888147: ruby-backports: FTBFS on ruby2.5: tests: encoding change

[Chris West (Faux)]

Source: ruby-backports
Version: 3.6.8-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


51 tests, 170 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
100% passed
--
63.57 tests/s, 211.91 assertions/s
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-backports-3.6.8/debian/ruby-backports/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-backports/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
/build/ruby-backports-3.6.8/test/_backport_guards_test.rb:51: warning: constant 
::Fixnum is deprecated
/build/ruby-backports-3.6.8/test/lazy_test.rb:212: warning: assigned but unused 
variable - enum
/build/ruby-backports-3.6.8/test/lazy_test.rb:304: warning: assigned but unused 
variable - bug7696
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
.F
===
Failure: test__2_backports_wont_override_unnecessarily(AAA_TestBackportGuards)
/build/ruby-backports-3.6.8/test/_backport_guards_test.rb:30:in `teardown'
<"">(UTF-8) expected but was
<"/build/ruby-backports-3.6.8/lib/backports/tools/extreme_object.rb:4: warning: 
parentheses after method name is interpreted as an argument list, not a 
decomposed argument\n" +
"/build/ruby-backports-3.6.8/lib/backports/tools/extreme_object.rb:8: warning: 
parentheses after method name is interpreted as an argument list, not a 
decomposed argument\n" +
"/build/ruby-backports-3.6.8/lib/backports/1.8.7/fixnum/div.rb:1: warning: 
constant ::Fixnum is deprecated\n" +
"/build/ruby-backports-3.6.8/lib/backports/1.8.7/fixnum/fdiv.rb:1: warning: 
constant ::Fixnum is deprecated\n">(US-ASCII)

diff:
+ /build/ruby-backports-3.6.8/lib/backports/tools/extreme_object.rb:4: warning: 
parentheses after method name is interpreted as an argument list, not a 
decomposed argument
+ /build/ruby-backports-3.6.8/lib/backports/tools/extreme_object.rb:8: warning: 
parentheses after method name is interpreted as an argument list, not a 
decomposed argument
+ /build/ruby-backports-3.6.8/lib/backports/1.8.7/fixnum/div.rb:1: warning: 
constant ::Fixnum is deprecated
+ /build/ruby-backports-3.6.8/lib/backports/1.8.7/fixnum/fdiv.rb:1: warning: 
constant ::Fixnum is deprecated
  
? Encoding: UTF-8
?S  ASCII
===
F
===
Failure: 
test_setlib_load_correctly_after_requiring_backports(AAA_TestBackportGuards)
/build/ruby-backports-3.6.8/test/_backport_guards_test.rb:30:in `teardown'
<"">(UTF-8) expected but was
<"/build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:973: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument\n" +
"/build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:1468: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument\n" +
"/build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:1481: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument\n">(US-ASCII)

diff:
+ /build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:973: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument
+ /build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:1468: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument
+ /build/ruby-backports-3.6.8/lib/backports/1.9.2/stdlib/matrix.rb:1481: 
warning: parentheses after method name is interpreted as an argument list, not 
a decomposed argument
  
? Encoding: UTF-8
?S  ASCII
===


Finished in 0.500010822 seconds.
--
51 tests, 170 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
100% passed
--
102.00 tests/s, 339.99 assertions/s
/usr/lib/ruby/vendor_ruby/rake/testtask.rb:130:in `block (3 levels) in define': 
Command failed with status (1) (RuntimeError)
from 

Bug#888145: r10k: FTBFS on ruby2.5: undefined method `features' for Rugged:Module

[Chris West (Faux)]

Source: r10k
Version: 2.6.1-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Finished in 7.41 seconds (files took 0.74599 seconds to load)
707 examples, 0 failures, 3 pending

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/r10k-2.6.1/debian/r10k/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/r10k/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb  
--exclude-pattern ./spec/unit/forge/module_release_spec.rb
...*...FFF.*.*...# terminated with exception (report_on_exception is true):
/build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:53:in `select': 
closed stream (IOError)
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:53:in 
`rescue in pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:48:in 
`pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:30:in 
`block in start'
# terminated with exception (report_on_exception is true):
:74:in `__read_nonblock': stream closed in another thread 
(IOError)
from :74:in `read_nonblock'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:49:in 
`pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:30:in 
`block in start'
...

Pending: (Failures listed here are expected and do not affect your suite's 
status)

...

Failures:

  1) R10K::Git explicitly setting the provider under c-based rubies sets the 
current provider if the provider exists and is functional
 Failure/Error: if !::Rugged.features.include?(transport)

 NoMethodError:
   undefined method `features' for Rugged:Module
 # ./lib/r10k/git.rb:31:in `block (2 levels) in '
 # ./lib/r10k/git.rb:30:in `each'
 # ./lib/r10k/git.rb:30:in `block in '
 # ./lib/r10k/git.rb:92:in `provider='
 # ./spec/unit/git_spec.rb:59:in `block (4 levels) in '

  2) R10K::Git retrieving the current provider under c-based rubies uses the 
default if a provider has not been set
 Failure/Error: raise R10K::Error, _("Git provider '%{name}' is not 
functional.") % {name: name}

 R10K::Error:
   Git provider 'rugged' is not functional.
 # ./lib/r10k/git.rb:89:in `provider='
 # ./lib/r10k/git.rb:106:in `provider'
 # ./spec/unit/git_spec.rb:77:in `block (4 levels) in '

  3) R10K::Git retrieving the current provider under c-based rubies uses an 
explicitly set provider
 Failure/Error: if !::Rugged.features.include?(transport)

 NoMethodError:
   undefined method `features' for Rugged:Module
 # ./lib/r10k/git.rb:31:in `block (2 levels) in '
 # ./lib/r10k/git.rb:30:in `each'
 # ./lib/r10k/git.rb:30:in `block in '
 # ./lib/r10k/git.rb:92:in `provider='
 # ./spec/unit/git_spec.rb:82:in `block (4 levels) in '

Finished in 3.97 seconds (files took 0.70702 seconds to load)
660 examples, 3 failures, 3 pending

Failed examples:

rspec ./spec/unit/git_spec.rb:57 # R10K::Git explicitly setting the provider 
under c-based rubies sets the current provider if the provider exists and is 
functional
rspec ./spec/unit/git_spec.rb:75 # R10K::Git retrieving the current provider 
under c-based rubies uses the default if a provider has not been set
rspec ./spec/unit/git_spec.rb:80 # R10K::Git retrieving the current provider 
under c-based rubies uses an explicitly set provider

/usr/bin/ruby2.5 /usr/bin/rspec --pattern 

Bug#888146: ruby-autoparse: FTBFS on ruby2.5: undefined method `[]' for 3.14:Float

[Chris West (Faux)]

Source: ruby-autoparse
Version: 0.3.3-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Deprecation Warnings:


JSONMatchers::EqualsJson implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /build/ruby-autoparse-0.3.3/spec/autoparse/instance_spec.rb:69:in 
`block (2 levels) in ')


JSONMatchers::EqualsJson implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /build/ruby-autoparse-0.3.3/spec/autoparse/instance_spec.rb:149:in 
`block (2 levels) in ')


JSONMatchers::EqualsJson implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /build/ruby-autoparse-0.3.3/spec/autoparse/instance_spec.rb:369:in 
`block (2 levels) in ')

Too many similar deprecation messages reported, disregarding further reports. 
Pass `--deprecation-out` or set `config.deprecation_stream` to a file for full 
output.

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/ruby-autoparse-0.3.3/spec/autoparse/instance_spec.rb:31:in `block (2 
levels) 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.

Failures:

  1) AutoParse::Instance with the node schema should not accept an invalid node 
input
 Failure/Error: if data['$ref']

 NoMethodError:
   undefined method `[]' for 3.14:Float
 # ./lib/autoparse/instance.rb:303:in `initialize'
 # ./lib/autoparse/instance.rb:172:in `new'
 # ./lib/autoparse/instance.rb:172:in `validate_object_property'
 # ./lib/autoparse/instance.rb:205:in `block in validate_union_property'
 # ./lib/autoparse/instance.rb:182:in `each'
 # ./lib/autoparse/instance.rb:182:in `validate_union_property'
 # ./lib/autoparse/instance.rb:272:in `validate_property_value'
 # ./lib/autoparse/instance.rb:397:in `block in valid?'
 # ./lib/autoparse/instance.rb:395:in `each'
 # ./lib/autoparse/instance.rb:395:in `valid?'
 # ./spec/autoparse/instance_spec.rb:1369:in `block (2 levels) in '

11 deprecation warnings total

Finished in 0.28262 seconds (files took 0.21684 seconds to load)
111 examples, 1 failure

Failed examples:

rspec ./spec/autoparse/instance_spec.rb:1363 # AutoParse::Instance with the 
node schema should not accept an invalid node input

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-autoparse-0.3.3/debian/ruby-autoparse returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-autoparse.log

Please fix it!

Cheers,
Chris.

Bug#888135: ruby-lapack: FTBFS on ruby2.5: `dirname': no implicit conversion of nil into String

[Chris West (Faux)]

Source: ruby-lapack
Version: 1.7.2-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-lapack-1.7.2 debian/ruby-lapack
"make clean"
make[1]: Entering directory '/build/ruby-lapack-1.7.2/ext'
make[1]: Leaving directory '/build/ruby-lapack-1.7.2/ext'
"make clean"
make[1]: Entering directory '/build/ruby-lapack-1.7.2/ext'
make[1]: Leaving directory '/build/ruby-lapack-1.7.2/ext'
current directory: /build/ruby-lapack-1.7.2/ext
/usr/bin/ruby2.5 -r ./siteconf20180123-6749-8r2khb.rb extconf.rb
checking for -llapack... yes
extconf.rb:81:in `dirname': no implicit conversion of nil into String 
(TypeError)
from extconf.rb:81:in `'
~ ↓ mkmf.log ~
find_library: checking for -llapack...  yes

"gcc -o conftest -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC conftest.c  -L. 
-L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -Wl,-z,now -fstack-protector 
-rdynamic -Wl,-export-dynamic -lruby-2.5  -lpthread -lgmp -ldl -lcrypt -lm  
 -lc"
checked program was:
/* begin */
1: #include "ruby.h"
2: 
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */

"gcc -o conftest -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC conftest.c  -L. 
-L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -Wl,-z,now -fstack-protector 
-rdynamic -Wl,-export-dynamic -lruby-2.5 -llapack  -lpthread -lgmp -ldl 
-lcrypt -lm   -lc"
checked program was:
/* begin */
 1: #include "ruby.h"
 2: 
 3: /*top*/
 4: extern int t(void);
 5: int main(int argc, char **argv)
 6: {
 7:   if (argc > 100) {
 8: printf("%p", );
 9:   }
10: 
11:   return 0;
12: }
13: 
14: int t(void) { ; return 0; }
/* end */



/usr/lib/ruby/2.5.0/rubygems/ext/builder.rb:92:in `run': extconf failed, exit 
code 1 (Gem::InstallError)
from /usr/lib/ruby/2.5.0/rubygems/ext/ext_conf_builder.rb:46:in `block 
in build'
from /usr/lib/ruby/2.5.0/tempfile.rb:295:in `open'
from /usr/lib/ruby/2.5.0/rubygems/ext/ext_conf_builder.rb:30:in `build'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:76:in 
`block in build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
`chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
`build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:108:in 
`block in build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:105:in 
`each'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:105:in 
`build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:121:in 
`'
~ ↑ mkmf.log ~
/usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': /usr/bin/ruby2.5 
/usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /build/ruby-lapack-1.7.2 
debian/ruby-lapack (Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb.rb:67:in `run_ruby'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:37:in `block in 
install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in 
`install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in 
install'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
from /usr/bin/dh_ruby:94:in `'
dh_auto_install: dh_ruby --install /build/ruby-lapack-1.7.2/debian/tmp returned 
exit code 1
make: *** [binary] Error 1
debian/rules:4: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-lapack.log

Please fix it!

Cheers,
Chris.

Bug#888119: ruby-awesome-print: FTBFS on ruby2.5: test failure: colorization default

[Chris West (Faux)]

Source: ruby-awesome-print
Version: 1.6.1-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

...

Finished in 0.16369 seconds (files took 0.1327 seconds to load)
135 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-awesome-print-1.6.1/debian/ruby-awesome-print/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-awesome-print/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
FF.../build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: 
warning: constant ::Fixnum is deprecated
.FFF.../build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378:
 warning: constant ::Fixnum is deprecated
./build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: warning: 
constant ::Fixnum is deprecated
.../build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: warning: 
constant ::Fixnum is deprecated
./build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: warning: 
constant ::Fixnum is deprecated
.FF/build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378:
 warning: constant ::Fixnum is deprecated
./build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: 
warning: constant ::Fixnum is deprecated
F/build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378:
 warning: constant ::Fixnum is deprecated
./build/ruby-awesome-print-1.6.1/lib/awesome_print/formatter.rb:378: warning: 
constant ::Fixnum is deprecated


Failures:

  1) AwesomePrint colorization default settings (no forced colors) colorizes 
tty processes by default
 Failure/Error: expect(@arr.ai(:multiline => false)).to eq(COLORIZED)

   expected: "[ \e[1;34m1\e[0m, \e[0;36m:two\e[0m, \e[0;33m\"three\"\e[0m, 
[ \e[1;31mnil\e[0m, [ \e[1;32mtrue\e[0m, \e[1;31mfalse\e[0m ] ] ]"
got: "[ 1, \e[0;36m:two\e[0m, \e[0;33m\"three\"\e[0m, [ 
\e[1;31mnil\e[0m, [ \e[1;32mtrue\e[0m, \e[1;31mfalse\e[0m ] ] ]"

   (compared using ==)
 # ./spec/colors_spec.rb:33:in `block (4 levels) in '

  2) AwesomePrint colorization default settings (no forced colors) colorizes 
processes with ENV['ANSICON'] by default
 Failure/Error: expect(@arr.ai(:multiline => false)).to eq(COLORIZED)

   expected: "[ \e[1;34m1\e[0m, \e[0;36m:two\e[0m, \e[0;33m\"three\"\e[0m, 
[ \e[1;31mnil\e[0m, [ \e[1;32mtrue\e[0m, \e[1;31mfalse\e[0m ] ] ]"
got: "[ 1, \e[0;36m:two\e[0m, \e[0;33m\"three\"\e[0m, [ 
\e[1;31mnil\e[0m, [ \e[1;32mtrue\e[0m, \e[1;31mfalse\e[0m ] ] ]"

   (compared using ==)
 # ./spec/colors_spec.rb:40:in `block (4 levels) in '

  3) AwesomePrint colorization forced colors override still colorizes tty 
processes
 Failure/Error: expect(@arr.ai(:multiline => false)).to eq(COLORIZED)

...

Finished in 0.15707 seconds (files took 0.10502 seconds to load)
135 examples, 12 failures

Failed examples:

rspec ./spec/colors_spec.rb:31 # AwesomePrint colorization default settings (no 
forced colors) colorizes tty processes by default
rspec ./spec/colors_spec.rb:36 # AwesomePrint colorization default settings (no 
forced colors) colorizes processes with ENV['ANSICON'] by default
rspec ./spec/colors_spec.rb:71 # AwesomePrint colorization forced colors 
override still colorizes tty processes
rspec ./spec/colors_spec.rb:76 # AwesomePrint colorization forced colors 
override colorizes processes with ENV['ANSICON'] set to 0
rspec ./spec/colors_spec.rb:86 # AwesomePrint colorization forced colors 
override colorizes dumb terminals
rspec ./spec/colors_spec.rb:96 # AwesomePrint colorization forced colors 
override colorizes subprocess
rspec ./spec/formats_spec.rb:92 # AwesomePrint Array colored multiline (default)
rspec ./spec/formats_spec.rb:109 # AwesomePrint Array colored multiline indented
rspec ./spec/formats_spec.rb:126 # AwesomePrint Array colored single line
rspec ./spec/methods_spec.rb:12 # Single method plain: should handle a method 
with no arguments
rspec ./spec/methods_spec.rb:17 # Single method color: should handle a method 
with no arguments
rspec ./spec/misc_spec.rb:97 # AwesomePrint HTML output wraps multiline ap 
output with 

Bug#888132: ruby-state-machines-activerecord: FTBFS on ruby2.5: "File does not exist:"

[Chris West (Faux)]

Source: ruby-state-machines-activerecord
Version: 0.4.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


207 tests, 236 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

fatal: Not a git repository (or any of the parent directories): .git
GEM_PATH=debian/ruby-state-machines-activerecord/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"state_machines-activerecord\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-state-machines-activerecord-0.4.0/debian/ruby-state-machines-activerecord/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-state-machines-activerecord/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/integration_test.rb" 
"test/machine_by_default_test.rb" "test/machine_errors_test.rb" 
"test/machine_multiple_test.rb" "test/machine_nested_action_test.rb" 
"test/machine_unmigrated_test.rb" "test/machine_with_aliased_attribute_test.rb" 
"test/machine_with_callbacks_test.rb" 
"test/machine_with_column_state_attribute_test.rb" 
"test/machine_with_complex_pluralization_scopes_test.rb" 
"test/machine_with_conflicting_predicate_test.rb" 
"test/machine_with_conflicting_state_name_test.rb" 
"test/machine_with_custom_attribute_test.rb" 
"test/machine_with_default_scope_test.rb" 
"test/machine_with_different_column_default_test.rb" 
"test/machine_with_different_integer_column_default_test.rb" 
"test/machine_with_dirty_attribute_and_custom_attributes_during_loopback_test.rb"
 "test/machine_with_dirty_attribute_and_state_events_test.rb" 
"test/machine_with_dirty_attributes_and_custom_attribute_test.rb" 
"test/machine_with_dirty_attributes_during_loopback_test.rb" 
"test/machine_with_dirty_attributes_test.rb" 
"test/machine_with_dynamic_initial_state_test.rb" 
"test/machine_with_event_attributes_on_autosave_test.rb" 
"test/machine_with_event_attributes_on_custom_action_test.rb" 
"test/machine_with_event_attributes_on_save_bang_test.rb" 
"test/machine_with_event_attributes_on_save_test.rb" 
"test/machine_with_event_attributes_on_validation_test.rb" 
"test/machine_with_events_test.rb" "test/machine_with_failed_action_test.rb" 
"test/machine_with_failed_after_callbacks_test.rb" 
"test/machine_with_failed_before_callbacks_test.rb" 
"test/machine_with_initialized_state_test.rb" 
"test/machine_with_internationalization_test.rb" 
"test/machine_with_loopback_test.rb" 
"test/machine_with_non_column_state_attribute_defined_test.rb" 
"test/machine_with_same_column_default_test.rb" 
"test/machine_with_scopes_and_joins_test.rb" 
"test/machine_with_scopes_and_owner_subclass_test.rb" 
"test/machine_with_scopes_test.rb" 
"test/machine_with_state_driven_validations_test.rb" 
"test/machine_with_states_test.rb" 
"test/machine_with_static_initial_state_test.rb" 
"test/machine_with_transactions_test.rb" 
"test/machine_with_validations_and_custom_attribute_test.rb" 
"test/machine_with_validations_test.rb" "test/machine_without_database_test.rb" 
"test/machine_without_transactions_test.rb" "test/model_test.rb" -v
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/slice.rb:21: warning: 
method redefined; discarding old slice
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:8: warning: 
method redefined; discarding old transform_keys
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:19: warning: 
method redefined; discarding old transform_keys!
/usr/lib/ruby/vendor_ruby/state_machines/assertions.rb:14: warning: method 
redefined; discarding old assert_valid_keys
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:71: warning: 
previous definition of assert_valid_keys was here
/usr/lib/ruby/vendor_ruby/state_machines/state.rb:187: warning: assigned but 
unused variable - method
/usr/lib/ruby/vendor_ruby/arel/visitors/informix.rb:20: warning: assigned 

Bug#888131: ruby-oj: FTBFS on ruby2.5: too many arguments to function 'rb_struct_ptr'

[Chris West (Faux)]

Source: ruby-oj
Version: 2.17.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

current directory: /build/ruby-oj-2.17.4/ext/oj
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-oj-2.17.4/ext/oj'
...
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -DRUBY_TYPE=ruby -DRUBY_RUBY 
-DRUBY_VERSION=2.5.0 -DRUBY_VERSION_MAJOR=2 -DRUBY_VERSION_MINOR=5 
-DRUBY_VERSION_MICRO=0 -DHAS_RB_TIME_TIMESPEC=1 -DHAS_ENCODING_SUPPORT=1 
-DHAS_NANO_TIME=1 -DHAS_IVAR_HELPERS=1 -DHAS_EXCEPTION_MAGIC=1 
-DHAS_PROC_WITH_BLOCK=1 -DHAS_TOP_LEVEL_ST_H=0 -DNEEDS_RATIONAL=0 
-DIS_WINDOWS=0 -DUSE_PTHREAD_MUTEX=1 -DUSE_RB_MUTEX=0 -DDATETIME_1_8=0 
-DNO_TIME_ROUND_PAD=0 -DHAS_DATA_OBJECT_WRAP=1 -Wall -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o dump.o -c 
dump.c
dump.c: In function 'dump_struct_obj':
dump.c:1880:2: warning: 'rb_struct_ptr' is deprecated 
[-Wdeprecated-declarations]
  for (i = (int)RSTRUCT_LEN(obj), vp = RSTRUCT_CONST_PTR(obj); 0 < i; i--, 
vp++) {
  ^~~
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from oj.h:43,
 from dump.c:43:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
/usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h:129:52: note: in 
definition of macro 'NORETURN'
 #define NORETURN(x) __attribute__ ((__noreturn__)) x
^
/usr/include/ruby-2.5.0/ruby/backward.h:39:14: note: in expansion of macro 
'ERRORFUNC'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^
/usr/include/ruby-2.5.0/ruby/backward.h:39:58: note: in expansion of macro 
'DEPRECATED'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^~
/usr/include/ruby-2.5.0/ruby/backward.h:47:1: note: in expansion of macro 
'DECLARE_DEPRECATED_INTERNAL_FEATURE'
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
In file included from /usr/include/ruby-2.5.0/ruby.h:33:0,
 from oj.h:43,
from dump.c:43:








/usr/include/ruby-2.5.0/ruby/ruby.h:1189:33: error: too many arguments to 
function 'rb_struct_ptr'
 #define RSTRUCT_PTR(st) rb_struct_ptr(st)








^
dump.c:1878:47: note: in expansion of macro 'RSTRUCT_PTR'
 # define RSTRUCT_CONST_PTR(st) (const VALUE *)RSTRUCT_PTR(st)
   ^~~
dump.c:1880:39: note: in expansion of macro 'RSTRUCT_CONST_PTR'
  for (i = (int)RSTRUCT_LEN(obj), vp = RSTRUCT_CONST_PTR(obj); 0 < i; i--, 
vp++) {
   ^
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from oj.h:43,
 from dump.c:43:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
/usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h:129:52: note: in 
definition of macro 'NORETURN'
 #define NORETURN(x) __attribute__ ((__noreturn__)) x
^
/usr/include/ruby-2.5.0/ruby/backward.h:39:14: note: in expansion of macro 
'ERRORFUNC'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^
/usr/include/ruby-2.5.0/ruby/backward.h:39:58: note: in expansion of macro 
'DEPRECATED'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^~
/usr/include/ruby-2.5.0/ruby/backward.h:47:1: note: in expansion of macro 
'DECLARE_DEPRECATED_INTERNAL_FEATURE'
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
dump.c:1878:32: error: invalid use of void expression
 # define RSTRUCT_CONST_PTR(st) (const VALUE *)RSTRUCT_PTR(st)
^
dump.c:1880:39: note: in expansion of macro 'RSTRUCT_CONST_PTR'
  for (i = (int)RSTRUCT_LEN(obj), vp = RSTRUCT_CONST_PTR(obj); 0 < i; i--, 
vp++) {
   ^
Makefile:242: recipe for target 'dump.o' failed
make[1]: Leaving directory '/build/ruby-oj-2.17.4/ext/oj'
make[1]: *** [dump.o] Error 1

Bug#888129: ruby-json-spec: FTBFS on ruby2.5: Fixnum/Integer

[Chris West (Faux)]

Source: ruby-json-spec
Version: 1.1.2-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-json-spec-1.1.2/debian/ruby-json-spec/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-json-spec/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
WARNING: Using the 
`raise_error` matcher without providing a specific error or message risks false 
positives, since `raise_error` will match when Ruby raises a `NoMethodError`, 
`NameError` or `ArgumentError`, potentially allowing the expectation to pass 
without even executing the method you are intending to call. Actual error 
raised was #. Instead 
consider providing a specific error class or message. This message can be 
suppressed by setting: 
`RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 
Called from 
/build/ruby-json-spec-1.1.2/spec/json_spec/matchers/be_json_eql_spec.rb:102:in 
`block (2 levels) in '.
FWARNING: Using the `raise_error` 
matcher without providing a specific error or message risks false positives, 
since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` 
or `ArgumentError`, potentially allowing the expectation to pass without even 
executing the method you are intending to call. Actual error raised was 
#. Instead consider 
providing a specific error class or message. This message can be suppressed by 
setting: `RSpec::Expectations.configuration.on_potential_false_positives = 
:nothing`. Called from 
/build/ruby-json-spec-1.1.2/spec/json_spec/matchers/include_json_spec.rb:75:in 
`block (2 levels) in '.
..

Failures:

  1) JsonSpec::Matchers::HaveJsonType provides a failure message for negation
 Failure/Error: matcher.failure_message_when_negated.should   == "Expected 
JSON value type to not be Numeric, got Fixnum"

   expected: "Expected JSON value type to not be Numeric, got Fixnum"
got: "Expected JSON value type to not be Numeric, got Integer" 
(using ==)
 # ./spec/json_spec/matchers/have_json_type_spec.rb:59:in `block (2 levels) 
in '

Finished in 0.09429 seconds (files took 0.20874 seconds to load)
111 examples, 1 failure

Failed examples:

rspec ./spec/json_spec/matchers/have_json_type_spec.rb:56 # 
JsonSpec::Matchers::HaveJsonType provides a failure message for negation

/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/ruby-json-spec-1.1.2/debian/ruby-json-spec returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-json-spec.log

Please fix it!

Cheers,
Chris.

Bug#888130: ruby-net-http-persistent: FTBFS on ruby2.5: ssl verification fails

[Chris West (Faux)]

Source: ruby-net-http-persistent
Version: 2.9.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


105 runs, 355 assertions, 0 failures, 0 errors, 4 skips

You have skipped tests. Run with --verbose for details.
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-net-http-persistent/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:29:
 warning: Object#timeout is deprecated, use Timeout.timeout instead.
/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:
 warning: Object#timeout is deprecated, use Timeout.timeout instead.
Run options: --seed 44879

# Running:

E..DEPRECATED: Use 
assert_nil if expecting nil from 
/build/ruby-net-http-persistent-2.9.4/test/test_net_http_persistent.rb:816. 
This will fail in Minitest 6.
.S..SS..DEPRECATED: Use assert_nil if expecting nil 
from 
/build/ruby-net-http-persistent-2.9.4/test/test_net_http_persistent.rb:1116. 
This will fail in Minitest 6.
.S

Finished in 0.034938s, 3005.3406 runs/s, 10132.2911 assertions/s.

  1) Error:
TestNetHttpPersistentSSLReuse#test_ssl_connection_reuse:
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate 
verify failed (unspecified certificate verification error)

/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in
 `connect'

/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in
 `block in connect'
/usr/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
/usr/lib/ruby/2.5.0/timeout.rb:33:in `block in catch'
/usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
/usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
/usr/lib/ruby/2.5.0/timeout.rb:108:in `timeout'
/usr/lib/ruby/2.5.0/timeout.rb:122:in `timeout'

/build/ruby-net-http-persistent-2.9.4/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in
 `connect'
/usr/lib/ruby/2.5.0/net/http.rb:920:in `do_start'
/usr/lib/ruby/2.5.0/net/http.rb:915:in `start'

/build/ruby-net-http-persistent-2.9.4/test/test_net_http_persistent_ssl_reuse.rb:93:in
 `test_ssl_connection_reuse'
/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'

105 runs, 354 assertions, 0 failures, 1 errors, 4 skips

You have skipped tests. Run with --verbose for details.
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 

Bug#888127: ruby-grape-entity: FTBFS on ruby2.5: syntax error, unexpected '{'

[Chris West (Faux)]

Source: ruby-grape-entity
Version: 0.6.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-grape-entity-0.6.0/debian/ruby-grape-entity/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-grape-entity/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in `load': 
/build/ruby-grape-entity-0.6.0/spec/grape_entity/entity_spec.rb:30: syntax 
error, unexpected '{', expecting '}' (SyntaxError)
...e :name, format_with: proc {} {} }.to raise_error ArgumentEr...
...  ^
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-grape-entity-0.6.0/debian/ruby-grape-entity returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-grape-entity.log

Please fix it!

Cheers,
Chris.

Bug#888125: ruby-email-reply-parser: test relies on timing / speed

[Chris West (Faux)]

Source: ruby-email-reply-parser
Version: 0.5.8-2
Severity: wishlist

Dear Maintainer,

This package occasionally fails to build on build servers, as it
has tests which fail dependent on system load.

Please make it not do that.

(Note that this was run on an experimental ruby2.5 builder, which is not
currently anything like sid. Hopefully it doesn't change the outcome.)


Build log:

┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-email-reply-parser-0.5.8/debian/ruby-email-reply-parser/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-email-reply-parser/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Loaded suite -e
Started
..F
===
Failure:
  Took too long, upgrade to re2 gem.
   is not true.
test_pathological_emails(EmailReplyParserTest)
/build/ruby-email-reply-parser-0.5.8/test/email_reply_parser_test.rb:195:in 
`test_pathological_emails'
 192:   def test_pathological_emails
 193: t0 = Time.now
 194: reply = email("pathological")
  => 195: assert (Time.now - t0) < 1, "Took too long, upgrade to re2 gem."
 196:   end
 197: 
 198:   def test_doesnt_remove_signature_delimiter_in_mid_line
===


Finished in 8.758398299 seconds.
--
23 tests, 68 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
95.6522% passed
--
2.63 tests/s, 7.76 assertions/s


Cheers,
Chris.

Bug#888124: ruby-fakeweb: FTBFS on ruby2.5: undefined method `close' for #

[Chris West (Faux)]

Source: ruby-fakeweb
Version: 1.3.0+git20131202.48208f9+dfsg-3
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


188 runs, 359 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-fakeweb/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"fakeweb\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-fakeweb/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
Run options: --seed 13512

# Running:

..E.EE...EEEFFEEF.E.EE...EEE..F..EE..E.E..E...EE.EE...EF...FE...E.EFE.EF..EF....

Finished in 0.103453s, 1817.2499 runs/s, 2590.5477 assertions/s.

  1) Error:
TestFakeWebTrailingSlashes#test_registering_root_with_slash_and_request:
NoMethodError: undefined method `close' for 
#
Did you mean?  closed?
   clone
/usr/lib/ruby/2.5.0/net/http.rb:1014:in `do_finish'
/usr/lib/ruby/2.5.0/net/http.rb:912:in `start'
/usr/lib/ruby/2.5.0/net/http.rb:609:in `start'

/build/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/test/test_trailing_slashes.rb:23:in
 `test_registering_root_with_slash_and_request'
/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'

  2) Error:
TestFakeWebTrailingSlashes#test_registering_root_without_slash_and_request:
NoMethodError: undefined method `close' for 
#
Did you mean?  closed?
   clone
/usr/lib/ruby/2.5.0/net/http.rb:1014:in `do_finish'
/usr/lib/ruby/2.5.0/net/http.rb:912:in `start'
/usr/lib/ruby/2.5.0/net/http.rb:609:in `start'

/build/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/test/test_trailing_slashes.rb:12:in
 `test_registering_root_without_slash_and_request'

...

188 runs, 268 assertions, 9 failures, 54 errors, 0 skips
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-fakeweb-1.3.0\+git20131202.48208f9\+dfsg/debian/ruby-fakeweb 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-fakeweb.log

Please fix it!

Cheers,
Chris.

Bug#888123: ruby-crack: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime

[Chris West (Faux)]

Source: ruby-crack
Version: 0.4.3-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-crack-0.4.3/debian/ruby-crack/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-crack/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/hash_test.rb" 
"test/json_test.rb" "test/parser_test.rb" "test/string_test.rb" 
"test/xml_test.rb" 
/build/ruby-crack-0.4.3/test/hash_test.rb:10: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/build/ruby-crack-0.4.3/test/hash_test.rb:11: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/build/ruby-crack-0.4.3/test/hash_test.rb:12: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/build/ruby-crack-0.4.3/test/hash_test.rb:22: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/build/ruby-crack-0.4.3/test/hash_test.rb:23: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/build/ruby-crack-0.4.3/test/hash_test.rb:24: warning: ambiguous first 
argument; put parentheses or a space even after `/' operator
/usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:22:in `': 
uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)
Did you mean?  SafeYAML::Parse::Date::DATE_MATCHER
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:3:in 
`'
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:2:in 
`'
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/safe_yaml/load.rb:14:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-crack-0.4.3/lib/crack/json.rb:6:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-crack-0.4.3/lib/crack.rb:6:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-crack-0.4.3/test/test_helper.rb:3:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-crack-0.4.3/test/hash_test.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/hash_test.rb" 
"test/json_test.rb" "test/parser_test.rb" "test/string_test.rb" 
"test/xml_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-crack-0.4.3/debian/ruby-crack 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-crack.log

Please fix it!

Cheers,
Chris.

Bug#888121: ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as'

[Chris West (Faux)]

Source: ruby-delayed-job-active-record
Version: 4.0.3-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

...

Finished in 1.56 seconds (files took 2.53 seconds to load)
88 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"delayed_job_active_record\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-delayed-job-active-record-4.0.3/debian/ruby-delayed-job-active-record/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant ::Fixnum 
is deprecated
/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant ::Fixnum 
is deprecated
/usr/lib/ruby/vendor_ruby/active_record/dynamic_matchers.rb:26:in 
`method_missing': undefined method `yaml_as' for ActiveRecord::Base:Class 
(NoMethodError)
Did you mean?  yaml_tag
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:4:in 
`'
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:3:in 
`'
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:2:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
`block in require'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:240:in 
`load_dependency'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
`require'
from /usr/lib/ruby/vendor_ruby/delayed/worker.rb:64:in `backend='
from 
/build/ruby-delayed-job-active-record-4.0.3/lib/delayed_job_active_record.rb:5:in
 `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-delayed-job-active-record-4.0.3/spec/helper.rb:8:in 
`'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from 
/build/ruby-delayed-job-active-record-4.0.3/spec/delayed/backend/active_record_spec.rb:1:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-delayed-job-active-record-4.0.3/debian/ruby-delayed-job-active-record
 returned exit code 1
debian/rules:10: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-delayed-job-active-record.log

Please fix it!

Cheers,
Chris.

Bug#888120: ruby-dalli: FTBFS on ruby2.5: "File does not exist:"

[Chris West (Faux)]

Source: ruby-dalli
Version: 2.7.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

I have no idea what's going on here, maybe a gem2deb problem causing it
to not be happy building twice in a row?

Build log excerpt:

...

Finished in 13.066640s, 0.0765 runs/s, 0.0765 assertions/s.

1 runs, 1 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"dalli\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-dalli-2.7.4/debian/ruby-dalli/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" -v
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized 
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of 
WANT_RAILS_VERSION was here
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized 
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of 
WANT_RAILS_VERSION was here
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized 
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of 
WANT_RAILS_VERSION was here

File does not exist: 

rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-dalli-2.7.4/debian/ruby-dalli 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-dalli.log


Please fix it!

Cheers,
Chris.

Bug#888118: homesick: FTBFS on ruby2.5: test fail: got: ("GEM_SKIP")

[Chris West (Faux)]

Source: homesick
Version: 1.1.6-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/homesick-1.1.6/debian/homesick/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/homesick/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*_spec.rb
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's default settings.
FF...

Failures:

  1) Homesick::CLI open returns an error message when the $EDITOR environment 
variable is not set
 Failure/Error: after { home.destroy! }

   {"DEB_HOST_GNU[...]4", "LC_MESSAGES"=>"C"} received :[] with unexpected 
arguments
 expected: ("EDITOR")
  got: ("GEM_SKIP")
Please stub a default value first if message might be received with 
other args as well. 
 # ./spec/homesick_cli_spec.rb:8:in `block (2 levels) in '

  2) Homesick::CLI open returns an error message when the given castle does not 
exist
 Failure/Error: after { home.destroy! }

...

Finished in 2.97 seconds (files took 1.45 seconds to load)
73 examples, 2 failures

Failed examples:

rspec ./spec/homesick_cli_spec.rb:743 # Homesick::CLI open returns an error 
message when the $EDITOR environment variable is not set
rspec ./spec/homesick_cli_spec.rb:751 # Homesick::CLI open returns an error 
message when the given castle does not exist

/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/homesick-1.1.6/debian/homesick 
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/homesick.log

Bug#888117: ruby-beautify: FTBFS on ruby2.5: tests fail: .. got: "EXPR_BEG

[Chris West (Faux)]

Source: ruby-beautify
Version: 0.97.4-3
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log:

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-beautify-0.97.4/debian/ruby-beautify/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-beautify/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation

Ruby Beautify
  will work
  will do multiple files
  will update files (overwrite) in place
  will honor --spaces
  will honor the ident_count prefix
  will use a .ruby-beautify config file

Ruby Beautify Library
  #pretty_string
will indent by tab ( by default ) (FAILED - 1)
will indent by space (FAILED - 2)
will honor indent count (FAILED - 3)

Usage Scenarios
  will test: mutli_level (FAILED - 4)
  will test: case (FAILED - 5)
  will test: from_control (FAILED - 6)
  will test: or_equals (FAILED - 7)
  will test: lambda_literal (FAILED - 8)
  will test: pre_indented (FAILED - 9)
  will test: multiline_strings (FAILED - 10)
  will test: monolithic_example (FAILED - 11)

Failures:

  1) Ruby Beautify Library #pretty_string will indent by tab ( by default )
 Failure/Error: expect(RubyBeautify.pretty_string(@ugly_string)).to eq 
@pretty_string

   expected: "# Test for already indented blocks\nclass There2 < 
There\n\tdef m1()\n\t\tputs \"m1\"\n\tend\n\tdef m2()\n\t\tputs 
\"m2\"\n\tend\n\tdef m3()\n\t\tputs \"m3\"\n\tend\nend\n"
got: 
"EXPR_BEGEXPR_BEGEXPR_CLASSEXPR_CLASSEXPR_ARGEXPR_ARGEXPR_BEGEXPR_BEGEXPR_CMDARGEXPR_BEG\tEXPR_BEGEXP...XPR_CMDARGEXPR_CMDARGEXPR_END|EXPR_ENDARGEXPR_BEG\tEXPR_BEGEXPR_ENDEXPR_BEGEXPR_BEGEXPR_ENDEXPR_BEG"

   (compared using ==)

   Diff:
   @@ -1,13 +1,2 @@
   -# Test for already indented blocks
   -class There2 < There
   -def m1()
   -puts "m1"
   -end
   -def m2()
   -puts "m2"
   -end
   -def m3()
   -puts "m3"
   -end
   -end
   
+EXPR_BEGEXPR_BEGEXPR_CLASSEXPR_CLASSEXPR_ARGEXPR_ARGEXPR_BEGEXPR_BEGEXPR_CMDARGEXPR_BEG
 EXPR_BEGEXPR_FNAMEEXPR_FNAMEEXPR_ENDFNEXPR_BEG|EXPR_LABELEXPR_ENDFNEXPR_BEG
 
EXPR_BEGEXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_END|EXPR_ENDARGEXPR_BEG
EXPR_BEGEXPR_ENDEXPR_BEG
EXPR_FNAMEEXPR_FNAMEEXPR_ENDFNEXPR_BEG|EXPR_LABELEXPR_ENDFNEXPR_BEG 
EXPR_BEGEXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_END|EXPR_ENDARGEXPR_BEG
EXPR_BEGEXPR_ENDEXPR_BEG
EXPR_BEGEXPR_FNAMEEXPR_FNAMEEXPR_ENDFNEXPR_BEG|EXPR_LABELEXPR_ENDFNEXPR_BEG 

EXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_CMDARGEXPR_END|EXPR_ENDARGEXPR_BEG
EXPR_BEGEXPR_ENDEXPR_BEGEXPR_BEGEXPR_ENDEXPR_BEG
 # ./spec/lib/ruby-beautify_spec.rb:15:in `block (3 levels) in '

  2) Ruby Beautify Library #pretty_string will indent by space
 Failure/Error: expect(RubyBeautify.pretty_string(@ugly_string, 
indent_token:' ')).to eq @pretty_string_space

   expected: "# Test for already indented blocks\nclass There2 < There\n 
def m1()\n  puts \"m1\"\n end\n def m2()\n  puts \"m2\"\n end\n def m3()\n  
puts \"m3\"\n end\nend\n"
got: 
"EXPR_BEGEXPR_BEGEXPR_CLASSEXPR_CLASSEXPR_ARGEXPR_ARGEXPR_BEGEXPR_BEGEXPR_CMDARGEXPR_BEG
 EXPR_BEGEXPR...EXPR_CMDARGEXPR_CMDARGEXPR_END|EXPR_ENDARGEXPR_BEG 
EXPR_BEGEXPR_ENDEXPR_BEGEXPR_BEGEXPR_ENDEXPR_BEG"

...

ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-beautify-0.97.4/debian/ruby-beautify returned exit code 1
debian/rules:15: recipe for target 'override_dh_auto_install' failed

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-beautify.log

Cheers,
Chris.

Bug#887031: openvswitch-ipsec: Please drop this deprecated binary

[Chris West]

Source: openvswitch
Version: 2.8.1+dfsg1-4
Priority: normal

Hi,

Please consider dropping the openvswitch-ipsec binary package from
openvswitch.

It's marked as deprecated in the description. It depends on ipsec-tools,
which doesn't look like it's going to make Buster, e.g. #858930. I've
talked with the maintainer (CC'd) and upstream appears to be dead.

(openvswitch would have been autoremoved from testing already, due to
this RC bug in ipsec-tools, but there's a problem(tm) with autoremovals
which is causing the removal to fail. This would remove neutron and many
other OpenStack packages.)

Cheers,
Chris.

Bug#859543: Fix build with openssl-1.1

[Chris West]

Control: tags -1 + patch

The attached patch disables the faulty detection of MD2, causing the
build to proceed to completion. MD2 authentication will be disabled, as
I understand it, but this is probably okay?

MD2 is supported by openssl-1.1, but it has been disabled at configure
time in Debian, as is the default.
MD2 is a very old, very broken hash algorithm (even worse than MD5).

Cheers,
Chris.

>From 4bf11095b29a8f9490b0e093c8fb2659dcea8894 Mon Sep 17 00:00:00 2001
From: "Chris West (Faux)" <g...@goeswhere.com>
Date: Wed, 10 Jan 2018 13:25:45 +
Subject: [PATCH] eliminate faulty check for md2

---
 openhpi-3.6.1/configure.ac   | 2 +-
 openhpi-3.6.1/debian/control | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/openhpi-3.6.1/configure.ac b/openhpi-3.6.1/configure.ac
index 02b5786..cb9bc01 100644
--- a/openhpi-3.6.1/configure.ac
+++ b/openhpi-3.6.1/configure.ac
@@ -179,7 +179,7 @@ AC_CHECK_LIB([crypto],[MD5_Init],[CRYPTO_LIB=-lcrypto],[CRYPTO_LIB=])
 AC_SUBST(CRYPTO_LIB)
 AC_CHECK_LIB([ssl],[SSL_library_init],[SSL_LIB=-lssl],[SSL_LIB=])
 AC_SUBST(SSL_LIB)
-AC_CHECK_HEADERS([openssl/md2.h openssl/md5.h openssl/bio.h openssl/ssl.h openssl/err.h],[have_openssl=yes],[have_openssl=no])
+AC_CHECK_HEADERS([openssl/md5.h openssl/bio.h openssl/ssl.h openssl/err.h],[have_openssl=yes],[have_openssl=no])
 
 dnl xml is used for XML-based communication in ilo2_ribcl and oa_soap
 AC_CHECK_LIB([xml2],[xmlParseMemory],[XML2_LIB=-lxml2],[XML2_LIB=])
diff --git a/openhpi-3.6.1/debian/control b/openhpi-3.6.1/debian/control
index 57402a8..fde4ce2 100644
--- a/openhpi-3.6.1/debian/control
+++ b/openhpi-3.6.1/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Mohan Devarajulu <mohan.devaraj...@hpe.com>
 Uploaders: Khalid Aziz <kha...@debian.org>
 Homepage: http://openhpi.org
-Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), autotools-dev, autoconf (>= 2.57), dh-autoreconf, automake(>= 1.9), uuid-dev, libglib2.0-dev (>= 2.2), pkg-config, libltdl-dev, openipmi (>= 2.0.7), libopenipmi-dev (>=2.0.7), libsnmp-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), libsysfs-dev (>= 0.3), libncurses5-dev, libxml2-dev
+Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), autotools-dev, autoconf (>= 2.57), dh-autoreconf, automake(>= 1.9), uuid-dev, libglib2.0-dev (>= 2.2), pkg-config, libltdl-dev, openipmi (>= 2.0.7), libopenipmi-dev (>=2.0.7), libsnmp-dev, libssl-dev, libsysfs-dev (>= 0.3), libncurses5-dev, libxml2-dev
 Standards-Version: 4.0.0
 
 Package: libopenhpi3
-- 
2.15.1

Bug#828451: Patches

[Chris West]

Control: tags -1 + patch

I've sent upstream some patches:
 * https://github.com/netty/netty-tcnative/pull/325
 * https://github.com/netty/netty/pull/7544

There hasn't been any objections, beyond an unwillingness to remove the
feature. I am pretty sure we can live with having removed the feature,
so could apply the patches regardless of upstream's decision.

The patches turned out to be very small, and will usefully conflict with
any upstream changes, e.g. if they decide to properly fix renegotiation.

Chris.

Bug#867749: I will adopt this package

[Chris West]

Control: retitle -1 ITA: keychain -- key manager for OpenSSH

I intend to adopt this package. I'm a DM and have uploaded previously,
but don't have permission to upload this package. I also don't have
access to push to the original collab-maint repo, so I've temporarily
mirrored it:
https://github.com/FauxFaux/keychain-deb

Chris.

Bug#884536: Consider dropping jython build-dep?

[Chris West]

Source: batik
Version: 1.9-3
Priority: wishlist


batik pulls jython, and a whole load of related libraries, into the
"key packages" set[1], which complicates transitions[2].

Please consider not building the Jython bindings, to drop this
dependency.

Upstream supports this, and the installed libbatik-java only suggests
jython, as the bindings are entirely optional.

The jython bindings don't seem to be used by any of the rdeps, but I
didn't check very hard. Jython is generally not very widely used at all
in Debian, which makes it reasonably easy to say this.

As with most Java libraries, I expect any real users, if there are any,
will be pulling the JARs from maven central, so won't care what we have
built.


Cheers,
Chris.

 1: https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
 2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828451#48

Bug#785274: Helper script

[Chris West]

I had a go at rebasing the above pull request, but gbp's test suite
won't behave on my machine, and I'm not motivated enough to fight it
(I'm pretty furious right now), so only one of the recommendations in
the original pull request is applied:
https://github.com/FauxFaux/git-buildpackage/commits/pq_import_dep3


Instead, I wrote a script that changes existing DEP3 headers into
something gbp won't mangle so badly. I hope this is useful for someone.

https://github.com/FauxFaux/rc/blob/563f84375084fbe738746e6819f7bceba4ca78b8/gbp-prepare.py
https://paste.debian.net/1000447/

Chris.

Bug#884187: ant: please ask javadoc to ignore source errors on Java9+

[Chris West]

Package: ant
Version: 1.9.9-5
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

ant is upgrading the -source and -target options passed to javac and
javadoc such that they are a minimum of 1.6, to fix projects compiling
with Java 9.

However, javadoc in Java 9 has become more picky, and requires there to
be no source errors (including the classpath being correct), by default.

There is a (hidden) option in Java 9 (and currently in 10) to disable
this behaviour and revert to the Java 8 behaviour of just warning:
--ignore-source-errors.

Please make ant apply this option during a Debian build.

Chris.

Bug#883468: debian-edu-config: Please migrate to cfengine3

[Chris West]

Package: debian-edu-config
Version: 1.940
Severity: wishlist

Please migrate debian-edu-config and education-common away from
cfengine2, perhaps to cfengine3 or another system.

debian-edu-config and education-common are the only packages holding
cfengine2 in Debian[1]. cfengine2 currently doesn't look like it's going
to survive the openssl1.0-rm transition[2], as I find it unlikely that
anyone is going to successfully patch it. I did the cfengine3 port, with
lots of help from upstream[3], who abandoned cfengine2 many (*many*)
years ago. CC: Antonio is the cfengine2 maintainer and may disagree with
me.


Cheers,
Chris.

 1: https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
 2: https://release.debian.org/transitions/html/openssl1.0-rm.html
 3: https://github.com/cfengine/core/pull/2916#issuecomment-333993086

Bug#828245: balsa: FTBFS for me, and the buildds

[Chris West]

Control: severity -1 serious
Control: retitle -1 balsa: FTBFS with openssl 1.1.0

This is failing to build for me still on sid (with libssl-dev):

auth-cram.c: In function ‘hmac_md5’:
auth-cram.c:134:14: error: storage size of ‘ctx’ isn’t known
   EVP_MD_CTX ctx;
  ^~~
Makefile:515: recipe for target 'auth-cram.o' failed

And on the buildds for the transition:
https://release.debian.org/transitions/html/openssl1.0-rm.html

This is a typical error for this openssl version migration:
the structs have become opaque and you must use pointers everywhere.

Going back to "serious" because that's what the other transition
bugs are today, but they were raised with much more notice; maybe
more time can be taken to fix this.

Chris.

Bug#883450: omniorb-dfsg: FTBFS with openssl-1.1

[Chris West]

Source: omniorb-dfsg
Version: 4.1.6-2.2
Severity: serious
Justification: blocks ongoing transition?
Control: block 827061 by -1

omniorb-dfsg build-depends on openssl 1.0, which is to be removed.
With openssl-1.1, omniorb-dfsg fails to build from source. This is
blocking the removal of openssl-1.0.

There was a big round of bug raising for this before, I don't know
how this package has slipped through the gaps. I've raised this as
serious as all the other bugs in this category are, but maybe more
time should be given.


Build log:

g++ -c -O2 -Wall [..] ./../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc: In member function 
‘virtual void sslContext::set_DH()’:
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc:380:5: error: 
invalid use of incomplete type ‘DH {aka struct dh_st}’
   dh->p = BN_bin2bn(dh512_p, sizeof(dh512_p), 0);
 ^~
In file included from /usr/include/openssl/crypto.h:31:0,
 from /usr/include/openssl/comp.h:16,
 from /usr/include/openssl/ssl.h:47,
 from ../../../../../../include/omniORB4/sslContext.h:86,
 from 
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc:104:
/usr/include/openssl/ossl_typ.h:104:16: note: forward declaration of ‘DH {aka 
struct dh_st}’
 typedef struct dh_st DH;
^

This is classic "using the old openssl API with direct access to
structs, instead of using getters".

Chris.

Bug#844939: Yup, fixed.

[Chris West]

Control: tags -1 + fixed-upstream

Mark has kindly fixed the bug upstream, and the package now builds
correctly (after adding locales-all). My repo[1] now builds successfully
inside gbp with pbuilder.

I've also bumped the standards version, as I believe it only requires a
trivial change.

1: https://github.com/FauxFaux/git-remote-hg

Bug#844939: update attempt

[Chris West]

I had a stab at updating the packaging Marks' fork[1], but the tests
still fail. Firstly, they're missing locales-all, which is easy to fix.
The second bug[2] I've raised against the github repo, as it doesn't
look Debian specific.

 [1]: https://github.com/FauxFaux/git-remote-hg
 [2]: https://github.com/mnauw/git-remote-hg/issues/11

Chris.

Bug#851076: patch

[Chris West]

Control: tags -1 + patch

The attached patch fixes the build of the current gvpe in unstable,
which is different to the version that the bug was originally reported
against; the compile errors are different, more like:

conf.C: In constructor 
‘configuration_parser::configuration_parser(configuration&, bool, int, char**)’:
conf.C:653:37: error: invalid use of incomplete type ‘RSA {aka struct rsa_st}’
 if (BN_cmp (conf.rsa_key->n, conf.thisnode->rsa_key->n) != 0
 ^~

>From 57c6de81da714b76d3a8e3b0ffca1db026f961ab Mon Sep 17 00:00:00 2001
From: "Chris West (Faux)" <g...@goeswhere.com>
Date: Wed, 22 Nov 2017 12:12:37 +
Subject: [PATCH] use RSA getters for libssl 1.1 compat

---
 gvpe-3.0/debian/control |  2 +-
 gvpe-3.0/src/conf.C | 16 ++--
 2 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/gvpe-3.0/debian/control b/gvpe-3.0/debian/control
index a3f61df..4073fdf 100644
--- a/gvpe-3.0/debian/control
+++ b/gvpe-3.0/debian/control
@@ -3,7 +3,7 @@ Section: net
 Priority: extra
 Maintainer: TANIGUCHI Takaki <tak...@debian.org>
 Build-Depends: debhelper (>= 9), autotools-dev,
-	libssl1.0-dev | libssl-dev (<< 1.1.0~),
+	libssl-dev,
 	dh-autoreconf,
 	info, zlib1g-dev, texinfo
 Standards-Version: 3.9.8
diff --git a/gvpe-3.0/src/conf.C b/gvpe-3.0/src/conf.C
index 51eaab6..da06312 100644
--- a/gvpe-3.0/src/conf.C
+++ b/gvpe-3.0/src/conf.C
@@ -650,12 +650,16 @@ configuration_parser::configuration_parser (configuration ,
 }
 
   if (conf.rsa_key && conf.thisnode->rsa_key)
-if (BN_cmp (conf.rsa_key->n, conf.thisnode->rsa_key->n) != 0
-|| BN_cmp (conf.rsa_key->e, conf.thisnode->rsa_key->e) != 0)
-  {
-slog (L_NOTICE, _("private hostkey and public node key mismatch: is '%s' the correct node?"), ::thisnode);
-exit (EXIT_FAILURE);
-  }
+{
+  const BIGNUM *conf_n, *conf_e, *thisnode_n, *thisnode_e;
+  RSA_get0_key(conf.rsa_key, _n, _e, NULL);
+  RSA_get0_key(conf.thisnode->rsa_key, _n, _e, NULL);
+  if (BN_cmp (conf_n, thisnode_n) != 0 || BN_cmp (conf_e, thisnode_e) != 0)
+{
+  slog (L_NOTICE, _("private hostkey and public node key mismatch: is '%s' the correct node?"), ::thisnode);
+  exit (EXIT_FAILURE);
+}
+}
 }
 }
 
-- 
2.15.0

Bug#880676: RFP: coredns -- pluggable DNS server in Go

[Chris West]

Package: wnpp
Severity: wishlist

* Package name : coredns
  Version  : 0.9.9
  Upstream Author  : Miek Gieben 
* URL  : https://github.com/coredns/coredns
* License  : Apache 2.0
  Programming Lang : Go
  Description  : pluggable DNS server in Go

Upstream description:

CoreDNS aims to be a fast and flexible DNS server. The keyword here is
flexible: with CoreDNS you are able to do what you want with your DNS
data. And if not: write a plugin!

Motivation:

coredns is approaching 1.0, and upstream care about .deb/.rpm packages.

coredns supports interesting client configurations, including
dns-over-tls and dns-over-json/https (to Google), as well as supporting
server usecases.


Cheers,
Chris.

Bug#873993: [Packaging] Bug#873993: FTBFS with Java 9 due to -source/-target only

[Chris West]

On Tue, Oct 03, 2017 at 10:45:34PM +, Holger Levsen wrote:
> upstream's Makefile.config has this line, which I think is to blame here:
> 
> Makefile.config:JFLAGS := -g -source 1.5 -target 1.5 -Xlint
> 
> Shall I ask upstream to drop these options entirely, or does one need to
> specify them?

Dropping them will cause the build to run against "whatever is the
latest", which may work; the tool only checked that 1.6 would work.
The wiki has some text: https://wiki.debian.org/Java/Java9Pitfalls


> Will Java 9 will be the default for Buster?

We're hoping so, yes. Ubuntu are also planning to transition for 18.04.

--
Chris.

Bug#858436: patch

[Chris West]

Control: tags -1 + patch

Attached is a patch which fixes the two minor API usage issues, and
allows the package to build.

diff --git a/eiskaltdcpp-2.2.9/dcpp/CryptoManager.cpp b/eiskaltdcpp-2.2.9/dcpp/CryptoManager.cpp
index 08893a7..fd381a5 100644
--- a/eiskaltdcpp-2.2.9/dcpp/CryptoManager.cpp
+++ b/eiskaltdcpp-2.2.9/dcpp/CryptoManager.cpp
@@ -109,10 +109,12 @@ CryptoManager::CryptoManager()
 };
 
 if(dh) {
-dh->p = BN_bin2bn(dh4096_p, sizeof(dh4096_p), 0);
-dh->g = BN_bin2bn(dh4096_g, sizeof(dh4096_g), 0);
+BIGNUM *p = BN_bin2bn(dh4096_p, sizeof(dh4096_p), 0);
+BIGNUM *g = BN_bin2bn(dh4096_g, sizeof(dh4096_g), 0);
 
-if(!dh->p || !dh->g) {
+DH_set0_pqg(dh, p, NULL, g);
+
+if(!p || !g) {
 dh.reset();
 } else {
 SSL_CTX_set_options(serverContext, SSL_OP_SINGLE_DH_USE);
diff --git a/eiskaltdcpp-2.2.9/dcpp/SSLSocket.cpp b/eiskaltdcpp-2.2.9/dcpp/SSLSocket.cpp
index 54db316..5705029 100644
--- a/eiskaltdcpp-2.2.9/dcpp/SSLSocket.cpp
+++ b/eiskaltdcpp-2.2.9/dcpp/SSLSocket.cpp
@@ -54,9 +54,9 @@ bool SSLSocket::waitConnected(uint32_t millis) {
 }
 
 while(true) {
-int ret = ssl->server?SSL_accept(ssl):SSL_connect(ssl);
+int ret = SSL_is_server(ssl)?SSL_accept(ssl):SSL_connect(ssl);
 if(ret == 1) {
-dcdebug("Connected to SSL server using %s as %s\n", SSL_get_cipher(ssl), ssl->server?"server":"client");
+dcdebug("Connected to SSL server using %s as %s\n", SSL_get_cipher(ssl), SSL_is_server(ssl)?"server":"client");
 return true;
 }
 if(!waitWant(ret, millis)) {
diff --git a/eiskaltdcpp-2.2.9/debian/control b/eiskaltdcpp-2.2.9/debian/control
index a4f06c3..9679bce 100644
--- a/eiskaltdcpp-2.2.9/debian/control
+++ b/eiskaltdcpp-2.2.9/debian/control
@@ -19,7 +19,7 @@ Build-Depends: chrpath,
libnotify-dev,
libpcre3-dev,
libqt4-dev,
-   libssl1.0-dev,
+   libssl-dev,
pkg-config,
po-debconf,
qt4-dev-tools,

Bug#876434: [new check] detect outdated use of dpkg-parsechangelog | grep

[Chris West]

Package: lintian
Version: 2.5.53
Priority: wishlist

Dear maintainer,

Many packages contain invocations such as:

DEB_VERSION=$(shell dpkg-changelog | grep '^Version' | cut ...)

https://codesearch.debian.net/search?q=path%3Adebian%2Frules+shell+dpkg-parsechangelog

Since dpkg 1.17 (available in "oldstable" as of today), this can better
be written as:

DEB_VERSION=$(shell dpkg-parsechangelog -SVersion)

Or:
include /usr/share/dpkg/pkg-info.mk; $(DEB_VERSION)


Please inform people that they should prefer the new syntax.

Cheers,
Chris.

Bug#875789: FTBFS with Java 9: tests error out

[Chris West]

Source: rdp-classifier
Version: 2.10.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

All of the tests in one class exception out. Nothing looks especially
suspicious in the class, but I didn't bother to extract the proper logs,
sorry!

https://sources.debian.net/src/rdp-classifier/2.10.2-1/test/edu/msu/cme/rdp/classifier/rrnaclassifier/TrainingInfoTest.java/

Build log:

[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.273 sec
[junit] Running edu.msu.cme.rdp.classifier.rrnaclassifier.TrainingInfoTest
[junit] testCreateTree
[junit] testCreateGenusWordConditionalProbList
[junit] testCreateLogWordPriorArr
[junit] testCreateProbIndexArr
[junit] testCreateClassifier
[junit] Tests run: 5, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 
0.33 sec

BUILD FAILED
/build/rdp-classifier-2.10.2/tmp-junit.xml:11: Test 
edu.msu.cme.rdp.classifier.rrnaclassifier.TrainingInfoTest failed

Total time: 7 seconds
debian/rules:23: recipe for target 'override_dh_auto_test' failed


Cheers,
Chris.

Bug#875790: FTBFS with Java 9: configure fails to detect Java

[Chris West]

Source: scilab
Version: 5.5.2-5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The "/jre" part of the install path is gone. Also, many of the libraries
have moved. I'm not sure why configure cares so much about the actual
locations.

Build log:

checking type of jvm... jdk
checking java API version... 1.8
Using the following JNI include flags 
-I/usr/lib/jvm/java-9-openjdk-amd64/include 
-I/usr/lib/jvm/java-9-openjdk-amd64/include/linux
checking if jni.h can be included... yes
Looking for JNI libs with x86_64 as machine hardware name
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/x86_64/libjava.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/amd64/libjava.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/i386/client/libjvm.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/bin/classic/libjvm.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/lib/jvm.lib
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/mipsel/libjava.so
configure: error: Could not detect the location of the Java
shared library. You will need to update java.m4
to add support for this JVM configuration.
make: *** [debian/stamp-autotools] Error 1
/usr/share/cdbs/1/class/autotools.mk:44: recipe for target 
'debian/stamp-autotools' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2




Cheers,
Chris.

Bug#875779: FTBFS with Java 9: boot classpath guess is wrong

[Chris West]

Source: pixelmed-codec
Version: 20141206
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

It looks like the package is trying to set a boot classpath. This is
generally not a good idea for a Debian build, and the technique that's
being used is incorrect here:

https://sources.debian.net/src/pixelmed-codec/20141206-2/debian/patches/set_java_home.patch/

This causes failures like "unable to find java.lang", such as in the build log:

Build log:

make[2]: Entering directory 
'/build/pixelmed-codec-20141206/com/pixelmed/codec/jpeg'
Makefile:21: warning: overriding recipe for target 'clean'
../../../../Makefile.common.mk:25: warning: ignoring old recipe for target 
'clean'
export JAVAVERSIONTARGETJARFILE=/usr/lib/jvm/default-java/jre/lib/rt.jar; javac 
-O -target 1.7 -source 1.7 -bootclasspath ${JAVAVERSIONTARGETJARFILE} -encoding 
"UTF8" -Xlint:deprecation \
-classpath ../../../.. \
-sourcepath ../../../.. EntropyCodedSegment.java
Fatal Error: Unable to find package java.lang in classpath or bootclasspath
../../../../Makefile.common.mk:20: recipe for target 
'EntropyCodedSegment.class' failed
make[2]: *** [EntropyCodedSegment.class] Error 3
make[2]: Leaving directory 
'/build/pixelmed-codec-20141206/com/pixelmed/codec/jpeg'
Makefile:60: recipe for target 'pixelmed_codec.jar' failed
make[1]: Leaving directory '/build/pixelmed-codec-20141206'


Cheers,
Chris.

Bug#875778: FTBFS with Java 9: path shenanigans confuse ant?

[Chris West]

Source: pegasus-wms
Version: 4.4.0+dfsg-6
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

On my builder, this fails as follows. I suspect it's due to this weird
fiddling with the path, which is invalid:
https://sources.debian.net/src/pegasus-wms/4.4.0%2Bdfsg-6/debian/rules/#L10

JAVA_HOME := $(firstword $(wildcard 
/usr/lib/jvm/java-7-openjdk-$(DEB_HOST_ARCH)))
PATH := ${JAVA_HOME}/bin:${PATH}

However, it works on Java 8, on Reproducible Builds jenkins, so it's
apparently not totally crazy.

(I realise that this package is orphaned.)

Build log:

dpkg-buildpackage: info: source package pegasus-wms
dpkg-buildpackage: info: source version 4.4.0+dfsg-6
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Adam Borowski 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build pegasus-wms-4.4.0+dfsg
dpkg-source: info: using options from 
pegasus-wms-4.4.0+dfsg/debian/source/options: 
--extend-diff-ignore=(Version.java|\.jar|doc/docbook/.*|doc/manpages/.*|share/man/man1/.*|\.pdf)$
 debian/rules clean
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp
ant clean
/bin/ant: 1: cd: can't cd to /bin/../share/ant/bin/..
Error: Could not find or load main class org.apache.tools.ant.launch.Launcher
Caused by: java.lang.ClassNotFoundException: 
org.apache.tools.ant.launch.Launcher
debian/rules:149: recipe for target 'clean' failed
make: *** [clean] Error 1
dpkg-buildpackage: error: debian/rules clean gave error exit status 2


Cheers,
Chris.

Bug#875776: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: openid4java
Version: 0.9.6.662
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javadoc now requires the same classpath as the release build.

Build log:

apidoc:
[mkdir] Created dir: /build/openid4java-0.9.6.662/apidoc
  [javadoc] Generating Javadoc
  [javadoc] Javadoc execution
  [javadoc] Loading source files for package org.openid4java...
  [javadoc] Loading source files for package org.openid4java.association...
  [javadoc] Loading source files for package org.openid4java.consumer...
  [javadoc] Loading source files for package org.openid4java.discovery...
  [javadoc] Loading source files for package org.openid4java.discovery.html...
  [javadoc] Loading source files for package org.openid4java.discovery.xrds...
  [javadoc] Loading source files for package org.openid4java.discovery.xri...
  [javadoc] Loading source files for package org.openid4java.discovery.yadis...
  [javadoc] Loading source files for package org.openid4java.infocard...
  [javadoc] Loading source files for package org.openid4java.infocard.rp...
  [javadoc] Loading source files for package org.openid4java.infocard.sts...
  [javadoc] Loading source files for package org.openid4java.message...
  [javadoc] Loading source files for package org.openid4java.message.ax...
  [javadoc] Loading source files for package org.openid4java.message.pape...
  [javadoc] Loading source files for package org.openid4java.message.sreg...
  [javadoc] Loading source files for package org.openid4java.server...
  [javadoc] Loading source files for package org.openid4java.util...
  [javadoc] Constructing Javadoc information...
  [javadoc] 
/build/openid4java-0.9.6.662/src/org/openid4java/discovery/xri/LocalXriResolver.java:15:
 error: package org.openxri does not exist
  [javadoc] import org.openxri.XRI;
  [javadoc]   ^
  [javadoc] 
/build/openid4java-0.9.6.662/src/org/openid4java/discovery/xri/LocalXriResolver.java:16:
 error: package org.openxri.resolve does not exist
  [javadoc] import org.openxri.resolve.Resolver;
  [javadoc]   ^




Cheers,
Chris.

Bug#875775: FTBFS with Java 9: javadoc -source 9

[Chris West]

Source: mvel
Version: 2.3.1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The javadoc build seems to be trying to use -source 9, even though the
rest of the build uses -source 1.6. As the code uses _ as an identifier,
it's necessary to run the javadoc build with a -source of 1.8 or below.

The presence of the _ is probably a problem, for which I raised upstream issue:
https://github.com/mvel/mvel/issues/132

(Also, the homepage URL in the package is wrong; it's moved to github.)


Build log:

Loading source files for package org.mvel2.templates.util.io...
Loading source files for package org.mvel2.util...
10 errors
[INFO] 
[INFO] 
[INFO] Skipping mvel
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 42.972 s
[INFO] Finished at: 2017-08-30T21:18:44Z
[INFO] Final Memory: 25M/84M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (default-cli) on 
project mvel2: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/mvel-2.3.1/src/main/java/org/mvel2/util/Make.java:32: error: as of 
release 9, '_' is a keyword, and may not be used as an identifier
[ERROR] public Map _(K key, V value) {
[ERROR]  ^
[ERROR] /build/mvel-2.3.1/src/main/java/org/mvel2/util/Make.java:37: error: as 
of release 9, '_' is a keyword, and may not be used as an identifier
[ERROR] public java.util.Map _() {
[ERROR]^


Cheers,
Chris.

Bug#875594: FTBFS with Java 9: test failures around reflection on core classes

[Chris West]

Source: kryo-serializers
Version: 0.22-3
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

It goes digging around in core classes and looking at their fields. This
will be banned in a future release. I can't see where it's doing it in
the code at the moment, but I suspect it has some implementation details
of e.g. ArrayList hardcoded.

This package has no rdeps, and is a library, so could be RM'd. It was
added as a build-dep of sbt, which might be coming back into Debian at
some point, so maybe people will argue to leave it for that reason.

Build log:

---
 T E S T S
---
Running TestSuite
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
de.javakaffee.kryoserializers.ArraysAsListSerializer 
(file:/build/kryo-serializers-0.22/target/classes/) to field 
java.util.Arrays$ArrayList.a
WARNING: Please consider reporting this to the maintainers of 
de.javakaffee.kryoserializers.ArraysAsListSerializer
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
have size: 4096
Tests run: 47, Failures: 7, Errors: 0, Skipped: 3, Time elapsed: 2.595 sec <<< 
FAILURE! - in TestSuite
testArrayListSubList(de.javakaffee.kryoserializers.SubListSerializersTest)  
Time elapsed: 0.031 sec  <<< FAILURE!
java.lang.RuntimeException: java.lang.NoSuchFieldException: parentOffset
at 
de.javakaffee.kryoserializers.SubListSerializersTest.doTest(SubListSerializersTest.java:60)
at 
de.javakaffee.kryoserializers.SubListSerializersTest.testArrayListSubList(SubListSerializersTest.java:83)
Caused by: java.lang.NoSuchFieldException: parentOffset
at 
de.javakaffee.kryoserializers.SubListSerializersTest.doTest(SubListSerializersTest.java:60)
at 
de.javakaffee.kryoserializers.SubListSerializersTest.testArrayListSubList(SubListSerializersTest.java:83)

testArrayListSubListSubList(de.javakaffee.kryoserializers.SubListSerializersTest)
  Time elapsed: 0.006 sec  <<< FAILURE!
java.lang.RuntimeException: java.lang.NoSuchFieldException: parentOffset
at 
de.javakaffee.kryoserializers.SubListSerializersTest.doTest(SubListSerializersTest.java:60)
at 
de.javakaffee.kryoserializers.SubListSerializersTest.testArrayListSubListSubList(SubListSerializersTest.java:89)
Caused by: java.lang.NoSuchFieldException: parentOffset
at 
de.javakaffee.kryoserializers.SubListSerializersTest.doTest(SubListSerializersTest.java:60)
at 
de.javakaffee.kryoserializers.SubListSerializersTest.testArrayListSubListSubList(SubListSerializersTest.java:89)




Cheers,
Chris.

Bug#875592: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: jzmq
Version: 3.1.0
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javadoc needs the full build classpath to generate documentation now.

Build log:

Loading source file ./src/test/java/org/zeromq/ZThreadTest.java...
Constructing Javadoc information...
./src/test/java/org/zeromq/ZContextTest.java:3: error: package org.junit does 
not exist
import org.junit.Test;
^
./src/test/java/org/zeromq/ZContextTest.java:6: error: package org.junit does 
not exist
import static org.junit.Assert.assertEquals;
   ^
./src/test/java/org/zeromq/ZContextTest.java:6: error: static import only from 
classes and interfaces
import static org.junit.Assert.assertEquals;
^
./src/test/java/org/zeromq/ZContextTest.java:7: error: package org.junit does 
not exist
import static org.junit.Assert.assertTrue;
   ^



Cheers,
Chris.

Bug#875590: FTBFS with Java 9: test fails

[Chris West]

Source: junit4
Version: 4.12
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

---
 T E S T S
---
Running org.junit.tests.AllTests
Tests run: 876, Failures: 1, Errors: 0, Skipped: 7, Time elapsed: 21.901 sec 
<<< FAILURE! - in org.junit.tests.AllTests
providesAnnotatedMethodsSortedByName(org.junit.runners.model.TestClassTest)  
Time elapsed: 0.019 sec  <<< FAILURE!
java.lang.AssertionError: 
Wrong number of annotated methods.
Expected: is <3>
 but: was <9>
at 
org.junit.runners.model.TestClassTest.providesAnnotatedMethodsSortedByName(TestClassTest.java:142)


Results :

Failed tests: 
  TestClassTest.providesAnnotatedMethodsSortedByName:142 Wrong number of 
annotated methods.
Expected: is <3>
 but: was <9>

Tests run: 876, Failures: 1, Errors: 0, Skipped: 7




Cheers,
Chris.

Bug#875591: FTBFS with Java 9: sun.audio

[Chris West]

Source: jxplorer
Version: 3.3.2+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

sun.audio seems to have been removed.

Build log:

warning: [options] source value 1.5 is obsolete and will be removed in a future 
release
XXX: totally hacking the source version
warning: [options] target value 1.5 is obsolete and will be removed in a future 
release
XXX: totally hacking the target version
src/com/ca/directory/jxplorer/editor/audioeditor.java:28: error: cannot find 
symbol
protected AudioStreamaudioStream;
  ^
  symbol:   class AudioStream
  location: class audioeditor
src/com/ca/directory/jxplorer/editor/audioaccessory.java:8: warning: 
AppletAudioClip is internal proprietary API and may be removed in a future 
release
import sun.applet.AppletAudioClip;
 ^
src/com/ca/directory/jxplorer/editor/audioeditor.java:15: error: package 
sun.audio does not exist
import sun.audio.*;
^
src/com/ca/directory/jxplorer/tree/SmartTree.java:23: warning: 
DragSourceContextPeer is internal proprietary API and may be removed in a 
future release
import java.awt.dnd.peer.DragSourceContextPeer;
^
src/com/ca/directory/jxplorer/editor/audioeditor.java:135: error: cannot find 
symbol
audioStream = new AudioStream(new ByteArrayInputStream(bytes));
  ^
  symbol:   class AudioStream
  location: class audioeditor
src/com/ca/directory/jxplorer/editor/audioeditor.java:146: error: package 
AudioPlayer does not exist
 AudioPlayer.player.start(audioStream);
^
src/com/ca/directory/jxplorer/editor/audioeditor.java:154: error: package 
AudioPlayer does not exist
 AudioPlayer.player.stop(audioStream);
^
src/com/ca/directory/jxplorer/editor/audioaccessory.java:117: warning: 
AppletAudioClip is internal proprietary API and may be removed in a future 
release
  currentClip = new AppletAudioClip(u);
^
src/com/ca/directory/jxplorer/tree/SmartTree.java:2182: warning: 
DragSourceContextPeer is internal proprietary API and may be removed in a 
future release
(DragSourceContextPeer dscp, DragGestureEvent dgl, Cursor 
dragCursor,
 ^
src/com/ca/directory/jxplorer/tree/SmartTree.java:2186: error: constructor 
DragSourceContext in class DragSourceContext cannot be applied to given types;
return new DragSourceContext(dscp, dgl, dragCursor, dragImage, 
imageOffset, t, dsl)
   ^
  required: DragGestureEvent,Cursor,Image,Point,Transferable,DragSourceListener
  found: 
DragSourceContextPeer,DragGestureEvent,Cursor,Image,Point,Transferable,DragSourceListener
  reason: actual and formal argument lists differ in length




Cheers,
Chris.

Bug#875589: FTBFS with Java 9: pkcs11 api has all changed

[Chris West]

Source: jss
Version: 4.3.1-7
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The PKCS11 API has totally changed in Java 9. There doesn't appear to be
a compatible way to support both Java 8 and Java 9. This fails at
runtime, as well as at compile time. This is very annoying.

Here's the new API details:
https://docs.oracle.com/javase/9/security/pkcs11-reference-guide1.htm

DAVMAIL upstream have come up with a solution involving reflection for
their small usecase:

 * https://bugs.debian.org/873218
 * https://sourceforge.net/p/davmail/feature-requests/112/#6947


It's possible that some API usage can be restored by including the module,
as explained by the error message. I didn't try it.


Build log:

./org/mozilla/jss/pkcs11/PK11SymmetricKeyDeriver.java:41: error: package 
sun.security.pkcs11.wrapper is not visible
import sun.security.pkcs11.wrapper.*;
  ^
  (package sun.security.pkcs11.wrapper is declared in module 
jdk.crypto.cryptoki, which is not in the module graph)
./org/mozilla/jss/tests/SymKeyDeriving.java:43: error: package 
sun.security.pkcs11.wrapper is not visible
import sun.security.pkcs11.wrapper.PKCS11Constants;
  ^
  (package sun.security.pkcs11.wrapper is declared in module 
jdk.crypto.cryptoki, which is not in the module graph)


Cheers,
Chris.

Bug#875588: FTBFS with Java 9: sun.management

[Chris West]

Source: jruby
Version: 9.1.8.0
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

These sun.* packages are generally gone.
Upstream have switched this specific one to a reflective call:
https://github.com/jruby/jruby/commit/304342c8f8071faa829679e2d62f6aa312d45185

Build log:

[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/jruby-9.1.8.0/core/src/main/java/org/jruby/management/BeanManagerImpl.java:[87,26]
 error: cannot find symbol
  symbol:   class Agent
  location: package sun.management
[INFO] 1 error




Cheers,
Chris.

Bug#875587: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: josql
Version: 2.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javadoc has got stricter about getting the classpath right during the
generation of javadoc.

Build log:

  [javadoc] Constructing Javadoc information...
  [javadoc] 
/build/josql-2.2/src/org/josql/contrib/JoSQLAntFileSelector.java:19: error: 
package org.apache.tools.ant.types.selectors does not exist
  [javadoc] import org.apache.tools.ant.types.selectors.ExtendFileSelector;
  [javadoc]^
  [javadoc] 
/build/josql-2.2/src/org/josql/contrib/JoSQLAntFileSelector.java:21: error: 
package org.apache.tools.ant.types does not exist
  [javadoc] import org.apache.tools.ant.types.Parameter;
  [javadoc]  ^



Cheers,
Chris.

Bug#875584: FTBFS with Java 9: can't find jdk

[Chris West]

Source: jhdf
Version: 2.11.0+dfsg-2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

checking HDF4to5 library... no
checking jni.h usability... yes
checking jni.h presence... yes
checking for jni.h... yes
configure: error: cannot find jdk classes in JDK lib path.
/usr/share/cdbs/1/class/autotools.mk:44: recipe for target 
'debian/stamp-autotools' failed
make: *** [debian/stamp-autotools] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Cheers,
Chris.

Bug#875585: FTBFS with Java 9: AWT api changes

[Chris West]

Source: jmol
Version: 14.6.4+2016.11.05+dfsg1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

cd JSpecView && ant -Dnetscape.jar.path=/usr/share/icedtea-web/plugin.jar 
-DPrivate.propertyFile=none make-application-jar javadoc
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 
Buildfile: /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/build.xml
[input] skipping input as property Private.propertyFile has already been 
set.

build:
 [echo] copying files from ../Jmol/src/org/jmol
 [copy] Copying 5 files to 
/build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/src/org/jmol
 [echo] getting application icons and resources
[mkdir] Created dir: /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/bin
[javac] Compiling 86 source files to 
/build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/bin
[javac] 
/build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/src/jspecview/application/AwtTreeNode.java:9:
 error: AwtTreeNode is not abstract and does not override abstract method 
children() in JSVTreeNode
[javac] public class AwtTreeNode extends
[javac]^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 1 error

BUILD FAILED
/build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/build.xml:115: Compile failed; 
see the compiler error output for details.



Cheers,
Chris.

Bug#875582: FTBFS with Java 9: boot classpath misdetected

[Chris West]

Source: jclic
Version: 0.3.2.1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The build tries to overload the boot classpath, which is just not
helpful for Debian, and wrong for Java 9, as the .jars are *gone*:
https://sources.debian.net/src/jclic/0.3.2.1-1/build.xml/#L47

Build log:

init:
 [echo] -
 [echo] JClic build
 [echo] -
 [echo] Using Apache Ant(TM) version 1.9.9 compiled on June 29 2017, in 
/usr/share/ant
 [echo] Using Java 9-Debian by Oracle Corporation in 
/usr/lib/jvm/java-9-openjdk-amd64
 [echo] Generating code for Java 1.6
 [echo] Bootstrap: /usr/lib/jvm/java-9-openjdk-amd64/lib/rt.jar
[mkdir] Created dir: /build/jclic-0.3.2.1/build


...

[ext.javac.nogenerics] 3 warnings
[ext.javac.nogenerics] Fatal Error: Unable to find package java.lang in 
classpath or bootclasspath





Cheers,
Chris.

Bug#875583: FTBFS with Java 9: checks for java 8

[Chris West]

Source: jedit
Version: 5.4.0+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

init:
 [echo] Buildfile for jedit (/build/jedit-5.4.0+dfsg/build.xml)

BUILD FAILED
/build/jedit-5.4.0+dfsg/build.xml:78: Java 1.8 is needed for jEdit to build, 
please install it and rerun (found Java version: '9')


Cheers,
Chris.

Bug#875580: FTBFS with Java 9: -source, enum as keyword

[Chris West]

Source: jcharts
Version: 0.7.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

-source is set to 1.5, which is too low. After fixing this, 'enum' is
used as a keyword, which is now illegal.

Build log:

compile:
[javac] /build/jcharts-0.7.5/build/build.xml:50: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 121 source files to /build/jcharts-0.7.5/build/garbage
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.4
[javac] warning: [options] source value 1.4 is obsolete and will be removed 
in a future release
[javac] XXX: totally hacking the source version
[javac] /build/jcharts-0.7.5/src/org/jCharts/chartText/TextTag.java:407: 
error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] java.util.Enumeration enum = attributes.keys();
[javac]   ^
[javac] /build/jcharts-0.7.5/src/org/jCharts/chartText/TextTag.java:409: 
error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] while( enum.hasMoreElements() )
[javac]^
[javac] /build/jcharts-0.7.5/src/org/jCharts/chartText/TextTag.java:411: 
error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] Object ob = enum.nextElement();
[javac] ^
[javac] 3 errors
[javac] 2 warnings



Cheers,
Chris.

Bug#875579: FTBFS with Java 9: library path guessed wrong

[Chris West]

Source: jcc
Version: 2.22
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The guess of the path of the libraries is wrong:
https://sources.debian.net/src/jcc/2.22-1/debian/rules/#L24

See the wiki about "/jre".

Build log:

x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -W[...] 
-L/usr/lib/jvm/default-java/jre/lib/amd64 -ljava 
-L/usr/lib/jvm/default-java/jre/lib/amd64/server -ljvm [...]
/usr/bin/ld: cannot find -ljava
/usr/bin/ld: cannot find -ljvm
collect2: error: ld returned 1 exit status


Cheers,
Chris.

Bug#875578: FTBFS with Java 9: javax.xml.bind

[Chris West]

Source: jaxrs-api
Version: 2.0.1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javax.xml.bind has been hidden behind module flags. Looks like it's only
necessary for tests here. (And for consumers.)

Build log:

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - in 
javax.ws.rs.core.GenericEntityTest
Running javax.ws.rs.core.MediaTypeTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
javax.ws.rs.core.MediaTypeTest
Running javax.ws.rs.core.JaxbLinkTest
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.003 sec <<< 
FAILURE! - in javax.ws.rs.core.JaxbLinkTest
testSerializationOfJaxbLink(javax.ws.rs.core.JaxbLinkTest)  Time elapsed: 0.003 
sec  <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext
at 
javax.ws.rs.core.JaxbLinkTest.testSerializationOfJaxbLink(JaxbLinkTest.java:69)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext
at 
javax.ws.rs.core.JaxbLinkTest.testSerializationOfJaxbLink(JaxbLinkTest.java:69)


Results :

Tests in error: 
  JaxbLinkTest.testSerializationOfJaxbLink:69 NoClassDefFound 
javax/xml/bind/JAX...




Cheers,
Chris.

Bug#875577: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: jaxe
Version: 3.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javadoc needs the same classpath that the main build needs now.

Build log:

BUILD SUCCESSFUL
Total time: 11 seconds
chmod -x editeurconfig-source/dist/editeurconfig.jar
rm -f dist/Jaxe/*.bat
rm -f dist/Jaxe/config/dita/license.txt
( cd source ; javadoc -notimestamp -encoding iso-8859-1 -d api jaxe )
Loading source files for package jaxe...
Constructing Javadoc information...
./jaxe/AboutBox.java:15: error: package org.apache.log4j does not exist
import org.apache.log4j.Logger;
   ^
./jaxe/AboutBox.java:38: error: cannot find symbol
private static final Logger LOG = Logger.getLogger(AboutBox.class);
 ^




Cheers,
Chris.

Bug#875576: FTBFS with Java 9: _, -source/-target

[Chris West]

Source: java-gnome
Version: 4.1.3
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Looks like it's just confused about -source and -target, which need to
be >1.5 and <9 (as _ is used). It wasn't picked up by the automatic tool
as apparently the tool has made javadoc(1) AssertionError, cool.

Build log:

JAVADOC doc/api/*.html
/usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc -d doc/api -public -nodeprecated 
-source 1.5 ...
error: Source option 1.5 is no longer supported. Use 1.6 or later.


..or:

Loading source file src/bindings/org/freedesktop/bindings/Time.java...
Loading source file src/bindings/org/freedesktop/bindings/Version.java...
Loading source file 
src/bindings/org/freedesktop/bindings/Internationalization.java...
src/bindings/org/freedesktop/bindings/Internationalization.java:380: warning: 
as of release 9, '_' is a keyword, and may not be used as an identifier
public static final String _(String msg, java.lang.Object... parameters) {
   ^
Loading source files for package org...
Constructing Javadoc information...
javadoc: error - fatal error encountered: java.lang.AssertionError
javadoc: error - Please file a bug against the javadoc tool via the Java bug 
reporting page
(http://bugreport.java.com) after checking the Bug Database 
(http://bugs.java.com)
for duplicates. Include error messages and the following diagnostic in your 
report. Thank you.
java.lang.AssertionError
at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155)
at 
jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62)
at 
jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1193)
at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.findModuleOfPackageName(ElementsTable.java:864)
at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.addPackagesFromLocations(ElementsTable.java:547)
at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.computeSubpackages(ElementsTable.java:520)
at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.computeSpecifiedPackages(ElementsTable.java:754)
at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.analyze(ElementsTable.java:348)
at 
jdk.javadoc/jdk.javadoc.internal.tool.JavadocTool.getEnvironment(JavadocTool.java:211)
at 
jdk.javadoc/jdk.javadoc.internal.tool.Start.parseAndExecute(Start.java:562)
at jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:423)
at jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:340)
at jdk.javadoc/jdk.javadoc.internal.tool.Main.execute(Main.java:63)
at jdk.javadoc/jdk.javadoc.internal.tool.Main.main(Main.java:52)
2 errors
2 warnings
Makefile:87: recipe for target 'doc' failed



Cheers,
Chris.

Bug#875418: FTBFS with Java 9: sun.awt.X11GraphicsDevice

[Chris West]

Source: java3d
Version: 1.5.2+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

jni has changed, and sun.awt.X11GraphicsDevice is pretty gone.

Build log:

compile-ogl:
 [echo] Executing 64 bit native renderer build [opt]
 [exec] 
/build/java3d-1.5.2+dfsg/j3d-core/src/native/ogl/DrawingSurfaceObjectAWT.c:38:10:
 fatal error: jni.h: No such file or directory
 [exec]  #include 
 [exec]   ^~~
 [exec] compilation terminated.
 [exec] /build/java3d-1.5.2+dfsg/j3d-core/src/native/ogl/Canvas3D.c:45:10: 
fatal error: jni.h: No such file or directory
 [exec]  #include 
 [exec]   ^~~
 [exec] compilation terminated.

...

  [javadoc] Constructing Javadoc information...
  [javadoc] 
/build/java3d-1.5.2+dfsg/j3d-core/src/classes/x11/javax/media/j3d/X11NativeScreenInfo.java:35:
 error: package sun.awt is not visible
  [javadoc] import sun.awt.X11GraphicsDevice;
  [javadoc]   ^
  [javadoc]   (package sun.awt is declared in module java.desktop, which does 
not export it to the unnamed module)


...


dh_installdirs -plibjava3d-jni \

dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
install -m 644 -D j3d-core/build/default/opt/native/libj3dcore-ogl.so \
debian/libjava3d-jni/usr/lib/jni/libj3dcore-ogl.so
install: cannot stat 'j3d-core/build/default/opt/native/libj3dcore-ogl.so': No 
such file or directory
debian/rules:24: recipe for target 'install/libjava3d-jni' failed
make: *** [install/libjava3d-jni] Error 1




Cheers,
Chris.

Bug#875416: FTBFS with Java 9: javax.xml.soap / (mvn) javadoc classpath

[Chris West]

Source: jasperreports
Version: 6.2.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Fails to find javax.xml.soap packages during maven javadoc generation.
Double-whammy of wiki-related fun!

Build log:

ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (default-cli) on 
project jasperreports: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/jasperreports-6.2.2/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:35:
 error: package javax.xml.soap is not visible
[ERROR] import javax.xml.soap.MessageFactory;
[ERROR] ^
[ERROR]   (package javax.xml.soap is declared in module java.xml.ws, which is 
not in the module graph)
[ERROR] 
/build/jasperreports-6.2.2/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:36:
 error: package javax.xml.soap is not visible
[ERROR] import javax.xml.soap.MimeHeaders;
[ERROR] ^





Cheers,
Chris.

Bug#875414: FTBFS with Java 9: ant javadoc classpath

[Chris West]

Source: janino
Version: 2.70
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javadoc has got strict about getting the classpath right, which this
package apparently doesn't do right.

Build log:

  [javadoc] Loading source files for package org.codehaus.commons.io...
  [javadoc] Constructing Javadoc information...
  [javadoc] 
/build/janino-2.7.0/janino/src/org/codehaus/janino/AntCompilerAdapter.java:32: 
error: package org.apache.tools.ant.types does not exist
  [javadoc] import org.apache.tools.ant.types.Path;
  [javadoc]  ^
  [javadoc] 
/build/janino-2.7.0/janino/src/org/codehaus/janino/AntCompilerAdapter.java:41: 
error: cannot find symbol
  [javadoc] class AntCompilerAdapter extends DefaultCompilerAdapter {
  [javadoc]  ^
  [javadoc]   symbol: class DefaultCompilerAdapter


Cheers,
Chris.

Bug#875411: FTBFS with Java 9: Module

[Chris West]

Source: jackson-databind
Version: 2.8.6
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/jackson-databind-2.8.6/src/main/java/com/fasterxml/jackson/databind/module/SimpleModule.java:[29,13]
 reference to Module is ambiguous
  both class com.fasterxml.jackson.databind.Module in 
com.fasterxml.jackson.databind and class java.lang.Module in java.lang match
[ERROR] 
/build/jackson-databind-2.8.6/src/main/java/com/fasterxml/jackson/databind/module/SimpleModule.java:[403,29]
 cannot find symbol
  symbol:   class SetupContext
  location: class com.fasterxml.jackson.databind.module.SimpleModule



Cheers,
Chris.

Bug#875412: FTBFS with Java 9: Module

[Chris West]

Source: jackson-datatype-guava
Version: 2.7.3
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/jackson-datatype-guava-2.7.3/src/main/java/com/fasterxml/jackson/datatype/guava/GuavaModule.java:[25,34]
 reference to Module is ambiguous
  both class com.fasterxml.jackson.databind.Module in 
com.fasterxml.jackson.databind and class java.lang.Module in java.lang match
[ERROR] 
/build/jackson-datatype-guava-2.7.3/src/main/java/com/fasterxml/jackson/datatype/guava/GuavaModule.java:[53,29]
 cannot find symbol
  symbol:   class SetupContext
  location: class com.fasterxml.jackson.datatype.guava.GuavaModule
[ERROR] 
/build/jackson-datatype-guava-2.7.3/src/main/java/com/fasterxml/jackson/datatype/guava/GuavaModule.java:[49,5]
 method does not override or implement a method from a supertype




Cheers,
Chris.

Bug#875408: FTBFS with Java 9: JDK detection

[Chris West]

Source: icu4j-4.4
Version: 4.4.2.2-2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Probably identical to https://bugs.debian.org/873217

Build log:

Buildfile: /build/icu4j-4.4-4.4.2.2/debian/.eclipse-build/build.xml

BUILD FAILED
/build/icu4j-4.4-4.4.2.2/debian/.eclipse-build/build.xml:37: The JDK version is 
too old or unknown.

Total time: 0 seconds


Cheers,
Chris.

Bug#875404: FTBFS with Java 9: sun.rmi.server

[Chris West]

Source: gridengine
Version: 8.1.9+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

sun.rmi, sun.management packages seem to have gone. They're not on the
list of things moved to modules, but maybe they have been!

Note that without ant 1.9.9-5 UNRELEASED you won't see this error.

Build log:

 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/JGDISecurityManager.java:34:
 warning: [deprecation] RMISecurityManager in java.rmi has been deprecated
 [java] [javac] import java.rmi.RMISecurityManager;
 [java] [javac]^
 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/ConnectorBootstrap.java:62:
 warning: UnicastServerRef is internal proprietary API and may be removed in a 
future release
 [java] [javac] import sun.rmi.server.UnicastServerRef;
 [java] [javac]  ^
 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/ConnectorBootstrap.java:63:
 warning: UnicastServerRef2 is internal proprietary API and may be removed in a 
future release
 [java] [javac] import sun.rmi.server.UnicastServerRef2;
 [java] [javac]  ^
 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/ConnectorBootstrap.java:64:
 error: cannot find symbol
 [java] [javac] import sun.management.Agent;
 [java] [javac]  ^
 [java] [javac]   symbol:   class Agent
 [java] [javac]   location: package sun.management
 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/ConnectorBootstrap.java:65:
 error: cannot find symbol
 [java] [javac] import sun.management.AgentConfigurationError;
 [java] [javac]  ^
 [java] [javac]   symbol:   class AgentConfigurationError
 [java] [javac]   location: package sun.management
 [java] [javac] 
/build/gridengine-8.1.9+dfsg/source/libs/jgdi/src/com/sun/grid/jgdi/management/ConnectorBootstrap.java:66:
 error: cannot find symbol
 [java] [javac] import static sun.management.AgentConfigurationError.*;


Cheers,
Chris.

Bug#875402: RM? FTBFS with Java 9, no upstream support, 1 recommends rdep

[Chris West]

Source: icu4j-4.2
Version: 4.2.1.1-5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk,
although it would probably be easy to fix.

The package has been superseded by multiple versions of icu4j, all of
which are still in the archive.

The only rdepend is a Recommends: by liblucene2-java, which I also hope
to RM: https://bugs.debian.org/875401

The package appears to already have been RM'd, I don't really understand
why it came back into the archive: https://bugs.debian.org/657305

Can we RM it again, and hope it stays dead this time?

Cheers,
Chris.