RE: Replies tearing threads apart [Was: %ifarch note]
> 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". > > Seems to me, as if some Android-MUAs might not be able to preserve > threads or might tweak them in a way, thunderbird isn't able to sort > them correctly. > > Ralf No, currently I (have to) use a web mail service. When I am back I can use thunderbird. Regards, Mamoru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Replies tearing threads apart [Was: %ifarch note]
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". Seems to me, as if some Android-MUAs might not be able to preserve threads or might tweak them in a way, thunderbird isn't able to sort them correctly. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
RE: RE: %ifarch note
> 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 %{_arch} (the architecture of the build server). It does not. It
> > > matches %{_target_cpu}.
> > >
> > > If you need to conditionalize on the value of %{_arch} in such a spec
> > > file, you need to do it explicitly:
> > >
> > > %if %{_arch} == x86_64 || %{_arch} == i686
> > >
> > > Hope that helps other folks,
> > >
> > > ~tom
> >
> > Using %if %{_arch} == x86_64 || %{_arch} == i686 seems to break building
> > srpm
> > on arm koji:
> > http://koji.fedoraproject.org/koji/taskinfo?taskID=6049393
> > (when making srpm on i686 or x86_64, it seems okay).
> >
> > Perhaps when building srpm on arm, _arch is not defined on koji.
> >
> > Regards,
> > Mamoru
> Till just told me about %ifnarch %{arm}.
> Is it better?
This is explained in the original spot's mail (, which
is included in this mail), i.e.
when "BuildArch: noarch" exists, %ifarch or %ifnarch
doesn't work as expected (when building binary rpm).
(Currently my reply seems to create new thread...)
Regard,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
RE: %ifarch note
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 %{_arch} (the architecture of the build server). It does not. It
> > matches %{_target_cpu}.
> >
> > If you need to conditionalize on the value of %{_arch} in such a spec
> > file, you need to do it explicitly:
> >
> > %if %{_arch} == x86_64 || %{_arch} == i686
> >
> > Hope that helps other folks,
> >
> > ~tom
>
> Using %if %{_arch} == x86_64 || %{_arch} == i686 seems to break building
srpm
> on arm koji:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6049393
> (when making srpm on i686 or x86_64, it seems okay).
>
> Perhaps when building srpm on arm, _arch is not defined on koji.
>
> Regards,
> Mamoru
Till just told me about %ifnarch %{arm}.
Is it better?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
RE: %ifarch note
> 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}.
>
> If you need to conditionalize on the value of %{_arch} in such a spec
> file, you need to do it explicitly:
>
> %if %{_arch} == x86_64 || %{_arch} == i686
>
> Hope that helps other folks,
>
> ~tom
Using %if %{_arch} == x86_64 || %{_arch} == i686 seems to break building srpm
on arm koji:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6049393
(when making srpm on i686 or x86_64, it seems okay).
Perhaps when building srpm on arm, _arch is not defined on koji.
Regards,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: %ifarch note
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 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}.
> >
> > If you need to conditionalize on the value of %{_arch} in such a spec
> > file, you need to do it explicitly:
> >
> > %if %{_arch} == x86_64 || %{_arch} == i686
> >
> > Hope that helps other folks,
> >
> > ~tom
>
> sorry for the silly question
> isn't the same use:
> %ifarch %{arm}
> for e.g. skip test suite only if the builder is arm?
> see https://bugzilla.redhat.com/show_bug.cgi?id=991712
For archful packages %ifarch probably works as you expect; spot's caveat
was about building noarch packages.
- ajax
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: %ifarch note
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 server). It does not. It
matches %{_target_cpu}.
If you need to conditionalize on the value of %{_arch} in such a spec
file, you need to do it explicitly:
%if %{_arch} == x86_64 || %{_arch} == i686
Hope that helps other folks,
~tom
==
Fedora Project
sorry for the silly question
isn't the same use:
%ifarch %{arm}
for e.g. skip test suite only if the builder is arm?
see https://bugzilla.redhat.com/show_bug.cgi?id=991712
regards
gil
<>--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
%ifarch note
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}.
If you need to conditionalize on the value of %{_arch} in such a spec
file, you need to do it explicitly:
%if %{_arch} == x86_64 || %{_arch} == i686
Hope that helps other folks,
~tom
==
Fedora Project
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
