rpkg

#503 mock-config fails when there's unpushed changes on a dist-git repo
Closed: Insufficient data by onosek. Opened by deepshikhakhandelwal.

Closed: Insufficient data
Reopen Issue

Why should mock-config bothers about the clean/unclean repo. It should not fail when there are any changes exist locally.

Metadata Update from @onosek:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

Hi @deepshikhakhandelwal,

I tried to recreate your issue. I am not aware of such a behaviour you described.
There is an end-message when you operates (=builds) with brew/koji:

Could not execute build: /repo/fedpkg has uncommitted changes.  Use git status to see details

And this is I think reasonable because this operation is performed remotely.
But it is not applied for mock-config or mockbuild. Please, could you provide more information about what your concern is? Or give me an example of how did you met this behaviour? Until then I closed this issue.

I can't reproduce this with python3-rpkg-1.60-3.fc31 either...

$ cd /tmp/
$ fedpkg clone -a coreutils
$ cd coreutils
$ touch unpushed-change.txt
$ git add unpushed-change.txt
$ git commit -m "add an unpushed change"

With this setup, fedpkg mock-config works for me.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.