Integrated permissions/ownership reset on file operations for etckeeper/bzr

Bug #322339 reported by Thierry Carrez on 2009-01-28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bzr (Ubuntu)
etckeeper (Ubuntu)

Bug Description

Binary package hint: etckeeper

Since the VCS doesn't handle full permissions/ownership information, etckeeper keeps track of the differences in permissions/ownership in a .etckeeper file.

When the repository is restored to a previous revision (or any other VCS operation that cause a file to be modified), its permissions/ownership properties must be manually synced, since the VCS is not aware of them.

To make etckeeper more user-friendly, it would be nice to integrate the ownership/permissions changes into the file operations. This may be done at the bzr etckeeper plugin level, using a hook that would reset the permissions/ownership for each file by looking into the corresponding .etckeeper state.

Thierry Carrez (ttx) on 2009-01-28
Changed in etckeeper:
importance: Undecided → Wishlist
Thierry Carrez (ttx) on 2009-03-19
Changed in etckeeper:
status: New → Confirmed
Thierry Carrez (ttx) on 2009-06-10
Changed in bzr (Ubuntu):
importance: Undecided → Wishlist
Robert Collins (lifeless) wrote :

We need some more details about what bzr changes are needed to move this bug along.

Changed in bzr:
status: New → Incomplete
Daniel Hahler (blueyed) on 2010-03-10
Changed in etckeeper (Ubuntu):
status: Confirmed → Triaged
Jelmer Vernooij (jelmer) on 2011-01-20
Changed in bzr (Ubuntu):
status: New → Confirmed
Jelmer Vernooij (jelmer) on 2011-02-04
tags: added: hooks
Mark A. Hershberger (hexmode) wrote :

I don't know what is needed, but this just bit me in the butt. Luckily the file was there so I could see *when* the permissions changed, but it would be better if this actually took care of rolling them back, as well.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers