On Sun, Jun 30, 2013 at 08:10:23AM -0400, Brendan Conoboy wrote: > Number of candidate source rpms: 13595 > > Number of source rpms built in stage 4: 10646 > > Number of packages built in stage4 with aarch64 components: 4117 I have been watching the automatic mails since they were introduced, (thanks I now have yet another in memory counter, I was actually mentally happy when it crossed 4000 thinking we're getting closer to 50%). What is the limitating factor ? I don't think there is a too big depth of package dependencies, so if the main factor isn't some lack of computing power, I would have assumed that unlocking some key package (e.g. python, gtk libs, ...) would allow some quick progresses, but it smells like it's progressing purely lineary. Is that dependant on converting each of the package (like auto* updates when they lack aarch64 support ?) Cole (I assume it's mostly you based on mails and commits samples I saw), would you share the story there ? Just being curious, Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard@xxxxxxxxxx | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/ _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm