W3C home > Mailing lists > Public > public-rdf-ruby@w3.org > January 2018

Re: Spira dependency issue

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 8 Jan 2018 14:16:57 -0800
Message-Id: <89D3F5BB-56E3-4F16-A09E-6DC2DCECEE6C@greggkellogg.net>
Cc: "public-rdf-ruby@w3.org" <public-rdf-ruby@w3.org>
To: Stephen Meyer <stephen.meyer@wisc.edu>
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

> On Jan 8, 2018, at 2:06 PM, Stephen Meyer <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


Received on Monday, 8 January 2018 22:17:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:19 UTC