[Bug 781813] New: Can't push simple-scan branches due pre-receive hook

["sysadmin" (GNOME Bugzilla) <bugzilla gnome org>]

Bug ID	781813
Summary	Can't push simple-scan branches due pre-receive hook
Classification	Infrastructure
Product	sysadmin
Version	unspecified
OS	Linux
Status	NEW
Severity	normal
Priority	Normal
Component	Git
Assignee	sysadmin-maint@gnome.bugs
Reporter	robert.ancell@gmail.com
QA Contact	sysadmin-maint@gnome.bugs
GNOME version	---

I imported simple-scan into git from bzr. However I didn't import the branches.
If I try and push them now I get:

 git push
Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 865 bytes | 0 bytes/s, done.
Total 8 (delta 6), reused 0 (delta 0)
remote: ---
remote: The following translation (.po) file appears to be invalid. (When
updating branch 'gnome-3-24'.)
remote: 
remote: help/ar/ar.po
remote: 
remote: The results of the validation follow. Please correct the errors on the
line numbers mentioned and try to push again.
remote: 
remote: <stdin>:1:2: syntax error
remote: <stdin>:1: keyword "ar" unknown
remote: msgfmt: (null): warning: PO file header missing or invalid
remote:                 warning: charset conversion will not work
remote: msgfmt: found 3 fatal errors
remote: 
remote: To check this locally before attempting to push again, you can use the
following command:
remote: 
remote: msgfmt -c ar.po
remote: 
remote: After making fixes, modify your commit to include them, by doing:
remote: 
remote: git add ar.po
remote: git commit --amend
remote: 
remote: If you have any further problems or questions, please contact the GNOME
Translation Project mailing list <gnome-i18n@gnome.org>. Thank you.
remote: ---
To ssh://git.gnome.org/git/simple-scan
 ! [remote rejected] gnome-3-24 -> gnome-3-24 (pre-receive hook declined)
error: failed to push some refs to
'ssh://rancell@git.gnome.org/git/simple-scan'

I think I need to get back to import mode to push these?

---

      You are receiving this mail because:

• You are watching the QA Contact of the bug.
• You are watching the assignee of the bug.