Created attachment 401932 [details] patch.out * Package: dev-python/python-keystoneclient-1.4.0 * Repository: gentoo * Maintainer: prometheanfire@gentoo.org openstack@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python2_7 python_targets_python3_3 userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Applying cve-2015-1852-master-keystoneclient.patch ... * Failed Patch: cve-2015-1852-master-keystoneclient.patch ! * ( /usr/portage/dev-python/python-keystoneclient/files/cve-2015-1852-master-keystoneclient.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-python/python-keystoneclient-1.4.0/temp/cve-2015-1852-master-keystoneclient.patch.out * ERROR: dev-python/python-keystoneclient-1.4.0::gentoo failed (prepare phase): * Failed Patch: cve-2015-1852-master-keystoneclient.patch! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 3732: Called distutils-r1_src_prepare * environment, line 1147: Called python_prepare_all * environment, line 3568: Called distutils-r1_python_prepare_all * environment, line 1057: Called epatch '/usr/portage/dev-python/python-keystoneclient/files/cve-2015-1852-master-keystoneclient.patch' * environment, line 1518: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=dev-python/python-keystoneclient-1.4.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-python/python-keystoneclient-1.4.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-python/python-keystoneclient-1.4.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/python-keystoneclient-1.4.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/python-keystoneclient-1.4.0/work/python-keystoneclient-1.4.0' * S: '/var/tmp/portage/dev-python/python-keystoneclient-1.4.0/work/python-keystoneclient-1.4.0'
According to https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1852 that patch is attempting to patch something that only affected versions <=1.3.0 - is it even needed for 1.4.0?
fixed :D
