Compat issue with CSV 0.7 (again...)

[tlienart]

After #100, I assumed that it would be fine to have RDatasets 0.6.9 and CSV 0.7. It turns out that's not the case, I just tried in a fresh environment and:

] add RDatasets
] add CSV@0.7

gives the disappointing

ERROR: Unsatisfiable requirements detected for package DataFrames [a93c6f00]:
 DataFrames [a93c6f00] log:
 ├─possible versions are: [0.11.7, 0.12.0, 0.13.0-0.13.1, 0.14.0-0.14.1, 0.15.0-0.15.2, 0.16.0, 0.17.0-0.17.1, 0.18.0-0.18.4, 0.19.0-0.19.4, 0.20.0-0.20.2, 0.21.0-0.21.6] or uninstalled
 ├─restricted by compatibility requirements with RDatasets [ce6b1742] to versions: [0.13.0-0.13.1, 0.14.0-0.14.1, 0.15.0-0.15.2, 0.16.0, 0.17.0-0.17.1, 0.18.0-0.18.4, 0.19.0-0.19.4, 0.20.0-0.20.2, 0.21.0-0.21.6]
 │ └─RDatasets [ce6b1742] log:
 │   ├─possible versions are: [0.5.0, 0.6.0-0.6.9] or uninstalled
 │   ├─restricted to versions * by an explicit requirement, leaving only versions [0.5.0, 0.6.0-0.6.9]
 │   └─restricted by compatibility requirements with CSV [336ed68f] to versions: [0.5.0, 0.6.0-0.6.1] or uninstalled, leaving only versions: [0.5.0, 0.6.0-0.6.1]
 │     └─CSV [336ed68f] log:
 │       ├─possible versions are: [0.3.0-0.3.1, 0.4.0-0.4.3, 0.5.0-0.5.26, 0.6.0-0.6.2, 0.7.0-0.7.7] or uninstalled
 │       └─restricted to versions 0.7 by an explicit requirement, leaving only versions 0.7.0-0.7.7
 ├─restricted by compatibility requirements with CSV [336ed68f] to versions: 0.21.0-0.21.6
 │ └─CSV [336ed68f] log: see above
 └─restricted by compatibility requirements with RDatasets [ce6b1742] to versions: [0.13.0-0.13.1, 0.14.0-0.14.1, 0.15.0-0.15.2, 0.16.0, 0.17.0-0.17.1, 0.18.0-0.18.4] — no versions left
   └─RDatasets [ce6b1742] log: see above

while my current status is

(foobox) pkg> status
Status `~/Desktop/tjd/foobox/Project.toml`
  [336ed68f] CSV v0.6.2
  [ce6b1742] RDatasets v0.6.9

Not sure why it's blocked, I always find these compat clashes to be extremely painful to figure out.

[tlienart]

hmm it may be that my thought that #100 had indeed been tagged was just wrong... let's see if 483f070 fixes stuff..

[iblislin]

yeah, let's wait for the new tag

[tlienart]

ok it's fixed