Re: [Savannah-hackers-public] savane git cannot be committed

[Joan Lledó]

Hi Karl,

I don't know your particular problem but attending to the message the origin is rejecting your push, probably due to a permission issue in the origin. For example, maybe one of the files you're trying to update has root-only writing permissions or such like.

Take a look at this url:
http://andrey.mikhalchuk.com/2013/03/02/git-remote-rejected-master-master-na-unpacker-error.html

2013/10/1 Karl Berry <address@hidden>

    [1] - http://stackoverflow.com/questions/7228715/git-failed-to-push-some-refs-although-i-have-done-git-pull

Thanks for the research.  That looks like the same problem, but sorry,
it's basically incomprehensible to me.  I have no idea what "branches"
they are talking about, or how to figure out what they are.

Also, I certainly don't want to blindly do "git pull" on the live
checkout since I have no idea what will change.  How can that be
determined (as in, git diff-aginst-what-will-be-pulled)?

Anyway, you or anyone can log in to frontend.sv.gnu.org (as root) and do
whatever needs to be done in /usr/src/savane to get the changes pushed.

If no one can figure out how to fix it, an alternative would be to stop
using git for this source.

karl

P.S. Tomasz, more importantly -- any chance of your working on the
XSS/SQL/etc. attacks?  Weren't you going to do that?