-
Notifications
You must be signed in to change notification settings - Fork 28
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
On Fedora depext always asks for sudo password #131
Comments
I think I just got bit by this same issue when building Tezos on a computer running Fedora. |
To check installed package, it first done using
What doesn't work? opam install (see test guide), or depext handling on fedora doesn't work at all ? If you can open an issue in opam bugtracker it is very helpful for us. |
I am not OP, but just to add some information. This is from a coworker's computer, which runs Fedora 33, and opam 2.0.6. Output from this command:
is:
As you can see, it asks permission when running the install commands, and that works. But the commands do nothing because the packages are already installed, it is just that I have never used Fedora myself, so I don't really know what the problem is exactly or how to solve it, posting the above in case it may be useful. |
Although all required packages are installed, on Fedora it still asks for the sudo password, because it falsely claims
package pkgconfig is not installed
and then starts ayum -y update
. Later it verifies correctly with therpm -q --whatprovides pkgconfig
command, but does it falsely with sudo again, which is not required for this command. See output below.The correct way would be to test from the beginning with running
rpm -q --whatprovides pkgconfig
without sudo and only if that fails to execute commands with sudo.I know this code goes into opam itself, but I tried it the beta and it doesn't work at all there, so I can't verify the behavior there, and I want to document the problem at least here.
Output of
opam depext --yes --update keyfender conf-jq
(click to expand)The text was updated successfully, but these errors were encountered: