The packages manager "yay" (command: yay -Syu --devel) always see a commit and it tries to update it even if there is no commit.
It's probably a mistake in the PKGBUILD see here: https://github.com/Jguer/yay/issues/691
Git Clone URL: | https://aur.archlinux.org/optimus-manager.git (read-only, click to copy) |
---|---|
Package Base: | optimus-manager |
Description: | Management utility to handle GPU switching for Optimus laptops |
Upstream URL: | https://github.com/Askannz/optimus-manager |
Licenses: | MIT |
Conflicts: | optimus-manager-git |
Provides: | optimus-manager |
Submitter: | Askannz |
Maintainer: | Askannz |
Last Packager: | Askannz |
Votes: | 124 |
Popularity: | 1.08 |
First Submitted: | 2018-11-17 05:42 (UTC) |
Last Updated: | 2023-07-29 00:30 (UTC) |
The packages manager "yay" (command: yay -Syu --devel) always see a commit and it tries to update it even if there is no commit.
It's probably a mistake in the PKGBUILD see here: https://github.com/Jguer/yay/issues/691
@ValHue @jpegxguy should be fixed in the new v0.4 release
@ValHue It needs this in the service file
[Install]
WantedBy=graphical.target
Add it with systemctl edit or edit the file directly because it will be there in the next release anyway. It's fixed in github master but not in 0.3
I will get an error when I run:
sudo systemctl enable optimus-manager.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
I've looked inside optimus-manager.service and I do not have the [Install] section, so I think that's where the error is.
Should we install it in another way?
I followed the instructions at https://github.com/Askannz/optimus-manager and I was unable to activate the service.
Thanks.
Thank you @coderobe, I fixed those issues.
There are a couple issues with your PKGBUILD:
You're not installing the license, which is a requirement for MIT-licensed projects
You're pulling git master HEAD on a regular versioned package - pin commits or tags, or rename the package to optimus-manager-git
You're depending on python3, use python instead
Renaming the source in source=() is redundant in your case
Your packaging functions don't follow the Python package guidelines (https://wiki.archlinux.org/index.php/Python_package_guidelines)
Could you please fix the aforementioned packaging issues?
Install and set up in 2 minutes. Huge performance improvement compared to Bumblebee (twice as much FPS in CSGO than before).
Pinned Comments
Askannz commented on 2023-06-18 07:37 (UTC)
Announcement about the current state of optimus-manager and the future of its development: https://github.com/Askannz/optimus-manager/issues/543