0s autopkgtest [00:01:19]: starting date and time: 2025-01-03 00:01:19+0000 0s autopkgtest [00:01:19]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [00:01:19]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.lrpnei47/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:debhelper --apt-upgrade debputy --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=debhelper/13.23ubuntu1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-14.secgroup --name adt-plucky-ppc64el-debputy-20250102-224156-juju-7f2275-prod-proposed-migration-environment-2-a4b677df-d52e-4538-b53b-c7d4c4fc74eb --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 53s autopkgtest [00:02:12]: testbed dpkg architecture: ppc64el 53s autopkgtest [00:02:12]: testbed apt version: 2.9.18 54s autopkgtest [00:02:13]: @@@@@@@@@@@@@@@@@@@@ test bed setup 54s autopkgtest [00:02:13]: testbed release detected to be: None 55s autopkgtest [00:02:14]: updating testbed package index (apt update) 55s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 55s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 55s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 55s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 55s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [648 kB] 56s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [58.3 kB] 56s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [10.1 kB] 56s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 56s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [65.9 kB] 56s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [756 B] 56s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [493 kB] 56s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [2584 B] 56s Fetched 1362 kB in 1s (1271 kB/s) 57s Reading package lists... 57s Reading package lists... 58s Building dependency tree... 58s Reading state information... 58s Calculating upgrade... 58s The following packages will be upgraded: 58s base-passwd bash-completion 58s 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 58s Need to get 269 kB of archives. 58s After this operation, 143 kB of additional disk space will be used. 58s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el base-passwd ppc64el 3.6.6 [55.2 kB] 58s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el bash-completion all 1:2.16.0-1 [214 kB] 59s Preconfiguring packages ... 59s Fetched 269 kB in 0s (570 kB/s) 59s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 73900 files and directories currently installed.) 59s Preparing to unpack .../base-passwd_3.6.6_ppc64el.deb ... 59s Unpacking base-passwd (3.6.6) over (3.6.5) ... 59s Setting up base-passwd (3.6.6) ... 59s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 73900 files and directories currently installed.) 59s Preparing to unpack .../bash-completion_1%3a2.16.0-1_all.deb ... 59s Unpacking bash-completion (1:2.16.0-1) over (1:2.14.0-2) ... 59s Setting up bash-completion (1:2.16.0-1) ... 59s Processing triggers for man-db (2.13.0-1) ... 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 61s autopkgtest [00:02:20]: upgrading testbed (apt dist-upgrade and autopurge) 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 62s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 62s Starting 2 pkgProblemResolver with broken count: 0 62s Done 62s Entering ResolveByKeep 62s 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Reading package lists... 63s Building dependency tree... 63s Reading state information... 63s Starting pkgProblemResolver with broken count: 0 63s Starting 2 pkgProblemResolver with broken count: 0 63s Done 63s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s autopkgtest [00:02:25]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 66s autopkgtest [00:02:25]: @@@@@@@@@@@@@@@@@@@@ apt-source debputy 67s Get:1 http://ftpmaster.internal/ubuntu plucky/universe debputy 0.1.58 (dsc) [2145 B] 67s Get:2 http://ftpmaster.internal/ubuntu plucky/universe debputy 0.1.58 (tar) [661 kB] 68s gpgv: Signature made Sun Dec 29 13:47:09 2024 UTC 68s gpgv: using RSA key F5E7199AEF5E5C67E555873F740D68888365D289 68s gpgv: issuer "niels@thykier.net" 68s gpgv: Can't check signature: No public key 68s dpkg-source: warning: cannot verify inline signature for ./debputy_0.1.58.dsc: no acceptable signature found 68s autopkgtest [00:02:27]: testing package debputy version 0.1.58 68s autopkgtest [00:02:27]: build not needed 69s autopkgtest [00:02:28]: test debputy-py.test: preparing testbed 69s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s Starting pkgProblemResolver with broken count: 0 69s Starting 2 pkgProblemResolver with broken count: 0 69s Done 69s The following NEW packages will be installed: 69s autoconf automake autopoint autotools-dev cpp cpp-14 69s cpp-14-powerpc64le-linux-gnu cpp-powerpc64le-linux-gnu debhelper debugedit 69s dh-autoreconf dh-debputy dh-strip-nondeterminism dwz gcc gcc-14 69s gcc-14-powerpc64le-linux-gnu gcc-powerpc64le-linux-gnu gettext 69s intltool-debian libarchive-zip-perl libasan8 libcc1-0 libdebhelper-perl 69s libfile-stripnondeterminism-perl libgcc-14-dev libgomp1 libisl23 libitm1 69s liblsan0 libmpc3 libpython3.13-minimal libpython3.13-stdlib libquadmath0 69s libtool libtsan2 libubsan1 m4 po-debconf python3-all python3-cattr 69s python3-colored python3-colorlog python3-debian python3-iniconfig 69s python3-lsprotocol python3-packaging python3-pluggy python3-pytest 69s python3-ruyaml python3.13 python3.13-minimal strip-nondeterminism 70s 0 upgraded, 53 newly installed, 0 to remove and 0 not upgraded. 70s Need to get 54.9 MB of archives. 70s After this operation, 194 MB of additional disk space will be used. 70s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el libpython3.13-minimal ppc64el 3.13.1-2 [883 kB] 70s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3.13-minimal ppc64el 3.13.1-2 [2496 kB] 71s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el m4 ppc64el 1.4.19-4build1 [278 kB] 71s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el autoconf all 2.72-3 [382 kB] 71s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el autotools-dev all 20220109.1 [44.9 kB] 71s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el automake all 1:1.16.5-1.3ubuntu1 [558 kB] 71s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el autopoint all 0.22.5-3 [616 kB] 71s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el libisl23 ppc64el 0.27-1 [882 kB] 71s Get:9 http://ftpmaster.internal/ubuntu plucky/main ppc64el libmpc3 ppc64el 1.3.1-1build2 [62.1 kB] 71s Get:10 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-14-powerpc64le-linux-gnu ppc64el 14.2.0-12ubuntu1 [10.5 MB] 72s Get:11 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-14 ppc64el 14.2.0-12ubuntu1 [1038 B] 72s Get:12 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-powerpc64le-linux-gnu ppc64el 4:14.1.0-2ubuntu1 [5456 B] 72s Get:13 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp ppc64el 4:14.1.0-2ubuntu1 [22.5 kB] 72s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libdebhelper-perl all 13.23ubuntu1 [95.1 kB] 72s Get:15 http://ftpmaster.internal/ubuntu plucky/main ppc64el libcc1-0 ppc64el 14.2.0-12ubuntu1 [48.1 kB] 72s Get:16 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgomp1 ppc64el 14.2.0-12ubuntu1 [161 kB] 72s Get:17 http://ftpmaster.internal/ubuntu plucky/main ppc64el libitm1 ppc64el 14.2.0-12ubuntu1 [32.1 kB] 72s Get:18 http://ftpmaster.internal/ubuntu plucky/main ppc64el libasan8 ppc64el 14.2.0-12ubuntu1 [2945 kB] 72s Get:19 http://ftpmaster.internal/ubuntu plucky/main ppc64el liblsan0 ppc64el 14.2.0-12ubuntu1 [1322 kB] 72s Get:20 http://ftpmaster.internal/ubuntu plucky/main ppc64el libtsan2 ppc64el 14.2.0-12ubuntu1 [2695 kB] 72s Get:21 http://ftpmaster.internal/ubuntu plucky/main ppc64el libubsan1 ppc64el 14.2.0-12ubuntu1 [1191 kB] 73s Get:22 http://ftpmaster.internal/ubuntu plucky/main ppc64el libquadmath0 ppc64el 14.2.0-12ubuntu1 [158 kB] 73s Get:23 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgcc-14-dev ppc64el 14.2.0-12ubuntu1 [1620 kB] 73s Get:24 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-14-powerpc64le-linux-gnu ppc64el 14.2.0-12ubuntu1 [20.6 MB] 73s Get:25 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-14 ppc64el 14.2.0-12ubuntu1 [533 kB] 73s Get:26 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-powerpc64le-linux-gnu ppc64el 4:14.1.0-2ubuntu1 [1222 B] 73s Get:27 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc ppc64el 4:14.1.0-2ubuntu1 [5006 B] 73s Get:28 http://ftpmaster.internal/ubuntu plucky/main ppc64el libtool all 2.4.7-8 [166 kB] 73s Get:29 http://ftpmaster.internal/ubuntu plucky/main ppc64el dh-autoreconf all 20 [16.1 kB] 73s Get:30 http://ftpmaster.internal/ubuntu plucky/main ppc64el libarchive-zip-perl all 1.68-1 [90.2 kB] 73s Get:31 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfile-stripnondeterminism-perl all 1.14.0-1 [20.1 kB] 73s Get:32 http://ftpmaster.internal/ubuntu plucky/main ppc64el dh-strip-nondeterminism all 1.14.0-1 [5058 B] 73s Get:33 http://ftpmaster.internal/ubuntu plucky/main ppc64el debugedit ppc64el 1:5.1-1 [52.1 kB] 73s Get:34 http://ftpmaster.internal/ubuntu plucky/main ppc64el dwz ppc64el 0.15-1build6 [142 kB] 73s Get:35 http://ftpmaster.internal/ubuntu plucky/main ppc64el gettext ppc64el 0.22.5-3 [1083 kB] 73s Get:36 http://ftpmaster.internal/ubuntu plucky/main ppc64el intltool-debian all 0.35.0+20060710.6 [23.2 kB] 73s Get:37 http://ftpmaster.internal/ubuntu plucky/main ppc64el po-debconf all 1.0.21+nmu1 [233 kB] 73s Get:38 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el debhelper all 13.23ubuntu1 [895 kB] 73s Get:39 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-colored all 2.2.4-1 [14.2 kB] 73s Get:40 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-colorlog all 6.9.0-1 [21.6 kB] 73s Get:41 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-debian all 0.1.49ubuntu3 [116 kB] 73s Get:42 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-ruyaml all 0.91.0-3 [107 kB] 73s Get:43 http://ftpmaster.internal/ubuntu plucky/universe ppc64el strip-nondeterminism all 1.14.0-1 [5552 B] 74s Get:44 http://ftpmaster.internal/ubuntu plucky/universe ppc64el dh-debputy all 0.1.58 [466 kB] 74s Get:45 http://ftpmaster.internal/ubuntu plucky/main ppc64el libpython3.13-stdlib ppc64el 3.13.1-2 [2131 kB] 74s Get:46 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3.13 ppc64el 3.13.1-2 [729 kB] 74s Get:47 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-all ppc64el 3.12.8-1 [892 B] 74s Get:48 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-cattr all 23.2.3-1ubuntu1 [38.3 kB] 74s Get:49 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-iniconfig all 1.1.1-2 [6024 B] 74s Get:50 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-lsprotocol all 2023.0.1-1 [58.3 kB] 74s Get:51 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-packaging all 24.2-1 [51.5 kB] 74s Get:52 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-pluggy all 1.5.0-1 [21.0 kB] 74s Get:53 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-pytest all 8.3.3-1 [251 kB] 74s Fetched 54.9 MB in 4s (13.1 MB/s) 74s Selecting previously unselected package libpython3.13-minimal:ppc64el. 74s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 74025 files and directories currently installed.) 74s Preparing to unpack .../00-libpython3.13-minimal_3.13.1-2_ppc64el.deb ... 74s Unpacking libpython3.13-minimal:ppc64el (3.13.1-2) ... 74s Selecting previously unselected package python3.13-minimal. 74s Preparing to unpack .../01-python3.13-minimal_3.13.1-2_ppc64el.deb ... 74s Unpacking python3.13-minimal (3.13.1-2) ... 74s Selecting previously unselected package m4. 74s Preparing to unpack .../02-m4_1.4.19-4build1_ppc64el.deb ... 74s Unpacking m4 (1.4.19-4build1) ... 74s Selecting previously unselected package autoconf. 74s Preparing to unpack .../03-autoconf_2.72-3_all.deb ... 74s Unpacking autoconf (2.72-3) ... 74s Selecting previously unselected package autotools-dev. 74s Preparing to unpack .../04-autotools-dev_20220109.1_all.deb ... 74s Unpacking autotools-dev (20220109.1) ... 74s Selecting previously unselected package automake. 74s Preparing to unpack .../05-automake_1%3a1.16.5-1.3ubuntu1_all.deb ... 74s Unpacking automake (1:1.16.5-1.3ubuntu1) ... 74s Selecting previously unselected package autopoint. 74s Preparing to unpack .../06-autopoint_0.22.5-3_all.deb ... 74s Unpacking autopoint (0.22.5-3) ... 74s Selecting previously unselected package libisl23:ppc64el. 74s Preparing to unpack .../07-libisl23_0.27-1_ppc64el.deb ... 74s Unpacking libisl23:ppc64el (0.27-1) ... 74s Selecting previously unselected package libmpc3:ppc64el. 74s Preparing to unpack .../08-libmpc3_1.3.1-1build2_ppc64el.deb ... 74s Unpacking libmpc3:ppc64el (1.3.1-1build2) ... 74s Selecting previously unselected package cpp-14-powerpc64le-linux-gnu. 74s Preparing to unpack .../09-cpp-14-powerpc64le-linux-gnu_14.2.0-12ubuntu1_ppc64el.deb ... 74s Unpacking cpp-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 74s Selecting previously unselected package cpp-14. 74s Preparing to unpack .../10-cpp-14_14.2.0-12ubuntu1_ppc64el.deb ... 74s Unpacking cpp-14 (14.2.0-12ubuntu1) ... 74s Selecting previously unselected package cpp-powerpc64le-linux-gnu. 74s Preparing to unpack .../11-cpp-powerpc64le-linux-gnu_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 74s Unpacking cpp-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 74s Selecting previously unselected package cpp. 74s Preparing to unpack .../12-cpp_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 74s Unpacking cpp (4:14.1.0-2ubuntu1) ... 74s Selecting previously unselected package libdebhelper-perl. 74s Preparing to unpack .../13-libdebhelper-perl_13.23ubuntu1_all.deb ... 74s Unpacking libdebhelper-perl (13.23ubuntu1) ... 74s Selecting previously unselected package libcc1-0:ppc64el. 74s Preparing to unpack .../14-libcc1-0_14.2.0-12ubuntu1_ppc64el.deb ... 74s Unpacking libcc1-0:ppc64el (14.2.0-12ubuntu1) ... 74s Selecting previously unselected package libgomp1:ppc64el. 74s Preparing to unpack .../15-libgomp1_14.2.0-12ubuntu1_ppc64el.deb ... 74s Unpacking libgomp1:ppc64el (14.2.0-12ubuntu1) ... 74s Selecting previously unselected package libitm1:ppc64el. 74s Preparing to unpack .../16-libitm1_14.2.0-12ubuntu1_ppc64el.deb ... 74s Unpacking libitm1:ppc64el (14.2.0-12ubuntu1) ... 74s Selecting previously unselected package libasan8:ppc64el. 75s Preparing to unpack .../17-libasan8_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking libasan8:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package liblsan0:ppc64el. 75s Preparing to unpack .../18-liblsan0_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking liblsan0:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package libtsan2:ppc64el. 75s Preparing to unpack .../19-libtsan2_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking libtsan2:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package libubsan1:ppc64el. 75s Preparing to unpack .../20-libubsan1_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking libubsan1:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package libquadmath0:ppc64el. 75s Preparing to unpack .../21-libquadmath0_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking libquadmath0:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package libgcc-14-dev:ppc64el. 75s Preparing to unpack .../22-libgcc-14-dev_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking libgcc-14-dev:ppc64el (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package gcc-14-powerpc64le-linux-gnu. 75s Preparing to unpack .../23-gcc-14-powerpc64le-linux-gnu_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking gcc-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package gcc-14. 75s Preparing to unpack .../24-gcc-14_14.2.0-12ubuntu1_ppc64el.deb ... 75s Unpacking gcc-14 (14.2.0-12ubuntu1) ... 75s Selecting previously unselected package gcc-powerpc64le-linux-gnu. 75s Preparing to unpack .../25-gcc-powerpc64le-linux-gnu_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 75s Unpacking gcc-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 75s Selecting previously unselected package gcc. 75s Preparing to unpack .../26-gcc_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 75s Unpacking gcc (4:14.1.0-2ubuntu1) ... 75s Selecting previously unselected package libtool. 75s Preparing to unpack .../27-libtool_2.4.7-8_all.deb ... 75s Unpacking libtool (2.4.7-8) ... 75s Selecting previously unselected package dh-autoreconf. 75s Preparing to unpack .../28-dh-autoreconf_20_all.deb ... 75s Unpacking dh-autoreconf (20) ... 75s Selecting previously unselected package libarchive-zip-perl. 75s Preparing to unpack .../29-libarchive-zip-perl_1.68-1_all.deb ... 75s Unpacking libarchive-zip-perl (1.68-1) ... 75s Selecting previously unselected package libfile-stripnondeterminism-perl. 75s Preparing to unpack .../30-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... 75s Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... 75s Selecting previously unselected package dh-strip-nondeterminism. 75s Preparing to unpack .../31-dh-strip-nondeterminism_1.14.0-1_all.deb ... 75s Unpacking dh-strip-nondeterminism (1.14.0-1) ... 75s Selecting previously unselected package debugedit. 75s Preparing to unpack .../32-debugedit_1%3a5.1-1_ppc64el.deb ... 75s Unpacking debugedit (1:5.1-1) ... 75s Selecting previously unselected package dwz. 75s Preparing to unpack .../33-dwz_0.15-1build6_ppc64el.deb ... 75s Unpacking dwz (0.15-1build6) ... 75s Selecting previously unselected package gettext. 75s Preparing to unpack .../34-gettext_0.22.5-3_ppc64el.deb ... 75s Unpacking gettext (0.22.5-3) ... 75s Selecting previously unselected package intltool-debian. 75s Preparing to unpack .../35-intltool-debian_0.35.0+20060710.6_all.deb ... 75s Unpacking intltool-debian (0.35.0+20060710.6) ... 75s Selecting previously unselected package po-debconf. 75s Preparing to unpack .../36-po-debconf_1.0.21+nmu1_all.deb ... 75s Unpacking po-debconf (1.0.21+nmu1) ... 75s Selecting previously unselected package debhelper. 75s Preparing to unpack .../37-debhelper_13.23ubuntu1_all.deb ... 75s Unpacking debhelper (13.23ubuntu1) ... 75s Selecting previously unselected package python3-colored. 75s Preparing to unpack .../38-python3-colored_2.2.4-1_all.deb ... 75s Unpacking python3-colored (2.2.4-1) ... 75s Selecting previously unselected package python3-colorlog. 75s Preparing to unpack .../39-python3-colorlog_6.9.0-1_all.deb ... 75s Unpacking python3-colorlog (6.9.0-1) ... 75s Selecting previously unselected package python3-debian. 75s Preparing to unpack .../40-python3-debian_0.1.49ubuntu3_all.deb ... 75s Unpacking python3-debian (0.1.49ubuntu3) ... 75s Selecting previously unselected package python3-ruyaml. 75s Preparing to unpack .../41-python3-ruyaml_0.91.0-3_all.deb ... 75s Unpacking python3-ruyaml (0.91.0-3) ... 75s Selecting previously unselected package strip-nondeterminism. 75s Preparing to unpack .../42-strip-nondeterminism_1.14.0-1_all.deb ... 75s Unpacking strip-nondeterminism (1.14.0-1) ... 75s Selecting previously unselected package dh-debputy. 75s Preparing to unpack .../43-dh-debputy_0.1.58_all.deb ... 75s Unpacking dh-debputy (0.1.58) ... 76s Selecting previously unselected package libpython3.13-stdlib:ppc64el. 76s Preparing to unpack .../44-libpython3.13-stdlib_3.13.1-2_ppc64el.deb ... 76s Unpacking libpython3.13-stdlib:ppc64el (3.13.1-2) ... 76s Selecting previously unselected package python3.13. 76s Preparing to unpack .../45-python3.13_3.13.1-2_ppc64el.deb ... 76s Unpacking python3.13 (3.13.1-2) ... 76s Selecting previously unselected package python3-all. 76s Preparing to unpack .../46-python3-all_3.12.8-1_ppc64el.deb ... 76s Unpacking python3-all (3.12.8-1) ... 76s Selecting previously unselected package python3-cattr. 76s Preparing to unpack .../47-python3-cattr_23.2.3-1ubuntu1_all.deb ... 76s Unpacking python3-cattr (23.2.3-1ubuntu1) ... 76s Selecting previously unselected package python3-iniconfig. 76s Preparing to unpack .../48-python3-iniconfig_1.1.1-2_all.deb ... 76s Unpacking python3-iniconfig (1.1.1-2) ... 76s Selecting previously unselected package python3-lsprotocol. 76s Preparing to unpack .../49-python3-lsprotocol_2023.0.1-1_all.deb ... 76s Unpacking python3-lsprotocol (2023.0.1-1) ... 76s Selecting previously unselected package python3-packaging. 76s Preparing to unpack .../50-python3-packaging_24.2-1_all.deb ... 76s Unpacking python3-packaging (24.2-1) ... 76s Selecting previously unselected package python3-pluggy. 76s Preparing to unpack .../51-python3-pluggy_1.5.0-1_all.deb ... 76s Unpacking python3-pluggy (1.5.0-1) ... 76s Selecting previously unselected package python3-pytest. 76s Preparing to unpack .../52-python3-pytest_8.3.3-1_all.deb ... 76s Unpacking python3-pytest (8.3.3-1) ... 76s Setting up python3-iniconfig (1.1.1-2) ... 76s Setting up python3-colorlog (6.9.0-1) ... 76s Setting up libarchive-zip-perl (1.68-1) ... 76s Setting up libdebhelper-perl (13.23ubuntu1) ... 76s Setting up m4 (1.4.19-4build1) ... 76s Setting up libgomp1:ppc64el (14.2.0-12ubuntu1) ... 76s Setting up libpython3.13-minimal:ppc64el (3.13.1-2) ... 76s Setting up autotools-dev (20220109.1) ... 76s Setting up python3-packaging (24.2-1) ... 76s Setting up python3-cattr (23.2.3-1ubuntu1) ... 77s Setting up python3-debian (0.1.49ubuntu3) ... 77s Setting up libquadmath0:ppc64el (14.2.0-12ubuntu1) ... 77s Setting up libmpc3:ppc64el (1.3.1-1build2) ... 77s Setting up autopoint (0.22.5-3) ... 77s Setting up autoconf (2.72-3) ... 77s Setting up python3-pluggy (1.5.0-1) ... 77s Setting up libubsan1:ppc64el (14.2.0-12ubuntu1) ... 77s Setting up dwz (0.15-1build6) ... 77s Setting up libasan8:ppc64el (14.2.0-12ubuntu1) ... 77s Setting up debugedit (1:5.1-1) ... 77s Setting up python3.13-minimal (3.13.1-2) ... 78s Setting up python3-colored (2.2.4-1) ... 78s Setting up libtsan2:ppc64el (14.2.0-12ubuntu1) ... 78s Setting up libisl23:ppc64el (0.27-1) ... 78s Setting up python3-ruyaml (0.91.0-3) ... 78s Setting up libpython3.13-stdlib:ppc64el (3.13.1-2) ... 78s Setting up libcc1-0:ppc64el (14.2.0-12ubuntu1) ... 78s Setting up liblsan0:ppc64el (14.2.0-12ubuntu1) ... 78s Setting up libitm1:ppc64el (14.2.0-12ubuntu1) ... 78s Setting up automake (1:1.16.5-1.3ubuntu1) ... 78s update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode 78s Setting up libfile-stripnondeterminism-perl (1.14.0-1) ... 78s Setting up gettext (0.22.5-3) ... 78s Setting up python3-lsprotocol (2023.0.1-1) ... 79s Setting up python3.13 (3.13.1-2) ... 80s Setting up python3-pytest (8.3.3-1) ... 80s Setting up python3-all (3.12.8-1) ... 80s Setting up strip-nondeterminism (1.14.0-1) ... 80s Setting up intltool-debian (0.35.0+20060710.6) ... 80s Setting up cpp-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 80s Setting up cpp-14 (14.2.0-12ubuntu1) ... 80s Setting up dh-strip-nondeterminism (1.14.0-1) ... 80s Setting up libgcc-14-dev:ppc64el (14.2.0-12ubuntu1) ... 80s Setting up cpp-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 80s Setting up gcc-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 80s Setting up po-debconf (1.0.21+nmu1) ... 80s Setting up gcc-14 (14.2.0-12ubuntu1) ... 80s Setting up gcc-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 80s Setting up cpp (4:14.1.0-2ubuntu1) ... 80s Setting up libtool (2.4.7-8) ... 80s Setting up gcc (4:14.1.0-2ubuntu1) ... 80s Setting up dh-autoreconf (20) ... 80s Setting up debhelper (13.23ubuntu1) ... 80s Setting up dh-debputy (0.1.58) ... 81s Processing triggers for libc-bin (2.40-4ubuntu1) ... 81s Processing triggers for systemd (257-2ubuntu1) ... 81s Processing triggers for man-db (2.13.0-1) ... 82s Processing triggers for install-info (7.1.1-1) ... 83s autopkgtest [00:02:42]: test debputy-py.test: [----------------------- 83s + mkdir /tmp/autopkgtest.WOc61X/autopkgtest_tmp/debian 83s + cp -r pyproject.toml tests/ /tmp/autopkgtest.WOc61X/autopkgtest_tmp 83s + cp -a debian/control /tmp/autopkgtest.WOc61X/autopkgtest_tmp/debian 83s + export PYTHONWARNINGS=d 83s + export DEBPUTY_TEST_AGAINST_INSTALLED_PLUGINS=uninstalled 83s + DEBPUTY_PYTHONPATH=/usr/share/dh-debputy 83s + PYTHOHPATH= 83s + [ ] 83s + PYTHOHPATH=/usr/share/dh-debputy 83s + export DEBPUTY_REQUIRE_LIBCAP=1 83s + cd /tmp/autopkgtest.WOc61X/autopkgtest_tmp/ 83s + py3versions -s 83s ---------------------------------------------- 83s Testing with python3.13 83s ---------------------------------------------- 83s + echo ---------------------------------------------- 83s + echo Testing with python3.13 83s + echo ---------------------------------------------- 83s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C python3.13 -m pytest 86s ============================= test session starts ============================== 86s platform linux -- Python 3.13.1, pytest-8.3.3, pluggy-1.5.0 86s rootdir: /tmp/autopkgtest.WOc61X/autopkgtest_tmp 86s configfile: pyproject.toml 86s testpaths: src, tests, self-hosting-plugins 86s plugins: typeguard-4.4.1 86s collected 421 items 86s 86s tests/lint_tests/test_lint_changelog.py .... [ 0%] 86s tests/lint_tests/test_lint_dcpy.py ..... [ 2%] 87s tests/lint_tests/test_lint_dctrl.py .ss.................s.s............. [ 10%] 87s .....s. [ 12%] 87s tests/lint_tests/test_lint_debputy.py ..s... [ 13%] 87s tests/lint_tests/test_lint_dpatches_series.py ... [ 14%] 87s tests/lint_tests/test_lint_dtctrl.py .s [ 14%] 87s tests/lint_tests/test_lint_upstream_metadata.py . [ 15%] 87s tests/lsp_tests/test_debpkg_metadata.py ........... [ 17%] 87s tests/lsp_tests/test_lsp_dctrl.py ssssssssssssssss [ 21%] 87s tests/lsp_tests/test_lsp_debputy_manifest_completer.py sssssssss [ 23%] 87s tests/lsp_tests/test_lsp_debputy_manifest_hover.py ssssssssss [ 26%] 87s tests/lsp_tests/test_lsp_dpatches_series.py s [ 26%] 87s tests/plugin_tests/gnome_test.py .... [ 27%] 87s tests/plugin_tests/grantlee_test.py . [ 27%] 87s tests/plugin_tests/numpy3_test.py .. [ 28%] 87s tests/plugin_tests/perl-openssl_test.py . [ 28%] 87s tests/test_alternatives.py . [ 28%] 87s tests/test_apply_compression.py . [ 28%] 87s tests/test_architecture.py . [ 28%] 87s tests/test_cross_check_precheck.py ............... [ 32%] 87s tests/test_deb_packaging_support.py .......... [ 34%] 88s tests/test_debputy_plugin.py ........................................... [ 45%] 88s .. [ 45%] 88s tests/test_declarative_parser.py ............ [ 48%] 89s tests/test_fs_metadata.py .................. [ 52%] 89s tests/test_install_rules.py ............ [ 55%] 89s tests/test_interpreter.py ............. [ 58%] 89s tests/test_migrations.py .................................. [ 66%] 89s tests/test_output_filename.py ...... [ 68%] 89s tests/test_packager_provided_files.py ....................s.s [ 73%] 89s tests/test_packer_pack.py . [ 73%] 89s tests/test_parser.py ............................................. [ 84%] 89s tests/test_path.py . [ 84%] 89s tests/test_plugin_tester.py ....................... [ 90%] 90s tests/test_style.py ....x....... [ 93%] 90s tests/test_substitute.py ...... [ 94%] 90s tests/test_symbolic_mode.py ........ [ 96%] 90s tests/test_symlink_normalization.py .......... [ 98%] 90s tests/test_utils.py ..... [100%] 90s 90s ================== 375 passed, 45 skipped, 1 xfailed in 5.17s ================== 90s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C.UTF-8 python3.13 -m pytest 91s ============================= test session starts ============================== 91s platform linux -- Python 3.13.1, pytest-8.3.3, pluggy-1.5.0 91s rootdir: /tmp/autopkgtest.WOc61X/autopkgtest_tmp 91s configfile: pyproject.toml 91s testpaths: src, tests, self-hosting-plugins 91s plugins: typeguard-4.4.1 91s collected 421 items 91s 91s tests/lint_tests/test_lint_changelog.py .... [ 0%] 91s tests/lint_tests/test_lint_dcpy.py ..... [ 2%] 93s tests/lint_tests/test_lint_dctrl.py .ss.................s.s............. [ 10%] 93s .....s. [ 12%] 93s tests/lint_tests/test_lint_debputy.py ..s... [ 13%] 93s tests/lint_tests/test_lint_dpatches_series.py ... [ 14%] 93s tests/lint_tests/test_lint_dtctrl.py .s [ 14%] 93s tests/lint_tests/test_lint_upstream_metadata.py . [ 15%] 93s tests/lsp_tests/test_debpkg_metadata.py ........... [ 17%] 93s tests/lsp_tests/test_lsp_dctrl.py ssssssssssssssss [ 21%] 93s tests/lsp_tests/test_lsp_debputy_manifest_completer.py sssssssss [ 23%] 93s tests/lsp_tests/test_lsp_debputy_manifest_hover.py ssssssssss [ 26%] 93s tests/lsp_tests/test_lsp_dpatches_series.py s [ 26%] 93s tests/plugin_tests/gnome_test.py .... [ 27%] 93s tests/plugin_tests/grantlee_test.py . [ 27%] 93s tests/plugin_tests/numpy3_test.py .. [ 28%] 93s tests/plugin_tests/perl-openssl_test.py . [ 28%] 93s tests/test_alternatives.py . [ 28%] 93s tests/test_apply_compression.py . [ 28%] 93s tests/test_architecture.py . [ 28%] 93s tests/test_cross_check_precheck.py ............... [ 32%] 93s tests/test_deb_packaging_support.py .......... [ 34%] 94s tests/test_debputy_plugin.py ........................................... [ 45%] 94s .. [ 45%] 94s tests/test_declarative_parser.py ............ [ 48%] 94s tests/test_fs_metadata.py .................. [ 52%] 94s tests/test_install_rules.py ............ [ 55%] 94s tests/test_interpreter.py ............. [ 58%] 94s tests/test_migrations.py .................................. [ 66%] 95s tests/test_output_filename.py ...... [ 68%] 95s tests/test_packager_provided_files.py ....................s.s [ 73%] 95s tests/test_packer_pack.py . [ 73%] 95s tests/test_parser.py ............................................. [ 84%] 95s tests/test_path.py . [ 84%] 95s tests/test_plugin_tester.py ....................... [ 90%] 95s tests/test_style.py ....x....... [ 93%] 95s tests/test_substitute.py ...... [ 94%] 95s tests/test_symbolic_mode.py ........ [ 96%] 95s tests/test_symlink_normalization.py .......... [ 98%] 95s tests/test_utils.py ..... [100%] 95s 95s ================== 375 passed, 45 skipped, 1 xfailed in 4.41s ================== 95s ---------------------------------------------- 95s Testing with python3.12 95s ---------------------------------------------- 95s + echo ---------------------------------------------- 95s + echo Testing with python3.12 95s + echo ---------------------------------------------- 95s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C python3.12 -m pytest 98s ============================= test session starts ============================== 98s platform linux -- Python 3.12.8, pytest-8.3.3, pluggy-1.5.0 98s rootdir: /tmp/autopkgtest.WOc61X/autopkgtest_tmp 98s configfile: pyproject.toml 98s testpaths: src, tests, self-hosting-plugins 98s plugins: typeguard-4.4.1 98s collected 421 items 98s 98s tests/lint_tests/test_lint_changelog.py .... [ 0%] 98s tests/lint_tests/test_lint_dcpy.py ..... [ 2%] 99s tests/lint_tests/test_lint_dctrl.py .ss.................s.s............. [ 10%] 99s .....s. [ 12%] 99s tests/lint_tests/test_lint_debputy.py ..s... [ 13%] 99s tests/lint_tests/test_lint_dpatches_series.py ... [ 14%] 99s tests/lint_tests/test_lint_dtctrl.py .s [ 14%] 99s tests/lint_tests/test_lint_upstream_metadata.py . [ 15%] 99s tests/lsp_tests/test_debpkg_metadata.py ........... [ 17%] 99s tests/lsp_tests/test_lsp_dctrl.py ssssssssssssssss [ 21%] 99s tests/lsp_tests/test_lsp_debputy_manifest_completer.py sssssssss [ 23%] 99s tests/lsp_tests/test_lsp_debputy_manifest_hover.py ssssssssss [ 26%] 99s tests/lsp_tests/test_lsp_dpatches_series.py s [ 26%] 99s tests/plugin_tests/gnome_test.py .... [ 27%] 99s tests/plugin_tests/grantlee_test.py . [ 27%] 99s tests/plugin_tests/numpy3_test.py .. [ 28%] 99s tests/plugin_tests/perl-openssl_test.py . [ 28%] 99s tests/test_alternatives.py . [ 28%] 99s tests/test_apply_compression.py . [ 28%] 100s tests/test_architecture.py . [ 28%] 100s tests/test_cross_check_precheck.py ............... [ 32%] 100s tests/test_deb_packaging_support.py .......... [ 34%] 101s tests/test_debputy_plugin.py ........................................... [ 45%] 101s .. [ 45%] 101s tests/test_declarative_parser.py ............ [ 48%] 101s tests/test_fs_metadata.py .................. [ 52%] 101s tests/test_install_rules.py ............ [ 55%] 101s tests/test_interpreter.py ............. [ 58%] 101s tests/test_migrations.py .................................. [ 66%] 101s tests/test_output_filename.py ...... [ 68%] 101s tests/test_packager_provided_files.py ....................s.s [ 73%] 101s tests/test_packer_pack.py . [ 73%] 102s tests/test_parser.py ............................................. [ 84%] 102s tests/test_path.py . [ 84%] 102s tests/test_plugin_tester.py ....................... [ 90%] 102s tests/test_style.py ....x....... [ 93%] 102s tests/test_substitute.py ...... [ 94%] 102s tests/test_symbolic_mode.py ........ [ 96%] 102s tests/test_symlink_normalization.py .......... [ 98%] 102s tests/test_utils.py ..... [100%] 102s 102s ================== 375 passed, 45 skipped, 1 xfailed in 5.60s ================== 102s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C.UTF-8 python3.12 -m pytest 103s ============================= test session starts ============================== 103s platform linux -- Python 3.12.8, pytest-8.3.3, pluggy-1.5.0 103s rootdir: /tmp/autopkgtest.WOc61X/autopkgtest_tmp 103s configfile: pyproject.toml 103s testpaths: src, tests, self-hosting-plugins 103s plugins: typeguard-4.4.1 103s collected 421 items 103s 103s tests/lint_tests/test_lint_changelog.py .... [ 0%] 103s tests/lint_tests/test_lint_dcpy.py ..... [ 2%] 105s tests/lint_tests/test_lint_dctrl.py .ss.................s.s............. [ 10%] 105s .....s. [ 12%] 105s tests/lint_tests/test_lint_debputy.py ..s... [ 13%] 105s tests/lint_tests/test_lint_dpatches_series.py ... [ 14%] 105s tests/lint_tests/test_lint_dtctrl.py .s [ 14%] 105s tests/lint_tests/test_lint_upstream_metadata.py . [ 15%] 105s tests/lsp_tests/test_debpkg_metadata.py ........... [ 17%] 105s tests/lsp_tests/test_lsp_dctrl.py ssssssssssssssss [ 21%] 105s tests/lsp_tests/test_lsp_debputy_manifest_completer.py sssssssss [ 23%] 105s tests/lsp_tests/test_lsp_debputy_manifest_hover.py ssssssssss [ 26%] 105s tests/lsp_tests/test_lsp_dpatches_series.py s [ 26%] 105s tests/plugin_tests/gnome_test.py .... [ 27%] 105s tests/plugin_tests/grantlee_test.py . [ 27%] 105s tests/plugin_tests/numpy3_test.py .. [ 28%] 105s tests/plugin_tests/perl-openssl_test.py . [ 28%] 105s tests/test_alternatives.py . [ 28%] 105s tests/test_apply_compression.py . [ 28%] 105s tests/test_architecture.py . [ 28%] 105s tests/test_cross_check_precheck.py ............... [ 32%] 105s tests/test_deb_packaging_support.py .......... [ 34%] 106s tests/test_debputy_plugin.py ........................................... [ 45%] 106s .. [ 45%] 106s tests/test_declarative_parser.py ............ [ 48%] 106s tests/test_fs_metadata.py .................. [ 52%] 106s tests/test_install_rules.py ............ [ 55%] 106s tests/test_interpreter.py ............. [ 58%] 107s tests/test_migrations.py .................................. [ 66%] 107s tests/test_output_filename.py ...... [ 68%] 107s tests/test_packager_provided_files.py ....................s.s [ 73%] 107s tests/test_packer_pack.py . [ 73%] 107s tests/test_parser.py ............................................. [ 84%] 107s tests/test_path.py . [ 84%] 107s tests/test_plugin_tester.py ....................... [ 90%] 108s tests/test_style.py ....x....... [ 93%] 108s tests/test_substitute.py ...... [ 94%] 108s tests/test_symbolic_mode.py ........ [ 96%] 108s tests/test_symlink_normalization.py .......... [ 98%] 108s tests/test_utils.py ..... [100%] 108s 108s ================== 375 passed, 45 skipped, 1 xfailed in 4.54s ================== 108s autopkgtest [00:03:07]: test debputy-py.test: -----------------------] 108s autopkgtest [00:03:07]: test debputy-py.test: - - - - - - - - - - results - - - - - - - - - - 108s debputy-py.test PASS 109s autopkgtest [00:03:08]: test debputy-cli: preparing testbed 177s autopkgtest [00:04:16]: testbed dpkg architecture: ppc64el 178s autopkgtest [00:04:17]: testbed apt version: 2.9.18 178s autopkgtest [00:04:17]: @@@@@@@@@@@@@@@@@@@@ test bed setup 178s autopkgtest [00:04:17]: testbed release detected to be: plucky 179s autopkgtest [00:04:18]: updating testbed package index (apt update) 179s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 179s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 179s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 179s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 179s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [648 kB] 180s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 180s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [10.1 kB] 180s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [58.3 kB] 180s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [65.9 kB] 180s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [756 B] 180s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [493 kB] 180s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [2584 B] 180s Fetched 1362 kB in 1s (1460 kB/s) 181s Reading package lists... 181s Reading package lists... 181s Building dependency tree... 181s Reading state information... 181s Calculating upgrade... 182s The following packages will be upgraded: 182s base-passwd bash-completion 182s 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 182s Need to get 269 kB of archives. 182s After this operation, 143 kB of additional disk space will be used. 182s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el base-passwd ppc64el 3.6.6 [55.2 kB] 182s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el bash-completion all 1:2.16.0-1 [214 kB] 182s Preconfiguring packages ... 182s Fetched 269 kB in 0s (558 kB/s) 183s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 73900 files and directories currently installed.) 183s Preparing to unpack .../base-passwd_3.6.6_ppc64el.deb ... 183s Unpacking base-passwd (3.6.6) over (3.6.5) ... 183s Setting up base-passwd (3.6.6) ... 183s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 73900 files and directories currently installed.) 183s Preparing to unpack .../bash-completion_1%3a2.16.0-1_all.deb ... 183s Unpacking bash-completion (1:2.16.0-1) over (1:2.14.0-2) ... 183s Setting up bash-completion (1:2.16.0-1) ... 183s Processing triggers for man-db (2.13.0-1) ... 184s Reading package lists... 184s Building dependency tree... 184s Reading state information... 184s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 185s autopkgtest [00:04:24]: upgrading testbed (apt dist-upgrade and autopurge) 185s Reading package lists... 185s Building dependency tree... 185s Reading state information... 185s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 185s Starting 2 pkgProblemResolver with broken count: 0 185s Done 185s Entering ResolveByKeep 186s 186s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 186s Reading package lists... 186s Building dependency tree... 186s Reading state information... 186s Starting pkgProblemResolver with broken count: 0 186s Starting 2 pkgProblemResolver with broken count: 0 186s Done 187s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 189s Reading package lists... 189s Building dependency tree... 189s Reading state information... 189s Starting pkgProblemResolver with broken count: 0 190s Starting 2 pkgProblemResolver with broken count: 0 190s Done 190s The following NEW packages will be installed: 190s autoconf automake autopoint autotools-dev cpp cpp-14 190s cpp-14-powerpc64le-linux-gnu cpp-powerpc64le-linux-gnu debhelper debugedit 190s dh-autoreconf dh-debputy dh-strip-nondeterminism dwz gcc gcc-14 190s gcc-14-powerpc64le-linux-gnu gcc-powerpc64le-linux-gnu gettext 190s intltool-debian libarchive-zip-perl libasan8 libcc1-0 libdebhelper-perl 190s libfile-stripnondeterminism-perl libgcc-14-dev libgomp1 libisl23 libitm1 190s liblsan0 libmpc3 libquadmath0 libtool libtsan2 libubsan1 m4 po-debconf 190s python3-colored python3-colorlog python3-debian python3-ruyaml 190s strip-nondeterminism 190s 0 upgraded, 42 newly installed, 0 to remove and 0 not upgraded. 190s Need to get 48.2 MB of archives. 190s After this operation, 166 MB of additional disk space will be used. 190s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el m4 ppc64el 1.4.19-4build1 [278 kB] 190s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el autoconf all 2.72-3 [382 kB] 190s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el autotools-dev all 20220109.1 [44.9 kB] 190s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el automake all 1:1.16.5-1.3ubuntu1 [558 kB] 190s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el autopoint all 0.22.5-3 [616 kB] 190s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el libisl23 ppc64el 0.27-1 [882 kB] 190s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el libmpc3 ppc64el 1.3.1-1build2 [62.1 kB] 190s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-14-powerpc64le-linux-gnu ppc64el 14.2.0-12ubuntu1 [10.5 MB] 191s Get:9 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-14 ppc64el 14.2.0-12ubuntu1 [1038 B] 191s Get:10 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp-powerpc64le-linux-gnu ppc64el 4:14.1.0-2ubuntu1 [5456 B] 191s Get:11 http://ftpmaster.internal/ubuntu plucky/main ppc64el cpp ppc64el 4:14.1.0-2ubuntu1 [22.5 kB] 191s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libdebhelper-perl all 13.23ubuntu1 [95.1 kB] 191s Get:13 http://ftpmaster.internal/ubuntu plucky/main ppc64el libcc1-0 ppc64el 14.2.0-12ubuntu1 [48.1 kB] 191s Get:14 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgomp1 ppc64el 14.2.0-12ubuntu1 [161 kB] 191s Get:15 http://ftpmaster.internal/ubuntu plucky/main ppc64el libitm1 ppc64el 14.2.0-12ubuntu1 [32.1 kB] 191s Get:16 http://ftpmaster.internal/ubuntu plucky/main ppc64el libasan8 ppc64el 14.2.0-12ubuntu1 [2945 kB] 191s Get:17 http://ftpmaster.internal/ubuntu plucky/main ppc64el liblsan0 ppc64el 14.2.0-12ubuntu1 [1322 kB] 191s Get:18 http://ftpmaster.internal/ubuntu plucky/main ppc64el libtsan2 ppc64el 14.2.0-12ubuntu1 [2695 kB] 191s Get:19 http://ftpmaster.internal/ubuntu plucky/main ppc64el libubsan1 ppc64el 14.2.0-12ubuntu1 [1191 kB] 191s Get:20 http://ftpmaster.internal/ubuntu plucky/main ppc64el libquadmath0 ppc64el 14.2.0-12ubuntu1 [158 kB] 191s Get:21 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgcc-14-dev ppc64el 14.2.0-12ubuntu1 [1620 kB] 191s Get:22 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-14-powerpc64le-linux-gnu ppc64el 14.2.0-12ubuntu1 [20.6 MB] 191s Get:23 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-14 ppc64el 14.2.0-12ubuntu1 [533 kB] 191s Get:24 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-powerpc64le-linux-gnu ppc64el 4:14.1.0-2ubuntu1 [1222 B] 191s Get:25 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc ppc64el 4:14.1.0-2ubuntu1 [5006 B] 191s Get:26 http://ftpmaster.internal/ubuntu plucky/main ppc64el libtool all 2.4.7-8 [166 kB] 191s Get:27 http://ftpmaster.internal/ubuntu plucky/main ppc64el dh-autoreconf all 20 [16.1 kB] 191s Get:28 http://ftpmaster.internal/ubuntu plucky/main ppc64el libarchive-zip-perl all 1.68-1 [90.2 kB] 191s Get:29 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfile-stripnondeterminism-perl all 1.14.0-1 [20.1 kB] 191s Get:30 http://ftpmaster.internal/ubuntu plucky/main ppc64el dh-strip-nondeterminism all 1.14.0-1 [5058 B] 191s Get:31 http://ftpmaster.internal/ubuntu plucky/main ppc64el debugedit ppc64el 1:5.1-1 [52.1 kB] 191s Get:32 http://ftpmaster.internal/ubuntu plucky/main ppc64el dwz ppc64el 0.15-1build6 [142 kB] 191s Get:33 http://ftpmaster.internal/ubuntu plucky/main ppc64el gettext ppc64el 0.22.5-3 [1083 kB] 192s Get:34 http://ftpmaster.internal/ubuntu plucky/main ppc64el intltool-debian all 0.35.0+20060710.6 [23.2 kB] 192s Get:35 http://ftpmaster.internal/ubuntu plucky/main ppc64el po-debconf all 1.0.21+nmu1 [233 kB] 192s Get:36 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el debhelper all 13.23ubuntu1 [895 kB] 192s Get:37 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-colored all 2.2.4-1 [14.2 kB] 192s Get:38 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-colorlog all 6.9.0-1 [21.6 kB] 192s Get:39 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-debian all 0.1.49ubuntu3 [116 kB] 192s Get:40 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-ruyaml all 0.91.0-3 [107 kB] 192s Get:41 http://ftpmaster.internal/ubuntu plucky/universe ppc64el strip-nondeterminism all 1.14.0-1 [5552 B] 192s Get:42 http://ftpmaster.internal/ubuntu plucky/universe ppc64el dh-debputy all 0.1.58 [466 kB] 192s Fetched 48.2 MB in 2s (25.4 MB/s) 192s Selecting previously unselected package m4. 192s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 74025 files and directories currently installed.) 192s Preparing to unpack .../00-m4_1.4.19-4build1_ppc64el.deb ... 192s Unpacking m4 (1.4.19-4build1) ... 192s Selecting previously unselected package autoconf. 192s Preparing to unpack .../01-autoconf_2.72-3_all.deb ... 192s Unpacking autoconf (2.72-3) ... 192s Selecting previously unselected package autotools-dev. 192s Preparing to unpack .../02-autotools-dev_20220109.1_all.deb ... 192s Unpacking autotools-dev (20220109.1) ... 192s Selecting previously unselected package automake. 192s Preparing to unpack .../03-automake_1%3a1.16.5-1.3ubuntu1_all.deb ... 192s Unpacking automake (1:1.16.5-1.3ubuntu1) ... 192s Selecting previously unselected package autopoint. 192s Preparing to unpack .../04-autopoint_0.22.5-3_all.deb ... 192s Unpacking autopoint (0.22.5-3) ... 192s Selecting previously unselected package libisl23:ppc64el. 192s Preparing to unpack .../05-libisl23_0.27-1_ppc64el.deb ... 192s Unpacking libisl23:ppc64el (0.27-1) ... 192s Selecting previously unselected package libmpc3:ppc64el. 192s Preparing to unpack .../06-libmpc3_1.3.1-1build2_ppc64el.deb ... 192s Unpacking libmpc3:ppc64el (1.3.1-1build2) ... 192s Selecting previously unselected package cpp-14-powerpc64le-linux-gnu. 192s Preparing to unpack .../07-cpp-14-powerpc64le-linux-gnu_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking cpp-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package cpp-14. 192s Preparing to unpack .../08-cpp-14_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking cpp-14 (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package cpp-powerpc64le-linux-gnu. 192s Preparing to unpack .../09-cpp-powerpc64le-linux-gnu_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 192s Unpacking cpp-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 192s Selecting previously unselected package cpp. 192s Preparing to unpack .../10-cpp_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 192s Unpacking cpp (4:14.1.0-2ubuntu1) ... 192s Selecting previously unselected package libdebhelper-perl. 192s Preparing to unpack .../11-libdebhelper-perl_13.23ubuntu1_all.deb ... 192s Unpacking libdebhelper-perl (13.23ubuntu1) ... 192s Selecting previously unselected package libcc1-0:ppc64el. 192s Preparing to unpack .../12-libcc1-0_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking libcc1-0:ppc64el (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package libgomp1:ppc64el. 192s Preparing to unpack .../13-libgomp1_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking libgomp1:ppc64el (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package libitm1:ppc64el. 192s Preparing to unpack .../14-libitm1_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking libitm1:ppc64el (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package libasan8:ppc64el. 192s Preparing to unpack .../15-libasan8_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking libasan8:ppc64el (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package liblsan0:ppc64el. 192s Preparing to unpack .../16-liblsan0_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking liblsan0:ppc64el (14.2.0-12ubuntu1) ... 192s Selecting previously unselected package libtsan2:ppc64el. 192s Preparing to unpack .../17-libtsan2_14.2.0-12ubuntu1_ppc64el.deb ... 192s Unpacking libtsan2:ppc64el (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package libubsan1:ppc64el. 193s Preparing to unpack .../18-libubsan1_14.2.0-12ubuntu1_ppc64el.deb ... 193s Unpacking libubsan1:ppc64el (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package libquadmath0:ppc64el. 193s Preparing to unpack .../19-libquadmath0_14.2.0-12ubuntu1_ppc64el.deb ... 193s Unpacking libquadmath0:ppc64el (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package libgcc-14-dev:ppc64el. 193s Preparing to unpack .../20-libgcc-14-dev_14.2.0-12ubuntu1_ppc64el.deb ... 193s Unpacking libgcc-14-dev:ppc64el (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package gcc-14-powerpc64le-linux-gnu. 193s Preparing to unpack .../21-gcc-14-powerpc64le-linux-gnu_14.2.0-12ubuntu1_ppc64el.deb ... 193s Unpacking gcc-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package gcc-14. 193s Preparing to unpack .../22-gcc-14_14.2.0-12ubuntu1_ppc64el.deb ... 193s Unpacking gcc-14 (14.2.0-12ubuntu1) ... 193s Selecting previously unselected package gcc-powerpc64le-linux-gnu. 193s Preparing to unpack .../23-gcc-powerpc64le-linux-gnu_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 193s Unpacking gcc-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 193s Selecting previously unselected package gcc. 193s Preparing to unpack .../24-gcc_4%3a14.1.0-2ubuntu1_ppc64el.deb ... 193s Unpacking gcc (4:14.1.0-2ubuntu1) ... 193s Selecting previously unselected package libtool. 193s Preparing to unpack .../25-libtool_2.4.7-8_all.deb ... 193s Unpacking libtool (2.4.7-8) ... 193s Selecting previously unselected package dh-autoreconf. 193s Preparing to unpack .../26-dh-autoreconf_20_all.deb ... 193s Unpacking dh-autoreconf (20) ... 193s Selecting previously unselected package libarchive-zip-perl. 193s Preparing to unpack .../27-libarchive-zip-perl_1.68-1_all.deb ... 193s Unpacking libarchive-zip-perl (1.68-1) ... 193s Selecting previously unselected package libfile-stripnondeterminism-perl. 193s Preparing to unpack .../28-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... 193s Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... 193s Selecting previously unselected package dh-strip-nondeterminism. 193s Preparing to unpack .../29-dh-strip-nondeterminism_1.14.0-1_all.deb ... 193s Unpacking dh-strip-nondeterminism (1.14.0-1) ... 193s Selecting previously unselected package debugedit. 193s Preparing to unpack .../30-debugedit_1%3a5.1-1_ppc64el.deb ... 193s Unpacking debugedit (1:5.1-1) ... 193s Selecting previously unselected package dwz. 193s Preparing to unpack .../31-dwz_0.15-1build6_ppc64el.deb ... 193s Unpacking dwz (0.15-1build6) ... 193s Selecting previously unselected package gettext. 193s Preparing to unpack .../32-gettext_0.22.5-3_ppc64el.deb ... 193s Unpacking gettext (0.22.5-3) ... 193s Selecting previously unselected package intltool-debian. 193s Preparing to unpack .../33-intltool-debian_0.35.0+20060710.6_all.deb ... 193s Unpacking intltool-debian (0.35.0+20060710.6) ... 193s Selecting previously unselected package po-debconf. 193s Preparing to unpack .../34-po-debconf_1.0.21+nmu1_all.deb ... 193s Unpacking po-debconf (1.0.21+nmu1) ... 193s Selecting previously unselected package debhelper. 193s Preparing to unpack .../35-debhelper_13.23ubuntu1_all.deb ... 193s Unpacking debhelper (13.23ubuntu1) ... 193s Selecting previously unselected package python3-colored. 193s Preparing to unpack .../36-python3-colored_2.2.4-1_all.deb ... 193s Unpacking python3-colored (2.2.4-1) ... 193s Selecting previously unselected package python3-colorlog. 193s Preparing to unpack .../37-python3-colorlog_6.9.0-1_all.deb ... 193s Unpacking python3-colorlog (6.9.0-1) ... 193s Selecting previously unselected package python3-debian. 193s Preparing to unpack .../38-python3-debian_0.1.49ubuntu3_all.deb ... 193s Unpacking python3-debian (0.1.49ubuntu3) ... 193s Selecting previously unselected package python3-ruyaml. 193s Preparing to unpack .../39-python3-ruyaml_0.91.0-3_all.deb ... 193s Unpacking python3-ruyaml (0.91.0-3) ... 193s Selecting previously unselected package strip-nondeterminism. 193s Preparing to unpack .../40-strip-nondeterminism_1.14.0-1_all.deb ... 193s Unpacking strip-nondeterminism (1.14.0-1) ... 193s Selecting previously unselected package dh-debputy. 193s Preparing to unpack .../41-dh-debputy_0.1.58_all.deb ... 193s Unpacking dh-debputy (0.1.58) ... 193s Setting up python3-colorlog (6.9.0-1) ... 193s Setting up libarchive-zip-perl (1.68-1) ... 193s Setting up libdebhelper-perl (13.23ubuntu1) ... 193s Setting up m4 (1.4.19-4build1) ... 193s Setting up libgomp1:ppc64el (14.2.0-12ubuntu1) ... 193s Setting up autotools-dev (20220109.1) ... 193s Setting up python3-debian (0.1.49ubuntu3) ... 194s Setting up libquadmath0:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up libmpc3:ppc64el (1.3.1-1build2) ... 194s Setting up autopoint (0.22.5-3) ... 194s Setting up autoconf (2.72-3) ... 194s Setting up libubsan1:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up dwz (0.15-1build6) ... 194s Setting up libasan8:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up debugedit (1:5.1-1) ... 194s Setting up python3-colored (2.2.4-1) ... 194s Setting up libtsan2:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up libisl23:ppc64el (0.27-1) ... 194s Setting up python3-ruyaml (0.91.0-3) ... 194s Setting up libcc1-0:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up liblsan0:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up libitm1:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up automake (1:1.16.5-1.3ubuntu1) ... 194s update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode 194s Setting up libfile-stripnondeterminism-perl (1.14.0-1) ... 194s Setting up gettext (0.22.5-3) ... 194s Setting up strip-nondeterminism (1.14.0-1) ... 194s Setting up intltool-debian (0.35.0+20060710.6) ... 194s Setting up cpp-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 194s Setting up cpp-14 (14.2.0-12ubuntu1) ... 194s Setting up dh-strip-nondeterminism (1.14.0-1) ... 194s Setting up libgcc-14-dev:ppc64el (14.2.0-12ubuntu1) ... 194s Setting up cpp-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 194s Setting up gcc-14-powerpc64le-linux-gnu (14.2.0-12ubuntu1) ... 194s Setting up po-debconf (1.0.21+nmu1) ... 194s Setting up gcc-14 (14.2.0-12ubuntu1) ... 194s Setting up gcc-powerpc64le-linux-gnu (4:14.1.0-2ubuntu1) ... 194s Setting up cpp (4:14.1.0-2ubuntu1) ... 194s Setting up libtool (2.4.7-8) ... 194s Setting up gcc (4:14.1.0-2ubuntu1) ... 194s Setting up dh-autoreconf (20) ... 194s Setting up debhelper (13.23ubuntu1) ... 194s Setting up dh-debputy (0.1.58) ... 195s Processing triggers for libc-bin (2.40-4ubuntu1) ... 195s Processing triggers for man-db (2.13.0-1) ... 196s Processing triggers for install-info (7.1.1-1) ... 198s autopkgtest [00:04:37]: test debputy-cli: [----------------------- 198s + debputy --no-pager --help 198s usage: debputy [-h] [--version] [--debputy-manifest DEBPUTY_MANIFEST] [-d] 198s [--no-pager] [--plugin REQUIRED_PLUGINS] 198s COMMAND ... 198s 198s The `debputy` program is a Debian packaging tool. 198s 198s It serves multiple roles in the Debian packaging stack: 198s 198s 1) It is a maintainer support tool that can help maintain packages by providing 198s editor support (LSP), batch linting and style/file formatting for Debian 198s packaging files. This is covers subcommands like `debputy lint`, 198s `debputy lsp server`, `debputy reformat` 198s 198s 2) It is a manifest-based Debian package builder aiming to replace existing 198s package helper tools such as `debhelper . In this role, `debputy` is used 198s as a part of compiling a source package and transforming it into one 198s or more binary (.deb) packages. 198s 198s If you are using a screen reader, consider exporting setting the environment variable 198s OPTIMIZE_FOR_SCREEN_READER=1. This will remove some of the visual formatting and some 198s commands will render the output in a purely textual manner rather than visual layout. 198s 198s positional arguments: 198s COMMAND 198s internal-command Commands used for internal purposes. These are 198s implementation details and subject to change 198s tool-support Tool integration commands. These are intended to have 198s stable output and behavior 198s check-manifest Check the manifest for obvious errors, but do not run 198s anything 198s autopkgtest-test-runner 198s Detect tests in the debian dir and run them against 198s installed plugins 198s migrate-from-dh Generate/update manifest from a "dh $@" using package 198s plugin Interact with debputy plugins 198s lsp Language server related subcommands 198s lint Provide diagnostics for the packaging (like `lsp 198s server` except no editor is needed) 198s reformat Reformat the packaging files based on the 198s packaging/maintainer rules 198s 198s options: 198s -h, --help show this help message and exit 198s --version show program's version number and exit 198s --debputy-manifest DEBPUTY_MANIFEST 198s Specify another `debputy` manifest (default: 198s debian/debputy.manifest) 198s -d, --debug Enable debug logging and raw stack traces on errors. 198s Some warnings become errors as a consequence. 198s --no-pager For subcommands that can use a pager, disable the use 198s of pager. Some output formats implies --no-pager 198s --plugin REQUIRED_PLUGINS 198s Request the plugin to be loaded. Can be used multiple 198s time. Ignored for some commands (such as autopkgtest- 198s test-runner) 198s 198s Bug tracker: https://salsa.debian.org/debian/debputy/-/issues 199s + debputy --no-pager check-manifest 199s + debputy --no-pager plugin --help 199s usage: debputy plugin [-h] [--debputy-manifest DEBPUTY_MANIFEST] [-d] 199s [--no-pager] [--plugin REQUIRED_PLUGINS] 199s command ... 199s 199s positional arguments: 199s command 199s list List plugins or things provided by plugins (unstable 199s format). Pass `--help` *after* `list` get a topic 199s listing 199s show Show details about a plugin or things provided by 199s plugins (unstable format). Pass `--help` *after* 199s `show` get a topic listing 199s 199s options: 199s -h, --help show this help message and exit 199s --debputy-manifest DEBPUTY_MANIFEST 199s Specify another `debputy` manifest (default: 199s debian/debputy.manifest) 199s -d, --debug Enable debug logging and raw stack traces on errors. 199s Some warnings become errors as a consequence. 199s --no-pager For subcommands that can use a pager, disable the use 199s of pager. Some output formats implies --no-pager 199s --plugin REQUIRED_PLUGINS 199s Request the plugin to be loaded. Can be used multiple 199s time. Ignored for some commands (such as autopkgtest- 199s test-runner) 199s + debputy --no-pager plugin list --help 199s usage: debputy plugin list [-h] [--debputy-manifest DEBPUTY_MANIFEST] [-d] 199s [--no-pager] [--plugin REQUIRED_PLUGINS] 199s topic ... 199s 199s positional arguments: 199s topic 199s plugins List known plugins 199s used-packager-provided-files (uppf, u-p-p-f) 199s List packager provided files used by this package 199s (debian/pkg.foo) 199s packager-provided-files (ppf, p-p-f) 199s List packager provided file definitions 199s (debian/pkg.foo) 199s metadata-detectors List metadata detectors 199s manifest-variables List plugin provided manifest variables (such as 199s `{{path:FOO}}`) 199s pluggable-manifest-rules (p-m-r, pmr) 199s Pluggable manifest rules (such as install rules) 199s automatic-discard-rules (a-d-r) 199s List automatic discard rules 199s type-mappings Registered type mappings/descriptions 199s 199s options: 199s -h, --help show this help message and exit 199s --debputy-manifest DEBPUTY_MANIFEST 199s Specify another `debputy` manifest (default: 199s debian/debputy.manifest) 199s -d, --debug Enable debug logging and raw stack traces on errors. 199s Some warnings become errors as a consequence. 199s --no-pager For subcommands that can use a pager, disable the use 199s of pager. Some output formats implies --no-pager 199s --plugin REQUIRED_PLUGINS 199s Request the plugin to be loaded. Can be used multiple 199s time. Ignored for some commands (such as autopkgtest- 199s test-runner) 199s + debputy --no-pager plugin list 200s +-------------------------+-----------------------------------------------------------------+ 200s | Plugin Name | Plugin Path | 200s +-------------------------+-----------------------------------------------------------------+ 200s | debputy | | 200s | perl-openssl | /usr/share/debputy/debputy/plugins/perl-openssl.json | 200s | debhelper-documentation | /usr/share/debputy/debputy/plugins/debhelper-documentation.json | 200s | debputy-documentation | /usr/share/debputy/debputy/plugins/debputy-documentation.json | 200s | gnome | /usr/share/debputy/debputy/plugins/gnome.json | 200s | numpy3 | /usr/share/debputy/debputy/plugins/numpy3.json | 200s | grantlee | /usr/share/debputy/debputy/plugins/grantlee.json | 200s +-------------------------+-----------------------------------------------------------------+ 200s + debputy --no-pager plugin list plugins 200s +-------------------------+-----------------------------------------------------------------+ 200s | Plugin Name | Plugin Path | 200s +-------------------------+-----------------------------------------------------------------+ 200s | debputy | | 200s | perl-openssl | /usr/share/debputy/debputy/plugins/perl-openssl.json | 200s | debhelper-documentation | /usr/share/debputy/debputy/plugins/debhelper-documentation.json | 200s | debputy-documentation | /usr/share/debputy/debputy/plugins/debputy-documentation.json | 200s | gnome | /usr/share/debputy/debputy/plugins/gnome.json | 200s | numpy3 | /usr/share/debputy/debputy/plugins/numpy3.json | 200s | grantlee | /usr/share/debputy/debputy/plugins/grantlee.json | 200s +-------------------------+-----------------------------------------------------------------+ 200s + debputy --no-pager plugin list ppf 201s +-----------------------------+-------------------------------------------------------------------+------+------------------------+-------------+ 201s | Stem | Installed As | Mode | Features | Provided by | 201s +-----------------------------+-------------------------------------------------------------------+------+------------------------+-------------+ 201s | @path | /usr/lib/systemd/system/{name}@.path | 0644 | named | debputy | 201s | @service | /usr/lib/systemd/system/{name}@.service | 0644 | named | debputy | 201s | @socket | /usr/lib/systemd/system/{name}@.socket | 0644 | named | debputy | 201s | @target | /usr/lib/systemd/system/{name}@.target | 0644 | named | debputy | 201s | @timer | /usr/lib/systemd/system/{name}@.timer | 0644 | named | debputy | 201s | NEWS | /usr/share/doc/{name}/NEWS.Debian | 0644 | main-all-fallback | debputy | 201s | README.Debian | /usr/share/doc/{name}/README.Debian | 0644 | | debputy | 201s | TODO | /usr/share/doc/{name}/TODO.Debian | 0644 | | debputy | 201s | alternatives | /DEBIAN/alternatives | 0644 | arch | debputy | 201s | bash-completion | /usr/share/bash-completion/completions/{name} | 0644 | named | debputy | 201s | bug-control | /usr/share/bug/{name}/control | 0644 | | debputy | 201s | bug-presubj | /usr/share/bug/{name}/presubj | 0644 | | debputy | 201s | bug-script | /usr/share/bug/{name}/script | 0755 | | debputy | 201s | changelog | /usr/share/doc/{name}/changelog.Debian | 0644 | main-all-fallback | debputy | 201s | copyright | /usr/share/doc/{name}/copyright | 0644 | main-all-fallback | debputy | 201s | cron.d | /etc/cron.d/{name} | 0644 | named | debputy | 201s | cron.daily | /etc/cron.daily/{name} | 0755 | named | debputy | 201s | cron.hourly | /etc/cron.hourly/{name} | 0755 | named | debputy | 201s | cron.monthly | /etc/cron.monthly/{name} | 0755 | named | debputy | 201s | cron.weekly | /etc/cron.weekly/{name} | 0755 | named | debputy | 201s | cron.yearly | /etc/cron.yearly/{name} | 0755 | named | debputy | 201s | default | /etc/default/{name} | 0644 | named | debputy | 201s | doc-base | /usr/share/doc-base/{owning_package}.{name} | 0644 | named | debputy | 201s | fish-completion | /usr/share/fish/vendor_completions.d/{name} | 0644 | named | debputy | 201s | gsettings-override | /usr/share/glib-2.0/schemas/{priority:02}_{name}.gschema.override | 0644 | named,priority=10 | debputy | 201s | if-down | /etc/network/if-down.d/{name} | 0755 | named | debputy | 201s | if-post-down | /etc/network/if-post-down.d/{name} | 0755 | named | debputy | 201s | if-pre-up | /etc/network/if-pre-up.d/{name} | 0755 | named | debputy | 201s | if-up | /etc/network/if-up.d/{name} | 0755 | named | debputy | 201s | init | /etc/init.d/{name} | 0755 | named | debputy | 201s | initramfs-hook | /usr/share/initramfs-tools/hooks/{name} | 0755 | named | debputy | 201s | lintian-overrides | /usr/share/lintian/overrides/{name} | 0644 | | debputy | 201s | logcheck.cracking | /etc/logcheck/cracking.d/{name} | 0644 | named,post-format-hook | debputy | 201s | logcheck.ignore.paranoid | /etc/logcheck/ignore.d.paranoid/{name} | 0644 | named,post-format-hook | debputy | 201s | logcheck.ignore.server | /etc/logcheck/ignore.d.server/{name} | 0644 | named,post-format-hook | debputy | 201s | logcheck.ignore.workstation | /etc/logcheck/ignore.d.workstation/{name} | 0644 | named,post-format-hook | debputy | 201s | logcheck.violations | /etc/logcheck/violations.d/{name} | 0644 | named,post-format-hook | debputy | 201s | logcheck.violations.ignore | /etc/logcheck/violations.ignore.d/{name} | 0644 | named,post-format-hook | debputy | 201s | logrotate | /etc/logrotate.d/{name} | 0644 | named | debputy | 201s | mime | /usr/lib/mime/packages/{name} | 0644 | named | debputy | 201s | modprobe | /etc/modprobe.d/{name}.conf | 0644 | named | debputy | 201s | mount | /usr/lib/systemd/system/{name}.mount | 0644 | named | debputy | 201s | pam | /usr/lib/pam.d/{name} | 0644 | named | debputy | 201s | path | /usr/lib/systemd/system/{name}.path | 0644 | named | debputy | 201s | ppp.ip-down | /etc/ppp/ip-down.d/{name} | 0755 | named | debputy | 201s | ppp.ip-up | /etc/ppp/ip-up.d/{name} | 0755 | named | debputy | 201s | service | /usr/lib/systemd/system/{name}.service | 0644 | named | debputy | 201s | sharedmimeinfo | /usr/share/mime/packages/{name}.xml | 0644 | named | debputy | 201s | shlibs | /DEBIAN/shlibs | 0644 | | debputy | 201s | socket | /usr/lib/systemd/system/{name}.socket | 0644 | named | debputy | 201s | symbols | /DEBIAN/symbols | 0644 | arch | debputy | 201s | sysusers | /usr/lib/sysusers.d/{name}.conf | 0644 | named | debputy | 201s | target | /usr/lib/systemd/system/{name}.target | 0644 | named | debputy | 201s | templates | /DEBIAN/templates | 0644 | | debputy | 201s | timer | /usr/lib/systemd/system/{name}.timer | 0644 | named | debputy | 201s | tmpfiles | /usr/lib/tmpfiles.d/{name}.conf | 0644 | named | debputy | 201s | zsh-completion | /usr/share/zsh/vendor-completions/{name} | 0644 | named | debputy | 201s +-----------------------------+-------------------------------------------------------------------+------+------------------------+-------------+ 201s 201s Hint: You can use `debputy plugin list used-packager-provided-files` to have `debputy` 201s list all the files in debian/ that matches these definitions. 201s + debputy --no-pager plugin list uppf 201s +------------------+--------------+----------------+--------------------------------------------+ 201s | File | Matched Stem | Installed Into | Installed As | 201s +------------------+--------------+----------------+--------------------------------------------+ 201s | debian/changelog | changelog | dh-debputy | /usr/share/doc/dh-debputy/changelog.Debian | 201s | debian/copyright | copyright | dh-debputy | /usr/share/doc/dh-debputy/copyright | 201s +------------------+--------------+----------------+--------------------------------------------+ 201s + debputy --no-pager plugin list manifest-variables 201s +----------------------------------+----------------------------------------+------+-------------+ 201s | Variable (use via: `{{ NAME }}`) | Value | Flag | Provided by | 201s +----------------------------------+----------------------------------------+------+-------------+ 201s | DEB_HOST_ARCH | ppc64el | | debputy | 201s | DEB_HOST_ARCH_ABI | base | | debputy | 201s | DEB_HOST_ARCH_BITS | 64 | | debputy | 201s | DEB_HOST_ARCH_CPU | ppc64el | | debputy | 201s | DEB_HOST_ARCH_ENDIAN | little | | debputy | 201s | DEB_HOST_ARCH_LIBC | gnu | | debputy | 201s | DEB_HOST_ARCH_OS | linux | | debputy | 201s | DEB_HOST_GNU_CPU | powerpc64le | | debputy | 201s | DEB_HOST_GNU_SYSTEM | linux-gnu | | debputy | 201s | DEB_HOST_GNU_TYPE | powerpc64le-linux-gnu | | debputy | 201s | DEB_HOST_MULTIARCH | powerpc64le-linux-gnu | | debputy | 201s | DEB_SOURCE | debputy | | debputy | 201s | DEB_VERSION | 0.1.58 | | debputy | 201s | DEB_VERSION_EPOCH_UPSTREAM | 0.1.58 | | debputy | 201s | DEB_VERSION_UPSTREAM | 0.1.58 | | debputy | 201s | DEB_VERSION_UPSTREAM_REVISION | 0.1.58 | | debputy | 201s | PACKAGE | | | debputy | 201s | SOURCE_DATE_EPOCH | 1735479764 | | debputy | 201s | path:BASH_COMPLETION_DIR | /usr/share/bash-completion/completions | | debputy | 201s | path:FISH_COMPLETION_DIR | /usr/share/fish/vendor_completions.d | | debputy | 201s | path:GNU_INFO_DIR | /usr/share/info | | debputy | 201s | path:ZSH_COMPLETION_DIR | /usr/share/zsh/vendor-completions | | debputy | 201s +----------------------------------+----------------------------------------+------+-------------+ 201s 201s +-----------------------+--------+-------------------------------------------------------+ 201s | Variable type | Value | Option | 201s +-----------------------+--------+-------------------------------------------------------+ 201s | Token variables | hidden | --show-token-variables OR --show-all-variables | 201s | Special use variables | hidden | --show-special-case-variables OR --show-all-variables | 201s +-----------------------+--------+-------------------------------------------------------+ 201s + debputy --no-pager plugin list manifest-variables --show-all-variables 202s +-------------------------------------+----------------------------------------+------------------+-------------+ 202s | Variable (use via: `{{ NAME }}`) | Value | Flag | Provided by | 202s +-------------------------------------+----------------------------------------+------------------+-------------+ 202s | DEB_BUILD_ARCH | ppc64el | special-use-case | debputy | 202s | DEB_BUILD_ARCH_ABI | base | special-use-case | debputy | 202s | DEB_BUILD_ARCH_BITS | 64 | special-use-case | debputy | 202s | DEB_BUILD_ARCH_CPU | ppc64el | special-use-case | debputy | 202s | DEB_BUILD_ARCH_ENDIAN | little | special-use-case | debputy | 202s | DEB_BUILD_ARCH_LIBC | gnu | special-use-case | debputy | 202s | DEB_BUILD_ARCH_OS | linux | special-use-case | debputy | 202s | DEB_BUILD_GNU_CPU | powerpc64le | special-use-case | debputy | 202s | DEB_BUILD_GNU_SYSTEM | linux-gnu | special-use-case | debputy | 202s | DEB_BUILD_GNU_TYPE | powerpc64le-linux-gnu | special-use-case | debputy | 202s | DEB_BUILD_MULTIARCH | powerpc64le-linux-gnu | special-use-case | debputy | 202s | DEB_HOST_ARCH | ppc64el | | debputy | 202s | DEB_HOST_ARCH_ABI | base | | debputy | 202s | DEB_HOST_ARCH_BITS | 64 | | debputy | 202s | DEB_HOST_ARCH_CPU | ppc64el | | debputy | 202s | DEB_HOST_ARCH_ENDIAN | little | | debputy | 202s | DEB_HOST_ARCH_LIBC | gnu | | debputy | 202s | DEB_HOST_ARCH_OS | linux | | debputy | 202s | DEB_HOST_GNU_CPU | powerpc64le | | debputy | 202s | DEB_HOST_GNU_SYSTEM | linux-gnu | | debputy | 202s | DEB_HOST_GNU_TYPE | powerpc64le-linux-gnu | | debputy | 202s | DEB_HOST_MULTIARCH | powerpc64le-linux-gnu | | debputy | 202s | DEB_SOURCE | debputy | | debputy | 202s | DEB_TARGET_ARCH | ppc64el | special-use-case | debputy | 202s | DEB_TARGET_ARCH_ABI | base | special-use-case | debputy | 202s | DEB_TARGET_ARCH_BITS | 64 | special-use-case | debputy | 202s | DEB_TARGET_ARCH_CPU | ppc64el | special-use-case | debputy | 202s | DEB_TARGET_ARCH_ENDIAN | little | special-use-case | debputy | 202s | DEB_TARGET_ARCH_LIBC | gnu | special-use-case | debputy | 202s | DEB_TARGET_ARCH_OS | linux | special-use-case | debputy | 202s | DEB_TARGET_GNU_CPU | powerpc64le | special-use-case | debputy | 202s | DEB_TARGET_GNU_SYSTEM | linux-gnu | special-use-case | debputy | 202s | DEB_TARGET_GNU_TYPE | powerpc64le-linux-gnu | special-use-case | debputy | 202s | DEB_TARGET_MULTIARCH | powerpc64le-linux-gnu | special-use-case | debputy | 202s | DEB_VERSION | 0.1.58 | | debputy | 202s | DEB_VERSION_EPOCH_UPSTREAM | 0.1.58 | | debputy | 202s | DEB_VERSION_UPSTREAM | 0.1.58 | | debputy | 202s | DEB_VERSION_UPSTREAM_REVISION | 0.1.58 | | debputy | 202s | PACKAGE | | | debputy | 202s | SOURCE_DATE_EPOCH | 1735479764 | | debputy | 202s | _DEBPUTY_INTERNAL_NON_BINNMU_SOURCE | 0.1.58 | internal | debputy | 202s | _DEBPUTY_SND_SOURCE_DATE_EPOCH | 1735479764 | internal | debputy | 202s | path:BASH_COMPLETION_DIR | /usr/share/bash-completion/completions | | debputy | 202s | path:FISH_COMPLETION_DIR | /usr/share/fish/vendor_completions.d | | debputy | 202s | path:GNU_INFO_DIR | /usr/share/info | | debputy | 202s | path:ZSH_COMPLETION_DIR | /usr/share/zsh/vendor-completions | | debputy | 202s | token:CLOSE_CURLY_BRACE | } | | debputy | 202s | token:DOUBLE_CLOSE_CURLY_BRACE | }} | | debputy | 202s | token:DOUBLE_OPEN_CURLY_BRACE | {{ | | debputy | 202s | token:NEWLINE | \n | | debputy | 202s | token:NL | \n | | debputy | 202s | token:OPEN_CURLY_BRACE | { | | debputy | 202s | token:TAB | \t | | debputy | 202s +-------------------------------------+----------------------------------------+------------------+-------------+ 202s 202s +-----------------------+-------+-------------------------------------------------------+ 202s | Variable type | Value | Option | 202s +-----------------------+-------+-------------------------------------------------------+ 202s | Token variables | shown | --show-token-variables OR --show-all-variables | 202s | Special use variables | shown | --show-special-case-variables OR --show-all-variables | 202s +-----------------------+-------+-------------------------------------------------------+ 202s + debputy --no-pager plugin list pmr 202s +-------------------------------+------------------------------+-------------+ 202s | Rule Name | Rule Type | Provided By | 202s +-------------------------------+------------------------------+-------------+ 202s | install | InstallRule | debputy | 202s | install-docs | InstallRule | debputy | 202s | install-doc | InstallRule | debputy | 202s | install-examples | InstallRule | debputy | 202s | install-example | InstallRule | debputy | 202s | install-man | InstallRule | debputy | 202s | discard | InstallRule | debputy | 202s | multi-dest-install | InstallRule | debputy | 202s | move | TransformationRule | debputy | 202s | remove | TransformationRule | debputy | 202s | create-symlink | TransformationRule | debputy | 202s | path-metadata | TransformationRule | debputy | 202s | create-directories | TransformationRule | debputy | 202s | remove | DpkgMaintscriptHelperCommand | debputy | 202s | rename | DpkgMaintscriptHelperCommand | debputy | 202s | cross-compiling | ManifestCondition | debputy | 202s | can-execute-compiled-binaries | ManifestCondition | debputy | 202s | run-build-time-tests | ManifestCondition | debputy | 202s | not | ManifestCondition | debputy | 202s | any-of | ManifestCondition | debputy | 202s | all-of | ManifestCondition | debputy | 202s | arch-matches | ManifestCondition | debputy | 202s | source-context-arch-matches | ManifestCondition | debputy | 202s | package-context-arch-matches | ManifestCondition | debputy | 202s | build-profiles-matches | ManifestCondition | debputy | 202s | autoconf | BuildRule | debputy | 202s | make | BuildRule | debputy | 202s | perl-build | BuildRule | debputy | 202s | perl-makemaker | BuildRule | debputy | 202s | debhelper | BuildRule | debputy | 202s | cmake | BuildRule | debputy | 202s | meson | BuildRule | debputy | 202s | qmake | BuildRule | debputy | 202s | qmake6 | BuildRule | debputy | 202s | manifest-version | | debputy | 202s | definitions | | debputy | 202s | installations | | debputy | 202s | packages | | debputy | 202s | build-environments | | debputy | 202s | default-build-environment | | debputy | 202s | builds | | debputy | 202s | variables | definitions | debputy | 202s | binary-version | packages.{{PACKAGE}} | debputy | 202s | transformations | packages.{{PACKAGE}} | debputy | 202s | conffile-management | packages.{{PACKAGE}} | debputy | 202s | services | packages.{{PACKAGE}} | debputy | 202s | clean-after-removal | packages.{{PACKAGE}} | debputy | 202s | installation-search-dirs | packages.{{PACKAGE}} | debputy | 202s +-------------------------------+------------------------------+-------------+ 202s + debputy --no-pager plugin list automatic-discard-rules 202s +-----------------------+-------------+ 202s | Name | Provided By | 202s +-----------------------+-------------+ 202s | python-cache-files | debputy | 202s | la-files | debputy | 202s | backup-files | debputy | 202s | version-control-paths | debputy | 202s | gnu-info-dir-file | debputy | 202s | debian-dir | debputy | 202s | doxygen-cruft-files | debputy | 202s +-----------------------+-------------+ 202s + debputy --no-pager plugin list a-d-r 203s +-----------------------+-------------+ 203s | Name | Provided By | 203s +-----------------------+-------------+ 203s | python-cache-files | debputy | 203s | la-files | debputy | 203s | backup-files | debputy | 203s | version-control-paths | debputy | 203s | gnu-info-dir-file | debputy | 203s | debian-dir | debputy | 203s | doxygen-cruft-files | debputy | 203s +-----------------------+-------------+ 203s + debputy --no-pager plugin show ppf changelog 203s Packager Provided File: changelog 203s ================================= 203s 203s This file is the changelog of the package and is mandatory. 203s 203s The changelog contains the version of the source package and is mandatory for all 203s packages. 203s 203s Use `dch --create` to create the changelog. 203s 203s In theory, the binary package can have a different changelog than the source 203s package (by having `debian/binary-package.changelog`). However, it is generally 203s not useful and leads to double administration. It has not been used in practice. 203s 203s Features: 203s * debian/changelog is used for *ALL* packages 203s * No naming support; at most one per package and it is named after the package. 203s * No architecture specific variants. 203s 203s Examples matches: 203s +-----------------------------+--------------------------------------------+ 203s | Source file | Installed As | 203s +-----------------------------+--------------------------------------------+ 203s | debian/changelog | /usr/share/doc/dh-debputy/changelog.Debian | 203s | debian/dh-debputy.changelog | /usr/share/doc/dh-debputy/changelog.Debian | 203s +-----------------------------+--------------------------------------------+ 203s 203s Documentation URIs: 203s * man:deb-changelog(5) 203s * https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog 203s * man:dch(1) 203s 203s Install Mode: 0644 203s Provided by plugin: debputy 203s + debputy --no-pager plugin show ppf debian/changelog 203s Packager Provided File: changelog 203s ================================= 203s 203s This file is the changelog of the package and is mandatory. 203s 203s The changelog contains the version of the source package and is mandatory for all 203s packages. 203s 203s Use `dch --create` to create the changelog. 203s 203s In theory, the binary package can have a different changelog than the source 203s package (by having `debian/binary-package.changelog`). However, it is generally 203s not useful and leads to double administration. It has not been used in practice. 203s 203s Features: 203s * debian/changelog is used for *ALL* packages 203s * No naming support; at most one per package and it is named after the package. 203s * No architecture specific variants. 203s 203s Examples matches: 203s +-----------------------------+--------------------------------------------+ 203s | Source file | Installed As | 203s +-----------------------------+--------------------------------------------+ 203s | debian/changelog | /usr/share/doc/dh-debputy/changelog.Debian | 203s | debian/dh-debputy.changelog | /usr/share/doc/dh-debputy/changelog.Debian | 203s +-----------------------------+--------------------------------------------+ 203s 203s Documentation URIs: 203s * man:deb-changelog(5) 203s * https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog 203s * man:dch(1) 203s 203s Install Mode: 0644 203s Provided by plugin: debputy 203s + debputy --no-pager plugin show ppf service 204s Packager Provided File: service 204s =============================== 204s 204s Sorry, no description provided by the plugin debputy. 204s 204s Features: 204s * debian/service is used for only for the "main" package 204s * Supports naming segment (multiple files and custom naming). 204s * No architecture specific variants. 204s 204s Examples matches: 204s +------------------------------------------+------------------------------------------------+ 204s | Source file | Installed As | 204s +------------------------------------------+------------------------------------------------+ 204s | debian/service | /usr/lib/systemd/system/dh-debputy.service | 204s | debian/dh-debputy.service | /usr/lib/systemd/system/dh-debputy.service | 204s | debian/dh-debputy.my.custom.name.service | /usr/lib/systemd/system/my.custom.name.service | 204s +------------------------------------------+------------------------------------------------+ 204s 204s Documentation URIs: 204s * man:systemd.service(5) 204s 204s Install Mode: 0644 204s Provided by plugin: debputy 204s + debputy --no-pager plugin show pmr --help 204s usage: debputy plugin show pluggable-manifest-rules [-h] 204s [--debputy-manifest DEBPUTY_MANIFEST] 204s [-d] [--no-pager] 204s [--plugin REQUIRED_PLUGINS] 204s rule-name 204s 204s positional arguments: 204s rule-name Name of the rule (such as `install`) to display 204s details about 204s 204s options: 204s -h, --help show this help message and exit 204s --debputy-manifest DEBPUTY_MANIFEST 204s Specify another `debputy` manifest (default: 204s debian/debputy.manifest) 204s -d, --debug Enable debug logging and raw stack traces on errors. 204s Some warnings become errors as a consequence. 204s --no-pager For subcommands that can use a pager, disable the use 204s of pager. Some output formats implies --no-pager 204s --plugin REQUIRED_PLUGINS 204s Request the plugin to be loaded. Can be used multiple 204s time. Ignored for some commands (such as autopkgtest- 204s test-runner) 204s Checking installations manifest rules 204s + echo Checking installations manifest rules 204s + debputy --no-pager plugin show pmr install 204s Generic install (`install`) 204s =========================== 204s 204s The generic `install` rule can be used to install arbitrary paths into packages 204s and is *similar* to how `dh_install` from debhelper works. It is a two "primary" uses. 204s 204s 1) The classic "install into directory" similar to the standard `dh_install` 204s 2) The "install as" similar to `dh-exec`'s `foo => bar` feature. 204s 204s The `install` rule installs a path exactly once into each package it acts on. In 204s the rare case that you want to install the same source *multiple* times into the 204s *same* packages, please have a look at `multi-dest-install`. 204s 204s Attributes: 204s - `source` (conditional): FileSystemMatchRule 204s `sources` (conditional): List of string 204s 204s A path match (`source`) or a list of path matches (`sources`) defining the 204s source path(s) to be installed. The path match(es) can use globs. Each match 204s is tried against default search directories. 204s - When a symlink is matched, then the symlink (not its target) is installed 204s as-is. When a directory is matched, then the directory is installed along 204s with all the contents that have not already been installed somewhere. 204s 204s - `dest-dir` (optional): FileSystemExactMatchRule 204s 204s A path defining the destination *directory*. The value *cannot* use globs, but can 204s use substitution. If neither `as` nor `dest-dir` is given, then `dest-dir` defaults 204s to the directory name of the `source`. 204s 204s - `into` (optional): string or a list of string 204s 204s Either a package name or a list of package names for which these paths should be 204s installed. This key is conditional on whether there are multiple binary packages listed 204s in `debian/control`. When there is only one binary package, then that binary is the 204s default for `into`. Otherwise, the key is required. 204s 204s - `as` (optional): FileSystemExactMatchRule 204s 204s A path defining the path to install the source as. This is a full path. This option 204s is mutually exclusive with `dest-dir` and `sources` (but not `source`). When `as` is 204s given, then `source` must match exactly one "not yet matched" path. 204s 204s - `when` (optional): ManifestCondition 204s 204s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 204s 204s The conditional will disable the entire rule when the conditional evaluates to false. 204s 204s 204s This rule enforces the following restrictions: 204s - The rule must use exactly one of: `source`, `sources` 204s - The attribute `as` cannot be used with any of: `dest-dir`, `sources` 204s 204s Non-mapping format: string or a list of string 204s When the input is a string or a list of string, then that value is used as shorthand 204s for `source` or `sources` (respectively). This form can only be used when `into` is 204s not required. 204s 204s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#generic-install-install 204s Used in: installations 204s Rule reference: InstallRule::install 204s Plugin: debputy 204s 204s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 204s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 204s + debputy --no-pager plugin show pmr install-docs 205s Install documentation (`install-docs`) 205s ====================================== 205s 205s This install rule resemble that of `dh_installdocs`. It is a shorthand over the generic 205s `install` rule with the following key features: 205s 205s 1) The default `dest-dir` is to use the package's documentation directory (usually something 205s like `/usr/share/doc/{PACKAGE}`, though it respects the "main documentation package" 205s recommendation from Debian Policy). The `dest-dir` or `as` can be set in case the 205s documentation in question goes into another directory or with a concrete path. In this 205s case, it is still "better" than `install` due to the remaining benefits. 205s 2) The rule comes with pre-defined conditional logic for skipping the rule under 205s `DEB_BUILD_OPTIONS=nodoc`, so you do not have to write that conditional yourself. 205s 3) The `into` parameter can be omitted as long as there is a exactly one non-`udeb` 205s package listed in `debian/control`. 205s 205s With these two things in mind, it behaves just like the `install` rule. 205s 205s Note: It is often worth considering to use a more specialized version of the `install-docs` 205s rule when one such is available. If you are looking to install an example or a man page, 205s consider whether `install-examples` or `install-man` might be a better fit for your 205s use-case. 205s 205s Attributes: 205s - `source` (conditional): FileSystemMatchRule 205s `sources` (conditional): List of string 205s 205s A path match (`source`) or a list of path matches (`sources`) defining the 205s source path(s) to be installed. The path match(es) can use globs. Each match 205s is tried against default search directories. 205s - When a symlink is matched, then the symlink (not its target) is installed 205s as-is. When a directory is matched, then the directory is installed along 205s with all the contents that have not already been installed somewhere. 205s 205s - **CAVEAT**: Specifying `source: examples` where `examples` resolves to a 205s directory for `install-examples` will give you an `examples/examples` 205s directory in the package, which is rarely what you want. Often, you 205s can solve this by using `examples/*` instead. Similar for `install-docs` 205s and a `doc` or `docs` directory. 205s 205s - `dest-dir` (optional): FileSystemExactMatchRule 205s 205s A path defining the destination *directory*. The value *cannot* use globs, but can 205s use substitution. If neither `as` nor `dest-dir` is given, then `dest-dir` defaults 205s to the relevant package documentation directory (a la `/usr/share/doc/{PACKAGE}`). 205s 205s - `into` (optional): string or a list of string 205s 205s Either a package name or a list of package names for which these paths should be 205s installed as documentation. This key is conditional on whether there are multiple 205s (non-`udeb`) binary packages listed in `debian/control`. When there is only one 205s (non-`udeb`) binary package, then that binary is the default for `into`. Otherwise, 205s the key is required. 205s 205s - `as` (optional): FileSystemExactMatchRule 205s 205s A path defining the path to install the source as. This is a full path. This option 205s is mutually exclusive with `dest-dir` and `sources` (but not `source`). When `as` is 205s given, then `source` must match exactly one "not yet matched" path. 205s 205s - `when` (optional): ManifestCondition 205s 205s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 205s This condition will be combined with the built-in condition provided by these rules 205s (rather than replacing it). 205s 205s 205s This rule enforces the following restrictions: 205s - The rule must use exactly one of: `sources`, `source` 205s - The attribute `as` cannot be used with any of: `sources`, `dest-dir` 205s 205s Non-mapping format: string or a list of string 205s When the input is a string or a list of string, then that value is used as shorthand 205s for `source` or `sources` (respectively). This form can only be used when `into` is 205s not required. 205s 205s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#install-documentation-install-docs 205s Used in: installations 205s Rule reference: InstallRule::install-docs 205s Plugin: debputy 205s 205s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 205s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 205s + debputy --no-pager plugin show pmr install-man 205s Install man pages (`install-man`) 205s ================================= 205s 205s Install rule for installing man pages similar to `dh_installman`. It is a shorthand 205s over the generic `install` rule with the following key features: 205s 205s 1) The rule can only match files (notably, symlinks cannot be matched by this rule). 205s 2) The `dest-dir` is computed per source file based on the man page's section and 205s language. 205s 3) The `into` parameter can be omitted as long as there is a exactly one non-`udeb` 205s package listed in `debian/control`. 205s 4) The rule comes with man page specific attributes such as `language` and `section` 205s for when the auto-detection is insufficient. 205s 5) The rule comes with pre-defined conditional logic for skipping the rule under 205s `DEB_BUILD_OPTIONS=nodoc`, so you do not have to write that conditional yourself. 205s 205s With these things in mind, the rule behaves similar to the `install` rule. 205s 205s Attributes: 205s - `source` (conditional): FileSystemMatchRule 205s `sources` (conditional): List of string 205s 205s A path match (`source`) or a list of path matches (`sources`) defining the 205s source path(s) to be installed. The path match(es) can use globs. Each match 205s is tried against default search directories. 205s - When a symlink is matched, then the symlink (not its target) is installed 205s as-is. When a directory is matched, then the directory is installed along 205s with all the contents that have not already been installed somewhere. 205s 205s - `into` (optional): string or a list of string 205s 205s Either a package name or a list of package names for which these paths should be 205s installed as man pages. This key is conditional on whether there are multiple (non-`udeb`) 205s binary packages listed in `debian/control`. When there is only one (non-`udeb`) binary 205s package, then that binary is the default for `into`. Otherwise, the key is required. 205s 205s - `section` (optional): integer 205s 205s If provided, it must be an integer between 1 and 9 (both inclusive), defining the 205s section the man pages belong overriding any auto-detection that `debputy` would 205s have performed. 205s 205s - `language` (optional): string 205s 205s If provided, it must be either a 2 letter language code (such as `de`), a 5 letter 205s language + dialect code (such as `pt_BR`), or one of the special keywords `C`, 205s `derive-from-path`, or `derive-from-basename`. The default is `derive-from-path`. 205s - When `language` is `C`, then the man pages are assumed to be "untranslated". 205s - When `language` is a language code (with or without dialect), then all man pages 205s matched will be assumed to be translated to that concrete language / dialect. 205s - When `language` is `derive-from-path`, then `debputy` attempts to derive the 205s language from the path (`man//man
`). This matches the 205s default of `dh_installman`. When no language can be found for a given source, 205s `debputy` behaves like language was `C`. 205s - When `language` is `derive-from-basename`, then `debputy` attempts to derive 205s the language from the basename (`foo..1`) similar to `dh_installman` 205s previous default. When no language can be found for a given source, `debputy` 205s behaves like language was `C`. Note this is prone to false positives where 205s `.pl`, `.so` or similar two-letter extensions gets mistaken for a language code 205s (`.pl` can both be "Polish" or "Perl Script", `.so` can both be "Somali" and 205s "Shared Object" documentation). In this configuration, such extensions are 205s always assumed to be a language. 205s 205s - `when` (optional): ManifestCondition 205s 205s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 205s 205s The conditional will disable the entire rule when the conditional evaluates to false. 205s 205s 205s This rule enforces the following restrictions: 205s - The rule must use exactly one of: `sources`, `source` 205s 205s Non-mapping format: string or a list of string 205s When the input is a string or a list of string, then that value is used as shorthand 205s for `source` or `sources` (respectively). This form can only be used when `into` is 205s not required. 205s 205s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#install-manpages-install-man 205s Used in: installations 205s Rule reference: InstallRule::install-man 205s Plugin: debputy 205s 205s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 205s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 205s + debputy --no-pager plugin show pmr discard 205s Discard (or exclude) upstream provided paths (`discard`) 205s ======================================================== 205s 205s When installing paths from `debian/tmp` into packages, it might be useful to ignore 205s some paths that you never need installed. This can be done with the `discard` rule. 205s 205s Once a path is discarded, it cannot be matched by any other install rules. A path 205s that is discarded, is considered handled when `debputy` checks for paths you might 205s have forgotten to install. The `discard` feature is therefore *also* replaces the 205s `debian/not-installed` file used by `debhelper` and `cdbs`. 205s 205s Attributes: 205s - `path` (conditional): FileSystemMatchRule 205s `paths` (conditional): List of string 205s 205s A path match (`path`) or a list of path matches (`paths`) defining the source 205s path(s) that should not be installed anywhere. The path match(es) can use globs. 205s - When a symlink is matched, then the symlink (not its target) is discarded as-is. 205s When a directory is matched, then the directory is discarded along with all the 205s contents that have not already been installed somewhere. 205s 205s - `search-dir` (optional): FileSystemExactMatchRule 205s `search-dirs` (optional): List of string 205s 205s A path (`search-dir`) or a list to paths (`search-dirs`) that defines 205s which search directories apply to. This attribute is primarily useful 205s for source packages that uses "per package search dirs", and you want 205s to restrict a discard rule to a subset of the relevant search dirs. 205s Note all listed search directories must be either an explicit search 205s requested by the packager or a search directory that `debputy` 205s provided automatically (such as `debian/tmp`). Listing other paths 205s will make `debputy` report an error. 205s - Note that the `path` or `paths` must match at least one entry in 205s any of the search directories unless *none* of the search directories 205s exist (or the condition in `required-when` evaluates to false). When 205s none of the search directories exist, the discard rule is silently 205s skipped. This special-case enables you to have discard rules only 205s applicable to certain builds that are only performed conditionally. 205s 205s - `required-when` (optional): ManifestCondition 205s 205s A condition as defined in [Conditional rules](#conditional-rules). The discard 205s rule is always applied. When the conditional is present and evaluates to false, 205s the discard rule can silently match nothing.When the condition is absent, *or* 205s it evaluates to true, then each pattern provided must match at least one path. 205s 205s 205s This rule enforces the following restrictions: 205s - The rule must use exactly one of: `paths`, `path` 205s - The following attributes are mutually exclusive: `search-dir`, `search-dirs` 205s 205s Non-mapping format: string or a list of string 205s When the input is a string or a list of string, then that value is used as shorthand 205s for `path` or `paths` (respectively). 205s 205s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#discard-or-exclude-upstream-provided-paths-discard 205s Used in: installations 205s Rule reference: InstallRule::discard 205s Plugin: debputy 205s 205s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 205s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 205s Checking binary package transformations manifest rules 205s + echo Checking binary package transformations manifest rules 205s + debputy --no-pager plugin show pmr TransformationRule::remove 206s Remove transformation rule (`remove`) 206s ===================================== 206s 206s The remove transformation rule is mostly only useful for single binary source packages, 206s where everything from upstream's build system is installed automatically into the package. 206s In those case, you might find yourself with some files that are _not_ relevant for the 206s Debian package (but would be relevant for other distros or for non-distro local builds). 206s Common examples include `INSTALL` files or `LICENSE` files (when they are just a subset 206s of `debian/copyright`). 206s 206s In the manifest, you can ask `debputy` to remove paths from the debian package by using 206s the `remove` transformation rule. 206s 206s Note that `remove` removes paths from future glob matches and transformation rules. 206s 206s Attributes: 206s - `path` (conditional): FileSystemMatchRule 206s `paths` (conditional): List of string 206s 206s A path match (`path`) or a list of path matches (`paths`) defining the 206s path(s) inside the package that should be removed. The path match(es) 206s can use globs. 206s - When a symlink is matched, then the symlink (not its target) is removed 206s as-is. When a directory is matched, then the directory is removed 206s along with all the contents. 206s 206s - `keep-empty-parent-dirs` (optional): boolean 206s 206s A boolean determining whether to prune parent directories that become 206s empty as a consequence of this rule. When provided and `true`, this 206s rule will leave empty directories behind. Otherwise, if this rule 206s causes a directory to become empty that directory will be removed. 206s 206s - `when` (optional): ManifestCondition 206s 206s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 206s This condition will be combined with the built-in condition provided by these rules 206s (rather than replacing it). 206s 206s 206s This rule enforces the following restrictions: 206s - The rule must use exactly one of: `paths`, `path` 206s 206s Non-mapping format: string or a list of string 206s When the input is a string or a list of string, then that value is used as shorthand 206s for `path` or `paths` (respectively). 206s 206s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#remove-transformation-rule-remove 206s Used in: packages.{{PACKAGE}}.transformations 206s Rule reference: TransformationRule::remove 206s Plugin: debputy 206s 206s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 206s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 206s + debputy --no-pager plugin show pmr move 206s Move transformation rule (`move`) 206s ================================= 206s 206s The move transformation rule is mostly only useful for single binary source packages, 206s where everything from upstream's build system is installed automatically into the package. 206s In those case, you might find yourself with some files that need to be renamed to match 206s Debian specific requirements. 206s 206s This can be done with the `move` transformation rule, which is a rough emulation of the 206s `mv` command line tool. 206s 206s Attributes: 206s - `source` (required): FileSystemMatchRule 206s 206s A path match defining the source path(s) to be renamed. The value can use globs 206s and substitutions. 206s 206s - `target` (required): FileSystemExactMatchRule 206s 206s A path defining the target path. The value *cannot* use globs, but can use 206s substitution. If the target ends with a literal `/` (prior to substitution), 206s the target will *always* be a directory. 206s 206s - `when` (optional): ManifestCondition 206s 206s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 206s 206s The conditional will disable the entire rule when the conditional evaluates to false. 206s 206s 206s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#move-transformation-rule-move 206s Used in: packages.{{PACKAGE}}.transformations 206s Rule reference: TransformationRule::move 206s Plugin: debputy 206s 206s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 206s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 206s + debputy --no-pager plugin show pmr create-symlink 206s Create symlinks transformation rule (`create-symlink`) 206s ====================================================== 206s 206s Often, the upstream build system will provide the symlinks for you. However, 206s in some cases, it is useful for the packager to define distribution specific 206s symlinks. This can be done via the `create-symlink` transformation rule. 206s 206s Attributes: 206s - `path` (required): FileSystemExactMatchRule 206s 206s The path that should be a symlink. The path may contain substitution 206s variables such as `{DEB_HOST_MULTIARCH}` but _cannot_ use globs. 206s Parent directories are implicitly created as necessary. 206s * Note that if `path` already exists, the behavior of this 206s transformation depends on the value of `replacement-rule`. 206s 206s - `target` (required): SymlinkTarget 206s 206s Where the symlink should point to. The target may contain substitution 206s variables such as `{DEB_HOST_MULTIARCH}` but _cannot_ use globs. 206s The link target is _not_ required to exist inside the package. 206s * The `debputy` tool will normalize the target according to the rules 206s of the Debian Policy. Use absolute or relative target at your own 206s preference. 206s 206s - `replacement-rule` (optional): One of the following literal values: "error-if-exists", "error-if-directory", "abort-on-non-empty-directory", "discard-existing" 206s 206s This attribute defines how to handle if `path` already exists. It can 206s be set to one of the following values: 206s - `error-if-exists`: When `path` already exists, `debputy` will 206s stop with an error. This is similar to `ln -s` semantics. 206s - `error-if-directory`: When `path` already exists, **and** it is 206s a directory, `debputy` will stop with an error. Otherwise, 206s remove the `path` first and then create the symlink. This is 206s similar to `ln -sf` semantics. 206s - `abort-on-non-empty-directory` (default): When `path` already 206s exists, then it will be removed provided it is a non-directory 206s **or** an *empty* directory and the symlink will then be 206s created. If the path is a *non-empty* directory, `debputy` 206s will stop with an error. 206s - `discard-existing`: When `path` already exists, it will be 206s removed. If the `path` is a directory, all its contents will 206s be removed recursively along with the directory. Finally, 206s the symlink is created. This is similar to having an explicit 206s `remove` rule just prior to the `create-symlink` that is 206s conditional on `path` existing (plus the condition defined in 206s `when` if any). 206s 206s Keep in mind, that `replacement-rule` only applies if `path` exists. 206s If the symlink cannot be created, because a part of `path` exist and 206s is *not* a directory, then `create-symlink` will fail regardless of 206s the value in `replacement-rule`. 206s 206s - `when` (optional): ManifestCondition 206s 206s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 206s 206s The conditional will disable the entire rule when the conditional evaluates to false. 206s 206s 206s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#create-symlinks-transformation-rule-create-symlink 206s Used in: packages.{{PACKAGE}}.transformations 206s Rule reference: TransformationRule::create-symlink 206s Plugin: debputy 206s 206s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 206s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 207s + debputy --no-pager plugin show pmr path-metadata 207s Change path owner/group or mode (`path-metadata`) 207s ================================================= 207s 207s The `debputy` command normalizes the path metadata (such as ownership and mode) similar 207s to `dh_fixperms`. For most packages, the default is what you want. However, in some 207s cases, the package has a special case or two that `debputy` does not cover. In that 207s case, you can tell `debputy` to use the metadata you want by using the `path-metadata` 207s transformation. 207s 207s Common use-cases include setuid/setgid binaries (such `usr/bin/sudo`) or/and static 207s ownership (such as /usr/bin/write). 207s 207s Attributes: 207s - `path` (conditional): FileSystemMatchRule 207s `paths` (conditional): List of string 207s 207s A path match (`path`) or a list of path matches (`paths`) defining the path(s) 207s inside the package that should be affected. The path match(es) can use globs 207s and substitution variables. Special-rules for matches: 207s - Symlinks are never followed and will never be matched by this rule. 207s - Directory handling depends on the `recursive` attribute. 207s 207s - `owner` (optional): one-of: integer, string 207s 207s Denotes the owner of the paths matched by `path` or `paths`. When omitted, 207s no change of owner is done. 207s 207s - `group` (optional): one-of: integer, string 207s 207s Denotes the group of the paths matched by `path` or `paths`. When omitted, 207s no change of group is done. 207s 207s - `mode` (optional): FileSystemMode 207s 207s Denotes the mode of the paths matched by `path` or `paths`. When omitted, 207s no change in mode is done. Note that numeric mode must always be given as 207s a string (i.e., with quotes). Symbolic mode can be used as well. If 207s symbolic mode uses a relative definition (e.g., `o-rx`), then it is 207s relative to the matched path's current mode. 207s 207s - `capabilities` (optional): Capability 207s 207s Denotes a Linux capability that should be applied to the path. When provided, 207s `debputy` will cause the capability to be applied to all *files* denoted by 207s the `path`/`paths` attribute on install (via `postinst configure`) provided 207s that `setcap` is installed on the system when the `postinst configure` is 207s run. 207s - If any non-file paths are matched, the `capabilities` will *not* be applied 207s to those paths. 207s 207s 207s - `capability-mode` (optional): FileSystemMode 207s 207s Denotes the mode to apply to the path *if* the Linux capability denoted in 207s `capabilities` was successfully applied. If omitted, it defaults to `a-s` as 207s generally capabilities are used to avoid "setuid"/"setgid" binaries. The 207s `capability-mode` is relative to the *final* path mode (the mode of the path 207s in the produced `.deb`). The `capability-mode` attribute cannot be used if 207s `capabilities` is omitted. 207s 207s - `recursive` (optional): boolean 207s 207s When a directory is matched, then the metadata changes are applied to the 207s directory itself. When `recursive` is `true`, then the transformation is 207s *also* applied to all paths beneath the directory. The default value for 207s this attribute is `false`. 207s 207s - `when` (optional): ManifestCondition 207s 207s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 207s 207s The conditional will disable the entire rule when the conditional evaluates to false. 207s 207s 207s This rule enforces the following restrictions: 207s - The rule must use exactly one of: `path`, `paths` 207s 207s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#change-path-ownergroup-or-mode-path-metadata 207s Used in: packages.{{PACKAGE}}.transformations 207s Rule reference: TransformationRule::path-metadata 207s Plugin: debputy 207s 207s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 207s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 207s + debputy --no-pager plugin show pmr create-directories 207s Create directories transformation rule (`create-directories`) 207s ============================================================= 207s 207s NOTE: This transformation is only really needed if you need to create an empty 207s directory somewhere in your package as an integration point. All `debputy` 207s transformations will create directories as required. 207s 207s In most cases, upstream build systems and `debputy` will create all the relevant 207s directories. However, in some rare cases you may want to explicitly define a path 207s to be a directory. Maybe to silence a linter that is warning you about a directory 207s being empty, or maybe you need an empty directory that nothing else is creating for 207s you. This can be done via the `create-directories` transformation rule. 207s 207s Unless you have a specific need for the mapping form, you are recommended to use the 207s shorthand form of just listing the directories you want created. 207s 207s Attributes: 207s - `path` (conditional): FileSystemExactMatchRule 207s `paths` (conditional): List of string 207s 207s A path (`path`) or a list of path (`paths`) defining the path(s) inside the 207s package that should be created as directories. The path(es) _cannot_ use globs 207s but can use substitution variables. Parent directories are implicitly created 207s (with owner `root:root` and mode `0755` - only explicitly listed directories 207s are affected by the owner/mode options) 207s 207s - `owner` (optional): one-of: integer, string 207s 207s Denotes the owner of the directory (but _not_ what is inside the directory). 207s Default is "root". 207s 207s - `group` (optional): one-of: integer, string 207s 207s Denotes the group of the directory (but _not_ what is inside the directory). 207s Default is "root". 207s 207s - `mode` (optional): FileSystemMode 207s 207s Denotes the mode of the directory (but _not_ what is inside the directory). 207s Note that numeric mode must always be given as a string (i.e., with quotes). 207s Symbolic mode can be used as well. If symbolic mode uses a relative 207s definition (e.g., `o-rx`), then it is relative to the directory's current mode 207s (if it already exists) or `0755` if the directory is created by this 207s transformation. The default is "0755". 207s 207s - `when` (optional): ManifestCondition 207s 207s A condition as defined in [Conditional rules](https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#Conditional rules). 207s 207s The conditional will disable the entire rule when the conditional evaluates to false. 207s 207s 207s This rule enforces the following restrictions: 207s - The rule must use exactly one of: `path`, `paths` 207s 207s Non-mapping format: string or a list of string 207s When the input is a string or a list of string, then that value is used as shorthand 207s for `path` or `paths` (respectively). 207s 207s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#create-directories-transformation-rule-directories 207s Used in: packages.{{PACKAGE}}.transformations 207s Rule reference: TransformationRule::create-directories 207s Plugin: debputy 207s 207s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 207s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 207s + debputy --no-pager plugin show pmr run-build-time-tests 208s Whether build time tests should be run `run-build-time-tests` 208s ============================================================= 208s 208s The `run-build-time-tests` condition is used to determine whether (build 208s time) tests should be run for this build. This condition roughly 208s translates into whether `nocheck` is present in `DEB_BUILD_OPTIONS`. 208s 208s In general, the manifest *should not* prevent build time tests from being 208s run during cross-builds. 208s 208s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#whether-build-time-tests-should-be-run-run-build-time-tests-string 208s Used in: *.when 208s Rule reference: ManifestCondition::run-build-time-tests 208s Plugin: debputy 208s 208s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 208s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 208s + debputy --no-pager plugin show pmr arch-matches 208s Architecture match condition `arch-matches` 208s =========================================== 208s 208s Sometimes, a rule needs to be conditional on the architecture. 208s This can be done by using the `arch-matches` rule. In 99.99% 208s of the cases, `arch-matches` will be form you are looking for 208s and practically behaves like a comparison against 208s `dpkg-architecture -qDEB_HOST_ARCH`. 208s 208s For the cross-compiling specialists or curious people: The 208s `arch-matches` rule behaves like a `package-context-arch-matches` 208s in the context of a binary package and like 208s `source-context-arch-matches` otherwise. The details of those 208s are covered in their own keywords. 208s 208s Non-mapping format: string 208s The value must be a string in the form of a space separated list 208s architecture names or architecture wildcards (same syntax as the 208s architecture restriction in Build-Depends in debian/control except 208s there is no enclosing `[]` brackets). The names/wildcards can 208s optionally be prefixed by `!` to negate them. However, either 208s *all* names / wildcards must have negation or *none* of them may 208s have it. 208s 208s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#architecture-match-condition-arch-matches-mapping 208s Used in: *.when 208s Rule reference: ManifestCondition::arch-matches 208s Plugin: debputy 208s 208s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 208s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 208s + debputy --no-pager plugin show pmr not 208s Negated condition `not` (mapping) 208s ================================= 208s 208s It is possible to negate a condition via the `not` condition. 208s 208s As an example: 208s 208s packages: 208s util-linux: 208s transformations: 208s - create-symlink 208s path: sbin/getty 208s target: /sbin/agetty 208s when: 208s # On Hurd, the package "hurd" ships "sbin/getty". 208s # This example happens to also be alternative to `arch-marches: '!hurd-any` 208s not: 208s arch-matches: 'hurd-any' 208s 208s The `not` condition is specified as a mapping, where the key is `not` and the 208s value is a nested condition. 208s 208s Attributes: 208s - `not` (required): ManifestCondition 208s 208s The condition to be negated. 208s 208s 208s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#whether-build-time-tests-should-be-run-run-build-time-tests-string 208s Used in: *.when 208s Rule reference: ManifestCondition::not 208s Plugin: debputy 208s 208s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 208s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 208s + debputy --no-pager plugin show pmr build-profiles-matches 209s Active build profile match condition `build-profiles-matches` 209s ============================================================= 209s 209s The `build-profiles-matches` condition is used to assert whether the 209s active build profiles (`DEB_BUILD_PROFILES` / `dpkg-buildpackage -P`) 209s matches a given build profile restriction. 209s 209s Non-mapping format: string 209s The value is a string using the same syntax as the `Build-Profiles` 209s field from `debian/control` (i.e., a space separated list of 209s `<[!]profile ...>` groups). 209s 209s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#active-build-profile-match-condition-build-profiles-matches-mapping 209s Used in: *.when 209s Rule reference: ManifestCondition::build-profiles-matches 209s Plugin: debputy 209s 209s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 209s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 209s + debputy --no-pager plugin show pmr cross-compiling 209s Cross-Compiling condition `cross-compiling` 209s =========================================== 209s 209s The `cross-compiling` condition is used to determine if the current build is 209s performing a cross build (i.e., `DEB_BUILD_GNU_TYPE` != `DEB_HOST_GNU_TYPE`). 209s Often this has consequences for what is possible to do. 209s 209s Note if you specifically want to know: 209s 209s * whether build-time tests should be run, then please use the 209s `run-build-time-tests` condition. 209s * whether compiled binaries can be run as if it was a native binary, please 209s use the `can-execute-compiled-binaries` condition instead. That condition 209s accounts for cross-building in its evaluation. 209s 209s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#cross-compiling-condition-cross-compiling-string 209s Used in: *.when 209s Rule reference: ManifestCondition::cross-compiling 209s Plugin: debputy 209s 209s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 209s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 209s + debputy --no-pager plugin show pmr binary-version 209s Custom binary version (`binary-version`) 209s ======================================== 209s 209s In the *rare* case that you need a binary package to have a custom version, you can use 209s the `binary-version:` key to describe the desired package version. An example being: 209s 209s packages: 209s foo: 209s # The foo package needs a different epoch because we took it over from a different 209s # source package with higher epoch version 209s binary-version: '1:{DEB_VERSION_UPSTREAM_REVISION}' 209s 209s Use this feature sparingly as it is generally not possible to undo as each version must be 209s monotonously higher than the previous one. This feature translates into `-v` option for 209s `dpkg-gencontrol`. 209s 209s The value for the `binary-version` key is a string that defines the binary version. Generally, 209s you will want it to contain one of the versioned related substitution variables such as 209s `{DEB_VERSION_UPSTREAM_REVISION}`. Otherwise, you will have to remember to bump the version 209s manually with each upload as versions cannot be reused and the package would not support binNMUs 209s either. 209s 209s Non-mapping format: string 209s 209s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#custom-binary-version-binary-version 209s Used in: packages.{{PACKAGE}} 209s Rule reference: packages.{{PACKAGE}}::binary-version 209s Plugin: debputy 209s 209s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 209s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 209s + debputy --no-pager plugin show pmr definitions 210s Packager provided definitions 210s ============================= 210s 210s Reusable packager provided definitions such as manifest variables. 210s 210s Attributes: 210s - `variables` (optional): Mapping of string 210s 210s It is possible to provide custom manifest variables via the `variables` attribute. An example: 210s 210s manifest-version: '0.1' 210s definitions: 210s variables: 210s LIBPATH: "/usr/lib/{DEB_HOST_MULTIARCH}" 210s SONAME: "1" 210s installations: 210s - install: 210s source: build/libfoo.so.{SONAME}* 210s # The quotes here is for the YAML parser's sake. 210s dest-dir: "{LIBPATH}" 210s into: libfoo{SONAME} 210s 210s The value of the `variables` key must be a mapping, where each key is a new variable name and 210s the related value is the value of said key. The keys must be valid variable name and not shadow 210s existing variables (that is, variables such as `PACKAGE` and `DEB_HOST_MULTIARCH` *cannot* be 210s redefined). The value for each variable *can* refer to *existing* variables as seen in the 210s example above. 210s 210s As usual, `debputy` will insist that all declared variables must be used. 210s 210s Limitations: 210s * When declaring variables that depends on another variable declared in the manifest, the 210s order is important. The variables are resolved from top to bottom. 210s * When a manifest variable depends on another manifest variable, the existing variable is 210s currently always resolved in source context. As a consequence, some variables such as 210s `{PACKAGE}` cannot be used when defining a variable. This restriction may be 210s lifted in the future. 210s 210s 210s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#packager-provided-definitions 210s Used in: The manifest root 210s Rule reference: ::definitions 210s Plugin: debputy 210s 210s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 210s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 210s + debputy --no-pager plugin show pmr variables 210s Manifest Variables (`variables`) 210s ================================ 210s 210s It is possible to provide custom manifest variables via the `variables` attribute. An example: 210s 210s manifest-version: '0.1' 210s definitions: 210s variables: 210s LIBPATH: "/usr/lib/{DEB_HOST_MULTIARCH}" 210s SONAME: "1" 210s installations: 210s - install: 210s source: build/libfoo.so.{SONAME}* 210s # The quotes here is for the YAML parser's sake. 210s dest-dir: "{LIBPATH}" 210s into: libfoo{SONAME} 210s 210s The value of the `variables` key must be a mapping, where each key is a new variable name and 210s the related value is the value of said key. The keys must be valid variable name and not shadow 210s existing variables (that is, variables such as `PACKAGE` and `DEB_HOST_MULTIARCH` *cannot* be 210s redefined). The value for each variable *can* refer to *existing* variables as seen in the 210s example above. 210s 210s As usual, `debputy` will insist that all declared variables must be used. 210s 210s Limitations: 210s * When declaring variables that depends on another variable declared in the manifest, the 210s order is important. The variables are resolved from top to bottom. 210s * When a manifest variable depends on another manifest variable, the existing variable is 210s currently always resolved in source context. As a consequence, some variables such as 210s `{PACKAGE}` cannot be used when defining a variable. This restriction may be 210s lifted in the future. 210s 210s Non-mapping format: Mapping of string 210s 210s Reference documentation: No reference documentation link provided by the plugin 210s Used in: definitions 210s Rule reference: definitions::variables 210s Plugin: debputy 210s 210s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 210s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 210s + debputy --no-pager plugin show pmr ::definitions 210s Packager provided definitions 210s ============================= 210s 210s Reusable packager provided definitions such as manifest variables. 210s 210s Attributes: 210s - `variables` (optional): Mapping of string 210s 210s It is possible to provide custom manifest variables via the `variables` attribute. An example: 210s 210s manifest-version: '0.1' 210s definitions: 210s variables: 210s LIBPATH: "/usr/lib/{DEB_HOST_MULTIARCH}" 210s SONAME: "1" 210s installations: 210s - install: 210s source: build/libfoo.so.{SONAME}* 210s # The quotes here is for the YAML parser's sake. 210s dest-dir: "{LIBPATH}" 210s into: libfoo{SONAME} 210s 210s The value of the `variables` key must be a mapping, where each key is a new variable name and 210s the related value is the value of said key. The keys must be valid variable name and not shadow 210s existing variables (that is, variables such as `PACKAGE` and `DEB_HOST_MULTIARCH` *cannot* be 210s redefined). The value for each variable *can* refer to *existing* variables as seen in the 210s example above. 210s 210s As usual, `debputy` will insist that all declared variables must be used. 210s 210s Limitations: 210s * When declaring variables that depends on another variable declared in the manifest, the 210s order is important. The variables are resolved from top to bottom. 210s * When a manifest variable depends on another manifest variable, the existing variable is 210s currently always resolved in source context. As a consequence, some variables such as 210s `{PACKAGE}` cannot be used when defining a variable. This restriction may be 210s lifted in the future. 210s 210s 210s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md#packager-provided-definitions 210s Used in: The manifest root 210s Rule reference: ::definitions 210s Plugin: debputy 210s 210s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 210s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 210s + debputy --no-pager plugin show pmr definitions::variables 211s Manifest Variables (`variables`) 211s ================================ 211s 211s It is possible to provide custom manifest variables via the `variables` attribute. An example: 211s 211s manifest-version: '0.1' 211s definitions: 211s variables: 211s LIBPATH: "/usr/lib/{DEB_HOST_MULTIARCH}" 211s SONAME: "1" 211s installations: 211s - install: 211s source: build/libfoo.so.{SONAME}* 211s # The quotes here is for the YAML parser's sake. 211s dest-dir: "{LIBPATH}" 211s into: libfoo{SONAME} 211s 211s The value of the `variables` key must be a mapping, where each key is a new variable name and 211s the related value is the value of said key. The keys must be valid variable name and not shadow 211s existing variables (that is, variables such as `PACKAGE` and `DEB_HOST_MULTIARCH` *cannot* be 211s redefined). The value for each variable *can* refer to *existing* variables as seen in the 211s example above. 211s 211s As usual, `debputy` will insist that all declared variables must be used. 211s 211s Limitations: 211s * When declaring variables that depends on another variable declared in the manifest, the 211s order is important. The variables are resolved from top to bottom. 211s * When a manifest variable depends on another manifest variable, the existing variable is 211s currently always resolved in source context. As a consequence, some variables such as 211s `{PACKAGE}` cannot be used when defining a variable. This restriction may be 211s lifted in the future. 211s 211s Non-mapping format: Mapping of string 211s 211s Reference documentation: No reference documentation link provided by the plugin 211s Used in: definitions 211s Rule reference: definitions::variables 211s Plugin: debputy 211s 211s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 211s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 211s + debputy --no-pager plugin show pmr :: 211s Auto-generated reference documentation for the manifest root 211s ============================================================ 211s 211s This is an automatically generated reference documentation for the manifest root. It is generated 211s from input provided by debputy via the debputy API. 211s 211s (If you are the provider of the debputy plugin, you can replace this text with 211s your own documentation by providing the `inline_reference_documentation` when registering 211s the manifest rule.) 211s 211s Attributes: 211s - `manifest-version` (optional): One of the following literal values: "0.1" 211s 211s All `debputy` manifests must include a `debputy` manifest version, which will enable the 211s format to change over time. For now, there is only one version (`"0.1"`) and you have 211s to include the line: 211s 211s manifest-version: "0.1" 211s 211s On its own, the manifest containing only `manifest-version: "..."` will not do anything. So if you 211s end up only having the `manifest-version` key in the manifest, you can just remove the manifest and 211s rely entirely on the built-in rules. 211s 211s - `definitions` (optional): Object (see `::definitions`) 211s 211s Reusable packager provided definitions such as manifest variables. 211s 211s - `installations` (optional): 211s 211s For source packages building a single binary, the `dh_auto_install` from debhelper will default to 211s providing everything from upstream's install in the binary package. The `debputy` tool matches this 211s behavior and accordingly, the `installations` feature is only relevant in this case when you need to 211s manually specify something upstream's install did not cover. 211s 211s For sources, that build multiple binaries, where `dh_auto_install` does not detect anything to install, 211s or when `dh_auto_install --destdir debian/tmp` is used, the `installations` section of the manifest is 211s used to declare what goes into which binary package. An example: 211s 211s installations: 211s - install: 211s sources: "usr/bin/foo" 211s into: foo 211s - install: 211s sources: "usr/*" 211s into: foo-extra 211s 211s All installation rules are processed in order (top to bottom). Once a path has been matched, it can 211s no longer be matched by future rules. In the above example, then `usr/bin/foo` would be in the `foo` 211s package while everything in `usr` *except* `usr/bin/foo` would be in `foo-extra`. If these had been 211s ordered in reverse, the `usr/bin/foo` rule would not have matched anything and caused `debputy` 211s to reject the input as an error on that basis. This behavior is similar to "DEP-5" copyright files, 211s except the order is reversed ("DEP-5" uses "last match wins", where here we are doing "first match wins") 211s 211s In the rare case that some path need to be installed into two packages at the same time, then this is 211s generally done by changing `into` into a list of packages. 211s 211s All installations are currently run in *source* package context. This implies that: 211s 211s 1) No package specific substitutions are available. Notably `{PACKAGE}` cannot be resolved. 211s 2) All conditions are evaluated in source context. For 99.9% of users, this makes no difference, 211s but there is a cross-build feature that changes the "per package" architecture which is affected. 211s 211s This is a limitation that should be fixed in `debputy`. 211s 211s **Attention debhelper users**: Note the difference between `dh_install` (etc.) vs. `debputy` on 211s overlapping matches for installation. 211s 211s - `packages` (optional): PackageContext (chains to `::packages`) 211s 211s Inside the manifest, the `packages` mapping can be used to define requests for the binary packages 211s you want `debputy` to produce. Each key inside `packages` must be the name of a binary package 211s defined in `debian/control`. The value is a dictionary defining which features that `debputy` 211s should apply to that binary package. An example could be: 211s 211s packages: 211s foo: 211s transformations: 211s - create-symlink: 211s path: usr/share/foo/my-first-symlink 211s target: /usr/share/bar/symlink-target 211s - create-symlink: 211s path: usr/lib/{DEB_HOST_MULTIARCH}/my-second-symlink 211s target: /usr/lib/{DEB_HOST_MULTIARCH}/baz/symlink-target 211s bar: 211s transformations: 211s - create-directories: 211s - some/empty/directory.d 211s - another/empty/integration-point.d 211s - create-directories: 211s path: a/third-empty/directory.d 211s owner: www-data 211s group: www-data 211s 211s In this case, `debputy` will create some symlinks inside the `foo` package and some directories for 211s the `bar` package. The following subsections define the keys you can use under each binary package. 211s 211s - `build-environments` (optional): 211s 211s Define named environments to set the environment for any build commands that needs 211s a non-default environment. 211s 211s The environment definitions can be used to tweak the environment variables used by the 211s build commands. An example: 211s 211s build-environments: 211s - name: custom-env 211s set: 211s ENV_VAR: foo 211s ANOTHER_ENV_VAR: bar 211s builds: 211s - autoconf: 211s environment: custom-env 211s 211s The environment definition has multiple attributes for setting environment variables 211s which determines when the definition is applied. The resulting environment is the 211s result of the following order of operations. 211s 211s 1. The environment `debputy` received from its parent process. 211s 2. Apply all the variable definitions from `set` (if the attribute is present) 211s 3. Apply all computed variables (such as variables from `dpkg-buildflags`). 211s 4. Apply all the variable definitions from `override` (if the attribute is present) 211s 5. Remove all variables listed in `unset` (if the attribute is present). 211s 211s Accordingly, both `override` and `unset` will overrule any computed variables while 211s `set` will be overruled by any computed variables. 211s 211s Note that these variables are not available via manifest substitution (they are only 211s visible to build commands). They are only available to build commands. 211s 211s - `default-build-environment` (optional): 211s 211s Define the environment variables used in all build commands that uses the default 211s environment. 211s 211s The environment definition can be used to tweak the environment variables used by the 211s build commands. An example: 211s 211s default-build-environment: 211s set: 211s ENV_VAR: foo 211s ANOTHER_ENV_VAR: bar 211s 211s The environment definition has multiple attributes for setting environment variables 211s which determines when the definition is applied. The resulting environment is the 211s result of the following order of operations. 211s 211s 1. The environment `debputy` received from its parent process. 211s 2. Apply all the variable definitions from `set` (if the attribute is present) 211s 3. Apply all computed variables (such as variables from `dpkg-buildflags`). 211s 4. Apply all the variable definitions from `override` (if the attribute is present) 211s 5. Remove all variables listed in `unset` (if the attribute is present). 211s 211s Accordingly, both `override` and `unset` will overrule any computed variables while 211s `set` will be overruled by any computed variables. 211s 211s Note that these variables are not available via manifest substitution (they are only 211s visible to build commands). They are only available to build commands. 211s 211s - `builds` (optional): 211s 211s Define how to build the upstream part of the package. Usually this is done via "build systems", 211s which also defines the clean rules. 211s 211s 211s Reference documentation: https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md 211s Rule reference: :: 211s 211s PS: If you want to know more about a non-trivial type of an attribute such as `FileSystemMatchRule`, 211s you can use `debputy plugin show type-mappings FileSystemMatchRule` to look it up 211s + debputy --no-pager plugin show manifest-variables DEB_SOURCE 212s Variable: DEB_SOURCE 212s ==================== 212s 212s Documentation: Name of the source package (`dpkg-parsechangelog -SSource`) 212s Resolved: debputy 212s Plugin: debputy 212s + debputy --no-pager plugin show manifest-variables token:TAB 212s Variable: token:TAB 212s =================== 212s 212s Documentation: Literal tab character 212s Resolved: \t 212s Plugin: debputy 212s + debputy --no-pager plugin show manifest-variables DEB_HOST_ARCH 212s Variable: DEB_HOST_ARCH 212s ======================= 212s 212s Documentation: Debian's name for the architecture (installed on) 212s This variable describes machine information used when the package is compiled and assembled. 212s * Machine type: The package will be **installed** on this type of machine / system 212s * Value description: Debian's name for the architecture 212s 212s The value is the output of: `dpkg-architecture -qDEB_HOST_ARCH` 212s Resolved: ppc64el 212s + debputy --no-pager plugin show manifest-variables DEB_BUILD_ARCH 213s Variable: DEB_BUILD_ARCH 213s ======================== 213s 213s Documentation: Debian's name for the architecture (compiled on) 213s This variable describes machine information used when the package is compiled and assembled. 213s * Machine type: The compilation of this package will be performed **on** this kind of machine / system 213s * Value description: Debian's name for the architecture 213s 213s The value is the output of: `dpkg-architecture -qDEB_BUILD_ARCH` 213s Resolved: ppc64el 213s Special-case: The variable has been marked as a "special-case"-only variable. 213s + debputy --no-pager plugin show automatic-discard-rules python-cache-files 213s Automatic Discard Rule: python-cache-files 213s ========================================== 213s 213s Discards any *.pyc, *.pyo files and any __pycache__ directories 213s 213s Example 213s ------- 213s 213s Consider the following source paths matched by a glob or directory match: 213s 213s /.../__pycache__/ << Discarded (directly by the rule) 213s /.../__pycache__/... << Discarded (directory was discarded) 213s /.../foo.py 213s /.../foo.pyc << Discarded (directly by the rule) 213s /.../foo.pyo << Discarded (directly by the rule) 213s + debputy --no-pager plugin show automatic-discard-rules la-files 213s Automatic Discard Rule: la-files 213s ================================ 213s 213s Discards any file with the extension .la beneath the directory /usr/lib 213s 213s Example 213s ------- 213s 213s Consider the following source paths matched by a glob or directory match: 213s 213s /usr/lib/libfoo.la << Discarded (directly by the rule) 213s /usr/lib/libfoo.so.1.0.0 213s + debputy --no-pager plugin show automatic-discard-rules backup-files 214s Automatic Discard Rule: backup-files 214s ==================================== 214s 214s Discards common back up files such as foo~, foo.bak or foo.orig 214s 214s Example 214s ------- 214s 214s Consider the following source paths matched by a glob or directory match: 214s 214s /.../.foo.sw. << Discarded (directly by the rule) 214s /.../DEADJOE << Discarded (directly by the rule) 214s /.../foo.orig << Discarded (directly by the rule) 214s /.../foo.rej << Discarded (directly by the rule) 214s /.../foo~ << Discarded (directly by the rule) 214s + debputy --no-pager plugin show automatic-discard-rules version-control-paths 214s Automatic Discard Rule: version-control-paths 214s ============================================= 214s 214s Discards common version control paths such as .git, .gitignore, CVS, etc. 214s 214s Example 214s ------- 214s 214s Consider the following source paths matched by a glob or directory match: 214s 214s /.../.git/ << Discarded (directly by the rule) 214s /.../.git/... << Discarded (directory was discarded) 214s /.../.gitattributes << Discarded (directly by the rule) 214s /.../.gitignore << Discarded (directly by the rule) 214s /.../CVS/ << Discarded (directly by the rule) 214s /.../CVS/... << Discarded (directory was discarded) 214s /tools/foo 214s + debputy --no-pager plugin show automatic-discard-rules gnu-info-dir-file 214s Automatic Discard Rule: gnu-info-dir-file 214s ========================================= 214s 214s Discards the /usr/share/info/dir file (causes package file conflicts) 214s 214s Example 214s ------- 214s 214s Consider the following source paths matched by a glob or directory match: 214s 214s /usr/share/info/dir << Discarded (directly by the rule) 214s /usr/share/info/dir.info 214s /usr/share/info/foo.info 214s /usr/share/random/case/dir 214s + debputy --no-pager plugin show automatic-discard-rules debian-dir 215s Automatic Discard Rule: debian-dir 215s ================================== 215s 215s (Implementation detail) Discards any DEBIAN directory to avoid it from appearing literally in the file listing 215s 215s Example 215s ------- 215s 215s Consider the following source paths matched by a glob or directory match: 215s 215s /DEBIAN/ << Discarded (directly by the rule) 215s /DEBIAN/control << Discarded (directory was discarded) 215s /usr/bin/foo 215s /usr/share/DEBIAN/foo 215s + debputy --no-pager plugin show automatic-discard-rules doxygen-cruft-files 215s Automatic Discard Rule: doxygen-cruft-files 215s =========================================== 215s 215s Discards cruft files generated by doxygen 215s 215s Example 215s ------- 215s 215s Consider the following source paths matched by a glob or directory match: 215s 215s /usr/share/doc/foo/api/.../cruft.map << Discarded (directly by the rule) 215s /usr/share/doc/foo/api/.../cruft.md5 << Discarded (directly by the rule) 215s /usr/share/doc/foo/api/doxygen.css 215s /usr/share/doc/foo/api/doxygen.svg 215s /usr/share/doc/foo/api/index.html 215s + debputy --no-pager tool-support annotate-debian-directory 216s {"result": [{"path": "debian/changelog", "pkgfile-stem": "changelog", "pkgfile-is-active-in-build": true, "pkgfile-explicit-package-name": false, "binary-package": "dh-debputy", "file-categories": ["ppf-file"], "documentation-uris": ["man:dh_installchangelogs(1)"]}, {"path": "debian/copyright", "pkgfile-stem": "copyright", "pkgfile-is-active-in-build": true, "pkgfile-explicit-package-name": false, "binary-package": "dh-debputy", "install-path": "/usr/share/doc/dh-debputy/copyright", "install-pattern": "usr/share/doc/{owning_package}/copyright", "file-categories": ["ppf-file"], "documentation-uris": ["man:dh_installdocs(1)"]}, {"path": "debian/control", "file-categories": ["pkg-metadata"], "documentation-uris": ["man:deb-src-control(5)", "https://www.debian.org/doc/debian-policy/ch-controlfields.html#source-package-control-files-debian-control"]}, {"path": "debian/debputy.manifest", "file-categories": ["pkg-helper-config"], "documentation-uris": ["https://salsa.debian.org/debian/debputy/-/blob/debian/0.1.58/MANIFEST-FORMAT.md"], "debputy-cmd-templates": ["debputy plugin list p-m-r", "debputy plugin show p-m-r {{TOPIC}}"]}, {"path": "debian/gbp.conf", "file-categories": ["maint-config"], "documentation-uris": ["man:gbp.conf(5)"]}, {"path": "debian/rules", "documentation-uris": ["man:deb-src-rules(5)", "https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules"]}, {"path": "debian/source/format", "file-categories": ["pkg-metadata"], "documentation-uris": ["man:dpkg-source(1)"]}, {"path": "debian/tests/control", "file-categories": ["testing"], "documentation-uris": ["https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst", "https://ci.debian.net/doc/file.TUTORIAL.html"]}], "reference-datasets": ["config-features", "file-categories"]}+ debputy --no-pager tool-support export-reference-data --output-format=json 216s {"reference-data": {"config-features": {"dh-filearray": {"description": "The file will be read as a list of space/newline separated tokens"}, "dh-filedoublearray": {"description": "Each line in the file will be read as a list of space-separated tokens"}, "dh-hash-subst": {"description": "Supports debhelper #PACKAGE# style substitutions (udebs often excluded)"}, "dh-dollar-subst": {"description": "Supports debhelper ${PACKAGE} style substitutions (usually requires compat 13+)"}, "dh-glob": {"description": "Supports standard debhelper globing"}, "dh-partial-glob": {"description": "Supports standard debhelper globing but only to a subset of the values (implies dh-late-glob)"}, "dh-late-glob": {"description": "Globbing is done separately instead of using the built-in function"}, "dh-glob-after-execute": {"description": "When the dh config file is executable, the generated output will be subject to globbing"}, "dh-executable-config": {"description": "If marked executable, debhelper will execute the file and read its output"}, "dh-custom-format": {"description": "The dh tool will or may have a custom parser for this file"}, "dh-file-list": {"description": "The dh file contains a list of paths to be processed"}, "dh-install-list": {"description": "The dh file contains a list of paths/globs to be installed but the tool specific knowledge required to understand the file cannot be conveyed via this interface."}, "dh-install-list-dest-dir-like-dh_install": {"description": "The dh file is processed similar to dh_install (notably dest-dir handling derived from the path or the last token on the line)"}, "dh-install-list-fixed-dest-dir": {"description": "The dh file is an install list and the dest-dir is always the same for all patterns (when `install-pattern` or `install-path` are provided, they identify the directory - not the file location)"}, "dh-exec-rename": {"description": "When `dh-exec` is the interpreter of this dh config file, its renaming (=>) feature can be requested/used"}, "dh-docs-only": {"description": "The dh config file is used for documentation only. Implicit Build-Profiles support"}}, "file-categories": {"generated": {"description": "The file is (likely) generated from another file"}, "generic-template": {"description": "The file is (likely) a generic template that generates a known packaging file. While the file is annotated as if it was the target file, the file might uses a custom template language inside it."}, "ppf-file": {"description": "Packager provided file to be installed on the file system - usually as-is. When `install-pattern` or `install-path` are provided, this is where the file is installed."}, "ppf-control-file": {"description": "Packager provided file that becomes a control file - possible after processing. If `install-pattern` or `install-path` are provided, they denote where the is placed (generally, this will be of the form `DEBIAN/`)"}, "maint-config": {"description": "Maintenance configuration for a specific tool that the maintainer uses (tool / style preferences)"}, "pkg-metadata": {"description": "The file is related to standard package metadata (usually documented in Debian Policy)"}, "pkg-helper-config": {"description": "The file is packaging helper configuration or instruction file"}, "testing": {"description": "The file is related to automated testing (autopkgtests, salsa/gitlab CI)."}, "lint-config": {"description": "The file is related to a linter (such as overrides for false-positives or style preferences)"}}}}+ debputy --no-pager tool-support export-reference-data file-categories 216s +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 216s | key | description | 216s +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 216s | generated | The file is (likely) generated from another file | 216s | generic-template | The file is (likely) a generic template that generates a known packaging file. While the file is annotated as if it was the target file, the file might uses a custom template language inside it. | 216s | ppf-file | Packager provided file to be installed on the file system - usually as-is. When `install-pattern` or `install-path` are provided, this is where the file is installed. | 216s | ppf-control-file | Packager provided file that becomes a control file - possible after processing. If `install-pattern` or `install-path` are provided, they denote where the is placed (generally, this will be of the form `DEBIAN/`) | 216s | maint-config | Maintenance configuration for a specific tool that the maintainer uses (tool / style preferences) | 216s | pkg-metadata | The file is related to standard package metadata (usually documented in Debian Policy) | 216s | pkg-helper-config | The file is packaging helper configuration or instruction file | 216s | testing | The file is related to automated testing (autopkgtests, salsa/gitlab CI). | 216s | lint-config | The file is related to a linter (such as overrides for false-positives or style preferences) | 216s +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 216s 216s If you wanted this as JSON, please use --output-format=json 217s autopkgtest [00:04:56]: test debputy-cli: -----------------------] 217s debputy-cli PASS (superficial) 217s autopkgtest [00:04:56]: test debputy-cli: - - - - - - - - - - results - - - - - - - - - - 218s autopkgtest [00:04:57]: test debputy-cli-lint-lsp: preparing testbed 218s Reading package lists... 218s Building dependency tree... 218s Reading state information... 218s Starting pkgProblemResolver with broken count: 0 218s Starting 2 pkgProblemResolver with broken count: 0 218s Done 218s The following NEW packages will be installed: 218s python3-cattr python3-lsprotocol 219s 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. 219s Need to get 96.6 kB of archives. 219s After this operation, 763 kB of additional disk space will be used. 219s Get:1 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-cattr all 23.2.3-1ubuntu1 [38.3 kB] 219s Get:2 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-lsprotocol all 2023.0.1-1 [58.3 kB] 219s Fetched 96.6 kB in 0s (273 kB/s) 219s Selecting previously unselected package python3-cattr. 219s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75740 files and directories currently installed.) 219s Preparing to unpack .../python3-cattr_23.2.3-1ubuntu1_all.deb ... 219s Unpacking python3-cattr (23.2.3-1ubuntu1) ... 219s Selecting previously unselected package python3-lsprotocol. 219s Preparing to unpack .../python3-lsprotocol_2023.0.1-1_all.deb ... 219s Unpacking python3-lsprotocol (2023.0.1-1) ... 219s Setting up python3-cattr (23.2.3-1ubuntu1) ... 219s Setting up python3-lsprotocol (2023.0.1-1) ... 220s autopkgtest [00:04:59]: test debputy-cli-lint-lsp: [----------------------- 220s + debputy lint --linter-exit-code 222s debputy: info: Note: Due to a limitation in the linter, debian/debputy.manifest is 222s debputy: info: only **partially** checked by this command at the time of writing. 222s debputy: info: Please use `debputy check-manifest` to fully check the manifest. 222s + debputy lint --no-linter-exit-code 224s debputy: info: Note: Due to a limitation in the linter, debian/debputy.manifest is 224s debputy: info: only **partially** checked by this command at the time of writing. 224s debputy: info: Please use `debputy check-manifest` to fully check the manifest. 224s + debputy reformat --no-linter-exit-code --no-auto-fix 225s + debputy lsp editor-config 226s This version of debputy has instructions or editor config snippets for the following editors: 226s 226s * emacs (short for: emacs+eglot) 226s * emacs+eglot 226s * vim (short for: vim+youcompleteme) 226s * vim+youcompleteme 226s * vim+vim9lsp 226s * neovim (short for: neovim+nvim-lspconfig) 226s * neovim+nvim-lspconfig 226s 226s Use `debputy editor-config emacs+eglot` (as an example) to see the instructions for a concrete editor. 226s + debputy lsp editor-config emacs 227s ;; `deputy lsp server` glue for emacs eglot (eglot is built-in these days) 227s ;; 227s ;; Add to ~/.emacs or ~/.emacs.d/init.el and then activate via `M-x eglot`. 227s ;; 227s ;; Requires: apt install elpa-dpkg-dev-el elpa-yaml-mode 227s ;; Recommends: apt install elpa-markdown-mode 227s 227s ;; Make emacs recognize debian/debputy.manifest as a YAML file 227s (add-to-list 'auto-mode-alist '("/debian/debputy.manifest\'" . yaml-mode)) 227s ;; Inform eglot about the debputy LSP 227s (with-eval-after-load 'eglot 227s (add-to-list 'eglot-server-programs 227s '( 227s ( 227s ;; Requires elpa-dpkg-dev-el (>= 37.12) 227s (debian-autopkgtest-control-mode :language-id "debian/tests/control") 227s ;; Requires elpa-dpkg-dev-el 227s (debian-control-mode :language-id "debian/control") 227s (debian-changelog-mode :language-id "debian/changelog") 227s (debian-copyright-mode :language-id "debian/copyright") 227s ;; No language id for these atm. 227s makefile-gmake-mode 227s ;; Requires elpa-yaml-mode 227s yaml-mode 227s ) 227s . ("debputy" "lsp" "server") 227s ))) 227s 227s ;; Auto-start eglot for the relevant modes. 227s (add-hook 'debian-control-mode-hook 'eglot-ensure) 227s ;; Requires elpa-dpkg-dev-el (>= 37.12) 227s ;; Technically, the `eglot-ensure` works before then, but it causes a 227s ;; visible and very annoying long delay on opening the first changelog. 227s ;; It still has a minor delay in 37.12, which may still be too long for 227s ;; for your preference. In that case, comment it out. 227s (add-hook 'debian-changelog-mode-hook 'eglot-ensure) 227s (add-hook 'debian-copyright-mode-hook 'eglot-ensure) 227s ;; Requires elpa-dpkg-dev-el (>= 37.12) 227s (add-hook 'debian-autopkgtest-control-mode-hook 'eglot-ensure) 227s (add-hook 'makefile-gmake-mode-hook 'eglot-ensure) 227s (add-hook 'yaml-mode-hook 'eglot-ensure) 227s 227s + debputy lsp editor-config emacs+eglot 228s ;; `deputy lsp server` glue for emacs eglot (eglot is built-in these days) 228s ;; 228s ;; Add to ~/.emacs or ~/.emacs.d/init.el and then activate via `M-x eglot`. 228s ;; 228s ;; Requires: apt install elpa-dpkg-dev-el elpa-yaml-mode 228s ;; Recommends: apt install elpa-markdown-mode 228s 228s ;; Make emacs recognize debian/debputy.manifest as a YAML file 228s (add-to-list 'auto-mode-alist '("/debian/debputy.manifest\'" . yaml-mode)) 228s ;; Inform eglot about the debputy LSP 228s (with-eval-after-load 'eglot 228s (add-to-list 'eglot-server-programs 228s '( 228s ( 228s ;; Requires elpa-dpkg-dev-el (>= 37.12) 228s (debian-autopkgtest-control-mode :language-id "debian/tests/control") 228s ;; Requires elpa-dpkg-dev-el 228s (debian-control-mode :language-id "debian/control") 228s (debian-changelog-mode :language-id "debian/changelog") 228s (debian-copyright-mode :language-id "debian/copyright") 228s ;; No language id for these atm. 228s makefile-gmake-mode 228s ;; Requires elpa-yaml-mode 228s yaml-mode 228s ) 228s . ("debputy" "lsp" "server") 228s ))) 228s 228s ;; Auto-start eglot for the relevant modes. 228s (add-hook 'debian-control-mode-hook 'eglot-ensure) 228s ;; Requires elpa-dpkg-dev-el (>= 37.12) 228s ;; Technically, the `eglot-ensure` works before then, but it causes a 228s ;; visible and very annoying long delay on opening the first changelog. 228s ;; It still has a minor delay in 37.12, which may still be too long for 228s ;; for your preference. In that case, comment it out. 228s (add-hook 'debian-changelog-mode-hook 'eglot-ensure) 228s (add-hook 'debian-copyright-mode-hook 'eglot-ensure) 228s ;; Requires elpa-dpkg-dev-el (>= 37.12) 228s (add-hook 'debian-autopkgtest-control-mode-hook 'eglot-ensure) 228s (add-hook 'makefile-gmake-mode-hook 'eglot-ensure) 228s (add-hook 'yaml-mode-hook 'eglot-ensure) 228s 228s + debputy lsp editor-config vim 228s # debputy lsp server glue for vim with vim-youcompleteme. Add to ~/.vimrc 228s # 228s # Requires: apt install vim-youcompleteme 228s 228s # Make vim recognize debputy.manifest as YAML file 228s au BufNewFile,BufRead debputy.manifest setf yaml 228s # Inform vim/ycm about the debputy LSP 228s # - NB: No known support for debian/tests/control that we can hook into. 228s # Feel free to provide one :) 228s let g:ycm_language_server = [ 228s \ { 'name': 'debputy', 228s \ 'filetypes': [ 'debcontrol', 'debcopyright', 'debchangelog', 'make', 'yaml'], 228s \ 'cmdline': [ 'debputy', 'lsp', 'server', '--ignore-language-ids' ] 228s \ }, 228s \ ] 228s 228s packadd! youcompleteme 228s # Add relevant ycm keybinding such as: 228s # nmap d (YCMHover) 228s 229s autopkgtest [00:05:08]: test debputy-cli-lint-lsp: -----------------------] 229s autopkgtest [00:05:08]: test debputy-cli-lint-lsp: - - - - - - - - - - results - - - - - - - - - - 229s debputy-cli-lint-lsp PASS (superficial) 230s autopkgtest [00:05:09]: test debputy-cli-lsp: preparing testbed 230s Reading package lists... 230s Building dependency tree... 230s Reading state information... 230s Starting pkgProblemResolver with broken count: 0 230s Starting 2 pkgProblemResolver with broken count: 0 230s Done 231s The following NEW packages will be installed: 231s python3-pygls 231s 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 231s Need to get 36.4 kB of archives. 231s After this operation, 265 kB of additional disk space will be used. 231s Get:1 http://ftpmaster.internal/ubuntu plucky/universe ppc64el python3-pygls all 1.3.0-2 [36.4 kB] 231s Fetched 36.4 kB in 0s (160 kB/s) 231s Selecting previously unselected package python3-pygls. 231s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75811 files and directories currently installed.) 231s Preparing to unpack .../python3-pygls_1.3.0-2_all.deb ... 231s Unpacking python3-pygls (1.3.0-2) ... 231s Setting up python3-pygls (1.3.0-2) ... 232s autopkgtest [00:05:11]: test debputy-cli-lsp: [----------------------- 232s + debputy lsp features 233s LSP language IDs and their features: 233s * : 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - inlay hint (doc) 233s - format file handler 233s * dch: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - on-save handler 233s * debchangelog: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - on-save handler 233s * debcontrol: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - inlay hint (doc) 233s - format file handler 233s * debcopyright: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * debian-autopkgtest-control-mode: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * debian-changelog: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - on-save handler 233s * debian-control: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - inlay hint (doc) 233s - format file handler 233s * debian-copyright: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * debian/changelog: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - on-save handler 233s * debian/control: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - inlay hint (doc) 233s - format file handler 233s * debian/copyright: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * debian/debputy.manifest: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - on-save handler 233s * debian/patches/series: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - semantic tokens 233s - on-save handler 233s * debian/rules: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - on-save handler 233s * debian/tests/control: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * debian/upstream/metadata: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - on-save handler 233s * debputy.manifest: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - on-save handler 233s * debtestscontrol: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - folding ranges 233s - semantic tokens 233s - on-save handler 233s - format file handler 233s * make: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - on-save handler 233s * makefile: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - on-save handler 233s * makefile-gmake: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - on-save handler 233s * patches/series: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - semantic tokens 233s - on-save handler 233s * yaml: 233s - diagnostics (lint) 233s - code actions/quickfixes 233s - completion suggestions 233s - hover docs 233s - on-save handler 233s 233s Aliases: 233s 233s General features: 233s * minimum requirements: enabled 233s * typo detection: disabled 233s - Run `apt satisfy 'python3-levenshtein'` to enable this feature 233s * spell checking: disabled 233s - Run `apt satisfy 'hunspell-en-us, python3-hunspell'` to enable this feature 233s * extra dh support: enabled 233s * apt cache packages: enabled 233s + debputy lsp server 234s pygls.feature_manager: info: Registered builtin feature exit 234s pygls.feature_manager: info: Registered builtin feature initialize 234s pygls.feature_manager: info: Registered builtin feature initialized 234s pygls.feature_manager: info: Registered builtin feature notebookDocument/didChange 234s pygls.feature_manager: info: Registered builtin feature notebookDocument/didClose 234s pygls.feature_manager: info: Registered builtin feature notebookDocument/didOpen 234s pygls.feature_manager: info: Registered builtin feature $/setTrace 234s pygls.feature_manager: info: Registered builtin feature shutdown 234s pygls.feature_manager: info: Registered builtin feature textDocument/didChange 234s pygls.feature_manager: info: Registered builtin feature textDocument/didClose 234s pygls.feature_manager: info: Registered builtin feature textDocument/didOpen 234s pygls.feature_manager: info: Registered builtin feature window/workDoneProgress/cancel 234s pygls.feature_manager: info: Registered builtin feature workspace/didChangeWorkspaceFolders 234s pygls.feature_manager: info: Registered builtin feature workspace/executeCommand 234s pygls.feature_manager: info: Registered "initialize" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/didOpen" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/didChange" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/completion" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/hover" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/inlayHint" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/codeAction" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/foldingRange" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/semanticTokens/full" with options "SemanticTokensRegistrationOptions(legend=SemanticTokensLegend(token_types=['keyword', 'enumMember', 'comment', 'string'], token_modifiers=[]), document_selector=None, range=None, full=True, work_done_progress=None, id=None)" 234s pygls.feature_manager: info: Registered "textDocument/willSaveWaitUntil" with options "None" 234s pygls.feature_manager: info: Registered "textDocument/formatting" with options "None" 234s debputy: info: Loaded style preferences: 9 unique maintainer preferences recorded 234s pygls.server: info: Starting IO server 234s pygls.server: info: Shutting down the server 234s pygls.server: info: Closing the event loop. 235s autopkgtest [00:05:14]: test debputy-cli-lsp: -----------------------] 235s autopkgtest [00:05:14]: test debputy-cli-lsp: - - - - - - - - - - results - - - - - - - - - - 235s debputy-cli-lsp PASS (superficial) 236s autopkgtest [00:05:15]: @@@@@@@@@@@@@@@@@@@@ summary 236s debputy-py.test PASS 236s debputy-cli PASS (superficial) 236s debputy-cli-lint-lsp PASS (superficial) 236s debputy-cli-lsp PASS (superficial) 241s nova [W] Using flock in prodstack6-ppc64el 241s Creating nova instance adt-plucky-ppc64el-debputy-20250102-224156-juju-7f2275-prod-proposed-migration-environment-2-a4b677df-d52e-4538-b53b-c7d4c4fc74eb from image adt/ubuntu-plucky-ppc64el-server-20250102.img (UUID e277528a-d512-4652-872e-b2357bc0955c)... 241s nova [W] Timed out waiting for 856397f5-cf04-4cfe-8192-494870b6ab88 to get deleted. 241s nova [W] Using flock in prodstack6-ppc64el 241s Creating nova instance adt-plucky-ppc64el-debputy-20250102-224156-juju-7f2275-prod-proposed-migration-environment-2-a4b677df-d52e-4538-b53b-c7d4c4fc74eb from image adt/ubuntu-plucky-ppc64el-server-20250102.img (UUID e277528a-d512-4652-872e-b2357bc0955c)... 241s nova [W] Timed out waiting for 1fbbc13e-e94c-40be-abed-0ff2fce3eec2 to get deleted.