Re: [gentoo-dev] AUTOCLEAN="yes" destroyed my system (was Re: [gentoo-dev] Portage wants to downgrade)

[George Shapovalov <george@gentoo.org>]

Yes, this is indeed not very good behaviour. It should be remedied along the 
sticky flag dependency development. Please submit the proper bug report (I 
did not find one in a quick search for "autoclean") so that this issue won't 
get forgotten.

Meanwhile you should probably choose to stay clear from combining all three 
of:
1. KEYWORDS="~arch" emerge pkgname   (adding "~arch" to make.conf should be 
safe in *that* respect, though clearly you may not want to do this for other 
reasons)
2. AUTOCLEAN="yes" and
3. emerge -u world
(basically, this is a classical "choose any two" situation).

George


On Sunday 15 December 2002 06:09, Cong wrote:
> Recently portage behaves really strangely on my system.
> When I do "emerge clean", Portage trys to clean newest packages
> For example with phoenix-bin:
>
> # emerge net-www/phoenix-bin
> SUCCESS
> # emerge net-www/phoenix-bin -p
> [ebuild   R  ] net-www/phoenix-bin-0.4-r2
> # emerge net-www/phoenix-bin -cp
>
> >>> These are the packages that I would unmerge:
>
>  net-www/phoenix-bin
>     selected: 0.4-r2
>    protected: 20021121
>      omitted: none
>
> And the problem is that this happened with sys-apps/portage itself,
> i.e, after upgrade previous version to portage-2.0.45-r5, portage
> cleaned sys-apps/portage-2.0.45-r5 ( it tried to kept
> sys-apps/portage-2.0.45-r4) and portage got broken. Same things
> happened with almost all packages: gcc, glibc, xfree ....
>
> Now I am forced to put AUTOCLEAN="no" in /etc/make.conf .
>
> / Cong


--
gentoo-dev@gentoo.org mailing list