| Summary: | www-plugins/adobe-flash-11.2.202.356.x86_64.tar.gz size mismatch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | peter <peter> |
| Component: | [OLD] Library | Assignee: | Jeroen Roovers (RETIRED) <jer> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
peter@prh.myzen.co.uk
2014-05-08 18:46:40 UTC
I can't reproduce that. Do you use a caching proxy? Yes, I have a box on the LAN that runs squid and http-replicator. Taking your hint, I ran wget with --no-proxy to get the flash file and had no further problem, so it looks like I shouldn't have raised the bug. Sorry. I had a similar problem with the previous version too, so a pattern seemed to be emerging (no pun intended). But why should my proxy have bad copies of these two versions of adobe-flash and yet never another bad file in the (few) years I've been running this way? Anyway, I'll close the bug report. (In reply to Peter Humphrey from comment #2) > Yes, I have a box on the LAN that runs squid and http-replicator. Taking > your hint, I ran wget with --no-proxy to get the flash file and had no > further problem, so it looks like I shouldn't have raised the bug. Sorry. > > I had a similar problem with the previous version too, so a pattern seemed > to be emerging (no pun intended). But why should my proxy have bad copies of > these two versions of adobe-flash and yet never another bad file in the > (few) years I've been running this way? Because Adobe doesn't version their files properly, and because your caching proxy fails at distinguishing the URLs. The URLs contain the version as a directory and include only the major version in the file name. A SRC_URI arrow is used to save the downloaded file under a more useful name that includes the package name and version. You would need to teach your proxy to distinguish between those directories. (For the 64-bit installer:) http://fpdownload.macromedia.com/get/flashplayer/pdc/${PV}/install_flash_player_${PV_M}_linux.x86_64.tar.gz -> ${P}.x86_64.tar.gz What emerge ends up seeing is the part after the arrow "->", while the former is being requested from your proxy. It should be easy to tell it not to cache it or to pay better attention. :) I use http-replicator to buffer emerge's source fetches. It has no built-in options to filter what it gets, at least not as far as I can see. Maybe I should arrange it to fetch through the local squid proxy, though it seems wasteful to cache files twice. Thanks for the explanation anyway - you must weary of telling everyone who stumbles over this problem. |
