> >I think Cesar has fixed almost all lintian warnings except the "too >much arch independent data" warning, including the "keyword" keyword >funny issue mentioned by Gianfranco. However, I see mainly 2 problems. >First, if I try to build using debuild, I get the error >`dh_autoreconf: autoreconf -f -i returned exit code 1'. I think it is >because dh_autoreconf is running "naked" `autoreconf' instead of >`autogen.sh'. So I think the fix is to add the following entry into >debian/rule: > >override dh_autoreconf: > dh_autoreconf ./autogen.sh > >Besides, if I try to re-build I get `dpkg-source: error: >unrepresentable changes to source'. Now I don't really know how to fix >since I don't know how translation works. Maybe Gianfranco could help?
I see some *.gmo files created and not deleted during clean, this should be fixed upstream or with a simple find po -name "*.gmo" -delete in the dh_clean target the other problem is that the timestamp of the po files gets updated during the build and this makes the source content change. I'm not sure which is the "correct" fix, but I presume the po files should be updated "prior" to release the tarball, and not during the debian build (where the po should just be compiled) --- eviacam-2.0.3.orig/po/ar.po +++ eviacam-2.0.3/po/ar.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: viacam 1.3.1\n" "Report-Msgid-Bugs-To: ce...@crea-si.com\n" -"POT-Creation-Date: 2015-09-24 15:52+0200\n" +"POT-Creation-Date: 2015-10-10 11:12+0200\n" "PO-Revision-Date: \n" "Last-Translator: Hatim Alahmadi <dr.ha...@hotmail.com>\n" "Language-Team: Hatim Alahmadi <dr.ha...@hotmail.com>\n" @@ -590,7 +590,7 @@ msgstr "" "ﻪﻟ ﺕﺮﻳﺩ ﺍﻼﺴﺘﻣﺭﺍﺭ؟" #: src/wconfiguration.cpp:1747 src/wconfiguration.cpp:1882 -#: src/wconfiguration.cpp:2008 src/viacamcontroller.cpp:383 +#: src/wconfiguration.cpp:2008 src/viacamcontroller.cpp:385 #: src/cmotioncalibration.cpp:186 msgid "eViacam warning" msgstr "ﺖﺣﺬﻳﺭ ﻢﻧ ﻒﻳﺍ ﻙﺎﻣ" and please change cd po; make update-po; cd .. to "$(MAKE) -C po update-po" but I'm pretty sure this is already done automatically. So I would even drop the override_dh_auto_build target and also the "po/stamp-po" should be cleaned during clean, and this seems to be an upstream issue too. cheers, G.