Group file and registry warnings when upgrading swig-python

Ryan Schmidt ryandesign at macports.org
Sun Apr 29 15:38:08 PDT 2012


On Apr 23, 2012, at 12:11, Adam Mercer wrote:

> On updating a couple of my machines today I saw the following:
> 
> --->  Computing dependencies for swig-python
> --->  Fetching swig-python
> --->  Verifying checksum(s) for swig-python
> --->  Extracting swig-python
> --->  Configuring swig-python
> --->  Building swig-python
> --->  Staging swig-python into destroot
> --->  Installing swig-python @2.0.5_0
> --->  Cleaning swig-python
> --->  Computing dependencies for swig-python
> Warning: Group file could not be located.
> Warning: Failed to open Portfile from registry for swig-python @2.0.4_0
> --->  Deactivating swig-python @2.0.4_0
> --->  Activating swig-python @2.0.5_0
> --->  Cleaning swig-python
> Warning: Group file could not be located.
> Warning: Failed to open Portfile from registry for swig-python @2.0.4_0
> --->  Uninstalling swig-python @2.0.4_0

Me too.


> Are these warnings anything to worry about?

No, it's only because the old port had been installed before you were using the sqlite registry (i.e. before you upgraded to MacPorts 2).





More information about the macports-users mailing list