Public bug reported: Upon running e.g. Puppet's r10k, which makes use of ruby-faraday (version 0.15.4-3), a few lines of deprecation warnings are thrown on every invocation:
# /usr/bin/r10k deploy environment -p /usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given block using Proc.new is deprecated; use `&block` instead /usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given block using Proc.new is deprecated; use `&block` instead /usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given block using Proc.new is deprecated; use `&block` instead /usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given block using Proc.new is deprecated; use `&block` instead /usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given block using Proc.new is deprecated; use `&block` instead Apparently this is all known and fixed upstream already, see https://github.com/lostisland/faraday/pull/1082. Mind you that this is NOT an upgrade per se, but 0.17.x is the same as 0.15.4 with just bugfixes (see https://github.com/lostisland/faraday/blob/main/CHANGELOG.md#v0171). So updating this package to use 0.17.x would fix the issues without being an actual upgrade. Essentially it boils down to a single patch that likely fixes this particular issue: https://patch- diff.githubusercontent.com/raw/lostisland/faraday/pull/1009.patch, maybe that one could at least be applied if updating to 0.17.x is not feasible? ** Affects: ruby-faraday (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958629 Title: Deprecation warnings about Proc.new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-faraday/+bug/1958629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
