+++ This bug was initially created as a clone of Bug #297933 +++ bash-4.1 introduces a new read-only variable (BASHOPTS). it'll need to be filtered when saving/restoring the environment. i dont know how you guys manage these save/restore steps, but portage shows multiple: /var/tmp/portage/app-shells/bash-4.1_rc1/temp/environment: line 7: declare: BASHOPTS: readonly variable you'll probably want to get this fixed before bash-4.1 is released and i add to the tree ... ------------------------ Emerged app-shells/bash-4.1_p2 and after it whenever I try to emerge ANYTHING ELSE I get this bloody error.
error: "BASHOPTS:readonly variable"
Created attachment 221241 [details] build.log
(In reply to comment #0) > Emerged app-shells/bash-4.1_p2 and after it whenever I try to emerge ANYTHING > ELSE I get this bloody error. The bash-4.1_p2 ebuild has a !<sys-apps/portage-2.1.7.16 blocker which prevents it from being installed incompatible versions of portage. I guess somehow you got it installed with older portage?
Created attachment 221253 [details] build.log
Yea.. somehow.. maybe tree was buggy, what should I do now to fix it?
You can try replacing /bin/bash with a compatible version. Maybe you can find a compatible binary in the tinderbox: http://tinderbox.dev.gentoo.org/default-linux/x86/app-shells/bash-4.0_p35.tbz2 http://tinderbox.dev.gentoo.org/default-linux/amd64/app-shells/bash-4.0_p35.tbz2 You can use tar to extract the package and then manually copy /bin/bash out of it.
