I keep getting messages about sed being called in global scope from portage, even though the ebuilds never call sed, and the eclasses don't either. This usually happens for ebuilds in overlays. See example output below: openlab ~ $ emerge -NDuavt world These are the packages that would be merged, in reverse order: Calculating dependencies | * QA Notice: 'sed' called in global scope: dev-libs/vc-9999 \ * QA Notice: 'sed' called in global scope: app-shells/bash-completion-2.1_p20141224 \ * QA Notice: 'sed' called in global scope: sci-physics/root-6.04.00 / * QA Notice: 'sed' called in global scope: sys-libs/ncurses-6.0-r1 \ * QA Notice: 'sed' called in global scope: sci-physics/geant-4.10.02_beta01 - * QA Notice: 'sed' called in global scope: sci-physics/root-9999 \ * QA Notice: 'sed' called in global scope: app-shells/bash-4.3_p30-r1 \ * QA Notice: 'sed' called in global scope: sci-physics/root-6.03.04 - * QA Notice: 'sed' called in global scope: sci-physics/root-6.03.02 \ * QA Notice: 'sed' called in global scope: sci-physics/geant-4.10.01_p02 | * QA Notice: 'sed' called in global scope: sys-libs/readline-6.3_p8-r1 \ * QA Notice: 'sed' called in global scope: sys-libs/ncurses-5.9-r101 - * QA Notice: 'sed' called in global scope: sys-libs/ncurses-5.9-r5 ... done! [ebuild U ] sys-devel/gdb-7.10-r1::gentoo_prefix [7.10::gentoo_prefix] USE="client expat lzma nls python server zlib -multitarget {-test} -vanilla" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_3 -python3_4" 0 KiB [nomerge ] app-portage/gentoolkit-dev-0.3.0::gentoo_prefix USE="{-test}" PYTHON_TARGETS="python2_7 python3_3 -python3_4" [nomerge ] dev-lang/python-2.7.10:2.7::gentoo_prefix USE="gdbm ipv6 ncurses readline sqlite ssl threads (wide-unicode) xml (-aqua) (-berkdb) -build -doc -examples -hardened -tk -wininst" [nomerge ] app-admin/python-updater-0.13::gentoo_prefix [nomerge ] sys-apps/portage-2.2.20::gentoo_prefix USE="(ipc) -build -doc -epydoc -prefix-chaining (-pypy2_0) -python2 -python3 (-selinux) -xattr" LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_3 -pypy1_9 (-pypy2_0) (-python2_6) -python3_1 (-python3_2) -python3_4" [nomerge ] app-misc/pax-utils-0.8.1::gentoo_prefix USE="python -caps" [nomerge ] dev-python/pyelftools-0.23-r1::gentoo_prefix USE="-examples" PYTHON_TARGETS="python2_7 python3_3 -python3_4" [nomerge ] dev-lang/python-3.3.3:3.3::gentoo_prefix USE="gdbm ipv6 ncurses readline sqlite ssl threads xml (-aqua) -build -crypt -doc -examples -hardened -nis -tk -wininst" [nomerge ] dev-libs/openssl-1.0.2d::gentoo_prefix USE="asm tls-heartbeat zlib -bindist -gmp -kerberos -rfc3779 -sctp -static-libs {-test} -vanilla" CPU_FLAGS_X86="(sse2)" [ebuild U ] app-misc/ca-certificates-20150426.3.20::gentoo_prefix [20141019.3.19-r1::gentoo_prefix] USE="cacert -libressl" 7,089 KiB [ebuild U ] app-arch/xz-utils-5.2.2::gentoo_prefix [5.2.1-r1::gentoo_prefix] USE="nls threads -static-libs" 1,430 KiB Total: 3 packages (3 upgrades), Size of downloads: 8,519 KiB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests Reproducible: Always
Something must be calling sed, because this QA notice is only triggered when something calls it. Do you have anything in /etc/portage/bashrc?
No, I have no bashrc file for portage. Something may be calling sed, but it is definitely not in the ebuilds, where it is being reported. If you have any more suspects I should check, let me know. I could not figure it out yet.
Another strange thing is that these warnings only show sometimes. If I press control-C and run the same emerge command again, the warnings go away. They only show once when I run repoman too. I always run repoman twice now, to make sure the warnings are just the spurious ones.
(In reply to Guilherme Amadio from comment #3) > Another strange thing is that these warnings only show sometimes. If I press > control-C and run the same emerge command again, the warnings go away. They > only show once when I run repoman too. I always run repoman twice now, to > make sure the warnings are just the spurious ones. That's expected, because the QA notice is only triggered when it's generating cache. After the cache is written in /var/cache/edb/dep, it won't be re-generated until it becomes stale due to modification of an ebuild or eclass.
(In reply to Zac Medico from comment #4) > That's expected, because the QA notice is only triggered when it's > generating cache. After the cache is written in /var/cache/edb/dep, it won't > be re-generated until it becomes stale due to modification of an ebuild or > eclass. Thank you for the explanation. I've since moved to use hasufell's portage git configuration [1] and have not seen these messages show up anymore. 1. https://github.com/hasufell/portage-gentoo-git-config
