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

Update auto-cpufreq-installer to update Suse support #808

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

CaffineAddic
Copy link
Contributor

Changed python38 to python3 to solve an install error and also python3-setuptools were causing a conflict using python311-setuptools ended up solving that install.

Solved failed installation on OpenSUSE systems.

Changed python38 to python3 to solve an install error and also python3-setuptools were causing a conflict using python311-setuptools ended up solving that install.
@CaffineAddic
Copy link
Contributor Author

image
Working Install proof, in case anyone wants to see

@AdnanHodzic AdnanHodzic changed the title Update auto-cpufreq-installer Update auto-cpufreq-installer to update Suse support Jan 15, 2025
@AdnanHodzic
Copy link
Owner

AdnanHodzic commented Jan 15, 2025

One small remark, can you please make a change to set python311-setuptools as python3-setuptools? As this way it won't be limited by particular Python version and will always get the latest, preventing the problem that occured in #805 from happening in future again.

@CaffineAddic
Copy link
Contributor Author

CaffineAddic commented Jan 15, 2025

Actually python3-setuptools are being maped to some old 54 version or something

the latest version available for OpenSUSE is available as python311-setuptools-75.6.0-2.2.noarch

If python3-setuptools were tried to be installed it caused a conflict and the installation setup to fail.

Problem: 1: the installed python311-setuptools-75.6.0-2.2.noarch obsoletes 'python3-setuptools < 75.6.0-2.2' provided by the to be installed python3-setuptools-57.0.0-1.55.noarch

@AdnanHodzic
Copy link
Owner

Clear, weird that Suse is doing it like that instead of linking python metapackage to its latest version.

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

Closes: #805

@AdnanHodzic AdnanHodzic merged commit db54ea3 into AdnanHodzic:master Jan 15, 2025
2 checks passed
@CaffineAddic
Copy link
Contributor Author

Thanks a bunch, if you have any specific things if you wanna delegate to me I would be happy to work on

@AdnanHodzic
Copy link
Owner

Thank, best thing to do is take a look at Looking for developers and co-maintainers section of README, or my latest comment in #312

@CaffineAddic
Copy link
Contributor Author

Oh I did, honestly it's my first time so starting on alone to develop a new part of this project would be a little daunting, I would feel more in line if you could just delegate some task with some tips on how would I go about completing it.

Sorry for being a little inflexible

@AdnanHodzic
Copy link
Owner

Sure, I can keep your name on when new issues come in, but there's a lot of existing open ones so please check if there's any interesting for you. In meantime I would recommend to subscribe to all auto-cpufreq issues so you're notified when there's a new one.

Also, please note just yesterday I released auto-cpufreq-genAI-chatbot and try to also use it for some things :)

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.

2 participants