Closed Khady closed 1 month ago
Will be fixed by https://github.com/ocaml/opam/pull/5999
In the meantime, i believe that if you add --readonly
to your opam show
invocation it should now work fine without waiting for the lock.
are there cases when opam show is not readonly?
Yes, for example, if the internal repository data cache (marshalled data) isn't up-to-date or has been removed, opam will try to save that file by default
information messages such as "Another process has locked" and "lock acquired" should be printed on stderr, not stdout, as they aren't really part of the output of a command.
An example where we caught the problem
Can end up being executed as
This is true for lock messages but probably also applied to other informational messages.