On Saturday 30 April 2005 22:18, Richard Watson wrote:
Failed to write to mtimedb: 'module' object has no attribute
'HIGHEST_PROTOCOL'
That would be due to running python-2.2. Although, the portage-2.0.51.19
ebuild is meant to detect the use of python-2.2 and patch accordingly.
Perhaps you
I just tried to emerge sync an install I did off a stage 3 LiveCD I bought
during 2004. I'm getting some strange results. Can anyone tell me what the
output below is telling me. I tried running fixpackages but that did not
fix it. Now when I try and emerge any package portage keeps trying to sync
On Saturday 30 April 2005 17:40, Richard Watson wrote:
I just tried to emerge sync an install I did off a stage 3 LiveCD I bought
during 2004. I'm getting some strange results. Can anyone tell me what the
output below is telling me. I tried running fixpackages but that did not
fix it. Now
In either case, relink /etc/make.profile
to /usr/portage/profiles/default-x86-2004.2. Then ignore the deprecation
notice and above slotmove error until you've upgraded portage to 2.0.51.
Regards,
Jason Stubbs
Hi Jason - thanks. I did what you suggested and it sort of fixed the
problem. However
On Saturday 30 April 2005 22:18, Richard Watson wrote:
Failed to write to mtimedb: 'module' object has no attribute
'HIGHEST_PROTOCOL'
That would be due to running python-2.2. Although, the portage-2.0.51.19
ebuild is meant to detect the use of python-2.2 and patch accordingly.
Perhaps you
5 matches
Mail list logo
