Bug 1382120

Summary:	nut-2.7.2-3 packages do not install cleanly
Product:	[Fedora] Fedora EPEL	Reporter:	Doug Kelly <djk7wb>
Component:	nut	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	mhlavink, orion
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-13 17:44:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Doug Kelly 2016-10-05 19:19:46 UTC

Description of problem:
The various nut packages (built out of the nut SRPM) all have a hard-coded dependency on adding the user "nut" with a uid of 57 -- which is in use by the user "comp" on a normal install.  Additionally, when correcting this problem manually and rolling a new RPM myself, I found that that the build dependencies do not specify gcc or gcc-c++ -- might be overly-pedantic, but they are required for the build to complete.

Version-Release number of selected component (if applicable):
2.7.2-3

How reproducible:
Always

Steps to Reproduce:
1. Install epel repository
2. yum install nut nut-client

Actual results:
Packages fail to install because of a dependency on the "nut" user, which can't be added because of the uid conflict.  Additionally, attempting to remove the half-installed packages causes warnings because the manifests appear to list files which don't exist.

Expected results:
Package should install and uninstall cleanly

Additional info:
This was found on an install with the Infrastructure Server, base and core package groups installed, as well as git and kexec-tools.  While I tried to keep the configuration as clean as possible, I have not replicated this on a 100% pristine install.

Comment 1 Orion Poplawski 2016-10-05 19:52:57 UTC

Where is the "comp" user coming from?  I've never heard of it.

Comment 2 Michal Hlavinka 2016-10-13 17:44:23 UTC

(In reply to Doug Kelly from comment #0)
> Description of problem:
> The various nut packages (built out of the nut SRPM) all have a hard-coded
> dependency on adding the user "nut" with a uid of 57 -- which is in use by
> the user "comp" on a normal install. 

wrong assumption, the thing that creates comp user with uid 57 is the wrong one,
nut has reserved uid/gid 57, see /usr/share/doc/setup/uidgid

> Additionally, when correcting this
> problem manually and rolling a new RPM myself, I found that that the build
> dependencies do not specify gcc or gcc-c++ -- might be overly-pedantic, but
> they are required for the build to complete.

This is how we specify build dependencies. Generic "default" build dependencies are expected to be on the system. This is bash, sh, cat, grep, ls, sed, awk, gcc, g++,...Those are not specified in the list of build dependencies.