On 12/03/16 19:41, Gordan Bobic wrote: > It would appear that above group isn't defined, but it is what mock uses > to build a minimal development chroot. Is the omission of this group > deliberate or accidental? > > I can add it trivially enough through a dummy repository containing > nothing but a group definition, but I'm curious as to whether there is a > good reason for this not being there in the first place. > > Gordan AFAIK we all stopped using a @buildsys group for the chroot_setup_cmd (for all CentOS 7 builds), but rather the common list of pkgs to be in the buildroot. See for example the mock config files (and c7.00.00 being one example) : https://git.centos.org/blob/sig-core!bld-seven.git/29517e030ebfb5c376dd742711077ac305e8c269/mock!c7.00.00-x86_64.cfg#L5 Cheers, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -------------- 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/arm-dev/attachments/20160312/6d130b11/attachment-0006.sig>