I suppose /usr/src/savane on vcs isn't used for anything and
and should therefore just be deleted. (But I'm not willing to go that
far just now.)
I concur that /usr/src/savane isn't used. It is behind the HEAD of
that branch. It is just causing confusion.
I moved it out of the way.
On 10/07/2013 11:34 PM, Karl Berry wrote:
git fetch origin git diff origin
Thanks very much. Unfortunately, the results are disturbing.
The git fetch origin went without incident, ending with:
..
From git://127.0.0.1/savane-cleanup
91a0400..8ce63e8 master - origin/master
And I
Err.. I thought we were speaking about frontend rather than vcs :)
Whew!! I knew I was missing something obvious.
git fetch origin git diff origin comes up clean. I feel better.
I suppose /usr/src/savane on vcs isn't used for anything and
and should therefore just be deleted. (But I'm
On 10/05/2013 08:51 PM, Karl Berry wrote:
I wonder whether it is actually useful to push from root@frontend.
Yes, at least to me it is. Whenever I push from other places I end up
in some kind of git hell.
Beyond that, it is the only safe thing I've found to do. Like I asked
before, how
I wonder whether it is actually useful to push from root@frontend.
Yes, at least to me it is. Whenever I push from other places I end up
in some kind of git hell.
Beyond that, it is the only safe thing I've found to do. Like I asked
before, how you can tell what git pull will bring in?
k
Tomasz Konojacki wrote:
Additionally, I'm not sure why, but origin was set to
git://git.sv.gnu.org/administration/savane.git which doesn't seem to
be right,
That is the anonymous read-only access path. You can clone and read
using that URL but you can't write using it. You can make patches
Bob,
To log into vcs, first log into mgt.
He can't. He doesn't have a static IP address (as far as I know --
Tomasz, if I'm wrong, let me know). I asked him to ask sysadmin for an
account on fencepost but I don't think that has happened yet.
There is a firewall on all of the VMs
Karl Berry wrote:
To log into vcs, first log into mgt.
He can't. He doesn't have a static IP address (as far as I know --
Tomasz, if I'm wrong, let me know). I asked him to ask sysadmin for an
account on fencepost but I don't think that has happened yet.
But should be able to get to
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:
: RE: [Savannah-hackers-public] savane git cannot be committed
[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
Hi Tomasz,
As far as I understood things, Nico did not fix all the issues that were
reported to him. He fixed the XSS problems mentioned in his first
message, but not the exploits mentioned in his following messages, with
screenshots (which I couldn't understand how to make sense of, sorry to
So I did git commit on the not-checked-in files in frontend:/usr/src/savane
since nobody else has. Namely:
git commit -m'safe htmlify from Nico' frontend/php/account/register.php
git commit -m'registration wording' frontend/php/account/register.php
git commit -m'do not specify nonfree (or any)
Date: Tue, 1 Oct 2013 16:50:33 +
From: k...@freefriends.org
To: savannah-hackers-public@gnu.org
Subject: [Savannah-hackers-public] savane git cannot be committed
So I did git commit on the not-checked-in files in frontend:/usr/src/savane
since nobody else has. Namely:
git commit -m'safe
[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
14 matches
Mail list logo
