| 1 |
On Thu, 12 Oct 2006 10:58:18 +0200 |
| 2 |
Bo Ørsted Andresen <bo.andresen@××××.dk> wrote: |
| 3 |
> It really would help if we knew what version you were running. Try |
| 4 |
> this: |
| 5 |
> |
| 6 |
> # emerge -u portage |
| 7 |
|
| 8 |
owl ~ # emerge -pu portage |
| 9 |
|
| 10 |
These are the packages that would be merged, in order: |
| 11 |
|
| 12 |
Calculating dependencies... done! |
| 13 |
|
| 14 |
> # emerge -u python |
| 15 |
|
| 16 |
owl ~ # emerge -pu python |
| 17 |
|
| 18 |
These are the packages that would be merged, in order: |
| 19 |
|
| 20 |
Calculating dependencies... done! |
| 21 |
[ebuild U ] dev-libs/openssl-0.9.8d [0.9.7j] USE="-sse2%" |
| 22 |
[ebuild U ] sys-libs/ncurses-5.5-r3 [5.5-r2] USE="gpm* -trace%" |
| 23 |
[ebuild U ] dev-lang/python-2.4.3-r4 [2.4.3-r1] USE="-tk%" |
| 24 |
|
| 25 |
|
| 26 |
(Emerged python with -u) |
| 27 |
|
| 28 |
> # python-updater |
| 29 |
|
| 30 |
owl ~ # python-updater |
| 31 |
* Can't determine any previous Python version(s). |
| 32 |
|
| 33 |
> # revdep-rebuild |
| 34 |
|
| 35 |
owl ~ # revdep-rebuild -p |
| 36 |
Configuring search environment for revdep-rebuild |
| 37 |
|
| 38 |
Checking reverse dependencies... |
| 39 |
|
| 40 |
Packages containing binaries and libraries broken by a package update |
| 41 |
will be emerged. |
| 42 |
|
| 43 |
Collecting system binaries and libraries... done. |
| 44 |
(/root/.revdep-rebuild.1_files) |
| 45 |
|
| 46 |
Collecting complete LD_LIBRARY_PATH... done. |
| 47 |
(/root/.revdep-rebuild.2_ldpath) |
| 48 |
|
| 49 |
Checking dynamic linking consistency... |
| 50 |
done. |
| 51 |
(/root/.revdep-rebuild.3_rebuild) |
| 52 |
|
| 53 |
Assigning files to ebuilds... Nothing to rebuild |
| 54 |
|
| 55 |
Evaluating package order... done. |
| 56 |
(/root/.revdep-rebuild.5_order) |
| 57 |
|
| 58 |
Dynamic linking on your system is consistent... All done. |
| 59 |
|
| 60 |
> If after that you still see the above behaviour: |
| 61 |
> |
| 62 |
> # emerge --debug -S netrw &> debug.log |
| 63 |
> # gzip debug.log |
| 64 |
> |
| 65 |
> Then attach debug.log.gz and post that together with the output of: |
| 66 |
> |
| 67 |
> # emerge --info |
| 68 |
|
| 69 |
owl ~ # emerge -S netrw |
| 70 |
Searching... |
| 71 |
[ Results for search key : netrw ] |
| 72 |
[ Applications found : 0 ] |
| 73 |
|
| 74 |
There is no netrw in portage tree. XD |
| 75 |
|
| 76 |
But thanks guys, it will help me in some way, now emerge -S netrw does |
| 77 |
not Segmentation Fault. |
| 78 |
|
| 79 |
Seems to solved. |
| 80 |
|
| 81 |
-- |
| 82 |
Wagner Vaz |
| 83 |
Blog: http://wagnervaz.wordpress.com |
| 84 |
Linux User: #372744 |
| 85 |
GPG Key: B4D1B312 | Keyserver: subkeys.pgp.net |
Archives