RE: Replies tearing threads apart [Was: %ifarch note]

2013-10-11 Thread Mamoru TASAKA
> On 10/11/2013 09:26 AM, Mamoru TASAKA wrote: > > (Currently my reply seems to create new thread...) > Are you replying from a SmartPhone or other Android-Device? > > I have been observing this issue for quite a while and when ever asking > senders about their equipement they replied "Android-S

Replies tearing threads apart [Was: %ifarch note]

2013-10-11 Thread Ralf Corsepius
On 10/11/2013 09:26 AM, Mamoru TASAKA wrote: (Currently my reply seems to create new thread...) Are you replying from a SmartPhone or other Android-Device? I have been observing this issue for quite a while and when ever asking senders about their equipement they replied "Android-SmartPhone".

RE: RE: %ifarch note

2013-10-11 Thread Mamoru TASAKA
> On Oct 11, 2013 1:55 PM, "Mamoru TASAKA" wrote: > > > > > Since I hit this, I'd imagine other people might. > > > If your package has: > > > > > > BuildArch: noarch > > > > > > It will set %{_target_cpu} to "noarch". > > > > > > If you also use %ifarch in that spec file, you might be expecting i

RE: %ifarch note

2013-10-10 Thread Christopher Meng
On Oct 11, 2013 1:55 PM, "Mamoru TASAKA" wrote: > > > Since I hit this, I'd imagine other people might. > > If your package has: > > > > BuildArch: noarch > > > > It will set %{_target_cpu} to "noarch". > > > > If you also use %ifarch in that spec file, you might be expecting it to > > match %{_ar

RE: %ifarch note

2013-10-10 Thread Mamoru TASAKA
> Since I hit this, I'd imagine other people might. > If your package has: > > BuildArch: noarch > > It will set %{_target_cpu} to "noarch". > > If you also use %ifarch in that spec file, you might be expecting it to > match %{_arch} (the architecture of the build server). It does not. It > matc

Re: %ifarch note

2013-10-10 Thread Adam Jackson
On Thu, 2013-10-10 at 13:06 +0200, punto...@libero.it wrote: > Il 10/10/2013 04:12, Tom Callaway ha scritto: > > Since I hit this, I'd imagine other people might. > > > > If your package has: > > > > BuildArch: noarch > > > > It will set %{_target_cpu} to "noarch". > > > > If you also use %ifarch i

Re: %ifarch note

2013-10-10 Thread punto...@libero.it
Il 10/10/2013 04:12, Tom Callaway ha scritto: Since I hit this, I'd imagine other people might. If your package has: BuildArch: noarch It will set %{_target_cpu} to "noarch". If you also use %ifarch in that spec file, you might be expecting it to match %{_arch} (the architecture of the build

%ifarch note

2013-10-09 Thread Tom Callaway
Since I hit this, I'd imagine other people might. If your package has: BuildArch: noarch It will set %{_target_cpu} to "noarch". If you also use %ifarch in that spec file, you might be expecting it to match %{_arch} (the architecture of the build server). It does not. It matches %{_target_cpu}.