| Summary: | Patch fails without X use flag in media-libs/libdc1394-1.2.2 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Eric Westbrook <gentoo> |
| Component: | [OLD] Library | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Ebuild's patch output as requested by error message
Corrected nox11 patch file for libdc1394-1.2.2 Changes to media-libs/libdc1394-1.2.2.ebuild for using new nox11 patch file |
||
|
Description
Eric Westbrook
2010-03-08 16:10:17 UTC
I neglected to be clear that enabling the X use flag does result in a successful emerge, but one might expect that, since the offending patch name contains "nox11". :) Created attachment 222693 [details]
Ebuild's patch output as requested by error message
I also suspect that bug 263251 is closely related to this, even though the failure output is a bit different. Please advise if this bug should be marked duplicate and that bug reopened instead. Created attachment 222713 [details, diff]
Corrected nox11 patch file for libdc1394-1.2.2
I created this patch file by manually merging the libdc1394-1.2.1-nox11.patch file's differences into examples/Makefile.in and then using diff -ur. It seems to resolve this issue for me.
Created attachment 222715 [details, diff]
Changes to media-libs/libdc1394-1.2.2.ebuild for using new nox11 patch file
Differences in the ebuild used in my overlay to implement the above new patch file.
It still fails with "-X". Why is 1.2.2 pulling 1.2.1 patch? -------------------- * Package: media-libs/libdc1394-1.2.2 * Repository: gentoo * Maintainer: stefaan@gentoo.org * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU >>> cfg-update-1.8.2-r1: Checksum index is up-to-date ... * Applying libdc1394-1.2.1-nox11.patch ... * Failed Patch: libdc1394-1.2.1-nox11.patch ! * ( /usr/portage/media-libs/libdc1394/files/libdc1394-1.2.1-nox11.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/media-libs/libdc1394-1.2.2/temp/libdc1394-1.2.1-nox11.patch.out * ERROR: media-libs/libdc1394-1.2.2 failed: * Failed Patch: libdc1394-1.2.1-nox11.patch! * * Call stack: * ebuild.sh, line 56: Called src_unpack * environment, line 2656: Called epatch '/usr/portage/media-libs/libdc1394/files/libdc1394-1.2.1-nox11.patch' * environment, line 1294: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of 'emerge --info =media-libs/libdc1394-1.2.2', * the complete build log and the output of 'emerge -pqv =media-libs/libdc1394-1.2.2'. * The complete build log is located at '/var/tmp/portage/media-libs/libdc1394-1.2.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/libdc1394-1.2.2/temp/environment'. * S: '/var/tmp/portage/media-libs/libdc1394-1.2.2/work/libdc1394-1.2.2' Patch has been removed altogether (see bug #226751 as for why, it was a bad idea in the first place). |
