When rebuilding mysql-python (required after an upgrade of mysql to V4) I found portage removing gimp-print - see emerge.log below. I am using portage-2.0.48-r1 Changing AUTOCLEAN="yes" to AUTOCLEAN="no" in make.conf stops this from happening. As I managed to kill the process before it had finished, portage still thinks that I have gimp-print installed (which I still partly do). By settng AUTOCLEAN back to yes and re-merging mysql-python I can reproduce this at any time. Should you require any more information, I will be happy to provide all I can. <--------- excerpt from emerge.log -----------------------> 1058650300: Started emerge on: Jul 19, 2003 22:31:40 1058650300: *** emerge mysql-python 1058650300: >>> emerge (1 of 1) dev-python/mysql-python-0.9.2-r1 to / 1058650300: === (1 of 1) Cleaning (/usr/portage/dev-python/mysql-python/mysql-python-0.9.2-r1.ebuild) 1058650301: === (1 of 1) Compiling/Merging (/usr/portage/dev-python/mysql-python/mysql-python-0.9.2-r1.ebuild) 1058650363: === (1 of 1) Updating world file (/usr/portage/dev-python/mysql-python/mysql-python-0.9.2-r1.ebuild) 1058650363: === (1 of 1) Post-Build Cleaning (/usr/portage/dev-python/mysql-python/mysql-python-0.9.2-r1.ebuild) 1058650365: >>> AUTOCLEAN: dev-python/mysql-python 1058650365: --- AUTOCLEAN: Nothing unmerged. 1058650365: ::: completed emerge (1 of 1) dev-python/mysql-python-0.9.2-r1 to / 1058650365: *** Finished. Cleaning up... 1058650416: === Unmerging... (media-gfx/gimp-print-4.2.1) 1058650535: *** terminating.
emerge info -v attach your world file /var/cache/edb/world ls -lR /var/db/pkg > pkg.db.lslR You can email those to me if you don't wish to post them.
Old.
