I have fvwm installed and have EwmhBaseStruts set up in ~/.fvwm/config like below SetEnv strut.left 0 SetEnv strut.right 0 SetEnv strut.top 0 SetEnv strut.bottom 0 EwmhBaseStruts $[strut.left] $[strut.right] $[strut.top] $[strut.bottom] unmerging net-misc/tor seems to stumble on these declarations as the log below shows cat /var/log/portage/net-misc:tor-0.1.2.17:20080225-153322.log /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 218: strut.bottom=0: command not found /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 219: strut.left=0: command not found /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 220: strut.right=0: command not found /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 221: strut.top=0: command not found /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 4130: declare: `strut.bottom=0': not a valid identifier /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 4131: declare: `strut.left=0': not a valid identifier /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 4132: declare: `strut.right=0': not a valid identifier /var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment: line 4133: declare: `strut.top=0': not a valid identifier * * ERROR: net-misc/tor-0.1.2.17 failed. * Call stack: * ebuild.sh, line 1641: Called die * The specific snippet of code: * preprocess_ebuild_env || \ * die "error processing environment" * The die message: * error processing environment * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/net-misc:tor-0.1.2.17:20080225-153322.log'. * The ebuild environment file is located at '/var/tmp/binpkgs/net-misc/tor-0.1.2.17/temp/environment'. * FROM THE EBUILD ENVIRONMENT declare -x strut.bottom="0" declare -x strut.left="0" declare -x strut.right="0" declare -x strut.top="0" Reproducible: Always Steps to Reproduce: 1. setup fvwm to use EwmhBaseStruts like shown above (or perhaps simply declare a variable 'test.variable="0"') 2. unmerge net-misc/tor Actual Results: fails like shown in description Expected Results: no other ebuild ever stumbled on these declarations so why should tor? Easy Workaround available, just unset the variables and unmerge tor -> so just a minor bug
This is not a tor bug at all; portage is saving way too much stuff to environment.bz2, leading to problem like this or Bug 211178 *** This bug has been marked as a duplicate of bug 56407 ***
