| Summary: | sys-apps/portage-2.2_rc1: Python error in elog_process during upgrade to portage 2.2 | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Martin von Gagern <Martin.vGagern> |
| Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Please post the output of ls -l /var/tmp/portage/sys-apps/portage*/temp/logging (In reply to comment #0) > File "/usr/lib/portage/pym/portage.py", line 506, in elog_process > msgfunction, msgtype = f.split(".") > ValueError: need more than 1 value to unpack This appears to be triggered by the format change of the elog files. In 2.2, the elog functions store the messages differently. Note that >=portage-2.1.4 is immune to this issue since they don't rely on compatibility of the scripts in /usr/lib/portage/bin when upgrading portage. Instead, >=portage-2.1.4 creates a copy of it's own scripts in a temp directory, and it uses those to perform the upgrade without needing to be concerned about such compatibility problems. Considering that >=2.1.4.4 has been stable for a long time and it will be included in the 2008.0 stages, I think we can just ignore this bug. |
Updating from portage-2.1.3.19 to portage-2.2_rc1 I got this error: >>> sys-apps/portage-2.2_rc1 merged. Traceback (most recent call last): File "/usr/bin/emerge", line 6518, in ? File "/usr/bin/emerge", line 6512, in emerge_main File "/usr/bin/emerge", line 5971, in action_build File "/usr/bin/emerge", line 3833, in merge File "/usr/lib/portage/pym/portage.py", line 4543, in merge mydbapi=mydbapi, prev_mtimes=prev_mtimes) File "/usr/lib/portage/pym/portage.py", line 8822, in merge elog_process(self.mycpv, self.settings) File "/usr/lib/portage/pym/portage.py", line 506, in elog_process msgfunction, msgtype = f.split(".") ValueError: need more than 1 value to unpack As this was a live system, this message was somewhat scary, as I feared an incomplete portage installation or migration. I merged it once more to be sure, which seemed to work well enough. So I hope this was only a problem with portage restarting itself or some such.