1830 – unbound local variable assignment in portage.py

Bug 1830 - unbound local variable assignment in portage.py

Summary: unbound local variable assignment in portage.py

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-04-16 05:34 UTC by Artem Baguinski
Modified:	2011-10-30 22:17 UTC (History)
CC List:	0 users

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

Attachments
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 Artem Baguinski 2002-04-16 05:34:43 UTC

i'm using portage 1.8.19
while qmerging ebuild (openquicktime-1.0, it's my own ebuild, not in portage
tree [yet?]) i've got an error:

[...unrelevant skipped...]
File "/usr/lib/python2.2/site-packages/portage.py", line 2984, in mergeme
  print zing,mydest
UnboundLocalError: local variable 'zing' referenced before assignment
[...end of qoute...]

i checked the file and indeed, zing is only assigned some value if moveme==true
(if moveme: at line 2977).

Comment 1 Artem Baguinski 2002-04-16 05:51:04 UTC

well, i also had a look what actually happend. indeed very strange thing. it
seems openquicktime's makefile is not very smart - when i tried DESTDIR approach
it tried to write outside it, when i tried to set prefix it just couldnt grasp
it correctly and created file '/usr/lib' (not directory, but file, whatever is
in it). it was when qmerging this wrong file that zing-error occured. this
doesnt make it less of a bug though. imho.

Comment 2 Ryan Phillips (RETIRED) gentoo-dev

2002-04-19 03:18:01 UTC

Resolved by a message from me in IRC.  Resolved in Portage 1.9.0