On 07/05/2014 12:23 PM, Farkas Levente wrote: > On 07/05/2014 01:46 PM, Johnny Hughes wrote: >> On 07/05/2014 06:10 AM, Farkas Levente wrote: >>> On 06/21/2014 02:09 PM, Johnny Hughes wrote: >>>> On 06/21/2014 06:49 AM, Johnny Hughes wrote: >>>>> On 06/21/2014 06:39 AM, Farkas Levente wrote: >>>>>> On 06/21/2014 12:07 PM, Johnny Hughes wrote: >>>>>>> On 06/21/2014 03:01 AM, Farkas Levente wrote: >>>>>>>> On 06/20/2014 11:18 PM, Johnny Hughes wrote: >>>>>>>>> On 06/20/2014 03:34 PM, Johnny Hughes wrote: >>>>>>>>>> On 06/20/2014 12:51 PM, Farkas Levente wrote: >>>>>>>>>>> hi, is there any way to make the old c7.00.02 >>>>>>>>>>> and c7.00.00 centos repos available? currently >>>>>>>>>>> many i686 packages missing from c7.00.03 and >>>>>>>>>>> c7.00.04, but without these packages none of the >>>>>>>>>>> i686 packages cab be build. regards. >>>>>>>>>>> >>>>>>>>>> we can put the c7.00.02 there ... that should have >>>>>>>>>> everything required to build everything in the >>>>>>>>>> current c7 tree .. we'll get that pushed soon >>>>>>>>> OK, Its there (c7.00.02) >>>>>>>> may be c7.00.00 would be useful since eg gnupg2 has no >>>>>>>> i686 package which required by rpm-build-libs so >>>>>>>> required by everything... >>>>>>>> >>>>>>> I am not building against c7.00.00 ... and everything is >>>>>>> working fine for me now for i686. The issue is that the >>>>>>> more older RPMs we keep putting out there, the harder it >>>>>>> is for yum to pick the right one. >>>>>>> >>>>>>> To yum, all RPMs of name-1.2.3-15.i686.rpm .. so if 3 or >>>>>>> 4 exist, it can pick either one to use. >>>>>> can you tell me which repo contains gnupg2-x.i686.rpm? >>>>>> unfortunately none of them. and this rpm required by >>>>>> rpm-build-libs-4.11.1-16.el7.i686 which is required for >>>>>> all build. so with the current c7.00.02, c7.00.03 and >>>>>> c7.00.04 it's not possible to build any i686 rpm:-( >>>>>> >>>>> I am moving one into c7.00.02 now, that should hopefully >>>>> solve the issue. >>>> OK, that is now in place, let me know if you have other issues >>>> >>>> http://buildlogs.centos.org/c7.00.02/gnupg2/20140501124358/2.0.22-3.el7.i386/ > is >>> there any reason not to publish c7.00.00? eg: pacemaker can only >>> build with publican-3.1.5 which is neither in the publish repos >>> nor in the final release:-( >> Yes, there is a reason or it would be published. I moved the >> publican stuff over to c7.00.02, it should be there now, though a >> metadata rebuild is in progress. >> >> Let me know if you have any more issues. > > java6-1.6.0-* still missing. Is it required by something I built ... looking through some older stuff I do not see a good i686 build of java-1.6.0. It might be there somewhere, but I don't see it now. We are not releasing a i686 until later and we have not begun concentration on a full i686 build yet. However, if it is a requirement to build something that I have already built, then I'll spend more time looking. > > another nice thing would be know how are you able to build python? > it's clear from this builds: > http://buildlogs.centos.org/c7.00.04/python/ > there was many unsuccessful build, but than somehow it was successful, > but how and why? > http://buildlogs.centos.org/c7.00.04/python/20140617165351/2.7.5-16.el7.i386/ There is a build.log, a root.log, a mock config and everything you could need to know right there .. shows where the things were loaded from. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140705/b3d3134a/attachment-0007.sig>