| 1 |
Yes, this is indeed not very good behaviour. It should be remedied along the |
| 2 |
sticky flag dependency development. Please submit the proper bug report (I |
| 3 |
did not find one in a quick search for "autoclean") so that this issue won't |
| 4 |
get forgotten. |
| 5 |
|
| 6 |
Meanwhile you should probably choose to stay clear from combining all three |
| 7 |
of: |
| 8 |
1. KEYWORDS="~arch" emerge pkgname (adding "~arch" to make.conf should be |
| 9 |
safe in *that* respect, though clearly you may not want to do this for other |
| 10 |
reasons) |
| 11 |
2. AUTOCLEAN="yes" and |
| 12 |
3. emerge -u world |
| 13 |
(basically, this is a classical "choose any two" situation). |
| 14 |
|
| 15 |
George |
| 16 |
|
| 17 |
|
| 18 |
On Sunday 15 December 2002 06:09, Cong wrote: |
| 19 |
> Recently portage behaves really strangely on my system. |
| 20 |
> When I do "emerge clean", Portage trys to clean newest packages |
| 21 |
> For example with phoenix-bin: |
| 22 |
> |
| 23 |
> # emerge net-www/phoenix-bin |
| 24 |
> SUCCESS |
| 25 |
> # emerge net-www/phoenix-bin -p |
| 26 |
> [ebuild R ] net-www/phoenix-bin-0.4-r2 |
| 27 |
> # emerge net-www/phoenix-bin -cp |
| 28 |
> |
| 29 |
> >>> These are the packages that I would unmerge: |
| 30 |
> |
| 31 |
> net-www/phoenix-bin |
| 32 |
> selected: 0.4-r2 |
| 33 |
> protected: 20021121 |
| 34 |
> omitted: none |
| 35 |
> |
| 36 |
> And the problem is that this happened with sys-apps/portage itself, |
| 37 |
> i.e, after upgrade previous version to portage-2.0.45-r5, portage |
| 38 |
> cleaned sys-apps/portage-2.0.45-r5 ( it tried to kept |
| 39 |
> sys-apps/portage-2.0.45-r4) and portage got broken. Same things |
| 40 |
> happened with almost all packages: gcc, glibc, xfree .... |
| 41 |
> |
| 42 |
> Now I am forced to put AUTOCLEAN="no" in /etc/make.conf . |
| 43 |
> |
| 44 |
> / Cong |
| 45 |
|
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives