[java-sig-commits] [Bug 794913] New: jetty user creation is broken
bugzilla at redhat.com
bugzilla at redhat.com
Fri Feb 17 21:56:24 UTC 2012
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: jetty user creation is broken
https://bugzilla.redhat.com/show_bug.cgi?id=794913
Summary: jetty user creation is broken
Product: Fedora
Version: 17
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: unspecified
Component: jetty
AssignedTo: jjohnstn at redhat.com
ReportedBy: orion at cora.nwra.com
QAContact: extras-qa at fedoraproject.org
CC: jjohnstn at redhat.com, overholt at redhat.com,
sochotni at redhat.com,
java-sig-commits at lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
The BuildRequires on fedora-usermgmt-devel and %{?FE_USERADD_REQ} was removed
but %pre and %postun still make use of the macros defined in there. This
results in those macros not getting expanded at build time:
# rpm -q --scripts jetty
preinstall scriptlet (using /bin/sh):
# Add the "jetty" user and group
%__fe_groupadd 110 -r jetty &>/dev/null || :
# Use /bin/sh so init script will start properly.
%__fe_useradd 110 -r -s /bin/sh -d /usr/share/jetty -M \
-g jetty jetty &>/dev/null || :
postuninstall scriptlet (using /bin/sh):
%__fe_userdel jetty &>/dev/null || :
%__fe_groupdel jetty &>/dev/null || :
12:41:12 Installing jetty-8.1.0-1.fc17.noarch
/var/tmp/rpm-tmp.YheWdg: line 2: fg: no job control
/var/tmp/rpm-tmp.YheWdg: line 4: fg: no job control
warning: user jetty does not exist - using root
warning: group jetty does not exist - using root
warning: user jetty does not exist - using root
warning: group jetty does not exist - using root
warning: user jetty does not exist - using root
warning: group jetty does not exist - using root
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the java-sig-commits
mailing list