locations.conf settings ignored for lightweight checkouts

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodney Dawes wrote:
> Public bug reported:
>
> Recently, a bug was fixed in tarmac, causing all the checkouts that
> tarmac does to be lightweight checkouts. I am running tarmac under cron,
> to land branches for several projects. Due to this, I have to disable
> gpg signing of commits in the directory where my tarmac is checking out
> branches. I have this configured in my locations.conf, while defaulting
> to create_signatures = always in bazaar.conf. Unfortunately, it seems
> that lightweight checkouts are ignoring the settings from
> locations.conf, and bzr fails to sign the commits, simply exiting.
>
> Using lightweight checkouts should also obey the settings in
> locations.conf as any other rich checkout would.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>

I would expect it to use the setting that matches the branch it is a
checkout from, not the setting for the local working tree. Is it not
even respecting that?

 status: incomplete
 importance: low

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxbK5EACgkQJdeBCYSNAAPuwACeI3BvxSuf1nBQKHwj8ML8sX2T
C20An3/hZRyqyflSVlHRFoAicCXX9T7f
=fk1T
-----END PGP SIGNATURE-----

On Thu, 2010-08-05 at 21:22 +0000, John A Meinel wrote:
> I would expect it to use the setting that matches the branch it is a
> checkout from, not the setting for the local working tree. Is it not
> even respecting that?

How does that work if the branch it is a checkout of, is remote?
Can you even configure such settings for remote branches?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodney Dawes wrote:
> On Thu, 2010-08-05 at 21:22 +0000, John A Meinel wrote:
>> I would expect it to use the setting that matches the branch it is a
>> checkout from, not the setting for the local working tree. Is it not
>> even respecting that?
>
> How does that work if the branch it is a checkout of, is remote?
> Can you even configure such settings for remote branches?
>

[bzr+ssh://bazaar.launchpad.net/~jameinel/bzr]
public_location = http://bazaar.launchpad.net/~jameinel/bzr
public_location:policy = appendpath

Whatever the url you open the branch at locally, can be configured in
locations.conf. It is explicitly there so that you can override remote
settings (that you can't change), with local ones.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxcUfkACgkQJdeBCYSNAAN8/wCfW0EdBxUTwFUFxJ1DCBsReMte
DdcAniyjAEbQpaew/eOyKMWUoVTn9lQu
=odcG
-----END PGP SIGNATURE-----

On Fri, 2010-08-06 at 18:18 +0000, John A Meinel wrote:
> [bzr+ssh://bazaar.launchpad.net/~jameinel/bzr]
> public_location = http://bazaar.launchpad.net/~jameinel/bzr
> public_location:policy = appendpath
>
> Whatever the url you open the branch at locally, can be configured in
> locations.conf. It is explicitly there so that you can override remote
> settings (that you can't change), with local ones.

So, I'd rather not do this, because i have a lot of working trees, all
being created under the same subdir (/var/cache/tarmac). It would be
much more efficient to have a blanket config setting for them, like I
can do for regular checkouts, by specifying the path which the checkout
resides under on the local file system.

locations.conf is only consulted for locations of branches. See also bug 276201.

[Expired for Bazaar because there has been no activity for 60 days.]