Bug 785614 - etckeeper init should really run git config --add receive.denyCurrentBranch ignore
Summary: etckeeper init should really run git config --add receive.denyCurrentBranch i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: etckeeper
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 00:36 UTC by Paul Wouters
Modified: 2012-02-08 20:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 20:49:52 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 659160 0 None None None Never

Description Paul Wouters 2012-01-30 00:36:54 UTC 
Description of problem:

you cannot git push a commit to a cloned etckeeper repository because git refuses to push to a checked out branch per default. Obviously, the master tree of /etc on the remote is checked out :)

This can be fixed by running:

 git config --add receive.denyCurrentBranch ignore 

in the "etckeeper init" command.
Comment 1 Thomas Moschny 2012-02-08 20:37:02 UTC 
Forwarding to upstream.
Comment 2 Thomas Moschny 2012-02-08 20:49:52 UTC 
Quoting upstream (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659160#10) :

Pushing into a checked out git repository is unsafe. /etc is the most
important thing on your system. This combination seems very unwise to
me, and certianly not a good default. 

Especially since many etckeeper users are probably not expert git users.
Those who think they know how to handle pushes into checked out branches
also know where the config is.
Note You need to log in before you can comment on or make changes to this bug.