Sinatra: Unable to activate dm-serializer-1.2.2, because json-2.0.2 conflicts with json (~> 1.6) (Gem::ConflictError)

Created on 10 May 2017  路  41Comments  路  Source: sinatra/sinatra

After Sinatra update to 2.0.0 version, my project fail to start.
Downgrade to sinatra 1.4.6 solved my issue.
Sinatra + Datamapper 1.2.0

How can i use SInatra 2.0.0 with Datamapper?

feedback
Source
picture frankymad
👍1

Most helpful comment

@lshep I see

If you create Gemfile with the following content:

# frozen_string_literal: true

source "https://rubygems.org"

git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }

gem "sinatra"
gem "data_mapper"

and issue the commands

gem install bundler
bundle install

you will be able to run irb like this:

$ bundle exec irb
irb(main):001:0> require './main'
=> true

and main.rb like this:

bundle exec ruby main.rb
picture dentarg on 20 Jun 2018
👍4 🚀2

All 41 comments

Could you provide a stacktrace?

zzak picture zzak on 10 May 2017

Help... Issue in my Proyect.

sandronicolasm picture sandronicolasm on 23 May 2017

`# frozen_string_literal: true
source "https://rubygems.org"

gem "sinatra", "~> 1.4.6"

gem "json", "~> 1.6"`

My Gemfile. Help. I'm sorry for my english.

sandronicolasm picture sandronicolasm on 28 May 2017

@smanezItec Could you send us a backtrace please? :bow:

zzak picture zzak on 29 May 2017

Having the same issue.

/home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:2288:in raise_if_conflicts': Unable to activate dm-seri alizer-1.2.2, because json-2.0.2 conflicts with json (~> 1.6) (Gem::ConflictError) from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1408:in activate' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1442:in block in activate_dependencies' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1428:in each' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1428:in activate_dependencies' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1410:in activate' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems.rb:220:in rescue in try_activate' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems.rb:213:in try_activate' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:126:in rescue in require' from /home/landen/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:40:in require' from main.rb:4:in <main>'

landendanyluk picture landendanyluk on 30 May 2017

I have this error too!

shortcircuit3 picture shortcircuit3 on 7 Jun 2017

Same here

gcstr picture gcstr on 7 Jun 2017

Soluci貌n: utilizar Bundler con un archivo Gemfile

Supongamos que tu aplicaci贸n se llama MiApp, se encuentra en mi_app/app.rb y tiene el siguiente c贸digo:

require 'sinatra'

class MiApp < Sinatra::Base
get "/" do
"Hola mundo!"
end
end

Crea un archivo Gemfile, en el directorio ra铆z de tu aplicaci贸n, con el siguiente contenido:

source "https://rubygems.org"

```

gem 'sinatra', '1.4.8'
gem 'data_mapper', '1.2.0'
gem 'dm-sqlite-adapter', '1.2.0'
gem 'json', '~>1.6'
gem 'thin', '1.7.0'
gem 'slim', '3.0.8'
gem 'shotgun', '0.9.2'

    Crea un archivo configu.ru, tambi茅n en el directorio ra铆z de tu aplicaci贸n, con el siguiente contenido:

   ```
 require 'rubygems'
    require 'bundler'

    Bundler.require

    require './app'
    run MiApp


Donde app se refiere al nombre de tu archivo (i.e. app.rb) y MiApp al nombre de tu clase dentro de ese archivo.

Ejecuta shotgun utilizando bundle exec (para utilizar la versi贸n de rake adecuada):

`$ bundle exec shotgun`

Con esta configuraci贸n garantizas que tu aplicaci贸n utilice las gemas y versiones indicadas en el Gemfile, independientemente de las versiones que tengas instaladas en tu sistema.

sandronicolasm picture sandronicolasm on 7 Jun 2017
👍4 🎉1

I have the same problem >> any solutions yet?

hamad2030 picture hamad2030 on 15 Jun 2017

Please remove the gem 'json', '...' from your Gemfile and try again :bow:

zzak picture zzak on 4 Jul 2017
😕1

I got this error, and I don't have JSON in my Gemfile, but I have plenty of other stuff:

source 'https://rubygems.org'
gem 'sinatra'
gem 'data_mapper'
gem 'webrick'
gem 'dm-sqlite-adapter'
gem 'actionview'
gem 'sinatra-flash'
gem 'rubyzip'
gem 'httparty'
gem 'aws-sdk'
gem 'net-ldap'
gem 'net-ssh'
gem 'duo-api'
mike-bailey picture mike-bailey on 5 Jul 2017
❤1

Apparently it is necessary to write this gem versions explicitly in the Gemfile and to use a config.ru to configure Rack. Smanezitec's solution with using Ruby 2.3.3 works fine for me:

My Gemfile:

source 'https://rubygems.org'

gem 'sinatra',            '1.4.8'
gem 'data_mapper',        '1.2.0'
gem 'dm-sqlite-adapter',  '1.2.0'
gem 'json',               '~>1.6'
gem 'shotgun',            '0.9.2'
gem 'slim',               '3.0.8'
gem 'thin',               '1.7.0'

my config.ru:

require 'rubygems'
require 'bundler'

Bundler.require

require './app'
run MiApp

my main.rb:

require 'sinatra'
require 'data_mapper'

# setup the database connection
DataMapper.setup(
  :default,
  ENV['DATABASE_URL'] || "sqlite3://#{Dir.pwd}/development.db"
)

# model definitions etc. placed here ...

# check the integrity of the models
DataMapper.finalize

class MiApp < Sinatra::Base
  get '/' do
    "Hello World!"
  end
end
casi picture casi on 22 Jul 2017
🎉1

Still an issue for me, used the above gemfile pretty much to the T and still didn't go

mike-bailey picture mike-bailey on 30 Jul 2017
👍3 🎉1

Ok, so then change the line

gem 'json', '~>1.6'

into

gem 'json', '1.8.6'

or uninstall json 2.1 if possible, and do a bundle install again.

casi picture casi on 31 Jul 2017
👍1

Even with both JSONs uninstalled, different combinations, etc this still persists.

mike-bailey picture mike-bailey on 22 Aug 2017
👍1

This issue still persist and Sinatra 2.0 can not be used with data_mapper, am I right?

szabcsee picture szabcsee on 1 Nov 2017
👍1

I'm not sure this is even an issue, or how Sinatra would be at fault.

We don't even specify json as a dependency:
https://github.com/sinatra/sinatra/blob/master/sinatra.gemspec#L28-L31

It must be caused through some transitive dependency that is apart of your application.

If anyone can provide a Gemfile.lock which reproduces the issue, and stacktrace to go with it, we could probably figure out which one.

zzak picture zzak on 2 Nov 2017

https://github.com/sinatra/sinatra/issues/1294#issuecomment-313166451 Don't have stack trace off-hand

mike-bailey picture mike-bailey on 2 Nov 2017

@mike-bailey could you share your lockfile?

zzak picture zzak on 3 Nov 2017

Given this is like a season old I don't still have the project around in that state, but my gemfile at the time was what was linked.

mike-bailey picture mike-bailey on 3 Nov 2017

@zzak lockfile from my latest project.
https://github.com/frankymad/sinatra-datamapper-sample/blob/master/lockfile

frankymad picture frankymad on 12 Nov 2017

@zzak, thank you for wanting to help, my lockfile: https://hastebin.com/raw/otihuqujib (hastebin because it's pretty long)

elisaado picture elisaado on 25 Nov 2017

I've also been having this exact issue! Has anyone yet found a resolution?

peterwdj picture peterwdj on 22 Dec 2017

This issue still hasn't been resolved? I currently have the same problem.

SirKeebz picture SirKeebz on 7 May 2018

@SirKeebz do you have a backtrace for this?

kgrz picture kgrz on 11 May 2018

I'm still getting this same issue - I'm trying to use sinatra (2.0.1) and data_mapper (1.2.0) - has there been any resolution yet?

lshep picture lshep on 19 Jun 2018

@lshep can you provide a Gemfile.lock and stack trace that reproduces the issue?

dentarg picture dentarg on 19 Jun 2018

So I don't have a Gemfile.lock. I'm admittedly am a notice trying to learn and work thought examples. I am working through
Just Do It Part I and made it through no problem but now when I am working through Just Do It Part II. I haven't installed any specific versions of gems so I assume I am running all the latest. But when I run 

> irb
irb(main):006:0> require './main'
Traceback (most recent call last):
       15: from /home/lori/.rbenv/versions/2.5.0/bin/irb:11:in `<main>'
       14: from (irb):6
       13: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
       12: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
       11: from /home/lori/learn-sinatra/JustDoIt/main.rb:2:in `<top (required)>'
       10: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        9: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        8: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems.rb:217:in `try_activate'
        7: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems.rb:224:in `rescue in try_activate'
        6: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:1439:in `activate'
        5: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:1457:in `activate_dependencies'
        4: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:1457:in `each'
        3: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:1471:in `block in activate_dependencies'
        2: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:1437:in `activate'
        1: from /home/lori/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/specification.rb:2324:in `raise_if_conflicts'
Gem::ConflictError (Unable to activate dm-serializer-1.2.2, because json-2.1.0 conflicts with json (~> 1.6))
lshep picture lshep on 20 Jun 2018

@lshep I see

If you create Gemfile with the following content:

# frozen_string_literal: true

source "https://rubygems.org"

git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }

gem "sinatra"
gem "data_mapper"

and issue the commands

gem install bundler
bundle install

you will be able to run irb like this:

$ bundle exec irb
irb(main):001:0> require './main'
=> true

and main.rb like this:

bundle exec ruby main.rb
dentarg picture dentarg on 20 Jun 2018
👍4 🚀2

I get the same error but the following is the Gemfile.lock that was produced:

JustDoIt$ cat Gemfile.lock 
GEM
  remote: https://rubygems.org/
  specs:
    addressable (2.5.2)
      public_suffix (>= 2.0.2, < 4.0)
    bcrypt (3.1.12)
    bcrypt-ruby (3.1.5)
      bcrypt (>= 3.1.3)
    data_mapper (1.2.0)
      dm-aggregates (~> 1.2.0)
      dm-constraints (~> 1.2.0)
      dm-core (~> 1.2.0)
      dm-migrations (~> 1.2.0)
      dm-serializer (~> 1.2.0)
      dm-timestamps (~> 1.2.0)
      dm-transactions (~> 1.2.0)
      dm-types (~> 1.2.0)
      dm-validations (~> 1.2.0)
    dm-aggregates (1.2.0)
      dm-core (~> 1.2.0)
    dm-constraints (1.2.0)
      dm-core (~> 1.2.0)
    dm-core (1.2.1)
      addressable (~> 2.3)
    dm-migrations (1.2.0)
      dm-core (~> 1.2.0)
    dm-serializer (1.2.2)
      dm-core (~> 1.2.0)
      fastercsv (~> 1.5)
      json (~> 1.6)
      json_pure (~> 1.6)
      multi_json (~> 1.0)
    dm-timestamps (1.2.0)
      dm-core (~> 1.2.0)
    dm-transactions (1.2.0)
      dm-core (~> 1.2.0)
    dm-types (1.2.2)
      bcrypt-ruby (~> 3.0)
      dm-core (~> 1.2.0)
      fastercsv (~> 1.5)
      json (~> 1.6)
      multi_json (~> 1.0)
      stringex (~> 1.4)
      uuidtools (~> 2.1)
    dm-validations (1.2.0)
      dm-core (~> 1.2.0)
    fastercsv (1.5.5)
    json (1.8.6)
    json_pure (1.8.6)
    multi_json (1.13.1)
    mustermann (1.0.2)
    public_suffix (3.0.2)
    rack (2.0.5)
    rack-protection (2.0.3)
      rack
    sinatra (2.0.3)
      mustermann (~> 1.0)
      rack (~> 2.0)
      rack-protection (= 2.0.3)
      tilt (~> 2.0)
    slim (3.0.9)
      temple (>= 0.7.6, < 0.9)
      tilt (>= 1.3.3, < 2.1)
    stringex (1.5.1)
    temple (0.8.0)
    tilt (2.0.8)
    uuidtools (2.1.5)

PLATFORMS
  ruby

DEPENDENCIES
  data_mapper
  sinatra
  slim

BUNDLED WITH
   1.16.2
lshep picture lshep on 20 Jun 2018

I don't get any error with your Gemfile.lock, are you sure it is the same error? Please post all the commands and their output

dentarg picture dentarg on 20 Jun 2018

Nevermind - I had to add the dm-sqlite-adapter to the Gemfile and re install. @dentarg thank you for your assistance!

lshep picture lshep on 20 Jun 2018
👍1

For anyone who find this via google:

gem uninstall -Vax --force --no-abort-on-dependent json
# specify your desired json gem version in Gemfile
bundle install
sandstrom picture sandstrom on 21 Aug 2018

On Ubuntu 18.04 running Sinatra 2.0.4 navigate to:
/usr/lib/ruby/gems/2.5.0/specifications/default

Run:
sudo rm json-2.1.0.gemspec

This completely cleared the error:
Unable to activate dm-types-1.2.2, because json-2.1.0 conflicts with json (~> 1.6) (Gem::ConflictError)

m061l picture m061l on 11 Nov 2018
👍2

Apparently it is necessary to write this gem versions explicitly in the Gemfile and to use a config.ru to configure Rack. Smanezitec's solution with using Ruby 2.3.3 works fine for me:

My Gemfile:

source 'https://rubygems.org'

gem 'sinatra',            '1.4.8'
gem 'data_mapper',        '1.2.0'
gem 'dm-sqlite-adapter',  '1.2.0'
gem 'json',               '~>1.6'
gem 'shotgun',            '0.9.2'
gem 'slim',               '3.0.8'
gem 'thin',               '1.7.0'

my config.ru:

require 'rubygems'
require 'bundler'

Bundler.require

require './app'
run MiApp

my main.rb:

require 'sinatra'
require 'data_mapper'

# setup the database connection
DataMapper.setup(
  :default,
  ENV['DATABASE_URL'] || "sqlite3://#{Dir.pwd}/development.db"
)

# model definitions etc. placed here ...

# check the integrity of the models
DataMapper.finalize

class MiApp < Sinatra::Base
  get '/' do
    "Hello World!"
  end
end

How did you know which version numbers to use?

noahniuwa picture noahniuwa on 22 Feb 2019

I had this problem w/ ruby 2.6.3 and I just reverted to ruby 2.3.7

voodoologic picture voodoologic on 10 Jul 2019

Add require 'bundler/setup' to main.rb.

srgx picture srgx on 11 Oct 2019
👍1

I solved this issue by:
gem 'json', '~> 1.6', '>= 1.6.7'

None of the solutions above worked for me. If i reverted to an earlier ruby version I had errors with openssl.

scanclini picture scanclini on 30 Dec 2019

Are contributors still looking at this? Tried multiple things in this thread to limited/no avail. Gonna work on getting a Lockfile or something.

mike-bailey picture mike-bailey on 8 Jan 2020

After trying to make myself useful, I've noticed data_mapper is archived, so presumably unmaintained. We're working on dropping DataMapper from our project at my company.

mike-bailey picture mike-bailey on 8 Jan 2020

I recently found this out as well. Sequel is alive and well. A Google group with the author in there. It's quite good. It needs a Dash library though.

daBee picture daBee on 8 Jan 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

aren55555 picture aren55555  路  7Comments
GCorbel picture GCorbel  路  7Comments
mediafinger picture mediafinger  路  7Comments
za3k picture za3k  路  5Comments
paulmenzel picture paulmenzel  路  4Comments