Red Hat Bugzilla – Bug 1271977
RFE - asking for el7 i386 build option
Last modified: 2017-11-03 01:26:24 EDT
Description of problem:
There is no epel-7-i386 chroot available for people to use copr
Version-Release number of selected component (if applicable):
Try to create a copr repo/project to build el7 i386 packages
Steps to Reproduce:
It's a current known fact that epel-7 i386 doesn't exist (yet ?) but CentOS 7 i386 already exists (http://mirror.centos.org/altarch/7/os/i386/) so why not using it for el7 i386 buildroot ?
a working build environment
Chroot was added but it is no-op as there is no epel-7-i386 mock config and there are no epel-7-i386 repos. I think, without epel-7-i386 base, we cannot really do much. I started this thread https://firstname.lastname@example.org/thread/OJVTY5MWCZXPLKACU6MPRRRHJCUN5JE4/. We will see where it goes.
Maybe for now it would actually mostly work use the x86-64 configuration but just make sure that the target is i386. That allows me to build i386 RPMs on my x86-64 system at least.
Figured I'd provide a real world use case for the ticket: Skype
Skype is currently 32bit only and the official RPM requires qtwebkit.i686 which is not provided by EPEL7. EPEL7 does have qtwebkit.x86_64.
I disabled the chroot for the lack of epel-7-i386 repos.
Well, the option is to point to CentOS i386 repo (AltArch) which exists and you can then have a mock chroot with i386 pkgs .. that's how I built my wine i386 packages for x86_64 desktops
Or is the issue the fact that you don't/can't enable CentOS repositories in Copr ?
(In reply to Fabian Arrotin from comment #5)
> Well, the option is to point to CentOS i386 repo (AltArch) which exists and
> you can then have a mock chroot with i386 pkgs .. that's how I built my wine
> i386 packages for x86_64 desktops
> Or is the issue the fact that you don't/can't enable CentOS repositories in
> Copr ?
We don't have just CentOS chroot. Only CentOS + EPEL and EPEL7 does not seem to exists for i386.
I think if you need something like that you could use the custom chroot and configure repositories and buildroot packages manually (in Project Settings -> "Edit" ...for the custom chroot). It's not the same thing for user, I admit. We would need to let users pick their own name for a custom chroot.