| Summary: | Failure during emerge for glibc-2.3.3.20040420 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Miller <dmiller> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | g1gsw |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Same problem here. By the way, this is a duplicate of 53120, I think. And, #53107 already seems to contain the solution... changing line 267 in the ebuild to 2.3.3 from 3.3.3 fixed it for me. |
During the emerge, there is a failure message. I believe there is a typo in the version number. Since I'm not a developer, I don't know where to look, but the relevant line refers to $EPATCH_SOURCE. The ebuild is looking for glibc-3.3.3-etc, and I believe that should be glibc-2.3.3-etc Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -U system 3. Actual Results: >>> Unpacking source... >>> Unpacking glibc-2.3.2.tar.bz2 to /var/tmp/portage/glibc-2.3.3.20040420/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/distfiles/glibc-3.3.3-branch-update-20040420.patch.bz2 !!! ERROR: sys-libs/glibc-2.3.3.20040420 failed. !!! Function epatch, Line 182, Exitcode 0 !!! Cannot find $EPATCH_SOURCE!