emerging world after new bootstrap, e2fsprogs-1.35 patch "e2fsprogs-sed-locale" failed to apply Reproducible: Always Steps to Reproduce: 1.bootstrap 2. emerge world 3. Actual Results: >>> emerge (1 of 27) sys-fs/e2fsprogs-1.35 to / >>> md5 src_uri ;-) e2fsprogs-1.35.tar.gz >>> Unpacking source... >>> Unpacking e2fsprogs-1.35.tar.gz to /var/tmp/portage/e2fsprogs-1.35/work * Applying e2fsprogs-1.32-mk_cmds-cosmetic.patch... [ ok ] * Applying e2fsprogs-sed-locale.patch... * Failed Patch: e2fsprogs-sed-locale.patch! -21492.out ***** e2fsprogs-sed-locale.patch ***** =============================================================== PATCH COMMAND: patch -p0 -g0 < /usr/portage/sys-fs/e2fsprogs/files/e2fsprogs-se d-locale.patch =============================================================== can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/config.rpath e2fsprogs-1.34/config.rpath |--- e2fsprogs-1.34.orig/config.rpath 2003-07-23 05:57:24.000000000 -0700 |+++ e2fsprogs-1.34/config.rpath 2003-12-30 01:24:38.000000000 -0800 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 16 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/configure e2fsprogs-1.34/configure |--- e2fsprogs-1.34.orig/configure 2003-07-23 06:07:31.000000000 -0700 |+++ e2fsprogs-1.34/configure 2003-12-30 01:21:32.000000000 -0800 -------------------------- No file to patch. Skipping patch. 11 out of 11 hunks ignored can't find file to patch at input line 123 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/lib/ss/ct_c.sed e2fsprogs-1.34/lib/ss/ct_c.sed |--- e2fsprogs-1.34.orig/lib/ss/ct_c.sed 2002-02-02 22:03:43.000000000 -0 800 |+++ e2fsprogs-1.34/lib/ss/ct_c.sed 2003-12-30 01:23:55.000000000 -0800 -------------------------- No file to patch. Skipping patch. patch unexpectedly ends in middle of line 4 out of 4 hunks ignored =============================================================== PATCH COMMAND: patch -p1 -g0 < /usr/portage/sys-fs/e2fsprogs/files/e2fsprogs-se d-locale.patch =============================================================== patching file config.rpath patching file configure Hunk #8 succeeded at 2213 (offset 15 lines). Hunk #9 succeeded at 2246 (offset 15 lines). Hunk #10 FAILED at 6219. Hunk #11 succeeded at 6330 (offset 88 lines). 1 out of 11 hunks FAILED -- saving rejects to file configure.rej patching file lib/ss/ct_c.sed patch unexpectedly ends in middle of line Hunk #4 succeeded at 132 with fuzz 1. =============================================================== PATCH COMMAND: patch -p2 -g0 < /usr/portage/sys-fs/e2fsprogs/files/e2fsprogs-se d-locale.patch =============================================================== missing header for unified diff at line 4 of patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/config.rpath e2fsprogs-1.34/config.rpath |--- e2fsprogs-1.34.orig/config.rpath 2003-07-23 05:57:24.000000000 -0700 |+++ e2fsprogs-1.34/config.rpath 2003-12-30 01:24:38.000000000 -0800 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 16 of patch can't find file to patch at input line 16 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/configure e2fsprogs-1.34/configure |--- e2fsprogs-1.34.orig/configure 2003-07-23 06:07:31.000000000 -0700 |+++ e2fsprogs-1.34/configure 2003-12-30 01:21:32.000000000 -0800 -------------------------- No file to patch. Skipping patch. 11 out of 11 hunks ignored can't find file to patch at input line 123 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/lib/ss/ct_c.sed e2fsprogs-1.34/lib/ss/ct_c.sed |--- e2fsprogs-1.34.orig/lib/ss/ct_c.sed 2002-02-02 22:03:43.000000000 -0 800 |+++ e2fsprogs-1.34/lib/ss/ct_c.sed 2003-12-30 01:23:55.000000000 -0800 -------------------------- No file to patch. Skipping patch. patch unexpectedly ends in middle of line 4 out of 4 hunks ignored =============================================================== PATCH COMMAND: patch -p3 -g0 < /usr/portage/sys-fs/e2fsprogs/files/e2fsprogs-se d-locale.patch =============================================================== missing header for unified diff at line 4 of patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/config.rpath e2fsprogs-1.34/config.rpath |--- e2fsprogs-1.34.orig/config.rpath 2003-07-23 05:57:24.000000000 -0700 |+++ e2fsprogs-1.34/config.rpath 2003-12-30 01:24:38.000000000 -0800 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 16 of patch can't find file to patch at input line 16 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/configure e2fsprogs-1.34/configure |--- e2fsprogs-1.34.orig/configure 2003-07-23 06:07:31.000000000 -0700 |+++ e2fsprogs-1.34/configure 2003-12-30 01:21:32.000000000 -0800 -------------------------- No file to patch. Skipping patch. 11 out of 11 hunks ignored can't find file to patch at input line 123 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/lib/ss/ct_c.sed e2fsprogs-1.34/lib/ss/ct_c.sed |--- e2fsprogs-1.34.orig/lib/ss/ct_c.sed 2002-02-02 22:03:43.000000000 -0 800 |+++ e2fsprogs-1.34/lib/ss/ct_c.sed 2003-12-30 01:23:55.000000000 -0800 -------------------------- No file to patch. Skipping patch. patch unexpectedly ends in middle of line 4 out of 4 hunks ignored =============================================================== PATCH COMMAND: patch -p4 -g0 < /usr/portage/sys-fs/e2fsprogs/files/e2fsprogs-se d-locale.patch =============================================================== missing header for unified diff at line 4 of patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/config.rpath e2fsprogs-1.34/config.rpath |--- e2fsprogs-1.34.orig/config.rpath 2003-07-23 05:57:24.000000000 -0700 |+++ e2fsprogs-1.34/config.rpath 2003-12-30 01:24:38.000000000 -0800 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 16 of patch can't find file to patch at input line 16 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/configure e2fsprogs-1.34/configure |--- e2fsprogs-1.34.orig/configure 2003-07-23 06:07:31.000000000 -0700 |+++ e2fsprogs-1.34/configure 2003-12-30 01:21:32.000000000 -0800 -------------------------- No file to patch. Skipping patch. 11 out of 11 hunks ignored missing header for unified diff at line 123 of patch can't find file to patch at input line 123 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN e2fsprogs-1.34.orig/lib/ss/ct_c.sed e2fsprogs-1.34/lib/ss/ct_c.sed |--- e2fsprogs-1.34.orig/lib/ss/ct_c.sed 2002-02-02 22:03:43.000000000 -0 800 |+++ e2fsprogs-1.34/lib/ss/ct_c.sed 2003-12-30 01:23:55.000000000 -0800 -------------------------- No file to patch. Skipping patch. patch unexpectedly ends in middle of line 4 out of 4 hunks ignored
can you please emerge sync and retry. also please include the output of emerge info in the bug report. thanks
Works for me. Must have been a bad sync.
seemed to be a bad emerge sync
