Daniel Macks wrote:
> On Tue, Mar 18, 2008 at 09:06:50AM -0400, Alexander Hansen wrote:
>   
>> Daniel Macks wrote:
>>     
>>> On Sun, Mar 16, 2008 at 10:04:50AM -0700, Trevor Harmon wrote:
>>>   
>>>       
>>>> On Mar 16, 2008, at 7:11 AM, Martin Costabel wrote:
>>>>
>>>>     
>>>>         
>>>>> OSX 10.5.2 update, perhaps?
>>>>>       
>>>>>           
>>>> No, that was released on February 11. The package was working fine  
>>>> with it. I'm pretty sure it was a change in Fink that's causing this  
>>>> problem.
>>>>     
>>>>         
>>> You probably still have the older fink package in /sw/fink/debs; you
>>> can "sudo dpkg -i fink-whatever.deb" to upgrade and downgrade manually
>>> and find out exactly whether that's what matters.
>>>
>>> dan
>>>
>>>   
>>>       
>> One can't do _much_ of a downgrade in this case.  As committed from the 
>> tracker, the package declared a BuildDepend on fink ( >= 0.27.99 ).  I 
>> tried building with fink-0.28.0 on 10.5.2 w/affiliated stuff current as 
>> of midnight, which resulted in the same failure as with fink-0.28.1 .
>>     
>
> The BuildDepends:fink(>= 0.28) is only due to the private Shlibs;
> since it appears we're talking about a build error (i.e., well before
> the .deb gets created) , you can safely remove that BDep entirely.
>
> FWIW, I didn't test this submission...was a minor-version update to an
> existing package with minimal interaction with other packages, assumed
> that if it worked for submitter when submitted, it was good to go.
>
> dan
>
>   
I tried a local modification and a build with fink-0.27.11 on 10.5.2 .  
That still didn't work, failing identically to the prior cases.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel

Reply via email to