Bug 157027 - gulm packaging nits
gulm packaging nits
Product: Fedora
Classification: Fedora
Component: gulm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Feist
Depends On:
  Show dependency treegraph
Reported: 2005-05-06 06:51 EDT by Joe Orton
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.0.0.pre30.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-04 19:15:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Orton 2005-05-06 06:51:22 EDT
# chkconfig: 22 78
# description: start/stop the gulm lock daemon

Installing gulm-1.0-0.pre28.6.i386.
service lock_gulmd does not support chkconfig
error: %post(gulm-1.0-0.pre28.6.i386) scriptlet failed, exit status 1

also, a packaging nit:

any -devel package should require a matching VR of main package, i.e.

Requires: gulm = %{version}-%{release}
Comment 1 Joe Orton 2005-05-06 06:58:59 EDT
Bill fixed the former.  The missing Requires remains; other issues:

2. gulm-devel %description needs expanding at least to have the standard "This
package contains... " text for a -devel package
3. /usr/lib/libgulm.so should be in the -devel package not the main package
unless there is some app which does dlopen("libgulm.so", ...) at runtime.
4. add a %doc COPYING at least to the main package
5. lock_gulm(8) has odd formatting in the OPTIONS section:


You  can completely configure gulm from the command line.  If you
do this, you need to use the same options on every  node  in  the
Comment 2 Joe Orton 2005-05-06 07:02:27 EDT
6. also missing deps for the scriptlets, add:

Requires(post,preun): /sbin/chkconfig

to the main package

7. use the %{ix86} macro in place of i386 in the ExclusiveArch line, since
people can validly attempt to build this package for an athlon or i686 target.
Comment 3 Chris Feist 2005-05-23 11:40:22 EDT
All of these should be fixed in the latest release of gulm (1.0.0.pre30.0+)

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