Hi Kaleb,

I was able to run the script on the softserve setup on centos-7 and
centos-8.
Also managed to send a patch for this to work on centos-8 and use the devel
branch instead of master.
https://github.com/gluster/centosci/pull/112

Thanks again Niels, Kaleb, Saju for your help.

Regards
Rinku

On Wed, Oct 14, 2020 at 6:49 PM Kaleb Keithley <kkeit...@redhat.com> wrote:

> On Tue, Oct 13, 2020 at 11:32 AM Niels de Vos <nde...@redhat.com> wrote:
>
>>
>> For me, the following works:
>>
>>     $ mkdir centos8-fluster
>>     $ cd centos8-gluster
>>     $ vagrant init centos/8
>>     $ vagrant up
>>     $ cat << EOF | vagrant ssh -c 'sudo sh'
>>     dnf -y update
>>     dnf -y install epel-release
>>     curl https://termbin.com/sc70j > nightly-build.sh
>>     export CENTOS_VERSION=8 CENTOS_ARCH=x86_64 GERRIT_BRANCH=master
>>     sh -x nightly-build.sh
>>     EOF
>>
>> The https://termbin.com/sc70j is a slightly modified version of the
>> jobs/scripts/nightly-builds/nightly-builds.sh script from the
>> gluster/centosci repository. It has some adaptions for CentOS-8, which
>> will need to get merged in a cleaner way into the original script.
>>
>> You mentioned over chat that this didn't work for you. So I am wondering
>> if others have problems with the above steps too.
>>
>
> The above worked for me.  I was also able to just run the script by itself
> without vagrant, and even just build in mock from the/a src.rpm (made from
> head of release-8 branch.)
>
> Rinku and I spent a couple hours trying different things and found that
> %{python3_sitelib} is somehow not defined when he was running the builds in
> mock. But it could be seen in the root.log that python3-rpm-macros was
> installed, so we were at a loss as to why %{python3-sitelib} was not
> defined.
>
> --
>
> Kaleb
>
>
_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply via email to