| Summary: | sys-fs/aufs3 with sys-kernel/tuxonice-sources-3.4.x - Failed Patch: aufs3-base-4.patch ! | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | rafnov <rafnov> |
| Component: | New packages | Assignee: | Justin Lecher (RETIRED) <jlec> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | ibuyandtrade0+bugs.gentoo.org, tommy |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info patch.out build.log aufs3-base-5.patch.out |
||
Created attachment 324788 [details]
emerge --info
file /usr/src/linux /usr/src/linux: symbolic link to `linux-3.4.11-tuxonice' Created attachment 325180 [details]
patch.out
Are you using a clean and fresh source directory? I had same problem with sys-kernel/pf-sources-3.5.4 and sys-devel/patch-2.7.0. Masking >=patch-2.7.0 helped, but now it's working with 2.7.1. I don't have time to check with 2.7.0 again though (not in the tree anymore). so you are thinking it is a patch-2.7.0 bug? (In reply to comment #4) > Are you using a clean and fresh source directory? I've removed package of sys-kernel/tuxonice-sources-3.4.11 , reinstalled it, then succesfully installed sys-fs/aufs3-3_p20120813 and compiled kernel with it. Yes, tried again with patch-2.7 from here http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/patch/patch-2.7.ebuild?revision=1.4 and aufs3 fails while patching aufs3-base-5.patch. Created attachment 325742 [details]
build.log
Created attachment 325744 [details]
aufs3-base-5.patch.out
as sys-devel/patch-2.7 isn't in the tree anymore and sys-devel/patch-2.7.1 works I will close this bug. |
Created attachment 324786 [details] build.log Installing sys-fs/aufs3-3_p20120813 and three versions back fails on kernels 3.4.x with the following output: * Messages for package sys-fs/aufs3-3_p20120813: * Patching your kernel... * Failed Patch: aufs3-base-4.patch ! * ( /usr/portage/sys-fs/aufs3/files/aufs3-base-4.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20120813/temp/aufs3-base-4.patch.out * ERROR: sys-fs/aufs3-3_p20120813 failed (setup phase): * Failed Patch: aufs3-base-4.patch! * * Call stack: * ebuild.sh, line 85: Called pkg_setup * aufs3-3_p20120813.ebuild, line 72: Called epatch '/usr/portage/sys-fs/aufs3/files/aufs3-base-4.patch' '/usr/portage/sys-fs/aufs3/files/aufs3-standalone-4.patch' * eutils.eclass, line 325: Called epatch '/usr/portage/sys-fs/aufs3/files/aufs3-base-4.patch' * eutils.eclass, line 530: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * * If you need support, post the output of `emerge --info '=sys-fs/aufs3-3_p20120813'`, * the complete build log and the output of `emerge -pqv '=sys-fs/aufs3-3_p20120813'`. * The complete build log is located at '/var/tmp/portage/sys-fs/aufs3-3_p20120813/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/aufs3-3_p20120813/temp/die.env'. * Working directory: '/usr/src/linux' * S: '/var/tmp/portage/sys-fs/aufs3-3_p20120813/work/aufs3-standalone' * * The following package has failed to build or install: * * (sys-fs/aufs3-3_p20120813::gentoo, ebuild scheduled for merge), Log file: * '/var/tmp/portage/sys-fs/aufs3-3_p20120813/temp/build.log' Build.log and emerge --info in the attachments.