Failed to open Portfile from registry

[Ryan Schmidt]

On Apr 23, 2010, at 17:42, Rainer Müller wrote:
> On 2010-04-24 00:29 , Ryan Schmidt wrote:
>> When upgrading a port in a MacPorts prefix that had been running a
>> prior version of trunk and which I just updated to the latest, I get
>> this warning:
>> 
>> $ sudo /x86_64-10.6-mp/bin/port -u upgrade zlib
>> --->  Computing dependencies for zlib
>> --->  Fetching zlib
>> --->  Verifying checksum(s) for zlib
>> --->  Extracting zlib
>> --->  Applying patches to zlib
>> --->  Configuring zlib
>> --->  Building zlib
>> --->  Staging zlib into destroot
>> --->  Computing dependencies for zlib
>> --->  Installing zlib @1.2.5_0
>> Warning: Failed to open Portfile from registry for zlib @1.2.4_1
>> --->  Deactivating zlib @1.2.4_1
>> --->  Activating zlib @1.2.5_0
>> --->  Cleaning zlib
>> Warning: Failed to execute portfile from registry for zlib @1.2.4_1
>> --->  Uninstalling zlib @1.2.4_1
>> 
>> 
>> Is this expected?
> 
> Yes. After you converted your registry to the sqlite format there are no
> Portfiles stored in the registry as that did not exist in the old
> format. Conversion stores an empty string instead, resulting in this
> warning as this is not a valid Portfile.

Ok. Is that really the experience we want for users? Users who upgrade from one version of MacPorts to the next don't expect to get all these warnings they didn't get before. If we keep this warning as is, I think we'll get to explain this situation over and over on the mailing list.