FRBNY-DSGE/SMC.jl

error precompiling SMC

Closed this issue · 7 comments

I get the following error when I'm trying to precompile the package. I get the same message in 0.7, 1.1, 1.2. Running instantiate doesn't help.

LoadError: ArgumentError: Package SMC [c6043b28-c053-11e9-348c-19d3cb73bbb3] is required but does not seem to be installed:

  • Run Pkg.instantiate() to install all recorded dependencies.

Hi! To narrow down the issue, what is returned when you type Base.identify_package("SMC") into the REPL?

Thanks for the quick response!
I get this: SMC [c6043b28-c053-11e9-348c-19d3cb73bbb3]

Hello again! From searching Julia discourse, it appears this error might be related to SMC.jl's recent licensing as an official Julia package. For now, try a clean deletion and re-installation:

  1. julia>] rm SMC
  2. Then, (as we've historically had issues with re-adding packages after deleting them), delete the physical package (likely located in ~/.julia/packages/SMC).
  3. julia>] add SMC

Should this not work, try repeating (1-2) and adding the package back with the following:
3. julia> Pkg.add(PackageSpec(url = "https://github.com/FRBNY-DSGE/SMC.jl.git"))

If neither of the above works, could you share what is returned by typing julia>] status?

Hi!! I've tried removing the package (and even the entire ~/.Julia/ directory) and I'm still getting the same error.

When I add the package instead using
]add https://github.com/FRBNY-DSGE/SMC.jl.git
I get a series of
WARNING: replacing module SMC.
followed by
ERROR: Package SMC errored during testing

To keep you in the loop, we have managed to replicate the error, and will get back to you once we determine how to resolve it!

Hi,
We've fixed the problem (Linux respects that files with the same name but different capitalizations are different files, however Mac and Windows don't) on master.

If you pull from master of both SMC.jl and ModelConstructors.jl, hopefully everything should work for you now. We should have tagged releases of both within the next day.

Updating to v0.1.4 seems to fix the problem. Thank you!