Your message dated Thu, 03 Mar 2016 18:50:48 +0000
with message-id <e1abykm-00005q...@franck.debian.org>
and subject line Bug#816359: fixed in ruby-solve 2.0.2-1
has caused the Debian Bug report #816359,
regarding ruby-solve: FTBFS: got #<NoMethodError: undefined method 
`allow_missing?' for #<Solve::RubySolver:0x00000001df6f00>> with backtrace:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-solve
Version: 2.0.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-solve fails to build from source in unstable/amd64:

  [..]

  Pending: (Failures listed here are expected and do not affect your suite's 
status)
  
    1) Solve::GecodeSolver finding unsatisfiable demands partitions demands 
into satisfiable and not satisfiable
       # Not yet implemented
       # ./spec/unit/solve/gecode_solver_spec.rb:183
  
    2) Solve ClassMethods #it returns nil if a solution does not exist
       # No reason given
       # ./spec/unit/solve_spec.rb:8
  
    3) Solve ClassMethods #it! raises NoSolutionError if a solution does not 
exist
       # No reason given
       # ./spec/unit/solve_spec.rb:14
  
  Failures:
  
    1) Solutions when using the ruby solver raises NoSolutionError when a 
solution cannot be found
       Failure/Error: lambda {
         expected Solve::Errors::NoSolutionError, got #<NoMethodError: 
undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001df6f00>> 
with backtrace:
           # ./lib/solve/ruby_solver.rb:177:in `resolve_with_error_wrapping'
           # ./lib/solve/ruby_solver.rb:72:in `resolve'
           # ./lib/solve.rb:64:in `it!'
           # ./spec/acceptance/ruby_solver_solutions_spec.rb:36:in `block (3 
levels) in <top (required)>'
           # ./spec/acceptance/ruby_solver_solutions_spec.rb:35:in `block (2 
levels) in <top (required)>'
       # ./spec/acceptance/ruby_solver_solutions_spec.rb:35:in `block (2 
levels) in <top (required)>'
  
    2) Solutions when using the ruby solver tries all combinations until it 
finds a solution
       Failure/Error: result = Solve.it!(graph, demands)
       NoMethodError:
         undefined method `allow_missing?' for 
#<Solve::RubySolver:0x00000001f7b448>
       # ./lib/solve/ruby_solver.rb:177:in `resolve_with_error_wrapping'
       # ./lib/solve/ruby_solver.rb:72:in `resolve'
       # ./lib/solve.rb:64:in `it!'
       # ./spec/acceptance/ruby_solver_solutions_spec.rb:201:in `block (2 
levels) in <top (required)>'
  
    3) Solve::RubySolver when the constraints are not solvable and molinillo 
identifies constraints that exclude all known versions raises an error 
detailing the missing artifacts
       Failure/Error: expect(error).to 
be_a_kind_of(Solve::Errors::NoSolutionError)
         expected #<NoMethodError: undefined method `allow_missing?' for 
#<Solve::RubySolver:0x00000001cbaa38>> to be a kind of 
Solve::Errors::NoSolutionError
       # ./spec/unit/solve/ruby_solver_spec.rb:110:in `block (4 levels) in <top 
(required)>'
  
    4) Solve::RubySolver when the constraints are not solvable and molinillo 
identifies missing artifacts raises an error detailing the missing artifacts
       Failure/Error: expect(error).to 
be_a_kind_of(Solve::Errors::NoSolutionError)
         expected #<NoMethodError: undefined method `allow_missing?' for 
#<Solve::RubySolver:0x00000001c5dcc0>> to be a kind of 
Solve::Errors::NoSolutionError
       # ./spec/unit/solve/ruby_solver_spec.rb:90:in `block (4 levels) in <top 
(required)>'
  
  Deprecation Warnings:
  
  RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= 
is deprecated, it is now set to true as default and setting it to false has no 
effect.
  
  Using `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 
/home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/spec/unit/solve/gecode_solver_spec.rb:68:in
 `block (2 levels) in <top (required)>'.
  
  Using `stub` from rspec-mocks' old `:should` syntax without explicitly 
enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
enable `:should` instead. Called from 
/home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/spec/unit/solve/gecode_solver_spec.rb:153:in
 `block (4 levels) in <top (required)>'.
  
  
  If you need more of the backtrace for any of these deprecations to
  identify where to make the necessary changes, you can configure
  `config.raise_errors_for_deprecations!`, and it will turn the
  deprecation warnings into errors, giving you the full backtrace.
  
  3 deprecation warnings total
  
  Finished in 0.12653 seconds (files took 0.12439 seconds to load)
  105 examples, 4 failures, 3 pending
  
  Failed examples:
  
  rspec ./spec/acceptance/ruby_solver_solutions_spec.rb:31 # Solutions when 
using the ruby solver raises NoSolutionError when a solution cannot be found
  rspec ./spec/acceptance/ruby_solver_solutions_spec.rb:167 # Solutions when 
using the ruby solver tries all combinations until it finds a solution
  rspec ./spec/unit/solve/ruby_solver_spec.rb:109 # Solve::RubySolver when the 
constraints are not solvable and molinillo identifies constraints that exclude 
all known versions raises an error detailing the missing artifacts
  rspec ./spec/unit/solve/ruby_solver_spec.rb:89 # Solve::RubySolver when the 
constraints are not solvable and molinillo identifies missing artifacts raises 
an error detailing the missing artifacts
  
  Randomized with seed 54553
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/debian/ruby-solve
 returned exit code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      la...@debian.org / chris-lamb.co.uk
       `-

Attachment: ruby-solve.2.0.1-2.unstable.amd64.log.txt.gz
Description: Binary data


--- End Message ---
--- Begin Message ---
Source: ruby-solve
Source-Version: 2.0.2-1

We believe that the bug you reported is fixed in the latest version of
ruby-solve, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia <s...@sebian.fr> (supplier of updated ruby-solve package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 03 Mar 2016 15:27:17 -0300
Source: ruby-solve
Binary: ruby-solve
Architecture: source all
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Sebastien Badia <s...@sebian.fr>
Description:
 ruby-solve - Ruby version constraint solver implementing semantic versioning
Closes: 816359
Changes:
 ruby-solve (2.0.2-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Christian Hofstaedtler ]
   * Add patch for Molinillo 0.4
 .
   [ Sebastien Badia ]
   * Imported Upstream version (Closes: #816359)
   * Bump compat. version to 9
   * d/control:
       Update Vcs-* fields (use https everywhere)
       Bump Standards-Version to 3.9.7 (no changes)
   * Update Debian packaging using dh-make-ruby
   * d/patches:
       Remove spork usage (ROM)
       Remove Change-Version-to-Semverse-Version patch (applied upstream)
Checksums-Sha1:
 6fb36b39b8a12ccd9c53046846f4daabd34875f6 1750 ruby-solve_2.0.2-1.dsc
 6bd91ddbb57f0eb94d42850fe2a0626832e7e6ae 127295 ruby-solve_2.0.2.orig.tar.gz
 0219a41a933a8538c0038d24ca8434d6d7f32262 3040 ruby-solve_2.0.2-1.debian.tar.xz
 23d571b7180102858dffd07a005e742d2f935b2e 12864 ruby-solve_2.0.2-1_all.deb
Checksums-Sha256:
 507d6e5ed2e2551024a1868d9efb546835b21298d0fb72a333668ee6d804fedb 1750 
ruby-solve_2.0.2-1.dsc
 40be2beb238c21088a1a82f4ed61f09168a2c229c70c43a484dfe09f5330a859 127295 
ruby-solve_2.0.2.orig.tar.gz
 26d4aa57faf704dd5b97a4efe2cbb47ffd2b333cffedfa16a73844a967467cfd 3040 
ruby-solve_2.0.2-1.debian.tar.xz
 7065fc277d47c3ed02240e3b970f2d26ea393b043d50fef4efd9824a67a0eb57 12864 
ruby-solve_2.0.2-1_all.deb
Files:
 0ce93482f0be5aa31dd43fd577f28ff6 1750 ruby optional ruby-solve_2.0.2-1.dsc
 8b87c8456c76bb6eba42d2e2391d08f6 127295 ruby optional 
ruby-solve_2.0.2.orig.tar.gz
 d7b74aae688e70e37c00e8290e13e463 3040 ruby optional 
ruby-solve_2.0.2-1.debian.tar.xz
 1236ee8518e687068d9d364e48e675c7 12864 ruby optional ruby-solve_2.0.2-1_all.deb

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJW2IWOAAoJEImvgrc5zSF6CIkH+wXljd10DJaV4T9YetzHAZ73
aDfsS3htDmCyITwIrAwSNAx6JkfkmvfpN3EZE9yJupkCbMvL2Mp/rvyTCua+8OyR
WgVZgA1wZcr4BsE1hoQ/9Vxw/ftV/P/8/Y8edL1+xkh8S+No0nYaiamuQYkRRkpL
F/Igq4OMcgghOB02S+ODuaXvZLuw7WG0OdTE8i1rLzpRyNZQJQDkiqfQYh/BznJ7
4W4FRxJxfmUQbxKD4wzgANXNADF7D/xJw4qVKF0bs6vxqo1qliPRFbsxNVJYCXi9
N/lL3GELkOZWNelr5oeDyUxoNWOw5RMq+S9Kd6p1hxBwDQ6obt9qhzcTAeNjOhE=
=N4l2
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to