Bug 568638 - Review Request: smx - httpd server macro language
Review Request: smx - httpd server macro language
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-02-26 03:14 EST by erik aronesty
Modified: 2012-07-03 17:39 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-07-03 17:39:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
rpmlint output (11.55 KB, text/plain)
2010-02-26 03:14 EST, erik aronesty
no flags Details

  None (edit)
Description erik aronesty 2010-02-26 03:14:39 EST
Created attachment 396490 [details]
rpmlint output

Spec URL: http://www.smxlang.org/smx.spec
SRPM URL: http://smx.googlecode.com/files/smx-1.1.4-437.src.rpm

SMX is a text-embedded macro processing language with extended support for inclusion in web-pages.  Core features include database access and image manipulation.

- this is my first package, and i am seeking a sponsor

- rpmlint spews a ton of lint for the installed %macro documentation since macros contain percent signs.  i'd like to keep the "man %func" as a feature which users seem to like, but not if everyone here hates it...
Comment 1 Till Maas 2010-03-29 08:04:16 EDT
This is probably wrong:
strip --strip-unneeded %{buildroot}/%{_libdir}/*.so
strip --strip-unneeded %{buildroot}/%{_bindir}/smx*

The files are automatically stripped by rpm and the information is stored in
the debuginfo package. When you do this yourself, the debuginfo packages will
be useless.

You can try this to get the rpmlin errors away:

The %% represents one % in SPEC files.
Comment 2 Jason Tibbitts 2010-11-17 18:43:22 EST
Any response to this commentary?  It's been months.
Comment 3 erik aronesty 2010-11-18 04:42:16 EST
Sorry, I made both changes:

1- without the strip lines, i get "unstripped binary" errors in rpmlint, and the binary is, indeed, never stripped

2- the two percent signs helped a little (one error saved out of 90)... but I still get flooded with errors on that.   the problem is that the "files" glob expansion doesn't quote percent signs.
Comment 4 erik aronesty 2010-11-18 07:10:11 EST
Trying to figure out what to do instead of strip, and how to get the glob to put two % signs in the rpm .... when the file path has a % sign.
Comment 5 Till Maas 2010-11-18 12:08:34 EST
(In reply to comment #3)

> 1- without the strip lines, i get "unstripped binary" errors in rpmlint, and
> the binary is, indeed, never stripped

Then there should be some errors shown by a script called find-debuginfo.sh or similiar at the end of the build. The script is responsible to strip all binaries.
Comment 6 erik aronesty 2010-11-19 07:29:39 EST
I'm definitely not dong something correct when it comes to debug builds.  I never got a debuginfo RPM.  Links to the output of rpmbuild -v -ba .... without the compilation steps for readability.

abbreviated rpmbuild with -v: 
(full output):

You can see it only ever writes the rpm, srpm and devel rpm (with the header).   Nothing else.
Comment 7 Jason Tibbitts 2012-06-15 16:11:05 EDT
It seems that the whiteboard never got cleared when you responded so this has been hidden from the review reports for months.  I would just close this out because it's so old, but just in case:

Are you still remotely interested in submitting this package?  The last spec I see needs some work but I'm sure everything can be beaten into shape if you still want to work on it.
Comment 8 Jason Tibbitts 2012-07-03 17:39:34 EDT
At this point I think I'll just go ahead and close this.  I'm really sorry that the process broke down here but at this point there's not much that I can do about it.  If you do wish to submit this in the future, please feel free to reopen this ticket, or open a new one and make sure I'm CC'd on it.

Note You need to log in before you can comment on or make changes to this bug.