The fink package installer can try to build and run the tests either as root or as a non-privileged user. So the testing does run as root under the package manager unless asked not to. It is preferred that the non-privileged user account "fink-bld" be used. I just tried manually running the tar command as the fink-bld user and all the extracted files have “fink-bld” as the user. As expected. This user can also delete the hierarchy as well in my testing.
sudo -u fink-bld rm -r dup_source/testfiles
So, it isn’t the test files extraction and deletion that requires root privilege (through the sudo command) but rather something else in the testing phase. I will try a full rebuild while running as "fink-bld” user but lots of file descriptors and try to isolate the failures to a particular test.
-Scott
On Feb 5, 2017, at 12:14 PM, Kenneth Loafman via Duplicity-talk < address@hidden> wrote:
The tests don't run as root, so not sure what you mean by "as root on linux". The -p option would cause tar to try and make the target owner the same as the original, not the test user, which I'm sure would break things. Lots of moving parts, and since some of them move relative to ownership of the file, and system platform, it would take a while to untangle. MacOS is different from Linux is different from BSD. Root has different defaults than a normal user.
I think a lot of this lies in the BSD'ness of the MacOS vs Linux.
...Ken
_______________________________________________ Duplicity-talk mailing list address@hiddenhttps://lists.nongnu.org/mailman/listinfo/duplicity-talk
|