Package Details: mock 3.1-1.1

Git Clone URL: (read-only, click to copy)
Package Base: mock
Description: A simple chroot build environment manager for building RPMs
Upstream URL:
Licenses: GPL2
Submitter: td123
Maintainer: larchunix
Last Packager: larchunix
Votes: 3
Popularity: 0.000000
First Submitted: 2011-02-23 05:50 (UTC)
Last Updated: 2022-07-23 09:20 (UTC)

Dependencies (16)

Required by (0)

Sources (3)

Latest Comments

patatahooligan commented on 2020-09-23 16:13 (UTC) (edited on 2020-09-23 16:18 (UTC) by patatahooligan)

There's a bigger issue than just convenience when removing system users. The id of a user should not be reused because if there are leftover files owned by the old user, they will now be owned by the one that replaces it. So you actually want to keep system users indefinitely for security reasons!

EDIT: I misread the post_remove script as deleting the user, when instead it deletes the group. I think the same issue applies if files are created with the group set as mock.

anatolik commented on 2020-09-15 20:19 (UTC)

IMHO it makes sense not to remove mock group in post_remove(). Otherwise it makes harder to re-install this package

post_remove() {
  getent group mock >/dev/null && groupdel mock
  echo 'Make sure to empty out /var/lib/mock and /var/cache/mock'

larchunix commented on 2020-05-23 18:10 (UTC)


It would be great if the package installed a default config file.

Which config should be used as default? Fedora? CentOS? ...? IMHO, none of them make sense as default on Arch Linux systems.

anatolik commented on 2020-05-22 04:39 (UTC) (edited on 2020-05-22 04:39 (UTC) by anatolik)

I installed the package and at the first run it says:

$ mock
ERROR: Could not find required config file: /etc/mock/default.cfg
ERROR:   Did you forget to specify the chroot to use with '-r'?
ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg

It would be great if the package installed a default config file.

larchunix commented on 2017-11-17 19:05 (UTC)

@pnorcks: should be OK now, thanks for the report

pnorcks commented on 2017-11-17 14:15 (UTC)

When trying to use mock 1.4.7-1, I run into an exception: Traceback (most recent call last): File "/usr/bin/mock", line 79, in <module> from mockbuild import util File "/usr/lib/python3.6/site-packages/mockbuild/", line 41, in <module> from pyroute2 import IPRoute ModuleNotFoundError: No module named 'pyroute2'

pnorcks commented on 2016-03-14 04:00 (UTC)

@Duologic: I'm not sure what you mean by "collaborate". Can you clarify? I really prefer to run mock with 'sudo', both for reason I mentioned in my previous comment, and also because it makes clear that I'm running the program as root. Running mock with 'usermode' blurs that distinction...

Duologic commented on 2016-03-13 14:25 (UTC)

Can you collaborate on getting it running in 'usermode'?

pnorcks commented on 2015-06-04 22:46 (UTC)

I adopted the package. Note that I removed the 'usermode' dependency from this package, since I prefer running mock with 'sudo', and it simplifies packaging.

pnorcks commented on 2015-02-05 20:35 (UTC)

@roheim: Thanks! I'm now seeing an install failure. Error output is below. error: failed to commit transaction (conflicting files) mock: /usr/sbin exists in filesystem mock: /usr/sbin/mock exists in filesystem Errors occurred, no packages were upgraded.

roheim commented on 2015-02-05 18:01 (UTC)

@pnorcks: done. Also upgraded to newest version.

pnorcks commented on 2015-01-28 06:39 (UTC)

I recommend passing '--sysconfdir=/etc' to ./configure so that the mock's many configuration files will live under /etc/ instead of /usr/etc.

roheim commented on 2014-08-28 21:46 (UTC)

This package is currently broken, but will be fixed.

Peter_Littmann commented on 2014-01-16 10:04 (UTC)

I suggest to use mock-git which I just uploaded and let this package rest in peace.

nekolyanich commented on 2012-04-03 12:15 (UTC)

Hi, then i run mock, it display error dialog with unknown error(o_O). And completely do nothing. what i doing wrong?

execat commented on 2012-03-04 03:40 (UTC)

cd ${mygitname} git pull origin should be: cd ${mygitname} git pull origin -u master (or any other branch name)