When I try to emerge the newest mm-sources it fails: bash-2.05b# emerge -u mm-sources Calculating dependencies ...done! >>> emerge (1 of 1) sys-kernel/mm-sources-2.6.5_rc3-r1 to / >>> md5 src_uri ;-) patch-2.6.5-rc3.bz2 >>> md5 src_uri ;-) linux-2.6.4.tar.bz2 >>> md5 src_uri ;-) 2.6.5-rc3-mm1.bz2 >>> Preparing to unpack... >>> Unpacking source... >>> Unpacking linux-2.6.4.tar.bz2 to /var/tmp/portage/mm-sources-2.6.5_rc3-r1/work * Applying patch-2.6.5-rc3.patch... patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ] * Please attach /var/tmp/portage/mm-sources-2.6.5_rc3-r1/temp/patch-2.6.5-rc3.err to any bug you may post. !!! ERROR: sys-kernel/mm-sources-2.6.5_rc3-r1 failed. !!! Function unipatch, Line 443, Exitcode 0 !!! Unable to dry-run patch. Reproducible: Always Steps to Reproduce: 1.emerge mm-sources 2. 3.
Created attachment 28447 [details] Error message from emerge
*** This bug has been marked as a duplicate of 46322 ***
There was never a resolution to this posted. I have no broken symlinks that are related to portage/kernel. I don't remember doing a "dirty" unmerge and if I did, what do I do to "clean" it? It happens for the newest mm-sources-2.6.5_rc3-r4.
Same thing for sys-kernel/mm-sources-2.6.5-r1: >>> md5 src_uri ;-) linux-2.6.5.tar.bz2 >>> md5 src_uri ;-) 2.6.5-mm1.bz2 >>> Preparing to unpack... >>> Unpacking source... >>> Unpacking linux-2.6.5.tar.bz2 to /var/tmp/portage/mm-sources-2.6.5-r1/work * Applying 2.6.5-mm1.patch... patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ] * Please attach /var/tmp/portage/mm-sources-2.6.5-r1/temp/2.6.5-mm1.err to any bug you may post. !!! ERROR: sys-kernel/mm-sources-2.6.5-r1 failed. !!! Function unipatch, Line 443, Exitcode 0 !!! Unable to dry-run patch.
Created attachment 28764 [details] error log
Confirmed here as well. `diff` says my error log is exactly the same as the one posted above for mm-sources-2.6.5-r1 .
and another confirmation here... sigh
Could you try emerge patch and see if that fixes anything?
genlop -l | tail -2 Fri Apr 9 10:44:47 2004 --> sys-devel/patch-2.5.9 # emerge mm-sources Calculating dependencies ...done! >>> emerge (1 of 1) sys-kernel/mm-sources-2.6.5-r1 to / >>> md5 src_uri ;-) linux-2.6.5.tar.bz2 >>> md5 src_uri ;-) 2.6.5-mm1-gentoo1.bz2 >>> Preparing to unpack... >>> Unpacking source... >>> Unpacking linux-2.6.5.tar.bz2 to /var/tmp/portage/mm-sources-2.6.5-r1/work RUNNING FROM extra_functions.sh * Applying 2.6.5-mm1-gentoo1.bz2... * Failed Patch: 2.6.5-mm1-gentoo1.bz2! * * Include in your bugreport the contents of: * * /var/tmp/portage/mm-sources-2.6.5-r1/temp/2.6.5-mm1-gentoo1.bz2-3278.out !!! ERROR: sys-kernel/mm-sources-2.6.5-r1 failed. !!! Function epatch, Line 360, Exitcode 0 !!! Failed Patch: 2.6.5-mm1-gentoo1.bz2!
Created attachment 28964 [details] error file #emerge info Portage 2.0.50-r3 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-rc2-mm3) ================================================================= System uname: 2.6.5-rc2-mm3 i686 AMD-K7(tm) Processor Gentoo Base System version 1.4.3.13 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3. /share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/sha e/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texm /xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://gentoo.noved.org/ ftp://gentoo.noved.org/ ftp://mirror.iawnet.sandia.gov/pub/gentoo/ http://www.z ntek-international.com/mirrors/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile hyriand imlib java jpeg kde ldap libg++ libwww mad mikmod mmx motif mozilla moznocompose moznoirc mpeg ncurses nls oggvorbis o engl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl s ga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib"
Also i have had this problem since mm-sources_rc2-r3: Thu Mar 25 18:16:05 2004 --> sys-kernel/mm-sources-2.6.5_rc2-r3 Thu Mar 25 21:03:09 2004 --> media-gfx/bootsplash-0.6-r12 Thu Mar 25 22:00:53 2004 --> sys-fs/sysfsutils-0.4.0 Thu Mar 25 22:01:28 2004 --> sys-apps/hotplug-20040105 Thu Mar 25 22:02:20 2004 --> sys-fs/udev-016-r2 Fri Mar 26 00:01:36 2004 --> sys-fs/udev-023-r1
im trying to track down the problem so im patching it manually following what the ebuild would do, and i find that the patch fails because some source files aren't being extracted correctly. /var/tmp/portage/mm-sources-2.6.5-r1/work # patch -p0 --dry-run < mm.patch | grep rej 1 out of 13 hunks FAILED -- saving rejects to file linux-2.6.5-mm1/drivers/scsi/qla2xxx/ql2300_fw.c.rej 1 out of 10 hunks FAILED -- saving rejects to file linux-2.6.5-mm1/drivers/scsi/qla2xxx/ql2322_fw.c.rej 1 out of 10 hunks FAILED -- saving rejects to file linux-2.6.5-mm1/drivers/scsi/qla2xxx/ql6322_fw.c.rej 1 out of 39 hunks FAILED -- saving rejects to file linux-2.6.5-mm1/fs/devfs/base.c.rej root@sakai /var/tmp/portage/mm-sources-2.6.5-r1/work # vi linux-2.6.5-mm1/fs/devfs/base.c that file has a block section full of ^@^@^@^@^@.. it seems to be random .. i've gont through a few unpack/clean cycles and it's different files that fail, the qla2xxx stuff appears alot tho. so I'm thinking it's a buggy bzip2 or my FS is corrupting the files .. dmesg doesn't show any errors or anything unusual.
I've chrooted my sytem from the liveCD and reiserfsck'ed my hdd .. no corruption. i've managed to emerge mm-sources while in my chroot. I would guess the problem is somewhere in the kernel i was running. rfs3 drivers must be buggy. I have filed a new bug http://bugs.gentoo.org/show_bug.cgi?id=47406 .. to ask that release candidates be masked. to reduce the amount of people with buggy kernels.
Does the patching issue still exist on non rc mm-sources?
My opinion is that the person's running kernel is the problem. The patches aren't being written to disk correctly. I've been able to emerge mm-sources-r4 from mm-sources-r1 with no problem. Like my previous comments suggest, dropping to the liveCD or using a known good old kernel you still have in /boot should workaround the problem.
Comment 15 is confirmed here. I tried emerging development-sources-2.6.5 (which works fine since there is no patching) and it failed in compiling, throwing many errors. This was resolved by booting off a live-cd and compiling said kernel. Having done those steps (and running a new kernel), emerging mm-sources is successful. Unless others are still having issues, I believe should be closed.
Was running kernel causing the problems. Fixed by booting into a livecd and going from there.
