Steve Cohen wrote:
> Kenneth Porter wrote:
>
>> --On Monday, February 07, 2005 6:14 PM -0600 Steve Cohen
>> <scohen@javactivity.org> wrote:
>>
>>> my question is really more on the conceptual level. We are building a
>>> binary rpm from a source rpm. As far as rpmbuild knows, subversion has
>>> not even been deployed yet. So why would such tests be expected to
>>> work?
>>
>>
>>
>> It looks like a server is set up to listen on a user port for purposes
>> of testing. This server need not be in the final location to work.
>>
>> Do you have a firewall up on the build system? Perhaps blocking port
>> 15835 on the loopback interface is preventing the tests from
>> succeeding. My firewall includes a rule that allows all connections on
>> interface "lo".
>>
>> Note that there's not really anything special here about the use of
>> rpmbuild. You'd run into the same issue with "make test" when building
>> from the tarball. The rpm build system just wraps all the unpacking,
>> patching, making, and building the binary container in a simple
>> command. It captures and documents all the steps the tarball user
>> would have to perform "by hand".
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
>>
> Thanks, but I don't think it's a firewall issue. I don't have one. This
> is basically a home PC that runs Linux. It is protected from the
> outside world by a broadband router with a firewall, but I think this
> just affects eth0, not lo. Or do I have that wrong?? At any rate,
> iptables is running on my system but is set to allow everything.
>
> I googled "localhost:15835" and find a few references, all having to do
> with subversion.
>
> Most notably, I find this:
> http://www.endrun.org/xr/svn/source/subversion/tests/clients/cmdline/README
>
> where it says
> "If you run httpd on a port other than 80, you can specify the port in
> the URL: "http://localhost:15835" for example."
> Earlier in the doc, it says "Httpd should be running on port 80."
>
> So my question is why the default spec file that comes with the source
> rpm uses this odd value? Is someone deliberately trying to make this
> difficult? Or is there actually some significance to port 15835? I
> have modified the specfile so it no longer points there. We shall see
> what that does.
>
>
No, that isn't it either. It now appears that port 15835 is specified
in basic_tests.py as the port to listen on. So that makes sense as the
port to be specified in the spec.
I think that what the test is trying to tell me is that something is
wrong with my apache setup. Still don't know what, though.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 8 04:44:40 2005