First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 37176
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 37132
Assigned To: Gentoo Linux bug wranglers <bug-wranglers@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: jochen <jochen.eisinger@gmx.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 37176 depends on: Show dependency tree
Bug 37176 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2004-01-04 04:14 0000
>>> md5 src_uri ;-) libpcap-0.8.1.tar.gz
>>> Unpacking source...
>>> Unpacking libpcap-0.8.1.tar.gz to /var/tmp/portage/libpcap-0.8.1/work
tar: Removing leading `libpcap-0.8.1/./' from member names
 * Applying libpcap-0.8.1-fPIC.patch...

 * Failed Patch: libpcap-0.8.1-fPIC.patch!
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/libpcap-0.8.1/temp/libpcap-0.8.1-fPIC.patch-4731.out


!!! ERROR: net-libs/libpcap-0.8.1 failed.
!!! Function epatch, Line 354, Exitcode 0
!!! Failed Patch: libpcap-0.8.1-fPIC.patch!

the contents of above file is:
-4731.out
***** libpcap-0.8.1-fPIC.patch *****

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

PATCH COMMAND:  patch  -p0 < /usr/portage/net-libs/libpcap/files/libpcap-0.8.1-fPIC.patch

====================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- Makefile.in        2004-01-03 12:51:50.914715352 +0000
|+++ Makefile.in        2004-01-03 13:04:17.524952464 +0000
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
====================================
etc ...

I guess that's caused because tar stripped of the leading directory name

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Remy Nicolas 2004-01-04 04:38:43 0000 -------
I've got the same :(

------- Comment #2 From Remy Nicolas 2004-01-04 04:46:48 0000 -------
look at http://bugs.gentoo.org/show_bug.cgi?id=37132 this corrected the problem
for me

------- Comment #3 From jochen 2004-01-04 04:55:38 0000 -------

*** This bug has been marked as a duplicate of 37132 ***

First Last Prev Next    No search results available      Search page      Enter new bug