Spec Name or Url: Attached as sparse.spec SRPM Name or Url: Must build separately Description: A C semantic parser. While flailing and failing to resolve a kernel issue, I followed this "sparse" tangent and now have a sparse RPM for Fedora. The Linux kernel build system directly supports sparse, and including it in Fedora Extras would be a convenience to anyone wishing to attempt to use it. Because of compat-i386.c, the spec file may require: ExclusiveArch:i386 The license is OSL V1.1, but exemptions included in the license imply executables linking to the library itself (sparse) are not considered "Original Work". A kernel-2.6.spec.patch (for kernel-smp-2.6.15-1.2041) is attached to provide a convenient way to use sparse when rebuilding the kernel. Attached are: sparse.spec sparse-0.1-Makefile.patch kernel-2.6.spec.patch To git (from git-core) tarball: git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git cd sparse git-tar-tree HEAD sparse-0.1 | gzip > ../sparse-0.1.tar.gz rpmlint output: W: sparse invalid-license OSL W: sparse-debuginfo invalid-license OSL W: sparse-debuginfo objdump-failed W: sparse-devel invalid-license OSL
Created attachment 126063 [details] Sparse RPM spec file
Created attachment 126064 [details] Generate shared objects patch
Created attachment 126065 [details] Adds sparse support to kernel-2.6 (2041)
Created attachment 126107 [details] Sparse RPM spec file
Created attachment 126108 [details] Generate shared objects patch
Created attachment 126234 [details] Adds sparse support to kernel-2.6 (2054)
Created attachment 126235 [details] Sparse RPM spec file
Created attachment 126236 [details] Generate shared objects patch
I think its great that you've created a spare package and waht to make this available to others through FE. But first you really should learn some stuff about FE procedures. I didn't find your bkyoung account in onwers.list, so I assume that this is your first package. To become an FE packager you must follow the following procedure: http://fedoraproject.org/wiki/Extras/Contributors As is Outlined in the "Create Your Review Request" step you should have added the FE-NEEDSPONSOR blocker bug, since this is your first package. Please read the above page, the packaging guidelines and the review procedure wikipages thoroughly so that you can learn and understant the FE process / procedures. Also it is uncommon for package reviewers to have to put all the pieces like a git checkout and all your attachments together themselves. Instead create a .src.rpm file (rpmbuild -bs sparse.spec) upload that somewhere and put an URL in the review request (iow here in BZ).
Anything happening here? It's been two months.
*** This bug has been marked as a duplicate of 212513 ***