[Gluster-devel] autobuild fails because of network

Niels de Vos ndevos at redhat.com
Tue Nov 19 11:18:55 UTC 2013

On Tue, Nov 19, 2013 at 04:19:53PM +0530, Vijay Bellur wrote:
> On 11/19/2013 04:10 PM, Emmanuel Dreyfus wrote:
> >On Tue, Nov 19, 2013 at 11:22:25AM +0100, Niels de Vos wrote:
> >>I've now disabled (hopefully) any proxy directives in
> >>/etc/mock/site-defaults.cfg.
> >>http://build.gluster.org/job/regression/2638/ should be the first run
> >>that explicitly disables any proxy servers.
> >>
> >>/me crosses his fingers
> >
> >I still have network-related failure:
> >http://build.gluster.org/job/regression/2637/consoleFull
> >
> While we continue to investigate the 404 issue, I am inclined to
> provide Verified: +1 to this and other related patches manually as
> none of the changes by Emmanuel should affect rpmbuild. Does that
> seem fine?

Yes, I was thinking the same :)

However, no 404 errors in 
http://build.gluster.org/job/regression/2638/console. Only the EPEL-5 
build failed, EPEL-6 passed. The error in the build.log shows this:

    + ./autogen.sh
    ... GlusterFS autogen ...
    The following build tools are missing:
      * python
    Please install them and try again.

It seems that "env python --version" does not work on EPEL-5:

    $ env python --version
    Unknown option: --
    Unknown option: -e
    Unknown option: -r
    Unknown option: -s
    Unknown option: -o
    Unknown option: -n
    Unknown option: --
    usage: python [option] ... [-c cmd | -m mod | file | -] [arg] ...
    Try `python -h' for more information.

Using "env python -V" works as expected on both EPEL-5 and EPEL-6.


More information about the Gluster-devel mailing list