On Sat, 24 Sep 2016 02:01:11 -0600 Eric Smith <spacewar@xxxxxxxxx> wrote: > I wrote: > > Normally I build release packages and push updates using "fedpkg > > build" and "fedpkg update". I've already done that for a few > > packages for f24, but those didn't get aarch64. Is there a simple > > way to build them and push updates for aarch64 as well? > > On Sat, Sep 24, 2016 at 12:54 AM, Dan Horák <dan@xxxxxxxx> wrote: > > it's a semi-automatic process that follows the exact build order in > > primary koji and no action is needed from the maintainer. Which > > packages/builds should be missing in aarch64? > > For instance, I recently pushed an update for abc, > abc-1.01-9.hg20160905, to f24, f25, and epel7. While "fedpkg build" in > the rawhide branch built it just fine for aarch64, running "fedpkg > build" in the f24 and f25 branches only built packages for i686, > x86_64, and armv7hl, so only those architectures got the update. > > I wouldn't normally worry about getting an update to abc into existing > Fedora branches, but in this case it's necessary to build the yosys > Verilog synthesizer (pending package review #1375765), and I'd like to > push yosys and related FPGA tools to f24 and f25 (obviously depending > on when the package review happens). that's correct, only F-26/rawhide has aarch64 as part of primary koji instance, F<=25 are still built in http://arm.koji.fedoraproject.org for abc builds see http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=19281 Dan _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
