ebuilds should not be running `env-update`. the PM already does that. it's just a waste of time. dev-db/hsqldb/hsqldb-1.8.1.2-r1.ebuild env-update dev-db/hsqldb/hsqldb-1.8.1.3.ebuild env-update mail-mta/netqmail/netqmail-1.05-r8.ebuild env-update mail-mta/netqmail/netqmail-1.05-r4.ebuild env-update mail-mta/netqmail/netqmail-1.06.ebuild env-update mail-mta/qmail-ldap/qmail-ldap-1.03-r8.ebuild env-update sci-chemistry/gromacs/gromacs-4.5.4-r1.ebuild env-update && source /etc/profile sci-chemistry/gromacs/gromacs-4.5.5-r1.ebuild env-update && source /etc/profile dev-lang/gpc/gpc-20070904.ebuild env-update dev-lang/gpc/gpc-20051104.ebuild env-update dev-lang/icc/icc-11.1.046-r2.ebuild env-update dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-4.0.ebuild env-update dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-4.1.ebuild env-update dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-3.2.ebuild env-update dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-3.1.ebuild env-update dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-3.0.ebuild env-update
(In reply to comment #0) > sci-chemistry/gromacs/gromacs-4.5.4-r1.ebuild env-update && source /etc/profile > sci-chemistry/gromacs/gromacs-4.5.5-r1.ebuild env-update && source /etc/profile Done.
dev-lang/gpc done
Can we prevent this in the future with something like qa_intercepters? -A
(In reply to comment #0) > dev-db/hsqldb/hsqldb-1.8.1.2-r1.ebuild env-update > dev-db/hsqldb/hsqldb-1.8.1.3.ebuild env-update Done.
yes, we should be able to add a repoman/ebuild check for this
dev-util/nvidia-cuda-toolkit fixed.
i did the qmail ones icc is only one left
(In reply to comment #7) > icc is only one left done
(In reply to comment #5) > yes, we should be able to add a repoman/ebuild check for this repoman check is in git now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9997bb9c81e0742060dc795e4e0397db4cbfb5c2
awesome. sounds like we're all set now. thanks all!