59394 – 2.0.51_pre15 traceback on emerge -fp

Bug 59394 - 2.0.51_pre15 traceback on emerge -fp

Summary: 2.0.51_pre15 traceback on emerge -fp

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:

Reported:	2004-08-04 06:29 UTC by Brian Harring (RETIRED)
Modified:	2004-08-11 11:26 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
portage.py-lock-fix.patch (patch,494 bytes, patch) 2004-08-04 06:39 UTC, Brian Harring (RETIRED)	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Brian Harring (RETIRED) gentoo-dev

2004-08-04 06:29:30 UTC

Logic error involving when listonly=True and use_locks=True
Corrected in cvs, opening this bug so users can get at the patch till pre16 is out.

the last few lines of the traceback are this-
  File "/usr/lib/portage/pym/portage.py", line 2296, in fetch
    unlockfile(file_lock)
  File "/usr/lib/portage/pym/portage.py", line 209, in unlockfile
    lockfilename,myfd,unlinkfile = mytuple
TypeError: unpack non-sequence

attaching a patch.

Comment 1 Brian Harring (RETIRED) gentoo-dev

2004-08-04 06:39:42 UTC

Created attachment 36746 [details, diff]
portage.py-lock-fix.patch

...and here she is.
Pardon the borkage :-/

Comment 2 Brian Harring (RETIRED) gentoo-dev

2004-08-11 11:26:01 UTC

Fixed in pre16.