-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
switching registration system #798
Comments
|
@RalphAS installed the new Registrator, so you should be able to do it now. |
Looks like the new Registrator isn't compatible with the old one. Once the upstream dependency tagged a new release, there would be version conflict in the downstream unless explicitly specifying a old version. For example, I've released an ImageMorphology v0.2.0 using the new Registrator, (the same to (v1.1) pkg> activate .
(tmp) pkg> add ImageMorphology
Updating registry at `~/.julia/registries/General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
Resolving package versions...
Updating `~/tmp/Project.toml`
[787d08f9] + ImageMorphology v0.2.0
Updating `~/tmp/Manifest.toml`
...
(tmp) pkg> add ImageInpainting
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package ImageMorphology [787d08f9]:
ImageMorphology [787d08f9] log:
├─possible versions are: [0.0.1-0.0.2, 0.1.0-0.1.1, 0.2.0] or uninstalled
├─restricted to versions 0.2.0 by an explicit requirement, leaving only versions 0.2.0
└─restricted by compatibility requirements with ImageInpainting [2bcd8d84] to versions: [0.0.2, 0.1.0-0.1.1] — no versions left
└─ImageInpainting [2bcd8d84] log:
├─possible versions are: [0.0.1-0.0.2, 0.1.0] or uninstalled
└─restricted to versions * by an explicit requirement, leaving only versions [0.0.1-0.0.2, 0.1.0] repos that lack of
Are following repos deprecated, or are they just need someone to maintain? (they're not updated for at least two years) I can help to fill these
a small talk with @Evizero says once 1.0 works we can drop 0.7. I guess we only need at most three versions under CI test, i.e., 1.0 as LTS version, 1.1 as the latest release version, and nightly build which allows failure. |
JuliaImages/ImageCore.jl#71 (comment) Conclusion: set v0.7 incompatible when we drop the CI test for it.
JuliaImages/ImageView.jl#171 (comment) The answer is yes. |
There's a registrator bug for julia version compatibility The following package versions aren't compatible for julia version
(Possibly would be fixed in General in the future) |
A large part of the switching procedure is finished except |
Thanks so much @johnnychen94 for your steadfast stewardship of this transition! 🎆 |
I tried to upgrade
ImageMorphology
to support Julia v1.0 and v1.1 in JuliaImages/ImageMorphology.jl#14 and fix broken CI, also a releasev0.2.0
is published.But in Julia CLI it says no such release
Looks like it's because attobot is disabled according to switching package registration system, and we need a change from attobot to Registrator
And looks like installing new Registrator will be enough to fix this release failure, but this's out of my knowledge at present :(
cc: @timholy
The text was updated successfully, but these errors were encountered: