[gentoo-user] adobe-flash and constant errors.

[gentoo-user] adobe-flash and constant errors.

[Dale]

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"

Re: [gentoo-user] adobe-flash and constant errors.

[William Kenworthy]

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
> 
> :-)  :-)
> 

Re: [gentoo-user] adobe-flash and constant errors.

[Dale]

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"

Re: [gentoo-user] adobe-flash and constant errors.

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 3752 bytes --]

On Monday 11 Jun 2012 14:46:19 Dale wrote:
> 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_f
> >> ailure_.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?

Haven't tried the latest, but it has happened here too in the past.

I recall following pretty much what you've done to resolve this problem 
(except for the replicator thing).  I seem to recall that on one occasion I 
had to try again the next day to get it to work, because I did not want to 
risk it with manifest-ing a dodgy download.

I guess you could try downloading it manually directly from adobe?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] adobe-flash and constant errors.

[Dale]

Mick wrote:
> Haven't tried the latest, but it has happened here too in the past. I
> recall following pretty much what you've done to resolve this problem
> (except for the replicator thing). I seem to recall that on one
> occasion I had to try again the next day to get it to work, because I
> did not want to risk it with manifest-ing a dodgy download. I guess
> you could try downloading it manually directly from adobe? 

I watched the download, it came from adobe.  I wouldn't have done the
manifest thing if it came from anywhere else.  So far, I think the new
sources are working better.  It's not crashing/freezing so much.  I'm
not going to complain as long as it works.  lol

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"

Re: [gentoo-user] adobe-flash and constant errors.

[David Haller]

Hello,

On Mon, 11 Jun 2012, Dale wrote:
>`/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz' saved

11.2.202.235 crashes all the time anyway (at least on x86_64), there's
a new version 11.2.202.236 out since yesterday or so that works again.

HTH,
-dnh

-- 
The speed at which a mistyped command executes is directly proportional
to the amount of damage done.                               -- Joe Zeff

Re: [gentoo-user] adobe-flash and constant errors.

[Dale]

David Haller wrote:
> Hello,
>
> On Mon, 11 Jun 2012, Dale wrote:
>> `/usr/portage/distfiles/adobe-flash-11.2.202.235.i386.tar.gz' saved
> 11.2.202.235 crashes all the time anyway (at least on x86_64), there's
> a new version 11.2.202.236 out since yesterday or so that works again.
>
> HTH,
> -dnh
>


I been using *.236 for a while.  I think it is a mismatch between flash
and something else, maybe nvidia, Seamonkey or something like that. 

Right now, it seems to be working fine.  I've done a few upgrades so
maybe whatever was not happy got updated to a happy version.  Now that
it is happy, I'll join in.  lol

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"