Unable to register: Version v0.1.0 already exists #81954
Comments
nkottary
added a commit
to nkottary/RegistryTools.jl
that referenced
this issue
May 3, 2023
- When the registration server crashes abruptly it can sometimes leave behind untracked files from a previous registration. This can cause issues like JuliaRegistries/General#81954. Here I added a `git clean -fd` before checkout so that untracked files will be cleaned. - Added `-q --depth=1` to `git clone`s so that cloning will be faster and quieter in the logs.
nkottary
added a commit
to JuliaRegistries/RegistryTools.jl
that referenced
this issue
May 3, 2023
…nes (#91) * Use git clean to remove untracked files; shallow clone for faster clones - When the registration server crashes abruptly it can sometimes leave behind untracked files from a previous registration. This can cause issues like JuliaRegistries/General#81954. Here I added a `git clean -fd` before checkout so that untracked files will be cleaned. - Added `-q --depth=1` to `git clone`s so that cloning will be faster and quieter in the logs. * Update Project.toml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have recently created two packages:
HorizonsAPI, andHorizonsEphemeris. TheHorizonsEphemerispackage depends onHorizonsAPI.HorizonsAPIis in the queue for its first release in the General registry.I tried to register
HorizonsEphemeristoday for the first time. Of course, this was rejected, sinceHorizonsAPIis still in the waiting period. To getHorizonsEphemerisin the queue, I removed its dependency onHorizonsAPI. I hoped to release this first version to claim the name, and release a minor patch which re-introduces the dependency onHorizonsAPI. When I tried to registerHorizonsEphemerisfor the second time, I got an error stating "v0.1.0 already exists".It seems that I got the @JuliaRegistrator in a bad state by trying to register a package which has a private dependency. Somehow, the registrator bot now recognizes
HorizonsEphemerisas registered, despite the name not existing in the General registry.This is not a big issue for me — I can just release my first
HorizonsEphemerisversion asv0.1.1afterHorizonsAPIis merged into the General registry. I wanted to make known this bad state I somehow got the registrator bot in.The text was updated successfully, but these errors were encountered: