#Errors installing Reactant
1 messages · Page 1 of 1 (latest)
It should include a message about entering err or running Pkg.precompile to get a better error message
Okay, do you get the same error if you run this?
using Pkg
Pkg.activate(; temp = true)
Pkg.add("Reactant_jll")
Pkg.precompile()
Hm interestingly not
Ugh ok ig I'll reconfig the environment and hope it works
Tyy
Ok after a bit more testing the problem comes from GNNLux
Sorry if I'm being stupid but why is GNNLux loading a very outdated version of GNNlib (0.x) when its Project.toml file says it's compatible with 1.x
It might be that a package that is already loaded prevents the newer compatibility requirements from being enfored
If you find the problematic package, you should be able to set a company bound that fixes your issue
Is there any way to check which package that might be without going through every Project.toml
It can be rather frustrating to do this though, but I've done it a few times
Sorry what's a company bound
Compat*
Auto correct
I'd start with the one that failed and work your way up to your full environment
So next, try reactant_jll and reactant
Write down the loaded versions and whether it works each time
Ok did a bit more digging and the minimal combination required to reproduce the error seems to be just having Reactant and GNNLux. One level deeper, the reason for the error is that GNNLux loads an outdated version of GNNlib; if I install just Reactant and the latest version of GNNlib, there is no error. Is there any way to either troubleshoot why GNNLux is loading an older version of GNNlib than it should or to force it to use the current version?
Try adding gnnlib as a dependency, move it's uuid to a section called [extras], then give it a compat bound for the version that works! I'd also check gnnlux to see what the current compat bound is and file an issue if it's incorrect
It's a bit more difficult to determine exactly why the wrong one is loaded. It's possible for an older version to be loaded before this new compat bound is known to the resolver, giving you a broken environment state. Given you reproduced with only 2 packages, this could only happen if your startup file loads packages or if you had loaded some packages before creating this new environment with gnnlux and gnnlib
Ugh ok found the problem! Fsr the latest version of GNNLux isn't reflected in the general package registry
When I added it directly from the package's Github repo it worked fine
Ty for your help :)
Cool! Is that version tagged? If it isn't, then it might not be "ready" for release. Either way, you should ask for them to register a release