Summary: | ebuilds running `env-update` in pkg_* funcs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | Current packages | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dev-portage |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
2012-02-06 03:14:46 UTC
(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! |