| View previous topic :: View next topic |
| Author |
Message |
johnhringiv
n00b
Joined: 15 Mar 2018
Posts: 9
|
 Posted: Sat Mar 17, 2018 7:59 pm Post subject: cudnn bug? |
 |
|
When I try to emerge dev-libs/cudnn I get the following error:
| Code: | Fetch instructions for dev-libs/cudnn-7.0.5-r1:
* The following files cannot be fetched for cudnn:
* cudnn-9.1-linux-x64-v7.tgz
|
It appears that the URL in the ebuild is incorrect. I'd like someone to help confirm that the error's not on my end if possible before I go ahead with a bug report.
Edit: The issue can be worked around by going to https://developer.nvidia.com/rdp/cudnn-download downloading the required file and copying it to /usr/portage/distfiles
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22930
|
| Posted: Sat Mar 17, 2018 8:50 pm Post subject: |
|
|
I only see a HOMEPAGE URL in the ebuild. What do you believe is wrong here?- You expected the ebuild to fetch automatically. This is disallowed explicitly, presumably because nVidia prohibits unattended fetches by trapping the files behind a badly written survey. This can be fixed by getting nVidia to permit unattended fetches, at which point the ebuild can do the work for you. Currently, for no good technical reason, nVidia disallows this.
- You expected the ebuild to give an exact download URL suitable for pasting into wget. This is probably absent for the same reason as #1. Both commonly happen when the upstream provider insists on silly "clickwrap" licenses. Generally, such ebuilds should be evicted from the tree until upstream comes to their senses, but some users expect to have access to them.
- You expected the ebuild to give any useful URL without requiring you to read the ebuild. I agree this would be a nice improvement.
- You expected the provided URL to point to a page from which you can more readily get the required file. This would also be nice, but is not possible with some upstreams that frequently rearrange their sites. I do not know if nVidia is such an upstream.
|
|
| Back to top |
|
|
johnhringiv
n00b
Joined: 15 Mar 2018
Posts: 9
|
| Posted: Sat Mar 17, 2018 10:22 pm Post subject: |
|
|
| Thank you for your response. Due to my inexperience I did not immediately recognize that everything was working as expected, although I should have guessed as much after having to login to Nvidia. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22930
|
| Posted: Sat Mar 17, 2018 10:30 pm Post subject: |
|
|
Everything might be overstating it a bit.  It would be nice if the ebuild had a pkg_nofetch function that would explain more precisely what is expected of you: where to go (the page where nVidia asks you to complete the survey) and a short summary of what you will be expected to provide to nVidia (so you can decide up front if this is worth your time). |
|
| Back to top |
|
|
johnhringiv
n00b
Joined: 15 Mar 2018
Posts: 9
|
| Posted: Sat Mar 17, 2018 10:41 pm Post subject: |
|
|
| That's a great idea. I'm currently working though the dev manual (I see there's a page on pkg_nofetch) as there's a couple of packages I'd like to write ebuilds for. After I learn some more I'll see what I can do about contributing that change. |
|
| Back to top |
|
|
|
Portage & Programming
