Re: bug in slocate after 1.3.1 upgrade

Paul Guyot wrote:
> Fixed.
> Please don't use upgrade with ports that aren't installed.
> 
> Paul
> 
> Le 1 août 06 à 04:58, Juan Manuel Palacios a écrit :
> 
>>
>>
>>     Hmmm, I can't repro this. I see you're using autoclean, right? I 
>> enabled it on my installation but things worked flawlessly. Mind 
>> giving us a bit more info on your system and dp installation and using 
>> the -d flag for debugging output? Please uninstall the port and clean 
>> everything before you try again.
>>
>>     Thanks,...
>>
>> -jmpp
>>
>>
>>
>> On Jul 31, 2006, at 3:16 PM, Artemio Gonzalez Lopez wrote:
>>
>>> After the 1.3.1 upgrade,
>>>
>>> sudo port -vuf upgrade slocate
>>>
>>> fails at the very end with the following error message:
>>>
>>>
>>> --->  Activating slocate 3.1_0
>>> --->  Cleaning slocate
>>> --->  Removing workpath for slocate
>>> can't read "variant": no such variable
>>>     while executing
>>> "set oldvariant $variant"
>>>     (procedure "darwinports::upgrade" line 200)
>>>     invoked from within
>>> "darwinports::upgrade $portname "port:$portname" [array get 
>>> variations] [array get options]"
>>>     ("uplevel" body line 9)
>>>     invoked from within
>>> "uplevel 1 $block"
>>>     (procedure "foreachport" line 16)
>>>     invoked from within
>>> "foreachport $portlist {
>>>                 # Merge global variations into the variations 
>>> specified for this port
>>>                 foreach { variation value } [array get global_variat..."
>>>     (procedure "action_upgrade" line 3)
>>>     invoked from within
>>> "$action_proc $action $portlist [array get global_options]"
>>>     (procedure "process_cmd" line 49)
>>>     invoked from within
>>> "process_cmd $remaining_args"
>>>     invoked from within
>>> "if { [llength $remaining_args] > 0 } {
>>>
>>>         # If there are remaining arguments, process those as a command
>>>
>>>         # Exit immediately, by default, unless we'r..."
>>>     (file "/opt/local/bin/port" line 2565)
>>>
>>>
>>> Although the bug is relatively harmless ("port installed slocate" 
>>> shows the new version of the port as active, and the only consequence 
>>> seems to be that the work directory is not removed at the end), I 
>>> thought this might be worth reporting just in case it messes up with 
>>> other ports.
>>>
>>> Cheers,
>>>
>>> Artemio
>>>
>>> _______________________________________________
>>> Darwinports mailing list
>>> [email protected]
>>> http://www.opendarwin.org/mailman/listinfo/darwinports
>>
>> _______________________________________________
>> Darwinports mailing list
>> [email protected]
>> http://www.opendarwin.org/mailman/listinfo/darwinports
> 
> --Ministre ultraplénipotentiaire en disponibilité.
> Mobile. Sans baignoire fixe.
> http://www.kallisys.com/
> http://www-poleia.lip6.fr/~guyot/

Paul,

The slocate port was actually installed before I tried to upgrade it. 
Here's the actual sequence of commands I executed (after upgrading to 
1.3.1):

pb-g4:~ artemio$ port outdated
The following installed ports are outdated:
slocate                        2.7_2 < 3.1_0
pb-g4:~ artemio$ sudo port -vuf upgrade slocate

Thanks,

Artemio