Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base): ------------------------------------------------------------------------------- Source: /rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm Target: nrepentin-1-1 Submitter: nicolas@shivaserv.fr Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done
But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174.
--> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it?
Thanks
Le 31/08/2015 17:57, Nicolas Repentin a écrit :
Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base):
Source: /rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm Target: nrepentin-1-1 Submitter: nicolas@shivaserv.fr Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done
But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174.
--> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it?
Thanks
-- Nicolas Repentin nicolas@shivaserv.fr
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello
Abrt seems good to compil. I think you can restart job 4177 :)
Le 31/08/2015 18:19, Nicolas Repentin a écrit :
Le 31/08/2015 17:57, Nicolas Repentin a écrit :
Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base):
Source: /rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm Target: nrepentin-1-1 Submitter: nicolas@shivaserv.fr Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done
But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174.
--> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it?
Thanks
-- Nicolas Repentin nicolas@shivaserv.fr
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello
Abrt seems good to compil. I think you can restart job 4177 :)
-- Nicolas Repentin nicolas@shivaserv.fr
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello (again :p)
I just have launched some "easy" compilations, normally should be ok (only dependancies problems which are resolved now).
Some here are ok http://armv7.dev.centos.org/repodir/nrepentin-1-1/ and could be requeued. Some other are in progress actually : ID 7007 to 7009 here http://armv7.dev.centos.org/rpmbuild/nrepentin-1-1/, and we can see them here http://armv7.dev.centos.org/building.html
Hope it is correctly done.
Thanks,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 31/08/15 18:46, Nicolas Repentin wrote:
Le 31/08/2015 18:19, Nicolas Repentin a écrit :
Le 31/08/2015 17:57, Nicolas Repentin a écrit :
Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base):
Source:
/rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm
Target: nrepentin-1-1
Submitter: nicolas@shivaserv.fr Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done
But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174.
--> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it?
Thanks
-- Nicolas Repentin nicolas@shivaserv.fr
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello
Abrt seems good to compil. I think you can restart job 4177 :)
-- Nicolas Repentin nicolas@shivaserv.fr
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello (again :p)
I just have launched some "easy" compilations, normally should be ok (only dependancies problems which are resolved now).
Some here are ok http://armv7.dev.centos.org/repodir/nrepentin-1-1/ and could be requeued. Some other are in progress actually : ID 7007 to 7009 here http://armv7.dev.centos.org/rpmbuild/nrepentin-1-1/, and we can see them here http://armv7.dev.centos.org/building.html
Hope it is correctly done.
Thanks,
-- Nicolas Repentin nicolas@shivaserv.fr
Success: Job 4177 has been requeued. Success: Job 4248 has been requeued. Success: Job 4233 has been requeued. Success: Job 4256 has been requeued. Success: Job 4261 has been requeued. Success: Job 4273 has been requeued. Success: Job 4286 has been requeued. Success: Job 4326 has been requeued.
Thanks ..
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Hello
Here are some compilations, with new ID and old ID to requeue if OK :)
colord-kde - 7010 - 4346 --> OK control-center - 7011 - 4362 --> OK cyrus-imapd - 7012 - 4390 --> OK devhelp - 7013 - 4405 --> OK dragon - 7014 - 4433 --> OK ekiga - 7015 - 4452 --> OK empathy - 7016 - 4458 --> KO : error from mirror (error 404) evolution - 7017 - 6756 --> KO suitesparse - 7018 - 6969 --> KO libibverbs - 7019 - 6878 (this one is needed by a lot of others failed packages) --> KO - need valgrind (which need openpmi) Question: how often the repo are regenerated with "createrepo"? I've got some fails for dependancies, but these dependancies are recents successfull compilations. Thanks, Nicolas Repentin 31 août 2015 21:11 "Fabian Arrotin" a écrit:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/08/15 18:46, Nicolas Repentin wrote: Le 31/08/2015 18:19, Nicolas Repentin a écrit :Le 31/08/2015 17:57, Nicolas Repentin a écrit :Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base): ------------------------------------------------------------------------------- Source:
/rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm Target: nrepentin-1-1
Submitter: nicolas@shivaserv.fr (mailto:nicolas@shivaserv.fr) Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174. --> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it? Thanks -- Nicolas Repentin _______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
Hello
Abrt seems good to compil. I think you can restart job 4177 :)
-- Nicolas Repentin _______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
Hello (again :p)
I just have launched some "easy" compilations, normally should be ok (only dependancies problems which are resolved now).
Some here are ok http://armv7.dev.centos.org/repodir/nrepentin-1-1 (http://armv7.dev.centos.org/repodir/nrepentin-1-1/) and could be requeued. Some other are in progress actually : ID 7007 to 7009 here http://armv7.dev.centos.org/rpmbuild/nrepentin-1-1 (http://armv7.dev.centos.org/rpmbuild/nrepentin-1-1/), and we can see them here http://armv7.dev.centos.org/building.html (http://armv7.dev.centos.org/building.html)
Hope it is correctly done.
Thanks,
-- Nicolas Repentin Success: Job 4177 has been requeued. Success: Job 4248 has been requeued. Success: Job 4233 has been requeued. Success: Job 4256 has been requeued. Success: Job 4261 has been requeued. Success: Job 4273 has been requeued. Success: Job 4286 has been requeued. Success: Job 4326 has been requeued.
Thanks .. - -- Fabian Arrotin The CentOS Project | http://www.centos.org (http://www.centos.org) gpg key: 56BEC54E | twitter: @arrfab
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/09/15 08:13, Nicolas Repentin wrote:
Hello
Here are some compilations, with new ID and old ID to requeue if OK :)
colord-kde - 7010 - 4346 --> *OK* control-center - 7011 - 4362 --> *OK* cyrus-imapd - 7012 - 4390 --> *OK* devhelp - 7013 - 4405 --> *OK* dragon - 7014 - 4433 --> *OK* ekiga - 7015 - 4452 --> *OK* empathy - 7016 - 4458 --> KO : error from mirror (error 404) evolution - 7017 - 6756 --> KO suitesparse - 7018 - 6969 --> KO libibverbs - 7019 - 6878 (this one is needed by a lot of others failed packages) --> KO - need valgrind (which need openpmi)
Question: how often the repo are regenerated with "createrepo"? I've got some fails for dependancies, but these dependancies are recents successfull compilations.
Thanks,
Hi Nicolas,
[arrfab@geonosis ~]$ for id in 4346 4362 4390 4405 4433 4452 ; do plague-client requeue ${id};done Success: Job 4346 has been requeued. Success: Job 4362 has been requeued. Success: Job 4390 has been requeued. Success: Job 4405 has been requeued. Success: Job 4433 has been requeued. Success: Job 4452 has been requeued.
So keep up the good work. :-)
WRT the createrepo step : each time that plague has a successful build, it runs it against the existing repo, but obviously that takes quite some time now, due to the number of packages in the tree. And because plague is a distributed build farm, if for example you submit packages a b c d, and that d needs b (still itself building), obviously you need to requeue again that package when all satisfied deps are built and available in the main repo/repodata.
Hope that it clarifies the situation.
Cheers, and thanks for having a look at the previous build logs ! :-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Thanks for the requeue and the explaination.
I've submitted others jobs:
abrt-java-connector - 4178 --> OK empathy - 4458 --> In progress (ID 7016) Questions :p
- How to help to resolve real compilation errors with plague? Need to modify and regenerate a modify src.rpm package? - Same, for example, to build libibverbs, needed for a lot of packages, I need valgrind-devel. Valgrind need openmpi-devel >= 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and others). How to proceed to this kind of case? Because devel package is generated from normal package, right? Nicolas Repentin 1 septembre 2015 08:26 "Fabian Arrotin" a écrit:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 08:13, Nicolas Repentin wrote: Hello
Here are some compilations, with new ID and old ID to requeue if OK :)
colord-kde - 7010 - 4346 --> *OK* control-center - 7011 - 4362 --> *OK* cyrus-imapd - 7012 - 4390 --> *OK* devhelp - 7013 - 4405 --> *OK* dragon - 7014 - 4433 --> *OK* ekiga - 7015 - 4452 --> *OK* empathy - 7016 - 4458 --> KO : error from mirror (error 404) evolution - 7017 - 6756 --> KO suitesparse - 7018 - 6969 --> KO libibverbs - 7019 - 6878 (this one is needed by a lot of others failed packages) --> KO - need valgrind (which need openpmi) Question: how often the repo are regenerated with "createrepo"? I've got some fails for dependancies, but these dependancies are recents successfull compilations. Thanks, Hi Nicolas,
[arrfab@geonosis ~]$ for id in 4346 4362 4390 4405 4433 4452 ; do plague-client requeue ${id};done Success: Job 4346 has been requeued. Success: Job 4362 has been requeued. Success: Job 4390 has been requeued. Success: Job 4405 has been requeued. Success: Job 4433 has been requeued. Success: Job 4452 has been requeued.
So keep up the good work. :-)
WRT the createrepo step : each time that plague has a successful build, it runs it against the existing repo, but obviously that takes quite some time now, due to the number of packages in the tree. And because plague is a distributed build farm, if for example you submit packages a b c d, and that d needs b (still itself building), obviously you need to requeue again that package when all satisfied deps are built and available in the main repo/repodata.
Hope that it clarifies the situation.
Cheers, and thanks for having a look at the previous build logs ! :-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org (http://www.centos.org) gpg key: 56BEC54E | twitter: @arrfab
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
Little update Thanks for the requeue and the explaination.
I've submitted others jobs:
abrt-java-connector - 4178 --> OK empathy - 4458 --> OK Questions :p
- How to help to resolve real compilation errors with plague? Need to modify and regenerate a modify src.rpm package? - Same, for example, to build libibverbs, needed for a lot of packages, I need valgrind-devel. Valgrind need openmpi-devel >= 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and others). How to proceed to this kind of case? Because devel package is generated from normal package, right? Nicolas Repentin 1 septembre 2015 08:26 "Fabian Arrotin" a écrit: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 08:13, Nicolas Repentin wrote: Hello
Here are some compilations, with new ID and old ID to requeue if OK :)
colord-kde - 7010 - 4346 --> *OK* control-center - 7011 - 4362 --> *OK* cyrus-imapd - 7012 - 4390 --> *OK* devhelp - 7013 - 4405 --> *OK* dragon - 7014 - 4433 --> *OK* ekiga - 7015 - 4452 --> *OK* empathy - 7016 - 4458 --> KO : error from mirror (error 404) evolution - 7017 - 6756 --> KO suitesparse - 7018 - 6969 --> KO libibverbs - 7019 - 6878 (this one is needed by a lot of others failed packages) --> KO - need valgrind (which need openpmi) Question: how often the repo are regenerated with "createrepo"? I've got some fails for dependancies, but these dependancies are recents successfull compilations. Thanks, Hi Nicolas,
[arrfab@geonosis ~]$ for id in 4346 4362 4390 4405 4433 4452 ; do plague-client requeue ${id};done Success: Job 4346 has been requeued. Success: Job 4362 has been requeued. Success: Job 4390 has been requeued. Success: Job 4405 has been requeued. Success: Job 4433 has been requeued. Success: Job 4452 has been requeued.
So keep up the good work. :-)
WRT the createrepo step : each time that plague has a successful build, it runs it against the existing repo, but obviously that takes quite some time now, due to the number of packages in the tree. And because plague is a distributed build farm, if for example you submit packages a b c d, and that d needs b (still itself building), obviously you need to requeue again that package when all satisfied deps are built and available in the main repo/repodata.
Hope that it clarifies the situation.
Cheers, and thanks for having a look at the previous build logs ! :-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org (http://www.centos.org) gpg key: 56BEC54E | twitter: @arrfab
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/09/15 14:09, Nicolas Repentin wrote:
Little update
<nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
Thanks for the requeue and the explaination.
I've submitted others jobs:
*abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK*
requeued ...
Questions :p
- How to help to resolve real compilation errors with plague? Need
to modify and regenerate a modify src.rpm package?
yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available.
- Same, for example, to build libibverbs, needed for a lot of
packages, I need valgrind-devel. Valgrind need openmpi-devel >= 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and others). How to proceed to this kind of case? Because devel package is generated from normal package, right?
That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot/ So those were built *outside* of plague, and so directly with mock, against specific mock config files.
For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/ but then, when Johnny took up the build effort, I don't know where he copied his.
Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Thanks
Some status for failed builds:
- atlas : compil error - bacula : compil error - base64coder : compil error - batik : compil error - bogofilter : need gsl-devel - brasero : need brasero-devel, nautilus-devel, tracker-devel - compat-gcc-32 : compil error - compat-gcc-34 : compil error - compat-gcc-44 : compil error - compat-glibc : compil error - compat-opensm-libs : need libibmad-devel, libibumad-devel - dapl : need libibverbs-devel, librdmacm-devel - easymock : compil error - evolution : need bogofilter - evolution-ews : need evolution-devel - evolution-mapi : need evolution-devel - gegl : need suitesparse-devel - gimp : need gegl-devel - gnome-document : need inkscape - golang-github-gorilla-context : need golang - golang-github-kr-pty : need golang - golang-github-syndtr-gocapability : need golang - gsl : compil error - gutenprint : need gimp, gimp-devel - hwloc : need libibverbs-devel - ibacm : need libibumad-devel, libibverbs-devel - ibutils : need libibumad-devel, libibverbs-devel, opensm-devel - infiniband-diags : need libibmad-devel, libibumad-devel, opensm-devel - inkscape : need gsl-devel - ipa : need python-lesscpy - libcap-ng : compil error - libcxgb3 : need libibverbs-devel, valgrind-devel - libcxgb4 : need libibverbs-devel - libibcm : need libibverbs-devel - libibmad : need libibumad-devel, valgrind-devel - libibumad : need valgrind-devel - libibverbs : need valgrind-devel - libmlx4 : need libibverbs-devel - libmlx5 : need libibverbs-devel - libmthca : need libibverbs-devel, valgrind-devel - libnes : need libibverbs-devel, valgrind-devel - libocrdma : need libibverbs-devel - librdmacm : need ibacm-devel, libibverbs-devel, valgrind-devel - libreoffice : compil error - libreoffice-voikko : need libreoffice-sdk - libseccomp : need valgrind - libusnic_verbs : need libibverbs-devel, valgrind-devel - mpich : need hwlock-devel - mstflint : need libibmad-devel - mvapich2 : need hwloc-devel, libibmad-devel, libibumad-devel, libibverbs-devel, librdmacm-devel - openmpi : need hwloc-devel, libibcm-devel, libibverbs-devel, librdmacm-devel, opensm-devel, valgrind-devel - opensm : need libibmad-devel - openssl098e : compil error - papi : need libibmad-devel - pcp : need libibmad-devel, libibumad-devel, papi-devel - perftest : need libibumad-devel, libibverbs-devel, librdmacm-devel - qemu-guest-agent : need librdmacm-devel - qemu-kvm : need librdmacm-devel - qperf : need libibverbs-devel, librdmacm-devel - rhythmbox : need brasero-devel - scipy : need suitesparse-devel - spice-gtk : need libcacard-devel - srptools : need libibumad-devel, libibverbs-devel - suitesparse : need atlas-devel > 3.10 - syslinux : need /usr/include/gnu/stubs-32.h - valgrind : need openmpi-devel - virt-top : compil error - virt-viewer : need spice-gtk3-devel - xsane : need gimp-devel So... in bold, only dependancies problems. If we can get libibverbs, libibmad, libibumad we should compile a lot of packages, but to get libibverbs it's a circular dep..
--> libibverbs : need valgrind-devel. valgrind need openmpi-devel. Openmpi need libibverbs-devel... Anyway to put libibverbs-devel on c7-buildroot?
--> Brasero : need brasero-devel. Circular dep :s
--> Golang* : need golang package, but it is not on repo and not on build list? Nicolas Repentin 1 septembre 2015 18:39 "Fabian Arrotin" a écrit: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot (http://armv7.dev.centos.org/repodir/c7-buildroot/) So those were built *outside* of plague, and so directly with mock, against specific mock config files. For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS (http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/) but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin > > - -- Fabian Arrotin The CentOS Project | http://www.centos.org (http://www.centos.org) gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
Hello
No one ? :p Nicolas Repentin 2 septembre 2015 08:43 "Nicolas Repentin" a écrit:
Thanks
Some status for failed builds:
- atlas : compil error - bacula : compil error - base64coder : compil error - batik : compil error - bogofilter : need gsl-devel - brasero : need brasero-devel, nautilus-devel, tracker-devel - compat-gcc-32 : compil error - compat-gcc-34 : compil error - compat-gcc-44 : compil error - compat-glibc : compil error - compat-opensm-libs : need libibmad-devel, libibumad-devel - dapl : need libibverbs-devel, librdmacm-devel - easymock : compil error - evolution : need bogofilter - evolution-ews : need evolution-devel - evolution-mapi : need evolution-devel - gegl : need suitesparse-devel - gimp : need gegl-devel - gnome-document : need inkscape - golang-github-gorilla-context : need golang - golang-github-kr-pty : need golang - golang-github-syndtr-gocapability : need golang - gsl : compil error - gutenprint : need gimp, gimp-devel - hwloc : need libibverbs-devel - ibacm : need libibumad-devel, libibverbs-devel - ibutils : need libibumad-devel, libibverbs-devel, opensm-devel - infiniband-diags : need libibmad-devel, libibumad-devel, opensm-devel - inkscape : need gsl-devel - ipa : need python-lesscpy - libcap-ng : compil error - libcxgb3 : need libibverbs-devel, valgrind-devel - libcxgb4 : need libibverbs-devel - libibcm : need libibverbs-devel - libibmad : need libibumad-devel, valgrind-devel - libibumad : need valgrind-devel - libibverbs : need valgrind-devel - libmlx4 : need libibverbs-devel - libmlx5 : need libibverbs-devel - libmthca : need libibverbs-devel, valgrind-devel - libnes : need libibverbs-devel, valgrind-devel - libocrdma : need libibverbs-devel - librdmacm : need ibacm-devel, libibverbs-devel, valgrind-devel - libreoffice : compil error - libreoffice-voikko : need libreoffice-sdk - libseccomp : need valgrind - libusnic_verbs : need libibverbs-devel, valgrind-devel - mpich : need hwlock-devel - mstflint : need libibmad-devel - mvapich2 : need hwloc-devel, libibmad-devel, libibumad-devel, libibverbs-devel, librdmacm-devel - openmpi : need hwloc-devel, libibcm-devel, libibverbs-devel, librdmacm-devel, opensm-devel, valgrind-devel - opensm : need libibmad-devel - openssl098e : compil error - papi : need libibmad-devel - pcp : need libibmad-devel, libibumad-devel, papi-devel - perftest : need libibumad-devel, libibverbs-devel, librdmacm-devel - qemu-guest-agent : need librdmacm-devel - qemu-kvm : need librdmacm-devel - qperf : need libibverbs-devel, librdmacm-devel - rhythmbox : need brasero-devel - scipy : need suitesparse-devel - spice-gtk : need libcacard-devel - srptools : need libibumad-devel, libibverbs-devel - suitesparse : need atlas-devel > 3.10 - syslinux : need /usr/include/gnu/stubs-32.h - valgrind : need openmpi-devel - virt-top : compil error - virt-viewer : need spice-gtk3-devel - xsane : need gimp-devel So... in bold, only dependancies problems. If we can get libibverbs, libibmad, libibumad we should compile a lot of packages, but to get libibverbs it's a circular dep..
--> libibverbs : need valgrind-devel. valgrind need openmpi-devel. Openmpi need libibverbs-devel... Anyway to put libibverbs-devel on c7-buildroot?
--> Brasero : need brasero-devel. Circular dep :s
--> Golang* : need golang package, but it is not on repo and not on build list? Nicolas Repentin 1 septembre 2015 18:39 "Fabian Arrotin" a écrit: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot (http://armv7.dev.centos.org/repodir/c7-buildroot/) So those were built *outside* of plague, and so directly with mock, against specific mock config files. For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS (http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/) but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin > > - -- Fabian Arrotin The CentOS Project | http://www.centos.org (http://www.centos.org) gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org (mailto:Arm-dev@centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 15/09/15 07:51, Nicolas Repentin wrote:
Hello
No one ? :p
Well, Johnny was supposed to give feedback last week about that so don't know. @Johnny ? @Nicolas : on your side, had you a look at the build logs to see where it could fail, and also try some builds including patches ? (at the .spec level, or some packages that need to be in the buildroot first, or a real patch for the application itself ?)
Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
2 septembre 2015 08:43 "Nicolas Repentin" <nicolas@shivaserv.fr <mailto:%22Nicolas%20Repentin%22%20nicolas@shivaserv.fr>> a écrit:
Thanks
Some status for failed builds:
- atlas : compil error - bacula : compil error - base64coder :
compil error - batik : compil error *- bogofilter : need gsl-devel
- brasero : need brasero-devel, nautilus-devel, tracker-devel* -
compat-gcc-32 : compil error - compat-gcc-34 : compil error - compat-gcc-44 : compil error - compat-glibc : compil error *?- compat-opensm-libs : need libibmad-devel, libibumad-devel - dapl : need libibverbs-devel, librdmacm-devel* - easymock : compil error *- evolution : need bogofilter - evolution-ews : need evolution-devel - evolution-mapi : need evolution-devel - gegl : need suitesparse-devel - gimp : need gegl-devel - gnome-document : need inkscape - golang-github-gorilla-context : need golang - golang-github-kr-pty : need golang - golang-github-syndtr-gocapability : need golang* - gsl : compil error *- gutenprint : need gimp, gimp-devel - hwloc : need libibverbs-devel - ibacm : need libibumad-devel, libibverbs-devel - ibutils : need libibumad-devel, libibverbs-devel, opensm-devel - infiniband-diags : need libibmad-devel, libibumad-devel, opensm-devel - inkscape : need gsl-devel - ipa : need python-lesscpy* - libcap-ng : compil error *- libcxgb3 : need libibverbs-devel, valgrind-devel - libcxgb4 : need **libibverbs-devel - libibcm : need libibverbs-devel - libibmad : need libibumad-devel, valgrind-devel - libibumad : need valgrind-devel - libibverbs : need valgrind-devel - libmlx4 : need libibverbs-devel - libmlx5 : need libibverbs-devel - libmthca : need libibverbs-devel, valgrind-devel - libnes : need libibverbs-devel, valgrind-devel - libocrdma : need libibverbs-devel - librdmacm : need ibacm-devel, libibverbs-devel, valgrind-devel* - libreoffice : compil error *- libreoffice-voikko : need libreoffice-sdk - libseccomp : need valgrind - libusnic_verbs : need libibverbs-devel, valgrind-devel - mpich : need hwlock-devel - mstflint : need libibmad-devel - mvapich2 : need hwloc-devel, libibmad-devel, libibumad-devel, libibverbs-devel, librdmacm-devel - openmpi : need hwloc-devel, libibcm-devel, libibverbs-devel, librdmacm-devel, opensm-devel, valgrind-devel - opensm : need libibmad-devel* - openssl098e : compil error *- papi : need libibmad-devel - pcp : need libibmad-devel, libibumad-devel, papi-devel - perftest : need libibumad-devel, libibverbs-devel, librdmacm-devel - qemu-guest-agent : need librdmacm-devel - qemu-kvm : need librdmacm-devel - qperf : need libibverbs-devel, librdmacm-devel - rhythmbox : need brasero-devel - scipy : need suitesparse-devel - spice-gtk : need libcacard-devel - srptools : need libibumad-devel, libibverbs-devel - suitesparse : need atlas-devel > 3.10 - syslinux : need **/usr/include/gnu/stubs-32.h - valgrind : need openmpi-devel* - virt-top : compil error *- virt-viewer : need spice-gtk3-devel - xsane : need gimp-devel*
So... in bold, only dependancies problems. If we can get libibverbs, libibmad, libibumad we should compile a lot of packages, but to get libibverbs it's a circular dep..
--> libibverbs : need valgrind-devel. valgrind need openmpi-devel. Openmpi need libibverbs-devel... Anyway to put libibverbs-devel on c7-buildroot?
--> Brasero : need brasero-devel. Circular dep :s
--> Golang* : need golang package, but it is not on repo and not on build list?
Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
1 septembre 2015 18:39 "Fabian Arrotin" <arrfab@centos.org <mailto:%22Fabian%20Arrotin%22%20arrfab@centos.org>> a écrit:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr mailto:mailto:nicolas@shivaserv.fr>> > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot http://armv7.dev.centos.org/repodir/c7-buildroot/ So those were built *outside* of plague, and so directly with mock, against specific mock config files. For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/ but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr > <mailto:nicolas@shivaserv.fr mailto:mailto:nicolas@shivaserv.fr>> > - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org mailto:Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Hi Nicolas,
Your previous mail read to me like a status update rather than a question. Probably that's why there was so little response.
On circular references, there are a couple of things which can be tried: - get the rpm from F19 and see if that works - read through the spec file. Often there is a "bootstrap" procedure, which might be tried
for your question about golang: there are some packages that (apparently) are not part of the distro, but needed to build it. Their SRPMS are here: http://vault.centos.org/7.1.1503/extras/Source/SPackages/
I notice that many of the issues you face are similar to the ones I had when building RHEL7 for armv5. my notes of that are here: http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/RS7.1_issuelog.html and patches here: http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/old-patches/ http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/patches/
last, but not least, do not expect everything to build. Forget about (for example) the compat-* stuff. It'll be a hell of a job to get it to build and nobody needs it probably.
Jacco
PS. I wondered about libreoffice, which always build normally for me. It seems that your build environment does not have enough memory to complete the build.
On 15-09-15 07:51, Nicolas Repentin wrote:
Hello
No one ? :p
Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
2 septembre 2015 08:43 "Nicolas Repentin" <nicolas@shivaserv.fr mailto:%22Nicolas%20Repentin%22%20%3Cnicolas@shivaserv.fr%3E> a écrit:
Thanks Some status for failed builds: - atlas : compil error - bacula : compil error - base64coder : compil error - batik : compil error *- bogofilter : need gsl-devel - brasero : need brasero-devel, nautilus-devel, tracker-devel* - compat-gcc-32 : compil error - compat-gcc-34 : compil error - compat-gcc-44 : compil error - compat-glibc : compil error *- compat-opensm-libs : need libibmad-devel, libibumad-devel - dapl : need libibverbs-devel, librdmacm-devel* - easymock : compil error *- evolution : need bogofilter - evolution-ews : need evolution-devel - evolution-mapi : need evolution-devel - gegl : need suitesparse-devel - gimp : need gegl-devel - gnome-document : need inkscape - golang-github-gorilla-context : need golang - golang-github-kr-pty : need golang - golang-github-syndtr-gocapability : need golang* - gsl : compil error *- gutenprint : need gimp, gimp-devel - hwloc : need libibverbs-devel - ibacm : need libibumad-devel, libibverbs-devel - ibutils : need libibumad-devel, libibverbs-devel, opensm-devel - infiniband-diags : need libibmad-devel, libibumad-devel, opensm-devel - inkscape : need gsl-devel - ipa : need python-lesscpy* - libcap-ng : compil error *- libcxgb3 : need libibverbs-devel, valgrind-devel - libcxgb4 : need **libibverbs-devel - libibcm : need libibverbs-devel - libibmad : need libibumad-devel, valgrind-devel - libibumad : need valgrind-devel - libibverbs : need valgrind-devel - libmlx4 : need libibverbs-devel - libmlx5 : need libibverbs-devel - libmthca : need libibverbs-devel, valgrind-devel - libnes : need libibverbs-devel, valgrind-devel - libocrdma : need libibverbs-devel - librdmacm : need ibacm-devel, libibverbs-devel, valgrind-devel* - libreoffice : compil error *- libreoffice-voikko : need libreoffice-sdk - libseccomp : need valgrind - libusnic_verbs : need libibverbs-devel, valgrind-devel - mpich : need hwlock-devel - mstflint : need libibmad-devel - mvapich2 : need hwloc-devel, libibmad-devel, libibumad-devel, libibverbs-devel, librdmacm-devel - openmpi : need hwloc-devel, libibcm-devel, libibverbs-devel, librdmacm-devel, opensm-devel, valgrind-devel - opensm : need libibmad-devel* - openssl098e : compil error *- papi : need libibmad-devel - pcp : need libibmad-devel, libibumad-devel, papi-devel - perftest : need libibumad-devel, libibverbs-devel, librdmacm-devel - qemu-guest-agent : need librdmacm-devel - qemu-kvm : need librdmacm-devel - qperf : need libibverbs-devel, librdmacm-devel - rhythmbox : need brasero-devel - scipy : need suitesparse-devel - spice-gtk : need libcacard-devel - srptools : need libibumad-devel, libibverbs-devel - suitesparse : need atlas-devel > 3.10 - syslinux : need **/usr/include/gnu/stubs-32.h - valgrind : need openmpi-devel* - virt-top : compil error *- virt-viewer : need spice-gtk3-devel - xsane : need gimp-devel* So... in bold, only dependancies problems. If we can get libibverbs, libibmad, libibumad we should compile a lot of packages, but to get libibverbs it's a circular dep.. --> libibverbs : need valgrind-devel. valgrind need openmpi-devel. Openmpi need libibverbs-devel... Anyway to put libibverbs-devel on c7-buildroot? --> Brasero : need brasero-devel. Circular dep :s --> Golang* : need golang package, but it is not on repo and not on build list? Nicolas Repentin <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr>> 1 septembre 2015 18:39 "Fabian Arrotin" <arrfab@centos.org <mailto:%22Fabian%20Arrotin%22%20%3Carrfab@centos.org%3E>> a écrit: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr> <mailto:nicolas@shivaserv.fr <mailto:mailto:nicolas@shivaserv.fr>>> > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot <http://armv7.dev.centos.org/repodir/c7-buildroot/> So those were built *outside* of plague, and so directly with mock, against specific mock config files. For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS <http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/> but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr> > <mailto:nicolas@shivaserv.fr <mailto:mailto:nicolas@shivaserv.fr>>> > - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org <mailto:Arm-dev@centos.org> https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello Jacco
Sorry for the delay.
Thanks for all these infos ;)
I tried to compil some dependancy with F19 srpm: - gsl: succeeded - libibverbs: succeeded - libibumad: succeeded
Testing after satisfaying dependancy: - hwloc:succeeded. Fabian can you requeue job 6799? - ibacm: succeeded. Fabian can you requeue job 6875? - bogofilter: succeeded. Fabian can you requeue job 6743?
I will check tomorrow and start other builds :)
Le 15/09/2015 09:12, Jacco Ligthart a écrit :
Hi Nicolas,
Your previous mail read to me like a status update rather than a question. Probably that's why there was so little response.
On circular references, there are a couple of things which can be tried:
- get the rpm from F19 and see if that works
- read through the spec file. Often there is a "bootstrap" procedure,
which might be tried
for your question about golang: there are some packages that (apparently) are not part of the distro, but needed to build it. Their SRPMS are here: http://vault.centos.org/7.1.1503/extras/Source/SPackages/
I notice that many of the issues you face are similar to the ones I had when building RHEL7 for armv5. my notes of that are here: http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/RS7.1_issuelog.html and patches here: http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/old-patches/ http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/patches/
last, but not least, do not expect everything to build. Forget about (for example) the compat-* stuff. It'll be a hell of a job to get it to build and nobody needs it probably.
Jacco
PS. I wondered about libreoffice, which always build normally for me. It seems that your build environment does not have enough memory to complete the build.
On 15-09-15 07:51, Nicolas Repentin wrote:
Hello
No one ? :p
Nicolas Repentin <nicolas@shivaserv.fr mailto:nicolas@shivaserv.fr>
2 septembre 2015 08:43 "Nicolas Repentin" nicolas@shivaserv.fr a écrit:
Thanks Some status for failed builds: - atlas : compil error - bacula : compil error - base64coder : compil error - batik : compil error *- bogofilter : need gsl-devel - brasero : need brasero-devel, nautilus-devel, tracker-devel* - compat-gcc-32 : compil error - compat-gcc-34 : compil error - compat-gcc-44 : compil error - compat-glibc : compil error *- compat-opensm-libs : need libibmad-devel, libibumad-devel - dapl : need libibverbs-devel, librdmacm-devel* - easymock : compil error *- evolution : need bogofilter - evolution-ews : need evolution-devel - evolution-mapi : need evolution-devel - gegl : need suitesparse-devel - gimp : need gegl-devel - gnome-document : need inkscape - golang-github-gorilla-context : need golang - golang-github-kr-pty : need golang - golang-github-syndtr-gocapability : need golang* - gsl : compil error *- gutenprint : need gimp, gimp-devel - hwloc : need libibverbs-devel - ibacm : need libibumad-devel, libibverbs-devel - ibutils : need libibumad-devel, libibverbs-devel, opensm-devel - infiniband-diags : need libibmad-devel, libibumad-devel, opensm-devel - inkscape : need gsl-devel - ipa : need python-lesscpy* - libcap-ng : compil error *- libcxgb3 : need libibverbs-devel, valgrind-devel - libcxgb4 : need **libibverbs-devel - libibcm : need libibverbs-devel - libibmad : need libibumad-devel, valgrind-devel - libibumad : need valgrind-devel - libibverbs : need valgrind-devel - libmlx4 : need libibverbs-devel - libmlx5 : need libibverbs-devel - libmthca : need libibverbs-devel, valgrind-devel - libnes : need libibverbs-devel, valgrind-devel - libocrdma : need libibverbs-devel - librdmacm : need ibacm-devel, libibverbs-devel, valgrind-devel* - libreoffice : compil error *- libreoffice-voikko : need libreoffice-sdk - libseccomp : need valgrind - libusnic_verbs : need libibverbs-devel, valgrind-devel - mpich : need hwlock-devel - mstflint : need libibmad-devel - mvapich2 : need hwloc-devel, libibmad-devel, libibumad-devel, libibverbs-devel, librdmacm-devel - openmpi : need hwloc-devel, libibcm-devel, libibverbs-devel, librdmacm-devel, opensm-devel, valgrind-devel - opensm : need libibmad-devel* - openssl098e : compil error *- papi : need libibmad-devel - pcp : need libibmad-devel, libibumad-devel, papi-devel - perftest : need libibumad-devel, libibverbs-devel, librdmacm-devel - qemu-guest-agent : need librdmacm-devel - qemu-kvm : need librdmacm-devel - qperf : need libibverbs-devel, librdmacm-devel - rhythmbox : need brasero-devel - scipy : need suitesparse-devel - spice-gtk : need libcacard-devel - srptools : need libibumad-devel, libibverbs-devel - suitesparse : need atlas-devel > 3.10 - syslinux : need **/usr/include/gnu/stubs-32.h - valgrind : need openmpi-devel* - virt-top : compil error *- virt-viewer : need spice-gtk3-devel - xsane : need gimp-devel* So... in bold, only dependancies problems. If we can get libibverbs, libibmad, libibumad we should compile a lot of packages, but to get libibverbs it's a circular dep.. --> libibverbs : need valgrind-devel. valgrind need openmpi-devel. Openmpi need libibverbs-devel... Anyway to put libibverbs-devel on c7-buildroot? --> Brasero : need brasero-devel. Circular dep :s --> Golang* : need golang package, but it is not on repo and not on build list? Nicolas Repentin <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr>> 1 septembre 2015 18:39 "Fabian Arrotin" <arrfab@centos.org> a écrit: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr> <mailto:nicolas@shivaserv.fr <mailto:mailto:nicolas@shivaserv.fr>>> > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All those patches will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) :http://armv7.dev.centos.org/repodir/c7-buildroot <http://armv7.dev.centos.org/repodir/c7-buildroot/> So those were built *outside* of plague, and so directly with mock, against s pecific mock config files. For patches, I initially put those I needed here :http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS <http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS/> but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr> > <mailto:nicolas@shivaserv.fr <mailto:mailto:nicolas@shivaserv.fr>>> > - -- Fabian Arrotin The CentOS Project |http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 .0.22 (GN U/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing listArm-dev@centos.org <mailto:Arm-dev@centos.org> https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/09/15 20:56, Nicolas Repentin wrote:
Hello Jacco
Sorry for the delay.
Thanks for all these infos ;)
I tried to compil some dependancy with F19 srpm: - gsl: succeeded - libibverbs: succeeded - libibumad: succeeded
Testing after satisfaying dependancy: - hwloc:succeeded. Fabian can you requeue job 6799? - ibacm: succeeded. Fabian can you requeue job 6875? - bogofilter: succeeded. Fabian can you requeue job 6743?
I will check tomorrow and start other builds :)
Hi Nicolas,
Thanks a lot for having a look at this. So it seems you built the first packages from f19 srpm[s]. But I can't just requeue the three builds you mention, as they still depends on other packages, and your build artifacts aren't available for the c7-pass-1 build env.
I so had a quick look and here are the buildrequires (each time with other build requires for package) for hwloc: libibverbs valgrind openmpi valgrind (and other ones, like libiverbs too) => circular build dep
So let me then just try to * rebuild openmpi (from f19, against f19+c7) * inject it in buildroot (_staging) * try to then rebuild valgrind, libibverbs, hwloc, etc
That's probably what we need to look at : (circular build deps) and just having a look at http://armv7.dev.centos.org/report.html (and so the build and root logs) would help finding such cases/issues.
I'm myself working on some other infra things, but ping me here or on irc if you find something else
Cheers, and thanks for helping pushing the armv7hl build effort forward :-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
I so had a quick look and here are the buildrequires (each time with > other build requires for package) for > hwloc: > libibverbs >
valgrind > openmpi > valgrind (and other ones, like libiverbs too) => circular > build dep > > So let me then just try to > * rebuild openmpi (from f19, against f19+c7) > * inject it in buildroot (_staging) > * try to then rebuild valgrind, libibverbs, hwloc, etc
what you probably want is: * rebuild openmpi (from *c7*, against f19+c7)
Jacco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/09/15 09:11, Jacco Ligthart wrote:
I so had a quick look and here are the buildrequires (each time with > other build requires for package) for > hwloc: > libibverbs >
valgrind > openmpi > valgrind (and other ones, like libiverbs too) => circular > build dep > > So let me then just try to > * rebuild openmpi (from f19, against f19+c7) > * inject it in buildroot (_staging) > * try to then rebuild valgrind, libibverbs, hwloc, etc
what you probably want is: * rebuild openmpi (from *c7*, against f19+c7)
Jacco
Hi Jacco,
I like the idea of just rebuilding the previous version (f19) in that case in a staging buildroot, just to satisfy the other buildrequires for that package (but with the correct c7 version), so that the c7 srpm itself is built against the c7-buildroot/pass-1 (and not having to rely on f19 anymore) : so that staging repo is just temporary
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 24-09-15 09:14, Fabian Arrotin wrote:
On 24/09/15 09:11, Jacco Ligthart wrote:
I so had a quick look and here are the buildrequires (each time with > other build requires for package) for > hwloc: > libibverbs >
valgrind > openmpi > valgrind (and other ones, like libiverbs too) => circular > build dep > > So let me then just try to > * rebuild openmpi (from f19, against f19+c7) > * inject it in buildroot (_staging) > * try to then rebuild valgrind, libibverbs, hwloc, etc
what you probably want is: * rebuild openmpi (from *c7*, against f19+c7)
Jacco
Hi Jacco,
I like the idea of just rebuilding the previous version (f19) in that case in a staging buildroot, just to satisfy the other buildrequires for that package (but with the correct c7 version), so that the c7 srpm itself is built against the c7-buildroot/pass-1 (and not having to rely on f19 anymore) : so that staging repo is just temporary
hmm, not sure if we mean the same or not. I'm also in favor of a staging area. So what I did when building armv5tel is (when needed) build C7 srpms against a mix of already build C7 RPMS, some hand picked F18 (latest armv5 fedora) and sometimes some manual adjustments. The result would then (hopefully) be a RPM. These RPMS would go into staging, only to be used to build release worthy RPMS.
The only RPMS that got into release were those that were exclusively build against C7 content.
I guess that I just don't see the point in rebuilding F19 SRPMS. It might however depend on the version differences we're talking about. if the versions are for all practical reasons the same, than it does not really matter.
J.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 31/08/15 18:19, Nicolas Repentin wrote:
Le 31/08/2015 17:57, Nicolas Repentin a écrit :
Hello
I have access to plague servers (thanks to Fabian for the live debug :p).
I've tried to compil a package, and it was successfull. I see the job goes to my folder, but to go in the standard build queue, I need to requeue the original failed job, but I don't have access to it. For example, I have compiled this package with this ID:
bash-4.2$ plague-client detail 7001
Detail for Job ID 7001 (389-ds-base):
Source:
/rpmbuild/srpm_upload_dir/nrepentin-1-1/389-ds-base-1.3.3.1-13.el7.src.rpm
Target: nrepentin-1-1
Submitter: nicolas@shivaserv.fr Status: needsign/ Archjobs: armv7hl: armv7-02.dev.centos.org done/done
But if I want to requeue the original job:
-bash-4.2$ plague-client requeue 4174 Error: You are not the original submitter for Job 4174.
--> Is it possible to have a right to requeue the original job, or do I need to ask someone with rights to do it?
Thanks
-- Nicolas Repentin nicolas@shivaserv.fr
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello
Abrt seems good to compil. I think you can restart job 4177 :)
-- Nicolas Repentin nicolas@shivaserv.fr
Requeued ...
Cheers,
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-
Fabian Arrotin -
Jacco Ligthart -
Nicolas Repentin