RE: [gentoo-user] emerge sync - portage: Update type slotmove not recognized. - !!! No profile directory; system mode unavailable.
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 have both 2.2 and 2.3 installed? Well I think I got there ... Thanks for all your help. Richard -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.0 - Release Date: 29/04/2005 -- gentoo-user@gentoo.org mailing list
[gentoo-user] emerge sync - portage: Update type slotmove not recognized. - !!! No profile directory; system mode unavailable.
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 (again I think) and fails the package installation. The output I'm confused about is: portage: Update type slotmove not recognized. !!! No profile directory; system mode unavailable. I'm a bit stuck at the moment so any help would be greatly appreciated. Regards, Richard === Output Below === Performing Global Updates: /usr/portage/profiles/updates/4Q-2004 (Could take a couple minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' .portage: Update type slotmove not recognized. ...portage: Update type slotmove not recognized. portage: Update type slotmove not recognized. ..* Done. ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the tbz2's in the packages directory. Note: This can take a very long time. portage: Update type slotmove not recognized. !!! No profile directory; system mode unavailable. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.0 - Release Date: 29/04/2005 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge sync - portage: Update type slotmove not recognized. - !!! No profile directory; system mode unavailable.
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 when I try and emerge any package portage keeps trying to sync (again I think) and fails the package installation. The output I'm confused about is: portage: Update type slotmove not recognized. This would probably indicate portage-2.0.50. !!! No profile directory; system mode unavailable. Did you get a deprecation notice and change the /etc/make.profile symlink? Is the CD anything other than 2004.2? 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 pgpll6ipA3lm4.pgp Description: PGP signature
RE: [gentoo-user] emerge sync - portage: Update type slotmove not recognized. - !!! No profile directory; system mode unavailable.
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 when I now run (after updating portage) emerge -s portage I get the following output. I'm interested in the message Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Plus why does it keep streaming this output? Thanks, Richard Start Output = # emerge -s portage Performing Global Updates: /usr/portage/profiles/updates/3Q-2002 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/4Q-2002 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' ... Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/1Q-2003 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' .. Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/2Q-2003 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/3Q-2003 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' .. Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/4Q-2003 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' . Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/1Q-2004 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' . Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/2Q-2004 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' Failed to write to mtimedb: 'module' object has no attribute 'HIGHEST_PROTOCOL' Performing Global Updates: /usr/portage/profiles/updates/3Q-2004 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' . Failed to write to mtimedb: 'module' object
Re: [gentoo-user] emerge sync - portage: Update type slotmove not recognized. - !!! No profile directory; system mode unavailable.
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 have both 2.2 and 2.3 installed? Regards, Jason Stubbs pgpwfpCa3MNBB.pgp Description: PGP signature
