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

fix dubious ownership error in auto-cpufreq-installer #597

Merged
merged 1 commit into from
Nov 12, 2023
Merged

fix dubious ownership error in auto-cpufreq-installer #597

merged 1 commit into from
Nov 12, 2023

Conversation

amogus07
Copy link
Contributor

When trying to install auto-cpufreq in Fedora 39, I got the following error:

Detected Git repository, but failed because of dubious ownership

Adding the line at the top of the install function according to https://sam.hooke.me/note/2023/08/poetry-fixing-dubious-ownership-error/ solved the error for me.

When trying to install auto-cpufreq in Fedora 39, I got the following error: "Detected Git repository, but failed because of dubious ownership"
Adding the line at the top of the install function according to https://sam.hooke.me/note/2023/08/poetry-fixing-dubious-ownership-error/ solved the error for me.
@AdnanHodzic AdnanHodzic merged commit 15c17fc into AdnanHodzic:master Nov 12, 2023
@AdnanHodzic
Copy link
Owner

LGTM, thank you for your contribution, you will be credited for your work as part of future release.

Also it seems that this PR closes #595

shadeyg56 pushed a commit to shadeyg56/auto-cpufreq that referenced this pull request Feb 12, 2024
When trying to install auto-cpufreq in Fedora 39, I got the following error: "Detected Git repository, but failed because of dubious ownership"
Adding the line at the top of the install function according to https://sam.hooke.me/note/2023/08/poetry-fixing-dubious-ownership-error/ solved the error for me.
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 this pull request may close these issues.

None yet

2 participants