Info about upcoming removal of packages in the General registry #65
Comments
|
@barche I recently verified that current QML master branch works on Julia v1.2 (at least for my projects and most of your examples), after carefully following all your instructions for JlQML. I understand that you'd like to have something more polished for a real release, but please don't let your promising work be shunted off to obscurity! |
|
Thanks for the kind words, but doing a release at this point won't help much, it will just fail the automated tests due to no binaries being available. Also, wow, that is one month ago already :) |
|
Well, then just disable the tests that would fail...Von meinem Samsung Gerät gesendet.
…-------- Ursprüngliche Nachricht --------
Von: Bart Janssens <[email protected]>
Datum: 06.10.19 22:18 (GMT+01:00)
An: "barche/QML.jl" <[email protected]>
Cc: Subscribed <[email protected]>
Betreff: Re: [barche/QML.jl] Info about upcoming removal of packages in the
General registry (#65)
Thanks for the kind words, but doing a release at this point won't help much, it will just fail the automated tests due to no binaries being available.
Also, wow, that is one month ago already :)
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#65",
"url": "#65",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
|
No, this isn't about any internal QML.jl tests, if I understand correctly there is now a standard test that does Pkg.add when you register or release a new version, and that would fail since a normal Pkg.add won't work yet (is this correct @KristofferC ?) |
|
Well, if I try to add QML to Julia 1.2 I get: But this should be easy to fix, or not? |
|
Ok tried to add QML#master, this worked when trying twice: So which test do expect to fail when creating a new version from master? |
|
Ok, precompile failed. How to fix that? |
|
Referring to issue #60 since this one is Julia-admin-created and closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As described in https://discourse.julialang.org/t/ann-plans-for-removing-packages-that-do-not-yet-support-1-0-from-the-general-registry/ we are planning on removing packages that do not support 1.0 from the General registry. This package has been detected to not support 1.0 and is thus slated to be removed. The removal of packages from the registry will happen approximately a month after this issue is open.
To transition to the new Pkg system using
Project.toml, see https://github.com/JuliaRegistries/Registrator.jl#transitioning-from-require-to-projecttoml.To then tag a new version of the package, see https://github.com/JuliaRegistries/Registrator.jl#via-the-github-app.
If you believe this package has erroneously been detected as not supporting 1.0 or have any other questions, don't hesitate to discuss it here or in the thread linked at the top of this post.
The text was updated successfully, but these errors were encountered: