Bug 385733

Summary:	www-plugins/adobe-flash-11.0.1.152 unpack phase: install_flash_player_11_linux.x86_64.tar.gz does not exist
Product:	Gentoo Linux	Reporter:	zaiyers <zaiyers>
Component:	New packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	changes the unpack source

Description zaiyers 2011-10-05 12:33:39 UTC

Created attachment 288859 [details]
changes the unpack source

MY_64B_URI & MY_32B_URI don't work for unpacking

build.log
---------------
 * Package:    www-plugins/adobe-flash-11.0.1.152
 * Repository: gentoo
 * Maintainer: lack@gentoo.org desktop-misc@gentoo.org
 * USE:        32bit 64bit amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   sandbox
>>> Unpacking source...
>>> Unpacking install_flash_player_11_linux.x86_64.tar.gz to /var/tmp/portage/www-plugins/adobe-flash-11.0.1.152/work
 * ERROR: www-plugins/adobe-flash-11.0.1.152 failed (unpack phase):
 *   install_flash_player_11_linux.x86_64.tar.gz does not exist
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_unpack
 *   environment, line 2707:  Called unpack 'install_flash_player_11_linux.x86_64.tar.gz' '->' 'adobe-flash-11.0.1.152.x86_64.tar.gz'
 *     ebuild.sh, line  366:  Called die
 * The specific snippet of code:
 *   		[[ ! -s ${srcdir}${x} ]] && die "${x} does not exist"
 * 
 * If you need support, post the output of 'emerge --info =www-plugins/adobe-flash-11.0.1.152',
 * the complete build log and the output of 'emerge -pqv =www-plugins/adobe-flash-11.0.1.152'.
 * The complete build log is located at '/var/tmp/portage/www-plugins/adobe-flash-11.0.1.152/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-plugins/adobe-flash-11.0.1.152/temp/environment'.
 * S: '/var/tmp/portage/www-plugins/adobe-flash-11.0.1.152/work'


attached diff fixed it for me

Comment 1 zaiyers 2011-10-05 12:40:26 UTC


*** This bug has been marked as a duplicate of bug 385731 ***