> Another option would be to say we always attempt to chown the .bazaar (and
> .bzr.log) to be the same
> as the containing directory.
Until parthm nudged me enough to reveal that chown isn't working for the
average user, I had always thought
*any* user can freely use chown as long as he had write access to the
containing directory.
I was wrong.
chown(2) unambiguously says:
Only a privileged process (Linux: one with the CAP_CHOWN capability)
may change the owner of a file. The owner of a file may change the
group of the file to any group of which that owner is a member. A
privileged process (Linux: with CAP_CHOWN) may change the group arbi‐
trarily.
--
~/.bazaar created owned by root (when run under sudo)
https://bugs.launchpad.net/bugs/376388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
