Source: ruby-ntlm Version: 0.6.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: OpenSSL::Digest::MD4.digest pwd > > OpenSSL::Digest::DigestError: > Digest initialization failed: initialization error > # ./lib/net/ntlm.rb:149:in `ntlm_hash' > # ./spec/lib/net/ntlm_spec.rb:119:in `block (2 levels) in <top > (required)>' > > Finished in 0.29403 seconds (files took 0.31806 seconds to load) > 741 examples, 19 failures > > Failed examples: > > rspec ./spec/lib/net/ntlm/client/session_spec.rb:14 # > Net::NTLM::Client::Session#sign_message signs a message and when KEY_EXCHANGE > is true > rspec ./spec/lib/net/ntlm/client/session_spec.rb:27 # > Net::NTLM::Client::Session#verify_signature verifies a message signature > rspec ./spec/lib/net/ntlm/client/session_spec.rb:39 # > Net::NTLM::Client::Session#seal_message should seal the message > rspec ./spec/lib/net/ntlm/client/session_spec.rb:47 # > Net::NTLM::Client::Session#unseal_message should unseal the message > rspec ./spec/lib/net/ntlm/client/session_spec.rb:55 # > Net::NTLM::Client::Session#exported_session_key returns a random 16-byte key > when negotiate_key_exchange? is true > rspec ./spec/lib/net/ntlm/message/type2_spec.rb:64 # > Net::NTLM::Message::Type2 should generate a type 3 response > rspec ./spec/lib/net/ntlm/message/type2_spec.rb:81 # > Net::NTLM::Message::Type2 should upcase domain when provided > rspec ./spec/lib/net/ntlm/message/type3_spec.rb:97 # > Net::NTLM::Message::Type3.parse with NTLMv2 data #blank_password? should be > true > rspec ./spec/lib/net/ntlm/message/type3_spec.rb:154 # > Net::NTLM::Message::Type3.parse NTLM2 Session Response Authentication; NTLM2 > Signing and Sealing Using the 128-bit NTLM2 Session Response User Session Key > With Key Exchange Negotiated #password? should be true for "test1234" > rspec ./spec/lib/net/ntlm/message/type3_spec.rb:159 # > Net::NTLM::Message::Type3.parse NTLM2 Session Response Authentication; NTLM2 > Signing and Sealing Using the 128-bit NTLM2 Session Response User Session Key > With Key Exchange Negotiated #blank_password? should be false > rspec ./spec/lib/net/ntlm_spec.rb:36 # Net::NTLM should encrypt the string > with DES for each key supplied > rspec ./spec/lib/net/ntlm_spec.rb:42 # Net::NTLM should generate an lm_hash > rspec ./spec/lib/net/ntlm_spec.rb:46 # Net::NTLM should generate an ntlm_hash > rspec ./spec/lib/net/ntlm_spec.rb:50 # Net::NTLM should generate an > ntlmv2_hash > rspec ./spec/lib/net/ntlm_spec.rb:62 # Net::NTLM should generate an > lm_response > rspec ./spec/lib/net/ntlm_spec.rb:71 # Net::NTLM should generate an > ntlm_response > rspec ./spec/lib/net/ntlm_spec.rb:81 # Net::NTLM should generate a > lvm2_response > rspec ./spec/lib/net/ntlm_spec.rb:91 # Net::NTLM should generate a > ntlmv2_response > rspec ./spec/lib/net/ntlm_spec.rb:116 # Net::NTLM should generate a > ntlm2_session > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2022/05/25/ruby-ntlm_0.6.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
