FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 11-14-2008, 03:31 PM
Conrad Meyer
 
Default why koji try to build on ppc when ExcludeArch ppc?

On Friday 14 November 2008 08:18:58 am Jason L Tibbitts III wrote:
> >>>>> "FL" == Farkas Levente <lfarkas@lfarkas.org> writes:
>
> FL> why try to build on ppc? it's a koji bug?
>
> It's a noarch package, so it just gets assigned randomly to the pool.
> I thought that koji did check excludearch lines even for noarch
> packages, but maybe that's just the compose tools.
>
> - J<

Don't believe so -- I've run into this in the past.

--
Conrad Meyer <konrad@tylerc.org>


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 11-14-2008, 03:36 PM
Jason L Tibbitts III
 
Default why koji try to build on ppc when ExcludeArch ppc?

Actually, the problem is pretty clear: you simply cannot do what
you're trying to do.

If your package won't even build on PPC, it simply can't be noarch.
The ExcludeArch: case for noarch packages is for those with runtime
dependencies that aren't available for all architectures. That's not
the case you're seeing.

Your options are either to wait until the JRE bug is fixed or make
your package arch-specific.

- J<

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 11-14-2008, 09:25 PM
Farkas Levente
 
Default why koji try to build on ppc when ExcludeArch ppc?

Jason L Tibbitts III wrote:
> Actually, the problem is pretty clear: you simply cannot do what
> you're trying to do.
>
> If your package won't even build on PPC, it simply can't be noarch.
> The ExcludeArch: case for noarch packages is for those with runtime
> dependencies that aren't available for all architectures. That's not
> the case you're seeing.
>
> Your options are either to wait until the JRE bug is fixed or make
> your package arch-specific.

no it's not that easy. the question is:
what the noarch means?
- it should have to be run on any arch?
or
- it should have to be run _AND_ build on any arch?
this package is a pure java package which is noarch the the result
gstreamer-java-1.0-1.fc10.noarch.rpm can be run on any arch,
BUT as there is a bug in #468831 in
java-1.6.0-openjdk on ppc it can't be compiled on ppc.
so if eg. there is a bug in python compiler or in the python interpreter
on ppc then the python packages no longer noarch packages?

--
Levente "Si vis pacem para bellum!"

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 11-14-2008, 11:44 PM
Michael Schwendt
 
Default why koji try to build on ppc when ExcludeArch ppc?

On Fri, 14 Nov 2008 23:25:07 +0100, Farkas Levente wrote:

> what the noarch means?
> - it should have to be run on any arch?
> or
> - it should have to be run _AND_ build on any arch?

The tag is "BuildArch", which refers to the target arch as in "build for".

"noarch" means the built package is not specific to a particular arch. It
may be used on any arch.

Imagine that any of your build requirements (including many core tools
like "install", "mkdir", "patch", "sed", "bash", "rpmbuild", "dos2unix",
"convert", "iconv") may break on any platform and temporarily make it
impossible to build your noarch pkg on that platform. Just that with
Java you cannot simply replace the build tool.

> this package is a pure java package which is noarch the the result
> gstreamer-java-1.0-1.fc10.noarch.rpm can be run on any arch,
> BUT as there is a bug in #468831 in
> java-1.6.0-openjdk on ppc it can't be compiled on ppc.
> so if eg. there is a bug in python compiler or in the python interpreter
> on ppc then the python packages no longer noarch packages?

Yes. Noarch packages with strict [build/run-time] dependencies on
arch-specific packages are contaminative ("poisonous"). Any
arch-specific package, which is needed to rebuild the noarch package,
must be available and must work on _any_ platform supported by the
buildsys. Even if you don't need an interpreter at build-time, you
likely need it at run-time. If you drop the run-time dependency, you
may win, and the package may become installable, but the package would
not work if the interpreter is missing/broken. Under the hood, the
noarch package becomes arch-specific -- in the worst-case, it becomes
unusable (or even uninstallable and not rebuildable).

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 05:39 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org