Bug 206277 - src package install warns about missing mockbuild user/group
src package install warns about missing mockbuild user/group
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: mock (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-13 09:54 EDT by David Timms
Modified: 2013-01-09 20:32 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-13 10:13:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Timms 2006-09-13 09:54:45 EDT
Description of problem:
Install a src.rpm
rpm script complains that user and group mockbuild don't exist.

Version-Release number of selected component (if applicable):
mock                    i386       0.6.4-1.fc6      extras-development 
  {fc6t2+2006-09-13 devel}

How reproducible:
install of both the gkrellm and dia src generate these messages.

Steps to Reproduce:
1. wget
http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/dia-0.95-7.fc6.src.rpm
2. rpm -Uvh dia-0.95-7.fc6.src.rpm
  
Actual results:
   1:dia                warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root

Expected results:
########################################### [100%]  :)

Additional info:
src rpm install of the same package in FC5 just showed the expected result.
If mock package install created this user and group, then the above would just
work. (It would also save having to chown the files {away from root} after
installing the .src.rpm)
- or maybe this is not the "best practice" way to go about it ?
Comment 1 Jesse Keating 2006-09-13 10:13:04 EDT
This is expected result.  The package files will get the ownership of whomever
built the package, in mock's case mockbuild.  The warnings are benign and should
be ignored.

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