[Pkg-giraffe-discuss] zarafa-webapp-files seems not completely translated in the UI

[Guido Günther]

Hi Carsten,
On Tue, Dec 01, 2015 at 07:17:41PM +0100, Carsten Schoenert wrote:
> Hello,
> 
> Am 30.11.2015 um 08:58 schrieb Guido Günther:
> > We're at least lacking a build-dep on gettext:
> > 
> >     https://github.com/tijuca/zarafa-webapp/pull/2
> > 
> > This is _not_ build-tested since the upstream branch seems broken at the
> > moment:
> > 
> >     ...
> >     dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/uk.js has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/zh_CN.js has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/zh_TW.js has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/client/zarafa/advancesearch/data/DateRangeFields.js has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/client/zarafa/core/data/ZarafaCustomEventDispatcher.js has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/version has no final newline (either original or modified version)
> >     dpkg-source: warning: file zarafa-webapp/version has no final newline (either original or modified version)
> >     dpkg-source: error: unrepresentable changes to source
> >     dpkg-buildpackage: error: dpkg-source -b zarafa-webapp gave error exit status 2
> > 
> > and there's no pristine-tar to create a md5 identical tarball. Could you
> > have a look?
> 
> I've changed the gbp.conf to enable a pristine-tar commit while
> git-buildpackage is running the import-orig task. For getting a
> pristine-tar branch for the current version 2.1.1 I've reset the current
> debian and upstream branch to be equal with the current version on
> Alioth and run a new import of the upstream sources with all the related
> local made patches.

In case of lacking pristine-tar entries you can always invoke
pristine-tar directly using

    pristine-tar ../tarball.orig.tar.gz upstream/<version>

so the history of the repo stays a bit more linear.

> 
> @Guido
> I cherry-picked your fix for debian/control.

Thanks!
 -- Guido