Re: [privoxy-devel] Release date for Privoxy 3.0.23 stable

[Ian S. <ian...@fa...>]

Okay am building fine now that the repository is tagged - will kill my 
HEAD checkout and recreated it from scratch.

Unfortunately now regression testing is failing and I am mystified as to 
why:

<snip>$ ./privoxy-regression-test.pl
2015-01-25 16:09:12: Asking Privoxy for the number of action files 
available ...
2015-01-25 16:09:13: Fetch failure: 'curl: (6) Couldn't resolve host 'p.p''
2015-01-25 16:09:13: Fetch failure: 'curl: (6) Couldn't resolve host 'p.p''
2015-01-25 16:09:13: Oh noes. Running curl failed 1 times in a row. Last 
error: 'curl: (6) Couldn't resolve host 'p.p''. Fatal error. Exiting.

Privoxy 3.0.23 is installed and running, and browsing to http://p.p/ 
returns the status page as per usual. Using curl to some other address 
at the command prompt works and is being routed through Privoxy as one 
would expect (the number of requests increments on 
http://config.privoxy.org/show-status) but for some reason Privoxy is 
not intercepting p.p when it is curled from the commandline. My hosts 
file has no entries for p.p by the way.

Any suggestions gratefully received,

Ian



On 15-01-25 12:12 PM, Fabian Keil wrote:
> Ian Silvester <ian...@fa...> wrote:
>
>> On 15-01-25 9:55 AM, Lee wrote:
>>> On 1/25/15, Ian Silvester <ian...@fa...> wrote:
>>>> On 15-01-24 12:33 PM, Fabian Keil wrote:
>>>>> Fabian Keil <fk...@fa...> wrote:
>>>>>
>>>>>>> I'd like to release Privoxy 3.0.23 stable around 2015-01-24
>>>>>>> as a bug fix release.
>>>>> Thanks for the feedback.
>>>>>
>>>>> I uploaded a potential release tarball to:
>>>>> http://www.privoxy.org/downloads/privoxy-3.0.23-stable-src.tar.gz
>>>>> http://www.privoxy.org/downloads/privoxy-3.0.23-stable-src.tar.gz.asc
>>>>>
>>>>> Please let me know if there are any issues.
>>>> 'Scuse ignorance but does your providing a source tarball suggest that I
>>>> can't build from CVS?
> It mainly suggests that Sourceforge did not let me upload it to the
> project page ...
>
>>> I would suggest not using CVS for anything but interim/test releases.
>> I use a clean checkout for releases using the tag since that is the
>> jumping-off point for all distributed files, source or otherwise, but
>> until the repository's tagged I can't do that ;o)
> It's tagged now, so you could try again.
>
> If you previously checked out HEAD (currently the same as v_3_0_23) you
> should already have gotten the latest configure.in, though, and it's not
> obvious to me why your checkout did not contain the file at all.
>
>>> If you build from the source tarball anyone can duplicate your work.
>>> If you build from CVS... who knows what's in your CVS tree.
>> I do, so it's up to me to make sure it's clean I guess :o/ I'll try a
>> build from the tarball later on (family commitments for a few hours now)
>> and see if I get a different result.
>>
>> Fabian if you've a comment I'd be interested; if memory serves there
>> were some changes to the build files for this release? Or was that for
>> 3.0.22?
> I'm not sure what changes you are referring to. I consider configure.in
> a build file, but it has to be changed for every release to bump the version.
>
> Fabian
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
>
>
> _______________________________________________
> Ijbswa-developers mailing list
> Ijb...@li...
> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers