[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] [bug #34654] [REGRESSION] update-po rule broken
From: |
Sandro Santilli |
Subject: |
[Gnash-commit] [bug #34654] [REGRESSION] update-po rule broken |
Date: |
Wed, 26 Oct 2011 07:04:25 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 |
Follow-up Comment #4, bug #34654 (project gnash):
This is what I get by reverting your commit:
src$ git status
# On branch po
nothing to commit (working directory clean)
src$ cd ../build/po
build/po$ make update-po
.....
build/po$ cd ../src
src$ git status
# On branch po
# Changed but not updated:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: po/cs.po
# modified: po/de.po
# modified: po/es.po
# modified: po/fi.po
# modified: po/fr.po
# modified: po/gnash.pot
# modified: po/it.po
# modified: po/ja.po
#
no changes added to commit (use "git add" and/or "git commit -a")
So, it did work for me pretty well.
I suggest you revert the Makefile.am and file a ticket for the problem you
were having. Filing a ticket before fixing a bug is also a way to leave a
trace of what's going on, allowing more organized discussion about it and
keeping changes aimed at different things isolated each-other. The ticket
would be referenced by the commit message.
PS: I've tried running autogen.sh but didn't work:
Merging cs.po...
/usr/bin/msgmerge: error while opening "/usr/src/gnash/gnash-head/gnash.pot"
for reading: No such file or directory
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34654>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/