[git-buildpackage] RFC: new option --git-preexport

[Andrea Zagli]

Il giorno dom 22 gen 2017 17:29:49 CET, Guido Günther ha scritto:

> On Sun, Jan 22, 2017 at 09:14:05AM +0000, Andrea Zagli wrote:
>> Il giorno dom 15 gen 2017 12:41:35 CET, Guido Günther ha scritto:
>> > [...]
>>
>>
>> i prepared the patch [1] (it isn't complete) for preexport new option
>>
>> it seems to work, but not as i would like
>>
>> as i saw i want to use the option to execute "rm -rf <build-dir>" before
>> package build start, because if i don't clean build dir i get some errors
>>
>>
>> ...
>> dpkg-source: info: using source format '3.0 (quilt)'
>> dpkg-source: info: building libreptool using existing
>> ./libreptool_0.5.0.orig.tar.gz
>> dpkg-source: warning: newly created empty file
>> 'build/sid/libreptool-0.5.0/NEWS' will not be represented in diff
>> dpkg-source: warning: newly created empty file
>> 'build/sid/libreptool-0.5.0/README' will not be represented in diff
>> dpkg-source: warning: executable mode 0755 of
>> 'build/sid/libreptool-0.5.0/autogen.sh' will not be represented in diff
>> dpkg-source: warning: executable mode 0755 of
>> 'build/sid/libreptool-0.5.0/debian/rules' will not be represented in diff
>> dpkg-source: warning: newly created empty file
>> 'build/sid/libreptool-0.5.0/docs/reference/libreptool-overrides.txt' will
>> not be represented in diff
>> dpkg-source: error: cannot represent change to
>> build/sid/libreptool-0.5.0/tests/db_test.db: binary file contents changed
>> dpkg-source: error: add build/sid/libreptool-0.5.0/tests/db_test.db in
>> debian/source/include-binaries if you want to store the modified binary in
>> the debian tarball
>> dpkg-source: error: cannot represent change to
>> build/sid/libreptool-0.5.0/tests/gnome-globe.png: binary file contents
>> changed
>> dpkg-source: error: add build/sid/libreptool-0.5.0/tests/gnome-globe.png in
>> debian/source/include-binaries if you want to store the modified binary in
>> the debian tarball
>> dpkg-source: error: cannot represent change to
>> build/sid/libreptool-0.5.0/tests/rodents.png: binary file contents changed
>> dpkg-source: error: add build/sid/libreptool-0.5.0/tests/rodents.png in
>> debian/source/include-binaries if you want to store the modified binary in
>> the debian tarball
>> dpkg-source: error: cannot represent change to
>> build/sid/libreptool_0.5.0-1~1.gbp8b8371.debian.tar.xz: binary file contents
>> changed
>> dpkg-source: error: add
>> build/sid/libreptool_0.5.0-1~1.gbp8b8371.debian.tar.xz in
>> debian/source/include-binaries if you want to store the modified binary in
>> the debian tarball
>> dpkg-source: error: cannot represent change to
>> build/sid/libreptool_0.5.0.orig.tar.gz: binary file contents changed
>> dpkg-source: error: add build/sid/libreptool_0.5.0.orig.tar.gz in
>> debian/source/include-binaries if you want to store the modified binary in
>> the debian tarball
>> dpkg-source: error: unrepresentable changes to source
>> ...
>>
>>
>> if i clean build dir by hand it works; but if i use the new option i got the
>> same errors, and i'm sure that the command was executed in the right way
>>
>> preexport is setted as "rm -rf $GBP_EXPORT_DIR/* && ls -l $GBP_EXPORT_DIR >
>> $GBP_EXPORT_DIR/pippo"
>>
>> someone can help me?
>
> Try
>
>     gbp buildpackage --git-verbose ....
>
> and you see in what order which command is executed (and we do too!).


the issue is present only if i create export dir inside the git repository

and (i think) the "problem" is that gbp executes this command

gbp:debug: ['git', 'add', '-f',  
'/home/andreaz/Documenti/sviluppo/debian_packages/libreptool']

so the command adds also export dir that i excluded from git  
repository in .gitignore


why does gbp use -f?


the good news is that the new option seems to work ;-)