On 07/21/03 reg hughson wrote: > After doing an emerge a few days ago, now whenever I use emerge to do > anything, I now get this: > > Performing Global Updates: /usr/portage/profiles/updates/3Q-2003 > (Could take a couple minutes if you have a lot of binary packages.) > .='update pass' *='binary update' @='/var/db move' > .Traceback (most recent call last): > File "/usr/bin/emerge", line 13, in ? > import portage > File "/usr/lib/python2.2/site-packages/portage.py", line 5032, in ? > do_upgrade(mykey) > File "/usr/lib/python2.2/site-packages/portage.py", line 4966, in > do_upgrade > db["/"]["bintree"].move_ent(mysplit) > File "/usr/lib/python2.2/site-packages/portage.py", line 3814, in > move_ent > self.populate() > File "/usr/lib/python2.2/site-packages/portage.py", line 3893, in > populate > if (not os.path.isdir(self.pkgdir+"/All") and not getbinpkg): > NameError: global name 'getbinpkg' is not defined > > > what happened and how can I fix it?
If you have portage-2.0.48-r4 update to -r5 (using "ebuild /usr/portage/sys-apps/portage/portage-2.0.48-r5.ebuild merge") Marius -- [EMAIL PROTECTED] mailing list
