From: ziggiman_REMOVEME@hotmail.com   
      
   "Michal Górny"  wrote in message   
   news:op.uhrq1esszfsi06@pomiot.cccp...   
   > On Sat, 20 Sep 2008 02:11:12 +0200, ZiGGi    
   > wrote:   
   >   
   >> When I am doing an 'emerge --sync' it fails with the following error:   
   >>   
   >>>>> Updating Portage cache:   89%Traceback (most recent call last):   
   >>   File "/usr/bin/emerge", line 6971, in    
   >>     retval = emerge_main()   
   >>   File "/usr/bin/emerge", line 6926, in emerge_main   
   >>     action_sync(settings, trees, mtimedb, myopts, myaction)   
   >>   File "/usr/bin/emerge", line 5409, in action_sync   
   >>     action_metadata(settings, portdb, myopts)   
   >>   File "/usr/bin/emerge", line 5503, in action_metadata   
   >>     eclass_cache=ec, verbose_instance=noise_maker)   
   >>   File "/usr/lib/portage/pym/cache/util.py", line 43, in mirror_cache   
   >>     trg = trg_cache[x]   
   >>   File "/usr/lib/portage/pym/cache/flat_hash.py", line 28, in __getitem__   
   >>     d = self._parse_data(myf, cpv)   
   >>   File "/usr/lib/portage/pym/cache/flat_hash.py", line 43, in _parse_data   
   >>     d = dict(map(lambda x:x.rstrip("\n").split("=", 1), data))   
   >>   
   >> I have tried recovering the portage tree etc. but nothing seems to work.   
   >> Any   
   >> ideas are highly appreciated!   
   >   
   > Maybe some ebuild in some overlay is broken?   
   >   
   > Well, try upgrading portage. I think it should work even with unfinished   
   > cache.   
   >   
   > --   
   > Best regards,   
   > Michal Górny   
   >   
   >    
   >    
      
   I have tried to emerge a new portage which completed without errors. I have   
   even done a manual installation of a "rescue portage" - but nothing has   
   changed :-(   
      
   Thx for the suggestion, though! :-)   
      
   /Michael   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)