Am Donnerstag, den 13.06.2013, 19:09 +0200 schrieb Mattias Ellert:
tor 2013-06-13 klockan 17:34 +0200 skrev Simone Caronni:
>
> Exactly, here an example of a Koji build done with _isa'ed
> BuildRequires (taken from the link I've posted before):
>
> $ rpm -qpR libguac-client-vnc-0.6.0-4.fc17.src.rpm
> cairo-devel(x86-64)
> gnutls-devel(x86-64)
> libguac-devel(x86-64) = 0.6.0
> libvncserver-devel(x86-64)
> rpmlib(FileDigests) <= 4.6.0-1
> rpmlib(CompressedFileNames) <= 3.0.4-1
>
> This means I can't rebuild the src.rpm on an i686. This is wrong.
If what you say above was true it would be a problem. But it doesn't
work like that.
$ uname -p
x86_64
$ rpm -q --requires -p globus-common-14.9-3.fc18.src.rpm | grep x86
globus-core(x86-32) >= 8
libtool-ltdl-devel(x86-32)
$ rpm -q --whatprovides 'globus-core(x86-32)'
'libtool-ltdl-devel(x86-32)'
inget paket tillhandahåller globus-core(x86-32)
inget paket tillhandahåller libtool-ltdl-devel(x86-32)
$ rpmbuild --rebuild globus-common-14.9-3.fc18.src.rpm
... build succeeds ... because the BRs needed on the build system's architecture are
there
[ellert@localhost ~]$ rpm -q --whatprovides 'globus-core(x86-64)'
'libtool-ltdl-devel(x86-64)'
globus-core-8.9-6.fc18.x86_64
libtool-ltdl-devel-2.4.2-7.fc18.x86_64
The _isa-macro _ALWAYS_ evals x86-64 on x86_64, even if the binary-rpm
is build against i686-devel/libs...
Or to be more clear: If you build an rpm on x86_64 against i686 libs the
resulting bin-rpm will _ALWAYS_ provide x86-64-arched.
The bogus requires in the created source rpm is no reason to write a
broken spec file.
What will break the spec by removing _isa-macro from BRs? Is there any
PROVEN reason for this? I'm NOT talking about the final-Requires in
spec.
Sorry for the double post. :)