** Branch linked: lp:debian/sid/bzr
--
~/.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
This bug was fixed in the package bzr - 2.2.0-1
---
bzr (2.2.0-1) unstable; urgency=low
* New upstream release.
+ Adds support for setting timestamps to originating revisions.
Closes: #473450
+ Removes remaining string exception. Closes: #585193, LP: #586926
+ Add C
** Branch linked: lp:~parthm/bzr/376388-dot-bazaar-ownership-
regression-2.2
--
~/.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
** Changed in: bzr
Status: In Progress = Fix Released
--
~/.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
snip/
btw I think this may vary between unixes.
I did test with FreeBSD and OSX and got the same results, I
mentioned the explanation for Linux because that was the only one
I cared to find but I've seen some mentions about a sysctl
variable for them that control this precise aspect and
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
On 11 March 2010 00:18, Vincent Ladeuil v.ladeuil...@free.fr wrote:
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
** Changed in: etckeeper (Ubuntu)
Status: Confirmed = In Progress
** Changed in: etckeeper (Ubuntu)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
~/.bazaar created owned by root (when run under sudo)
https://bugs.launchpad.net/bugs/376388
You received this bug notification
** Changed in: bzr (Ubuntu)
Importance: Undecided = Low
--
~/.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
This bug was fixed in the package etckeeper - 0.41ubuntu3
---
etckeeper (0.41ubuntu3) lucid; urgency=low
* etckeeper: Set HOME=~root if VCS=bzr, so that bzr doesn't create root-owned
.bazaar and .bzr.log in home directories when run under sudo (LP: #376388)
-- Thierry Carrez
** Branch linked: lp:ubuntu/etckeeper
--
~/.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
How about just adding HOME=/root (or something slightly more dynamic) to
our etckeeper.conf ? it's sourced everywhere and should ensure bzr is
always called with the right env ?
That doesn't solve the case where people run sudo bzr diff or others,
but that can probably wait for the fix to land in
(I meant HOME=~root)
--
~/.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
On 19 February 2010 19:06, Thierry Carrez thierry.car...@ubuntu.com wrote:
How about just adding HOME=/root (or something slightly more dynamic) to
our etckeeper.conf ? it's sourced everywhere and should ensure bzr is
always called with the right env ?
That makes sense to me.
--
Martin
** Branch linked: lp:~parthm/bzr/376388-dot-bazaar-ownership
--
~/.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
** Branch unlinked: lp:~parthm/bzr/2.0_376388_dot_bazaar_ownership
--
~/.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
I think Parth's patch in
https://code.edge.launchpad.net/~parthm/bzr/2.0_376388_dot_bazaar_ownership/+merge/19593
is reasonable and useful for bzr in its own right (review welcome)
but probably also etckeeper should run bzr and other programs with HOME
set to ~root to avoid the problem
We won't make -H the default in sudo; it would break other use cases
which rely on having the original $HOME, and general backwards
compatibliity.
--
~/.bazaar created owned by root (when run under sudo)
https://bugs.launchpad.net/bugs/376388
You received this bug notification because you are a
That leaves two options:
1/ special-casing sudo in configuration file management in bzr
2/ workaround in etckeeper (override HOME in bzr calls in etckeeper ?
Pre-create $HOME/.bazaar and $HOME/.bzr.log correctly ?)
(2) is certainly simpler, however it will fail to catch the case where
the
Please note that this is not a problem with Git / when using Git with etckeeper:
Apparently Git does not create the .git dir automatically - which may also be
an option for Bazaar.
Apart from that, Git behaves the same:
$ sudo git config --global user.name Daniel Hahler
$ ls -l ~/.gitconfig
Thierry's comment in #1 is interesting:
This is caused by bzr not really supporting to be run under sudo. In
config.py:ensure_config_dir_exists it creates $HOME/.bazaar without
dropping rights to the $SUDO_USER. Unfortunately the same could be said
for all other config-writing functions. I'm
I plan to look into this issue.
I was thinking of going with the approach Martin suggested:
Another option would be to say we always attempt to chown
the .bazaar (and .bzr.log) to be the same as the containing
directory.
Any other thoughts/suggestions welcome.
** Changed in: bzr
** Branch linked: lp:~parthm/bzr/2.0_376388_dot_bazaar_ownership
--
~/.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
On 17 February 2010 00:48, Soren Hansen so...@ubuntu.com wrote:
Would using pwd.getpwuid(os.geteuid()).pw_dir rather than
os.environ['HOME'] cause more problems than it solves?
I think so.
The right place to solve this is imo under sudo, by using the set_home
config option or -H option. This
Would using pwd.getpwuid(os.geteuid()).pw_dir rather than
os.environ['HOME'] cause more problems than it solves?
--
~/.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
** Changed in: bzr (Ubuntu)
Status: New = Confirmed
** Also affects: bzr
Importance: Undecided
Status: New
** Changed in: bzr
Status: New = Triaged
** Changed in: bzr
Importance: Undecided = Low
** Changed in: bzr
Importance: Low = Medium
--
~/.bazaar created
26 matches
Mail list logo
