Note to all: I've done some hackery to get recent solargraph (0.60.x) working with old ruby-rbs, and in addition, I did some work to build the package from source instead of binary, and to run the test suite. I'm currently waiting for two unmaintained package orphan requests (ruby-parlour and ruby-commander) which are dependencies for ruby-sord, which in turn is a new AUR package that is now a dependency for this package.

I've opted to go ahead and update this package, but I'm unsure if the older versions of ruby-parlour and ruby-commander break either ruby-sord or this package. The actually required version of ruby-commander is 5.x, and the actual required version of ruby-parlour is 9.2.x.

I hope to maintain both those packages in the near future (or for the maintainers to suddenly become responsive). Will update this message when it is so.

Note to all: I've done some hackery to get recent solargraph (0.60.x) working with old ruby-rbs, and in addition, I did some work to build the package from source instead of binary, and to run the test suite. I'm currently waiting for two unmaintained package orphan requests (ruby-parlour and ruby-commander) which are dependencies for ruby-sord, which in turn is a new AUR package that is now a dependency for this package.

I've opted to go ahead and update this package, but I'm unsure if the older versions of ruby-parlour and ruby-commander break either ruby-sord or this package. The actually required version of ruby-commander is 5.x, and the actual required version of ruby-parlour is 9.2.x.

I hope to maintain both those packages in the near future (or for the maintainers to suddenly become responsive). Will update this message when it is so.

@rlees85 yes, I was working on getting this fixed since forever. I have been tracking this upstream with this issue. The problem seems to be that certain modules that used to be gem packages, are now a part of ruby itself. that means that when they are specified as a gem dependency in a gemspec file, stuff breaks: ruby, since version 3.3, has prism, but not as a gem. I'm working with upstream to get this fixed and in meantime have added two patches to this package so stuff works again.

Anyone else getting this?

$ solargraph
/usr/lib/ruby/3.4.0/rubygems/specification.rb:1421:in 'block in Gem::Specification#activate_dependencies': Could not find 'prism' (~> 1.4) among 120 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/rich/.local/share/gem/ruby/3.4.0:/usr/lib/ruby/gems/3.4.0' at: /usr/lib/ruby/gems/3.4.0/specifications/solargraph-0.56.1.gemspec, execute `gem env` for more information
        from /usr/lib/ruby/3.4.0/rubygems/specification.rb:1407:in 'Array#each'
        from /usr/lib/ruby/3.4.0/rubygems/specification.rb:1407:in 'Gem::Specification#activate_dependencies'
        from /usr/lib/ruby/3.4.0/rubygems/specification.rb:1389:in 'Gem::Specification#activate'
        from /usr/lib/ruby/3.4.0/rubygems.rb:290:in 'block in Gem.activate_bin_path'
        from /usr/lib/ruby/3.4.0/rubygems.rb:289:in 'Thread::Mutex#synchronize'
        from /usr/lib/ruby/3.4.0/rubygems.rb:289:in 'Gem.activate_bin_path'
        from /usr/bin/solargraph:25:in '<main>'

Can't work out what package provides the "prism" Gem. All I can find is that Ruby 3.4 should be using it by default anyway.

@7cff Unfortunately I no longer use Ruby enough to maintain this. I've disowned it if you'd like to adopt it

@mnussbaum The latest releases of Solargraph now depend on RBS 3.x. Are you still maintaining this?

@mnussbaum I had this error when launching solargraph : /usr/lib/ruby/3.0.0/rubygems/specification.rb:1453:in `rescue in block in activate_dependencies': Could not find 'rbs' (~> 2.0) among 121 total gem(s) (Gem::MissingSpecError) So I simply did as indicated here:

gem install rbs -v 2.0.0

and it now works ! :D I guess this is not a clean installation for the arch system, but until there is a fix...

Hmm, it looks like ruby-rbs packages RBS version 3.1.0, but solargraph depends on RBS 2.x. Any suggestions for how to deal with this?

Another vote here for adding ruby-rbs to the runtime deps:

/usr/lib/ruby/3.0.0/rubygems/specification.rb:1453:in `rescue in block in activate_dependencies': Could not find 'rbs' (~> 2.0) among 112 total gem(s) (Gem::MissingSpecError)

I think this should also depend on version 2 of rbs