1 |
Anyone else seen this? Any solutions? |
2 |
|
3 |
Thanks, |
4 |
Mark |
5 |
|
6 |
lightning ~ # emerge portage |
7 |
Calculating dependencies... done! |
8 |
>>> Verifying ebuild Manifests... |
9 |
>>> starting parallel fetching pid 27419 |
10 |
|
11 |
>>> Emerging (1 of 3) app-admin/eselect-1.0.11-r1 to / |
12 |
* eselect-1.0.11.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] |
13 |
* checking ebuild checksums ;-) ... [ ok ] |
14 |
* checking auxfile checksums ;-) ... [ ok ] |
15 |
* checking miscfile checksums ;-) ... [ ok ] |
16 |
* checking eselect-1.0.11.tar.bz2 ;-) ... [ ok ] |
17 |
>>> Unpacking source... |
18 |
>>> Unpacking eselect-1.0.11.tar.bz2 to /var/tmp/portage/app-admin/eselect-1.0.11-r1/work |
19 |
* Applying eselect-1.0.11-fix-paludis-command.patch ... [ ok ] |
20 |
>>> Source unpacked. |
21 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
22 |
* is known to be triggered by things such as failed variable assignments |
23 |
* (bug #190128) or bad substitution errors (bug #200313). |
24 |
|
25 |
* Messages for package app-admin/eselect-1.0.11-r1: |
26 |
|
27 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
28 |
* is known to be triggered by things such as failed variable assignments |
29 |
* (bug #190128) or bad substitution errors (bug #200313). |
30 |
lightning ~ # |