| 1 |
Top posting for obvious reasons. ;-) |
| 2 |
|
| 3 |
I was thinking it could be this but this is the first time I have ever |
| 4 |
ran into this with adobe-flash. I wanted to sort of check into it |
| 5 |
before doing anything that may cause "issues' such as just redoing the |
| 6 |
manifest. I did think about it tho. |
| 7 |
|
| 8 |
Now to go redo the manifest and try to get it so that sites will work |
| 9 |
again. In ways flash is good but at times, I want to kick it in the |
| 10 |
family jewels. O_O |
| 11 |
|
| 12 |
Thanks. |
| 13 |
|
| 14 |
Dale |
| 15 |
|
| 16 |
:-) :-) |
| 17 |
|
| 18 |
|
| 19 |
William Kenworthy wrote: |
| 20 |
> I get this, commonly with adobe-flash and google-earth. I suspect that |
| 21 |
> they change the file content or dynamically regenerate it faster than |
| 22 |
> portage can track them/my local repos update. The only fix I have been |
| 23 |
> able to come up with is check as far as possible where the binary came |
| 24 |
> from and regenerate the manifest before emerging ... hardly secure. |
| 25 |
> |
| 26 |
> BillK |
| 27 |
> |
| 28 |
> |
| 29 |
> On Mon, 2012-06-11 at 05:54 -0500, Dale wrote: |
| 30 |
>> Howdy, |
| 31 |
>> |
| 32 |
>> I been trying to play around with versions of adobe-flash to see which |
| 33 |
>> version a) works and b) doesn't crash or cause other problems. Anyway, |
| 34 |
>> I was using one version, the 10 version, for a bit but am having issues |
| 35 |
>> so I wanted to try a newer version. It seems tho, no matter what |
| 36 |
>> version I want to try, I get messages similar to this: |
| 37 |
>> |
| 38 |
>> 2012-06-11 05:28:53 (292 MB/s) - |
| 39 |
>> `/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz' saved |
| 40 |
>> [6916648/6916648] |
| 41 |
>> |
| 42 |
>> !!! Fetched file: adobe-flash-11.2.202.235.i386.tar.gz VERIFY FAILED! |
| 43 |
>> !!! Reason: Filesize does not match recorded size |
| 44 |
>> !!! Got: 6916648 |
| 45 |
>> !!! Expected: 6916435 |
| 46 |
>> Refetching... File renamed to |
| 47 |
>> '/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz._checksum_failure_.8RQBX4' |
| 48 |
>> |
| 49 |
>> !!! Couldn't download 'adobe-flash-11.2.202.235.i386.tar.gz'. Aborting. |
| 50 |
>> * Fetch failed for 'www-plugins/adobe-flash-11.2.202.235', Log file: |
| 51 |
>> * '/var/tmp/portage/www-plugins/adobe-flash-11.2.202.235/temp/build.log' |
| 52 |
>> * |
| 53 |
>> |
| 54 |
>> |
| 55 |
>> The values change but the error is the same no matter what version I try |
| 56 |
>> to use. What I have tried so far: |
| 57 |
>> |
| 58 |
>> syncing the tree again. |
| 59 |
>> deleting the files in /usr/portage/www-plugins/adobe-flash/ |
| 60 |
>> deleting anything adobe in distfiles and in http-replicator. |
| 61 |
>> syncing the tree again. |
| 62 |
>> |
| 63 |
>> I still get the same error. |
| 64 |
>> |
| 65 |
>> Another thing I noticed. When I delete the adobe files in distfiles and |
| 66 |
>> try to emerge them, I get this on the tail end: |
| 67 |
>> |
| 68 |
>> 6750K .... 100% |
| 69 |
>> 189M=0.02s |
| 70 |
>> |
| 71 |
>> I have DSL here but to put it bluntly, it ain't nowhere near that fast. |
| 72 |
>> Heck, my hard drives ain't that fast. I run http-replicator but I also |
| 73 |
>> removed those files too so it is not coming from there. If it is not |
| 74 |
>> local, it can't download it that fast, where is it coming from? I only |
| 75 |
>> have one rig running locally, not that my network is that fast either. |
| 76 |
>> lol |
| 77 |
>> |
| 78 |
>> Is this just me or is anyone else having this issue? If it is just me, |
| 79 |
>> what else can I do to fix this? |
| 80 |
>> |
| 81 |
>> Thanks in advance. |
| 82 |
>> |
| 83 |
>> Dale |
| 84 |
>> |
| 85 |
>> :-) :-) |
| 86 |
>> |
| 87 |
-- |
| 88 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
| 89 |
|
| 90 |
Miss the compile output? Hint: |
| 91 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives