Description of problem: Mock seems to insists to use 499 for group mock and this fails. Version-Release number of selected component (if applicable): mock-1.1.1-1.fc13.noarch How reproducible: Steps to Reproduce: 1. mock -r epel-6-i386 --rebuild rpm/Conn-1.0.31-1.src.rpm 2. 3. Actual results: Expected results: Additional info: mock -r epel-6-i386 --rebuild rpm/Conn-1.0.31-1.src.rpm INFO: mock.py version 1.1.1 starting... State Changed: init plugins State Changed: start INFO: Start(rpm/Conn-1.0.31-1.src.rpm) Config(epel-6-i386) State Changed: lock buildroot State Changed: clean State Changed: init State Changed: lock buildroot Mock Version: 1.1.1 INFO: Mock Version: 1.1.1 INFO: enabled root cache INFO: enabled yum cache State Changed: cleaning yum metadata State Changed: running yum ERROR: Exception(rpm/Conn-1.0.31-1.src.rpm) Config(epel-6-i386) 26 minutes 57 seconds INFO: Results and/or logs in: /var/lib/mock/epel-6-i386/result ERROR: Command failed. See logs for output. # ['/usr/sbin/groupadd', '-g', '499', 'mockbuild']
Group 499 is 'vsca'.
It's likely that whatever package creates the vcsa group is doing it wrongly, and assuming that they are getting a specific GID when they aren't. What package is providing that user?
Seems that MAKEDEV is adding that group (http://www.rpmseek.com/rpm/MAKEDEV-3.24-1.src.html?hl=de&cx=0:-:0:6166934:0:0:0&ShowChangeLog=1).
Ok, there seems to be a bit of a bug in MAKEDEV in that while it picks a specific UID it doesn't pre-create the group ID to match, thus the vcsa group gets dynamically assigned. Changing bug topic and package.