Registered package invisible?

               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.7.0-beta3.0 (2021-07-07)
 _/ |\__'_|_|_|\__'_|  |  release-1.7/e76c9dad42 (fork: 68 commits, 84 days)
|__/                   |

julia> add DataDrop
ERROR: syntax: extra token "DataDrop" after end of expression
Stacktrace:
 [1] top-level scope
   @ none:1

(@v1.7) pkg> add DataDrop
    Updating registry at `C:\Users\PetrKrysl\.julia\registries\General.toml`
ERROR: The following package names could not be resolved:
 * DataDrop (not found in project, manifest or registry)


julia>

Yet, I can install this package in 1.6.


(@v1.6) pkg> st
      Status `C:\Users\PetrKrysl\.julia\environments\v1.6\Project.toml`
  [aa547a04] DataDrop v0.1.0

(@v1.6) pkg>

Do different julia versions have different registries?

This is probably:

You can try removing the Pkg server registry and switching to the Git registry:

julia> import Pkg

julia> Pkg.Registry.rm("General")

julia> ENV["JULIA_PKG_SERVER"] = ""

julia> Pkg.Registry.add("General")
1 Like

I am seeing this problem six hours after the package has been registered. That seems excessive doesn’t it?

I’m experiencing it as well. 15-30 minutes would have been just ok; but 4-5h is a bit excessive :wink:

there have unfortunately been times the package servers have been several days behind! However my understanding is the infrastructure folks have been working hard on improving the reliability and speed of them, and hopefully those long delays will not be common.

2 Likes

Understood. BTW: the trick of @dilumaluthge above works.

1 Like