These are my features in /etc/make.conf: FEATURES="fixpackages deplclean keepwork keeptemp collision-protect parallel-fetch" Since I'm using parallel-fetch I get a strange error during some merges. For example, when some package for some reason does not want to merge (eg. postgres - because it needs to have the database backed up) I usually type: emerge --resume --skipfirst Fix what is to be fixed and get an emerge again. Now, while parallel-fetch is on, it seems that emerge mixes the list of packages to merge and I have to emerge --resume --skipfirst the same package many times (eg. postgres). Here are some logs: 1136449821: >>> AUTOCLEAN: sys-apps/shadow 1136449827: === Unmerging... (sys-apps/shadow-4.0.13) 1136449831: >>> unmerge success: sys-apps/shadow-4.0.13 1136449831: ::: completed emerge (2 of 11) sys-apps/shadow-4.0.14 to / 1136449831: >>> emerge (3 of 11) dev-db/postgresql-8.1.1 to / 1136449831: === (3 of 11) Cleaning (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136449832: === (3 of 11) Compiling/Merging (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136449834: *** terminating. 1136449834: *** terminating. 1136449956: Started emerge on: Jan 05, 2006 09:32:36 1136449956: *** emerge --resume --skipfirst 1136449956: *** Resuming merge... 1136449956: >>> emerge (1 of 10) sys-apps/shadow-4.0.14 to / 1136449956: === (1 of 10) Cleaning (sys-apps/shadow-4.0.14::/mnt/hda4/portage/sys-apps/shadow/shadow-4.0.14.ebuild) 1136449957: === (1 of 10) Compiling/Merging (sys-apps/shadow-4.0.14::/mnt/hda4/portage/sys-apps/shadow/shadow-4.0.14.ebuild) 1136450031: === (1 of 10) Post-Build Cleaning (sys-apps/shadow-4.0.14::/mnt/hda4/portage/sys-apps/shadow/shadow-4.0.14.ebuild) 1136450032: >>> AUTOCLEAN: sys-apps/shadow 1136450032: --- AUTOCLEAN: Nothing unmerged. 1136450032: ::: completed emerge (1 of 10) sys-apps/shadow-4.0.14 to / 1136450032: >>> emerge (2 of 10) dev-db/postgresql-8.1.1 to / 1136450032: === (2 of 10) Cleaning (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136450033: === (2 of 10) Compiling/Merging (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136450034: *** terminating. 1136450034: *** terminating. 1136450041: Started emerge on: Jan 05, 2006 09:34:01 1136450041: *** emerge --resume --skipfirst 1136450041: *** Resuming merge... 1136450041: >>> emerge (1 of 9) dev-db/postgresql-8.1.1 to / 1136450041: === (1 of 9) Cleaning (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136450042: === (1 of 9) Compiling/Merging (dev-db/postgresql-8.1.1::/mnt/hda4/portage/dev-db/postgresql/postgresql-8.1.1.ebuild) 1136450043: *** terminating. 1136450043: *** terminating. 1136450054: Started emerge on: Jan 05, 2006 09:34:14 1136450054: *** emerge --resume --skipfirst 1136450055: *** Resuming merge... 1136450055: >>> emerge (1 of 8) app-text/poppler-0.4.3-r3 to / As you can see - shadow and postgres where supposed to be merged at least twice.
Created attachment 76216 [details, diff] emerge-mtimedb.patch Try this please.
I tested it now quickly, but I'll have to observe how portage/emerge works for some time and give you an answer. It worked this time (didn't want to fetch postgres again). I'll wait for a bigger update maybe, unless you have any other ideas.
el commito'd
Fixed in r2534 and released in 2.1_pre4.
