bzr status: does not recognise pure chmod changes

[Paul Sladen]

If some files have purely changed in their chmod permission status (for example, being embargoed before release), then bzr does not recognise a pure chmod permissions change as being something that can be committed.

Ideally bzr would notice the permission change, both in 'bzr status' and 'bzr commit'.

[John A Meinel (jameinel)]

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

On 9/29/2011 2:59 PM, Paul Sladen wrote:
> Public bug reported:
>
> If some files have purely changed in their chmod permission status
> (for example, being embargoed before release), then bzr does not
> recognise a pure chmod permissions change as being something that
> can be committed.
>
> Ideally bzr would notice the permission change, both in 'bzr
> status' and 'bzr commit'.
>
> ** Affects: bzr Importance: Undecided Status: New
>

I don't know what specific permission change you think bzr is supposed
to be watching.

$ bzr st
$ chmod a-x bzr
$ bzr st
modified:
  bzr*

I think the issue is that bzr *does not* track read-write permissions
at all. It is meant as a way to version code, so if you have access to
the *branch* you have access to the code. Doing 'bzr co' of the code
will give you regular 'rw' files.

Perhaps you want bzr to track the full rwx+ugo permissions. You may
want to look into 'etckeeper' which layers permission tracking on top
of bzr (using hooks).

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

iEYEARECAAYFAk6EjqgACgkQJdeBCYSNAAO18wCfT820uRlnxvmp1x44M/qGBDCb
q6wAoMPkju123KL0sOOkqjPRUqGxnilL
=m0fq
-----END PGP SIGNATURE-----

[Martin Pool (mbp)]

  duplicate 67589