Processed: Bug#1033913 marked as pending in partman-efi
Processing control commands: > tag -1 pending Bug #1033913 [partman-efi] partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode Added tag(s) pending. -- 1033913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033913: marked as pending in partman-efi
Control: tag -1 pending Hello, Bug #1033913 in partman-efi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/installer-team/partman-efi/-/commit/fcd3c59e48dcf4a962749f53f4244b2540296d4f Fix detection of BIOS-bootable systems Closes: #834373, #1033913 The previous logic was broken in multiple horrible ways, and didn't count things prperly at all. New logic: For each *disk*, check to see if it's BIOS-bootable. That means it must have either an msdos partition table type *or* a GPT partition table type with a BIOS boot partition. If we detect a BIOS-bootable disk which has non-ESP partitions on it, then we will consider that disk to be BIOS-bootable. If we detect that the system has a BIOS-bootable disk *and* has no existing ESPs on it, then we will trigger the "are you sure about UEFI?" warning. Tested in lots of combinations, all work as expected now. Also added lots more logging so we can see what's happend afterwards... (this message was generated automatically) -- Greetings https://bugs.debian.org/1033913
Bug#1030415: marked as done (php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1)
Your message dated Mon, 10 Apr 2023 00:18:51 + with message-id and subject line Bug#1030415: fixed in php-log 1.13.2-2 has caused the Debian Bug report #1030415, regarding php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-log Version: 1.13.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd Log-* && pear run-tests tests > Running 21 tests > PASS [ 1/21] Log: Backtrace Vars[tests/backtrace.phpt] > PASS [ 2/21] Log: Composite Handler[tests/composite.phpt] > PASS [ 3/21] Log: Console Handler[tests/console.phpt] > PASS [ 4/21] Log: Display Handler[tests/display.phpt] > PASS [ 5/21] Log: Error_Log Handler[tests/error_log.phpt] > SKIP Log: _extractMessage() [Zend Engine 2.0][tests/extract-zend2.0.phpt] > FAIL [ 7/21] Log: _extractMessage() [Zend Engine > 2.2][tests/extract-zend2.2.phpt] > PASS [ 8/21] Log: Factory[tests/factory.phpt] > PASS [ 9/21] Log: File Handler[tests/file.phpt] > PASS [10/21] Log: Firebug Handler[tests/firebug.phpt] > PASS [11/21] Log: Line Format[tests/format.phpt] > PASS [12/21] Log: Levels[tests/levels.phpt] > PASS [13/21] Log: Masks[tests/masks.phpt] > PASS [14/21] Log: Null Handler[tests/null.phpt] > PASS [15/21] Log: Priorities[tests/priority.phpt] > PASS [16/21] Log: Singleton[tests/singleton.phpt] > PASS [17/21] Log: SQL setIdent()[tests/sql_ident.phpt] > SKIP Log: Sqlite Handler[tests/sqlite.phpt] > PASS [19/21] Log: Syslog Handler[tests/syslog.phpt] > PASS [20/21] Log: Window Handler (Output Buffering)[tests/win-ob.phpt] > PASS [21/21] Log: Window Handler[tests/win.phpt] > wrote log to "/<>/Log-1.13.2/run-tests.log" > TOTAL TIME: 00:02 > 18 PASSED TESTS > 2 SKIPPED TESTS > 1 FAILED TESTS: > /<>/Log-1.13.2/tests/extract-zend2.2.phpt > Some tests failed > make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/03/php-log_1.13.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: php-log Source-Version: 1.13.2-2 Done: William Desportes We believe that the bug you reported is fixed in the latest version of php-log, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Desportes (supplier of updated php-log package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Mar 2023 02:47:09 +0100 Source: php-log Architecture: source Version: 1.13.2-2 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: William Desportes Closes: 1030415 Changes: php-log (1.13.2-2) unstable; urgency=medium . * Team upload. * Remove Guillaume Delacour from Uploaders * Add a patch to fix a test (Closes: #1030415) * Add gbp.conf and add Vcs-Git: -b . [Debian Janitor] * Upgrade d/watch to v4 * Update Standards-Version to 4.6.2 * Bump debhelper-compat to 12 * Fix linti
Bug#1033834: marked as done (php-log: autopkgtest regression: extract-zend2.2.phpt)
Your message dated Mon, 10 Apr 2023 00:18:51 + with message-id and subject line Bug#1030415: fixed in php-log 1.13.2-2 has caused the Debian Bug report #1030415, regarding php-log: autopkgtest regression: extract-zend2.2.phpt to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-log Version: 1.13.2-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since February 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report (further info is lacking). The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-log/32117259/log.gz 1 FAILED TESTS: /tmp/autopkgtest-lxc.iockyhp3/downtmp/build.ww9/src/Log-1.13.2/tests/extract-zend2.2.phpt OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: php-log Source-Version: 1.13.2-2 Done: William Desportes We believe that the bug you reported is fixed in the latest version of php-log, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Desportes (supplier of updated php-log package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Mar 2023 02:47:09 +0100 Source: php-log Architecture: source Version: 1.13.2-2 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: William Desportes Closes: 1030415 Changes: php-log (1.13.2-2) unstable; urgency=medium . * Team upload. * Remove Guillaume Delacour from Uploaders * Add a patch to fix a test (Closes: #1030415) * Add gbp.conf and add Vcs-Git: -b . [Debian Janitor] * Upgrade d/watch to v4 * Update Standards-Version to 4.6.2 * Bump debhelper-compat to 12 * Fix lintian:day-of-week for changelog entry 1.11.4-1 . * DO NOT SEND THIS BRANCH TO bookworm, use debian/bookworm branch instead Checksums-Sha1: b50cea5280ea68587784ac7766d0953d5e42bff6 2051 php-log_1.13.2-2.dsc 1e169c2dbee69df925179a216748bfce3781fbae 4768 php-log_1.13.2-2.debian.tar.xz 912ea2857bb0956860b6823b011bb6823bce0518 6578 php-log_1.13.2-2_amd64.buildinfo Checksums-Sha256: b7e21219a8e1c783fe48847a02b5fd98f2d34168b1604c90897e25d2f84d8861 2051 php-log_1.13.2-2.dsc 36d48e6e0e9408c6609a95ab94863dccdb370353751aa50d02c4b140465727a4 4768 php-log_1.13.2-2.debian.tar.xz 441a6d74fa15ebdb2dad1c6074045e2f81d7bacd252f8641d8c33784622e581d 6578 php-log_1.13.2-2_amd64.buildinfo Files: d48353b8b28676d6e324de4b362ae0e3 2051 php optional php-log_1.13.2-2.dsc c42d145621af6a7371b4d15d6c4ad97f 4768 php optional php-log_1.13.2-2.debian.tar.xz 063b7c79240b93672ba7f0f003aa0897 6578 php optional php-log_1.13.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmQzUGwWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICAkQD/9EXXTkSXoDRsogNdlMU4lZHMlI IiMu8pCjAs+V0j6yT2B6FNdFrhzW9OhmajDdmvAp6es6JOYb/uTtICk1RP95XPce 4XnODvY9djc8tDCeUC9V0yF9d+UqdKen063FYp4AvH6xIXmzxjqSMxRkfKK+gCuD 0VgKO7rhF0TkR8IlCRT2rDVyIo3B/gScED4ENqrXDWRiU+9yl2G56gOJv8qrGKtj 4YLQfTqzPyjKxRDfYmawrpPZQ919d0PfQxx7xO60ZL2q5CtvcnGvh1EjS++qwSTc 2utyPff+RcE4I8hofqBeOd+Lgcd+4Pz/3xZgQ7kNXX2IvCZ0iK4idjjQKPKZbzqQ LtrweCTEr+xnvuX+mBuYJF5iAVSJcm8YTU7XQ9OiVu/EiVR46e28mzEZtLuu/QdD 1rdcTiEsulgHtM2pU9jLhkWG/gkpfjaoChTMDYE+MVC9EtmEatS7QV+YDVq51fAp 0AwOzu9YGafEnYlFzYoHOB3BjlAUw2RSrzy
Processed: Bug#990746 marked as pending in thawab
Processing control commands:
> tag -1 pending
Bug #990746 {Done: Jeremy Bicha } [thawab]
/usr/bin/thawab-gtk: thawab fails to start.
Added tag(s) pending.
--
990746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990746: marked as done (/usr/bin/thawab-gtk: thawab fails to start.)
Your message dated Sun, 09 Apr 2023 23:48:30 + with message-id <64334ecee35b5_fd344960-...@godard.mail> and subject line Bug#990746 fixed in thawab has caused the Debian Bug report #990746, regarding /usr/bin/thawab-gtk: thawab fails to start. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 990746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thawab Version: 4.1-2 Severity: important File: /usr/bin/thawab-gtk Dear Maintainer, 'thawab' fails to start. I get this when I execute "thawab-gtk" from cmdline: "Traceback (most recent call last): File "/usr/bin/thawab-gtk", line 5, in from Thawab.gtkUi import main File "/usr/share/thawab/Thawab/gtkUi.py", line 34, in from Thawab.webApp import webApp, get_theme_dirs File "/usr/share/thawab/Thawab/webApp.py", line 25, in from cgi import escape # for html escaping ImportError: cannot import name 'escape' from 'cgi' (/usr/lib/python3.9/cgi.py)" Thanks for your work :) Awal -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thawab depends on: ii gir1.2-gtk-3.0 3.24.24-4 ii gir1.2-webkit2-4.0 2.32.1-2 ii mdbtools0.9.1-1 ii python3 3.9.2-3 ii python3-gi 3.38.0-2 ii python3-okasha 0.2.4-4 ii python3-othman 0.6.0-2 ii python3-paste 3.5.0+dfsg1-1 ii python3-whoosh 2.7.4+git6-g9134ad92-5 Versions of packages thawab recommends: pn islamic-menus thawab suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hello, Bug #990746 in thawab reported by you has been fixed in the Git repository. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/thawab/-/commit/6c302acecfbe6e85d0f56a9398e48572210a56e8 Add patch to adapt to Python 3.8 Closes: #990746 (this message was generated automatically) -- Greetings https://bugs.debian.org/990746--- End Message ---
Bug#990746: marked as pending in thawab
Control: tag -1 pending Hello, Bug #990746 in thawab reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/thawab/-/commit/6c302acecfbe6e85d0f56a9398e48572210a56e8 Add patch to adapt to Python 3.8 Closes: #990746 (this message was generated automatically) -- Greetings https://bugs.debian.org/990746
Processed: reassign 1033913 to partman-efi
Processing commands for cont...@bugs.debian.org: > reassign 1033913 partman-efi Bug #1033913 [partman-auto-lvm] partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode Bug reassigned from package 'partman-auto-lvm' to 'partman-efi'. No longer marked as found in versions partman-auto-lvm/87. Ignoring request to alter fixed versions of bug #1033913 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1033913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032104: linux: ppc64el iouring corrupted read
> > > Paul Gevers asked if the issues are gone as well with 6.1.12-1 > > > (or later 6.1.y series versions, which will land in bookworm). That > > > would be valuable information to know as well to exclude we do not > > > have the issue as well in bookworm. > > > > Were you able to verify this? Yes and new kernel did not fix it. I reviewed now all ppc64el autopkgtest runs of src:mariadb at https://ci.debian.net/packages/m/mariadb/testing/ppc64el/ This is still happening on latest kernel and latest src:mariadb in bookworm. The failing test varies, but they all have in common that they error on 'Database page corruption on disk'. autopkgtest [20:11:55]: starting date and time: 2023-04-08 20:11:55+ autopkgtest [20:12:17]: testbed running kernel: Linux 6.1.0-7-powerpc64le #1 SMP Debian 6.1.20-1 (2023-03-19) autopkgtest [20:12:39]: testing package mariadb version 1:10.11.2-1 Completed: Failed 6/1021 tests, 99.41% were successful. Failing test(s): main.innodb_ext_key main.statistics_upgrade_not_done Attached summary of downloading all recent logs and running: $ zgrep -e 'starting date' -e 'running kernel' -e 'testing package mariadb version' -e 'Completed: ' -e 'Failing test(s)' *.gz | tee mariadb-autopkgtest-ppc64el-summary.txt 30542346.log.gz:autopkgtest [16:38:18]: starting date and time: 2023-01-20 16:38:18+ 30542346.log.gz:autopkgtest [16:39:14]: testbed running kernel: Linux 5.10.0-20-powerpc64le #1 SMP Debian 5.10.158-2 (2022-12-13) 30542346.log.gz:autopkgtest [16:39:30]: testing package mariadb version 1:10.11.1-1 30542346.log.gz:Completed: All 1016 tests were successful. 31013059.log.gz:autopkgtest [23:16:23]: starting date and time: 2023-02-03 23:16:23+ 31013059.log.gz:autopkgtest [23:16:53]: testbed running kernel: Linux 5.10.0-20-powerpc64le #1 SMP Debian 5.10.158-2 (2022-12-13) 31013059.log.gz:autopkgtest [23:17:06]: testing package mariadb version 1:10.11.1-2 31013059.log.gz:Completed: All 1016 tests were successful. 31114152.log.gz:autopkgtest [10:00:31]: starting date and time: 2023-02-06 10:00:31+ 31114152.log.gz:autopkgtest [10:00:57]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31114152.log.gz:autopkgtest [10:01:09]: testing package mariadb version 1:10.11.1-3 31114152.log.gz:Completed: Failed 2/1016 tests, 99.80% were successful. 31114152.log.gz:Failing test(s): main.xa_prepared_binlog_off main.update_use_source 31138628.log.gz:autopkgtest [06:52:36]: starting date and time: 2023-02-07 06:52:36+ 31138628.log.gz:autopkgtest [06:53:04]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31138628.log.gz:autopkgtest [06:53:17]: testing package mariadb version 1:10.11.1-3 31138628.log.gz:Completed: All 1016 tests were successful. 31204767.log.gz:autopkgtest [12:32:51]: starting date and time: 2023-02-10 12:32:51+ 31204767.log.gz:autopkgtest [12:33:23]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31204767.log.gz:autopkgtest [12:33:46]: testing package mariadb version 1:10.11.1-4 31204767.log.gz:Completed: Failed 2/1016 tests, 99.80% were successful. 31204767.log.gz:Failing test(s): main.innodb_ext_key main.order_by_innodb 31253808.log.gz:autopkgtest [19:05:34]: starting date and time: 2023-02-11 19:05:34+ 31253808.log.gz:autopkgtest [19:06:15]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31253808.log.gz:autopkgtest [19:06:25]: testing package mariadb version 1:10.11.1-4 31253808.log.gz:Completed: All 1016 tests were successful. 31452860.log.gz:autopkgtest [09:50:34]: starting date and time: 2023-02-17 09:50:34+ 31452860.log.gz:autopkgtest [09:51:00]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31452860.log.gz:autopkgtest [09:51:21]: testing package mariadb version 1:10.11.1-5 31452860.log.gz:Completed: Failed 6/1020 tests, 99.41% were successful. 31452860.log.gz:Failing test(s): main.ctype_utf8mb4_innodb main.index_merge_innodb 31480673.log.gz:autopkgtest [01:00:30]: starting date and time: 2023-02-18 01:00:30+ 31480673.log.gz:autopkgtest [01:01:00]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31480673.log.gz:autopkgtest [01:01:17]: testing package mariadb version 1:10.11.2-1 31480673.log.gz:Completed: Failed 6/1021 tests, 99.41% were successful. 31480673.log.gz:Failing test(s): main.xa_prepared_binlog_off main.range_mrr_icp 31509348.log.gz:autopkgtest [05:09:32]: starting date and time: 2023-02-19 05:09:32+ 31509348.log.gz:autopkgtest [05:10:50]: testbed running kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) 31509348.log.gz:autopkgtest [05:11:06]: testing package mariadb version 1:10.11.2-1 31509348.log.gz:Completed: Failed 3/1019 tests, 99.71% were successful. 31509348.log.gz:Failing test(s): main.ctype_utf8mb4_innodb 323410
Bug#1034128: memcached breaks cachelib autopkgtest: TimeoutError
Source: memcached, cachelib
Control: found -1 memcached/1.6.19-1
Control: found -1 cachelib/0.9.0-1
Severity: serious
Tags: sid bookworm bookworm-ignore
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of memcached the autopkgtest of cachelib fails in
testing when that autopkgtest is run with the binary packages of
memcached from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
memcached from testing1.6.19-1
cachelib from testing0.9.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of memcached to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? [Release Team member hat on]
Because we're currently in the hard freeze for bookworm, I have marked
this bug as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=memcached
https://ci.debian.net/data/autopkgtest/testing/amd64/c/cachelib/32723565/log.gz
=== python3.11 ===
= test session starts
==
platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp
plugins: xprocess-0.22.2
collected 120 items / 1 skipped
tests/test_base_cache.py
[ 10%]
tests/test_file_system_cache.py
[ 43%]
[ 50%]
tests/test_interface_uniformity.py E
[ 50%]
tests/test_memcached_cache.py EEE
[ 60%]
tests/test_redis_cache.py ..
[ 78%]
tests/test_simple_cache.py ..
[100%]
ERRORS
__ ERROR at setup of
TestInterfaceUniformity.test_types_have_all_base_methods __
xprocess =
@pytest.fixture(scope="class")
def memcached_server(xprocess):
package_name = "pylibmc"
pytest.importorskip(
modname=package_name, reason=f"could not find python
package {package_name}"
)
class Starter(ProcessStarter):
pattern = "server listening"
args = ["memcached", "-vv"]
def startup_check(self):
out = subprocess.run(["memcached"], stderr=subprocess.PIPE)
return b"Address already" in out.stderr
> xprocess.ensure(package_name, Starter)
tests/conftest.py:72: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/xprocess/xprocess.py:282: in ensure
if not starter.wait(log_file_handle):
/usr/lib/python3/dist-packages/xprocess/xprocess.py:399: in wait
has_match = any(std.re.search(self.pattern, line) for line in lines)
/usr/lib/python3/dist-packages/xprocess/xprocess.py:399: in
has_match = any(std.re.search(self.pattern, line) for line in lines)
/usr/lib/python3/dist-packages/xprocess/xprocess.py:405: in
non_empty_lines = (x for x in lines if x.strip())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = .Starter object at 0x7fe20a7de690>
log_file = <_io.TextIOWrapper
name='/tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp/.pytest_cache/d/.xprocess/pylibmc/xprocess.log'
mode='r' encoding='UTF-8'>
def get_lines(self, log_file):
"""Read and yield one line at a time from log_file. Will raise
TimeoutError if pattern is not matched before self.timeout
seconds."""
while True:
line = log_file.readline()
if not line:
std.time.sleep(0.1)
if datetime.now() > self._max_time:
raise TimeoutError(
"The provided start pattern {} could not be matched \
within the specified time interval of {}
seconds".format(
self.pattern, self.timeout
)
)
E TimeoutError: The provided start pattern server
listening could not be matched within the specified
time interval of 120 seconds
/usr/lib/python3/dist-packages/xprocess/xprocess.py:422: TimeoutError
Captured stdout setup
-
/tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp/.pytest_cache/d/.xprocess/redis$
redis-server --port 6360
process 'redis' started pid=2393
2393:C 09 Apr 2023 15:11:50.229 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
2393:C 09 Apr 2023 15:11:50.229 # Redis version=7.0.10, bits=64,
Processed: memcached breaks cachelib autopkgtest: TimeoutError
Processing control commands: > found -1 memcached/1.6.19-1 Bug #1034128 [src:memcached, src:cachelib] memcached breaks cachelib autopkgtest: TimeoutError Marked as found in versions memcached/1.6.19-1. > found -1 cachelib/0.9.0-1 Bug #1034128 [src:memcached, src:cachelib] memcached breaks cachelib autopkgtest: TimeoutError Marked as found in versions cachelib/0.9.0-1. -- 1034128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000209: marked as done (timidity-daemon: Fails to install due to no timidity.service)
Your message dated Sun, 09 Apr 2023 19:54:18 + with message-id and subject line Bug#1000209: fixed in timidity 2.14.0-8.1 has caused the Debian Bug report #1000209, regarding timidity-daemon: Fails to install due to no timidity.service to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: timidity-daemon Version: 2.14.0-8 Severity: important X-Debbugs-Cc: witold.bary...@gmail.com root@debian:~# apt install timidity-daemon Reading package lists... Done Building dependency tree... Done Reading state information... Done timidity-daemon is already the newest version (2.14.0-8). 0 upgraded, 0 newly installed, 0 to remove and 567 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up timidity-daemon (2.14.0-8) ... usermod: no changes Failed to stop timidity.service: Unit timidity.service not loaded. invoke-rc.d: initscript timidity, action "stop" failed. dpkg: error processing package timidity-daemon (--configure): installed timidity-daemon package post-installation script subprocess returned error exit status 5 Errors were encountered while processing: timidity-daemon needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.1 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages timidity-daemon depends on: ii adduser 3.118 ii lsb-base 11.1.0 ii timidity 2.14.0-8+b1 timidity-daemon recommends no packages. timidity-daemon suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: timidity Source-Version: 2.14.0-8.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of timidity, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated timidity package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 07 Apr 2023 20:22:10 +0200 Source: timidity Architecture: source Version: 2.14.0-8.1 Distribution: unstable Urgency: medium Maintainer: Bastien Roucariès Changed-By: Paul Gevers Closes: 1000209 Changes: timidity (2.14.0-8.1) unstable; urgency=medium . * Non-maintainer upload * Fix fails to install: invoke update-rc.d before invoke-rc.d (Closes: #1000209) Checksums-Sha1: d6f80a16f809d61901e5390161f64f257dd188a8 2066 timidity_2.14.0-8.1.dsc 2be399a8a4ac1876a59366081aa57fe5e145a8c0 40372 timidity_2.14.0-8.1.debian.tar.xz Checksums-Sha256: fdefe345f3aa5a9d886f6ebeb02407bedb9cef9f5b965349d8f3666d364e01e9 2066 timidity_2.14.0-8.1.dsc 82395446a28362cbcef969554a48ee265a4e286fef61d5b62a19dc396d9cf9ad 40372 timidity_2.14.0-8.1.debian.tar.xz Files: fc9e6f70bf478f455e4ab8dbb4c7395c 2066 sound optional timidity_2.14.0-8.1.dsc 766adc7e81b1f5004eeea26de3033c5d 40372 sound optional timidity_2.14.0-8.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmQwby0ACgkQnFyZ6wW9 dQp53ggAoeOwo7zulfllTVyelmYKTflLik5bizrMRIo0uAtoYd4jjfo6eeY8HBnS Wl0IjXGTddtF5IYCNiuD8QgF9nsWXgyKFcVNMpju0WKecwahep/5dQGp7Km9PadP 2Nxgl1kEO9h1jd7jCzrHqY2ok7D/xMgmajXAdR0Xpo6pkn6I34eED9UJ8D/7Fghe 6NPjN4UFcN/IOF0rzC4tg5+O/a18FUPNBrSDxjbd4STixqJ377ej7GFOnYqXHUoB LHH+Kw9pV1Sg7k3VK6nczEToiBhZx1nYFuNPpVeTbQDwHr1B1Hibw2NAMpqjl383 /2cmqFd3eMrlmxcP0N+Kb8hrQYMDCw== =aSvn -END PGP SIGNATURE End Message ---
Bug#1010347: marked as done (cloudcompare: CVE-2021-21897 - heap-based buffer overflow loading a DXF file via embedded dxflib)
Your message dated Sun, 09 Apr 2023 19:34:18 + with message-id and subject line Bug#1010347: fixed in cloudcompare 2.11.3-7.1 has caused the Debian Bug report #1010347, regarding cloudcompare: CVE-2021-21897 - heap-based buffer overflow loading a DXF file via embedded dxflib to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cloudcompare Version: 2.11.3-5 Severity: important Tags: security X-Debbugs-Cc: codeh...@debian.org, Debian Security Team Hi, The following vulnerability was published for cloudcompare. CVE-2021-21897[0]: | A code execution vulnerability exists in the | DL_Dxf::handleLWPolylineData functionality of Ribbonsoft dxflib | 3.17.0. A specially-crafted .dxf file can lead to a heap buffer | overflow. An attacker can provide a malicious file to trigger this | vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-21897 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21897 Please adjust the affected versions in the BTS as needed. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: cloudcompare Source-Version: 2.11.3-7.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of cloudcompare, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated cloudcompare package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 07 Apr 2023 14:45:46 +0300 Source: cloudcompare Architecture: source Version: 2.11.3-7.1 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Adrian Bunk Closes: 1010347 Changes: cloudcompare (2.11.3-7.1) unstable; urgency=medium . * Non-maintainer upload. * CVE-2021-21897: Heap-based buffer overflow loading a DXF file. (Closes: #1010347) Checksums-Sha1: f6beb197efb58c9fdc634c433c0aab68b416c321 2096 cloudcompare_2.11.3-7.1.dsc bf5e563116110d9e98652d4f0f885b2cfa2aa2d0 12496 cloudcompare_2.11.3-7.1.debian.tar.xz Checksums-Sha256: c5b93db5c0f83654d5519c5be22c87275cd45631cc09961d1e22b74b2ad350ba 2096 cloudcompare_2.11.3-7.1.dsc 75f9fe83d58b93d71c64607d8eb71b3e79f8528f8b3bfd4123de66ef4cf3d6cd 12496 cloudcompare_2.11.3-7.1.debian.tar.xz Files: 781c12e9aa466827cbc5fa4d7f68b4b6 2096 graphics optional cloudcompare_2.11.3-7.1.dsc 20095c5fc30d53a6acaa190896356423 12496 graphics optional cloudcompare_2.11.3-7.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmQwBN8ACgkQiNJCh6LY mLE8ww//dO4zpQDR+CJ/5C1XONCAU3r9OjLDERcBH6NbkBsvRYkyc3imf7sVAFYR xDDIwp5+JoxtI5Z1S21Rc05cZfSXlcAcfNRwJa/Nxt615l48lNQQiU6+22D0nDgU rMq0mPf11OOUw3Lw6Jq9nTIgMBtegFCLDaM6oyj6exsPhzd/4qEB9w7EK14AufhS jw4/UE49r+nJeecw2mPMltGiJOE2v7/kxOpg5gW9/OcUhjrcBI8gcnfMc7ugMy4f odCh43/gB4vAW3RZp9/+/J9rwToE/NfOitMOfXV0j6TviGipBDMz23PQHRvJzDgu +6wvoLpz5bRF8d8QPu8lREFzc4xNyJjsos5KTG1DeA4kaMepfHs7PdEZermUYDe1 r6bE9KzZCyTn/h59F1cEZ/exPYS778HWqkw1i3Dbj2BEZVzqC+Tz4HjMBzPX+ItF EKpP4rJspy3hqjTg1+3pa/jCwvpQLnJP5+a04LAOo+MXQDCqNoT9Eez85X5d/Um9 abDvacaL7v5yEw6YPypvHD1fJVHFzYTin48MRN88oZH6uER/EFmgsQlLvQWU8Fr3 Oth+UMBS1Q7OpDzV/bf8SBhy+H7/ykausbfmbVpEW+0Dj54MgCXuHlWZiDCBrt4k 5Sv4C2PCK+ij1f/R4PuUCa75BfpdhJZ2Z05/swAb0EXmBPgYs5M= =zBYU -END PGP SIGNATURE End Message ---
Bug#1032104: linux: ppc64el iouring corrupted read
Hi Otto, On 09-04-2023 03:54, Otto Kekäläinen wrote: Paul Gevers asked if the issues are gone as well with 6.1.12-1 (or later 6.1.y series versions, which will land in bookworm). That would be valuable information to know as well to exclude we do not have the issue as well in bookworm. Were you able to verify this? No, not yet. I have not done new uploads to experimental after the one I mentioned and linked above from March 18th. I don't understand this point, so I wonder if you understood my question. Maybe you did, but in my view no new uploads are needed to answer the bookworm question. The builds for unstable are passing because I forced the tests to run with regular fsync instead of native I/O in https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d. I will test this again later but right now I don't want to do any extra uploads as the package is pending unblock and inclusion in Bullseye (Bug#1033811) and I don't want one single minor issue to jeopardize getting fixes for multiple major issues forward. My point was that I upgraded the ppc64el hosts where ci.debian.net runs the autopkgtests (so *not* the Debian build infrastructure). Since that upgrade, all tests on ci.debian.net *in every suite* have been using the bookworm (6.1.y) kernel. E.g. in unstable MariaDb 1:10.11.2-1 (so before the "Prevent mariadb-test-run from using native I/O on ppc64el and s390x due to Linux kernel bug" change) passed on 2023-03-26 10:39 but failed on the same day at 14:40. Is any of the failures on ppc64el before 1:10.11.2-2 and after 2023-03-09 from the same kernel issue we're discussing here (and thus the kernel still needs fixing in bookworm). Or are all the failures in that time-span from something else, and thus can we conclude that the kernel *probably* (no proof of course) got fixed between the version of the kernel in bullseye and the version in bookworm. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1034059: marked as pending in zstd-jni-java
On Sun, 9 Apr 2023, Markus Koschany wrote: >maven-compiler-plugin. Usually this just works without changes to the version >number. I don't think a strict plugin dependency is the true solution but it >might help future contributors to remember the RC bug. Also not a real fix but more sustainable might be to just always do an indep build when also doing an archdep build, as that apparently does not have this bug? bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption!
Bug#1034059: marked as pending in zstd-jni-java
Hi tony, Am Sonntag, dem 09.04.2023 um 11:19 -0700 schrieb tony mancill: > > I wanted to ask you your thoughts on whether the fix should also include > updating debian/control to strictly depend on the version(s) specified > in the patched pom. Without some explicit declaration of dependencies, > it seems like this is going to break again, right? Yes, you're right. This will certainly break again if the maven dependencies are updated. I didn't investigate the root cause of the problem but I guess it has something to do with the execute_before_* lines in debian/rules. We call two build systems, maven and cmake, and somehow maven is unable to find the maven-compiler-plugin. Usually this just works without changes to the version number. I don't think a strict plugin dependency is the true solution but it might help future contributors to remember the RC bug. Cheers, Markus signature.asc Description: This is a digitally signed message part
Bug#1034059: marked as pending in zstd-jni-java
On Sat, Apr 08, 2023 at 09:13:00PM +, Markus Koschany wrote: > Control: tag -1 pending > > Hello, > > Bug #1034059 in zstd-jni-java reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/java-team/zstd-jni-java/-/commit/67b4cbfab56dc775db01963cae87ca223b969b4a Hi Markus, Thank you for fixing this, both in unstable and experimental, and to Andreas for pinpointing the problem. I wanted to ask you your thoughts on whether the fix should also include updating debian/control to strictly depend on the version(s) specified in the patched pom. Without some explicit declaration of dependencies, it seems like this is going to break again, right? Thanks, tony signature.asc Description: PGP signature
Bug#1034120: sensible-utils: Broken shell invocation handling
Package: sensible-utils Version: 0.0.18 Severity: serious Hi! I installed this some time ago, and started seeing issues, but was still wondering why no one had reported this already and whether this was a local issue of mine, until I realized now this is an experimental only upload. In any case, when calling «dch» I'm getting stuff like: ,--- $ dch debian/changelog.dch": 1: Syntax error: Unterminated quoted string dch: fatal error at line 1742: Error editing debian/changelog `--- Regards, Guillem
Processed: tagging 1033258
Processing commands for cont...@bugs.debian.org: > tags 1033258 + fixed-upstream Bug #1033258 [src:upx-ucl] upx-ucl: CVE-2023-23456 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031874
Processing commands for cont...@bugs.debian.org: > tags 1031874 + fixed-upstream Bug #1031874 [src:upx-ucl] upx-ucl: CVE-2023-23457 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032553: marked as done (magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 09 Apr 2023 08:56:22 +
with message-id
and subject line Bug#1032553: fixed in magic-wormhole 0.12.0-1.1
has caused the Debian Bug report #1032553,
regarding magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test
-i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1032553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: magic-wormhole
Version: 0.12.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_nameplate.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_interfaces.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_lister.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/__main__.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/tor_manager.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/eventual.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/__init__.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/transit.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_key.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_allocator.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/util.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_code.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_wordlist.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_terminator.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_boss.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_rlcompleter.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/journal.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/xfer_util.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/ipaddrs.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/errors.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_order.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_send.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_input.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_mailbox.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/wormhole.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/timing.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_hints.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_version.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/observer.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_receive.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_rendezvous.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> creating
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/public_relay.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/cmd_ssh.py ->
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cl
