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
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/29517e030ebfb5c376dd74271...
Cheers,
This is correct. The mock config used to build aarch64 is very similar to the x86_64 config, in that the group is not used and the packages are defined individually.
On 03/12/2016 02:24 PM, Fabian Arrotin wrote:
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/29517e030ebfb5c376dd74271...
Cheers,
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
The mock package that ships with aarch64 CentOS 7 seems to still require the buildsys-build group, though:
Warning: Package group buildsys-build does not exist.
I created it by taking the epel-7-x86_64 config, and changed it for aarch64 (arch markers and repositories repointed to aarch64 CentOS 7).
Adding a dummy repository works, but it does appear to not be working the way as described (albeit it is working the way I expect).
Gordan
On 14/03/16 17:07, Jim Perrin wrote:
This is correct. The mock config used to build aarch64 is very similar to the x86_64 config, in that the group is not used and the packages are defined individually.
On 03/12/2016 02:24 PM, Fabian Arrotin wrote:
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/29517e030ebfb5c376dd74271...
Cheers,
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
I didn't modify the centos mock package at all. It's a rebuild of what exists in epel. In theory once epel exists for aarch64, most of the issues should fall away.
On 03/20/2016 03:50 AM, Gordan Bobic wrote:
The mock package that ships with aarch64 CentOS 7 seems to still require the buildsys-build group, though:
Warning: Package group buildsys-build does not exist.
I created it by taking the epel-7-x86_64 config, and changed it for aarch64 (arch markers and repositories repointed to aarch64 CentOS 7).
Adding a dummy repository works, but it does appear to not be working the way as described (albeit it is working the way I expect).
Gordan
On 14/03/16 17:07, Jim Perrin wrote:
This is correct. The mock config used to build aarch64 is very similar to the x86_64 config, in that the group is not used and the packages are defined individually.
On 03/12/2016 02:24 PM, Fabian Arrotin wrote:
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/29517e030ebfb5c376dd74271...
Cheers,
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Fabian Arrotin -
Gordan Bobic -
Jim Perrin