Paul F. Johnson (pfj) wrote:
Author: pfj
Update of /cvs/extras/rpms/z88dk/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23212/devel
Modified Files:
z88dk.spec
Log Message:
auto-import z88dk-1.6-8 on branch devel from z88dk-1.6-8.src.rpm
Index: z88dk.spec
===================================================================
RCS file: /cvs/extras/rpms/z88dk/devel/z88dk.spec,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- z88dk.spec 13 Jan 2006 00:19:34 -0000 1.1
+++ z88dk.spec 9 Mar 2006 10:33:10 -0000 1.2
@@ -1,13 +1,14 @@
Summary: A Z80 cross compiler
Name: z88dk
...
+ExcludeArch: x86_64 ia64
...
%changelog
+* Thu Mar 9 2006 Paul F. Johnson <paul@xxxxxxxxxxxxxxxxxxxxxx> - 1.6-8
+- Added ExcludeArch for ia64
+
* Mon Oct 17 2005 Paul F. Johnson <paul@xxxxxxxxxxxxxxxxxxxxxx> - 1.6-7
- Add ExcludeArch for x86_64 machines
You need to raise a bug on z88dk to track the ExcludeArch and make sure
it doesn't get forgotten:
See: http://fedoraproject.org/wiki/Packaging/ReviewGuidelines
If the package does not successfully compile, build or work on an
architecture, then those architectures should be listed in the spec in
ExcludeArch. Each architecture listed in ExcludeArch needs to have a bug
filed in bugzilla, describing the reason that the package does not
compile/build/work on that architecture. The bug number should then be
placed in a comment, next to the corresponding ExcludeArch line. New
packages will not have bugzilla entries during the review process, so
they should put this description in the comment until the package is
approved, then file the bugzilla entry, and replace the long explanation
with the bug number. The bug should be marked as blocking one (or more)
of the following bugs to simplify tracking such issues: [179258]
FE-ExcludeArch-x86, [179259] FE-ExcludeArch-x64, [179260] FE-ExcludeArch-ppc
Paul.
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
