[Bug 834239] Review Request: monobristol - frontend for britsol in mono

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=834239

--- Comment #7 from Jørn Lomax <northlomax at gmail.com> ---
I always run rpmlint and mock before submiting an updated package. I'll admit i
only use the default mock configuration though. I'll make sure to run it on
both rawhide and stable from now on. I looked everywhere for that macro, wiki,
google and i grep'ed both /etc/rpm and /usr/lib/rpm/macro in hopes of finding
it, no luck.


What i did not know was that i could run rpmlint on .rpm files, i thought i
would get the same output as with the srpms, Now,

SPEC: http://jvlomax.fedorapeople.org/packeging/monobristol.spec
SRPMS: 
http://jvlomax.fedorapeople.org/packeging/monobristol-0.60.3-5.fc17.src.rpm


rpmlint on the specfile comes out clean

rpmlint on SRPMS:
>[makerpm at Fafnir SPECS]$ rpmlint ../SRPMS/monobristol-0.60.3-5.fc17.src.rpm 
>monobristol.src: W: spelling-error Summary(en_US) bristol -> Bristol, bristle, >bristly
>monobristol.src: W: spelling-error %description -l en_US subtractive -> >subtracting, subtracted, subtract
>1 packages and 0 specfiles checked; 0 errors, 2 warnings.

rpmlint on the built package:
>monobristol.i686: W: spelling-error %description -l en_US subtractive -> >subtracting, subtracted, subtract
>monobristol.i686: E: no-binary
>monobristol.i686: W: only-non-binary-in-usr-lib
>monobristol.i686: W: no-manual-page-for-binary monobristol
>monobristol.i686: W: percent-in-%post

>From what i have read on the wikipage, the no-binary error is solved by making
the package a "noarch" package? Which  bring up another question i have. When i
was searching for macros earlier, i found one titled %mono_arches which is the
arches mono builds on. Should i be using this (i was originally, and was told
not to anymore)

As for getting it to run? is bristol showing up at all after you have pressed a
button, or is the monobristol gui not showing at all? I never got any sound
from bristol without running it through JACK instead of alsa

-- 
You are receiving this mail because:
You are on the CC list for the bug.