After a recent upgrade to portage 2.1-r2, I was getting progessively worse errors emerging updates, finally culminating in an inability to emerge anything, the script bombing out complaining that "myfavdmct.values in line 1930 not defined". On a hunch, I vim'd emerge, saw the function in line 1930, then searched to see where it was defined, and found this was the only instance in the script. Then searched for "myfavd" and saw all entries were "myfavdict". Changed 1930 to this function and all seems to work now.
Must be a local problem on your side, just remerged 2.1-r2 on one of my systems and didn't see a "myfavdmct" anywhere. If this really was "getting progessively worse" it could be hardware related.
Not experiencing these problems myself but looks like you made a typo: chaza@Mars ~ $ grep myfavdict /usr/bin/emerge myfavdict=genericdict(myfavs) if (not mysysdict.has_key(myfavkey)) and (not myfavdict.has_key(myfavkey)): myfavdict[myfavkey]=myfavkey "\n".join(myfavdict.values())) myfavdict=genericdict(myfavs) if (not mysysdict.has_key(myfavkey)) and (not myfavdict.has_key(myfavkey)): myfavdict[myfavkey]=myfavkey "\n".join(myfavdict.values())) chaza@Mars ~ $ grep myfavdmct /usr/bin/emerge chaza@Mars ~ $ chaza@Mars ~ $ emerge --version Portage 2.1.1_pre5 (default-linux/x86/2006.0, gcc-4.1.1/vanilla, glibc-2.4.20060329-r0, 2.6.17-gentoo-r4 i686)
