Bug 24171 - group utmp does not exist
group utmp does not exist
Product: Red Hat Linux
Classification: Retired
Component: gnome-libs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Owen Taylor
Florence Gold
Depends On:
  Show dependency treegraph
Reported: 2001-01-16 19:46 EST by Jeremy Katz
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-01 18:12:17 EST
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 Jeremy Katz 2001-01-16 19:46:34 EST
gnome-libs needs to preinstall utempter so that the utmp group will exist
when gnome-libs is installed
Comment 1 Jeremy Katz 2001-01-16 19:47:43 EST
sorry, beta2 with gnome-libs-1.2.8-1
Comment 2 Glen Foster 2001-01-17 13:19:10 EST
This defect is considered MUST-FIX for Florence Gold release
Comment 3 Nalin Dahyabhai 2001-01-22 13:24:44 EST
The utmp group is created by the initscripts %pre scriptlet, so adding a Prereq:
on initscripts should take care of this.
Comment 4 Elliot Lee 2001-02-01 18:12:13 EST
utempter also creates the utmp group, and is less likely to have extraneous
depdendencies, so it probably makes more sense to depend on it.
Comment 5 Elliot Lee 2001-02-07 16:17:28 EST
Fixed in gnome-libs-1.2.8-6 by adding the utempter dependency.
Comment 6 Mike A. Harris 2006-07-28 01:06:49 EDT
The spec also contains the following comment:
# Added to avoid the warning messages about utmp group, bug #24171
# fixme, just libzvt?

zvt doesn't appear to be in libgnome, or in Fedora for that matter.  A
complete grep of libgnome, vte shows no sign of utempter usage.

Since we're replacing the Red Hat utempter with the alternative
implementation named 'libutempter' in FC6, while updating the packages
that depend on utempter I noticed this.

Since I can't be easily sure wether or not a dependency still exists,
I thought I'd mention it here.  It is possible the dependency might
be able to be removed now, but I'll leave that to the discretion of
the package maintainer.

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