Date: Fri, 22 Apr 2022 15:07:30 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 263470] net-mgmt/rubygem-oxidized-web: Fails to start with ruby30 Message-ID: <bug-263470-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263470 Bug ID: 263470 Summary: net-mgmt/rubygem-oxidized-web: Fails to start with ruby30 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: einar@isnic.is CC: nick@foobar.org CC: nick@foobar.org Flags: maintainer-feedback?(nick@foobar.org) Created attachment 233396 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233396&action= =3Dedit Add patch to work with Ruby 3.0 rubygem-oxidized-web built with ruby30 (current default) won't start. The error shown is: /usr/local/lib/ruby/gems/3.0/gems/puma-5.6.4/lib/rack/handler/puma.rb:63:in `run': wrong number of arguments (given 2, expected 1) (ArgumentError) from /usr/local/lib/ruby/gems/3.0/gems/oxidized-web-0.13.1/lib/oxidized/web.rb:2= 9:in `block in run' wrong number of arguments (given 2, expected 1) I've raised the issue with upstream project, but created this patch as well since I imagine it affects all using latest ports tree with default ruby settings. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263470-7788>