|Summary:||New nvidia-settings as of 09192006|
|Product:||Gentoo Linux||Reporter:||Jonathan <jwagner95>|
|Component:||New packages||Assignee:||X11 External Driver Maintainers <x11-drivers>|
|Severity:||enhancement||CC:||agent_jdh, kanelxake, maxima.bugs, thomas.kear, thothonegan|
|Package list:||Runtime testing required:||---|
|Bug Depends on:||148670|
|Attachments:||Ebuild for nvidia-settings-1.0 from 09/19/2006|
Description Jonathan 2006-09-23 15:30:00 UTC
There is a new version of nvidia-settings out. One issue may be that this one is called nvidia-settings.1.0 rather than the usual nvidia-settings.1.0.<dateOfRelease> which may cause some issues with an emerge --update world.
Comment 1 Jonathan 2006-09-23 15:33:47 UTC
Created attachment 97898 [details] Ebuild for nvidia-settings-1.0 from 09/19/2006 I'm attaching an ebuild based on the nvidia-settings-1.0.20060516-r1. Changed the SRC_URI to nvidia's server since the packages obviously isn't in portage yet.
Comment 2 Jakub Moc (RETIRED) 2006-09-26 00:19:50 UTC
*** Bug 149133 has been marked as a duplicate of this bug. ***
Comment 3 Jonathan Heaney 2006-09-29 05:47:00 UTC
Should be pointed out this only works with the new nvidia 9-series beta drivers that are masked - it doesn't work at all with the current 8-series drivers.
Comment 4 adam 2006-09-29 20:24:17 UTC
I hope soon this will hit portage. The new version has features that I can really use right now.
Comment 5 adam 2006-10-01 08:19:05 UTC
Better yet, is there a reason why an updated ebuild for it has not hit portage yet?
Comment 6 adam 2006-10-01 08:23:51 UTC
>>> Downloading 'http://distfiles.gentoo.org/distfiles/nvidia-settings-1.0.20060 919.tar.gz' --08:22:11-- http://distfiles.gentoo.org/distfiles/nvidia-settings-1.0.20060919 .tar.gz => `/usr/portage/distfiles/nvidia-settings-1.0.20060919.tar.gz' Resolving distfiles.gentoo.org... 22.214.171.124, 126.96.36.199, 188.8.131.52, . .. Connecting to distfiles.gentoo.org|184.108.40.206|:80... connected. HTTP request sent, awaiting response... 404 Not Found 08:22:11 ERROR 404: Not Found. No digest file available and download failed. >>> Downloading 'http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfi les/nvidia-settings-1.0.20060919.tar.gz' --08:22:11-- http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles /nvidia-settings-1.0.20060919.tar.gz => `/usr/portage/distfiles/nvidia-settings-1.0.20060919.tar.gz' Resolving distro.ibiblio.org... 220.127.116.11 Connecting to distro.ibiblio.org|18.104.22.168|:80... connected. HTTP request sent, awaiting response... 404 Not Found 08:22:12 ERROR 404: Not Found. No digest file available and download failed. >>> Downloading 'ftp://download.nvidia.com/XFree86/nvidia-settings/nvidia-settin gs-1.0.20060919.tar.gz' --08:22:12-- ftp://download.nvidia.com/XFree86/nvidia-settings/nvidia-settings- 1.0.20060919.tar.gz => `/usr/portage/distfiles/nvidia-settings-1.0.20060919.tar.gz' Resolving download.nvidia.com... 22.214.171.124, 126.96.36.199, 188.8.131.52 Connecting to download.nvidia.com|184.108.40.206|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /XFree86/nvidia-settings ... done. ==> PASV ... done. ==> RETR nvidia-settings-1.0.20060919.tar.gz ... No such file `nvidia-settings-1.0.20060919.tar.gz'. No digest file available and download failed. !!! Couldn't download 'nvidia-settings-1.0.20060919.tar.gz'. Aborting. Now I see why.
Comment 7 adam 2006-10-01 08:30:21 UTC
Fixed the issue with it not able to download the nvidia src. Edit the ebuild and change the SRC link to ftp://download.nvidia.com/XFree86/nvidia-settings/nvidia-settings-1.0.tar.gz And it shall download and install perfectly fine now.
Comment 8 Jonathan 2006-10-01 12:35:35 UTC
Sorry, I had just named the ebuild nvidia-settings-1.0.ebuild which worked fine. If it is named nvidia-settings-1.0.20060919 or whatever, then it will not work. In the past, I believe the files were copied to portage's distfiles and renamed appropriately with the date.
Comment 9 Jonathan Heaney 2006-10-01 13:52:38 UTC
(In reply to comment #8) > Sorry, I had just named the ebuild nvidia-settings-1.0.ebuild which worked > fine. If it is named nvidia-settings-1.0.20060919 or whatever, then it will > not work. In the past, I believe the files were copied to portage's distfiles > and renamed appropriately with the date. > The file for earlier versions were actually dated on nvidia's ftp site. The latest version (i.e. the one being discussed here) is not dated. To get around the dating issue I've masked versions >1.0 so it only picks up this new ebuild form my overlay.
Comment 10 Jonathan 2006-10-01 16:29:34 UTC
(In reply to comment #9) > The file for earlier versions were actually dated on nvidia's ftp site. The > latest version (i.e. the one being discussed here) is not dated. > > To get around the dating issue I've masked versions >1.0 so it only picks up > this new ebuild form my overlay. > That's pretty much what I did as well.
Comment 11 Chris Gianelloni (RETIRED) 2006-10-06 11:39:21 UTC
I've added this to CVS, but it is masked since the appropriate nvidia-drivers are masked.
Comment 12 Jakub Moc (RETIRED) 2006-10-15 13:15:52 UTC
*** Bug 151499 has been marked as a duplicate of this bug. ***
Comment 13 Xake 2006-10-15 13:28:46 UTC
This bug says "new since 09/19/2006" while their ftp says "File: nvidia-settings-1.0.tar.gz 1268 KB _2006-09-25_ 17:10:00" How come? And why add a date to the ebuild the source-file does not have? It is only confusing. If this is your way to deal with the versioning problem not much unlike the one wine have had, then I hope for your sake that the 1.0.*-branch does not go on for too long, becouse as I said: confusing. (Not to talk about how a possible 1.0.1, 1.0.2, 1.0.3 will be named. Append date to that?)