search

JuliaRegistries / Registrator.jl

Julia package registration bot
https://julialang.org/packages
Other
210 stars 47 forks source link

Unable to register: version already exists #411

Open cadojo opened 1 year ago

cadojo commented 1 year ago

I made this issue at the General Registry, but I just found this project, and believe it is more appropriate here. I'm copying the original issue text below.

I have recently created two packages: HorizonsAPI, and HorizonsEphemeris. The HorizonsEphemeris package depends on HorizonsAPI. HorizonsAPI is in the queue for its first release in the General registry.

I tried to register HorizonsEphemeris today for the first time. Of course, this was rejected, since HorizonsAPI is still in the waiting period. To get HorizonsEphemeris in the queue, I removed its dependency on HorizonsAPI. I hoped to release this first version to claim the name, and release a minor patch which re-introduces the dependency on HorizonsAPI. When I tried to register HorizonsEphemeris for 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 HorizonsEphemeris as registered, despite the name not existing in the General registry.

This is not a big issue for me — I can just release my first HorizonsEphemeris version as v0.1.1 after HorizonsAPI is merged into the General registry. I wanted to make known this bad state I somehow got the registrator bot in.

JuliaRegistrator commented 1 year ago

Error while trying to register: Action not recognized: in

Seelengrab commented 1 year ago

I've observed the same issue here.

The circumstances are identical - I first tried to register SVD2Julia.jl last week and forgot that one of its dependencies was still not registered. That dependency is now registered, but trying to register SVD2Julia.jl now fails with the same error as reported above.

An initial investigation in Slack yielded a possible cause; stale branches in the local clone of the registry, which don't seem to get cleaned up here. I think that return path should clean up the stale registration branch?