-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/01/16 13:23, Nick Betteridge wrote: > Hi, > > I recently made a request to community buildsys arm32 so that I > can understand the build process and then try and do a do a build > for an olimex olinuxino A20 board. > > In addition, I've just received a Pine64 board and wouldn't mind > trying to do a build for that too. Do I need to resubmit the > request for buildsys - arm64 with the same keys? > > Cheers Nick Hi Nick, The community buildsys arm32 (plague build-farm) is just composed of plague/mock builders. If you're interested in testing/supporting a specific board, the first thing to do would be to see if the board requires : - - specific firmware - - specific kernel - - specific uboot If current uboot has support (image) for that board (http://mirror.centos.org/altarch/7/extras/armhfp/Packages/uboot-images-armv7-2015.10-4.el7.noarch.rpm), then it's just a matter of using rbf (and so not on the plague build-farm) to test an image. Obviously I can do that , if being pointed to the uboot image to include for that image. Also worth noting that my plan would be to reconfigure from scratch the current plague setup, as it currently runs on Fedora 21, so a need to migrate it to CentOS 7 userland, now that it exists. At the same time, I'd like to tie it with the newer auth backend (https://accounts.centos.org) instead of the (locally) generated certs. For arm64, there is no community buildsys available - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlaNCSkACgkQnVkHo1a+xU6aoACeOmd0bxxyFZovhKhLS57Nfrnc FIQAnRD3cCGRYsAU1LZMeCcDc//RmGMQ =4oYs -----END PGP SIGNATURE-----