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 at 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXlRRgACgkQnVkHo1a+xU757QCgjX12/I7UZWQHfSBmgR5t5KDg k/sAoIVBECr1BsvwJJEu2pKnWYs4jWLy =bnrM -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev at centos.org (mailto:Arm-dev at centos.org) https://lists.centos.org/mailman/listinfo/arm-dev (https://lists.centos.org/mailman/listinfo/arm-dev) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20150901/867a13d3/attachment-0006.html>