-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mockchain still creates a root-owned resultdir #1490
Comments
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 30, 2024
In the real one now, also for the --chain method which is changing the buildroot.resultdir for every single package. Previously, chroot_scan/ was (re)created for every --chain package in the basedir: /var/lib/mock/fedora-41-x86_64/result/chroot_scan Now, chroot_scan/ files are written into a package-specific resultdir, for example: /var/tmp/mock-chain-root-28259-ie_33sdi/results/default/copr-cli-2.0-1.git.15.526473b.fc41/chroot_scan /var/tmp/mock-chain-root-28259-ie_33sdi/results/default/python-copr-2.0-1.git.20.526473b.fc41/chroot_scan This in turn fixes a --chain build, because it - together with the `chroo_scan` directory it created also `chroot_scan/..` directory, mistakenly root-owned. Fixes: rpm-software-management#1490
The problem was that the plugin's resultdir was crated globally in /var/lib/mock//result, not in the per-package resultdir like /var/tmp/mock-chain-root-23693-8id_zl19/results/. |
nikromen
pushed a commit
that referenced
this issue
Dec 2, 2024
In the real one now, also for the --chain method which is changing the buildroot.resultdir for every single package. Previously, chroot_scan/ was (re)created for every --chain package in the basedir: /var/lib/mock/fedora-41-x86_64/result/chroot_scan Now, chroot_scan/ files are written into a package-specific resultdir, for example: /var/tmp/mock-chain-root-28259-ie_33sdi/results/default/copr-cli-2.0-1.git.15.526473b.fc41/chroot_scan /var/tmp/mock-chain-root-28259-ie_33sdi/results/default/python-copr-2.0-1.git.20.526473b.fc41/chroot_scan This in turn fixes a --chain build, because it - together with the `chroo_scan` directory it created also `chroot_scan/..` directory, mistakenly root-owned. Fixes: #1490
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Two subsequent runs of mockchain cause this traceback:
Caused by root ownership:
The text was updated successfully, but these errors were encountered: