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