[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Another broken Git repository



Hi,

I checked out

   git clone git+ssh://git.debian.org/git/debian-science/packages/liblemon1.git

and did some small cosmetic changes (Vcs fields are broken and thus the
recently announced machine-readable gatherer stumbles upon it).  Then I
tried to push:

$ git push
Counting objects: 12, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 922 bytes, done.
Total 8 (delta 6), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error: 
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error: 
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To git+ssh://git.debian.org/git/debian-science/packages/liblemon1.git
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to 'git+ssh://git.debian.org/git/debian-science/packages/liblemon1.git'


As a Git beginner I think there are many powerful features in Git but
also many ways to end up with a broken repository.  That's a bit
frustrating, thought.  Any hint?

Kind regards

      Andreas.

-- 
http://fam-tille.de


Reply to: