Kristoffer Carlsson
Kristoffer Carlsson
> The remaining regression is probably registry decompressing (which could be ignored for Pkg.status). Not true anymore due to the new status printing that shows outdated packages.
I think this can be closed now.
Just because there is nothing holding back a package doesn't mean that `up` will update it. That is because updating the package might cause other packages to downgrade. My guess...
I think a good compromise is that after `up` and there are packages that are still not at the latest version to show something (but maybe a bit terser) as...
https://github.com/JuliaLang/Pkg.jl/blob/423343402943074825392faa8b04a6d353204689/src/API.jl#L154
Don't you just have to generate a new key as described in https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?
From https://github.blog/2021-09-01-improving-git-protocol-security-github/ > If you’re using libgit2 or another piece of code using libssh2, we recommend you use libssh2 1.9.0 or newer and an ECDSA key, since it does not...
And you really need to use ssh, you cannot use https for the git remote?
That requires Julia 1.7.
So I just tried `dev`ing a private package on GitHub using Julia 1.6 with https and it didn't ask for any user/password and it worked fine so I guess that...