[MacPorts] #24656: DEBUG: Backtrace: Is a directory

[MacPorts]

#24656: DEBUG: Backtrace: Is a directory
-----------------------------------------+----------------------------------
  Reporter:  Andreas.Krueger2@…          |       Owner:  macports-tickets@…                   
      Type:  defect                      |      Status:  closed                               
  Priority:  Normal                      |   Milestone:                                       
 Component:  ports                       |     Version:  1.8.2                                
Resolution:  worksforme                  |    Keywords:                                       
      Port:  py25-distribute             |  
-----------------------------------------+----------------------------------

Comment(by Andreas.Krueger2@…):

 I did what you told me.

 {{{
 DEBUG: Adding file to file_map: /opt/local/lib/python2.5/site-
 packages/setuptools-0.6c11-py2.5.egg-info for: py25-distribute
 DEBUG: Is a directory
     while executing
 "filemap set file_map $file $port"
     (procedure "receipt_flat::register_file" line 11)
     invoked from within
 "${macports::registry.format}::register_file $file $port"
     (procedure "registry::register_file" line 3)
     invoked from within
 "registry::register_file $file $name"
     (procedure "portimage::activate" line 63)
     invoked from within
 "portimage::activate $portname [composite_version $portversion [array get
 variations]] [array get options]"
 Error: port activate failed: Is a directory
 }}}

 I then manually deleted the "setuptools-0.6c11-py2.5.egg-info" - which by
 the way was NOT a directory.

 And then simply started it again:

 {{{
 bash-3.2# port -d activate py25-distribute
 --->  Activating py25-distribute
 DEBUG: Image error: py25-distribute @0.6.10_0 is already active.
     while executing
 "portimage::activate $portname [composite_version $portversion [array get
 variations]] [array get options]"
 Error: port activate failed: Image error: py25-distribute @0.6.10_0 is
 already active.
 bash-3.2#
 }}}

 BUT:
 Why is it already active, if the above resulted in an error first?

 ...

 How can I trust the current state of my system now?

 ...

 What is the recipe to redo the whole thing reliably?

-- 
Ticket URL: <http://trac.macports.org/ticket/24656#comment:8>
MacPorts <http://www.macports.org/>
Ports system for Mac OS