Package Details: nvidia-beta-dkms 565.57.01-1

Git Clone URL: https://aur.archlinux.org/nvidia-beta-dkms.git (read-only, click to copy)
Package Base: nvidia-beta-dkms
Description: NVIDIA kernel modules - module sources (beta version)
Upstream URL: https://www.nvidia.com/
Licenses: LicenseRef-custom
Conflicts: nvidia, nvidia-dkms
Provides: nvidia, nvidia-beta, nvidia-dkms, NVIDIA-MODULE
Submitter: alucryd
Maintainer: dbermond
Last Packager: dbermond
Votes: 69
Popularity: 0.80
First Submitted: 2013-03-12 11:21 (UTC)
Last Updated: 2024-11-08 20:51 (UTC)

Required by (41)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 24 Next › Last »

shoober420 commented on 2021-04-01 16:32 (UTC) (edited on 2021-04-01 16:36 (UTC) by shoober420)

Since there is only a single package here, shouldn’t the depends section be where it normally is, and not under the package section? Because it’s under package, there is no warning before building that the user cannot resolve “nvidia-utils-beta”. It should warn the user before executing makepkg that nvidia-utils-beta is required, not after the fact. I only see depends under the package section when there are multiple packages within the PKGBUILD, understandably.

dbermond commented on 2021-01-09 02:39 (UTC)

@DDoSolitary Ok, probably it makes sense to have it on conflicts. I have added it. Thanks.

DDoSolitary commented on 2020-12-21 22:09 (UTC) (edited on 2020-12-21 22:10 (UTC) by DDoSolitary)

@dbermond It makes sense, but I still think it should at least conflict with nvidia-dkms in addition to nvidia, becase 1) On a system with nvidia-dkms already installed, installing nvidia-beta-dkms will fail because nvidia-utils-beta conflicts with nvidia-utils, but nvidia-utils is required by nvidia-dkms. I have to uninstall nvidia-dkms manually instead of simply pressing a "Y" on conflict, which is a bit inconvenient. 2) nvidia-beta-dkms and nvidia-dkms will in fact conflict if the latter is updated but the former is not.

dbermond commented on 2020-12-21 22:01 (UTC)

@DDoSolitary And you can take a look at other -dkms packages of the official repositories. You'll see that almost all of them conflicts (when a conflict is applicable [when a base package is also available]) with the base package or with the base module, following the Wiki example (witch should be followed). nvidia-dkms and virtualbox-{guest,host}-dkms are the only ones that are different. This package follows the Wiki.

DDoSolitary commented on 2020-12-21 21:37 (UTC)

@dbermond It's just an example. You can take a look at the official extra/nvidia-dkms package, which doesn't conflicts with extra/nvidia.

dbermond commented on 2020-12-21 21:30 (UTC)

@DDoSolitary https://wiki.archlinux.org/index.php/DKMS_package_guidelines#PKGBUILD

DDoSolitary commented on 2020-12-21 08:59 (UTC)

I think it should conflicts with nvidia-dkms rather than nvidia

dbermond commented on 2020-11-28 16:41 (UTC)

@wden Fixed.

wden commented on 2020-11-28 16:38 (UTC) (edited on 2020-11-28 16:44 (UTC) by wden)

I'm getting the patch error with this new update.

==> Validating source files with sha256sums... NVIDIA-Linux-x86_64-455.45.01-no-compat32.run ... Passed 110-nvidia-change-dkms-conf.patch ... FAILED 120-nvidia-linux-rt-gift.patch ... Passed ==> ERROR: One or more files did not pass the validity check!

I don't use any tools, I manually git clone and makepkg.

dbermond commented on 2020-09-17 22:48 (UTC)

@Lunia Fixed.