I'm running low on HD space, so I decided to symlink my UrbanTerror32.zip to /usr/portage/distfiles/UrbanTerror32.zip Portage reportated that it wasn't there. and I had to move the files to distfiles.... I checked the permissions, owned by root and readable by root games-fps/quake3-urbanterror-3.2 was What I was trying I didn't see any code in the ebuild that looked like it would cause this, I did see another bug about portage not using symlinked config files, but I think this is different... enough... and of course bugzilla doesn't search closed bugs take a look at: Bugzilla Bug 13007 Reproducible: Didn't try Steps to Reproduce: 1. 2.have a file symlinked to /usr/portage/distfiles 3.emerge the thing 4. fetch restrictions warning pops up.. 5... comment out src_uri and restrictions... 6.. it works!? 7... no. (I did have one file there, and it extracted) >>> emerge (1 of 1) games-fps/quake3-urbanterror-3.2 to / >>> Unpacking source... >>> Unpacking urbanterror3.zip to /var/tmp/portage/quake3-urbanterror-3.2/work >>> Unpacking UrbanTerror31.zip to /var/tmp/portage/quake3-urbanterror-3.2/work/q3ut3 unzip: cannot find /usr/portage/distfiles/UrbanTerror31.zip, /usr/portage/distfiles/UrbanTerror31.zip.zip or /usr/portage/distfiles/UrbanTerror31.zip.ZIP. !!! ERROR: games-fps/quake3-urbanterror-3.2 failed. !!! Function unpack, Line 331, Exitcode 9 !!! failure unpacking UrbanTerror31.zip
weird, i just did this: emerge -f nvidia-kernel cd /usr/portage/distfiles mv NVIDIA-Linux-x86-1.0-5336-pkg1.run / ln -s /NVIDIA-Linux-x86-1.0-5336-pkg1.run NVIDIA-Linux-x86-1.0-5336-pkg1.run emerge -f nvidia-kernel and it worked fine ... perhaps your soft link was screwed up ? :x
Hmm, the MD5 check should have failed if it is really a problem. We need `emerge info`, `ls -l /full/path/to/UrbanTerror31.zip` and `ls -l /usr/portage/distfiles/UrbanTerror31.zip`
I just cleared diskspace and copied it there, then I believe I tried it on something else and it worked. so... not much choice but to close it.
I've had this problem before as well, but I found out the reason. If the file that is being symlinked is inaccessible to user 'portage' (for example, user 'portage' does not have read access to some parent directory containing the symlinked file), then portage reports this problem. To solve the problem, move the symlinked file to some folder accessible to user 'portage'.
