Summary: | --sync --> KeyError: 'porttree' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | selckin |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | denys.duchier, dkarasik, gentoo-bugs, gentoo, hkbst, iaindb, ikelos, m.debruijne, mmokrejs, pqGungnir, schulz.benjamin |
Priority: | High | Keywords: | InVCS, REGRESSION |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077 | ||
Attachments: | fix the KeyError |
Description
selckin
2008-08-28 12:20:44 UTC
Created attachment 163998 [details, diff]
fix the KeyError
If this patch is saved as /tmp/sync_keyerror.patch, then it can be applied as follows:
patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/sync_keyerror.patch
Note that the KeyError after sync is relatively harmless since the only things that remain to do before emerge exits there are the news and the optional post_sync hook that may be located in /etc/portage/bin/.
*** Bug 236024 has been marked as a duplicate of this bug. *** q: Updating ebuild cache ... q: Finished 25242 entries in 0.425519 seconds Traceback (most recent call last): File "/usr/bin/emerge", line 18, in <module> retval = _emerge.emerge_main() File "/usr/lib/portage/pym/_emerge/__init__.py", line 13618, in emerge_main action_sync(settings, trees, mtimedb, myopts, myaction) File "/usr/lib/portage/pym/_emerge/__init__.py", line 11399, in action_sync display_news_notification(root_config, myopts) File "/usr/lib/portage/pym/_emerge/__init__.py", line 10711, in display_news_notification portdb = trees["porttree"].dbapi File "/usr/lib/portage/pym/portage/util.py", line 1082, in __getitem__ return dict.__getitem__(self, item_key) KeyError: 'porttree' # patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/sync_keyerror.patch patching file /usr/lib/portage/pym/_emerge/__init__.py Hunk #1 succeeded at 11373 (offset -130 lines). # Seems to fix the issue so that the next "emerge --sync" finished. This is fixed in 2.2_rc9. |