[Systems] Fwd: Pootle commit error

[Gonzalo Odiard]

On Fri, Dec 24, 2010 at 7:15 AM, Aleksey Lim <alsroot at member.fsf.org> wrote:

> On Thu, Dec 23, 2010 at 09:29:49AM -0300, Gonzalo Odiard wrote:
> > Hi
> > Pootle can't commit in git.
> > Previously showed a error about the ssh key of the git server.
> > Bernie solved it (read mail below)
> > Now does not show any error, but wait and finally timeout.
> > I can't see the logs in the server.
> > Please, can you test doing commit in any pending translation?
> > Thanks
> >
> > Gonzalo
>
> Is it for specific projects?
> I see pottle commits eg
>
> http://git.sugarlabs.org/imageviewer/mainline/commit/9ddbbcfd8fa4728825bb8a9ffd6a3da5b417a8ff
> and there are bunch of sessions (accepted) from pottle in logs.
>
> Hmm, you are right.
I am trying to commit the Spanish translations of the 0.84 branch.
The connection with the Pootle page timeout, and if you reload the general
view page, don't see changes, but reloading a few minutes later see the
commit was done and the following error:

Failed to commit file: [GIT] push of
('/var/lib/pootle/checkouts/fructose84/read-activity', 'po/es.po')

failed: warning: You did not specify any refspecs to push, and the current
remote warning: has not configured any push refspecs.

The default action in this warning: case is to push all matching refspecs,
that is, all branches warning: that exist both locally and remotely will be
updated.

This may warning: not necessarily be what you want to happen.

warning: You can specify what action you want to take in this case, and

warning: avoid seeing this message again, by configuring 'push.default' to:

warning: 'nothing' : Do not push anything warning: 'matching' : Push all
matching branches (default)

warning: 'tracking' : Push the current branch to whatever it is tracking
warning: 'current' : Push the current branch Counting objects: 7, done.

Delta compression using up to 4 threads.

Compressing objects: 25% (1/4)

Compressing objects: 50% (2/4)

Compressing objects: 75% (3/4)

Compressing objects: 100% (4/4)

Compressing objects: 100% (4/4), done.

Writing objects: 25% (1/4)

Writing objects: 50% (2/4)

Writing objects: 75% (3/4)

Writing objects: 100% (4/4)

Writing objects: 100% (4/4), 640 bytes, done.

Total 4 (delta 3), reused 0 (delta 0)

This method is deprecated and will be removed on the next release. Use
'publish' instead => Syncing Gitorious... [OK]

To gitorious at git.sugarlabs.org:read/mainline.git 5bca106..649263c
sucrose-0.84 -> sucrose-0.84 ! [rejected] master -> master (non-fast
forward) error: failed to push some refs to 'gitorious at git.sugarlabs.org:
read/mainline.git'

It appears to be a Pootle misconfiguration.
Anybody know what to do?

Gonzalo



> >
> >
> > ---------- Forwarded message ----------
> > From: Bernie Innocenti <bernie at codewiz.org>
> > Date: Wed, Dec 22, 2010 at 6:12 PM
> > Subject: Re: Pootle commit error
> > To: Gonzalo Odiard <gonzalo at laptop.org>
> > Cc: Aleksey Lim <alsroot at member.fsf.org>, Simon Schampijer <
> > simon at schampijer.de>, Thangamani Arun <thangam.arunx at gmail.com>, Sugar
> Labs
> > Systems <systems at lists.sugarlabs.org>
> >
> >
> > On Wed, 2010-12-22 at 09:31 -0300, Gonzalo Odiard wrote:
> > > This error appear in Pootle:
> >
> > To report problems with pootle.sugarlabs.org, please contact the current
> > maintainer:
> >
> >  தங்கமணி அருண் (Thangamani Arun) <thangam.arunx at gmail.com>
> >
> > (and cc systems at lists.sugarlabs.org)
> >
> >
> > I fixed the issue reported below and also changed the system-level ssh
> > configuration to avoid hashing the hosts, because it makes this sort of
> > thing harder to diagnose.
> >
> >
> > > Failed to commit file: [GIT] pull failed (['git', '--git-dir',
> > > '/var/lib/pootle/checkouts/fructose84/imageviewer-activity/.git',
> > > 'pull']):
> > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
> > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > >
> > > The RSA host key for git.sugarlabs.org has changed, and the key for
> > > the corresponding IP address 18.85.44.120 is unknown.
> > >
> > > This could either mean that DNS SPOOFING is happening or the IP
> > > address for the host and its host key have changed at the same time.
> > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be
> > > eavesdropping on you right now (man-in-the-middle attack)!
> > > It is also possible that the RSA host key has just been changed.
> > >
> > > The fingerprint for the RSA key sent by the remote host is
> > > 4f:5e:5c:7f:ca:94:49:9d:2e:77:85:86:7c:de:56:f1.
> > > Please contact your system administrator. Add correct host key
> > > in /var/lib/pootle/.ssh/known_hosts to get rid of this message.
> > >
> > > Offending key in /var/lib/pootle/.ssh/known_hosts:1 RSA host key for
> > > git.sugarlabs.org has changed and you have requested strict checking.
> > > Host key verification failed. fatal: The remote end hung up
> > > unexpectedly
> > >
> > > I think we only need change the line with the key of git.sugarlabs.org
> > > in /var/lib/pootle/.ssh/known_hosts, but I don't have access to this
> > > server
> > > Thanks
> >
> > --
> >   // Bernie Innocenti - http://codewiz.org/
> >  \X/  Sugar Labs       - http://sugarlabs.org/
>
> > _______________________________________________
> > Systems mailing list
> > Systems at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/systems
>
>
> --
> Aleksey
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/private/systems/attachments/20101224/6a9c5c70/attachment.html>