[ 0s] on X86_64, no limit mem size [ 0s] Using BUILD_ROOT=/var/cache/build/root_1 [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] [ 0s] [ 0s] obspw02 started "build _service:git-buildpackage:git-buildpackage_0.9.9-tizen20180912.dsc" at Wed Feb 20 05:35:03 UTC 2019. [ 0s] [ 0s] Building git-buildpackage for project 'Tools:Devel' repository 'Ubuntu_18.04' arch 'x86_64' srcmd5 '203c673b9f4ae98816eb534eae47739e' [ 0s] [ 0s] processing recipe /var/cache/build/root_1/.build-srcdir/_service:git-buildpackage:git-buildpackage_0.9.9-tizen20180912.dsc ... [ 0s] running changelog2spec --target debian --file /var/cache/build/root_1/.build-srcdir/_service:git-buildpackage:git-buildpackage_0.9.9-tizen20180912.dsc [ 0s] don't know how to convert changelog to format 'debian' [ 0s] init_buildsystem --configdir /var/run/obs/worker/1/build/configs --cachedir /var/cache/build --clean --rpmlist /var/cache/build/root_1/.build.rpmlist /var/cache/build/root_1/.build-srcdir/_service:git-buildpackage:git-buildpackage_0.9.9-tizen20180912.dsc build rpmlint-Factory ... [ 0s] copying qemu [ 0s] /usr/bin/qemu-arm-binfmt /usr/bin/qemu-arm-static /usr/bin/qemu-arm64-binfmt /usr/bin/qemu-arm64-static /usr/sbin/qemu-binfmt-conf.sh [ 0s] [ 1s] cycle: libc6 -> libgcc1 [ 1s] breaking dependency libgcc1 -> libc6 [ 1s] [1/49] preinstalling libgcc1... [ 1s] [2/49] preinstalling libc6... [ 2s] [3/49] preinstalling debianutils... [ 2s] [4/49] preinstalling diffutils... [ 2s] [5/49] preinstalling libattr1... [ 2s] [6/49] preinstalling libbz2-1.0... [ 2s] [7/49] preinstalling libc-bin... [ 2s] [8/49] preinstalling libdbus-1-3... [ 2s] [9/49] preinstalling libdebconfclient0... [ 2s] [10/49] preinstalling libgmp10... [ 2s] [11/49] preinstalling liblzma5... [ 2s] [12/49] preinstalling libnih1... [ 2s] [13/49] preinstalling libpcre3... [ 2s] [14/49] preinstalling libsepol1... [ 2s] [15/49] preinstalling libsigsegv2... [ 2s] [16/49] preinstalling libtinfo5... [ 2s] [17/49] preinstalling libzstd1... [ 2s] [18/49] preinstalling login... [ 2s] [19/49] preinstalling zlib1g... [ 2s] [20/49] preinstalling libstdc++6... [ 2s] [21/49] preinstalling base-passwd... [ 2s] [22/49] preinstalling libacl1... [ 2s] [23/49] preinstalling libmpfr6... [ 2s] [24/49] preinstalling libncurses5... [ 2s] [25/49] preinstalling libselinux1... [ 2s] [26/49] preinstalling xz-utils... [ 2s] [27/49] preinstalling libnih-dbus1... [ 2s] [28/49] preinstalling findutils... [ 2s] [29/49] preinstalling passwd... [ 2s] [30/49] preinstalling sed... [ 2s] [31/49] preinstalling tar... [ 2s] [32/49] preinstalling coreutils... [ 2s] [33/49] preinstalling util-linux... [ 3s] [34/49] preinstalling dpkg... [ 3s] [35/49] preinstalling readline-common... [ 3s] [36/49] preinstalling gzip... [ 3s] [37/49] preinstalling perl-base... [ 3s] [38/49] preinstalling dash... [ 3s] [39/49] preinstalling grep... [ 3s] [40/49] preinstalling debconf... [ 3s] [41/49] preinstalling init-system-helpers... [ 3s] [42/49] preinstalling perl-modules-5.26... [ 3s] [43/49] preinstalling libreadline7... [ 3s] [44/49] preinstalling tzdata... [ 4s] [45/49] preinstalling libperl5.26... [ 4s] [46/49] preinstalling gawk... [ 4s] [47/49] preinstalling base-files... [ 4s] [48/49] preinstalling perl... [ 4s] [49/49] preinstalling bash... [ 4s] [ 4s] running gawk postinstall script [ 4s] running base-files preinstall script [ 4s] dpkg-maintscript-helper: error: couldn't identify the package [ 4s] running base-files postinstall script [ 4s] chown: invalid user: 'root:root' [ 4s] running base-passwd preinstall script [ 4s] running base-passwd postinstall script [ 4s] running passwd preinstall script [ 4s] dpkg-maintscript-helper: error: environment variable DPKG_MAINTSCRIPT_NAME is required [ 4s] running passwd postinstall script [ 4s] Shadow passwords are now on. [ 4s] dpkg-maintscript-helper: error: environment variable DPKG_MAINTSCRIPT_NAME is required [ 6s] reordering...cycle: libc6 -> libgcc1 [ 6s] breaking dependency libgcc1 -> libc6 [ 6s] cycle: debhelper -> dh-autoreconf [ 6s] breaking dependency debhelper -> dh-autoreconf [ 6s] cycle: dh-strip-nondeterminism -> debhelper [ 6s] breaking dependency debhelper -> dh-strip-nondeterminism [ 6s] done [ 6s] [1/316] installing autotools-dev-20180224.1 [ 7s] [2/316] installing bash-completion-1:2.8-1ubuntu1 [ 7s] find: '/etc/bash_completion.d/': No such file or directory [ 8s] [3/316] installing binutils-common-2.30-15ubuntu1 [ 8s] [4/316] installing fonts-dejavu-core-2.37-1 [ 9s] [5/316] installing fonts-lmodern-2.004.5-3 [ 10s] [6/316] installing gcc-7-base-7.3.0-16ubuntu3 [ 10s] [7/316] installing gcc-8-base-8-20180414-1ubuntu2 [ 10s] [8/316] installing highlight-common-3.41-1 [ 11s] [9/316] installing libaudit-common-1:2.8.2-1ubuntu1 [ 11s] [10/316] installing libavahi-common-data-0.7-3.1ubuntu1 [ 11s] [11/316] installing libbison-dev-2:3.0.4.dfsg-1build1 [ 11s] [12/316] installing libgs9-common-9.22~dfsg+1-0ubuntu1 [ 12s] [13/316] installing libmagic-mgc-1:5.32-2 [ 13s] [14/316] installing libpython2.7-minimal-2.7.15~rc1-1 [ 13s] [15/316] installing libsemanage-common-2.7-2build2 [ 13s] [16/316] installing libx11-data-2:1.6.4-3 [ 14s] [17/316] installing linux-libc-dev-4.15.0-20.21 [ 15s] [18/316] installing lsb-base-9.20170808ubuntu1 [ 15s] [19/316] installing lynx-common-2.8.9dev16-3 [ 15s] [20/316] installing mime-support-3.60ubuntu1 [ 16s] [21/316] installing ncurses-base-6.1-1ubuntu1 [ 16s] [22/316] installing sensible-utils-0.0.12 [ 16s] Processing triggers for mime-support (3.60ubuntu1) ... [ 16s] [23/316] installing vim-runtime-2:8.0.1453-1ubuntu1 [ 16s] Adding 'diversion of /usr/share/vim/vim80/doc/help.txt to /usr/share/vim/vim80/doc/help.txt.vim-tiny by vim-runtime' [ 16s] Adding 'diversion of /usr/share/vim/vim80/doc/tags to /usr/share/vim/vim80/doc/tags.vim-tiny by vim-runtime' [ 17s] [24/316] installing xdg-utils-1.1.2-1ubuntu2 [ 17s] [25/316] installing x11-common-1:7.7+19ubuntu7 [ 18s] update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults [ 18s] invoke-rc.d: could not determine current runlevel [ 18s] invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block. [ 18s] [26/316] installing libgcc1-1:8-20180414-1ubuntu2 [ 18s] dpkg: libgcc1:amd64: dependency problems, but configuring anyway as you requested: [ 18s] libgcc1:amd64 depends on libc6 (>= 2.14); however: [ 18s] Package libc6 is not installed. [ 18s] [27/316] installing libc6-2.27-3ubuntu1 [ 19s] [28/316] installing cpio-2.12+dfsg-6 [ 19s] update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto mode [ 19s] [29/316] installing debianutils-4.8.4 [ 19s] [30/316] installing diffutils-1:3.6-1 [ 20s] [31/316] installing gettext-base-0.19.8.1-6 [ 20s] [32/316] installing hostname-3.20 [ 20s] [33/316] installing libattr1-1:2.4.47-2build1 [ 20s] [34/316] installing libbsd0-0.8.7-1 [ 21s] [35/316] installing libbz2-1.0-1.0.6-8.1 [ 21s] [36/316] installing libc-bin-2.27-3ubuntu1 [ 21s] [37/316] installing libc-dev-bin-2.27-3ubuntu1 [ 22s] [38/316] installing libcap-ng0-0.7.7-3.1 [ 22s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 22s] [39/316] installing libcap2-1:2.25-1.2 [ 22s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 22s] [40/316] installing libcom-err2-1.44.1-1 [ 22s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 22s] [41/316] installing libdb5.3-5.3.28-13.1ubuntu1 [ 23s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 23s] [42/316] installing libdebconfclient0-0.213ubuntu1 [ 23s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 23s] [43/316] installing libexpat1-2.2.5-3 [ 23s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 23s] [44/316] installing libfakeroot-1.22-2ubuntu1 [ 23s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 23s] [45/316] installing libffi6-3.2.1-8 [ 23s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 24s] [46/316] installing libgdbm5-1.14.1-6 [ 24s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 24s] [47/316] installing libgmp10-2:6.1.2+dfsg-2 [ 24s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 24s] [48/316] installing libgpg-error0-1.27-6 [ 24s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 24s] [49/316] installing libgpm2-1.20.7-5 [ 24s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 25s] [50/316] installing libgraphite2-3-1.3.11-2 [ 25s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 25s] [51/316] installing libidn11-1.33-2.1ubuntu1 [ 25s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 25s] [52/316] installing libijs-0.35-0.35-13 [ 25s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 25s] [53/316] installing libjbig0-2.1-3.1build1 [ 25s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 25s] [54/316] installing libjbig2dec0-0.13-6 [ 25s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 26s] [55/316] installing libkeyutils1-1.5.9-9.2ubuntu2 [ 26s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 26s] [56/316] installing libkpathsea6-2017.20170613.44572-8build1 [ 26s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 26s] [57/316] installing libkrb5support0-1.16-2build1 [ 26s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 26s] [58/316] installing liblcms2-2-2.9-1 [ 26s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 27s] [59/316] installing liblz4-1-0.0~r131-2ubuntu3 [ 27s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 27s] [60/316] installing liblzma5-5.2.2-1.3 [ 27s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 27s] [61/316] installing libmpdec2-2.4.2-1ubuntu1 [ 27s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 27s] [62/316] installing libnettle6-3.4-1 [ 28s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 28s] [63/316] installing libnih1-1.0.3-6ubuntu2 [ 28s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 28s] [64/316] installing libnspr4-2:4.18-1ubuntu1 [ 28s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 28s] [65/316] installing libpcre3-2:8.39-9 [ 28s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 29s] [66/316] installing libpipeline1-1.5.0-1 [ 29s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 29s] [67/316] installing libpixman-1-0-0.34.0-2 [ 29s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 29s] [68/316] installing libpopt0-1.16-11 [ 29s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 29s] [69/316] installing libpotrace0-1.14-2 [ 30s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 30s] [70/316] installing libseccomp2-2.3.1-2.1ubuntu4 [ 30s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 30s] [71/316] installing libsepol1-2.7-1 [ 30s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 30s] [72/316] installing libsigsegv2-2.12-1 [ 30s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 30s] [73/316] installing libsmartcols1-2.31.1-0.4ubuntu3 [ 31s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 31s] [74/316] installing libsqlite3-0-3.22.0-1 [ 31s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 31s] [75/316] installing libtasn1-6-4.13-2 [ 31s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 31s] [76/316] installing libtexlua52-2017.20170613.44572-8build1 [ 31s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 32s] [77/316] installing libtinfo5-6.1-1ubuntu1 [ 32s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 32s] [78/316] installing libudev1-237-3ubuntu10 [ 32s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 32s] [79/316] installing libunistring2-0.9.9-0ubuntu1 [ 34s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 35s] [80/316] installing libuuid1-2.31.1-0.4ubuntu3 [ 35s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 35s] [81/316] installing libzstd1-1.3.3+dfsg-2ubuntu1 [ 35s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 35s] [82/316] installing make-4.1-9.1ubuntu1 [ 36s] [83/316] installing multiarch-support-2.27-3ubuntu1 [ 36s] [84/316] installing patch-2.7.6-2ubuntu1 [ 36s] [85/316] installing t1utils-1.41-2 [ 36s] [86/316] installing xxd-2:8.0.1453-1ubuntu1 [ 37s] [87/316] installing zlib1g-1:1.2.11.dfsg-0ubuntu2 [ 37s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 37s] [88/316] installing libatomic1-8-20180414-1ubuntu2 [ 37s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 37s] [89/316] installing libavahi-common3-0.7-3.1ubuntu1 [ 37s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 37s] [90/316] installing libgomp1-8-20180414-1ubuntu2 [ 37s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 37s] [91/316] installing libitm1-8-20180414-1ubuntu2 [ 38s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 38s] [92/316] installing libmpx2-8-20180414-1ubuntu2 [ 38s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 38s] [93/316] installing libquadmath0-8-20180414-1ubuntu2 [ 38s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 38s] [94/316] installing libtexluajit2-2017.20170613.44572-8build1 [ 38s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 39s] [95/316] installing libasan4-7.3.0-16ubuntu3 [ 39s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 39s] [96/316] installing liblsan0-8-20180414-1ubuntu2 [ 39s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 39s] [97/316] installing libstdc++6-8-20180414-1ubuntu2 [ 40s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 40s] [98/316] installing libtsan0-8-20180414-1ubuntu2 [ 40s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 40s] [99/316] installing vim-common-2:8.0.1453-1ubuntu1 [ 40s] Processing triggers for mime-support (3.60ubuntu1) ... [ 40s] [100/316] installing base-passwd-3.5.44 [ 41s] [101/316] installing bzip2-1.0.6-8.1 [ 41s] [102/316] installing fakeroot-1.22-2ubuntu1 [ 41s] update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode [ 41s] [103/316] installing libacl1-2.2.52-3build1 [ 41s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 41s] [104/316] installing libblkid1-2.31.1-0.4ubuntu3 [ 41s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 41s] [105/316] installing libelf1-0.170-0.4 [ 41s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 42s] [106/316] installing libgcrypt20-1.8.1-4ubuntu1 [ 42s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 42s] [107/316] installing libgdbm-compat4-1.14.1-6 [ 42s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 42s] [108/316] installing libidn2-0-2.0.4-1.1build2 [ 42s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 42s] [109/316] installing libisl19-0.19-1 [ 43s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 43s] [110/316] installing libjpeg-turbo8-1.5.2-0ubuntu5 [ 43s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 43s] [111/316] installing libk5crypto3-1.16-2build1 [ 43s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 43s] [112/316] installing liblua5.1-0-5.1.5-8.1build2 [ 44s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 44s] [113/316] installing liblua5.2-0-5.2.4-1.1build1 [ 44s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 44s] [114/316] installing libmpfr6-4.0.1-1 [ 44s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 44s] [115/316] installing libncurses5-6.1-1ubuntu1 [ 45s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 45s] [116/316] installing libncursesw5-6.1-1ubuntu1 [ 45s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 45s] [117/316] installing libp11-kit0-0.23.9-2 [ 45s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 45s] [118/316] installing libpng16-16-1.6.34-1 [ 45s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 46s] [119/316] installing libptexenc1-2017.20170613.44572-8build1 [ 46s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 46s] [120/316] installing libselinux1-2.7-2build2 [ 46s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 46s] [121/316] installing libsynctex1-2017.20170613.44572-8build1 [ 46s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 46s] [122/316] installing libunwind8-1.2.1-8 [ 46s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 47s] [123/316] installing libxau6-1:1.0.8-1 [ 47s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 47s] [124/316] installing libxdmcp6-1:1.1.2-3 [ 47s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 47s] [125/316] installing libzzip-0-13-0.13.62-3.1 [ 47s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 47s] [126/316] installing m4-1.4.18-1 [ 48s] [127/316] installing unzip-6.0-21ubuntu1 [ 48s] Processing triggers for mime-support (3.60ubuntu1) ... [ 48s] [128/316] installing xz-utils-5.2.2-1.3 [ 48s] update-alternatives: using /usr/bin/xz to provide /usr/bin/lzma (lzma) in auto mode [ 48s] [129/316] installing groff-base-1.22.3-10 [ 48s] Processing triggers for mime-support (3.60ubuntu1) ... [ 48s] [130/316] installing less-487-0.1 [ 49s] Processing triggers for mime-support (3.60ubuntu1) ... [ 49s] [131/316] installing libaudit1-1:2.8.2-1ubuntu1 [ 49s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 49s] [132/316] installing libbinutils-2.30-15ubuntu1 [ 49s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 49s] [133/316] installing libc6-dev-2.27-3ubuntu1 [ 50s] [134/316] installing libhogweed4-3.4-1 [ 50s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 50s] [135/316] installing libice6-2:1.0.9-2 [ 50s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 51s] [136/316] installing libicu60-60.2-3ubuntu3 [ 52s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 52s] [137/316] installing libmagic1-1:5.32-2 [ 52s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 53s] [138/316] installing libnss3-2:3.35-2ubuntu2 [ 53s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 53s] [139/316] installing libosp5-1.5.2-13ubuntu2 [ 53s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 53s] [140/316] installing libostyle1c2-1.4devel1-21.3 [ 54s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 54s] [141/316] installing python2.7-minimal-2.7.15~rc1-1 [ 55s] [142/316] installing libcc1-0-8-20180414-1ubuntu2 [ 55s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 55s] [143/316] installing libcilkrts5-7.3.0-16ubuntu3 [ 55s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 55s] [144/316] installing libubsan0-7.3.0-16ubuntu3 [ 55s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 55s] [145/316] installing autopoint-0.19.8.1-6 [ 56s] [146/316] installing libjpeg8-8c-2ubuntu8 [ 56s] [147/316] installing file-1:5.32-2 [ 56s] [148/316] installing findutils-4.6.0+git+20170828-2 [ 56s] [149/316] installing net-tools-1.60+git20161116.90da8a0-1ubuntu1 [ 57s] [150/316] installing sed-4.4-2 [ 57s] [151/316] installing strace-4.21-1ubuntu1 [ 57s] [152/316] installing bison-2:3.0.4.dfsg-1build1 [ 57s] update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc (yacc) in auto mode [ 57s] [153/316] installing libfdisk1-2.31.1-0.4ubuntu3 [ 58s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 58s] [154/316] installing libfreetype6-2.8.1-2ubuntu2 [ 58s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 58s] [155/316] installing libmount1-2.31.1-0.4ubuntu3 [ 58s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 58s] [156/316] installing libmpc3-1.1.0-1 [ 58s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 59s] [157/316] installing libxcb1-1.13-1 [ 59s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 59s] [158/316] installing psmisc-23.1-1 [ 59s] [159/316] installing tar-1.29b-2 [ 59s] update-alternatives: using /usr/sbin/rmt-tar to provide /usr/sbin/rmt (rmt) in auto mode [ 59s] Processing triggers for mime-support (3.60ubuntu1) ... [ 60s] [160/316] installing binutils-x86-64-linux-gnu-2.30-15ubuntu1 [ 60s] [161/316] installing coreutils-8.28-1ubuntu1 [ 60s] [162/316] installing libsm6-2:1.2.2-1 [ 61s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 61s] [163/316] installing libsystemd0-237-3ubuntu10 [ 61s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 61s] [164/316] installing libxml2-2.9.4+dfsg1-6.1ubuntu1 [ 61s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 61s] [165/316] installing highlight-3.41-1 [ 62s] [166/316] installing libdw1-0.170-0.4 [ 62s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 62s] [167/316] installing libkrb5-3-1.16-2build1 [ 62s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 62s] [168/316] installing libsemanage1-2.7-2build2 [ 62s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 63s] [169/316] installing libgnutls30-3.5.18-1ubuntu1 [ 63s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 63s] [170/316] installing librpmio8-4.14.1+dfsg1-2 [ 63s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 63s] [171/316] installing libgcc-7-dev-7.3.0-16ubuntu3 [ 64s] [172/316] installing bsdutils-1:2.31.1-0.4ubuntu3 [ 64s] [173/316] installing libdbus-1-3-1.12.2-1ubuntu1 [ 64s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 64s] [174/316] installing libprocps6-2:3.3.12-3ubuntu1 [ 64s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 65s] [175/316] installing libxcb-render0-1.13-1 [ 65s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 65s] [176/316] installing libxcb-shm0-1.13-1 [ 65s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 65s] [177/316] installing libx11-6-2:1.6.4-3 [ 65s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 66s] [178/316] installing libxslt1.1-1.1.29-5 [ 66s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 66s] [179/316] installing libstdc++-7-dev-7.3.0-16ubuntu3 [ 66s] [180/316] installing binutils-2.30-15ubuntu1 [ 67s] [181/316] installing libgssapi-krb5-2-1.16-2build1 [ 67s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 67s] [182/316] installing libtiff5-4.0.9-5 [ 67s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 67s] [183/316] installing fdisk-2.31.1-0.4ubuntu3 [ 67s] [184/316] installing libglib2.0-0-2.56.1-2ubuntu1 [ 68s] No schema files found: doing nothing. [ 68s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 68s] [185/316] installing librpm8-4.14.1+dfsg1-2 [ 68s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 68s] [186/316] installing cpp-7-7.3.0-16ubuntu3 [ 69s] [187/316] keeping dpkg-1.19.0.5ubuntu2 [ 70s] [188/316] installing lynx-2.8.9dev16-3 [ 70s] update-alternatives: using /usr/bin/lynx to provide /usr/bin/www-browser (www-browser) in auto mode [ 70s] [189/316] installing cpp-4:7.3.0-3ubuntu2 [ 70s] [190/316] installing poppler-data-0.4.8-2 [ 71s] [191/316] installing sgml-base-1.29 [ 71s] [192/316] installing install-info-6.5.0.dfsg.1-2 [ 71s] [193/316] installing libxpm4-1:3.5.12-1 [ 71s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 72s] [194/316] installing libxrender1-1:0.9.10-1 [ 72s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 72s] [195/316] installing perl-base-5.26.1-6 [ 72s] [196/316] installing python-minimal-2.7.15~rc1-1 [ 73s] [197/316] installing dash-0.5.8-2.10 [ 73s] No diversion 'diversion of /bin/sh by dash', none removed. [ 73s] Adding 'diversion of /bin/sh to /bin/sh.distrib by bash' [ 73s] No diversion 'diversion of /usr/share/man/man1/sh.1.gz by dash', none removed. [ 73s] Adding 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by bash' [ 73s] dpkg-query: no packages found matching bash [ 73s] Removing 'diversion of /bin/sh to /bin/sh.distrib by bash' [ 73s] Adding 'diversion of /bin/sh to /bin/sh.distrib by dash' [ 73s] Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by bash' [ 73s] Adding 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' [ 73s] [198/316] installing libavahi-client3-0.7-3.1ubuntu1 [ 73s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 73s] [199/316] installing libcroco3-0.6.12-2 [ 73s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 74s] [200/316] installing libnih-dbus1-1.0.3-6ubuntu2 [ 74s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 74s] [201/316] installing libxext6-2:1.3.3-1 [ 74s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 74s] [202/316] installing xsltproc-1.1.29-5 [ 74s] [203/316] installing libharfbuzz0b-1.7.2-1ubuntu1 [ 74s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 75s] [204/316] installing librpmsign8-4.14.1+dfsg1-2 [ 75s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 75s] [205/316] installing libxt6-1:1.1.5-1 [ 75s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 75s] [206/316] installing bsdmainutils-11.1.2ubuntu1 [ 75s] update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode [ 75s] update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode [ 75s] [207/316] installing rpm-common-4.14.1+dfsg1-2 [ 76s] [208/316] installing librpmbuild8-4.14.1+dfsg1-2 [ 76s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 76s] [209/316] installing gcc-7-7.3.0-16ubuntu3 [ 77s] [210/316] installing debconf-1.5.66 [ 78s] [211/316] installing init-system-helpers-1.51 [ 78s] [212/316] installing gcc-4:7.3.0-3ubuntu2 [ 79s] [213/316] installing perl-modules-5.26-5.26.1-6 [ 80s] [214/316] installing readline-common-7.0-3 [ 80s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 80s] [215/316] installing xml-core-0.18 [ 81s] Processing triggers for sgml-base (1.29) ... [ 81s] [216/316] installing gzip-1.6-5ubuntu1 [ 81s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 81s] [217/316] installing info-6.5.0.dfsg.1-2 [ 81s] update-alternatives: using /usr/bin/info to provide /usr/bin/infobrowser (infobrowser) in auto mode [ 81s] Processing triggers for mime-support (3.60ubuntu1) ... [ 81s] [218/316] installing libharfbuzz-icu0-1.7.2-1ubuntu1 [ 81s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 81s] [219/316] installing libxi6-2:1.7.9-1 [ 82s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 82s] [220/316] installing grep-3.1-2 [ 82s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 82s] [221/316] installing libxmu6-2:1.1.2-2 [ 82s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 82s] [222/316] installing opensp-1.5.2-13ubuntu2 [ 82s] Processing triggers for sgml-base (1.29) ... [ 83s] [223/316] installing libcups2-2.2.7-1ubuntu2 [ 83s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 83s] [224/316] installing openjade-1.4devel1-21.3 [ 83s] Processing triggers for sgml-base (1.29) ... [ 83s] [225/316] installing g++-7-7.3.0-16ubuntu3 [ 85s] [226/316] installing gettext-0.19.8.1-6 [ 85s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 85s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 85s] [227/316] installing docbook-xsl-1.79.1+dfsg-2 [ 86s] Processing triggers for sgml-base (1.29) ... [ 86s] [228/316] installing tzdata-2018d-1 [ 87s] Current default time zone: 'Etc/UTC' [ 87s] Local time is now: Wed Feb 20 05:36:30 UTC 2019. [ 87s] Universal Time is now: Wed Feb 20 05:36:30 UTC 2019. [ 87s] Run 'dpkg-reconfigure tzdata' if you wish to change it. [ 87s] [229/316] installing libcupsimage2-2.2.7-1ubuntu2 [ 87s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 88s] [230/316] installing libssl1.1-1.1.0g-2ubuntu4 [ 88s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 88s] [231/316] installing locales-2.27-3ubuntu1 [ 90s] Generating locales (this might take a while)... [ 90s] Generation complete. [ 90s] [232/316] installing flex-2.6.4-6 [ 90s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 91s] [233/316] installing libpam0g-1.1.8-3.6ubuntu2 [ 91s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 91s] [234/316] installing libreadline7-7.0-3 [ 91s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 91s] [235/316] installing ucf-3.0038 [ 91s] Moving old data out of the way [ 92s] [236/316] installing g++-4:7.3.0-3ubuntu2 [ 92s] update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode [ 92s] [237/316] installing libtool-2.4.6-2 [ 92s] [238/316] installing libxaw7-2:1.0.13-1 [ 92s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 93s] [239/316] installing libperl5.26-5.26.1-6 [ 93s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 94s] [240/316] installing procps-2:3.3.12-3ubuntu1 [ 94s] update-alternatives: using /usr/bin/w.procps to provide /usr/bin/w (w) in auto mode [ 94s] [241/316] installing man-db-2.8.3-2 [ 94s] Building database of manual pages ... [ 106s] Processing triggers for mime-support (3.60ubuntu1) ... [ 106s] [242/316] installing fontconfig-config-2.12.6-0ubuntu2 [ 106s] Processing triggers for man-db (2.8.3-2) ... [ 106s] Processing triggers for sgml-base (1.29) ... [ 107s] [243/316] installing libpython3.6-minimal-3.6.5-3 [ 107s] [244/316] installing tex-common-6.09 [ 108s] update-language: texlive-base not installed and configured, doing nothing! [ 108s] Processing triggers for man-db (2.8.3-2) ... [ 108s] [245/316] installing libpam-modules-bin-1.1.8-3.6ubuntu2 [ 108s] Processing triggers for man-db (2.8.3-2) ... [ 108s] [246/316] installing libpaper1-1.1.24+nmu5ubuntu1 [ 109s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 109s] Processing triggers for man-db (2.8.3-2) ... [ 109s] [247/316] installing perl-5.26.1-6 [ 109s] Processing triggers for man-db (2.8.3-2) ... [ 109s] [248/316] installing gawk-1:4.1.4+dfsg-1build1 [ 110s] Processing triggers for man-db (2.8.3-2) ... [ 110s] [249/316] installing libpython2.7-stdlib-2.7.15~rc1-1 [ 111s] [250/316] installing util-linux-2.31.1-0.4ubuntu3 [ 112s] Processing triggers for mime-support (3.60ubuntu1) ... [ 112s] Processing triggers for man-db (2.8.3-2) ... [ 112s] [251/316] installing base-files-10.1ubuntu2 [ 112s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 113s] Processing triggers for man-db (2.8.3-2) ... [ 113s] [252/316] installing libarchive-zip-perl-1.60-1 [ 113s] Processing triggers for man-db (2.8.3-2) ... [ 113s] [253/316] installing libpython-stdlib-2.7.15~rc1-1 [ 113s] [254/316] installing libsgmls-perl-1.03ii-36 [ 113s] Processing triggers for man-db (2.8.3-2) ... [ 114s] [255/316] installing libtimedate-perl-2.3000-2 [ 114s] Processing triggers for man-db (2.8.3-2) ... [ 114s] [256/316] installing preview-latex-style-11.91-1ubuntu1 [ 114s] Processing triggers for tex-common (6.09) ... [ 114s] [257/316] installing intltool-debian-0.35.0+20060710.4 [ 115s] [258/316] installing libdpkg-perl-1.19.0.5ubuntu2 [ 115s] Processing triggers for man-db (2.8.3-2) ... [ 115s] [259/316] installing libpaper-utils-1.1.24+nmu5ubuntu1 [ 115s] Processing triggers for man-db (2.8.3-2) ... [ 116s] [260/316] installing autoconf-2.69-11 [ 116s] Processing triggers for man-db (2.8.3-2) ... [ 116s] [261/316] installing libpython2.7-2.7.15~rc1-1 [ 117s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 117s] [262/316] installing python2.7-2.7.15~rc1-1 [ 118s] Processing triggers for mime-support (3.60ubuntu1) ... [ 118s] Processing triggers for man-db (2.8.3-2) ... [ 118s] [263/316] installing sgml-data-2.0.10 [ 119s] Processing triggers for sgml-base (1.29) ... [ 119s] [264/316] installing libfontconfig1-2.12.6-0ubuntu2 [ 119s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 119s] [265/316] installing mount-2.31.1-0.4ubuntu3 [ 119s] Processing triggers for man-db (2.8.3-2) ... [ 119s] [266/316] installing libpam-modules-1.1.8-3.6ubuntu2 [ 120s] Processing triggers for man-db (2.8.3-2) ... [ 120s] [267/316] installing libpython3.6-stdlib-3.6.5-3 [ 121s] [268/316] installing automake-1:1.15.1-3ubuntu2 [ 121s] update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake (automake) in auto mode [ 121s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 121s] Processing triggers for man-db (2.8.3-2) ... [ 122s] [269/316] installing docbook-4.5-6 [ 122s] Processing triggers for sgml-base (1.29) ... [ 122s] [270/316] installing libfile-stripnondeterminism-perl-0.040-1.1~build1 [ 123s] [271/316] installing libpam-runtime-1.1.8-3.6ubuntu2 [ 123s] Processing triggers for man-db (2.8.3-2) ... [ 123s] [272/316] installing sgmlspl-1.03ii-36 [ 123s] Processing triggers for man-db (2.8.3-2) ... [ 123s] [273/316] installing docbook-xml-4.5-8 [ 126s] Processing triggers for sgml-base (1.29) ... [ 126s] [274/316] installing po-debconf-1.0.20 [ 127s] Processing triggers for man-db (2.8.3-2) ... [ 127s] [275/316] installing python-2.7.15~rc1-1 [ 128s] Processing triggers for man-db (2.8.3-2) ... [ 128s] [276/316] installing bash-4.4.18-2ubuntu1 [ 128s] update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode [ 128s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 128s] Processing triggers for man-db (2.8.3-2) ... [ 129s] [277/316] installing libpython3.6-3.6.5-3 [ 129s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 129s] [278/316] installing passwd-1:4.5-1ubuntu1 [ 129s] Shadow passwords are now on. [ 129s] Processing triggers for man-db (2.8.3-2) ... [ 130s] [279/316] installing dpkg-dev-1.19.0.5ubuntu2 [ 130s] Processing triggers for man-db (2.8.3-2) ... [ 132s] [280/316] installing libpoppler73-0.62.0-2ubuntu2 [ 132s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 133s] [281/316] installing libcairo2-1.15.10-2 [ 133s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 133s] [282/316] installing libgs9-9.22~dfsg+1-0ubuntu1 [ 134s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 134s] [283/316] installing pychecker-0.8.19-14 [ 135s] Processing triggers for man-db (2.8.3-2) ... [ 135s] [284/316] installing python-epydoc-3.0.1+dfsg-17 [ 136s] Processing triggers for man-db (2.8.3-2) ... [ 136s] [285/316] installing python-funcsigs-1.0.2-4 [ 137s] [286/316] installing python-pkg-resources-39.0.1-2 [ 137s] [287/316] installing python-six-1.11.0-2 [ 138s] [288/316] installing docbook-to-man-1:2.0.0-41 [ 138s] Processing triggers for man-db (2.8.3-2) ... [ 138s] Processing triggers for sgml-base (1.29) ... [ 138s] [289/316] installing pkg-config-0.29.1-0ubuntu2 [ 139s] Processing triggers for man-db (2.8.3-2) ... [ 139s] [290/316] installing build-essential-12.4ubuntu1 [ 139s] [291/316] installing docbook-dsssl-1.79-9.1 [ 140s] Processing triggers for sgml-base (1.29) ... [ 140s] Processing triggers for man-db (2.8.3-2) ... [ 140s] [292/316] installing login-1:4.5-1ubuntu1 [ 140s] Processing triggers for man-db (2.8.3-2) ... [ 141s] [293/316] installing python-rpm-4.14.1+dfsg1-2 [ 141s] [294/316] installing vim-2:8.0.1453-1ubuntu1 [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vim (vim) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vimdiff (vimdiff) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rvim (rvim) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rview (rview) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vi (vi) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/view (view) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/ex (ex) in auto mode [ 142s] update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/editor (editor) in auto mode [ 142s] [295/316] installing debhelper-11.1.6ubuntu1 [ 142s] dpkg: debhelper: dependency problems, but configuring anyway as you requested: [ 142s] debhelper depends on dh-autoreconf (>= 17~); however: [ 142s] Package dh-autoreconf is not installed. [ 142s] debhelper depends on dh-strip-nondeterminism (>= 0.028~); however: [ 142s] Package dh-strip-nondeterminism is not installed. [ 142s] Processing triggers for man-db (2.8.3-2) ... [ 145s] [296/316] installing librpm-tizen-4.11.0.1.tizen20140530-tizen20140723 [ 146s] Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 146s] [297/316] installing texlive-binaries-2017.20170613.44572-8build1 [ 147s] update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin (xdvi.bin) in auto mode [ 147s] update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex (bibtex) in auto mode [ 147s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 148s] Processing triggers for man-db (2.8.3-2) ... [ 149s] Processing triggers for tex-common (6.09) ... [ 149s] update-language: texlive-base not installed and configured, doing nothing! [ 149s] texlive-base is not ready, skipping fmtutil --all call [ 149s] [298/316] installing python-setuptools-39.0.1-2 [ 150s] [299/316] installing python-nose-1.3.7-3 [ 151s] Processing triggers for man-db (2.8.3-2) ... [ 151s] [300/316] installing dh-strip-nondeterminism-0.040-1.1~build1 [ 151s] Processing triggers for man-db (2.8.3-2) ... [ 151s] [301/316] installing python-pbr-3.1.1-3ubuntu3 [ 152s] update-alternatives: using /usr/bin/python2-pbr to provide /usr/bin/pbr (pbr) in auto mode [ 152s] [302/316] installing dh-autoreconf-17 [ 152s] Processing triggers for man-db (2.8.3-2) ... [ 153s] [303/316] installing texlive-base-2017.20180305-1 [ 155s] mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... [ 156s] mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... [ 156s] mktexlsr: Updating /var/lib/texmf/ls-R... [ 156s] mktexlsr: Done. [ 156s] tl-paper: setting paper size for dvips to a4: /var/lib/texmf/dvips/config/config-paper.ps [ 156s] tl-paper: setting paper size for dvipdfmx to a4: /var/lib/texmf/dvipdfmx/dvipdfmx-paper.cfg [ 156s] tl-paper: setting paper size for xdvi to a4: /var/lib/texmf/xdvi/XDvi-paper [ 157s] tl-paper: setting paper size for pdftex to a4: /var/lib/texmf/tex/generic/config/pdftexconfig.tex [ 157s] Processing triggers for mime-support (3.60ubuntu1) ... [ 157s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 157s] Processing triggers for man-db (2.8.3-2) ... [ 158s] Processing triggers for tex-common (6.09) ... [ 158s] Running mktexlsr. This may take some time... done. [ 158s] Running updmap-sys. This may take some time... done. [ 158s] Running mktexlsr /var/lib/texmf ... done. [ 158s] Building format(s) --all. [ 160s] This may take some time... done. [ 160s] [304/316] installing texlive-fonts-recommended-2017.20180305-1 [ 162s] Processing triggers for tex-common (6.09) ... [ 162s] Running mktexlsr. This may take some time... done. [ 162s] Running updmap-sys. This may take some time... done. [ 162s] Running mktexlsr /var/lib/texmf ... done. [ 163s] [305/316] installing texlive-plain-generic-2017.20180305-2 [ 166s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 166s] Processing triggers for tex-common (6.09) ... [ 166s] Running mktexlsr. This may take some time... done. [ 167s] [306/316] installing python-mock-2.0.0-3 [ 167s] [307/316] installing texlive-latex-base-2017.20180305-1 [ 168s] Processing triggers for man-db (2.8.3-2) ... [ 168s] Processing triggers for tex-common (6.09) ... [ 168s] Running mktexlsr. This may take some time... done. [ 169s] Running updmap-sys. This may take some time... done. [ 169s] Running mktexlsr /var/lib/texmf ... done. [ 169s] Building format(s) --all. [ 173s] This may take some time... done. [ 173s] [308/316] installing texlive-latex-recommended-2017.20180305-1 [ 175s] Processing triggers for man-db (2.8.3-2) ... [ 175s] Processing triggers for tex-common (6.09) ... [ 175s] Running mktexlsr. This may take some time... done. [ 176s] [309/316] installing tipa-2:1.3-20 [ 176s] Regenerating '/var/lib/texmf/fmtutil.cnf-DEBIAN'... done. [ 176s] Regenerating '/var/lib/texmf/fmtutil.cnf-TEXLIVEDIST'... done. [ 176s] update-fmtutil has updated the following file(s): [ 176s] /var/lib/texmf/fmtutil.cnf-DEBIAN [ 176s] /var/lib/texmf/fmtutil.cnf-TEXLIVEDIST [ 176s] If you want to activate the changes in the above file(s), [ 176s] you should run fmtutil-sys or fmtutil. [ 176s] Processing triggers for tex-common (6.09) ... [ 176s] Running mktexlsr. This may take some time... done. [ 177s] Running updmap-sys. This may take some time... done. [ 177s] Running mktexlsr /var/lib/texmf ... done. [ 177s] [310/316] installing gtk-doc-tools-1.27-3 [ 177s] Processing triggers for man-db (2.8.3-2) ... [ 178s] Processing triggers for sgml-base (1.29) ... [ 178s] [311/316] installing texlive-pictures-2017.20180305-1 [ 180s] Processing triggers for man-db (2.8.3-2) ... [ 180s] Processing triggers for tex-common (6.09) ... [ 180s] Running mktexlsr. This may take some time... done. [ 181s] Running updmap-sys. This may take some time... done. [ 181s] Running mktexlsr /var/lib/texmf ... done. [ 181s] [312/316] installing texlive-latex-extra-2017.20180305-2 [ 187s] Processing triggers for man-db (2.8.3-2) ... [ 187s] Processing triggers for tex-common (6.09) ... [ 187s] Running mktexlsr. This may take some time... done. [ 188s] Running updmap-sys. This may take some time... done. [ 188s] Running mktexlsr /var/lib/texmf ... done. [ 188s] [313/316] installing texlive-xetex-2017.20180305-1 [ 190s] Processing triggers for tex-common (6.09) ... [ 190s] Running mktexlsr. This may take some time... done. [ 190s] Building format(s) --all. [ 196s] This may take some time... done. [ 196s] [314/316] installing texlive-formats-extra-2017.20180305-2 [ 197s] Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 197s] Processing triggers for man-db (2.8.3-2) ... [ 197s] Processing triggers for tex-common (6.09) ... [ 198s] Running mktexlsr. This may take some time... done. [ 198s] Running updmap-sys. This may take some time... done. [ 198s] Running mktexlsr /var/lib/texmf ... done. [ 198s] Building format(s) --all. [ 206s] This may take some time... done. [ 206s] [315/316] installing sgml2x-1.0.0-11.4 [ 206s] Processing triggers for sgml-base (1.29) ... [ 206s] Processing triggers for man-db (2.8.3-2) ... [ 207s] [316/316] installing docbook-utils-0.6.14-3.3 [ 207s] Processing triggers for man-db (2.8.3-2) ... [ 207s] configuring all installed packages... [ 207s] removing nis flags from /var/cache/build/root_1/etc/nsswitch.conf... [ 207s] now finalizing build dir... [ 207s] texhash: Updating /usr/local/share/texmf/ls-R... [ 207s] texhash: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... [ 207s] texhash: Updating /var/lib/texmf/ls-R-TEXMFMAIN... [ 207s] texhash: Updating /var/lib/texmf/ls-R... [ 207s] texhash: Done. [ 207s] Running build time source services... [ 208s] dpkg-source: warning: extracting unsigned source package (/usr/src/packages/SOURCES/git-buildpackage_0.9.9-tizen20180912.dsc) [ 208s] dpkg-source: info: extracting git-buildpackage in /usr/src/packages/BUILD [ 208s] dpkg-source: info: unpacking git-buildpackage_0.9.9.orig.tar.gz [ 208s] dpkg-source: info: applying git-buildpackage_0.9.9-tizen20180912.diff.gz [ 208s] dpkg-source: info: upstream files that have been modified: [ 208s] /usr/src/packages/BUILD/gbp/scripts/buildpackage_rpm.py [ 208s] /usr/src/packages/BUILD/packaging/git-buildpackage.changes [ 208s] /usr/src/packages/BUILD/packaging/git-buildpackage.spec [ 208s] ----------------------------------------------------------------- [ 208s] ----- building git-buildpackage_0.9.9-tizen20180912.dsc (user abuild) [ 208s] ----------------------------------------------------------------- [ 208s] ----------------------------------------------------------------- [ 208s] dpkg-buildpackage: info: source package git-buildpackage [ 208s] dpkg-buildpackage: info: source version 0.9.9-tizen20180912 [ 208s] dpkg-buildpackage: info: source distribution unstable [ 208s] dpkg-buildpackage: info: source changed by Biao Wang [ 208s] dpkg-source --before-build BUILD [ 208s] dpkg-buildpackage: info: host architecture amd64 [ 208s] dpkg-source: info: using options from BUILD/debian/source/options: --extend-diff-ignore=^(tests/test_rpm_data/.*|tests/component/rpm/data/.*|tests/component/deb/data/.*) --diff-ignore [ 208s] fakeroot debian/rules clean [ 208s] dh clean --with python2 [ 208s] debian/rules override_dh_auto_clean [ 208s] make[1]: Entering directory '/usr/src/packages/BUILD' [ 208s] dh_auto_clean [ 209s] python setup.py clean -a [ 209s] /usr/lib/python2.7/dist-packages/setuptools/dist.py:406: UserWarning: The version specified ('0.9.9-tizen20180912') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details. [ 209s] "details." % self.metadata.version [ 209s] running clean [ 209s] 'build/lib.linux-x86_64-2.7' does not exist -- can't clean it [ 209s] 'build/bdist.linux-x86_64' does not exist -- can't clean it [ 209s] 'build/scripts-2.7' does not exist -- can't clean it [ 209s] find . -name \*.pyc -exec rm {} \+ [ 209s] # Remove renamed files - renames are not correctly expressed in debian.diff [ 209s] rm -f debian/doc-base [ 209s] rm -f debian/docs [ 209s] rm -f debian/examples [ 209s] rm -f debian/manpages [ 209s] rm -rf build/ [ 209s] make -C docs/ clean [ 209s] make[2]: Entering directory '/usr/src/packages/BUILD/docs' [ 209s] rm -r manual-html/ [ 209s] rm: cannot remove 'manual-html/': No such file or directory [ 209s] Makefile:71: recipe for target 'clean' failed [ 209s] make[2]: [clean] Error 1 (ignored) [ 209s] rm *.1 *.5 manpage.* version.ent [ 209s] rm: cannot remove '*.1': No such file or directory [ 209s] rm: cannot remove '*.5': No such file or directory [ 209s] rm: cannot remove 'manpage.*': No such file or directory [ 209s] rm: cannot remove 'version.ent': No such file or directory [ 209s] Makefile:71: recipe for target 'clean' failed [ 209s] make[2]: [clean] Error 1 (ignored) [ 209s] rm -r buildxref [ 209s] rm: cannot remove 'buildxref': No such file or directory [ 209s] Makefile:71: recipe for target 'clean' failed [ 209s] make[2]: [clean] Error 1 (ignored) [ 209s] make[2]: Leaving directory '/usr/src/packages/BUILD/docs' [ 209s] rm gbp/version.py [ 209s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 209s] dh_clean [ 209s] dpkg-source -b BUILD [ 209s] dpkg-source: info: using options from BUILD/debian/source/options: --extend-diff-ignore=^(tests/test_rpm_data/.*|tests/component/rpm/data/.*|tests/component/deb/data/.*) --diff-ignore [ 209s] dpkg-source: warning: source directory 'BUILD' is not - 'git-buildpackage-0.9.9' [ 209s] dpkg-source: warning: .orig directory name BUILD.orig is not - (wanted git-buildpackage-0.9.9.orig) [ 209s] dpkg-source: info: using source format '1.0' [ 209s] dpkg-source: info: building git-buildpackage using existing git-buildpackage_0.9.9.orig.tar.gz [ 209s] dpkg-source: info: building git-buildpackage in git-buildpackage_0.9.9-tizen20180912.diff.gz [ 209s] dpkg-source: warning: the diff modifies the following upstream files: [ 209s] gbp/scripts/buildpackage_rpm.py [ 209s] packaging/git-buildpackage.changes [ 209s] packaging/git-buildpackage.spec [ 209s] dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) [ 209s] dpkg-source: info: building git-buildpackage in git-buildpackage_0.9.9-tizen20180912.dsc [ 209s] debian/rules build [ 209s] dh build --with python2 [ 209s] dh_update_autotools_config [ 209s] dh_auto_configure [ 209s] debian/rules override_dh_auto_build [ 209s] make[1]: Entering directory '/usr/src/packages/BUILD' [ 209s] dh_auto_build [ 210s] python setup.py build --force [ 210s] /usr/lib/python2.7/dist-packages/setuptools/dist.py:406: UserWarning: The version specified ('0.9.9-tizen20180912') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details. [ 210s] "details." % self.metadata.version [ 210s] running build [ 210s] running build_py [ 210s] creating build [ 210s] creating build/lib.linux-x86_64-2.7 [ 210s] creating build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/tmpfile.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/version.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/log.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/format.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/notifications.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/dch.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/patch_series.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/command_wrappers.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/__init__.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/tristate.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/config.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] copying gbp/errors.py -> build/lib.linux-x86_64-2.7/gbp [ 210s] creating build/lib.linux-x86_64-2.7/gbp/pkg [ 210s] copying gbp/pkg/pristinetar.py -> build/lib.linux-x86_64-2.7/gbp/pkg [ 210s] copying gbp/pkg/__init__.py -> build/lib.linux-x86_64-2.7/gbp/pkg [ 210s] creating build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/upstreamsource.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/control.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/uscan.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/format.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/source.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/pristinetar.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/changelog.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/__init__.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/dscfile.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/git.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] copying gbp/deb/policy.py -> build/lib.linux-x86_64-2.7/gbp/deb [ 210s] creating build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/supercommand.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/rpm_ch.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/dch.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_srpm.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_orig_rpm.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/clone_bb.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_dsc.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/create_remote_repo.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/clone.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/submit_bb.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_dscs.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/pq_bb.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/buildpackage_bb.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/__init__.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/buildpackage.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/pq_rpm.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_bb.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/pq.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/config.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/pull.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/buildpackage_rpm.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] copying gbp/scripts/import_orig.py -> build/lib.linux-x86_64-2.7/gbp/scripts [ 210s] creating build/lib.linux-x86_64-2.7/gbp/bb [ 210s] copying gbp/bb/__init__.py -> build/lib.linux-x86_64-2.7/gbp/bb [ 210s] creating build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/repository.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/vfs.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/fastimport.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/commit.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/modifier.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/__init__.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/args.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] copying gbp/git/errors.py -> build/lib.linux-x86_64-2.7/gbp/git [ 210s] creating build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/linkedlist.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/lib_rpm.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/changelog.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/__init__.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/git.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] copying gbp/rpm/policy.py -> build/lib.linux-x86_64-2.7/gbp/rpm [ 210s] creating build/lib.linux-x86_64-2.7/gbp/scripts/common [ 210s] copying gbp/scripts/common/__init__.py -> build/lib.linux-x86_64-2.7/gbp/scripts/common [ 210s] copying gbp/scripts/common/buildpackage.py -> build/lib.linux-x86_64-2.7/gbp/scripts/common [ 210s] copying gbp/scripts/common/pq.py -> build/lib.linux-x86_64-2.7/gbp/scripts/common [ 210s] copying gbp/scripts/common/import_orig.py -> build/lib.linux-x86_64-2.7/gbp/scripts/common [ 210s] running build_scripts [ 210s] creating build/scripts-2.7 [ 210s] copying and adjusting bin/git-buildpackage -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-import-dsc -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-import-orig -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-dch -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-import-dscs -> build/scripts-2.7 [ 210s] copying and adjusting bin/gbp-pq -> build/scripts-2.7 [ 210s] copying and adjusting bin/gbp-pull -> build/scripts-2.7 [ 210s] copying and adjusting bin/gbp-clone -> build/scripts-2.7 [ 210s] copying and adjusting bin/gbp-create-remote-repo -> build/scripts-2.7 [ 210s] copying bin/git-pbuilder -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-import-srpm -> build/scripts-2.7 [ 210s] copying and adjusting bin/gbp-pq-rpm -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-buildpackage-rpm -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-import-orig-rpm -> build/scripts-2.7 [ 210s] copying and adjusting bin/git-rpm-ch -> build/scripts-2.7 [ 210s] changing mode of build/scripts-2.7/git-buildpackage from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-import-dsc from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-import-orig from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-dch from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-import-dscs from 664 to 775 [ 210s] changing mode of build/scripts-2.7/gbp-pq from 664 to 775 [ 210s] changing mode of build/scripts-2.7/gbp-pull from 664 to 775 [ 210s] changing mode of build/scripts-2.7/gbp-clone from 664 to 775 [ 210s] changing mode of build/scripts-2.7/gbp-create-remote-repo from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-pbuilder from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-import-srpm from 664 to 775 [ 210s] changing mode of build/scripts-2.7/gbp-pq-rpm from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-buildpackage-rpm from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-import-orig-rpm from 664 to 775 [ 210s] changing mode of build/scripts-2.7/git-rpm-ch from 664 to 775 [ 210s] epydoc -v --config=setup.cfg [ 214s] [.........................................................................] [ 214s] make -C docs/ [ 214s] make[2]: Entering directory '/usr/src/packages/BUILD/docs' [ 214s] echo '' > version.ent [ 214s] docbook-2-html -s local main.sgml [ 214s] openjade:W: feature "online" not supported [ 214s] openjade:W: feature "query" only partially supported [ 214s] openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file or directory) [ 214s] openjade:E: specification document does not have the DSSSL architecture as a base architecture [ 214s] Building Packages with git-buildpackage suiteVersion: 0.9.9-tizen20180912Building Debian Packages with git-buildpackageGuidoGuentheragx@sigxcpu.orgVersion: 0.9.9-tizen20180912Introduction Welcome to gbp, a system that integrates the [ 214s] Debian package build [ 214s] system with Git. The current version of this manual can be found [ 214s] here. [ 214s] What can these tools do for you: [ 214s] Import an existing Debian package into GitImport new upstream versions, NMUs etc. with optional filtersAutomatic upstream tarball generationMaintain a consistent branch and tag naming across [ 214s] repositories or across a team of developersAutomatically sign tagsAutomatically push changes to remote repositoriesMake sure you have committed all changes to the right [ 214s] branch before releasingExport to a clean build area before buildingAutomatic debian/changelog generationAutomatic generation of snapshot releases for local testingSimple patch management [ 214s] All of this is (hopefully) being done without restricting the user to certain usage patterns. [ 214s] Repository Layout and TerminologyIt is recommended to have the Debian packaging on a seprate [ 214s] branch than the upstream source this, of course, has [ 214s] no meaning for Debian native packages. [ 214s] This is necessary to be able to import [ 214s] and merge in new upstream versions via gbp import-orig. [ 214s] To distinguish these two branches the following terminology [ 214s] corresponding to the command [ 214s] line and config file options is used: [ 214s] The debian-branch (the default branch [ 214s] name used in the Git repository is master) holds [ 214s] your current development work. That's the branch you usually cut your [ 214s] releases from and the default branch new upstream releases are merged [ 214s] onto. The upstream-branch (the default [ 214s] branch name used in the Git repository is [ 214s] upstream) holds the upstream releases. This can [ 214s] either be a branch you import to or a branch of an upstream repository [ 214s] you pull from. The pristine-tar branch (the default [ 214s] branch name used in the Git repository is [ 214s] pristine-tar) holds the necessary additional [ 214s] information to recreate the original tarball from the [ 214s] upstream-branch. In order to use this feature you need [ 214s] to install the pristine-tar package. There can be one or more patch-queue [ 214s] branches. Every patch-queue branch is related to a [ 214s] debian-branch. If the debian-branch is called [ 214s] master the corresponding patch-queue branch is [ 214s] called patch-queue/master. The patch-queue branch is [ 214s] the debian branch plus the contents of [ 214s] debian/patches applied. These branches are managed [ 214s] with gbp pq. [ 214s] You're completely [ 214s] free to pick any repository layout and the branch names above are only [ 214s] gbp's defaults. They can be changed at any point in time [ 214s] and you can work with an arbitrary number of branches. [ 214s] For example branches like nmu, [ 214s] backports or stable might [ 214s] (temporarily or permanent) become your debian-branch [ 214s] and branches like dfsg or [ 214s] snapshots might become your [ 214s] upstream-branch - it doesn't matter if these branches [ 214s] are maintained with gbp import-orig or not. A recommended branch layout is described in . [ 214s] Since gbp buildpackage only works with local Git-repositories [ 214s] you have to use git push in order to publish your [ 214s] changes to remote repositories like git.debian.org, this can also be [ 214s] automized with gbp buildpackage's post-tag [ 214s] hook.Workflow A typical, simple workflow consists of the following steps: [ 214s] Import a new Debian package via gbp import-dsc. This [ 214s] imports the Debian Package on the debian-branch [ 214s] and the upstream sources on the upstream-branch.Develop, test, commit changes. During this time you can [ 214s] always build the package with gbp buildpackage. In case you have [ 214s] uncommitted changes in your source tree you can use the [ 214s] --git-ignore-new option.Optionally you can create the Debian changelog entries [ 214s] using gbp dch and create snapshot releases for testing using its [ 214s] --snapshot option.Once satisfied you can build the final package with [ 214s] gbp buildpackage --git-tag. This additionally [ 214s] creates a tag within Git so you can switch back to that version later [ 214s] at any time. The format of the tags can be specified, tags can [ 214s] be GPG signed.When a new upstream version is released and upstream [ 214s] isn't using Git you can import the new version via gbp import-orig [ 214s] onto the upstream-branch. gbp import-orig will [ 214s] by default try to merge the new upstream version onto the [ 214s] debian-branch. You can skip the merge with [ 214s] --no-merge. After resolving any potential conflicts [ 214s] go back to the second step. These steps will be explaind in more details in the following sections.Importing SourcesImporting already existing Debian packagesImporting an already exsting debian package into a git repository is as easy as: [ 214s] gbp import-dsc package_0.1-1.dsc [ 214s] [ 214s] This will create a new git repository named after the imported package, put [ 214s] the upstream sources onto the upstream-branch and the [ 214s] debian patch on the debian-branch. In case of a debian [ 214s] native package only the debian-branch is being used. [ 214s] You can specify alternative branch names via the [ 214s] --upstream-branch and --debian-branch [ 214s] options or via the upstream-branch and [ 214s] debian-branch options in the configuration file. [ 214s] If you want to be able to exactly recreate the original tarball [ 214s] (orig.tar.gz) from Git you should also specify the [ 214s] --pristine-tar option. This is recommended. [ 214s] If you want to import further versions you can change into your shiny new [ 214s] Git repository and just continue with the same command: [ 214s] cd package/ [ 214s] gbp import-dsc package_0.1-2.dsc [ 214s] gbp import-dsc package_0.1-3.dsc [ 214s] gbp import-dsc package_0.2-1.dsc [ 214s] [ 214s] Or you can import all versions at once using gbp import-dscs: [ 214s] gbp import-dscs /path/to/history/package_*.dsc [ 214s] [ 214s] This will create a Git repository if necessary and import all versions sorted [ 214s] by version number. [ 214s] Importing a new upstream versionChange into your git repository (which can be empty), make sure it [ 214s] has all local modifications committed and run either of: [ 214s] gbp import-orig /path/to/package_0.2.orig.tar.gz [ 214s] gbp import-orig /path/to/package_0.2.tar.bz2 [ 214s] gbp import-orig /path/to/package-0.2/ [ 214s] [ 214s] This puts the upstream souces onto the upstream-branch and [ 214s] tags them accordingly (the default tag format is [ 214s] upstream/%(version)s). [ 214s] The result is then merged onto the debian-branch [ 214s] and a new Debian changelog entry is created. You can again specify [ 214s] different branch names via the --upstream-branch and [ 214s] --debian-branch options. You can also filter out content [ 214s] you don't want imported: [ 214s] gbp import-orig --filter='CVS/*' /path/to/package_0.2.orig.tar.gz [ 214s] [ 214s] The --filter option can be used multiple times for more [ 214s] complex filtering. [ 214s] If you expect a merge conflict you can delay the merge to the [ 214s] debian-branch via the --no-merge and pull in [ 214s] the changes from the upstream-branch later. [ 214s] If you want to be able to exactly recreate the original tarball [ 214s] (orig.tar.gz) from Git you should also specify the [ 214s] --pristine-tar option. This is recommended. [ 214s] To customize the commit message used by gbp import-orig use [ 214s] the --import-msg option. This string is a standard [ 214s] python format string, into which the [ 214s] version variable is interpolated. (i.e., [ 214s] use %(version)s in your message to get [ 214s] the imported upstream version). [ 214s] Converting an existing Git repository If the Git repository wasn't created with gbp import-dsc you have to tell [ 214s] gbp buildpackage and friends where to find the upstream sources. [ 214s] Upstream sources on a branch If the upstream sources are already on a separate branch things are pretty [ 214s] simple. You can either rename that branch to the default [ 214s] upstream-branch name upstream with: [ 214s] git branch upstream theupstream-branch [ 214s] git branch -D theupstream-branch [ 214s] [ 214s] or you can tell gbp buildpackage the name of the branch to use as [ 214s] upstream-branch: [ 214s] cat <<EOF > .git/gbp.conf [ 214s] [DEFAULT] [ 214s] # this is the upstream-branch: [ 214s] upstream-branch=theupstream-branch [ 214s] EOF [ 214s] [ 214s] If you then use gbp import-orig to import new upstream sources, they will [ 214s] from now on end up on theupstream-branch and [ 214s] merged to the debian-branch. [ 214s] Upstream sources not on a branch If you don't have an upstream branch but started your repository with only [ 214s] the upstream sources (not the debian patch) you can simply branch from that [ 214s] point. So use gitk or git-log to locate the commit-id of that commit [ 214s] and create the upstream branch from there, e.g.: [ 214s] COMMIT_ID=`git log --pretty=oneline | tail -1 | awk '{ print $1 }'` [ 214s] git branch upstream $COMMIT_ID [ 214s] The important thing here is that the COMMIT_ID specifies a [ 214s] point on the master branch that carried only the [ 214s] upstream sources and not the debian modifications. The above example [ 214s] assumes that this was the first commit to that repository. [ 214s] There's currently no easy way to create the [ 214s] upstream-branch if you never had the upstream sources [ 214s] as a single commit. Using gbp import-orig on such repositories might lead [ 214s] to unexpected merge results.In order to fix this you can prepend the upstream sources as a [ 214s] single commit to your tree using Git's grafts. Afterwards you [ 214s] can simply create a branch as explained above and gbp import-orig will [ 214s] work as expected.Alternatively, if you are only importing source from original tarballs [ 214s] (for instance when converting from a Subversion repository where the [ 214s] mergeWithUpstream was set for svn-buildpackage), you can create an empty [ 214s] upstream branch with the following commands: [ 214s] git checkout --orphan upstream [ 214s] git rm -rf . [ 214s] git commit --allow-empty -m 'Initial upstream branch.' [ 214s] git checkout -f master [ 214s] With Git versions lower than 1.7.2.3, the commands are slightly more complicated: [ 214s] git symbolic-ref HEAD refs/heads/upstream [ 214s] git rm --cached -r . [ 214s] git commit --allow-empty -m 'Initial upstream branch.' [ 214s] git checkout -f master [ 214s] Starting a Debian package from scratch So far we assumed you already have a Debian package to start with but [ 214s] what if you want to start a new package? First create an empty repository: [ 214s] mkdir package-0.1 [ 214s] cd package-0.1 [ 214s] git init [ 214s] Then you import the upstream sources, branch off the [ 214s] upstream-branch branch and add the debian files (e.g. via dh_make): [ 214s] gbp import-orig -u 0.1 ../package-0.1.tar.gz [ 214s] dh_make [ 214s] [ 214s] That's it, you're done. If you want to publish you're new repository you can use gbp create-remote-repo. [ 214s] When upstream uses GIT If upstream already uses git for packaging there are several ways to handle packaging. Two of them will [ 214s] be described in a bit detail here: [ 214s] No upstream tarballsIf upstream doesn't build upstream tarballs or you don't care about them the simplest [ 214s] way is to clone upstreams repository and create a separate packaging branch in there. [ 214s] In order to help gbp buildpackage to find upstream tags you need to specify the format [ 214s] using the --git-upstream-tag comand line option or the the upstream-tag [ 214s] configuration variable. [ 214s] A common upstream format is to put a v in front of the version number. [ 214s] In this case the configuration option would look like: [ 214s] [git-buildpackage] [ 214s] upstream-tag = v%(version)s [ 214s] version will be replaced with the upstream version number as read from [ 214s] debian/changelog. [ 214s] If you're using pristine-tar you can make gbp buildpackage commit the generated tarball back to the [ 214s] pristine-tar branch by using the --git-pristine-tar-commit option. This will make sure [ 214s] others building your package can regenerate the tarball you generated for building the Debian pacakge. [ 214s] Step by stepTo not make any assumptions about gbp's configuration the following steps have all options given [ 214s] in its long versions on the command line . You can add these [ 214s] to gbp.conf to save lots of typing. [ 214s] First we clone the upstream repository. To avoid any dis ambiguities between the Debian packaging repository [ 214s] and the upstream repository we name the upstream repository ustream instead of the [ 214s] default origin. [ 214s] git clone --no-checkout -o upstream git://git.example.com/libgbp.git [ 214s] cd libgbp [ 214s] git checkout -b debian/sid v1.0 [ 214s] [ 214s] The above makes sure we have debian/sid for the Debian packaging. We didn't create [ 214s] any upstream/* branches, they're not needed for the packaging and only need to be [ 214s] kept up to date. After adding the Debian packaging we build the package. This assumes you're using pristine-tar [ 214s] and upstream uses a version number format as described above: [ 214s] gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='v%(version)s' --git-debian-branch=debian/sid [ 214s] [ 214s] When updating to a new upstream version we simply fetch from upstream and merge in the new tag. Afterwards we [ 214s] update the changelog and build the package: [ 214s] git fetch upstream [ 214s] git merge v1.1 [ 214s] gbp dch --debian-branch=debian/sid --snapshot --auto debian/ [ 214s] gbp buildpackage --git-ignore-new --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='v%(version)s' [ 214s] [ 214s] Note that the above gbp dch call makes sure we only pickup changes in the debian/ [ 214s] directory. Since we told it to build a snapshot changelog entry and we didn't commit the changelog yet [ 214s] we need to tell gbp buildpackage that the working directory is unclean via the --git-ignore-new. [ 214s] Once everything looks good commit the changelog and build a release version: [ 214s] gbp dch --release --auto --git-debian-branch=debian/sid [ 214s] git commit -m"Release 1.1-1" debian/changelog [ 214s] gbp buildpackage --git-upstream-tag='v%(version)s' --git-debian-branch=debian/sid [ 214s] [ 214s] If you want to share you're repository with others you can use gbp create-remote-repo and gbp pull as usual. [ 214s] Upstream tarballsIf you want to track upstream's git but continue to import the upstream tarballs, [ 214s] e.g. to make sure the tarball uploaded [ 214s] to Debian has the same checksum as upstream's you can use the --upstream-vcs-tag option [ 214s] when importing new tarballs with gbp import-orig. Assuming you have the upstream source in your [ 214s] repository with a tag v0.0.1 you can use: [ 214s] gbp import-orig --upstream-vcs-tag=v0.0.1 foo_0.0.1.orig.tar.gz [ 214s] [ 214s] to add upstream's tag as additional parent to the merge commit. [ 214s] See #664771 for more details. [ 214s] Branch layout By default gbp uses one branch to keep the Debian packaging called master [ 214s] and a branch to keep the upstream packaging called upstream. [ 214s] This layout is simple to get started but fails short if one needs to maintain several versions of [ 214s] the package at the same time. Therefore the following layout is recommended: [ 214s] debian/<release> [ 214s] the Debian packaging for a release jessie, [ 214s] wheezy, sid or experimental. [ 214s] upstream/<release> [ 214s] the upstream sources for a release matching one of the above [ 214s] security/<release> [ 214s] security updates for a certain release [ 214s] backports/<release> [ 214s] backports to a certain release [ 214s] dfsg/<release> [ 214s] the dfsg clean upstream sources in case the cleanup is done via a Git [ 214s] merge from upstream to this branch. [ 214s] In case pristine-tar is being used there will be a single pristine-tar [ 214s] branch that keeps all binary deltas. [ 214s] Building packages from the Git repository In order to build a Debian package from the Git repository you use: [ 214s] gbp buildpackage. This builds the upstream tarball as will be described below and [ 214s] invokes Debuild to build the package. To use another build command you [ 214s] can use the --git-builder option as described later in the manual [ 214s] but Debuild is nice since it can invoke lintian. [ 214s] During the development phase (when you're either not on the [ 214s] debian-branch or when you have uncommitted changes in [ 214s] your repository) you'll usually use: [ 214s] gbp buildpackage --git-ignore-newIf gbp buildpackage doesn't find a valid upstream tarball it will [ 214s] create one by looking at the tag matching the upstream version. To change [ 214s] this behaviour see the --git-upstream-tree option. [ 214s] If you want to recreate the original tarball using the additional [ 214s] information from the pristine-tar branch you have to [ 214s] specify the --git-pristine-tar option. This will make sure [ 214s] the upstream tarball matches exactly the one imported. Using this option is [ 214s] the recommended way of recreating the upstream tarball. [ 214s] Once you're satisfied with the build and want to do a release you commit all [ 214s] your changes and issue:gbp buildpackage --git-tagThis will again build the debian package and tag the final result after [ 214s] extracting the current version from the changelog. If you want GPG signed [ 214s] tags you can use the --git-sign and [ 214s] --git-keyid options. To save typing these option can be [ 214s] specified via the configuration files. You can futhermore change the tag [ 214s] format used when creating tags with the debian-tag [ 214s] option, the default is debian/<version>.Using a separate build dirTools like svn-buildpackage use a separate build-area. To achieve a similar behaviour [ 214s] with gbp buildpackage use the --git-export-dir option:gbp buildpackage --git-export-dir=../build-area/This will export the head of the ecurrent branch to [ 214s] ../build-area/package-version, build the [ 214s] package. If you don't want to export the current branch head you can use [ 214s] --git-export to export any treeish object, here are some [ 214s] examples:gbp buildpackage --git-export-dir=../build-area --git-export=debian/0.4.3 [ 214s] gbp buildpackage --git-export-dir=../build-area --git-export=etch [ 214s] gbp buildpackage --git-export-dir=../build-area --git-export=8caed309653d69b7ab440e3d35abc090eb4c6697 [ 214s] gbp buildpackage --git-export-dir=../build-area --git-export=INDEX [ 214s] gbp buildpackage --git-export-dir=../build-area --git-export=WCThe special argument INDEX exports the [ 214s] state of the current index which can be used to include staged but uncommitted [ 214s] changes in the build. Whereas the special argument [ 214s] WC exports the current working copy as is.If you want to default to build in a separate build area you can [ 214s] specify the directory to use in the gbp.conf. [ 214s] [git-buildpackage] [ 214s] # use a build area relative to the git repository [ 214s] export-dir=../build-area [ 214s] # to use the same build area for all packages use an absolute path: [ 214s] #export-dir=/home/debian-packages/build-area [ 214s] gbp buildpackage will cleanup the build-area after a successful build. If [ 214s] you want to keep the build tree use --git-no-purge. [ 214s] Invoking external programs Besides the commands for cleaning the package build dir [ 214s] (cleaner) and building the package [ 214s] (builder) you can also invoke hooks during the package [ 214s] build: immediately before a build (prebuild), [ 214s] after a successful build (postbuild) and after [ 214s] creating a tag (posttag). Typical applications are running [ 214s] lintian or pushing changes into a remote [ 214s] repository. [ 214s] Running lintiangbp buildpackage exports several variables into the [ 214s] posttag's environment (for details see the ). [ 214s] To invoke lintian we need to tell it where to find the changes file: [ 214s] git-buildpackage --git-postbuild='lintian $GBP_CHANGES_FILE' [ 214s] To call lintian automatically after each successful build add: [ 214s] postbuild=lintian $GBP_CHANGES_FILE [ 214s] to your .gbp.conf. [ 214s] Pushing into a remote repositoryIf you want to push your changes automatically after a successful build and tag [ 214s] you can use gbp buildpackage's posttag hook. A very simple invocation would look like this: [ 214s] git-buildpackage --git-tag --git-posttag="git push && git push --tags" [ 214s] This assumes you have set up a remote repository to push to in [ 214s] .git/config.Usually you want to make sure you don't push out any [ 214s] unrelated changes into the remote repository. This is handled by the [ 214s] following hook which only pushes out the created tag to where you pulled [ 214s] from and also forwards the corresponding remote branch to that position: [ 214s] #!/bin/sh -e [ 214s] # [ 214s] # gbp-posttag-push: post tag hook to push out the newly created tag and to [ 214s] # forward the remote branch to that position [ 214s] [ 214s] if ! REMOTE=$(git config --get branch."${GBP_BRANCH}".remote); then [ 214s] REMOTE=origin [ 214s] fi [ 214s] [ 214s] if [ "$GBP_TAG" ]; then [ 214s] echo "Pushing $GBP_TAG to $REMOTE" [ 214s] git push "$REMOTE" "$GBP_TAG" [ 214s] else [ 214s] echo "GBP_TAG not set." [ 214s] exit 1 [ 214s] fi [ 214s] [ 214s] if [ "$GBP_SHA1" ] && [ "$GBP_BRANCH" ]; then [ 214s] git push "$REMOTE" "$GBP_SHA1":"$GBP_BRANCH" [ 214s] else [ 214s] echo "GBP_SHA1 or GBP_BRANCH not set." [ 214s] exit 1 [ 214s] fi [ 214s] echo "done." [ 214s] GBP_TAG, GBP_SHA1 [ 214s] and GBP_BRANCH are passed to the hook via the [ 214s] environment. To call this hook automatically upon tag creation add: [ 214s] posttag="gbp-posttag-push" [ 214s] to your .gbp.conf and make sure gbp-push [ 214s] is somewhere in your $PATH. On Debian [ 214s] systems a more complete example can be found in [ 214s] /usr/share/doc/examples/git-buildpackage/examples/gbp-posttag-push. [ 214s] Running postexport hookgbp buildpackage exports several variables into the [ 214s] postexport's environment (for details see [ 214s] the ). The motivation [ 214s] for the postexport action is to allow further adjustment of [ 214s] the sources prior to building the package. A typical use case [ 214s] scenario is to allow creating multiple source and binary [ 214s] packages from one Debian branch - e.g. the bootstrap gcc and [ 214s] in the next stage the full gcc. [ 214s] The postexport action, postpones the creation of the [ 214s] upstream tarball, so that the metadata for creating it is [ 214s] already present in the exported source tree. The example [ 214s] postexport script below (crosstoolchain-expand.sh) expands [ 214s] changelog, lintian override files, rules and control files [ 214s] according to an environment variable 'PKG_FLAVOR'. [ 214s] Sample gbp.conf - enables source tree export by specifying [ 214s] the export directory: [ 214s] [git-buildpackage] [ 214s] # use a build area relative to the git repository [ 214s] export-dir = ../build-area [ 214s] # disable the since the sources are being exported first [ 214s] cleaner = [ 214s] # post export script that handles expansion of Debian specific files [ 214s] postexport = crosstoolchain-expand.shSample postexport script: crosstoolchain-expand.sh#!/bin/sh [ 214s] # [ 214s] # Purpose: this script is intended for creating multiple source and [ 214s] # binary Debian packages from one source tree. It can be used in [ 214s] # conjunction with git-buildpackage that support a postexport hook [ 214s] # [ 214s] # A typical use is preparing a bootstrap gcc package that is needed [ 214s] # for building newlib and then preparing a full gcc package from the [ 214s] # same source tree. The user may specify the package flavor via [ 214s] # PKG_FLAVOR environmental variable. [ 214s] # [ 214s] # [ 214s] # The script expands/processes the following files: [ 214s] # [ 214s] # - changelog.tmpl is converted to standard Debian changelog [ 214s] # [ 214s] # [ 214s] # - all binary package lintian override template files are expanded [ 214s] # and renamed to the requested package flavor [ 214s] # [ 214s] # - source package lintian override template file is expanded and [ 214s] # renamed [ 214s] # [ 214s] # - rules.$PKG_FLAVOR and control.$PKG_FLAVOR are renamed to rules and [ 214s] # control resp. [ 214s] [ 214s] [ 214s] # the template string has been carefully chosen, so that [ 214s] # e.g. changelogs that refer to the source package can still be [ 214s] # processed by dch/git-dch resp. [ 214s] TMPL_STR=-XXXXXX [ 214s] [ 214s] # by default replace string for the template is empty [ 214s] REPLACE_STR= [ 214s] [ 214s] if [ -n "$PKG_FLAVOR" ]; then [ 214s] REPLACE_STR=-$PKG_FLAVOR [ 214s] fi [ 214s] [ 214s] REPLACE_EXPR="s/$TMPL_STR/$REPLACE_STR/g" [ 214s] [ 214s] [ 214s] # actual processing of relevant files [ 214s] cd debian [ 214s] [ 214s] # expand the template changelog [ 214s] # remove the symlinked version [ 214s] rm changelog [ 214s] chglog_tmpl=changelog.tmpl [ 214s] [ -f "$chglog_tmpl" ] || { [ 214s] echo "Missing changelog template (debian/$chglog_tmpl)" [ 214s] exit 1 [ 214s] } [ 214s] cat changelog.tmpl | sed -e "$REPLACE_EXPR" > changelog [ 214s] rm changelog.tmpl [ 214s] [ 214s] # process binary package lintian overrides - each override must match [ 214s] # its package name [ 214s] for f in *.lintian-overrides.tmpl; do [ 214s] outfile=${f%.tmpl} [ 214s] [ -f "$f" ] || { [ 214s] echo "Missing lintian override files for binary packages" [ 214s] exit 1 [ 214s] } [ 214s] cat $f | sed -e "$REPLACE_EXPR" > ${outfile/$TMPL_STR/$REPLACE_STR} [ 214s] rm $f [ 214s] done [ 214s] [ 214s] # process the only source package lintian override [ 214s] source_lintian=source/lintian-overrides.tmpl [ 214s] cat $source_lintian | sed -e "$REPLACE_EXPR" > ${source_lintian%.tmpl} [ 214s] rm $source_lintian [ 214s] [ 214s] # rules and control file are package flavor specific [ 214s] [ -f rules.$PKG_FLAVOR ] && mv rules.$PKG_FLAVOR rules [ 214s] [ -f control.$PKG_FLAVOR ] && mv control.$PKG_FLAVOR control [ 214s] rm -f rules.* control.* [ 214s] [ 214s] exit 0Working with patches You can use gbp pq to handle patches. See [ 214s] [ 214s] for an example workflow. [ 214s] In order to avoid a patched (unclean) source tree after the build you [ 214s] can use Dpkg-source's unapply-patches option and [ 214s] tell Git to ignore the .pc directory. [ 214s] /usr/share/doc/git-buildpackage/examples/gbp-configure-unpatched-source [ 214s] sets up these two files for you. [ 214s] Releases and SnapshotsWhen branching and merging frequently, the different Debian changelog [ 214s] entries on the different branches tend to get into the way of the automatic [ 214s] merge and the the merge fails - leaving the (pathological) merge to the [ 214s] committer. In order to avoid this gbp dch offers a way for creating [ 214s] changelog entries from Git commits before doing a [ 214s] release or anytime between releases. The simplest way is doing all the changes to the [ 214s] debian-branch without touching [ 214s] debian/changelog at all. Then, when done, do: [ 214s] gbp dch --release This will look up the latest released version in the changelog, [ 214s] increment the version in the Debian changelog, generate changelog [ 214s] messages from the corresponding Git commit id up to the branch head and [ 214s] finally spawns an editor for final changelog file editing by invoking dch [ 214s] --release. But what if you want to have an (unreleased) snapshot for intermediate testing: [ 214s] gbp dch --snapshotwill generate a snapshot release with a specially crafted version number [ 214s] and a warning in the changelog that this is a snapshort release: [ 214s] git-buildpackage (0.3.7~1.gbp470ce2) UNRELEASED; urgency=low [ 214s] [ 214s] ** SNAPSHOT build @470ce29ec7877705c844474a2fd89869aea0406d ** [ 214s] [ 214s] * add support for automatic snapshot During subsequent calls with --snapshot this version [ 214s] number will continue to increase. Since the snapshot banners contains the [ 214s] commit id of the current branch head, gbp dch can figure out what to [ 214s] append to the changelog by itself: [ 214s] gbp dch --snapshot --auto [ 214s] will fetch the commit id and add changelog entries from that point to the [ 214s] current HEAD - again auto incrementing the version number. If you don't want [ 214s] to start at that commit id, you can specify any id or tag with:gbp dch --since=e76a6a180a57701ae4ae381f74523cacb3152780 --snapshot After testing you can remove the snapshot header by a final gbp dch call: [ 214s] gbp dch --since=HEAD --release This will add no further entries but simply remove the specially crafted [ 214s] version number and the snapshort header. Again you can use any commit id [ 214s] or tag instead of HEAD if you want to add further changelog [ 214s] entries - or you can (of course) use --auto again. [ 214s] Customizing snapshot numbersIf the auto incrementing of the snapshot number doesn't suite you needs you [ 214s] can give any python expression that evaluates to a positive integer to [ 214s] calculate the new snapshot number:gbp dch -S -a --snapshot-number=1 [ 214s] gbp dch -S -a --snapshot-number='snapshot + 2' [ 214s] gbp dch -S -a --snapshot-number='os.popen("git-log --pretty=oneline | wc -l").readlines()[0]' [ 214s] gbp dch -S -a --snapshot-number=`git-log --pretty=oneline debian/0.3.3 | wc -l`You can also add the snapshot-number calculation to gbp.conf:[DEFAULT] [ 214s] snapshot-number = os.popen("git-log --pretty=oneline | wc -l").readlines()[0]More on commit messagesYou can use --full to include the full commit [ 214s] message in the changelog, note that you will lose the formatting though, [ 214s] since dch wraps lines by itself.Additionally there are tags Closes: and [ 214s] Thanks: available to customize the commit message. Each tag [ 214s] has to start at the beginning of a single line. For example the git commit message [ 214s] New upstream version [ 214s] [ 214s] Closes: #1000 [ 214s] Thanks: cool upstream [ 214s] would result in a changelog entry: [ 214s] * New upstream version (Closes: #1000) - thanks to cool upstream [ 214s] You can use the Closes: tag multiple times.There are several tags to further customize what (and how) commit messages get [ 214s] included into the changelog:To exclude a commit from the generated changelog use:Git-Dch: Ignore [ 214s] This is e.g. useful if you're just fixing up a previous commit and couldn't [ 214s] ammend it or for other janitorial commits that really don't need to end up in [ 214s] the changelog. For example, the following git commit message [ 214s] Set correct branchnames in debian/gbp.conf [ 214s] [ 214s] Git-Dch: Ignore [ 214s] will not show up in the generated changelog in any way.To include the full commit message in the changelog use: [ 214s] Git-Dch: FullTo only include the short description in the changelog and skip the body use: [ 214s] Git-Dch: Short [ 214s] The latter only takes effect when running gbp dch with the [ 214s] --full option, since including only the short [ 214s] description is the default.Usually changelog entries should correspond to a single Git commit. In this case it's [ 214s] convenient to include the commit id in the changelog entry. [ 214s] This has the advantage that it's easy for people to identify changes without [ 214s] having to write very extensive changelog messages - the link back to Git can be [ 214s] automated via the Vcs-Browser and Vcs-Git [ 214s] fields in debian/control. See Cl2vcs for how this looks.The inclusion of the commit id can be done automatically [ 214s] via gbp dch's --id-length option. Using [ 214s] --id-length=7 would change the above example to: [ 214s] * [571bfd4] New upstream version (Closes: #1000) - thanks to cool upstream [ 214s] This makes it much easier to see which commit actually fixed bug #1000.Configuration filesThe configuration files are parsed in this order: [ 214s] /etc/git-buildpackage/gbp.confsystem wide configuraton~/.gbp.confper user configuration.gbp.confper repository/branch configuration (deprecated)debian/gbp.confper repository/branch configuration.git/gbp.confper (local) repository configuration [ 214s] All have the same format. They consist of several sections, all of them are optional: [ 214s] [DEFAULT]Options in this section apply to gbp buildpackage, [ 214s] gbp import-orig, gbp import-dsc and gbp dch.[buildpackage]Options in this section apply to gbp buildpackage only and override options from the [ 214s] [DEFAULT] section.[import-orig]Options in this section apply to gbp import-orig only and override options from the [ 214s] [DEFAULT] section.[import-dsc]Options in this section apply to gbp import-dsc only and override options from the [ 214s] [DEFAULT] section.[dch]Options in this section apply to gbp dch only and override options from the [ 214s] [DEFAULT] section....Same for the other gbp commands [ 214s] The actual options in these sections are the command line options without [ 214s] the '--' prefix. So --upstream-branch=dfsgfree would read: [ 214s] upstream-branch=dfsgfree in the config file. In the special case of gbp buildpackage the stripped [ 214s] prefix is not '--' but '--git-'. Here's a more complete example:[DEFAULT] [ 214s] # the default build command [ 214s] builder=debuild -i\.git -I.git [ 214s] # the default branch for upstream sources [ 214s] upstream-branch=upstream [ 214s] # the default branch for the debian patch [ 214s] debian-branch=master [ 214s] [ 214s] [buildpackage] [ 214s] upstream-branch=dfsgclean [ 214s] # Sign tags with GPG: [ 214s] sign-tags = True [ 214s] # Keyid to sign tags with [ 214s] #keyid = 0xdeadbeef [ 214s] [ 214s] [import-orig] [ 214s] upstream-branch=notdfsgclean [ 214s] [ 214s] [import-dsc] [ 214s] upstream-branch=notdfsgclean [ 214s] [ 214s] [dch] [ 214s] git-log=--no-mergesFor more details see the manual page.Special use casesHandling non-DFSG clean upstream sourcesIf you have to handle non DFSG clean upstream sources you can use a [ 214s] different branch which you have to create once: [ 214s] git branch dfsg_clean upstream [ 214s] This creates the dfsg_clean branch from the tip of a [ 214s] branch called upstream. Then, when importing a new [ 214s] upstream version, you import the new version on the [ 214s] upstream-branch (by default named [ 214s] upstream) as usual and just don't merge to the [ 214s] debian-branch (by default named [ 214s] master): [ 214s] gbp import-orig --no-merge /path/to/nondfsg-clean-package_10.4.orig.tar.gz [ 214s] git tag 10.4 [ 214s] After the import you can switch to the dfsg_clean [ 214s] branch and get the newly imported changes from the upstream branch: [ 214s] git checkout dfsg_clean [ 214s] git pull . upstream [ 214s] Now make this checkout dfsg clean (preverably by a cleanup script), commit [ 214s] your changes and merge to your debian-branch:cleanup-script.sh [ 214s] git commit -a -m "Make source dfsg clean" [ 214s] git tag 10.4.dfsg [ 214s] git checkout master [ 214s] git pull . dfsg_clean [ 214s] Importing NMUs First create a branch that holds the NMUs from the tip of your [ 214s] debian-branch (default is master) once: [ 214s] git branch nmu master [ 214s] To import an NMU change into the git repository and use gbp import-dsc: [ 214s] git checkout master [ 214s] gbp import-dsc --debian-branch=nmu /path/to/package_1.0-1nmu0.dsc [ 214s] This will import the NMU onto the branched named nmu [ 214s] instead of the default master. This method can also [ 214s] be used to import "old" releases into the Git repository when migrating [ 214s] to Git from another VCS. [ 214s] Using Pbuilder Since Pbuilder uses different command line arguments than [ 214s] Debuild and Dpkg-buildpackage we can't simply pass the options on the [ 214s] command line but have to wrap them in the --git-builder [ 214s] option instead. git-pbuilder helps you with that: [ 214s] [ 214s] git-buildpackage --git-builder="git-pbuilder" --git-cleaner="fakeroot debian/rules clean" [ 214s] [ 214s] Note that we also used a different clean command since since pdebuild [ 214s] clean means something different than debuild [ 214s] clean. [ 214s] [ 214s] We can shorten this further by using ~/.gbp.conf: [ 214s] [ 214s] cat <<EOF > ~/.gbp.conf [ 214s] [DEFAULT] [ 214s] # tell git-buildpackage howto clean the source tree [ 214s] cleaner = fakeroot debian/rules clean [ 214s] # this is how we invoke pbuilder, arguments passed to git-buildpackage will be [ 214s] # passed to dpkg-buildpackge in the chroot [ 214s] builder = /usr/bin/git-pbuilder [ 214s] [ 214s] git-pbuilder defaults to building a package for the [ 214s] sid distribution. If you want to build for another [ 214s] distribution pass this in the DIST environment variable. [ 214s] [ 214s] Invoking gbp buildpackage will now invoke pdebuild by [ 214s] default and all additional command line arguments are passed to [ 214s] dpkg-buildpackage. If you want to use [ 214s] debuild again (without modifying [ 214s] ~/.gbp.conf) you can use: [ 214s] git-buildpackage --git-builder=debuild [ 214s] [ 214s] Furthermore, if you don't want this for all your invocations of [ 214s] gbp buildpackage you can use .git/gbp.conf in [ 214s] one of your Git repositories instead of [ 214s] ~/.gbp.conf. [ 214s] Working on random packages Whenever you need to work on an arbitrary Debian package you can check it [ 214s] right into Git with one command: [ 214s] git-import-dsc --download package [ 214s] cd package [ 214s] git-branch debian [ 214s] This uses apt-get to download the source package, [ 214s] puts the orig tarball on the upstream-branch and the [ 214s] Debian changes on the debian-branch (by default [ 214s] master). The second command [ 214s] creates a branch called debian. Now you can easily [ 214s] modify the package, revert changes you made, create other branches for [ 214s] testing, see what changes you made, etc.. When finished just dogit-commit -a [ 214s] git-diff debian -- [ 214s] to get a nice patch that can be submitted to the Debian BTS. You can also [ 214s] fetch the source package from an URL: [ 214s] [ 214s] git-import-dsc --download http://mentors.debian.net/debian/pool/main/i/ipsec-tools/ipsec-tools_0.7.3-9.dsc [ 214s] [ 214s] The import works incrementally, you can import new versions on top of [ 214s] already imported ones for e.g. easy review of changes. [ 214s] Command Reference agx@sigxcpu.org [ 214s] GuidoGuenthergbp1gbpMaintain Debian packages in Gitgbp--help--version--list-cmdscommandargsDESCRIPTION gbp is used to maintain Debian source packages in the Git version control system. [ 214s] OPTIONS--help [ 214s] Print help--version [ 214s] Print the programs version--list-cmds [ 214s] List all available commandsGBP COMMANDS These are the possible commands. For possible arguments to these commands please [ 214s] see the corresponding man pages. [ 214s] buildpackage [ 214s] Build source and binary packages from a Git repositoryimport-orig [ 214s] Import a new upstream version into a Git repositoryimport-dsc [ 214s] Import a Debian source package into a Git repositoryimport-dscs [ 214s] Import several Debian source packages into a Git repository, sorted [ 214s] by version numberdch [ 214s] Generate the debian/changelog from Git commit historypq [ 214s] Manage debian/patches using Git rebasepull [ 214s] Update a Git repository from a remoteclone [ 214s] Clone a Git repository from a remote and set up the necessary branch tracking.create-remote-repo [ 214s] Create a remote Git repositoryCONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] git-pbuilder1, [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp-buildpackage1git-buildpackagegbp-buildpackageBuild Debian packages from a Git repositorygbp buildpackage--git-[no-]ignore-new--git-tag--git-verbose--git-color=[auto|on|off]--git-color-scheme=COLOR_SCHEME--git-notify=[auto|on|off]--git-upstream-branch=TREEISH--git-debian-branch=BRANCH_NAME--git-ignore-branch--git-[no-]submodules--git-builder=BUILD_CMD--git-cleaner=CLEAN_CMD--git-[no-]pbuilder--git-[no-]qemubuilder--git-dist=DIST--git-arch=ARCH--git-[no-]pbuilder-autoconf--git-pbuilder-options=PBUILDER_OPTIONS--git-[no-]sign-tags--git-keyid=GPG-KEYID--git-posttag=COMMAND--git-postbuild=COMMAND--git-postexport=COMMAND--git-prebuild=COMMAND--git-[no-]build--git-[no-]hooks--git-debian-tag=tag-format--git-upstream-tag=tag-format--git-debian-tag-msg=tag-msg-format--git-force-create--git-no-create-orig--git-upstream-tree=[TAG|BRANCH|TREEISH]--git-tarball-dir=DIRECTORY--git-compression=TYPE--git-compression-level=LEVEL--git-export-dir=DIRECTORY--git-export=TREEISH--git-[no-]pristine-tar--git-[no-]pristine-tar-commit--git-[no-]-purge--git-dont-purge--git-tag-only--git-retagDESCRIPTION gbp buildpackage is used to build Debian source and .deb packages from [ 214s] a Git repository. [ 214s] gbp buildpackage will, in order: [ 214s] Verify that it is being executed from the proper location. [ 214s] Verify that the repository doesn't contain any uncommitted source [ 214s] changes. [ 214s] Verify that it is being executed from the correct branch. [ 214s] (Optionally) export the source tree to a separate build area [ 214s] Build an orig tarball if it doesn't exist. [ 214s] Call debuild(1) (or the application [ 214s] specified via --git-builder) with arguments [ 214s] instructing it to ignore Git meta-data in the diff.gz, passing along [ 214s] all arguments given to gbp buildpackage that don't start with --git-. [ 214s] (Optionally) tag the tree after a successful build [ 214s] (Optionally) call a post build hook - e.g. to run lintian [ 214s] (Optionally) call a post tag hook - e.g. to push the results to a [ 214s] remote repository after creating the tag [ 214s] OPTIONS--git-[no-]ignore-new [ 214s] Don't abort if there are uncommitted changes in the source tree or [ 214s] the current branch doesn't match the [ 214s] DEBIAN-BRANCH. [ 214s] --git-tag [ 214s] Add a git tag after a successful build. [ 214s] --git-builder=BUILD_CMD [ 214s] Use BUILD_CMD instead of [ 214s] debuild -i -I [ 214s] --git-cleaner=CLEAN_CMD [ 214s] Use CLEAN_CMD instead of [ 214s] debuild clean [ 214s] --git-pbuilder [ 214s] Build package using git-pbuilder. Note that this [ 214s] overwrites any --git-builder and [ 214s] --git-cleaner options. [ 214s] --git-qemubuilder [ 214s] Build package using git-pbuilder with [ 214s] qemubuilder. Note that this overwrites any [ 214s] --git-builder and --git-cleaner [ 214s] options. [ 214s] --git-dist=DIST [ 214s] Build for distribution DIST when using [ 214s] --git-pbuilder. If unset build for the unstable [ 214s] distribution. [ 214s] --git-arch=ARCH [ 214s] Build for architecture ARCH when using [ 214s] --git-pbuilder. If unset no architecture is passed [ 214s] to git-pbuilder. [ 214s] --git-pbuilder-autoconf [ 214s] Whether to try to autoconfigure git-pbuilder or to [ 214s] rely on the settings in .pbuilderrc. See the [ 214s] git-pbuilder manpage for details. [ 214s] --git-pbuilder-options [ 214s] Options to pass to pbuilder [ 214s] --git-verbose [ 214s] verbose execution [ 214s] --git-color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --git-notify=[auto|on|off] [ 214s] Whether to send a desktop notification after the build. [ 214s] --git-color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --git-upstream-branch=BRANCH_NAME [ 214s] Branch to build the orig tarball from if [ 214s] --git-upstream-tree is set to [ 214s] BRANCH. Default is [ 214s] upstream. [ 214s] --git-debian-branch=BRANCH_NAME [ 214s] If you're not on this branch when invoking gbp buildpackage it will [ 214s] fail. Default is master. This is done to [ 214s] make sure you don't accidentally release from a topic branch. Not [ 214s] being on this branch will be ignored when using [ 214s] --git-ignore-new. [ 214s] --git-ignore-branch [ 214s] Don't check if the current branch matches [ 214s] DEBIAN-BRANCH. [ 214s] --git-[no-]sign-tags [ 214s] GPG sign all created tags [ 214s] --git-[no-]submodules [ 214s] Include git submodules in the orig tarball. [ 214s] --git-keyid=GPG-KEYID [ 214s] use this keyid for gpg signing tags [ 214s] --git-posttag=COMMAND [ 214s] excecute COMMAND after tagging a new [ 214s] version. [ 214s] Exported environment variables are: GBP_TAG (the name [ 214s] of the generated tag), GBP_BRANCH (the branch the [ 214s] package was build from) and GBP_SHA1 (the sha1 of the [ 214s] commit the tag was created at). [ 214s] --git-postbuild=COMMAND [ 214s] execute COMMAND after successful [ 214s] build. [ 214s] Exported environment variables are: GBP_CHANGES_FILE [ 214s] (the name of the generated changes file), [ 214s] GBP_BUILD_DIR (the build dir). [ 214s] --git-postexport=COMMAND [ 214s] execute COMMAND after exporting the source [ 214s] tree - valid only if --git-export-dir has been specified. [ 214s] Exported environment variables are: GBP_GIT_DIR (the [ 214s] repository the package is being built from), [ 214s] GBP_TMP_DIR (the temporary directory where the sources [ 214s] have been initially exported). [ 214s] --git-prebuild=COMMAND [ 214s] execute COMMAND from the build directory [ 214s] before calling debuild or the application [ 214s] specified via --git-builder. [ 214s] Exported environment variables are: GBP_GIT_DIR (the [ 214s] repository the package is being built from), [ 214s] GBP_BUILD_DIR (the build dir). [ 214s] --git-[no-]build [ 214s] Enable builder. Note: --git-no-build causes the [ 214s] postbuild hook to be disabled, too. [ 214s] --git-[no-]hooks [ 214s] Enable running all (cleaner, postexport, prebuild, postbuild, and [ 214s] posttag) hooks. Note: the --git-builder command is [ 214s] not affected by this option. [ 214s] --git-debian-tag=TAG-FORMAT [ 214s] use this tag format when tagging Debian versions, default is [ 214s] debian/%(version)s [ 214s] --git-upstream-tag=TAG-FORMAT [ 214s] use this tag format when looking for tags of upstream versions, [ 214s] default is upstream/%(version)s. [ 214s] --git-debian-tag-msg=tag-msg-format [ 214s] use this tag message format when signing Debian versions, [ 214s] default is %(pkg)s Debian release %(version)s--git-force-create [ 214s] Force creation of an orig tarball (overwriting a pre-existing one if [ 214s] present) [ 214s] --git-no-create-orig [ 214s] Don't try to create any orig tarball [ 214s] --git-overlay [ 214s] Extract orig tarball when using export-dir option (analog to [ 214s] mergeWithUpstream in svn-bp) [ 214s] --git-export-dir=DIRECTORY [ 214s] Export the current branch head (or the treeish object given via [ 214s] --git-export to DIRECTORY [ 214s] before building. [ 214s] --git-export=TREEISH [ 214s] Instead of exporting the current branch head, export the treeish [ 214s] object TREEISH. The special name [ 214s] INDEX exports the current index whereas [ 214s] the special name WC exports the current [ 214s] working copy as is. [ 214s] --git-upstream-tree=[TAG|BRANCH|TREEISH] [ 214s] How to find the upstream sources used to generate the tarball. [ 214s] TAG looks at a tag corresponding to the [ 214s] version in the changelog. BRANCH looks at [ 214s] the upstream branch given via the [ 214s] --git-upstream-branch option. Other values are [ 214s] interpreted as treeishs. [ 214s] This doesn't have any effect if --git-pristine-tar [ 214s] is being used. [ 214s] --git-tarball-dir=DIRECTORY [ 214s] Search for original tarballs in DIRECTORY [ 214s] instead of generating them [ 214s] --git-compression=TYPE [ 214s] Specifies the upstream tarball compression type. This will be used to [ 214s] locate and build the upstream tarball if necessary. The default is [ 214s] auto which derives the compression type [ 214s] from the pristine-tar branch if available and falls back to gzip [ 214s] otherwise. Other options are gzip, [ 214s] bzip2, lzma and [ 214s] xz. [ 214s] --git-compression-level=LEVEL [ 214s] Specifies the upstream tarball compression level if an upstream [ 214s] tarball needs to be built. [ 214s] --git[-no]-purge [ 214s] Purge (remove) temporary build directory after build [ 214s] --git-dont-purge [ 214s] Deprecated, use --git-no-purge instead. [ 214s] --git-tag-only [ 214s] don't build, only tag and run post-tag hooks [ 214s] --git-retag [ 214s] don't fail tag operations if a tag with the same version already [ 214s] exists [ 214s] --git-pristine-tar [ 214s] Use pristine-tar when generating the upstream tarball if it doesn't [ 214s] exist. [ 214s] --git-pristine-tar-commit [ 214s] Commit the pristine-tar delta to the pristine-tar branch if a new [ 214s] tarball was generated and the pristine-tar data isn't already there. [ 214s] EXAMPLES Build a Debian package using git pbuilder which in turn invokes [ 214s] cowbuilder. Instruct cowbuilder to build within a Wheezy chroot for [ 214s] i386. [ 214s] gbp buildpackage --git-pbuilder --git-arch=i386 --git-dist=wheezy [ 214s] Note that the above needs a cowbuilder chroot already. This can be [ 214s] created using: [ 214s] DIST=wheezy ARCH=i386 git pbuilder create [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details. All options in the config files are specified without the 'git-' prefix. [ 214s] SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] git-pbuilder1, [ 214s] cowbuilder8, [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Guido Guenther agx@sigxcpu.org [ 214s] agx@sigxcpu.org [ 214s] GuidoGuenthergbp-import-dsc1git-import-dscgbp-import-dscImport Debian packages into a Git repositorygbp import-dsc--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--allow-same-versions--author-date-is-committer-date--author-is-committer--debian-branch=branch_name--debian-tag=tag-format--download--filter=pattern--keyid=gpg-keyid--[no-]create-missing-branches--[no-]pristine-tar--[no-]sign-tags--skip-debian-tag=--upstream-branch=branch_name--upstream-tag=tag-formatdebian-source.dscgbp import-dscoptions--download--[no-]allow-unauthenticatedURLsource-packageDESCRIPTION gbp import-dsc imports a Debian source package into a Git repository, [ 214s] notes the package version in the commit logs, and commits the change. All [ 214s] information, including package name, version, Debian diffs, and upstream [ 214s] source is automatically detected from the source package. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --upstream-branch=branch_name [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream. [ 214s] --debian-branch=branch_name [ 214s] The branch in the Git repository the debian sources are put [ 214s] onto. Default is master. [ 214s] --[no-]sign-tags [ 214s] GPG sign all created tags [ 214s] --keyid=gpg-keyid [ 214s] use this keyid for gpg signing tags [ 214s] --debian-tag=tag-format [ 214s] use this tag format when tagging Debian versions, [ 214s] default is debian/%(version)s [ 214s] --upstream-tag=tag-format [ 214s] use this tag format when tagging upstream versions, [ 214s] default is upstream/%(version)s [ 214s] --skip-debian-tag [ 214s] Don't create Debian tag after importing the Debian patch. This can be [ 214s] useful if you already created a package but want to further work on [ 214s] it after importing it into git. [ 214s] --filter=pattern [ 214s] filter out files glob-matching pattern. Can be given multiple times. [ 214s] --pristine-tar [ 214s] generate pristine-tar delta file [ 214s] --download [ 214s] Download the source package instead of looking for it in the local [ 214s] file system. The argument can either be a [ 214s] source-package name or an [ 214s] URL. The former uses apt-get to download [ 214s] the source while the later uses dget. [ 214s] --allow-unauthenticated [ 214s] Whether to skip signature verification on downloads. [ 214s] --allow-same-version [ 214s] Allow to import a package with the same debian version. [ 214s] --author-is-committer [ 214s] When importing the Debian patch, use the author identity as [ 214s] committer identity. [ 214s] --author-date-is-committer-date [ 214s] When importing the Debian patch, use the author date as [ 214s] committer date. [ 214s] Git will subtly misbehave if the committer date of a commit is not [ 214s] later than or equal to all its parents. [ 214s] [ 214s] --[no-]create-missing-branches [ 214s] Create missing upstream and debian branch if missing. [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] apt-get1, [ 214s] dget1, [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Guido Guenther agx@sigxcpu.org [ 214s] agx@sigxcpu.org [ 214s] GuidoGuenthergbp-import-dscs1git-import-dscsgbp-import-dscsImport multiple versions of a Debian source packages into a Git repositorygbp import-dscsoptionsgit-import-dsc optionspkg_1.dscpkg_2.dsc...orgbp import-dscs--debsnapoptionsgit-import-dsc optionspackageDESCRIPTION gbp import-dscs imports several versions of a Debian source package into [ 214s] a Git repository. To do so it sorts the packages by their versions first [ 214s] and then imports them via calling gbp import-dsc on each package. [ 214s] If the current directory isn't a Git repository already the repository is [ 214s] created in a subdir of the current working directory, named after the first [ 214s] imported package, otherwise the Git repository in the current working [ 214s] directory is being used. This allows for incremental imports. [ 214s] OPTIONS--debsnap [ 214s] Fetch snapshots from snapshots.debian.org using debsnap.--ignore-repo-config [ 214s] Ignore gbp.conf files stored in the git [ 214s] repository itself. This can be useful to ignore branch informations and other [ 214s] options shipped in the package source. All other options are passed on verbatim to gbp import-dsc. [ 214s] SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp-import-orig1git-import-origgbp-import-origImport an upstream source into a git repositorygbp import-orig--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--upstream-version=version--[no-]merge--upstream-branch=branch_name--debian-branch=branch_name--[no-]create-missing-branches--upstream-vcs-tag=tag_name--[no-]sign-tags--keyid=gpg-keyid--upstream-tag=tag-format--filter=pattern--[no-]pristine-tar--[no-]filter-pristine-tar--[no-]symlink-orig--postimport=cmd--[no-]interactiveupstream-source--uscanDESCRIPTION gbp import-orig imports upstream-source into [ 214s] the Git repository. upstream-source can either [ 214s] be a gzip, bzip2, lzma or xz compressed tar archive, a zip archive or an [ 214s] already unpacked source tree. If it is already of the form [ 214s] package-name_version.orig.tar.gz, the version [ 214s] information is read from the tarball's filename otherwise it can be given [ 214s] on the command line via --upstream-version. If the source [ 214s] package name or version can't be determined gbp import-orig will prompt [ 214s] for it unless --no-interactive is given. [ 214s] The sources are placed on the upstream branch (default: [ 214s] upstream), tagged and merged onto the debian [ 214s] branch (default: master). [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --upstream-version=version-uversion The upstream version number [ 214s] --[no-]merge Merge the upstream branch to the debian branch after import [ 214s] --upstream-branch=branch_name [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream. [ 214s] --debian-branch=branch_name [ 214s] The branch in the Git repository the Debian package is being [ 214s] developed on, default is master. After [ 214s] importing the new sources on the upstream branch, gbp import-orig [ 214s] will try to merge the new version onto this branch. [ 214s] --[no-]create-missing-branches [ 214s] Create missing upstream branch if it does not exist. [ 214s] --upstream-vcs-tag=tag_name [ 214s] Add tag_name as additional parent to the [ 214s] commit of the upstream tarball. Useful when upstream uses git and you [ 214s] want to link to it's revision history. [ 214s] --[no-]sign-tags [ 214s] GPG sign all created tags [ 214s] --keyid=gpg-keyid [ 214s] use this keyid for gpg signing tags [ 214s] --upstream-tag=tag-format [ 214s] use this tag format when tagging upstream versions, [ 214s] default is upstream/%(version)s [ 214s] --import-msg=msg-format [ 214s] use this format string for the commit message when importing upstream [ 214s] versions, default is [ 214s] Imported Upstream version %(version)s [ 214s] --filter=pattern [ 214s] filter out files glob-matching pattern. Can be given multiple times. [ 214s] --[no-]pristine-tar [ 214s] generate pristine-tar delta file [ 214s] --[no-]filter-pristine-tar [ 214s] if using a filter also filter the files out of the tarball [ 214s] passed to pristine-tar [ 214s] --[no-]symlink-orig Whether to create and keep a symlink from the upstream tarball [ 214s] to a Debian policy conformant upstream tarball name located in [ 214s] ../. [ 214s] This is a good idea if not using pristine-tar [ 214s] since it avoids creating a new tarball with a different md5sum. [ 214s] --postimport=cmd run cmd after the import. [ 214s] --uscan Use uscan to fetch new upstream version. [ 214s] --[no-]interactive Run command interactively, i.e. ask package name and version if [ 214s] needed. [ 214s] --[no-]interactive Run command interactively, i.e. ask package name and version if [ 214s] needed. [ 214s] EXAMPLES Download and import a new upstream version using the informantion from debian/watch [ 214s] gbp import-orig --uscan [ 214s] After downloading an upstream tarball by hand import it [ 214s] gbp import-orig ../upstream-tarball-0.1.tar.gz [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Guido Guenther agx@sigxcpu.org [ 214s] agx@sigxcpu.org [ 214s] GuidoGuenthergbp-dch1git-dch;gbp-dch;Generate the Debian changelog from git commit messagesgbp dch--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--debian-branch=branch_name--debian-tag=tag-format--upstream-tag=tag-format--ignore-branch--snapshot--release--auto--since=commitish--new-version=version--bpo--nmu--qa--team--distribution=name--force-distribution--urgency=level--[no-]full--[no-]meta--meta-closes=bug-close-tags--snapshot-number=expression--id-length=number--git-log=git-log-options--[no-]git-author--[no-]multimaint--[no-]multimaint-merge--spawn-editor=[always|snapshot|release]--commit-msg=msg-format--commit--customizations=customization-file[path1 path2]DESCRIPTION gbp dch reads git commit messages and generates the Debian changelog from [ 214s] it. If no arguments are given gbp dch starts from the last tagged Debian [ 214s] package version up to the current tip of the current branch. If the [ 214s] distribution of the topmost section in [ 214s] debian/changelog is UNRELEASED [ 214s] the changelog entries will be inserted into this section. Otherwise a new [ 214s] section will be created. [ 214s] If --auto is given gbp dch tries to guess the [ 214s] last Git commit documented in the changelog - this only works in snapshot [ 214s] mode. Otherwise --since can be used to tell gbp dch [ 214s] at which point it should start in the Git history. [ 214s] The additional path arguments can be used to restrict the repository paths [ 214s] gbp dch looks at. Setting path to [ 214s] debian/ is a good choice if upstream uses Git and [ 214s] all Debian packaging changes are restricted to the [ 214s] debian/ subdir. In more sophisticated cases [ 214s] (like backports) you can use --git-log to restrict the [ 214s] generated changelog entries further. E.g. by using [ 214s] --git-log="--author=Foo Bar". [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --debian-branch=branch_name [ 214s] The branch in the Git repository the Debian package is being [ 214s] developed on, default is master. [ 214s] --ignore-branch [ 214s] Don't check if the current branch matches [ 214s] debian-branch. [ 214s] --debian-tag=tag-format [ 214s] tag format used, when tagging debian versions, [ 214s] default is debian/%(version)s [ 214s] --since=committish [ 214s] Start reading commit messages at [ 214s] committish. [ 214s] --auto, [ 214s] -a Guess the last commit documented in the changelog from the [ 214s] snapshot banner (or from the last tag if no snapshot banner exists). [ 214s] --[no-]meta Parse meta tags like Closes:, [ 214s] Thanks: and Git-Dch:. See META TAGS [ 214s] below. [ 214s] --meta-closes=bug-close-tags [ 214s] What meta tags to look for to generate bug-closing changelog entries. [ 214s] The default is 'Closes|LP' to support Debian and Launchpad. [ 214s] --[no-]full [ 214s] Include the full commit message in the changelog output. [ 214s] --snapshot, [ 214s] -S Create a snapshot release entry. This adds a snapshot release [ 214s] number and a warning banner to the changelog entry. The release [ 214s] version number is being auto incremented with every new snapshot [ 214s] release to avoid packages downgrades during snapshot testing. [ 214s] --snapshot-number=expression [ 214s] Python expression that gets eval()ed to the new snapshot number. [ 214s] --release, [ 214s] -R Remove any snapshot release banners and version suffixes, set [ 214s] the current distribution to unstable and [ 214s] open the changelog for final tweaking. [ 214s] --new-version=version, [ 214s] -N version [ 214s] Add a new changelog section with version [ 214s] newversion. Together with [ 214s] --snapshot the snapshot number will be appended to [ 214s] newversion. [ 214s] --team [ 214s] Create a Team upload changelog entry. [ 214s] --bpo [ 214s] Increment the Debian release number for an upload to backports, and [ 214s] add a backport upload changelog comment. [ 214s] --nmu [ 214s] Increment the Debian release number for a non-maintainer upload. [ 214s] --qa [ 214s] Increment the Debian release number for a Debian QA Team upload, and [ 214s] add a QA upload changelog comment. [ 214s] --distribution=name [ 214s] Set the distribution field to name. [ 214s] --force-distribution [ 214s] Force the distribution specified with --distribution [ 214s] to be used, even if it doesn't match the list of known distributions. [ 214s] --urgency=level [ 214s] Set the urgency field to level. [ 214s] --git-log=git-log-options [ 214s] Options passed on verbatim to git-log(1). [ 214s] --id-length=N [ 214s] Include N digits of the commit id in the [ 214s] changelog entry. Default is to not include any commit ids at all. [ 214s] --ignore-regex=regex [ 214s] Ignore commit lines matching regex [ 214s] when generating the changelog. [ 214s] --git-author [ 214s] Use user.name and user.email from [ 214s] git-config(1) for changelog trailer. [ 214s] --[no-]multimaint-merge [ 214s] Merge commits by maintainer. [ 214s] --spawn-editor=[always|snapshot|release] [ 214s] Whether to spawn an editor: always, when doing snapshots or when [ 214s] doing a release. [ 214s] --commit-msg=msg-format [ 214s] use this format string for the commit message when committing the [ 214s] generated changelog file (when --commit is given). [ 214s] Default is [ 214s] Update changelog for %(version)s release [ 214s] --commit [ 214s] Commit the generated changelog. [ 214s] --customizations=customization-file [ 214s] Load Python code from customization-file. [ 214s] At the moment, the only useful thing the code can do is define a [ 214s] custom format_changelog_entry() function. [ 214s] --customizations=customization-file [ 214s] Load Python code from customization-file. [ 214s] At the moment, the only useful thing the code can do is define a [ 214s] custom format_changelog_entry() function. [ 214s] Snapshot mode Snapshot mode can be used for quick test and install cycles without [ 214s] having to worry about version numbers or changelog entries. [ 214s] When using --snapshot or -S gbp dch [ 214s] uses a pseudo header in the Debian changelog to remember the last git [ 214s] commit it added a changelog entry for. It also sets a version number [ 214s] ending in [ 214s] ~<snaspshotnumber>.gbp<commitid>. [ 214s] It automatically increments the snapshot number on subsequent invocations [ 214s] of gbp dch -S so that later snapshots automatically [ 214s] have a higher version number. To leave snapshot mode invoke gbp dch [ 214s] with the --release option. This removes the pseudo [ 214s] header and unmangles the version number so the released version has a [ 214s] higher version number than the snapshots. [ 214s] META TAGS Additional to the above options the formatting of the commit message [ 214s] in debian/changelog can be modified by special tags [ 214s] (called Meta Tags) [ 214s] given in the git commit message. Meta Tag processing can be activated via [ 214s] the --meta option. The tags must start at the first column of [ 214s] a commit message but can appear on any line. [ 214s] They are of the form Tagname: [ 214s] value. Valid Meta Tags are: [ 214s] Git-Dch: action [ 214s] Supported actions are: Ignore which will [ 214s] ignore this commit when generating [ 214s] debian/changelog, [ 214s] Short which will only use the description [ 214s] (the first line) of the commit message when generating the changelog [ 214s] entry (useful when --full is given) and [ 214s] Full which will use the full commit [ 214s] message when generating the changelog entry (useful when [ 214s] --full is not given). [ 214s] Thanks: msg [ 214s] Add a thanks message after the commit message. [ 214s] Closes: bugnumber [ 214s] Indicate in the debian/changelog that the bug [ 214s] was closed by this commit. See the --meta-closes on [ 214s] how to extend this for other bugtrackers. [ 214s] The following git commit message: [ 214s] Document meta tags [ 214s] [ 214s] so one doesn't have to consult the manual [ 214s] [ 214s] Git-Dch: Short [ 214s] Closes: #636088 [ 214s] Thanks: Raphaël Hertzog for the suggestion [ 214s] Results in this debian/changelog entry: [ 214s] * Document meta tags. [ 214s] Thanks to Raphaël Hertzog for the suggestion (Closes: #636088) [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] Cl2vcs, [ 214s] AUTHOR Guido Guenther agx@sigxcpu.org [ 214s] agx@sigxcpu.org [ 214s] GuidoGuenthergbp-clone1gbp-cloneClone a repository from remotegbp clone--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--all--[no-]pristine-tar--debian-branch=branch_name--packaging-branch=branch_name--upstream-branch=branch_name--depth=depthremote_uriDESCRIPTION gbp clone clones a remote repository and sets up tracking branches for [ 214s] the debian, upstream and [ 214s] pristine-tar branches. This way you can easily update [ 214s] later using gbp pull. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --all [ 214s] Track all branches, not only debian [ 214s] and upstream.--debian-branch=branch_name [ 214s] The branch in the Git repository the Debian package is being [ 214s] developed on, default is master.--packaging-branch=branch_name [ 214s] The branch the packaging is being maintained on. [ 214s] Alternative to the --debian-branch option.--upstream-branch=branch_name [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream.--depth=depth [ 214s] Git history depth, for creating shallow git clones.--pristine-tar [ 214s] Track pristine tar branch.CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp-config1gbp-configQuery configuration valuesgbp config--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEMEcommand.optioncommandDESCRIPTION gbp config prints values from the configuration files. It interpolates the [ 214s] value for option of [ 214s] command. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] EXIT CODES When gbp config finishes it indicates success or failure with its exit code: [ 214s] 0Success.1Failed to parse command line2The value did not existEXAMPLESPrint the value upstream-branch that gbp buildpackage [ 214s] would use: $ gbp config buildpackage.upstream-branch [ 214s] buildpackage.upstream-branch=upstream [ 214s] Print the values of all of gbp buildpackages options $ gbp config buildpackage [ 214s] buildpackage.upstream-branch=upstream [ 214s] buildpackage.debian-branch=master [ 214s] ... [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp-pull1gbp-pullSafely update a repository from remotegbp pull--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--force=[merge|clean]--all--redo-pq--[no-]pristine-tar--ignore-branch--debian-branch=branch_name--packaging-branch=branch_name--upstream-branch=branch_name--depth=depthDESCRIPTION gbp pull updates the debian, [ 214s] upstream and pristine-tar [ 214s] branches from a remote repository in one go. It checks if the update is safe (would [ 214s] result in a fast-forward merge) and aborts otherwise. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --force=[merge|clean]Force a branch update even if this results in a non fast [ 214s] forward update. [ 214s] merge does a git-merge. [ 214s] clean checks out a clean copy from upstream. [ 214s] using clean [ 214s] makes you lose your modifications.--allUpdate all remote-tracking branches that have identical name in the [ 214s] remote repository.--redo-pqalso rebuild the corresponding patch-queue using gbp pq. [ 214s] This drops the patch-queue branch if it exists.--ignore-branch [ 214s] Don't care if we're on a branch or in detached head state.--debian-branch=branch_name [ 214s] The branch in the Git repository the Debian package is being [ 214s] developed on, default is master.--packaging-branch=branch_name [ 214s] The branch the packaging is being maintained on. [ 214s] Alternative to the --debian-branch option.--upstream-branch=branch_name [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream.--depth=depth [ 214s] Git history depth, for deepening shallow git clones.--pristine-tar [ 214s] Whether to update the pristine-tar branch too.EXIT CODES When gbp pull finishes it indicates success or failure with it's exit code: [ 214s] 0Success.1An error occured during the pull, see the printed error message for details.2At least one branch couldn't be fast forwarded.CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp-pq1gbp-pqManage quilt patches on patch queue branches in gitgbp pq--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--[no-]patch-numbers--topic=topic--time-machine=num--[no-]drop--forcedropexportimportrebaseswitchDESCRIPTION gbp pq helps one to manage quilt patches in Debian packages that are [ 214s] maintained with gbp. This is especially useful with packages using the [ 214s] 3.0 (quilt) source format. With gbp pq you can maintain the quilt patches [ 214s] that should be applied to a package on a separate branch called patch-queue [ 214s] branch. So if your Debian package lives on [ 214s] master the associated patch-queue branch will be [ 214s] called patch-queue/master. [ 214s] See [ 214s] for example workflows. [ 214s] ACTIONSimport [ 214s] Create a patch queue branch from quilt patches in debian/patches/ [ 214s] that are listed in debian/patches/series. The patches must apply [ 214s] without fuzz. [ 214s] export [ 214s] Export the patches on the patch-queue branch associated to the [ 214s] current branch into a quilt patch series in debian/patches/ and [ 214s] update the series file. [ 214s] rebase [ 214s] Switch to the patch-queue branch associated to the current branch and [ 214s] rebase it against the current branch. [ 214s] drop [ 214s] Drop (delete) the patch queue associated to the current branch. So if [ 214s] you're on branch foo this would drop [ 214s] branch patch-queue/foo. [ 214s] apply [ 214s] Add a single patch to the patch-queue similar to using [ 214s] git-am. Use --topic if you want [ 214s] the patch to appear in a separate subdir when exporting the patch queue [ 214s] using export. This can be used to separate upstream [ 214s] pathes from debian specific patches. [ 214s] switch [ 214s] Switch to the patch-queue branch if on the base branch and switch [ 214s] to base branch if on patch-queue branch. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --[no-]patch-numbers [ 214s] Whether the patch files should start with a number or not. [ 214s] --topic=topic [ 214s] Topic to use when importing a single patch [ 214s] --time-machine=NUM [ 214s] When importing a patch queue fails, go back commit by commit on the [ 214s] current branch to check if the patch-queue applies there. Do this at [ 214s] most NUM times. This can be useful if the [ 214s] patch-queue doesn't apply to the current branch HEAD anymore, e.g. [ 214s] after importing a new upstream version. [ 214s] --[no-]dropWhether to drop (delete) the patch queue branch after [ 214s] a succesful export--forceIn case of import even import if the branch already [ 214s] existsTAGS When exporting patches from a patch-queue branch gbp pq will look at the [ 214s] patch header for special tags it recognizes. All tags need to start at the [ 214s] first column and require at least one whitespace after the colon. [ 214s] Gbp[-Pq]: Ignore [ 214s] Ignores the commit, no patch is generated out of it. [ 214s] Gbp[-Pq]: Topic topic [ 214s] Moves the patch into a subdir called topic [ 214s] when running gbp pq export This allows for some [ 214s] structure below debian/patches. [ 214s] Gbp-Pq-Topic: topic [ 214s] Deprecated: use Gbp[-Pq]: Topic [ 214s] topic instead. [ 214s] SEE ALSO , [ 214s] dpkg-source1, [ 214s] quilt1, [ 214s] [ 214s] AUTHOR Guido Guenther agx@sigxcpu.org [ 214s] agx@sigxcpu.org [ 214s] GuidoGuenthergbp-create-remote-repo1gbp-create-remote-repoCreate remote repositoriesgbp create-remote-repo--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--remote-url-pattern=url-pattern--remote-name=name--template-dir=directory--remote-config=config--[no-]pristine-tar--debian-branch=branch_name--upstream-branch=branch_name--[no-]trackDESCRIPTION gbp create-remote-repo creates a repository at a remote location via ssh [ 214s] and pushes the local repository into it. It then sets up remote branch [ 214s] tracking so you can use gbp pull to update your repository from there. [ 214s] Before performing any action on the remote location it will print the [ 214s] remote URL and ask for confirmation. [ 214s] Note: By default the remote repositories are created in the collab-maint repository on git.debian.org. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --remote-url-pattern=pattern [ 214s] Where to create the remote repository. The part [ 214s] %(pkg)s will be replaced by the package name. [ 214s] --remote-name=name [ 214s] What name git will use when refering to that repository, e.g. [ 214s] 'origin'.--template-dir=directory [ 214s] Template directory to pass to git init on the remote [ 214s] side. This can be used to customize the remote repository, e.g. to set up hooks. [ 214s] --remote-config=config [ 214s] Name of a config file section in gbp.conf [ 214s] that specifies the above paramters. See [ 214s] manpage for details. [ 214s] --debian-branch=branch_name [ 214s] The branch in the Git repository the Debian package is being [ 214s] developed on, default is master.--upstream-branch=branch_name [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream.--pristine-tar [ 214s] Whether to push the pristine tar branch.--[no-]track [ 214s] Whether to set up branch tracking for the debian, upstream and [ 214s] pristine-tar branches.CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] [ 214s] AUTHORGuido Guenther agx@sigxcpu.org agx@sigxcpu.org [ 214s] GuidoGuenthergbp.conf5gbp.confGbp configuration file/etc/git-buildpackage/gbp.confsystem wide~/.gbp.confper user.gbp.confper branch, can be published with the [ 214s] repository (deprecated)debian/gbp.confper branch, can be published with the [ 214s] repository.git/gbp.confper repositoryDESCRIPTION The gbp.conf provides default global options and specific options [ 214s] for gbp commands. All have the same format and are parsed in the above order. The [ 214s] file consists of several sections, one for each command. Comments start with a hash sign [ 214s] (#). The generic file syntax is: [ 214s] [DEFAULT] [ 214s] # This is section for global settings. Affects all commands [ 214s] key = value [ 214s] [ 214s] [<command>] [ 214s] # Specific sections for each command, like gbp buildpackage [ 214s] key = value [ 214s] [ 214s] [remote-config <name>] [ 214s] # Specific sections for a remote configuration. This can be used several [ 214s] # times to set up remote configuration for gbp-create-remote-repo [ 214s] key = valueFor backwards compatibility sections starting with git- or [ 214s] gbp- are still supported. [ 214s] key=value pairs of the command sections reflect the command line [ 214s] options and their settings. For example [ 214s] manualpage contains the --git-export-dir=diirectory [ 214s] option which can be turned into configuration file setting by dropping the [ 214s] --git prefix with: [buildpackage] [ 214s] export-dir = directoryNotice that some option can take Python like lists. [ 214s] For example the commmand has the [ 214s] --filter=pattern option which can [ 214s] be truned into a configuration file option like this: [import-orig] [ 214s] filter = [ '.svn', '.hg' ]Boolean options can be either True or False. For example [ 214s] ; has the --pristine-tar and [ 214s] --no-pristine-tar options which translate to: [import-orig] [ 214s] pristine-tar = Trueand [import-orig] [ 214s] pristine-tar = Falserespectively.To see the current set of values that would be applied after parsing the [ 214s] configuration files run the command with --help and check it's [ 214s] output. gbp import-dscs and git-pbuilder [ 214s] can't be configured via gbp.conf. can additionally parse remote site [ 214s] configurations from gbp.conf. For example a configration like:[remote-config pkg-libvirt] [ 214s] # Location of the repository [ 214s] remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s [ 214s] # Template dir to passed to git-init [ 214s] template-dir = /srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-templateCan be used to create remote repositories for the pkg-libvirt project using:gbp-create-remote-repo --remote-config=pkg-libvirtThis can be useful if you're often creating new remote repositores for [ 214s] different projects.EXAMPLESAn example set up for packaging work: # $HOME/.gbp.conf [ 214s] [ 214s] [DEFAULT] [ 214s] pristine-tar = True [ 214s] cleaner = fakeroot debian/rules clean [ 214s] [ 214s] [buildpackage] [ 214s] export-dir = ../build-area/ [ 214s] [ 214s] [import-orig] [ 214s] dch = False [ 214s] filter = .svn [ 214s] filter = .hg [ 214s] filter = .bzr [ 214s] filter = CVS [ 214s] filter = debian/* [ 214s] filter = */debian/* [ 214s] filter-pristine-tar = True [ 214s] [ 214s] [import-dsc] [ 214s] filter = [ [ 214s] 'CVS', [ 214s] '.cvsignore', [ 214s] '.hg', [ 214s] '.hgignore' [ 214s] '.bzr', [ 214s] '.bzrignore', [ 214s] '.gitignore' [ 214s] ] [ 214s] [ 214s] # End of fileENVIRONMENTGBP_CONF_FILESColon separated list of files to parse. The default is [ 214s] the above list of configuration files.FILES See See /etc/git-buildpackage/gbp.conf for an example. [ 214s] SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] , [ 214s] The Git-Buildpackage Manual [ 214s] AUTHORSGuido Guenther agx@sigxcpu.orgThis manual page is based on a POD version by Jari Aalto jari.aalto@cante.net. [ 214s] Released under license GNU GPL version 2 or (at your option) any later. [ 214s] version. [ 214s] Copyright git-buildpackage, all associated scripts and programs, this manual, [ 214s] and all build scripts are Copyright © 2006-2014 Guido Guenther. [ 214s] This program is free software; you can redistribute it and/or modify [ 214s] it under the terms of the GNU General Public License as published by [ 214s] the Free Software Foundation; Version 2 of the License. [ 214s] This program is distributed in the hope that it will be useful, [ 214s] but WITHOUT ANY WARRANTY; without even the implied warranty of [ 214s] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the [ 214s] GNU General Public License for more details. [ 214s] You should have received a copy of the GNU General Public License [ 214s] along with this program; if not, write to the Free Software [ 214s] Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA [ 214s] Building RPM Packages with git-buildpackage-rpmMarkusLehtonenmarkus.lehtonen@linux.intel.comVersion: 0.9.9-tizen20180912Introduction Git-buildpackage is a Debian [ 214s] toolset for maintaining and building packages in/from git repositories. [ 214s] The still experimental RPM variants of the tool, extend the support [ 214s] from Debian-only to building and maintaining RPM packages, too. [ 214s] The documentation of git-buildpackage-rpm here reflects the the [ 214s] Debian git-buildpackage documentation [ 214s] [ 214s] The RPM versions of the tools can in their current state [ 214s] do basically all the same tasks as the Debian versions, except for changelog generation. [ 214s] However, the philosophy is somewhat different in some parts. The RPM tools [ 214s] read the .spec file instead of changelog in determining packaging [ 214s] information (version number, name etc). Another clear difference is [ 214s] that gbp buildpackage-rpm will always build in a separate build [ 214s] directory whereas gbp buildpackage (the Debian) tool builds in the [ 214s] git working dir, by default. [ 214s] Third, conceptual, difference (for non-native packages) is that you may [ 214s] have packaging files in an orphan branch, without development sources: [ 214s] i.e. you develop code in 'patch-queue' branch that doesn't contain any [ 214s] packaging files, and, do 'pq-rpm export' to 'packaging' branch that only [ 214s] contains packaging files (.spec file, patches etc.) but no sources. [ 214s] The Debian/RPM tool equivalence is: [ 214s] gbp buildpackage -> RPM: gbp buildpackage-rpmgbp import-dsc -> RPM: gbp import-srpmgbp import-orig -> RPM: gbp import-orig-rpmgbp pq -> RPM: gbp pq-rpmgbp clone -> RPM: gbp clone (the same tool)gbp pull -> RPM: gbp pull (the same tool)gbp dch -> RPM: not availablegbp import-dscs -> RPM: not available [ 214s] RPM Repository Layout The required repository layout is similar to Debian: basically the only [ 214s] requirement is that non-native packages must have clean upstream sources [ 214s] in a separate branch. Other branches are: [ 214s] packaging-branch contains packaging files (spec [ 214s] and source files, e.g. patches, needed by rpmbuild, except for the orig [ 214s] tarball). This branch may contain the development sources as well [ 214s] (always true for native packages). [ 214s] upstream-branch contains upstream sources. [ 214s] This can either be a branch you import to or a branch of an upstream [ 214s] repository you pull from. [ 214s] pristine-tar-branch contains pristine-tar data to [ 214s] recreate the original upstream tarball from the upstream-branch. [ 214s] patch-queue-branch(es) are related to [ 214s] packaging-branch(es). These are also called the [ 214s] development branhces in the RPM tools. [ 214s] The development/patch-queue branch is the upstream [ 214s] plus the patches from packaging branch applied. In RPM tools the [ 214s] default branch name of the development/patch-queue branch is [ 214s] development/<packaging-branch-name>. [ 214s] RPM Workflow The basic workflow is very similar to Debian: [ 214s] Import a package via gbp import-srpm OR clone from the [ 214s] distro git with gbp clone if the package is already maintained with [ 214s] gbp buildpackage-rpm. [ 214s] Develop, test, commit changes.Once satisfied you can build the final package with [ 214s] gbp buildpackage-rpm (optionally with --git-tag to create a tag in [ 214s] git) and push it to git server. [ 214s] Development flowDevelopment models The gbp buildpackage-rpm toolset basically supports three different [ 214s] models of package maintenance. [ 214s] Native package This means that you are the upstream, there is no separate [ 214s] upstream with which you have to sync. Basically, only [ 214s] packaging-branch is used - it contains both the source [ 214s] code and packaging files. No patches should be present as all [ 214s] changes can be directly committed to upstream (which is you). [ 214s] When building, gbp buildpackage-rpm will create the source [ 214s] tarball and copy it and the packaging to the build directory. [ 214s] Upstream package, alternative 1: packaging and sources in [ 214s] the same branch This represents somewhat Debian-style package maintenance. [ 214s] All changes (packaging and source code) are done to the same [ 214s] branch, i.e., the packaging-branch, based on the [ 214s] upstream-branch. When package is built, [ 214s] gbp buildpackage-rpm can automatically generate patches from [ 214s] upstream version to packaging branch head (one patch per commit). [ 214s] and modify the spec file accordingly. [ 214s] Upstream package, alternative 2: packaging and sources in [ 214s] separate branches In this model packaging files (spec and patches) are held in [ 214s] packaging-branch and upstream sources in [ 214s] upstream-branch. [ 214s] Your code development is done on the patch-queue-branch, [ 214s] based on the upstream-branch, which only contains source [ 214s] code but no packaging files. When building the package, [ 214s] gbp pq-rpm tool is used to export patches from the patch queue [ 214s] branch to the packaging branch and edit the spec file accordingly. [ 214s] Finally, gbp buildpackage-rpm will create the upstream source [ 214s] tarball and export it and the packaging files to the build [ 214s] directory, and, build the RPM package. [ 214s] Starting from scratch with a non-native package In this case, you most probably want to package software not yet [ 214s] found in your distro. First, create an empty repository: [ 214s] $ mkdir mypackage [ 214s] $ cd mypackage [ 214s] $ git init [ 214s] [ 214s] Then, import the upstream sources, create the packaging/development [ 214s] branch and add the rpm packaging files. You have two choices: [ 214s] packaging files and development sources in the same branch [ 214s] $ git-import-orig-rpm ../mypackage.tar.gz [ 214s] # Optionally (recommended): add gbp.conf [ 214s] $ vim .gbp.conf && git add .gbp.conf && git commit -m"Add gbp.conf" [ 214s] # Add packaging files to source tree under subdir 'packaging' [ 214s] $ mkdir packaging && cd packaging [ 214s] $ vim mypackage.spec [ 214s] $ git add . [ 214s] $ git commit -m"Add packaging files" [ 214s] development sources and packaging files in separate branches [ 214s] $ git-import-orig-rpm --no-merge ../mypackage.tar.gz [ 214s] # Optionally (recommended): add gbp.conf [ 214s] $ vim .gbp.conf && git add .gbp.conf && git commit -m"Add gbp.conf" [ 214s] # Add packaging files (to root of master branch) [ 214s] $ vim mypackage.spec [ 214s] $ git add . [ 214s] $ git commit -m"Add packaging files" [ 214s] Converting an existing git repository of a non-native package In this case, you already have a git repository containing the [ 214s] upstream source, but it was created neither with gbp clone nor [ 214s] gbp import-srpm. [ 214s] You need to have a separate branch for upstream sources. [ 214s] If you already have that, you can simply rename that branch to the [ 214s] default upstream-branch: [ 214s] $ git branch -m my-old-upstream-branch upstream [ 214s] [ 214s] OR just add the name of your upstream branch to gbp.conf. [ 214s] Then, you just create a packaging/development branch(es) with git and [ 214s] add packaging files to the packaging branch. If you want to maintain [ 214s] sources and packaging in the same branch [ 214s] () [ 214s] do something like: [ 214s] $ git checkout -b master upstream [ 214s] # Optionally (recommended): add gbp.conf [ 214s] $ vim .gbp.conf && git add .gbp.conf && git commit -m"Add gbp.conf" [ 214s] # Add packaging files to source tree, add and commit the packaging files [ 214s] # ... [ 214s] [ 214s] If you want to maintain development sources and packaging in separate [ 214s] branches [ 214s] (): [ 214s] $ git checkout --orphan master [ 214s] $ rm .git/index [ 214s] $ git commit --allow-empty -m"Create packaging branch" [ 214s] # Optionally (recommended): add gbp.conf [ 214s] $ vim .gbp.conf && git add .gbp.conf && git commit -m"Add gbp.conf" [ 214s] # Next, add and commit the packaging files (.spec etc) [ 214s] $ vim mypackage.spec && git add mypackage.spec && git commit -m"Add packaging files" [ 214s] # Now, you can create the development branch (and import possible patches) [ 214s] $ gbp pq-rpm import [ 214s] [ 214s] Building RPM packages from the Git repository The gbp buildpackage-rpm tool is used for building. [ 214s] The tool creates the source tarball and copies it and the packaging files [ 214s] to a separate build directory and builds the package there. By default, [ 214s] rpmbuild is used as the builder command. You can define a different [ 214s] builder command with the --git-builder option. [ 214s] To build the (non-native) package when on packaging-branch, [ 214s] using pristine-tar to create upstream tarball: [ 214s] $ gbp buildpackage-rpm --pristine-tar [ 214s] [ 214s] During development, if you have unclean git tree (untracked files and/or [ 214s] uncommitted changes) you may use: [ 214s] $ gbp buildpackage-rpm --git-ignore-untracked [ 214s] [ 214s] or: [ 214s] $ gbp buildpackage-rpm --git-ignore-new [ 214s] [ 214s] Git-buildpackage-rpm always builds in a separate build directory [ 214s] (./rpmbuild/ by default). You may change that and also [ 214s] build a different revision that your current branch HEAD. The revision can [ 214s] be any git "commit-ish", i.e. branch or tag name or a commit sha1. [ 214s] Git-buildpackage also supports some "special revisions", i.e. [ 214s] INDEX refer to the current index, [ 214s] WC or WC.IGNORED refer to the current working [ 214s] copy with all (even untracked and ignored) files, [ 214s] WC.TRACKED refers to the current working copy of the files [ 214s] tracked by git, [ 214s] WC.UNTRACKED refers to the current working copy of all files [ 214s] excluding ignore files. [ 214s] Some examples: [ 214s] $ gbp buildpackage-rpm --git-export-dir=/home/user/rpmbuild [ 214s] $ gbp buildpackage-rpm --git-export-dir=/home/user/rpmbuild --git-export=v1.2.3 [ 214s] $ gbp buildpackage-rpm --git-export=WC.UNTRACKED [ 214s] $ gbp buildpackage-rpm --git-export=INDEX [ 214s] $ gbp buildpackage-rpm --git-export=feature/cool-new-thing [ 214s] $ gbp buildpackage-rpm --git-export=8d55173610f [ 214s] [ 214s] Automatic patch generation When developing a non-native package with packaging and sources [ 214s] in the same branch [ 214s] (see ) [ 214s] you usually want for gbp buildpackage-rpm to automatically generate [ 214s] patches. In this mode, gbp buildpackage-rpm generates the upstream [ 214s] tarball and copies packaging files to the build dir. After that it [ 214s] generates patches from commits between upstream and the [ 214s] revision to be built, and, updates the spec file accordingly. [ 214s] Git-buildpackage-rpm also have some options to alter the patch [ 214s] generation. Build package with patch generation: [ 214s] $ gbp buildpackage-rpm --git-patch-export [ 214s] [ 214s] Ignore changes to packaging/ directory and compress patches larger [ 214s] than 100 kilobytes: [ 214s] $ gbp buildpackage-rpm --git-patch-export --git-patch-export-compress=100k --git-patch-export-ignore-path='^packaging/.*' [ 214s] [ 214s] Working with separate development branch When developing a non-native package with packaging data and source [ 214s] code in separate branches [ 214s] (see ) [ 214s] you use the gbp pq-rpm tool to handle the patches. You work on the [ 214s] source code on the development branch and then export [ 214s] the patches to the packaging branch when building the RPM package. [ 214s] Create a development (or patch-queue) branch [ 214s] by applying the patches in current packaging branch on top of the [ 214s] upstream version. This will create a new branch, e.g. [ 214s] development/master assuming your current branch is [ 214s] master. Simply: [ 214s] $ gbp pq-rpm import [ 214s] [ 214s] Now you can develop normally on the development branch (add, remove, [ 214s] rebase, amend commits). Just make sure you stay based on the correct [ 214s] upstream version, if doing git-rebase. After you're happy with your [ 214s] changes and you're ready to build an RPM package, you have to [ 214s] export the patches with gbp pq-rpm. This will change [ 214s] back to you packaging branch, generate patches from commits between [ 214s] between upstream and the HEAD of the development branch [ 214s] and update the spec file with the new patches: [ 214s] $ gbp pq-rpm export [ 214s] [ 214s] Commit the changes to packaging branch, and build. For example: [ 214s] $ git add *patch *spec [ 214s] $ git commit -a [ 214s] $ gbp buildpackage-rpm [ 214s] [ 214s] Of course you can build even without committing by using the [ 214s] --git-export=WC.UNTRACKED option of gbp buildpackage-rpm. [ 214s] Moving to a new upstream version is basically simple. Assuming you [ 214s] have imported/pulled new upstream version to your git-tree, just: [ 214s] $ git checkout master [ 214s] # Edit the spec file and change the 'Version:' tag to new upstream version [ 214s] $ vim *spec [ 214s] $ git commit *spec [ 214s] $ gbp pq-rpm rebase [ 214s] [ 214s] However, if the patches do not apply cleanly, you have to manually [ 214s] apply and resolve the patches. [ 214s] Command Reference markus.lehtonen@linux.intel.com [ 214s] MarkusLehtonengbp-buildpackage-rpm1git-buildpackage-rpmgbp-buildpackage-rpmBuild RPM packages from a Git repositorygbp buildpackage-rpm--git-[no-]ignore-new--git-[no-]ignore-untracked--git-tag--git-verbose--git-color=[auto|on|off]--git-color-scheme=COLOR_SCHEME--git-notify=[auto|on|off]--git-tmp-dir=DIRECTORY--git-vendor=VENDOR--git-upstream-branch=TREEISH--git-packaging-branch=BRANCH_NAME--git-pq-branch=BRANCH_NAME--git-ignore-branch--git-[no-]submodules--git-builder=BUILD_CMD--git-cleaner=CLEAN_CMD--git-[no-]sign-tags--git-keyid=GPG-KEYID--git-posttag=COMMAND--git-postbuild=COMMAND--git-postexport=COMMAND--git-prebuild=COMMAND--git-[no-]build--git-[no-]hooks--git-packaging-tag=TAG-FORMAT--git-upstream-tag=TAG-FORMAT--git-force-create--git-no-create-orig--git-upstream-tree=[TAG|BRANCH|TREEISH]--git-tarball-dir=DIRECTORY--git-compression-level=LEVEL--git-orig-prefix=PREFIX--git-export-dir=DIRECTORY--git-rpmbuild-builddir=DIRECTORY--git-rpmbuild-buidrootdir=DIRECTORY--git-rpmbuild-rpmdir=DIRECTORY--git-rpmbuild-sourcedir=DIRECTORY--git-rpmbuild-specdir=DIRECTORY--git-rpmbuild-srpmdir=DIRECTORY--git-export=TREEISH--git-export-only--git-packaging-dir=DIRECTORY--git-spec-file=FILEPATH--git-[no-]pristine-tar--git-[no-]pristine-tar-commit--git-tag-only--git-retag--git-[no-]patch-export--git-patch-export-rev=TREEISH--git-patch-export-compress=THRESHOLD--git-patch-export-ignore-path=REGEX--git-patch-export-squash-until=COMMITISH--git-[no-]patch-numbers--git-spec-vcs-tag=TAG_FORMATDESCRIPTION gbp buildpackage-rpm is used to build RPM packages from a Git [ 214s] repository. It is an RPM counterpart for the gbp buildpackage tool that [ 214s] is designed for building Debian packages. [ 214s] gbp buildpackage-rpm will, in order: [ 214s] Verify that it is being executed from the proper location. [ 214s] Verify that the repository doesn't contain any uncommitted source [ 214s] changes. [ 214s] Verify that it is being executed from the correct branch. [ 214s] Export packaging files to a separate build area. [ 214s] Create an orig source tarball if it doesn't exist. [ 214s] Call rpmbuild(1) (or the application [ 214s] specified via --git-builder), passing along all [ 214s] command line arguments that don't start with --git-. [ 214s] (Optionally) tag the tree after a successful build. [ 214s] (Optionally) call a post build hook - e.g. to run [ 214s] rpmlint. [ 214s] (Optionally) call a post tag hook - e.g. to push the results to a [ 214s] remote repository after creating the tag. [ 214s] OPTIONS--git-[no-]ignore-new [ 214s] Don't abort if there are uncommitted changes in the source tree or [ 214s] the current branch doesn't match the [ 214s] PACKAGING-BRANCH. [ 214s] --git-[no-]ignore-untracked [ 214s] Don't abort if there are untracked files in the source tree. [ 214s] --git-tag [ 214s] Add a git tag after a successful build. [ 214s] --git-builder=BUILD_CMD [ 214s] Use BUILD_CMD instead of [ 214s] rpmbuild -ba. [ 214s] --git-cleaner=CLEAN_CMD [ 214s] Use CLEAN_CMD. [ 214s] --git-verbose [ 214s] Verbose execution [ 214s] --git-color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --git-color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --git-notify=[auto|on|off] [ 214s] Whether to send a desktop notification after the build. [ 214s] --git-tmp-dir=DIRECTORY [ 214s] Base directory under which temporary directories are created. [ 214s] --git-vendor=VENDOR [ 214s] Distribution vendor name. [ 214s] --git-upstream-branch=BRANCH_NAME [ 214s] Branch to build the orig tarball from if [ 214s] --git-upstream-tree is set to [ 214s] BRANCH. Default is [ 214s] upstream. [ 214s] --git-packaging-branch=BRANCH_NAME [ 214s] If you're not on this branch when invoking gbp buildpackage-rpm it [ 214s] will fail. Default is master. This is done [ 214s] to make sure you don't accidentally release from a topic branch. Not [ 214s] being on this branch will be ignored when using [ 214s] --git-ignore-new. [ 214s] --git-pq-branch=BRANCH_NAME [ 214s] Name (format string) of the patch-queue/development branch. This [ 214s] makes building easier when working with separate packaging and [ 214s] development branches. [ 214s] If --git-patch-export is enabled and [ 214s] gbp buildpackage-rpm detects that the current branch has a [ 214s] patch-queue/development branch it exports the patches from there [ 214s] instead of the tip of the current branch (unless [ 214s] --git-patch-export-rev is defined, of course). [ 214s] Similarly, if the current branch is a patch-queue/development branch [ 214s] gbp buildpackage-rpm will automatically enable patch-export and [ 214s] export packaging files from the packaging branch instead of the [ 214s] current branch (unless --git-export) is defined. [ 214s] --git-ignore-branch [ 214s] Don't check if the current branch matches [ 214s] PACKAGING-BRANCH. [ 214s] --git-[no-]submodules [ 214s] Include git submodules in the orig tarball. [ 214s] --git-[no-]sign-tags [ 214s] GPG sign all created tags. [ 214s] --git-keyid=GPG-KEYID [ 214s] Use this keyid for gpg signing tags. [ 214s] --git-posttag=COMMAND [ 214s] Excecute COMMAND after tagging a new [ 214s] version. [ 214s] Exported environment variables are: GBP_TAG (the name [ 214s] of the generated tag), GBP_BRANCH (the branch the [ 214s] package was build from) and GBP_SHA1 (the sha1 of the [ 214s] commit the tag was created at). [ 214s] --git-postbuild=COMMAND [ 214s] Execute COMMAND after successful [ 214s] build. [ 214s] Exported environment variables are: GBP_CHANGES_FILE [ 214s] (the name of the generated changes file), [ 214s] GBP_BUILD_DIR (the build dir). [ 214s] --git-postexport=COMMAND [ 214s] Execute COMMAND after exporting the source [ 214s] tree. [ 214s] Exported environment variables are: GBP_GIT_DIR (the [ 214s] repository the package is being built from), [ 214s] GBP_TMP_DIR (the temporary directory where the sources [ 214s] have been initially exported). [ 214s] --git-prebuild=COMMAND [ 214s] Execute COMMAND from the build directory [ 214s] before calling rpmbuild or the application [ 214s] specified via --git-builder. [ 214s] Exported environment variables are: GBP_GIT_DIR (the [ 214s] repository the package is being built from), [ 214s] GBP_BUILD_DIR (the build dir). [ 214s] --git-[no-]build [ 214s] Enable builder. Note: --git-no-build causes the [ 214s] postbuild hook to be disabled, too. [ 214s] --git-[no-]hooks [ 214s] Enable running all (cleaner, postexport, prebuild, postbuild, and [ 214s] posttag) hooks. Note: the --git-builder command is [ 214s] not affected by this option. [ 214s] --git-packaging-tag=TAG-FORMAT [ 214s] Use this tag format when tagging released versions of the package. [ 214s] --git-upstream-tag=TAG-FORMAT [ 214s] Use this tag format when looking for tags of upstream versions, [ 214s] default is upstream/%(version)s. [ 214s] --git-force-create [ 214s] Force creation of an orig tarball (overwriting a pre-existing one if [ 214s] present). [ 214s] --git-no-create-orig [ 214s] Don't try to create any orig tarball. [ 214s] --git-export-dir=DIRECTORY [ 214s] Export the packaging files from the current branch head (or the [ 214s] treeish object given via --git-export to [ 214s] DIRECTORY before building. [ 214s] --git-rpmbuild-builddir=DIRECTORY [ 214s] --git-rpmbuild-buildrootdir=DIRECTORY [ 214s] --git-rpmbuild-rpmdir=DIRECTORY [ 214s] --git-rpmbuild-sourcedir=DIRECTORY [ 214s] --git-rpmbuild-specdir=DIRECTORY [ 214s] --git-rpmbuild-srpmdir=DIRECTORY [ 214s] Build subdirectory options for rpmbuild builder. Of these [ 214s] --git-rpmbuild-sourcedir and [ 214s] --git-rpmbuild-specdir also affects where [ 214s] gbp buildpackage-rpm exports the packaging files under the export [ 214s] directory. [ 214s] --git-export=TREEISH [ 214s] Instead of exporting the current branch head, export the treeish [ 214s] object TREEISH. The special name [ 214s] INDEX exports the current index, [ 214s] WC.TRACKED exports all files tracked by [ 214s] Git in the current working copy as is, [ 214s] WC.UNTRACKED exports all untracked files [ 214s] too whereas WC (or [ 214s] WC.IGNORED) exports all files in the [ 214s] current working directory, even ignored files. [ 214s] --git-export-only [ 214s] Only export packaging files without running builder. [ 214s] --git-packaging-dir=DIRECTORY [ 214s] Subdirectory that contains the RPM packaging files. [ 214s] --git-spec-file=FILEPATH [ 214s] Relative path to the spec file to use. Special value [ 214s] auto causes gbp buildpackage-rpm to [ 214s] search and guess. Other values cause the [ 214s] --git-packaging-dir option to be ignored: the [ 214s] directory of the spec file is used, instead. [ 214s] --git-upstream-tree=[TAG|BRANCH|TREEISH] [ 214s] How to find the upstream sources used to generate the tarball. [ 214s] TAG looks at a tag corresponding to the [ 214s] version in the changelog. BRANCH looks at [ 214s] the upstream branch given via the [ 214s] --git-upstream-branch option. Other values are [ 214s] interpreted as treeishs. [ 214s] This doesn't have any effect if --git-pristine-tar [ 214s] is being used. [ 214s] --git-tarball-dir=DIRECTORY [ 214s] Search for original tarballs in DIRECTORY [ 214s] instead of generating them. [ 214s] --git-compression-level=LEVEL [ 214s] Specifies the upstream tarball compression level if an upstream [ 214s] tarball needs to be built. [ 214s] --git-orig-prefix=PREFIX [ 214s] Prefix (directory) to be used when generating tarballs. Special value [ 214s] auto causes gbp buildpackage-rpm to [ 214s] guess the prefix. [ 214s] --git-tag-only [ 214s] Don't build, only tag and run post-tag hooks. [ 214s] --git-retag [ 214s] Don't fail tag operations if a tag with the same version already [ 214s] exists, but, overwrite the existing tag, instead. [ 214s] --git-pristine-tar [ 214s] Use pristine-tar when generating the upstream tarball if it doesn't [ 214s] exist. [ 214s] --git-pristine-tar-commit [ 214s] Commit the pristine-tar delta to the pristine-tar branch if a new [ 214s] tarball was generated and the pristine-tar data isn't already there. [ 214s] --git-[no-]patch-export [ 214s] Create patches from the commits between the upstream version and [ 214s] export-treeish. That is, after exporting packaging files (from the [ 214s] pacakging directory) gbp buildpackage-rpm creates one patch per [ 214s] commit (similar to git-format-patch) and updates the spec file in the [ 214s] export dir. You use --git-patch-export-rev to [ 214s] specify the tip commit of the patch series. [ 214s] --git-patch-export-rev=TREEISH [ 214s] Use TREEISH as the tip commit of the patch [ 214s] series instead of the default - i.e. treeish from which the packaging [ 214s] files are exported (which is defined with [ 214s] --git-export. [ 214s] --git-patch-export-compress=THRESHOLD [ 214s] Compress (auto-generated) patches larger than given [ 214s] THRESHOLD bytes. Special value 0 disabled [ 214s] patch compression. [ 214s] --git-patch-export-ignore-path=REGEX [ 214s] Exclude changes to path(s) matching REGEX [ 214s] in patch generation. [ 214s] --git-patch-export-squash-until=COMMITISH [ 214s] Squash commits up to the given COMMITISH [ 214s] into one monolitic diff. Could be used if one wants to squash commits [ 214s] from an upstream release up to a stable update into a single diff [ 214s] (commits on top of the stable would generate one patch per commit as [ 214s] usual). The format is '<commit_ish>[:<filename_base>]', [ 214s] i.e. commitish optionally followed by a colon and the desired [ 214s] filename base for the diff (suffix '.diff' is automatically added by [ 214s] gbp buildpackage-rpm). Magic word 'HEAD' translates to the [ 214s] patch-export-treeish when given as the squash-point. This allows one [ 214s] to configure gbp to always squash all commits into one monolithic [ 214s] diff. [ 214s] --git-[no-]patch-numbers [ 214s] Whether the patch files should start with a number or not. [ 214s] --git-spec-vcs-tag=TAG_FORMAT [ 214s] gbp buildpackage-rpm always automatically sets/updates the 'VCS:' [ 214s] tag in the spec file after exporting. This option defines the format [ 214s] string for the 'VCS:' tag. An empty value causes no 'VCS:' tag to be [ 214s] inserted and possible old 'VCS:' tag to be removed. Otherwise, the [ 214s] old 'VCS:' tag is updated or a new 'VCS:' tag is added if one does [ 214s] not exist. In the format string '%(tagname)s' expands to the long tag [ 214s] name (from git-describe) and '%(commit)s' expans to the sha1 of the [ 214s] exported commit. [ 214s] EXAMPLES Only build a source RPM with rpmbuild [ 214s] gbp buildpackage-rpm -bs [ 214s] Build an RPM package with rpmbuild on a custom branch with the uncommitted [ 214s] changes included. [ 214s] gbp buildpackage-rpm --git-ignore-branch --git-export=WC.UNTRACKED [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details. All options in the config files are specified without the 'git-' prefix. [ 214s] SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] rpmbuild8, [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Markus Lehtonen markus.lehtonen@linux.intel.com [ 214s] markus.lehtonen@linux.intel.com [ 214s] MarkusLehtonengbp-import-orig-rpm1git-import-orig-rpmgbp-import-orig-rpmImport an upstream source into a git repository.gbp import-orig-rpm--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--vendor=VENDOR--upstream-version=VERSION--[no-]merge--upstream-branch=BRANCH-NAME--packaging-branch=BRANCH-NAME--packaging-dir=DIRECTORY--[no-]create-missing-branches--upstream-vcs-tag=TAG-NAME--[no-]sign-tags--keyid=GPG-KEYID--upstream-tag=TAG-FORMAT--filter=PATTERN--[no-]pristine-tar--[no-]filter-pristine-tar--pristine-tarball-name=FILENAME--orig-prefix=PREFIX--postimport=CMD--[no-]interactiveUPSTREAM-SOURCEDESCRIPTION gbp import-orig-rpm is an basically identical to the gbp import-orig [ 214s] tool, with only some rpm-specific functionality added and some [ 214s] Debian-specific functionality removed. [ 214s] gbp import-orig-rpm imports UPSTREAM-SOURCE [ 214s] into the Git repository. UPSTREAM-SOURCE can [ 214s] either be a gzip, bzip2, lzma or xz compressed tar archive, a zip archive [ 214s] or an already unpacked source tree. If it is already of the form [ 214s] package-name-version.tar.gz, the version [ 214s] information is read from the tarball's filename otherwise it can be given [ 214s] on the command line via --upstream-version. If the source [ 214s] package name or version can't be determined gbp import-orig-rpm will [ 214s] prompt for it unless --no-interactive is given. [ 214s] gbp import-orig-rpm tries to download the archive from a remote server if [ 214s] a remote URL is given. In addition, if no [ 214s] UPSTREAM-SOURCE is given gbp import-orig-rpm [ 214s] takes the archive URI from the spec file - this makes it possible to import [ 214s] a new upstream version just by bumping the version number in the spec file [ 214s] and running gbp import-orig-rpm (assuming that the spec file contains [ 214s] a full URL for the archive and its filename automatically follows the [ 214s] package version e.g. by using the %{version} macro, of course). [ 214s] The sources are placed on the upstream branch (default: [ 214s] upstream) and tagged. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --vendor=VENDOR [ 214s] Distribution vendor name. [ 214s] --upstream-version=VERSION-uVERSION The upstream version number. [ 214s] --merge Merge the upstream branch to the packaging branch after import. [ 214s] --upstream-branch=BRANCH-NAME [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream. [ 214s] --packaging-branch=BRANCH-NAME [ 214s] The branch in the Git repository the package is being developed on, [ 214s] default is master. After importing the new [ 214s] sources on the upstream branch, gbp import-orig-rpm will try to [ 214s] merge the new version onto this branch. [ 214s] --packaging-dir=DIRECTORY [ 214s] Subdirectory that contains the RPM packaging files. [ 214s] gbp import-orig-rpm uses this to try to find a spec file which, in [ 214s] turn, is used to get the upstream source archive URI if one is not [ 214s] specified on the command line. [ 214s] --[no-]create-missing-branches [ 214s] Create missing upstream branch if it does not exist. [ 214s] --upstream-vcs-tag=TAG-NAME [ 214s] Add TAG-NAME as additional parent to the [ 214s] commit of the upstream tarball. Useful when upstream uses git and you [ 214s] want to link to it's revision history. [ 214s] --[no-]sign-tags [ 214s] GPG sign all created tags. [ 214s] --keyid=GPG-KEYID [ 214s] Use this keyid for gpg signing tags. [ 214s] --upstream-tag=TAG-FORMAT [ 214s] Use this tag format when tagging upstream versions, [ 214s] default is upstream/%(version)s. [ 214s] --import-msg=MSG-FORMAT [ 214s] Use this format string for the commit message when importing upstream [ 214s] versions, default is [ 214s] Imported Upstream version %(version)s. [ 214s] --filter=PATTERN [ 214s] Filter out files glob-matching pattern. Can be given multiple times. [ 214s] --[no-]pristine-tar [ 214s] Generate pristine-tar delta file. [ 214s] --[no-]filter-pristine-tar [ 214s] If using a filter also filter the files out of the tarball [ 214s] passed to pristine-tar. [ 214s] --pristine-tarball-name=FILENAME [ 214s] Filename to record to pristine-tar. This does not alter the tarball [ 214s] content, just the filename with which the tarball can be checked out [ 214s] with pristine-tar. [ 214s] --orig-prefix=PREFIX [ 214s] Prefix (directory) to be used when importing sources into [ 214s] pristine-tar. Only takes effect when --pristine-tar [ 214s] is used. Special value auto causes gbp import-orig-rpm to guess [ 214s] the prefix when importing unpacked sources, or, not to change the [ 214s] prefix when importing source archives. [ 214s] Using this option will alter the source archive that is imported to [ 214s] pristine-tar! That is, pristine-tar does not produce and identical [ 214s] copy of the original tarball (but the mangled tarball, instead). [ 214s] --postimport=CMD Run CMD after the import. [ 214s] --[no-]interactive Run command interactively, i.e. ask package name and version if [ 214s] needed. [ 214s] EXAMPLES Download and import a new upstream version using the informantion from the [ 214s] spec file [ 214s] gbp import-orig-rpm [ 214s] After manually downloading an upstream import it [ 214s] gbp import-orig-rpm ../upstream-tarball-0.1.tar.gz [ 214s] Import unpacked sources [ 214s] gbp import-orig-rpm --orig-prefix=upstream-0.1 ../upstream/ [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Markus Lehtonen markus.lehtonen@linux.intel.com [ 214s] markus.lehtonen@linux.intel.com [ 214s] MarkusLehtonengbp-import-srpm1git-import-srpmgbp-import-srpmImport source RPM packages into a Git repositorygbp import-srpm--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--vendor=VENDOR--allow-same-versions--author-is-committer--packaging-branch=BRANCH-NAME--packaging-tag=TAG-FORMAT--download--packaging-dir=DIRECTORY--[no-]patch-import--filter=PATTERN--keyid=GPG-KEYID--[no-]create-missing-branches--[no-]pristine-tar--[no-]sign-tags--upstream-branch=BRANCH-NAME--upstream-tag=TAG-FORMAT--nativeSRPMgbp import-srpmoptions--downloadURLSRC.RPMDIRECTORYDESCRIPTION gbp import-srpm imports an RPM source package into a Git repository, [ 214s] notes the package version in the commit logs, and commits the change. All [ 214s] information, including package name, version and upstream source is [ 214s] automatically detected from the source package. The tool supports importing [ 214s] both archived (src.rpm files) or unpacked (directory) source RPMs. [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --vendor=VENDOR [ 214s] Distribution vendor name. [ 214s] --upstream-branch=BRANCH-NAME [ 214s] The branch in the Git repository the upstream sources are put [ 214s] onto. Default is upstream. [ 214s] --packaging-branch=BRANCH-NAME [ 214s] The branch in the Git repository the packaging files are put [ 214s] onto. Default is master. [ 214s] --[no-]sign-tags [ 214s] GPG sign all created tags. [ 214s] --keyid=GPG-KEYID [ 214s] Use this keyid for gpg signing tags. [ 214s] --packaging-tag=TAG-FORMAT [ 214s] Use this tag format when tagging released versions, [ 214s] default is %(vendor)s/%(version)s. [ 214s] --upstream-tag=TAG-FORMAT [ 214s] Use this tag format when tagging upstream versions, [ 214s] default is upstream/%(version)s. [ 214s] --git-packaging-dir=DIRECTORY [ 214s] Subdirectory where to put the RPM packaging files. [ 214s] --[no-]patch-import [ 214s] Import patches to the packaging branch. That is, apply and commit all [ 214s] patches (that are not marked for manual maintenance) into the [ 214s] packaging branch after importing other packaging files. The patch [ 214s] files are automatically removed from the packaging directory and the [ 214s] spec file if all patches are successufully applied. This option is [ 214s] ignored if --orphan-packaging is used. [ 214s] --filter=PATTERN [ 214s] Filter out files glob-matching pattern. Can be given multiple times. [ 214s] --pristine-tar [ 214s] Generate pristine-tar delta file. [ 214s] --download [ 214s] Download the source package instead of looking for it in the local [ 214s] file system. The argument can either be a plain package name or an [ 214s] URI. The former uses yumdownloader to download the [ 214s] source while the later uses wget. [ 214s] --allow-same-version [ 214s] Allow to re-import a package with an already existing version. This [ 214s] will not re-import the upstream sources - only packaging files will [ 214s] be re-imported. [ 214s] --author-is-committer [ 214s] Use the author identity as the comitter when importing upstream [ 214s] sources and packaging files. [ 214s] --[no-]create-missing-branches [ 214s] Create missing upstream and/or packaging branch if missing. [ 214s] --orphan-packaging [ 214s] Import packaging files into an orphan branch that will not be based [ 214s] on the upstream branch. Useful if you want to maintain (non-native) [ 214s] package using the 'orphan-packaging' model. This option have no [ 214s] effect if --native is used. [ 214s] --native [ 214s] Treat the package as native package. No separate upstream branch or [ 214s] upstream tags will be created. [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] AUTHOR Markus Lehtonen markus.lehtonen@linux.intel.com [ 214s] markus.lehtonen@linux.intel.com [ 214s] MarkusLehtonengbp-pq-rpm1gbp-pq-rpmManage patches and development branches in Gitgbp pq-rpm--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--vendor=VENDOR--packaging-branch=BRANCH-NAME--pq-branch=BRANCH-NAME--packaging-dir=DIRECTORY--spec-file=FILEPATH--upstream-tag=TAG-FORMAT--force--import-files=FILES--export-rev=TREEISH--patch-export-compress=THRESHOLD--patch-export-ignore-path=REGEX--patch-export-squash-until=COMMITISH--[no-]patch-numbers--new-packaging-dir=DIRECTORY--retain-historydropexportimportrebaseswitchconvertDESCRIPTION gbp pq-rpm helps in managing patches and development branch(es) for [ 214s] packages that are maintained with gbp. It designed to be used for [ 214s] packages that are maintained using the "orphan-packaging" model. [ 214s] gbp pq-rpm has multiple subcommands, or actions, for working with the [ 214s] branches and patches. [ 214s] gbp pq-rpm makes it easy to do source code development on a separate [ 214s] development branch (patch-queue branch in Debian git-buildpackage terms). [ 214s] For example, if the packaging files would be stored in [ 214s] master the associated development branch would [ 214s] be development/master. [ 214s] ACTIONSimport [ 214s] Create a development (patch-queue) branch by applying all patches [ 214s] from the packaging branch on top of the upstream version. The patches [ 214s] must apply without fuzz. [ 214s] export [ 214s] Export patches from the development branch into the packaging branch. [ 214s] It generates patches (one-per-commit) from the development branch and [ 214s] updates the spec file accordingly. It doesn't automatically commit [ 214s] the changes though - they need to verified and committed manually. [ 214s] rebase [ 214s] Switch to the development branch and rebase it against the current [ 214s] upstream version (indicated in the spec file of the associated [ 214s] packaging branch). [ 214s] drop [ 214s] Drop (delete) the development branch associated to the current [ 214s] branch. For example, you're on branch foo [ 214s] this would drop branch development/foo. [ 214s] apply [ 214s] Add a single patch to the development branch - similar to using [ 214s] git-am. [ 214s] switch [ 214s] Switch between the development branch and the associated packaging [ 214s] branch. [ 214s] convert [ 214s] Convert a package from the "joint-packaging" maintenance model and [ 214s] git-layout to the "orphan-packaging" model. It takes the content of [ 214s] the packaging directory, auto-generates patches and puts these into a [ 214s] new orphan packaging branch. You can use the [ 214s] --retain-history to try to preserve as much of the [ 214s] git history as possible. Converting is a one-time action - conversion [ 214s] back to the "joint-packaging" model is not supported (yet). [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --vendor=VENDOR [ 214s] Distribution vendor name. [ 214s] --packaging-branch=BRANCH-NAME [ 214s] Branch the packaging files are being maintained on. Only relevant if [ 214s] a invariable/single development (pq-branch) is defined with [ 214s] --pq-branch, in which case this is used as the [ 214s] "base" branch. [ 214s] --pq-branch=BRANCH_NAME [ 214s] Name (format string) of the development (patch-queue) branch. The [ 214s] following string fields are accepted: "%(branch)s" (the base branch, [ 214s] i.e. the packaging branch that the development branch is associated [ 214s] to), "%(upstreamversion)s" (the upstream version), "%(release)s" (the [ 214s] rpm patchlevel, i.e. Release), "%(version)s" (full rpm package [ 214s] version). [ 214s] --packaging-dir=DIRECTORY [ 214s] Subdirectory that contains the RPM packaging files. [ 214s] --spec-file=FILEPATH [ 214s] Relative path to the spec file to use. Special value [ 214s] auto causes gbp to search and guess. [ 214s] Other values cause the --packaging-dir option to be [ 214s] ignored: the directory of the spec file is used, instead. [ 214s] --upstream-tag=TAG-FORMAT [ 214s] Use this tag format when looking for tags of upstream versions, [ 214s] default is upstream/%(version)s. [ 214s] --force Import even if the development (patch-queue) branch already exists. [ 214s] Only valid for the import action. [ 214s] --import-files=FILES [ 214s] Comma-separated list of additional file(s) to import from packaging [ 214s] branch. These will appear as one monolithic patch in the development [ 214s] (patch-queue) branch. By default, the local gbp conf files are [ 214s] imported in order to try to ensure that gbp sees the same settings on [ 214s] the development (pq) branch as on the packaging branch. [ 214s] --export-rev=TREEISH [ 214s] Export patches from TREEISH instead of the [ 214s] default which is HEAD of the development (patch-queue) branch. [ 214s] --patch-export-compress=THRESHOLD [ 214s] Compress patches larger than given [ 214s] THRESHOLD bytes. Special value 0 disabled [ 214s] patch compression. [ 214s] --patch-export-ignore-path=REGEX [ 214s] Exclude changes to path(s) matching REGEX [ 214s] in patch generation. [ 214s] --patch-export-squash-until=COMMITISH [ 214s] Squash commits up to the given COMMITISH [ 214s] into one monolitic diff. Could be used if one wants to squash commits [ 214s] from an upstream release up to a stable update into a single diff [ 214s] (commits on top of the stable would generate one patch per commit as [ 214s] usual). The format is '<commit_ish>[:<filename_base>]', [ 214s] i.e. commitish optionally followed by a colon and the desired [ 214s] filename base for the diff (suffix '.diff' is automatically added by [ 214s] gbp). Magic word 'HEAD' translates to the patch-export-treeish when [ 214s] given as the squash-point. This allows one to configure gbp to [ 214s] always squash all commits into one monolithic diff. [ 214s] --[no-]patch-numbers [ 214s] Whether the patch files should start with a number or not. [ 214s] --new-packaging-dir=DIRECTORY [ 214s] Directory where packaging files are put in the new orphan packaging [ 214s] branch after convert. If --new-packaging-dir= is not [ 214s] defined, packaging-dir is used. [ 214s] --retain-history [ 214s] Try to preserve as much history as possible when converting. That is, [ 214s] for each commit in the old branch create one corresponding commit in [ 214s] the new orphan packaging branch. However, commits that will not [ 214s] generate any changes are skipped (i.e. no empty commits are [ 214s] generated) - these are caused e.g. by changes in files that are [ 214s] ignored by patch-generation. [ 214s] META TAGS When exporting patches from a patch-queue branch gbp pq-rpm will look at [ 214s] the commit message for special tags it recognizes. All tags need to start [ 214s] at the first column and require at least one whitespace after the colon. [ 214s] Gbp-Rpm: Ignore [ 214s] Ignores the commit, no patch is generated out of it. [ 214s] Gbp-Rpm: If <expression> [ 214s] Conditional patch. Put patch inside "%if <expression>" in the [ 214s] spec file. [ 214s] Gbp-Rpm: IfArch<expression> [ 214s] Conditional patch. Put patch inside "%ifarch <expression>" in [ 214s] the spec file. [ 214s] For example, the following commit message: [ 214s] Fix around a problem in Fedora [ 214s] [ 214s] which is not applicable elsewhere. [ 214s] [ 214s] Gbp-Rpm: If 0%{?fedora} [ 214s] Will result something like this in the spec file: [ 214s] # 0001-Fix-around-a-problem-in-Fedora.patch [ 214s] %if 0%{?fedora} [ 214s] %patch0 -p1 [ 214s] %endif [ 214s] SEE ALSO , [ 214s] [ 214s] AUTHOR Markus Lehtonen markus.lehtonen@linux.intel.com [ 214s] markus.lehtonen@linux.intel.com [ 214s] MarkusLehtonengbp-rpm-ch1git-rpm-ch;gbp-rpm-ch;Generate the RPM changelog from git commit messagesgbp rpm-ch--version--help--verbose--color=[auto|on|off]--color-scheme=COLOR_SCHEME--vendor=VENDOR--packaging-branch=BRANCH-NAME--packaging-tag=TAG-FORMAT--ignore-branch--packaging-dir=DIRECTORY--changelog-file=FILEPATH--spec-file=FILEPATH--all--message=MESSAGE--since=COMMITISH--meta-bts=META_TAGS--no-release--[no-]git-author--[no-]full--id-length=NUMBER--changelog-revision=REV-FORMAT--git-log=GIT-LOG-OPTIONS--spawn-editor=[always|release|no]--editor-cmd=EDITOR--commit--tag--retag--[no-]sign-tags--keyid=GPG-KEYID--customizations=CUSTOMIZATION-FILE[PATH1 PATH2]DESCRIPTION gbp rpm-ch reads git commit messages up to the current tip of the current [ 214s] branch and updates the RPM changelog from them. [ 214s] By default, gbp rpm-ch tries to guess the last Git commit documented in [ 214s] the changelog. Alternatively, --since can be used to [ 214s] tell gbp rpm-ch at which point it should start in the Git history, or, [ 214s] --all to use all commits from the Git history. [ 214s] The additional path arguments can be used to restrict the repository paths [ 214s] gbp rpm-ch looks at. For even more detailed control, you can use [ 214s] --git-log to restrict the generated changelog entries [ 214s] further. E.g. by using [ 214s] --git-log="--author=Foo Bar". [ 214s] OPTIONS--version Print version of the program, i.e. version of the git-buildpackage [ 214s] suite [ 214s] -v--verbose Verbose execution [ 214s] -h--help Print help and exit [ 214s] --color=[auto|on|off] [ 214s] Whether to use colored output. [ 214s] --color-scheme=COLOR_SCHEME [ 214s] Colors to use in output (when color is enabled). The format for [ 214s] COLOR_SCHEME is [ 214s] '<debug>:<info>:<warning>:<error>'. [ 214s] Numerical values and color names are accepted, empty fields imply [ 214s] the default color. For example --git-color-scheme='cyan:34::' would [ 214s] show debug messages in cyan, info messages in blue and other messages [ 214s] in default (i.e. warning and error messages in red). [ 214s] --vendor=VENDOR [ 214s] Distribution vendor name. [ 214s] --packaging-branch=BRANCH-NAME [ 214s] The branch in the Git repository the package is being developed on, [ 214s] default is master. [ 214s] --ignore-branch [ 214s] Don't check if the current branch matches [ 214s] PACKAGING-BRANCH. [ 214s] --packaging-tag=TAG-FORMAT [ 214s] Tag format used, when tagging releases, [ 214s] default is %(vendor)s/%(version)s [ 214s] --packaging-dir=DIRECTORY [ 214s] Subdirectory that contains the RPM packaging files. [ 214s] --changelog-file=FILEPATH [ 214s] Relative path to the changelog file to use. Special value [ 214s] auto causes gbp to guess, [ 214s] SPEC uses the spec file, [ 214s] CHANGES uses a separate changelog file [ 214s] (name derived spec file name with .spec suffix replaced by .changes). [ 214s] Guessing logic is simple: use separate changelog file if it is found, [ 214s] otherwise use the spec file. [ 214s] --spec-file=FILEPATH [ 214s] Relative path to the spec file to use. Special value [ 214s] auto causes gbp to search and guess. [ 214s] Other values cause the --packaging-dir option to be [ 214s] ignored: the directory of the spec file is used, instead. [ 214s] --all [ 214s] Use all commits from the Git history, overrides [ 214s] --since. [ 214s] --since=COMMITTISH [ 214s] Start reading commit messages at [ 214s] COMMITTISH. [ 214s] --meta-bts=META_TAGS [ 214s] Meta tags in the commit messages that are interpreted as bug tracking [ 214s] system related references. The recognized bts references are added in [ 214s] the generated changelog entries. See the META TAGS section below for [ 214s] more information. The bts meta tag tracking feature can be disabled [ 214s] by defining an empty string. [ 214s] --no-release [ 214s] Do not create a new changelog section, just update the last [ 214s] changelog section. [ 214s] --[no-]full [ 214s] Include the full commit message in the changelog output. [ 214s] --git-log=GIT-LOG-OPTIONS [ 214s] Options passed on verbatim to git-log(1). [ 214s] --id-length=N [ 214s] Include N digits of the commit id in the [ 214s] changelog entry. Default is to not include any commit ids at all. [ 214s] --changelog-revision=REV-FORMAT [ 214s] Format string to use for revision field in the changelog header. The [ 214s] following string fields are accepted: [ 214s] %(upstreamversion)s the upstream version; [ 214s] %(release)s the rpm patchlevel, i.e. [ 214s] Release; %(version)s full rpm package [ 214s] version; %(tagname)s tag/commit, i.e. [ 214s] basically what git-describe would give. [ 214s] If empty or not defined the default from packaging policy is used. [ 214s] --ignore-regex=REGEX [ 214s] Ignore commit lines matching REGEX [ 214s] when generating the changelog. [ 214s] --git-author [ 214s] Use user.name and user.email from [ 214s] git-config(1) for the changelog header. [ 214s] --spawn-editor=[always|release|no] [ 214s] Whether to spawn an editor: always, when doing a release or never. [ 214s] --editor-cmd=EDITOR [ 214s] The editor to use for editing the changelog. [ 214s] --message=MESSAGE [ 214s] Text to use for new changelog entries. Git history and the commit [ 214s] messages, including --since and [ 214s] --all options are ignored in this case. [ 214s] --commit [ 214s] Commit changes to git after modifying changelog. Importantly, in [ 214s] addition to the changelog modifications all other staged changes are [ 214s] committed, too, making it possible to update other files in the same [ 214s] commit. [ 214s] --commit-msg=MSG-FORMAT [ 214s] Format string for the commit message when committing changes [ 214s] (when --commit is given). [ 214s] --tag [ 214s] Commit the changes and create a packaging (release) tag. Similarly to [ 214s] --commit, all staged changes are committed to git [ 214s] before creating the tag. This option makes it possible to create a [ 214s] release and correctly document the the tag name in the rpm changelog [ 214s] (by using %(tagname)s in the --changelog-revision [ 214s] string). [ 214s] --retag [ 214s] Don't fail tag operations if a tag with the same version already [ 214s] exists, but, overwrite the existing tag, instead. [ 214s] --[no-]sign-tags [ 214s] GPG sign all created tags. [ 214s] --keyid=GPG-KEYID [ 214s] Use this keyid for gpg signing tags. [ 214s] --customizations=CUSTOMIZATION-FILE [ 214s] Load Python code from CUSTOMIZATION-FILE. [ 214s] At the moment, the only useful thing the code can do is define a [ 214s] custom ChangelogEntryFormatter class. [ 214s] META TAGS Additional to the above options the formatting of the new changelog entries [ 214s] (one-per-commit) in the changelog can be modified by special tags (called [ 214s] Meta Tags) given in the git commit message. The tags must start at the [ 214s] first column of a commit message but can appear on any line. They are of [ 214s] the form Tagname: VALUE. Valid [ 214s] Meta Tags are: [ 214s] Git-Rpm-Ch: ACTION [ 214s] Supported actions are: Ignore which will [ 214s] ignore this commit when generating new changelog entries. [ 214s] Short which will only use the description [ 214s] (the first line) of the commit message when generating the changelog [ 214s] entry (useful when --full is given) and [ 214s] Full which will use the full commit [ 214s] message when generating the changelog entry (useful when [ 214s] --full is not given). [ 214s] [Close|Closes|...]: BUGNUMBER [ 214s] Indicate in the changelog entry that bug [ 214s] BUGNUMBER was addressed in this commit. [ 214s] The bts meta tags recognized by gbp rpm-ch is actually defined by [ 214s] the --meta-bts option. [ 214s] The following git commit message: [ 214s] Document meta tags [ 214s] [ 214s] so one doesn't have to consult the manual [ 214s] [ 214s] Git-Rpm-Ch: Short [ 214s] Closes: #636088 [ 214s] Results in this changelog entry: [ 214s] - Document meta tags (Closes: #636088) [ 214s] CONFIGURATION FILESSeveral gbp.conf files are parsed [ 214s] to set defaults for the above commandline arguments. See the [ 214s] manpage for details.SEE ALSO , [ 214s] , [ 214s] , [ 214s] , [ 214s] debuild1, [ 214s] git1, [ 214s] pristine-tar1, [ 214s] The Git-Buildpackage Manual [ 214s] [ 214s] Cl2vcs, [ 214s] AUTHOR Markus Lehtonen markus.lehtonen@linux.intel.com [ 214s] Copyright git-buildpackage, all associated scripts and programs, this manual, [ 214s] and all build scripts are Copyright © 2006-2014 Guido Guenther. [ 214s] This program is free software; you can redistribute it and/or modify [ 214s] it under the terms of the GNU General Public License as published by [ 214s] the Free Software Foundation; Version 2 of the License. [ 214s] This program is distributed in the hope that it will be useful, [ 214s] but WITHOUT ANY WARRANTY; without even the implied warranty of [ 214s] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the [ 214s] GNU General Public License for more details. [ 214s] You should have received a copy of the GNU General Public License [ 214s] along with this program; if not, write to the Free Software [ 214s] Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA [ 214s] rm -rf manual-html [ 214s] mv main-html manual-html [ 214s] cp /usr/share/gtk-doc/data/*.png manual-html [ 214s] docbook2man -o buildxref man.gbp.sgml [ 214s] Using catalogs: /etc/sgml/catalog [ 214s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 214s] Working on: /usr/src/packages/BUILD/docs/man.gbp.sgml [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:161:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:165:21:X: reference to non-existent ID "MAN.GBP.CLONE" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:163:21:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:159:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:160:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:157:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:164:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:162:21:X: reference to non-existent ID "MAN.GBP.PQ" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:158:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:170:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 214s] [ 214s] GuidoGuentherResolving references.. [ 214s] [ 214s] GuidoGuentherWarning: output contains unresolved XRefs [ 214s] Done. [ 214s] docbook2man -o buildxref man.gbp-buildpackage.sgml [ 214s] Using catalogs: /etc/sgml/catalog [ 214s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 214s] Working on: /usr/src/packages/BUILD/docs/man.gbp-buildpackage.sgml [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:648:19:X: reference to non-existent ID "MAN.GBP.DCH" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:645:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:657:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:646:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 214s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:647:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 214s] [ 214s] GuidoGuentherResolving references.. [ 215s] [ 215s] GuidoGuentherWarning: output contains unresolved XRefs [ 215s] Done. [ 215s] docbook2man -o buildxref man.gbp-buildpackage-rpm.sgml [ 215s] Using catalogs: /etc/sgml/catalog [ 215s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 215s] Working on: /usr/src/packages/BUILD/docs/man.gbp-buildpackage-rpm.sgml [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:754:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:747:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:748:19:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:746:19:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:749:19:X: reference to non-existent ID "MAN.GBP.PQ.RPM" [ 215s] [ 215s] MarkusLehtonenResolving references.. [ 215s] [ 215s] MarkusLehtonenWarning: output contains unresolved XRefs [ 215s] Done. [ 215s] docbook2man -o buildxref man.gbp-clone.sgml [ 215s] Using catalogs: /etc/sgml/catalog [ 215s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 215s] Working on: /usr/src/packages/BUILD/docs/man.gbp-clone.sgml [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:105:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:106:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:107:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] [ 215s] GuidoGuentherResolving references.. [ 215s] [ 215s] GuidoGuentherWarning: output contains unresolved XRefs [ 215s] Done. [ 215s] docbook2man -o buildxref man.gbp-config.sgml [ 215s] Using catalogs: /etc/sgml/catalog [ 215s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 215s] Working on: /usr/src/packages/BUILD/docs/man.gbp-config.sgml [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-config.sgml:93:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] [ 215s] GuidoGuentherResolving references.. [ 215s] [ 215s] GuidoGuentherWarning: output contains unresolved XRefs [ 215s] Done. [ 215s] docbook2man -o buildxref man.gbp-create-remote-repo.sgml [ 215s] Using catalogs: /etc/sgml/catalog [ 215s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 215s] Working on: /usr/src/packages/BUILD/docs/man.gbp-create-remote-repo.sgml [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:131:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:132:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:87:65:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:133:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] [ 215s] GuidoGuentherResolving references.. [ 215s] [ 215s] GuidoGuentherWarning: output contains unresolved XRefs [ 215s] Done. [ 215s] docbook2man -o buildxref man.gbp-dch.sgml [ 215s] Using catalogs: /etc/sgml/catalog [ 215s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 215s] Working on: /usr/src/packages/BUILD/docs/man.gbp-dch.sgml [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:486:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:487:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:489:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:488:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 215s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:485:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 215s] [ 216s] GuidoGuentherResolving references.. [ 216s] [ 216s] GuidoGuentherWarning: output contains unresolved XRefs [ 216s] Done. [ 216s] docbook2man -o buildxref man.gbp-import-dsc.sgml [ 216s] Using catalogs: /etc/sgml/catalog [ 216s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 216s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-dsc.sgml [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:230:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:239:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:227:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:229:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:228:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 216s] [ 216s] GuidoGuentherResolving references.. [ 216s] [ 216s] GuidoGuentherWarning: output contains unresolved XRefs [ 216s] Done. [ 216s] docbook2man -o buildxref man.gbp-import-dscs.sgml [ 216s] Using catalogs: /etc/sgml/catalog [ 216s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 216s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-dscs.sgml [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:86:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:83:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:87:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:85:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:84:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 216s] [ 216s] GuidoGuentherResolving references.. [ 216s] [ 216s] GuidoGuentherWarning: output contains unresolved XRefs [ 216s] Done. [ 216s] docbook2man -o buildxref man.gbp-import-orig.sgml [ 216s] Using catalogs: /etc/sgml/catalog [ 216s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 216s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-orig.sgml [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:270:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:268:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:269:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:271:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:267:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 216s] [ 216s] GuidoGuentherResolving references.. [ 216s] [ 216s] GuidoGuentherWarning: output contains unresolved XRefs [ 216s] Done. [ 216s] docbook2man -o buildxref man.gbp-import-orig-rpm.sgml [ 216s] Using catalogs: /etc/sgml/catalog [ 216s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 216s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-orig-rpm.sgml [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:314:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:313:21:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:312:21:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:311:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 216s] [ 216s] MarkusLehtonenResolving references.. [ 216s] [ 216s] MarkusLehtonenWarning: output contains unresolved XRefs [ 216s] Done. [ 216s] docbook2man -o buildxref man.gbp-import-srpm.sgml [ 216s] Using catalogs: /etc/sgml/catalog [ 216s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 216s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-srpm.sgml [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:252:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:250:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:251:21:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 216s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:249:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 217s] [ 217s] MarkusLehtonenResolving references.. [ 217s] [ 217s] MarkusLehtonenWarning: output contains unresolved XRefs [ 217s] Done. [ 217s] docbook2man -o buildxref man.gbp-pq.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pq.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq.sgml:219:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq.sgml:228:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] [ 217s] GuidoGuentherResolving references.. [ 217s] [ 217s] GuidoGuentherWarning: output contains unresolved XRefs [ 217s] Done. [ 217s] docbook2man -o buildxref man.gbp-pq-rpm.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pq-rpm.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq-rpm.sgml:389:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq-rpm.sgml:390:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] [ 217s] MarkusLehtonenResolving references.. [ 217s] [ 217s] MarkusLehtonenWarning: output contains unresolved XRefs [ 217s] Done. [ 217s] docbook2man -o buildxref man.gbp-pull.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pull.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:159:21:X: reference to non-existent ID "MAN.GBP.PQ" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:158:21:X: reference to non-existent ID "MAN.GBP.CLONE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:160:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:157:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 217s] [ 217s] GuidoGuentherResolving references.. [ 217s] [ 217s] GuidoGuentherWarning: output contains unresolved XRefs [ 217s] Done. [ 217s] docbook2man -o buildxref man.gbp-rpm-ch.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp-rpm-ch.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:434:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:433:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:431:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:432:21:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 217s] [ 217s] MarkusLehtonenResolving references.. [ 217s] [ 217s] MarkusLehtonenWarning: output contains unresolved XRefs [ 217s] Done. [ 217s] docbook2man -o buildxref man.gbp.conf.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp.conf.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:222:19:X: reference to non-existent ID "MAN.GBP.DCH" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:218:19:X: reference to non-existent ID "MAN.GBP.CLONE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:130:15:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:219:19:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:88:31:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:100:15:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:224:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:75:55:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:225:19:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:221:19:X: reference to non-existent ID "MAN.GBP.PULL" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:220:19:X: reference to non-existent ID "MAN.GBP.PQ" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:223:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 217s] [ 217s] GuidoGuentherDone. [ 217s] cp buildxref/manpage.refs manpage.refs [ 217s] docbook2man -o . man.gbp.sgml [ 217s] Using catalogs: /etc/sgml/catalog [ 217s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 217s] Working on: /usr/src/packages/BUILD/docs/man.gbp.sgml [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:161:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:165:21:X: reference to non-existent ID "MAN.GBP.CLONE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:163:21:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:159:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:160:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:157:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:164:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:162:21:X: reference to non-existent ID "MAN.GBP.PQ" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:158:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 217s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.sgml:170:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] [ 218s] GuidoGuentherDone. [ 218s] docbook2man -o . man.gbp-buildpackage.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-buildpackage.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:648:19:X: reference to non-existent ID "MAN.GBP.DCH" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:645:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:657:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:646:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage.sgml:647:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 218s] [ 218s] GuidoGuentherDone. [ 218s] docbook2man -o . man.gbp-buildpackage-rpm.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-buildpackage-rpm.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:754:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:747:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:748:19:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:746:19:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-buildpackage-rpm.sgml:749:19:X: reference to non-existent ID "MAN.GBP.PQ.RPM" [ 218s] [ 218s] MarkusLehtonenDone. [ 218s] docbook2man -o . man.gbp-clone.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-clone.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:105:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:106:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-clone.sgml:107:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] [ 218s] GuidoGuentherDone. [ 218s] docbook2man -o . man.gbp-config.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-config.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-config.sgml:93:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] [ 218s] GuidoGuentherDone. [ 218s] docbook2man -o . man.gbp-create-remote-repo.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-create-remote-repo.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:131:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:132:21:X: reference to non-existent ID "MAN.GBP.PULL" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:87:65:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-create-remote-repo.sgml:133:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] [ 218s] GuidoGuentherDone. [ 218s] docbook2man -o . man.gbp-dch.sgml [ 218s] Using catalogs: /etc/sgml/catalog [ 218s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 218s] Working on: /usr/src/packages/BUILD/docs/man.gbp-dch.sgml [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:486:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:487:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:489:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:488:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 218s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-dch.sgml:485:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 218s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-import-dsc.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-dsc.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:230:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:239:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:227:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:229:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dsc.sgml:228:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-import-dscs.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-dscs.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:86:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:83:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:87:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:85:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-dscs.sgml:84:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-import-orig.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-orig.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:270:21:X: reference to non-existent ID "MAN.GBP.DCH" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:268:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:269:21:X: reference to non-existent ID "MAN.GBP.IMPORT.DSCS" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:271:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig.sgml:267:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-import-orig-rpm.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-orig-rpm.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:314:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:313:21:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:312:21:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-orig-rpm.sgml:311:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] [ 219s] MarkusLehtonenDone. [ 219s] docbook2man -o . man.gbp-import-srpm.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-import-srpm.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:252:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:250:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:251:21:X: reference to non-existent ID "MAN.GBP.RPM.CH" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-import-srpm.sgml:249:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 219s] [ 219s] MarkusLehtonenDone. [ 219s] docbook2man -o . man.gbp-pq.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pq.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq.sgml:219:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq.sgml:228:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-pq-rpm.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pq-rpm.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq-rpm.sgml:389:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pq-rpm.sgml:390:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] [ 219s] MarkusLehtonenDone. [ 219s] docbook2man -o . man.gbp-pull.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-pull.sgml [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:159:21:X: reference to non-existent ID "MAN.GBP.PQ" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:158:21:X: reference to non-existent ID "MAN.GBP.CLONE" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:160:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 219s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-pull.sgml:157:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 219s] [ 219s] GuidoGuentherDone. [ 219s] docbook2man -o . man.gbp-rpm-ch.sgml [ 219s] Using catalogs: /etc/sgml/catalog [ 219s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 219s] Working on: /usr/src/packages/BUILD/docs/man.gbp-rpm-ch.sgml [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/man.conffiles.sgml:4:19:X: reference to non-existent ID "MAN.GBP.CONF" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:434:21:X: reference to non-existent ID "MAN.GBP.CONF" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:433:21:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG.RPM" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:431:21:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE.RPM" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp-rpm-ch.sgml:432:21:X: reference to non-existent ID "MAN.GBP.IMPORT.SRPM" [ 220s] [ 220s] MarkusLehtonenDone. [ 220s] docbook2man -o . man.gbp.conf.sgml [ 220s] Using catalogs: /etc/sgml/catalog [ 220s] Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print [ 220s] Working on: /usr/src/packages/BUILD/docs/man.gbp.conf.sgml [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:222:19:X: reference to non-existent ID "MAN.GBP.DCH" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:218:19:X: reference to non-existent ID "MAN.GBP.CLONE" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:130:15:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:219:19:X: reference to non-existent ID "MAN.GBP.CREATE.REMOTE.REPO" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:88:31:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:100:15:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:224:19:X: reference to non-existent ID "MAN.GBP.IMPORT.ORIG" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:75:55:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:225:19:X: reference to non-existent ID "MAN.GBP.BUILDPACKAGE" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:221:19:X: reference to non-existent ID "MAN.GBP.PULL" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:220:19:X: reference to non-existent ID "MAN.GBP.PQ" [ 220s] onsgmls:/usr/src/packages/BUILD/docs/manpages/gbp.conf.sgml:223:19:X: reference to non-existent ID "MAN.GBP.IMPORT.DSC" [ 220s] [ 220s] GuidoGuentherDone. [ 220s] pod2man ../bin/git-pbuilder git-pbuilder.1 [ 220s] make[2]: Leaving directory '/usr/src/packages/BUILD/docs' [ 220s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 220s] debian/rules override_dh_auto_test [ 220s] make[1]: Entering directory '/usr/src/packages/BUILD' [ 220s] Checks disabled via DEB_BUILD_OPTIONS [ 220s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 220s] fakeroot debian/rules binary [ 220s] dh binary --with python2 [ 220s] dh_testroot [ 220s] dh_prep [ 220s] debian/rules override_dh_auto_install [ 220s] make[1]: Entering directory '/usr/src/packages/BUILD' [ 220s] dh_auto_install [ 220s] python setup.py install --force --root=/usr/src/packages/BUILD/debian/tmp --no-compile -O0 --install-layout=deb [ 220s] /usr/lib/python2.7/dist-packages/setuptools/dist.py:406: UserWarning: The version specified ('0.9.9-tizen20180912') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details. [ 220s] "details." % self.metadata.version [ 220s] running install [ 220s] running build [ 220s] running build_py [ 220s] copying gbp/version.py -> build/lib.linux-x86_64-2.7/gbp [ 220s] running build_scripts [ 220s] running install_lib [ 220s] creating /usr/src/packages/BUILD/debian/tmp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7 [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/tmpfile.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/version.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/pkg [ 220s] copying build/lib.linux-x86_64-2.7/gbp/pkg/pristinetar.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/pkg [ 220s] copying build/lib.linux-x86_64-2.7/gbp/pkg/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/pkg [ 220s] copying build/lib.linux-x86_64-2.7/gbp/log.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/upstreamsource.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/control.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/uscan.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/format.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/source.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/pristinetar.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/changelog.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/dscfile.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/git.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/deb/policy.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/deb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/format.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/notifications.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/dch.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/supercommand.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/rpm_ch.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/dch.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_srpm.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_orig_rpm.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/clone_bb.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_dsc.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/create_remote_repo.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/clone.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts/common [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/common/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts/common [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/common/buildpackage.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts/common [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/common/pq.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts/common [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/common/import_orig.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts/common [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/submit_bb.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_dscs.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/pq_bb.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/buildpackage_bb.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/buildpackage.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/pq_rpm.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_bb.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/pq.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/config.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/pull.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/buildpackage_rpm.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/scripts/import_orig.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/scripts [ 220s] copying build/lib.linux-x86_64-2.7/gbp/patch_series.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/command_wrappers.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/bb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/bb/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/bb [ 220s] copying build/lib.linux-x86_64-2.7/gbp/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/repository.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/vfs.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/fastimport.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/commit.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/modifier.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/args.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/git/errors.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/git [ 220s] copying build/lib.linux-x86_64-2.7/gbp/tristate.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/config.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] copying build/lib.linux-x86_64-2.7/gbp/errors.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/linkedlist.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/lib_rpm.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/changelog.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/__init__.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/git.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] copying build/lib.linux-x86_64-2.7/gbp/rpm/policy.py -> /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp/rpm [ 220s] running install_data [ 220s] creating /usr/src/packages/BUILD/debian/tmp/etc [ 220s] creating /usr/src/packages/BUILD/debian/tmp/etc/git-buildpackage [ 220s] copying gbp.conf -> /usr/src/packages/BUILD/debian/tmp/etc/git-buildpackage/ [ 220s] running install_egg_info [ 220s] running egg_info [ 220s] creating gbp.egg-info [ 220s] writing gbp.egg-info/PKG-INFO [ 220s] writing top-level names to gbp.egg-info/top_level.txt [ 220s] writing dependency_links to gbp.egg-info/dependency_links.txt [ 220s] writing entry points to gbp.egg-info/entry_points.txt [ 220s] writing manifest file 'gbp.egg-info/SOURCES.txt' [ 220s] reading manifest file 'gbp.egg-info/SOURCES.txt' [ 220s] writing manifest file 'gbp.egg-info/SOURCES.txt' [ 220s] Copying gbp.egg-info to /usr/src/packages/BUILD/debian/tmp/usr/lib/python2.7/dist-packages/gbp-0.9.9_tizen20180912.egg-info [ 220s] Skipping SOURCES.txt [ 220s] running install_scripts [ 220s] creating /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-import-orig-rpm -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-import-dscs -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-import-srpm -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-pbuilder -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/gbp-pull -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-import-dsc -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/gbp-create-remote-repo -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/gbp-pq -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/gbp-clone -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-buildpackage -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-dch -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-buildpackage-rpm -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-import-orig -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/gbp-pq-rpm -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] copying build/scripts-2.7/git-rpm-ch -> /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-import-orig-rpm to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-import-dscs to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-import-srpm to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-pbuilder to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/gbp-pull to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-import-dsc to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/gbp-create-remote-repo to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/gbp-pq to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/gbp-clone to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-buildpackage to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-dch to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-buildpackage-rpm to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-import-orig to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/gbp-pq-rpm to 775 [ 220s] changing mode of /usr/src/packages/BUILD/debian/tmp/usr/bin/git-rpm-ch to 775 [ 220s] Installing gbp script to /usr/src/packages/BUILD/debian/tmp/usr/bin [ 220s] dh_bash-completion [ 221s] dh_bash-completion: file-list parsing failed, installing as proper snippet [ 221s] mkdir -p debian/git-buildpackage//usr/share/zsh/vendor-completions/ [ 221s] install -m644 debian/git-buildpackage.zsh-completion \ [ 221s] debian/git-buildpackage//usr/share/zsh/vendor-completions//_gbp [ 221s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 221s] dh_install [ 221s] dh_installdocs [ 221s] dh_installchangelogs [ 221s] dh_installexamples [ 221s] dh_installman [ 222s] dh_python2 [ 222s] W: dh_python2:479: Please add dh-python package to Build-Depends [ 222s] dh_bugfiles [ 222s] dh_perl [ 222s] dh_link [ 222s] dh_strip_nondeterminism [ 222s] debian/rules override_dh_compress [ 222s] make[1]: Entering directory '/usr/src/packages/BUILD' [ 222s] dh_compress --exclude=usr/share/doc/git-buildpackage/examples/ [ 222s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 222s] dh_fixperms [ 223s] dh_missing [ 223s] dh_installdeb [ 223s] dh_gencontrol [ 223s] dpkg-gencontrol: warning: Depends field of package git-buildpackage-common: unknown substitution variable ${shlibs:Depends} [ 223s] dpkg-gencontrol: warning: Depends field of package git-buildpackage: unknown substitution variable ${shlibs:Depends} [ 223s] dpkg-gencontrol: warning: Depends field of package git-buildpackage-rpm: unknown substitution variable ${shlibs:Depends} [ 223s] dpkg-gencontrol: warning: package git-buildpackage-bb: unused substitution variable ${python:Versions} [ 223s] dpkg-gencontrol: warning: package git-buildpackage-rpm: unused substitution variable ${python:Versions} [ 223s] dpkg-gencontrol: warning: package git-buildpackage-common: unused substitution variable ${python:Versions} [ 223s] dpkg-gencontrol: warning: package git-buildpackage: unused substitution variable ${python:Versions} [ 223s] dh_md5sums [ 223s] dh_builddeb [ 223s] dpkg-deb: building package 'git-buildpackage-common' in '../git-buildpackage-common_0.9.9-tizen20180912_all.deb'. [ 223s] dpkg-deb: building package 'git-buildpackage-rpm' in '../git-buildpackage-rpm_0.9.9-tizen20180912_all.deb'. [ 223s] dpkg-deb: building package 'git-buildpackage-bb' in '../git-buildpackage-bb_0.9.9-tizen20180912_all.deb'. [ 223s] dpkg-deb: building package 'git-buildpackage' in '../git-buildpackage_0.9.9-tizen20180912_all.deb'. [ 224s] dpkg-genbuildinfo [ 224s] dpkg-genchanges >../git-buildpackage_0.9.9-tizen20180912_amd64.changes [ 224s] dpkg-genchanges: info: including full source code in upload [ 224s] dpkg-source --after-build BUILD [ 224s] dpkg-source: info: using options from BUILD/debian/source/options: --extend-diff-ignore=^(tests/test_rpm_data/.*|tests/component/rpm/data/.*|tests/component/deb/data/.*) --diff-ignore [ 225s] dpkg-buildpackage: info: full upload (original source is included) [ 225s] Warning: mkbaselibs missing in build root, skipping baselibs [ 225s] [ 225s] obspw02 finished "build git-buildpackage_0.9.9-tizen20180912.dsc" at Wed Feb 20 05:38:48 UTC 2019. [ 225s]