Skip to content
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

[2.1.0~alpha] opam admin cache doesn't show the full url for some packages #4167

Closed
kit-ty-kate opened this issue Apr 30, 2020 · 2 comments · Fixed by #4193
Closed

[2.1.0~alpha] opam admin cache doesn't show the full url for some packages #4167

kit-ty-kate opened this issue Apr 30, 2020 · 2 comments · Fixed by #4193
Milestone

Comments

@kit-ty-kate
Copy link
Member

Using opam admin cache with opam master (3def1a6 with a few extra fixes) shows quite a lot of urls being replaced by (https://). For instance:

$ opam admin cache ~/.cache/opam
[...]
[graphics.4.06.1] synchronised (https://)
[pa_test.109.45.00] synchronised (https://ocaml.janestreet.com/ocaml-core/109.45.00/individual/pa_test-109.45.00.tar.gz)
[lablgtk3.0.beta2] synchronised (https://download.ocamlcore.org/lablgtk/Lablgtk3/3.0.beta2/lablgtk-3.0.beta2.tar.gz)
[alcotest.1.1.0] synchronised (https://)
[osx-acl.0.1.0] synchronised (https://github.com/dsheets/ocaml-osx-acl/archive/0.1.0.tar.gz)
[ppxx.1.1.0] synchronised (https://bitbucket.org/camlspotter/ppxx/get/1.1.0.tar.gz)
[jupyter-archimedes.2.3.2] synchronised (https://)
[...]

If this means that the archive has already been downloaded previously, could we get a more explicit log message?

@kit-ty-kate
Copy link
Member Author

kit-ty-kate commented Apr 30, 2020

When calling opam admin cache on an already populated cache, the synchronised (https://) appear everywhere. This was not the case in previous stable versions of opam.

@rjbou
Copy link
Collaborator

rjbou commented May 1, 2020

This message is wrongly not clear, as it is here to notify that the archive is already cached, but it makes me wonder if it should print a message when it is already cached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants