On 08/03/2013 18:27, Matt Joyce wrote: > Ok, I really just do not get what on earth it thinks I'm doing wrong > here, trying to install java firstly the ebuild in portage it appears is > too old, it wants me to fetch a copy of 7u15 from a page that now only > has 7u17 on it so fail there no problem just update it surely can't be > that hard err right so created an up to date copy of the ebuild in my > overlay directory except it wont create the manifest repeatedly tells me > to put the file jre-7u17-linux-x64.tar.gz in /usr/portage/distfiles, > great ok so...
your tree is out of date, do a sync the tree closely tracks Oracle's latest mind-fuck-of-the-day-version-whatever-that-is, so syncing often becomes a must with their java > > zeus oracle-jre-bin # cp ~/Downloads/jre-7u17-linux-x64.tar.gz > /usr/portage/distfiles > zeus oracle-jre-bin # ebuild *.ebuild manifest > > !!! dev-java/oracle-jre-bin-1.7.0.17 has fetch restriction turned on. > !!! This probably means that this ebuild's files must be downloaded > !!! manually. See the comments in the ebuild for more information. > > * Please download 'jre-7u17-linux-x64.tar.gz' from: > * > 'http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html' > * and move it to '/usr/portage/distfiles' > !!! Fetch failed for jre-7u17-linux-i586.tar.gz, can't update Manifest > > Err confused repeat, same, redownload same, try again, at this point > starting to meet the definition of insanity as the result isn't changing > finally after the third time finally notice the last line properly, I've > been there dutifully doing as it told me and failed to realize the real > issue is that it wants the x86 version of the download as well. > > Next it will point you to a wrong URL asking you to download > UnlimitedJCEPolicyJDK7.zip the following URL is the correct one, ty google. > > http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html > > After adding that ebuild manifest should work and the ebuild merges fine. > > I could have just attached the updated one I guess but I havn't for two > reasons firstly I had already written half this post when I noticed what > the real problem was and secondly I felt there was likely to be more > value to others in sharing the experience than there would in simply > attaching the file, I guess similar potential little gotchas may exist > with other packages also. > > Real lesson here is probably pretty much read *ALL* the output and don't > make assumptions, but anyway if it saves someone else some frustration > this was worth typing out. > -- Alan McKinnon [email protected]
