searching an interesting behavior about p5-DBD-Pg ports and tinderbox

[olli hauer]

On 2011-01-07 15:28, Joe Marcus Clarke wrote:
> On 1/2/11 3:59 PM, olli hauer wrote:
>> Hi,
>>
>> I'm searching an interesting behavior for the database/p5-DBD-Pg port.
>>
>> If I build the port manual in the ports directory it choose the
>> postgresql84-client. But when I build the port in tinderbox it choose
>> the postgresql90-client port ...
>>
>> I stopped the build with a .sleepme file chrooted into the build
>> and looked for the following vars.
>>
>> # cd database/p5-DBD-Pg
>> # make -V DEFAULT_PGSQL_VER
>> 84
>> # make -V PGSQL_VER
>> 90
>>
>>
>> Then I have deinstalled the postgresql90-client inside the build and got.
>>
>> # make -V DEFAULT_PGSQL_VER
>> 84
>> # make -V PGSQL_VER
>> 84
>>
>>
>> Second test with deleting all packages/logs and a tbcleanup same results.
>>
>>
>> PS:
>> - etc/env is empty
>> - no make.conf
> 
> Could the Build have been dirty in some way?  Are you using OPTIONS in TB?
> 
> Joe
> 


No, no options for this build.
I guess I found the issue but not really sure about.

I have on this machine some builds.

build 7.3-prod:
 with options and custom make.conf to override defaults
 to apache22, pgsql84 ...

build 7.3-test:
 with options synced from 7.3-prod and custom make.conf
 to override default to apache22, pgsql90 ...

build 7.3-porter:
 no options, no make.conf no etc/env

As I remember I build the specific port first on 7.3-test and have then
done the following in the webinterface for this port
 7.3-test => 7.3-porter => save => reset status

But even after deleting the queue, the port/packages from 7.3-porter and
tbcleanup I got the same results.

The only solution was to drop the database and and restore to a dump
I made early the day, cleanup the build/Makefile ...

--
olli