[DRE-maint] Bug#1025094: ruby-behance fails to rebuild after new upstream of ruby-faraday

Vinay vinaykeshava at disroot.org
Tue Nov 29 18:38:51 GMT 2022


Package: ruby-behance
Version:  0.6.1-4
Severity: important

Dear Maintainer,

While updating ruby-faraday to new upstream, rebuild of ruby-behance  fails
here is the log of the failed rebuild


/usr/bin/ruby3.0 -S gem build --config-file /dev/null --verbose 
/tmp/d20221127-92714-fvg3fe/gemspec
Failed to load /dev/null because it doesn't contain valid YAML hash
WARNING:  licenses is empty, but is recommended.  Use a license 
identifier from
http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
WARNING:  description and summary are identical
WARNING:  open-ended dependency on faraday (>= 0.15) is not recommended
   if faraday is semantically versioned, use:
     add_runtime_dependency 'faraday', '~> 0.15'
WARNING:  open-ended dependency on faraday_middleware (>= 0.12.2) is not 
recommended
   if faraday_middleware is semantically versioned, use:
     add_runtime_dependency 'faraday_middleware', '~> 0.12', '>= 0.12.2'
WARNING:  See https://guides.rubygems.org/specification-reference/ for help
   Successfully built RubyGem
   Name: behance
   Version: 0.6.1
   File: behance-0.6.1.gem
/usr/bin/ruby3.0 -S gem install --config-file /dev/null --verbose 
--local --verbose --no-document --ignore-dependencies --install-dir 
debian/ruby-behance/usr/share/rubygems-integration/all 
/tmp/d20221127-92714-fvg3fe/behance-0.6.1.gem
Failed to load /dev/null because it doesn't contain valid YAML hash
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/client.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/collections.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/creatives_to_follow.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/fields.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/project.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/user.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/version.rb
/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all/gems/behance-0.6.1/lib/behance/wips.rb
Successfully installed behance-0.6.1
1 gem installed
cd debian/ruby-behance/usr/share/rubygems-integration/all
rm -rf bin
rm -rf build_info
rm -rf cache
rm -rf doc
rm -rf extensions
rmdir plugins
cd gems/behance-0.6.1
rm -f
chmod 644 lib/behance/client.rb lib/behance/collections.rb 
lib/behance/creatives_to_follow.rb lib/behance/fields.rb 
lib/behance/project.rb lib/behance/user.rb lib/behance/version.rb 
lib/behance/wips.rb lib/behance.rb
find lib/ -type d -empty -delete
cd -
cd -
dh_installchangelogs -pruby-behance /<<PKGBUILDDIR>>/CHANGELOG.md upstream
/usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner

┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on 
ruby3.0                           │
└──────────────────────────────────────────────────────────────────────────────┘

GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-behance/usr/share/rubygems-integration/all:/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 
ruby3.0 -e gem\ \"behance\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in 
`raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, 
because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError)
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1379:in 
`activate'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1417:in 
`block in activate_dependencies'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`activate_dependencies'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
`activate'
     from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
     from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
     from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem'



More information about the Pkg-ruby-extras-maintainers mailing list