Bug 222217

Summary:	x11-drivers/nvidia-drivers-173.08 places modules.d file in modprobe.d
Product:	Gentoo Linux	Reporter:	Brian Johnson <gentoo-bugzilla>
Component:	New packages	Assignee:	Tony Vroon (RETIRED) <chainsaw>
Status:	RESOLVED INVALID
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Brian Johnson 2008-05-15 07:30:55 UTC

After installing nvidia-drivers-173.08, I noticed that a file in /etc/modprobe.d/nvidia had been created. Since I was upgrading from 169.12, which had the file in /etc/modules.d/nvidia it left the old file and created a duplicate in /etc/modprobe.d/.

Reproducible: Always

Steps to Reproduce:
1. emerge =x11-drivers/nvidia-drivers-173.08
Actual Results:  
A "nvidia" file is created in /etc/modprobe.d/ and not merged into the usual /etc/modules.d/ (thus etc-updeate doesn't function)

Expected Results:  
The nvidia should have been merged into /etc/modules.d/. etc-update should have kicked in and informed the user that a config is waiting to be merged.

To fix, remove /etc/modprobe.d/nvidia and update-modules.

Comment 1 Tony Vroon (RETIRED) gentoo-dev

2008-05-15 10:00:17 UTC

Portage does not support doing this in a meaningful way. Delete the old file manually.

Comment 2 Brian Johnson 2008-05-15 15:28:59 UTC

Saw this in the ebuild for nvidia-drivers-173.08:

                # Add the aliases
                [ -f "${FILESDIR}/nvidia" ] || die "nvidia missing in FILESDIR"
                sed -e 's:PACKAGE:'${PF}':g' \
                        -e 's:VIDEOGID:'${VIDEOGROUP}':' "${FILESDIR}"/nvidia-169.07 > \
                        "${WORKDIR}"/nvidia
                insinto /etc/modprobe.d
                doins "${WORKDIR}"/nvidia || die


Can we get that changed to /etc/modules.d/ ?

Comment 3 Tony Vroon (RETIRED) gentoo-dev

2008-05-15 16:12:39 UTC

No, we can not. /etc/modules.d is an invalid and deprecated location that should not be used. /etc/modprobe.d is the correct location, and this is expected behaviour.

Comment 4 Brian Johnson 2008-05-15 17:36:53 UTC

I have a relatively ~arch system and there is only one file in /etc/modprobe.d/. Perhaps it's worth informing users of this change as there are several other files in my /etc/modules.d/ (alsa, etc...). Should we continue to half-support /etc/modules.d/ it will likely break future programs (alsa-conf, etc.)

Marking as INVALID as the bug was originally invalid.