Top posting for obvious reasons. ;-) I was thinking it could be this but this is the first time I have ever ran into this with adobe-flash. I wanted to sort of check into it before doing anything that may cause "issues' such as just redoing the manifest. I did think about it tho.
Now to go redo the manifest and try to get it so that sites will work again. In ways flash is good but at times, I want to kick it in the family jewels. O_O Thanks. Dale :-) :-) William Kenworthy wrote: > I get this, commonly with adobe-flash and google-earth. I suspect that > they change the file content or dynamically regenerate it faster than > portage can track them/my local repos update. The only fix I have been > able to come up with is check as far as possible where the binary came > from and regenerate the manifest before emerging ... hardly secure. > > BillK > > > On Mon, 2012-06-11 at 05:54 -0500, Dale wrote: >> Howdy, >> >> I been trying to play around with versions of adobe-flash to see which >> version a) works and b) doesn't crash or cause other problems. Anyway, >> I was using one version, the 10 version, for a bit but am having issues >> so I wanted to try a newer version. It seems tho, no matter what >> version I want to try, I get messages similar to this: >> >> 2012-06-11 05:28:53 (292 MB/s) - >> `/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz' saved >> [6916648/6916648] >> >> !!! Fetched file: adobe-flash-11.2.202.235.i386.tar.gz VERIFY FAILED! >> !!! Reason: Filesize does not match recorded size >> !!! Got: 6916648 >> !!! Expected: 6916435 >> Refetching... File renamed to >> '/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz._checksum_failure_.8RQBX4' >> >> !!! Couldn't download 'adobe-flash-11.2.202.235.i386.tar.gz'. Aborting. >> * Fetch failed for 'www-plugins/adobe-flash-11.2.202.235', Log file: >> * '/var/tmp/portage/www-plugins/adobe-flash-11.2.202.235/temp/build.log' >> * >> >> >> The values change but the error is the same no matter what version I try >> to use. What I have tried so far: >> >> syncing the tree again. >> deleting the files in /usr/portage/www-plugins/adobe-flash/ >> deleting anything adobe in distfiles and in http-replicator. >> syncing the tree again. >> >> I still get the same error. >> >> Another thing I noticed. When I delete the adobe files in distfiles and >> try to emerge them, I get this on the tail end: >> >> 6750K .... 100% >> 189M=0.02s >> >> I have DSL here but to put it bluntly, it ain't nowhere near that fast. >> Heck, my hard drives ain't that fast. I run http-replicator but I also >> removed those files too so it is not coming from there. If it is not >> local, it can't download it that fast, where is it coming from? I only >> have one rig running locally, not that my network is that fast either. >> lol >> >> Is this just me or is anyone else having this issue? If it is just me, >> what else can I do to fix this? >> >> Thanks in advance. >> >> Dale >> >> :-) :-) >> -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
