Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 361804 Details for
Bug 489276
app-emulation/vmware-modules-279.0 - Failed Patch: 279-3.10.0.patch !
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Patch output.
279-3.10.0.patch.out (text/plain), 11.99 KB, created by
Dave Mak
on 2013-10-24 17:02:08 UTC
(
hide
)
Description:
Patch output.
Filename:
MIME Type:
Creator:
Dave Mak
Created:
2013-10-24 17:02:08 UTC
Size:
11.99 KB
patch
obsolete
>***** 279-3.10.0.patch ***** >PWD: /var/tmp/portage/app-emulation/vmware-modules-279.0/work > >============================ > >PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.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: >-------------------------- >|--- a/vmnet-only/bridge.c >|+++ b/vmnet-only/bridge.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 134 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/driver.c >|+++ b/vmnet-only/driver.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 228 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/hub.c >|+++ b/vmnet-only/hub.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 367 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/netif.c >|+++ b/vmnet-only/netif.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 497 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/procfs.c >|+++ b/vmnet-only/procfs.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 662 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/userif.c >|+++ b/vmnet-only/userif.c >-------------------------- >No file to patch. Skipping patch. >5 out of 5 hunks ignored >can't find file to patch at input line 758 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/vnetInt.h >|+++ b/vmnet-only/vnetInt.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 788 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|-- >|--- a/vmblock-only/linux/control.c 2013-05-21 19:21:19.165750556 +0200 >|+++ b/vmblock-only/linux/control.c 2013-05-21 19:22:18.363747723 +0200 >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored > >patch program exited with status 1 >============================ > >PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.patch' > >============================ >patching file vmnet-only/bridge.c >Hunk #3 FAILED at 364. >Hunk #4 succeeded at 1762 (offset -2 lines). >1 out of 4 hunks FAILED -- saving rejects to file vmnet-only/bridge.c.rej >patching file vmnet-only/driver.c >patching file vmnet-only/hub.c >Hunk #4 FAILED at 400. >Hunk #5 FAILED at 408. >Hunk #6 succeeded at 730 (offset -2 lines). >2 out of 6 hunks FAILED -- saving rejects to file vmnet-only/hub.c.rej >patching file vmnet-only/netif.c >Hunk #3 FAILED at 225. >Hunk #4 succeeded at 595 (offset -3 lines). >1 out of 4 hunks FAILED -- saving rejects to file vmnet-only/netif.c.rej >patching file vmnet-only/procfs.c >Hunk #1 FAILED at 45. >Hunk #2 FAILED at 71. >Hunk #3 FAILED at 94. >Hunk #4 FAILED at 116. >Hunk #5 succeeded at 303 (offset 102 lines). >Hunk #6 FAILED at 254. >5 out of 6 hunks FAILED -- saving rejects to file vmnet-only/procfs.c.rej >patching file vmnet-only/userif.c >Hunk #1 succeeded at 388 (offset -1 lines). >Hunk #2 succeeded at 402 (offset -1 lines). >Hunk #3 succeeded at 426 (offset -1 lines). >Hunk #4 FAILED at 1039. >Hunk #5 FAILED at 1048. >2 out of 5 hunks FAILED -- saving rejects to file vmnet-only/userif.c.rej >patching file vmnet-only/vnetInt.h >Hunk #1 FAILED at 171. >Hunk #2 succeeded at 210 (offset 14 lines). >1 out of 2 hunks FAILED -- saving rejects to file vmnet-only/vnetInt.h.rej >patching file vmblock-only/linux/control.c > >patch program exited with status 1 >============================ > >PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.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: >-------------------------- >|--- a/vmnet-only/bridge.c >|+++ b/vmnet-only/bridge.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 134 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/driver.c >|+++ b/vmnet-only/driver.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 228 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/hub.c >|+++ b/vmnet-only/hub.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 367 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/netif.c >|+++ b/vmnet-only/netif.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 497 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/procfs.c >|+++ b/vmnet-only/procfs.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 662 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/userif.c >|+++ b/vmnet-only/userif.c >-------------------------- >No file to patch. Skipping patch. >5 out of 5 hunks ignored >can't find file to patch at input line 758 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/vnetInt.h >|+++ b/vmnet-only/vnetInt.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 788 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|-- >|--- a/vmblock-only/linux/control.c 2013-05-21 19:21:19.165750556 +0200 >|+++ b/vmblock-only/linux/control.c 2013-05-21 19:22:18.363747723 +0200 >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored > >patch program exited with status 1 >============================ > >PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.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: >-------------------------- >|--- a/vmnet-only/bridge.c >|+++ b/vmnet-only/bridge.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 134 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/driver.c >|+++ b/vmnet-only/driver.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 228 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/hub.c >|+++ b/vmnet-only/hub.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 367 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/netif.c >|+++ b/vmnet-only/netif.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 497 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/procfs.c >|+++ b/vmnet-only/procfs.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 662 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/userif.c >|+++ b/vmnet-only/userif.c >-------------------------- >No file to patch. Skipping patch. >5 out of 5 hunks ignored >can't find file to patch at input line 758 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/vnetInt.h >|+++ b/vmnet-only/vnetInt.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 788 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|-- >|--- a/vmblock-only/linux/control.c 2013-05-21 19:21:19.165750556 +0200 >|+++ b/vmblock-only/linux/control.c 2013-05-21 19:22:18.363747723 +0200 >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored > >patch program exited with status 1 >============================ > >PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.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: >-------------------------- >|--- a/vmnet-only/bridge.c >|+++ b/vmnet-only/bridge.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 134 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/driver.c >|+++ b/vmnet-only/driver.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 228 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/hub.c >|+++ b/vmnet-only/hub.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 367 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/netif.c >|+++ b/vmnet-only/netif.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 497 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/procfs.c >|+++ b/vmnet-only/procfs.c >-------------------------- >No file to patch. Skipping patch. >6 out of 6 hunks ignored >can't find file to patch at input line 662 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/userif.c >|+++ b/vmnet-only/userif.c >-------------------------- >No file to patch. Skipping patch. >5 out of 5 hunks ignored >can't find file to patch at input line 758 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- a/vmnet-only/vnetInt.h >|+++ b/vmnet-only/vnetInt.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 788 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|-- >|--- a/vmblock-only/linux/control.c 2013-05-21 19:21:19.165750556 +0200 >|+++ b/vmblock-only/linux/control.c 2013-05-21 19:22:18.363747723 +0200 >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored > >patch program exited with status 1
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 489276
: 361804