Bug 207969 – sys-apps/coreutils-6.10-r1 patch 001_all_coreutils-gen-progress-bar.patch fails

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description manwe 2008-01-28 22:51:09 UTC]

This is great patch, not used be default but still available for people who wanted it. With version 6.10-r1 it fails to modify sourcecode.

Reproducible: Always

Steps to Reproduce:
1. remove 001_all_coreutils-gen-progress-bar.patch from EPATCH_EXCLUDE
2. emerge =coreutils-6.10-r1





Portage 2.1.4 (default-linux/amd64/2007.0, gcc-4.2.2, glibc-2.7-r1, 2.6.23-kamikaze5-endar-v19 x86_64)
=================================================================
System uname: 2.6.23-kamikaze5-endar-v19 x86_64 AMD Turion(tm) 64 Mobile Technology MT-32
Timestamp of tree: Mon, 28 Jan 2008 18:46:01 +0000
app-shells/bash:     3.2_p33
dev-java/java-config: 1.3.7, 2.1.3
dev-lang/python:     2.5.1-r5
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 2.0.0_rc6-r1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.7.9-r1, 1.9.6-r2, 1.10.1
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.24
ABI="amd64"
ACCEPT_KEYWORDS="amd64 ~amd64"





***** 001_all_coreutils-gen-progress-bar.patch *****

====================================================

PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /tmp/portage/sys-apps/coreutils-6.10-r1/work/patch/001_all_coreutils-gen-progress-bar.patch

====================================================
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Upstream has been contacted about this a few times ...
|
|they dont want progress bars in mv/cp:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-08/msg00114.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00083.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00084.html
|
|but they don't seem to mind a general util ... add this to future patchset:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00101.html
|http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00071.html
|
|--- coreutils/src/copy.c
|+++ coreutils/src/copy.c
--------------------------
No file to patch.  Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 240
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/copy.h
|+++ coreutils/src/copy.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 259
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/cp.c
|+++ coreutils/src/cp.c
--------------------------
No file to patch.  Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 325
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/mv.c
|+++ coreutils/src/mv.c
--------------------------
No file to patch.  Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 400
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/remove.h
|+++ coreutils/src/remove.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
====================================================

PATCH COMMAND:   patch -p1 -g0 -E --no-backup-if-mismatch < /tmp/portage/sys-apps/coreutils-6.10-r1/work/patch/001_all_coreutils-gen-progress-bar.patch

====================================================
patching file src/copy.c
Hunk #1 succeeded at 16 (offset -1 lines).
Hunk #3 succeeded at 60 with fuzz 2 (offset 4 lines).
Hunk #4 succeeded at 90 with fuzz 1 (offset -2 lines).
Hunk #5 succeeded at 307 with fuzz 1 (offset 107 lines).
Hunk #6 succeeded at 391 with fuzz 2 (offset 104 lines).
Hunk #7 FAILED at 508.
Hunk #8 succeeded at 530 with fuzz 2 (offset 59 lines).
Hunk #9 succeeded at 900 with fuzz 2 (offset 224 lines).
1 out of 9 hunks FAILED -- saving rejects to file src/copy.c.rej
patching file src/copy.h
Hunk #1 succeeded at 193 (offset 18 lines).
patching file src/cp.c
Hunk #1 succeeded at 85 (offset 4 lines).
Hunk #2 succeeded at 135 (offset 7 lines).
Hunk #3 succeeded at 192 with fuzz 2 (offset 7 lines).
Hunk #4 FAILED at 723.
Hunk #5 succeeded at 925 (offset 98 lines).
Hunk #6 succeeded at 985 (offset 98 lines).
1 out of 6 hunks FAILED -- saving rejects to file src/cp.c.rej
patching file src/mv.c
Hunk #3 succeeded at 112 (offset -1 lines).
Hunk #4 succeeded at 158 with fuzz 2.
Hunk #5 succeeded at 324 (offset -1 lines).
Hunk #6 succeeded at 392 (offset -1 lines).
Hunk #7 succeeded at 405 (offset -1 lines).
patching file src/remove.h
Hunk #1 succeeded at 59 (offset 11 lines).
====================================================

PATCH COMMAND:   patch -p2 -g0 -E --no-backup-if-mismatch < /tmp/portage/sys-apps/coreutils-6.10-r1/work/patch/001_all_coreutils-gen-progress-bar.patch

====================================================
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Upstream has been contacted about this a few times ...
|
|they dont want progress bars in mv/cp:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-08/msg00114.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00083.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00084.html
|
|but they don't seem to mind a general util ... add this to future patchset:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00101.html
|http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00071.html
|
|--- coreutils/src/copy.c
|+++ coreutils/src/copy.c
--------------------------
No file to patch.  Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 240
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/copy.h
|+++ coreutils/src/copy.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 259
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/cp.c
|+++ coreutils/src/cp.c
--------------------------
No file to patch.  Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 325
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/mv.c
|+++ coreutils/src/mv.c
--------------------------
No file to patch.  Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 400
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/remove.h
|+++ coreutils/src/remove.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
====================================================

PATCH COMMAND:   patch -p3 -g0 -E --no-backup-if-mismatch < /tmp/portage/sys-apps/coreutils-6.10-r1/work/patch/001_all_coreutils-gen-progress-bar.patch

====================================================
missing header for unified diff at line 14 of patch
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Upstream has been contacted about this a few times ...
|
|they dont want progress bars in mv/cp:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-08/msg00114.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00083.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00084.html
|
|but they don't seem to mind a general util ... add this to future patchset:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00101.html
|http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00071.html
|
|--- coreutils/src/copy.c
|+++ coreutils/src/copy.c
--------------------------
No file to patch.  Skipping patch.
9 out of 9 hunks ignored
missing header for unified diff at line 240 of patch
can't find file to patch at input line 240
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/copy.h
|+++ coreutils/src/copy.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 259 of patch
can't find file to patch at input line 259
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/cp.c
|+++ coreutils/src/cp.c
--------------------------
No file to patch.  Skipping patch.
6 out of 6 hunks ignored
missing header for unified diff at line 325 of patch
can't find file to patch at input line 325
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/mv.c
|+++ coreutils/src/mv.c
--------------------------
No file to patch.  Skipping patch.
7 out of 7 hunks ignored
missing header for unified diff at line 400 of patch
can't find file to patch at input line 400
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/remove.h
|+++ coreutils/src/remove.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
====================================================

PATCH COMMAND:   patch -p4 -g0 -E --no-backup-if-mismatch < /tmp/portage/sys-apps/coreutils-6.10-r1/work/patch/001_all_coreutils-gen-progress-bar.patch

====================================================
missing header for unified diff at line 14 of patch
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Upstream has been contacted about this a few times ...
|
|they dont want progress bars in mv/cp:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-08/msg00114.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00083.html
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00084.html
|
|but they don't seem to mind a general util ... add this to future patchset:
|http://lists.gnu.org/archive/html/bug-coreutils/2003-09/msg00101.html
|http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00071.html
|
|--- coreutils/src/copy.c
|+++ coreutils/src/copy.c
--------------------------
No file to patch.  Skipping patch.
9 out of 9 hunks ignored
missing header for unified diff at line 240 of patch
can't find file to patch at input line 240
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/copy.h
|+++ coreutils/src/copy.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 259 of patch
can't find file to patch at input line 259
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/cp.c
|+++ coreutils/src/cp.c
--------------------------
No file to patch.  Skipping patch.
6 out of 6 hunks ignored
missing header for unified diff at line 325 of patch
can't find file to patch at input line 325
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/mv.c
|+++ coreutils/src/mv.c
--------------------------
No file to patch.  Skipping patch.
7 out of 7 hunks ignored
missing header for unified diff at line 400 of patch
can't find file to patch at input line 400
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- coreutils/src/remove.h
|+++ coreutils/src/remove.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

[Comment 1 Jakub Moc (RETIRED) 2008-01-28 22:55:25 UTC]

(In reply to comment #0)
> 1. remove 001_all_coreutils-gen-progress-bar.patch from EPATCH_EXCLUDE
> 2. emerge =coreutils-6.10-r1

Yeah, and why is this a bug? Skip 1/ and you won't have problems. (Also cf. Bug 146964)