Bug 259649 - devel/rubygem-rdoc wrong number of arguments
Summary: devel/rubygem-rdoc wrong number of arguments
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ruby (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-04 17:50 UTC by Mikhail Teterin
Modified: 2022-01-08 06:17 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (ruby)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Teterin freebsd_committer freebsd_triage 2021-11-04 17:50:23 UTC
Trying to add the port -- with ruby30 -- I get the following error:

===> Fetching all distfiles required by rubygem-rdoc-6.3.2 for building
===>  Extracting for rubygem-rdoc-6.3.2
=> SHA256 Checksum OK for rubygem/rdoc-6.3.2.gem.
===>   rubygem-rdoc-6.3.2 depends on file: /opt/bin/ruby30 - found
===>   rubygem-rdoc-6.3.2 depends on file: /opt/bin/gem30 - found
ERROR:  While executing gem ... (Gem::Package::FormatError)
    package is corrupt, exception while verifying: wrong number of arguments (given 2, expected 1) (ArgumentError) in /usr/ports/distfiles/rubygem/rdoc-6.3.2.gem
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/rubygem-rdoc

Please, advise.
Comment 1 Henry Phan 2022-01-08 06:17:42 UTC
I'm running into this as well, using `lang/ruby30` and `devel/ruby-gems` with `DEFAULT_VERSIONS+=ruby=3.0` set in /etc/make.conf.

With this configuration, I'm not able to install any of the gems in the ports tree.

I think this is due to a mismatch between Ruby and RubyGems, based on the following:

* https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/ indicates that  Ruby 3.0 with RubyGems 3.2.3.

* https://cgit.freebsd.org/ports/tree/devel/ruby-gems/Makefile has RubyGems at 3.0.8.

* https://github.com/rubygems/rubygems/issues/4397 appears to be a report of the same issue, made by someone who had Ruby 3.0 paired with RubyGems 2.5.2.

I'm going to try putting together a port for RubyGems 3.2.3 to test this idea out. (This is my first time making a port, though, so I anticipate it'll take me some time.)