public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] adobe-flash and constant errors.
Date: Mon, 11 Jun 2012 19:52:11 +0800	[thread overview]
Message-ID: <1339415531.14610.3.camel@moriah> (raw)
In-Reply-To: <4FD5CE50.9090907@gmail.com>

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





  reply	other threads:[~2012-06-11 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 10:54 [gentoo-user] adobe-flash and constant errors Dale
2012-06-11 11:52 ` William Kenworthy [this message]
2012-06-11 13:46   ` Dale
2012-06-13 19:21     ` Mick
2012-06-13 20:44       ` Dale
2012-06-14 16:28 ` David Haller
2012-06-18  2:53   ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1339415531.14610.3.camel@moriah \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox