That’s entirely the wrong way to go if you want to get JuliaDB installed on Julia 0.7 or 1.0. Instead you should do
pkg> dev NamedTuples
and then adding JuliaDB will go through. Not that either package can be expected to work though, rather the opposite. But you are in a better position to fix NamedTuples yourself.
More technically speaking, the latest version of JuliaDB, 0.8.5, has an upper bound on the compatibility with Julia itself, making it only installable on Julia 0.6. When you try to install it on 0.7, it will instead pick 0.8.4, which was released before the upper bound was introduced in the REQUIRE file. However, it depends on NamedTuples, which doesn’t work on 0.7 and also has received an upper bound. In the NamedTuples case, however, the upper bound was introduced in METADATA retroactively for all released versions, meaning no released version can be installed, and the attempt to install JuliaDB v0.8.4 failed because there was no way to satisfy the dependencies. This can be fooled by manually installing NamedTuples, either with develop NamedTuples or with add NamedTuples#master, both of which circumvent the Julia version requirements in METADATA. (And even more technically Pkg3 doesn’t look in METADATA but in a registry that mirrors METADATA, so the effect is the same.)
I’m not entirely convinced about the wisdom of retroactively upper-bounding all versions of NamedTuples without having a new version available that can be installed on Julia 0.7. It’s technically correct since it doesn’t work on 0.7 and very possibly never will, but the package manager doesn’t handle it gracefully enough at this time, as seen by this and quite a few other threads on discourse.
