| 1 |
Recently portage behaves really strangely on my system. |
| 2 |
When I do "emerge clean", Portage trys to clean newest packages |
| 3 |
For example with phoenix-bin: |
| 4 |
|
| 5 |
# emerge net-www/phoenix-bin |
| 6 |
SUCCESS |
| 7 |
# emerge net-www/phoenix-bin -p |
| 8 |
[ebuild R ] net-www/phoenix-bin-0.4-r2 |
| 9 |
# emerge net-www/phoenix-bin -cp |
| 10 |
|
| 11 |
>>> These are the packages that I would unmerge: |
| 12 |
|
| 13 |
net-www/phoenix-bin |
| 14 |
selected: 0.4-r2 |
| 15 |
protected: 20021121 |
| 16 |
omitted: none |
| 17 |
|
| 18 |
And the problem is that this happened with sys-apps/portage itself, |
| 19 |
i.e, after upgrade previous version to portage-2.0.45-r5, portage |
| 20 |
cleaned sys-apps/portage-2.0.45-r5 ( it tried to kept |
| 21 |
sys-apps/portage-2.0.45-r4) and portage got broken. Same things |
| 22 |
happened with almost all packages: gcc, glibc, xfree .... |
| 23 |
|
| 24 |
Now I am forced to put AUTOCLEAN="no" in /etc/make.conf . |
| 25 |
|
| 26 |
/ Cong |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives