Hi! In the current glibc-ebuild the branch update version number is separated from the rest of the version number by a period, not an underscore. Thus, the patching only succeeds with this patch applied to the ebuild file: --- glibc-2.3.3.20040420.ebuild.orig 2004-06-06 06:58:22.380779704 +0200 +++ glibc-2.3.3.20040420.ebuild 2004-06-06 06:59:06.383090336 +0200 @@ -264,7 +264,7 @@ if [ -n "${BRANCH_UPDATE}" ] then - epatch ${DISTDIR}/${PN}-${PV/_*}-branch-update-${BRANCH_UPDATE}.patch.bz2 + epatch ${DISTDIR}/${PN}-${PV/.${BRANCH_UPDATE}}-branch-update-${BRANCH_UPDATE}.patch.bz2 fi if use_nptl Else, epatch fails, complaining about not being able to find glibc-2.3.3.20040420-branch-update-20040420.patch.bz2 The Problem occurred on two of my machines and went away after I applied the above patch. Would be nice to have this corrected in portage soon. Regards, Torsten
Same problem here. Your fix solved it. Poly
the patch doesnt work for me, but portage complains that glibc-3.3.3.20040420-branch-update.patch.bz2 doesnt exist (note major version number).
Same here Simon. Change line 267 in the ebuild to: 2.3.3 instead of: 3.3.3
fixed.. Thanks for reporting this guys.
*** Bug 53120 has been marked as a duplicate of this bug. ***
*** Bug 53121 has been marked as a duplicate of this bug. ***
*** Bug 53129 has been marked as a duplicate of this bug. ***