Starting from mm-sources-2.6.25-rc8-r1, mm-sources cannot be built on my system. The patch part of the ebuild fails with an assertion in patch. However patching using 'patch' from the command line by hand works fine. A diff of the mm ebuilds shows that the only difference appears to be the actual filename itself. Reproducible: Always Steps to Reproduce: 1. emerge sys-kernel/mm-sources-2.6.25-rc5-r3 (works) 2. emerge sys-kernel/mm-sources-2.6.25-rc8-r1 (patching fails as below) Actual Results: tornado mm-sources # emerge =sys-kernel/mm-sources-2.6.26_rc8-r1 WARNING: repository at /usr/local/portage is missing a repo_name entry Calculating dependencies... done! >>> Verifying ebuild manifests >>> Building (1 of 1) sys-kernel/mm-sources-2.6.26_rc8-r1 * patch-2.6.26-rc8.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * linux-2.6.25.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * 2.6.26-rc8-mm1.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Preparing to unpack ... >>> Unpacking source... >>> Unpacking linux-2.6.25.tar.bz2 to /var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/work * Applying patch-2.6.26-rc8.patch (-p0+) ... [ ok ] * Applying 2.6.26-rc8-mm1.patch (-p0+) ... patch: pch.c:621: intuit_diff_type: Assertion `i0 != NONE' failed. patch: pch.c:621: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ] * Please attach /var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/2.6.26-rc8-mm1.err to any bug you may post. * ERROR: sys-kernel/mm-sources-2.6.26_rc8-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2996: Called kernel-2_src_unpack * environment, line 2197: Called unipatch '/usr/portage/distfiles/patch-2.6.26-rc8.bz2 /usr/portage/distfiles/2.6.26-rc8-mm1.bz2' * environment, line 3466: Called die * The specific snippet of code: * die "Unable to dry-run patch."; * The die message: * Unable to dry-run patch. * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/environment'. * Messages for package sys-kernel/mm-sources-2.6.26_rc8-r1: * Please attach /var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/2.6.26-rc8-mm1.err to any bug you may post. * ERROR: sys-kernel/mm-sources-2.6.26_rc8-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2996: Called kernel-2_src_unpack * environment, line 2197: Called unipatch '/usr/portage/distfiles/patch-2.6.26-rc8.bz2 /usr/portage/distfiles/2.6.26-rc8-mm1.bz2' * environment, line 3466: Called die * The specific snippet of code: * die "Unable to dry-run patch."; * The die message: * Unable to dry-run patch. * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.26_rc8-r1/temp/environment'. tornado mm-sources # The 'environment' file is at http://www.reub.net/files/environment emerge --info is up at http://www.reub.net/files/emerge-info mm-sources-2.6.27_rc1-r1 fails at the patching phase in the same way. The error log for the first broken ebuild is at: http://www.reub.net/files/patch-2.6.26-rc8-r1.err The error log for the latest ebuild is at: http://www.reub.net/files/patch-2.6.27-rc1-r1.err I have not had issues with any other ebuilds on my machine failing to build..
Same here with mm-sources-2.6.27_rc1-r1. Let me know if you need the build and environment logs. >>> Unpacking source... >>> Unpacking linux-2.6.26.tar.bz2 to /var/tmp/portage/sys-kernel/mm-sources-2.6.27_rc1-r1/work * Applying patch-2.6.27-rc1.patch (-p0+) ... patch: pch.c:621: intuit_diff_type: Assertion `i0 != NONE' failed. patch: pch.c:621: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ] * Please attach /var/tmp/portage/sys-kernel/mm-sources-2.6.27_rc1-r1/temp/patch-2.6.27-rc1.err to any bug you may post. * ERROR: sys-kernel/mm-sources-2.6.27_rc1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3034: Called kernel-2_src_unpack * environment, line 2235: Called unipatch '/usr/portage/distfiles/patch-2.6.27-rc1.bz2 /usr/portage/distfiles/2.6.27-rc1-mm1.bz2' * environment, line 3504: Called die * The specific snippet of code: * die "Unable to dry-run patch."; * The die message: * Unable to dry-run patch. * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.27_rc1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/mm-sources-2.6.27_rc1-r1/temp/environment'.
I also have this problem, with the following versions: sys-kernel/mm-sources-2.6.27_rc1-r1 sys-kernel/mm-sources-2.6.26_rc8-r1. The last working one is: sys-kernel/mm-sources-2.6.26_rc5-r3
Next time please attach log files. :) I fixed this about 11 days ago and you should not be having this problem any more. Please confirm.
Yes works for me now with 2.6.27_rc1-r1 - thanks.
