You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a local registry where I develop my packages, accessible to only a few people but then when I want to share it more globally in my organization, I need to register them on a more public registry.
In the end, I have on my side the two registries set up, but both of them should have all of the versions available.
Right now (it's the first time I get the issue) Pkg complains that ERROR: hash mismatch in registries for <package name> at version <x.y.z>.
And indeed the two hashes for this version of the package in both registries are different, so I'm guessing each call to register hashes either time information or registry information, leading to this mismatch.
I'm wondering if it is malpractice to register the same version of a package on two registries, or if it is a missing way to register on multiple registries at the same time.
The text was updated successfully, but these errors were encountered:
Ah, that is indeed much more likely that I registered at two different commits. I don't know why but for some reason I thought it only accounted for the commit where the Project.toml version is modified. Thanks for the help !
Hi, I have a local registry where I develop my packages, accessible to only a few people but then when I want to share it more globally in my organization, I need to register them on a more public registry.
In the end, I have on my side the two registries set up, but both of them should have all of the versions available.
Right now (it's the first time I get the issue)
Pkg
complains thatERROR: hash mismatch in registries for <package name> at version <x.y.z>
.And indeed the two hashes for this version of the package in both registries are different, so I'm guessing each call to
register
hashes either time information or registry information, leading to this mismatch.I'm wondering if it is malpractice to register the same version of a package on two registries, or if it is a missing way to
register
on multiple registries at the same time.The text was updated successfully, but these errors were encountered: