Summary: | =net-libs/xulrunner-1.9.2.12: epatch fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Albert W. Hopkins <marduk> |
Component: | New packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
build.log emerge -pqv |
Description
Albert W. Hopkins
2010-10-29 23:02:59 UTC
Created attachment 252523 [details]
emerge --info
Created attachment 252525 [details]
build.log
Created attachment 252527 [details]
emerge -pqv
I have tested this twice now and patch has applied fine both times. Please sync up and retest. I've tried syncing several times and it still happens. (In reply to comment #5) > I've tried syncing several times and it still happens. > I have double checked with a few of my herd members and they are all reporting same results to me. What version of patch do you have installed? Did you completely remove ${PORTSDIR}/net-libs/xulrunner and sync again? (In reply to comment #6) > I have double checked with a few of my herd members and they are all reporting > same results to me. What version of patch do you have installed? Did you > completely remove ${PORTSDIR}/net-libs/xulrunner and sync again? Am using patch-2.6.1. I did downgrade to patch-2.5.9-r1 but experienced the same issue. I did remove the xulrunner directory and re-sync. I am using the portage-2.2 series and I even tried downgrading to 2.1, but still the same issue. I now have this issue reproducible on two different systems, that synced from two different servers. I will continue to look into it. Perhaps an emerge -e world will fix it. This is my fault. I had reported bug #341901. A patch was proposed. I tested it by monkey-patching the ebuild via /etc/portage/env... and after it started working I had since forgotten about it. Well this patch was the same as bug-606109.patch so it was attempting to apply it twice. Well I have learned a lesson. Sorry to waste your time. (In reply to comment #8) > This is my fault. > > I had reported bug #341901. A patch was proposed. I tested it by > monkey-patching the ebuild via /etc/portage/env... and after it started working > I had since forgotten about it. Well this patch was the same as > bug-606109.patch so it was attempting to apply it twice. > > Well I have learned a lesson. Sorry to waste your time. > Yeah we use the upstream bug numbers when we place them in the tree, this has actually already landed on firefox-1.9.2.13 but it will not be released for a few weeks hopefully. Sorry for the confusion. |