[Bug 258108] [exp-run] devel/ruby-gems: Update to 3.2.30 (Fixes for Ruby 3.0)
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 258108] devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 27 Jan 2022 11:30:58 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258108 Thibault Jouan <tj+freebsd_ports@a13.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #231355|0 |1 is obsolete| | --- Comment #65 from Thibault Jouan <tj+freebsd_ports@a13.fr> --- Created attachment 231387 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231387&action=edit update to 3.3.6 Thank you for the builds and list of failing ports. I was wrong in comment #60, change on textproc/rubygem-nokogiri is a recent patch addition, not removal. Anyway I adapted my patch for it, and other ports: devel/rubygem-gitlab-labkit fixed with nokogiri gemspec patch change devel/rubygem-mongo RubyGems version was in gemspec patch, fixed manually net/rubygem-kas-grpc gemspec patch fix net/rubygem-spamcheck gemspec patch fix textproc/rubygem-nokogiri new gemspec patch textproc/rubygem-nokogiri111 new port, needed gemspec patch Those ports seem to fail for reasons unrelated to RubyGems port patch: devel/rubygem-xdg port requires Ruby ~> 3.1 (marked broken otherwise) graphics/rubygem-objectdetect port maked broken mail/rubygem-tmail port marked broken science/cdcl port marked broken, unfetchable Those ports I ignore on purpose for now (comment #56 and bug #260207): www/rubygem-gollum-lib www/rubygem-gollum-rugged_adapter And now about databases/rubygem-mysql, it builds OK in my poudriere with Ruby 2.7 and default port options for the port. If you have time, take a look at the build log and guess if it's related to RubyGems. If something is worrying related to RubyGems, I'm interested to see the log. Last, can someone with the permission update the PR title with 3.3.6 instead of 3.2.30? -- You are receiving this mail because: You are the assignee for the bug.