558 2009-01-08 10:14:00 +0000 Portato fails on startup - only on Sabayon 2009-02-09 15:54:55 +0000 1 1 1 Unclassified Sabayon Installed Legacy (3.x) PC Linux RESOLVED WONTFIX P5 normal Current Stable 1 gentoo sabayonlinux joost.ruis 1595 gentoo 2009-01-08 10:14:54 +0000 I get about 10 mails per day stating, that portato fails (mostly on first startup). The error log is: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/portato/gui/windows/main.py", line 1247, in cb_pkg_list_selection self.fill_version_list(self.selCP) File "/usr/lib/python2.5/site-packages/portato/gui/windows/main.py", line 929, in fill_version_list packages = system.sort_package_list(system.find_packages(cp, masked=True)) File "/usr/lib/python2.5/site-packages/portato/backend/portage/system.py", line 213, in find_packages return self.geneticize_list(self._get_set(pkgSet).find(key, masked, with_version, only_cpv), only_cpv or not with_version) File "/usr/lib/python2.5/site-packages/portato/backend/portage/system.py", line 169, in geneticize_list return [self.new_package(x) for x in list_of_packages] File "/usr/lib/python2.5/site-packages/portato/backend/portage/system_22.py", line 64, in new_package return PortagePackage_22(cpv) File "/usr/lib/python2.5/site-packages/portato/backend/portage/package.py", line 54, in __init__ self._init_settings(True) File "/usr/lib/python2.5/site-packages/portato/backend/portage/package.py", line 79, in _init_settings self._settings.settings.setcpv(self.get_cpv(), mydb = dbapi) File "/usr/lib/portage/pym/portage/__init__.py", line 1968, in setcpv for k, v in izip(aux_keys, mydb.aux_get(self.mycpv, aux_keys)): File "/usr/lib/portage/pym/portage/dbapi/porttree.py", line 406, in aux_get raise KeyError(mycpv) KeyError: 'app-portage/portato-0.7.5' Portato version: 0.11.1 Python version: 2.5.2 (r252:60911, Nov 20 2008, 20:10:49) [GCC 4.3.2] Used backend: Portage 2.2_rc14 pygtk: 2.13.0 (using GTK+: 2.14.5) pygobject: 2.15.4 (using GLib: 2.18.3) Asking several of the bug filers, it seems to _only_ happen on Sabayon (esp. Live-DVD (4?)). As portato-0.7.5 is ... well ... outdated, I suppose, there might be something wrong with the portage cache. I'll look into this later on. Just as a "tracker" bug for the moment. 1596 gentoo 2009-01-08 10:16:24 +0000 Beside the component stating "Live DVD/CD", it also happens on (freshly) installed systems. 1607 gentoo 2009-01-10 20:13:12 +0000 The problem on the Live DVD is, that there is no portage-tree included. Thus it is quite obvious why portato (and some other related tools) fail. Solutions: Either include a portage snapshot - or no portage tools at all in the Live DVD. 1618 gentoo 2009-01-14 00:09:18 +0000 This should really get fixed. I spoke to several people, which thought "oh my god - a buggy release. lets look for another distribution" 1622 gentoo 2009-01-14 21:40:08 +0000 Seems to be the same error on install: There is no portage tree existing. Running "emerge --sync" to get one fixed the errors. 1624 joost.ruis 2009-01-19 10:49:56 +0000 (In reply to comment #4) > Seems to be the same error on install: There is no portage tree existing. > Running "emerge --sync" to get one fixed the errors. > You cannot built in an extra check (maybe run once) to check and see if an emerge --sync is needed? We expect our users todo this after they install Sabayonlinux. Reason to have it like this is to save some extra space on the ISO. 1625 gentoo 2009-01-19 14:00:13 +0000 I now added this check ;)