On Sat, Mar 08, 2014 at 06:53:19AM -0500, Michael K. Johnson wrote: > I suspect that these are all valid upstrea, but I don't actually > know how to tell mirrorball that this is OK. On to Brett!
Brett pointed out that this error comes out of the superclass, not out of mirrorball, and between us we got all the necessary fixes into the "archExceptions" list in factory-capsule-rpm that marks package names that are allowed to exist only on one architecture. Binary imports are now making progress. However, we're now limited by available build hardware; we're importing only about 40 packages per hour in the current build farm, which adds up to about 15 days just to do the initial import. That's in part because we haven't yet gotten the new build machines to deploy into the cluster, but in part because the build cluster was tuned for a few builds of source packages in which parallel make is very effective, not for many imports of binary packages in parallel. So we'll look at both approaches to speed things up. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
