I have trouble properly building console-setup packages. KiBi had recently to "clean out" the package because previous uploads (made by me) were containing cruft. It appears that my use of git-buildpackage and cowbuilder ends up in a process were several files are generated during the build and then included in the uploaded orig.tar.gz file I just tried to build without gbp and just my usual "build-sid" script: pdebuild --pbuilder cowbuilder -- --basepath /var/cache/pbuilder/base-sid.cow --distribution sid It ends up with less cruft but, still: bubulle@kheops:~/build/results/console-setup_1.117 $ debdiff console-setup_1.116.dsc console-setup_1.117.dsc|diffstat gpgv: Signature faite le mar. 25 nov. 2014 18:00:20 CET avec la clef RSA d'identifiant C2B35520 gpgv: Impossible de vérifier la signature : clef publique introuvable dpkg-source: avertissement: impossible de vérifier la signature sur /var/cache/pbuilder/build/results/console-setup_1.117/console-setup_1.116.dsc dpkg-source: avertissement: extraction d'un paquet source non signé (/var/cache/pbuilder/build/results/console-setup_1.117/console-setup_1.117.dsc) Fonts/soft.Makefile | 2 - Keyboard/ckb/symbols/compose | 38 ++++++++++++++++++++++++++++++++ debian/changelog | 7 +++++ debian/console-setup-udeb.templates | 2 - debian/keyboard-configuration.templates | 2 - debian/po/zh_CN.po | 2 - 6 files changed, 49 insertions(+), 4 deletions(-) The last 4 files changed are OK....They're documented in the changelog. However, the first two files changed...I really have no idea where thigns come from, as, in the git repo from which I built: # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: debian/changelog # no changes added to commit (use "git add" and/or "git commit -a") ...the only change is the result of "dch -r" So, indeed, I'm reluctant to upload c-s as I built it.....because I feel it would again bring cruft in the debdiff file..... But, as a consequence, I have no idea how to proceed......the build of this package is indeed a big mystery for me (and a damn long build, by the way). --
Attachment:
signature.asc
Description: Digital signature