| 1 |
On Tue, 24 Apr 2007 15:24:52 +0530 (IST), AIT Gentoo User wrote: |
| 2 |
|
| 3 |
Because it makes posts harder to follow. |
| 4 |
Why? |
| 5 |
Please don't top-post. |
| 6 |
|
| 7 |
> i sync it for the latest portage. kde-base/kde-env****ebuild not in that |
| 8 |
> portage.so how to unmerge it? |
| 9 |
|
| 10 |
Did you delete the folder from /var/db or move it? If the latter, move it |
| 11 |
back and "emerge --unmerge kde-env". If the former, you've broken the |
| 12 |
package database and it will be hard to remove the files as portage now |
| 13 |
thinks they are not installed. |
| 14 |
|
| 15 |
> >> i removed kdelibs but not workd.finaly i removed |
| 16 |
> >> /var/db/pkg/kde-base/kde-env<****> folder. & tried. it worked. |
| 17 |
> > |
| 18 |
> > That only removed the database entry for kde-env, not kde-env itself. |
| 19 |
> > The correct solution was to emerge --unmerge kde-env. It doesn't |
| 20 |
> > matter that the ebuild is no longer in the portage tree, because |
| 21 |
> > portage stores a copy of the ebuild used to install a package |
| 22 |
> > in /var/db/pkg and uses that to unmerge. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
Don't hate yourself in the morning, sleep until noon. |
Archives