Re: Compilation warnings in jbsockets.c

On 2013-03-07, at 8:44 AM, Ian Silvester wrote:

> 
> On 2013-03-07, at 7:14 AM, Fabian Keil wrote:
> 
>> Ian Silvester <[email protected]> wrote:
>> 
>>> The failure is something you might be interested in though Fabian since it has arisen
>>> since 3.0.20. My default OS X config now serves the user manual locally, and test 591
>>> fails as follows:
>>> 
>>> ./privoxy-regression-test.pl --privoxy-address 127.0.0.1:8118 --show-skipped-tests --max-level 109
>>> 2013-03-06 15:49:05: Asking Privoxy for the number of action files available ...
>>> 2013-03-06 15:49:05: Gathering regression tests from 4 action file(s) delivered by Privoxy 3.0.21.
>>> 2013-03-06 15:49:05: Executing regression tests ...
>> [...]
>>> 2013-03-06 15:49:14: Ooops. We expected status code 200, but received: 500.
>>> 2013-03-06 15:49:14: Failure for test 591. URL 'http://p.p/user-manual/p_doc.css' and expected status code '200'
>>> 2013-03-06 15:49:15: Executed 667 regression tests. Skipped 13. 666 successes, 1 failures.
>>> 
>>> My config is as follows:
>>> 
>>> user-manual /usr/local/share/doc/privoxy/user-manual/ 
>>> 
>>> p_doc.css is in the base folder for documentation (/usr/local/share/doc/privoxy),
>>> not in the user-manual subfolder. Is this related to the documentation cleanup
>>> you've done since 3.0.20 or something at my end?
>> 
>> How was the user-manual directory populated?
> 
> My package builder modue includes a script I wrote that simply copies the /doc hierarchy as-is to the correct location in the OS X package hierarchy.

Or, rather, the /doc/webserver hierarchy plus the correct selection of files from current (AUTHORS ChangeLog LICENSE README).

Ian

>> 
>> In the repository we have only one p_doc.css file and the
>> "install" target is responsible for copying it into both
>> the doc and the doc/user-manual directories.
>> 
>> If you aren't using the "install" target for your packages
>> you'll have to add the file manually.
> 
> Well well, what a winding way to have found a bug in my packaging!! And yet another last-minute fix for 3.0.21 ;o)
> 
> Ian
> 
> 
> 
>> Fabian
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
>> endpoint security space. For insight on selecting the right partner to 
>> tackle endpoint security challenges, access the full report. 
>> http://p.sf.net/sfu/symantec-dev2dev_______________________________________________
>> Ijbswa-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
> 
> 
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
> endpoint security space. For insight on selecting the right partner to 
> tackle endpoint security challenges, access the full report. 
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Ijbswa-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev