Package Details: optimus-manager-git 4:0-1

Git Clone URL: https://aur.archlinux.org/optimus-manager-git.git (read-only, click to copy)
Package Base: optimus-manager-git
Description: Allows using Nvidia Optimus laptop graphics
Upstream URL: https://github.com/Askannz/optimus-manager
Licenses: MIT
Conflicts: bumblebee, envycontrol, nvidia-exec, nvidia-switch, nvidia-xrun, optimus-manager, switcheroo-control
Provides: optimus-manager
Submitter: dude
Maintainer: Askannz (es20490446e)
Last Packager: es20490446e
Votes: 136
Popularity: 0.82
First Submitted: 2019-01-20 22:11 (UTC)
Last Updated: 2025-07-31 23:14 (UTC)

Required by (4)

Sources (1)

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

es20490446e commented on 2025-07-31 23:17 (UTC)

Reverted the problematic versioning scheme.

username227 commented on 2025-07-31 21:34 (UTC)

Won't build. Something is wrong with the version in the latest changes:

packaging.version.InvalidVersion: Invalid version: 'r798.4dfecf3'
==> ERROR: A failure occurred in build().
    Aborting...

es20490446e commented on 2025-05-21 13:43 (UTC)

What happened is that I zeroed the pkgver, and AUR managers were using that.

I did so because the generated pkgver would be wrong when building the package from GitHub, when cloning only the last commit.

rcassani commented on 2025-05-21 12:09 (UTC)

@solarisfire, I think you're into something, but rather of pkgver, what it seems it was missing was bumping up pkgrel

es20490446e commented on 2025-05-20 15:03 (UTC)

Maybe AUR managers shall be doing a checksum of the "PKGBUILD" instead.

curl --silent https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=optimus-manager-git | sha1sum

solarisfire commented on 2025-05-20 14:03 (UTC) (edited on 2025-05-20 14:03 (UTC) by solarisfire)

I have a theory it's something to do with the way this "pkgver = 0" change to automate things works with package manager cache's.

They don't see number go up, so don't think they need to refresh their cache. Shouldn't be too big of a headache if users know to clear their cache to get the latest version.

rcassani commented on 2025-05-20 13:57 (UTC)

@es20490446e, @solarisfire Same thing happened with paru. After cleaning its cache everything worked fine

es20490446e commented on 2025-05-16 16:45 (UTC)

I would report this to yay developers.

solarisfire commented on 2025-05-16 14:06 (UTC) (edited on 2025-05-16 14:35 (UTC) by solarisfire)

Weird. This was during an update and I told it to clean build, so I wonder why the version I'm getting is outdated...

EDIT: Cleared the cache, and now it installs fine... No idea why yay wouldn't fetch the new PKGBUILD and just wanted to use it's cached version.

es20490446e commented on 2025-05-16 13:53 (UTC)

@solarisfire

You are using and old version of the PKGBUILD.

1 2 3 4 5 6 .. 14 Next › Last »