Bug 485006 – sys-apps/portage-2.2.5 traceback on any operation - TypeError: unorderable types: NoneType() < str()

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Michael Palimaka (kensington) 2013-09-15 13:56:53 UTC]

Since 2.2.5, any portage operation instantly fails with this traceback:

Traceback (most recent call last):
  File "/usr/bin/emerge", line 50, in <module>
    retval = emerge_main()
  File "/usr/lib64/portage/pym/_emerge/main.py", line 1015, in emerge_main
    action=myaction, args=myfiles, opts=myopts)
  File "/usr/lib64/portage/pym/portage/proxy/objectproxy.py", line 31, in __call__
    return result(*args, **kwargs)
  File "/usr/lib64/portage/pym/_emerge/actions.py", line 3226, in load_emerge_config
    **portage._native_kwargs(kwargs))
  File "/usr/lib64/portage/pym/portage/__init__.py", line 582, in create_trees
    env=env, eprefix=eprefix)
  File "/usr/lib64/portage/pym/portage/package/ebuild/config.py", line 519, in __init__
    self['PORTAGE_REPOSITORIES'] = self.repositories.config_string()
  File "/usr/lib64/portage/pym/portage/repository/config.py", line 920, in config_string
    for repo_name, repo in sorted(self.prepos.items()):
TypeError: unorderable types: NoneType() < str()

[Comment 1 Zac Medico 2013-09-15 14:11:55 UTC]

This is fixed in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9e1d8136e644281729e278b68e6272ab2954ee6f

[Comment 2 Zac Medico 2013-09-15 14:21:56 UTC]

This is fixed in 2.2.6.