Re: Spira dependency issue

Greg, thanks for the quick response. It is greatly appreciated, in large part because I am quite a fan of the Spira gem for working with heterogeneous RDF data.

-Steve

On Jan 8, 2018, at 4:16 PM, Gregg Kellogg <gregg@greggkellogg.net<mailto:gregg@greggkellogg.net>> wrote:

Steve, I can take care of this, although I don’t think yanking is required, as there are still 2.x versions of RDF.rb available.

Ownership of this gem is flexible, and it’s never quite clear who should be doing maintenance releases, but this one is fairly simple.

Gregg Kellogg
gregg@greggkellogg.net<mailto:gregg@greggkellogg.net>

On Jan 8, 2018, at 2:06 PM, Stephen Meyer <stephen.meyer@wisc.edu<mailto:stephen.meyer@wisc.edu>> wrote:

Please let me know if this is not the appropriate list for this question/request.

I make use of the Spira gem in a project and noticed a dependency issue with the versions that have received the recent RDF 3.0 update and what is in RubyGems. What I am seeing is the following:

Spira in the main GitHub account<https://github.com/ruby-rdf/spira> is version 2.0.2 had its dependencies<https://github.com/ruby-rdf/spira/blob/develop/spira.gemspec> updated so they generally look like this:

     gem.add_runtime_dependency 'rdf', '>= 2.2', '< 4.0'

However, in RubyGems the latest version is 2.1.0 and it is pegged to rdf ~> 2.0.

Is it possible to yank the 2.1.0 Spira gem, update the 2.1.x branch’s gemspec to at least the same gemspec RDF requirements as 2.0.x branch, and push it as 2.1.1 version to both GitHub and RubyGems?

Thanks,
Steve Meyer