output of the patching problem (patch 1 of 3)

tar-1.12.patch-4510.out (text/plain), 15.39 KB, created by Selth on 2005-05-01 18:10:33 UTC

***** tar-1.12.patch *****

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

PATCH COMMAND:  patch -p0 -g0 < /usr/local/portage/app-admin/amanda/files/tar-1.12.patch

==========================
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|The first hunk in this file was submitted by Craig Wiegert
|<[e-mail]>.  It fixed a problem that causes
|GNUTAR to issue error messages like the following for sparse files:
|
|> /bin/tar: Read error at byte 0, reading 512 bytes, in file ./var/log/lastlog: Bad file number
|
|The others fix an estimate problem in GNUTAR on SunOS 4.1.3, HP/UX and
|other systems whose C libraries do not support "%lld" in printf format
|strings for printing long long integers.
|
|--- tar-1.12/src/create.c	Mon Dec 15 17:26:47 1997
|+++ tar-1.12/src/create.c	Mon Dec 15 17:50:48 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/lib/Makefile.am	Wed Apr 16 16:30:04 1997
|+++ tar-1.12/lib/Makefile.am	Mon Nov 17 06:45:43 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 36
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.h	Wed Apr 16 18:02:57 1997
|+++ tar-1.12/src/arith.h	Mon Nov 17 05:47:33 1997
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 66
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.c	Wed Apr 23 23:25:57 1997
|+++ tar-1.12/src/arith.c	Mon Nov 17 08:11:11 1997
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
can't find file to patch at input line 122
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure.in	Fri Apr 25 17:02:46 1997
|+++ tar-1.12/configure.in	Mon Nov 17 06:17:49 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 160
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/acconfig.h	Thu Apr 10 11:37:02 1997
|+++ tar-1.12/acconfig.h	Mon Nov 17 05:53:38 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 169
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure
|+++ tar-1.12/configure
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
==========================

PATCH COMMAND:  patch -p1 -g0 < /usr/local/portage/app-admin/amanda/files/tar-1.12.patch

==========================
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|The first hunk in this file was submitted by Craig Wiegert
|<[e-mail]>.  It fixed a problem that causes
|GNUTAR to issue error messages like the following for sparse files:
|
|> /bin/tar: Read error at byte 0, reading 512 bytes, in file ./var/log/lastlog: Bad file number
|
|The others fix an estimate problem in GNUTAR on SunOS 4.1.3, HP/UX and
|other systems whose C libraries do not support "%lld" in printf format
|strings for printing long long integers.
|
|--- tar-1.12/src/create.c	Mon Dec 15 17:26:47 1997
|+++ tar-1.12/src/create.c	Mon Dec 15 17:50:48 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/lib/Makefile.am	Wed Apr 16 16:30:04 1997
|+++ tar-1.12/lib/Makefile.am	Mon Nov 17 06:45:43 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 36
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.h	Wed Apr 16 18:02:57 1997
|+++ tar-1.12/src/arith.h	Mon Nov 17 05:47:33 1997
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 66
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.c	Wed Apr 23 23:25:57 1997
|+++ tar-1.12/src/arith.c	Mon Nov 17 08:11:11 1997
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
can't find file to patch at input line 122
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure.in	Fri Apr 25 17:02:46 1997
|+++ tar-1.12/configure.in	Mon Nov 17 06:17:49 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 160
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/acconfig.h	Thu Apr 10 11:37:02 1997
|+++ tar-1.12/acconfig.h	Mon Nov 17 05:53:38 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 169
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure
|+++ tar-1.12/configure
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
==========================

PATCH COMMAND:  patch -p2 -g0 < /usr/local/portage/app-admin/amanda/files/tar-1.12.patch

==========================
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|The first hunk in this file was submitted by Craig Wiegert
|<[e-mail]>.  It fixed a problem that causes
|GNUTAR to issue error messages like the following for sparse files:
|
|> /bin/tar: Read error at byte 0, reading 512 bytes, in file ./var/log/lastlog: Bad file number
|
|The others fix an estimate problem in GNUTAR on SunOS 4.1.3, HP/UX and
|other systems whose C libraries do not support "%lld" in printf format
|strings for printing long long integers.
|
|--- tar-1.12/src/create.c	Mon Dec 15 17:26:47 1997
|+++ tar-1.12/src/create.c	Mon Dec 15 17:50:48 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/lib/Makefile.am	Wed Apr 16 16:30:04 1997
|+++ tar-1.12/lib/Makefile.am	Mon Nov 17 06:45:43 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 36
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.h	Wed Apr 16 18:02:57 1997
|+++ tar-1.12/src/arith.h	Mon Nov 17 05:47:33 1997
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 66
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.c	Wed Apr 23 23:25:57 1997
|+++ tar-1.12/src/arith.c	Mon Nov 17 08:11:11 1997
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
missing header for unified diff at line 122 of patch
can't find file to patch at input line 122
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure.in	Fri Apr 25 17:02:46 1997
|+++ tar-1.12/configure.in	Mon Nov 17 06:17:49 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 160 of patch
can't find file to patch at input line 160
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/acconfig.h	Thu Apr 10 11:37:02 1997
|+++ tar-1.12/acconfig.h	Mon Nov 17 05:53:38 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 169 of patch
can't find file to patch at input line 169
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure
|+++ tar-1.12/configure
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
==========================

PATCH COMMAND:  patch -p3 -g0 < /usr/local/portage/app-admin/amanda/files/tar-1.12.patch

==========================
missing header for unified diff at line 13 of patch
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|The first hunk in this file was submitted by Craig Wiegert
|<[e-mail]>.  It fixed a problem that causes
|GNUTAR to issue error messages like the following for sparse files:
|
|> /bin/tar: Read error at byte 0, reading 512 bytes, in file ./var/log/lastlog: Bad file number
|
|The others fix an estimate problem in GNUTAR on SunOS 4.1.3, HP/UX and
|other systems whose C libraries do not support "%lld" in printf format
|strings for printing long long integers.
|
|--- tar-1.12/src/create.c	Mon Dec 15 17:26:47 1997
|+++ tar-1.12/src/create.c	Mon Dec 15 17:50:48 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 24 of patch
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/lib/Makefile.am	Wed Apr 16 16:30:04 1997
|+++ tar-1.12/lib/Makefile.am	Mon Nov 17 06:45:43 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 36 of patch
can't find file to patch at input line 36
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.h	Wed Apr 16 18:02:57 1997
|+++ tar-1.12/src/arith.h	Mon Nov 17 05:47:33 1997
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
missing header for unified diff at line 66 of patch
can't find file to patch at input line 66
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.c	Wed Apr 23 23:25:57 1997
|+++ tar-1.12/src/arith.c	Mon Nov 17 08:11:11 1997
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
missing header for unified diff at line 122 of patch
can't find file to patch at input line 122
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure.in	Fri Apr 25 17:02:46 1997
|+++ tar-1.12/configure.in	Mon Nov 17 06:17:49 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 160 of patch
can't find file to patch at input line 160
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/acconfig.h	Thu Apr 10 11:37:02 1997
|+++ tar-1.12/acconfig.h	Mon Nov 17 05:53:38 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 169 of patch
can't find file to patch at input line 169
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure
|+++ tar-1.12/configure
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
==========================

PATCH COMMAND:  patch -p4 -g0 < /usr/local/portage/app-admin/amanda/files/tar-1.12.patch

==========================
missing header for unified diff at line 13 of patch
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|The first hunk in this file was submitted by Craig Wiegert
|<[e-mail]>.  It fixed a problem that causes
|GNUTAR to issue error messages like the following for sparse files:
|
|> /bin/tar: Read error at byte 0, reading 512 bytes, in file ./var/log/lastlog: Bad file number
|
|The others fix an estimate problem in GNUTAR on SunOS 4.1.3, HP/UX and
|other systems whose C libraries do not support "%lld" in printf format
|strings for printing long long integers.
|
|--- tar-1.12/src/create.c	Mon Dec 15 17:26:47 1997
|+++ tar-1.12/src/create.c	Mon Dec 15 17:50:48 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 24 of patch
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/lib/Makefile.am	Wed Apr 16 16:30:04 1997
|+++ tar-1.12/lib/Makefile.am	Mon Nov 17 06:45:43 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 36 of patch
can't find file to patch at input line 36
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.h	Wed Apr 16 18:02:57 1997
|+++ tar-1.12/src/arith.h	Mon Nov 17 05:47:33 1997
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
missing header for unified diff at line 66 of patch
can't find file to patch at input line 66
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/src/arith.c	Wed Apr 23 23:25:57 1997
|+++ tar-1.12/src/arith.c	Mon Nov 17 08:11:11 1997
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
missing header for unified diff at line 122 of patch
can't find file to patch at input line 122
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure.in	Fri Apr 25 17:02:46 1997
|+++ tar-1.12/configure.in	Mon Nov 17 06:17:49 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 160 of patch
can't find file to patch at input line 160
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/acconfig.h	Thu Apr 10 11:37:02 1997
|+++ tar-1.12/acconfig.h	Mon Nov 17 05:53:38 1997
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 169 of patch
can't find file to patch at input line 169
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- tar-1.12/configure
|+++ tar-1.12/configure
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored