38267 – Cannot unmerge ('mycpv' is not defined)

Bug 38267 - Cannot unmerge ('mycpv' is not defined)

Summary: Cannot unmerge ('mycpv' is not defined)

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-01-15 01:58 UTC by Jonas Bofjäll
Modified:	2004-01-15 07:04 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 Jonas Bofjäll 2004-01-15 01:58:14 UTC

Python 2.3.3. 'emerge --version' outputs this:
Portage 2.0.50_pre14 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.6.1-mm2)

I get an error on 'emerge -C'. Although files are properly remobed, the package is not de-registered in Portage. I have no idea what have caused this. If I try, all files are removed properly, lockfile is removed, and then BANG just when I thought it ought to be ready:

Traceback (most recent call last):
  File "/usr/bin/emerge", line 2194, in ?
    if 1==unmerge(myaction, myfiles):
  File "/usr/bin/emerge", line 1746, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root,mysettings,unmerge_action not in ["clean","prune"])
  File "/usr/lib/portage/pym/portage.py", line 2256, in unmerge
    mylink.unmerge(trimworld=mytrimworld,cleanup=1)
  File "/usr/lib/portage/pym/portage.py", line 5310, in unmerge
    elif (len(matches)==1) and (matches[0]==mycpv):
NameError: global name 'mycpv' is not defined


Reproducible: Always
Steps to Reproduce:



Expected Results:

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2004-01-15 07:04:06 UTC

was fixed in _pre15, so `emerge --sync; emerge portage`