Whoops, I meant to ask if there was an issue in SQLite.jl, or if I was doing something wrong. I edited my question to make that distinction more clear, thanks. Now that you mention it, the issue might be in Pkg3 but my gut feeling is that the error is in SQLite.jl’s packaging.
SQLite.jl uses the Missings packages, but doesn’t have it in the REQUIRE file. In 0.6 this doesn’t cause a problem if you have Missings installed, but in 0.7 the package system is stricter about enforcing it.
If they add Missings to the REQUIRE file and release a new version, it will get synced to the 0.7 registry and should work.
Ok, I appended Missings to the REQUIRE file and previous error seems to be resolved. But now Pkg3 is making the same complaint about Compat. I appended Compat to REQUIRE the same way I appended Missings, but the error persists.
It is difficult to find documentation on this, so I’m just assuming that REQUIRE was used before 0.7 and Project.toml is the specification that will replace it. Maybe Pkg3 is looking for REQUIRE if it doesn’t see a Project.toml before we move on to 1.0?
In any case: all the packages specified in either REQUIRE or Project.toml should be pulled in before the build phase begins, correct? If that assumption is correct, then there should be no reason why Julia should complain of a missing Compat.
My process:
git clone my fork of SQLite.jl
append Missings and append Compat to REQUIRE
open up a Pkg3 REPL in the SQLite.jl directory
run add .
result: the build.log file says “Module Compat not found in current path”