Incompatibilities with ruby-json =>2.0
Bug #1666988 reported by
Unit 193
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-simplecov (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
ruby-simplesov's spec lists "~> 1.8", while Zesty (and Yakkety) contain ruby-json 2.0, this leads to an error such as: You have already activated json 2.0.1, but your Gemfile requires json 1.8.3. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
Of course, an even better solution would be to update the package, but since it's after feature freeze I went with a minimal approach.
Changed in ruby-simplecov (Ubuntu): | |
importance: | Undecided → Low |
To post a comment you must log in.
Thank you for the debdiff. Are you prepared to maintain this delta until we're in sync again please? Or is this package completely broken as-is - I can't tell from your bug description?
> Of course, an even better solution would be to update the package, but since it's after feature freeze I went with a minimal approach.
As we're in sync at the moment, is there a bug filed in Debian for this please?
> +ruby-simplecov (0.11.1-1ubuntu1) devel; urgency=medium
Shouldn't this be "zesty", or is there some magic in interpreting "devel" I don't know about?
+ * d/p/newer_ json.patch: Relax json dep to allow newer versions.
This should close this bug with "(LP: #1666988)".
+ rm -f metadata.yml
What's this for, please? Shouldn't it be mentioned in debian/changelog?