7090 – Errors when unmerging mod_php-4.2.2

Bug 7090 - Errors when unmerging mod_php-4.2.2

Summary: Errors when unmerging mod_php-4.2.2

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	x86 Linux

Importance:	High normal
Assignee:	Ryan Phillips (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-08-26 23:50 UTC by PJ
Modified:	2003-02-04 19:42 UTC (History)
CC List:	2 users (show)

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 PJ 2002-08-26 23:50:30 UTC

After updating mod_php-4.2.2 to mod_php-4.2.2-r1, emerge -c gave me the 
following error:

--- !empty dir /etc
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1311, in ?
    if 1==unmerge(myaction, myfiles):
  File "/usr/bin/emerge", line 1090, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1419, in unmerge
    mylink.delete()
  File "/usr/lib/python2.2/site-packages/portage.py", line 3146, in delete
    os.unlink(self.dbdir+"/"+x)
OSError: [Errno 21] Is a directory: '//var/db/pkg/dev-php/mod_php-4.2.2/files'

Comment 1 Duke 2002-08-27 00:31:16 UTC

Confirmed.
I got the exact same error after doing the same thing.

What happens now?  Is my portage system broken?  Has the mod_php been marked as
clean, or will I not be able to clean my system anymore (because this bug
prevents any packages below mod_php from being cleaned)?

Comment 2 Ryan Phillips (RETIRED) gentoo-dev

2002-09-03 15:41:49 UTC

It is most likely a problem on the ebuild blah config step of the
merge process... try moving away /var/db/pkg/dev-php/mod_php-4.2.2/files
and see if this solves the problem.