Processed: Bug#1061011 marked as pending in octave-zeromq
Processing control commands: > tag -1 pending Bug #1061011 [src:octave-zeromq] octave-zeromq: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1061011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061011: marked as pending in octave-zeromq
Control: tag -1 pending Hello, Bug #1061011 in octave-zeromq 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/pkg-octave-team/octave-zeromq/-/commit/412ae7c144479eb21edaa2c744c4b6e2371b8410 Build documentation from source + d/p/add-mkfuncdocs-py.patch: New patch + d/rules: - Change mode of doc/mkfuncdocs.py - Invoke make to build the Info, HTML and PDF forms of the documentation + d/clean: Drop file + d/control: Build-depend on python3 + d/octave-zeromq.doc-base: Add stanzas for HTML and Info formats + d/octave-zeromq.docs: Add HTML files Gbp-Dch: Full Closes: #1061011 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061011
Processed: bug 1060775 is forwarded to https://github.com/tmux-python/tmuxp/issues/902
Processing commands for cont...@bugs.debian.org: > forwarded 1060775 https://github.com/tmux-python/tmuxp/issues/902 Bug #1060775 [src:tmuxp] tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError Set Bug forwarded-to-address to 'https://github.com/tmux-python/tmuxp/issues/902'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 1060775
Processing commands for cont...@bugs.debian.org:
> reopen 1060775
Bug #1060775 {Done: Sebastien Delafond } [src:tmuxp] tmuxp:
flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError
Bug reopened
Ignoring request to alter fixed versions of bug #1060775 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfixed 1060775 in 1.34.0-2
Processing commands for cont...@bugs.debian.org:
> notfixed 1060775 1.34.0-2
Bug #1060775 {Done: Sebastien Delafond } [src:tmuxp] tmuxp:
flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError
No longer marked as fixed in versions tmuxp/1.34.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1035389: marked as pending in ruby-aws-sdk-core
Control: tag -1 pending Hello, Bug #1035389 in ruby-aws-sdk-core 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/ruby-team/ruby-aws-sdk-core/-/commit/922cc5c5cf05057c1dfb432fc6348a9557ddac79 Include VERSION in package (Closes: #1035389) (this message was generated automatically) -- Greetings https://bugs.debian.org/1035389
Processed: Bug#1035389 marked as pending in ruby-aws-sdk-core
Processing control commands: > tag -1 pending Bug #1035389 [ruby-aws-sdk-core] ruby-aws-sdk-core: The VERSION file is not packaged Added tag(s) pending. -- 1035389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051424: marked as done (ukui-settings-daemon: broken postinst)
Your message dated Thu, 18 Jan 2024 07:04:12 + with message-id and subject line Bug#1051424: fixed in ukui-settings-daemon 3.22.0.0-1 has caused the Debian Bug report #1051424, regarding ukui-settings-daemon: broken postinst 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.) -- 1051424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ukui-settings-daemon Version: 3.1.1.1-1 Severity: grave I attempted to install ukwm on my Debian GNOME Testing install and it got stuck in the postinst. I am filing this as "grave" because a broken postinst like this breaks dpkg until it is fixed or ukui-settings-daemon is uninstalled. As a workaround, I commented out this line in /var/lib/dpkg/info/ukui-settings-daemon.postinst save-param Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: ukui-settings-daemon Source-Version: 3.22.0.0-1 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of ukui-settings-daemon, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. handsome_feng (supplier of updated ukui-settings-daemon 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: Thu, 18 Jan 2024 14:14:46 +0800 Source: ukui-settings-daemon Architecture: source Version: 3.22.0.0-1 Distribution: unstable Urgency: medium Maintainer: Kylin Team Changed-By: handsome_feng Closes: 1051424 Changes: ukui-settings-daemon (3.22.0.0-1) unstable; urgency=medium . * New upstream release. (Closes: #1051424) Checksums-Sha1: 79a5acbd45ec051637db8c63a6a447e18ea7b99f 2981 ukui-settings-daemon_3.22.0.0-1.dsc 84c220265f31b1f5a398654458042992fd8622ad 465337 ukui-settings-daemon_3.22.0.0.orig.tar.gz 39d414ac54b0f74762521a70c9b28d22aabad262 4080 ukui-settings-daemon_3.22.0.0-1.debian.tar.xz 8d24240713c0dc52c92dc298b2c7bb1efffa5cb3 22847 ukui-settings-daemon_3.22.0.0-1_source.buildinfo Checksums-Sha256: 7b20f259686e24490f383afb329bae5b010c74d804375775cc3bd939c6577134 2981 ukui-settings-daemon_3.22.0.0-1.dsc 88f3a51ee3f641e12472d4af47c8c0d46d444cce7aa7baddc04904a3983e19e6 465337 ukui-settings-daemon_3.22.0.0.orig.tar.gz 77a4bc0792748089ebe44c5a2016e18a3692ebc9b89da92d4e22e81fe67b7643 4080 ukui-settings-daemon_3.22.0.0-1.debian.tar.xz 8ece29823a832442c3856a8b9576ce5ddd7b77fbb79eb9db95bc34ba4ad99645 22847 ukui-settings-daemon_3.22.0.0-1_source.buildinfo Files: 4a713e5030803950a1f4ff98eea13fff 2981 x11 optional ukui-settings-daemon_3.22.0.0-1.dsc d7887e2d47bcd11f7da7907932c81ca1 465337 x11 optional ukui-settings-daemon_3.22.0.0.orig.tar.gz f5683321ce1276da137c15fd5f4b7027 4080 x11 optional ukui-settings-daemon_3.22.0.0-1.debian.tar.xz 36deeacd96e2d0e285a1dc6f7e7eef65 22847 x11 optional ukui-settings-daemon_3.22.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJOBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmWoyNEbHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MTUwP+MPfwPLIVLMmdOpEV8+u c61HvV0bwXI4DV5uL3FHEKUV5WzcOUG5QhfyvXvuObKBO282U+g7/w8054xco9LF 3w1e6zVQ2qO85PEfh88uCGCpHv54a+x+/8Mnfl8ztm8FytIsHOdlzYOEjZGYnR/e vPWiYw1rXco81iVuAMlRjaC0i3cCnw+WVmS/O3HrNp1b15X7/wbKTUs5HqSjEl9F ZZnsv/g+aAr0c9gymz5LgVwugcxu80IH9Kb1j6HTLtMehSUXwvtZzoP90hTp2cV5 boWJROLN2RfhJ7bKlxqmJr+MUIGIyQngdRcXxvAm3/7L5ZNr1G7i9VMSsZ+WaR0T MHe2ru0NjH7sr5b/FkYDs3B5vvd9h8Qjc8RrN9c2TN+kHw9s7T9Lt1dd1Yy9TRyW 1yoZrLwhJ8f2FtYj5+NTFsz6ywQE2Dw87aU1VyiGE9CEIN5AXzBUlC8sbs8tcex7 P7LRkAeqL2e+CqZUS5fOzuAmBcXevkQeI1qX7Q0PpRZEsT9jnfhCxwRPEcwhIPB8 WSdqY5ovTC8efzXpQ8lPxyWywX3KHD0xEwer1aVfZ21+5SBZi62dWpaSX9k2tDLo pjfxvSerTPluFteyTVwbzV5yyt5rYGtI5yg/Qf87DFu6PlUQ8l8fvIYu+s7z7ub7 iHOk7eLf2XF28yAurO1CJZ4= =XwSa -END PGP SIGNATURE End Message ---
Processed: bug 1056522 is forwarded to https://github.com/Textualize/rich/issues/3261 ...
Processing commands for cont...@bugs.debian.org:
> forwarded 1056522 https://github.com/Textualize/rich/issues/3261
Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12
Changed Bug forwarded-to-address to
'https://github.com/Textualize/rich/issues/3261' from
'https://github.com/Textualize/rich/pull/2968'.
> forwarded 1058314 https://github.com/Textualize/rich/issues/3261
Bug #1058314 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Changed Bug forwarded-to-address to
'https://github.com/Textualize/rich/issues/3261' from
'https://github.com/Textualize/rich/pull/2968'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056522
1058314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Source: shed Followup-For: Bug #1057613 Hi, Just fyi, MRs will fix the issue: https://salsa.debian.org/pkg-security-team/shed/-/merge_requests -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1058317: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Source: celery Followup-For: Bug #1058317 Note the segmentation fault at the end of python 3.12 pytest run. Using export PYTHONFAULTHANDLER=1 before running the tests, I only got an error in garbage-collector, no trace. It is a bit like #1055717, which was closed by https://salsa.debian.org/python-team/packages/python-multidict/-/commit/2d54ca0b Also I tried with celery 5.3.6, and also with kombu 5.3.5 and vine 5.1.0, no luck. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (101, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1061016: marked as done (sccache: FTBFS: unsatisfiable build-dependencies)
Your message dated Thu, 18 Jan 2024 02:13:26 +0100 with message-id <170554040639.2588145.11758063430467644...@auryn.jones.dk> and subject line Re: Bug#1061016: sccache: FTBFS: unsatisfiable build-dependencies has caused the Debian Bug report #1061016, regarding sccache: FTBFS: unsatisfiable build-dependencies 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.) -- 1061016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sccache Version: 0.7.4-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, > librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, > librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, > librust-async-trait-0.1+default-dev (>= 0.1.52), > librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, > librust-bincode-1+default-dev, librust-blake3-1+default-dev, > librust-byteorder-1+default-dev, librust-bytes-1+default-dev, > librust-chrono-0.4+default-dev, librust-clap-4+default-dev, > librust-counted-array-0.1+default-dev, librust-daemonize-0.5+default-dev, > librust-directories-5+default-dev, librust-encoding-0.2+default-dev, > librust-env-logger-0.10+default-dev, librust-filetime-0.2+default-dev, > librust-flate2-1+rust-backend-dev, librust-fs-err-2+default-dev, > librust-futures-0.3+default-dev, librust-futures-locks-0.7+default-dev, > librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.19), > librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, > librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, > librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, > librust-log-0.4+default-dev, librust-memchr-2+default-dev, > librust-memmap2-0.9+default-dev, librust-mime-0.3+default-dev, > librust-num-cpus-1+default-dev, librust-number-prefix-0.4+default-dev, > librust-object-dev (<< 0.32), librust-once-cell-1+default-dev (>= 1.17), > librust-predicates-3+default-dev, librust-rand-0.8+default-dev, > librust-regex-1+default-dev, librust-reqwest-0.11+blocking-dev, > librust-reqwest-0.11+default-dev, librust-reqwest-0.11+json-dev, > librust-reqwest-0.11+rustls-tls-dev, librust-reqwest-0.11+stream-dev, > librust-reqwest-0.11+trust-dns-dev, librust-retry-2+default-dev, > librust-semver-1+default-dev, librust-serde-1+default-dev, > librust-serde-1+derive-dev, librust-serde-json-1+default-dev, > librust-serial-test-2+default-dev, librust-sha2-0.10+default-dev, > librust-strip-ansi-escapes-0.1+default-dev, librust-tar-0.4+default-dev, > librust-tempfile-3+default-dev, librust-test-case-3+default-dev, > librust-tokio-1+default-dev, librust-tokio-1+io-util-dev, > librust-tokio-1+macros-dev, librust-tokio-1+net-dev, > librust-tokio-1+process-dev, librust-tokio-1+rt-multi-thread-dev, > librust-tokio-1+time-dev, librust-tokio-serde-0.8+default-dev, > librust-tokio-util-0.7+codec-dev, librust-tokio-util-0.7+default-dev, > librust-tokio-util-0.7+io-dev, librust-toml-dev (<< 0.9), > librust-tower-0.4+default-dev, librust-trust-dns-resolver-0.22+default-dev, > librust-trust-dns-resolver-0.22+dns-over-https-rustls-dev, > librust-trust-dns-resolver-0.22+dns-over-rustls-dev, > librust-trust-dns-resolver-0.22+dnssec-ring-dev, librust-url-2+default-dev, > librust-uuid-1+default-dev, librust-uuid-1+v4-dev, > librust-walkdir-2+default-dev, librust-which-4-dev, librust-zip-0.6-dev, > librust-zstd-dev (<< 0.14), libstring-shellquote-perl, rustc (>= 1.65), > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, > librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, > librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, > librust-async-trait-0.1+default-dev (>= 0.1.52), > librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, > librust-bincode-1+default-dev, librust-blake3-1+default-dev, > librust-byteorder-1+default-dev, librust-bytes-1+default-dev, > librust-chrono-0.4+default-dev,
Bug#1060957: marked as done (cedar-backup3: FTBFS: make: *** [debian/rules:11: binary] Error 25)
Your message dated Wed, 17 Jan 2024 21:20:24 + with message-id and subject line Bug#1060957: fixed in cedar-backup3 3.8.0-1 has caused the Debian Bug report #1060957, regarding cedar-backup3: FTBFS: make: *** [debian/rules:11: binary] Error 25 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.) -- 1060957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cedar-backup3 Version: 3.7.9-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3,sphinxdoc --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >dh_auto_build -O--buildsystem=pybuild > I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" > module > I: pybuild base:305: python3.12 -m build --skip-dependency-check > --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12 > * Building wheel... > Successfully built cedar_backup3-3.7.9-py3-none-any.whl > I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with > "installer" module > I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" > module > I: pybuild base:305: python3.11 -m build --skip-dependency-check > --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 > * Building wheel... > Successfully built cedar_backup3-3.7.9-py3-none-any.whl > I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with > "installer" module >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd /<>/.pybuild/cpython3_3.12/build; > python3.12 -m unittest discover -s tests -t tests >
Bug#1061041: marked as done (syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8)
Your message dated Wed, 17 Jan 2024 14:09:54 -0700 with message-id <87plxzd5ul@navis.mail-host-address-is-not-set> and subject line Re: Bug#1061041: syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8 has caused the Debian Bug report #1061041, regarding syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8 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.) -- 1061041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: syncthingtray Version: 1.3.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/debian/build' > /usr/bin/ctest -V > UpdateCTestConfiguration from > :/<>/debian/build/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/debian/build/DartConfiguration.tcl > Test project /<>/debian/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: syncthingconnector_run_tests > > 1: Test command: > /<>/debian/build/connector/syncthingconnector_tests "-p" > "/<>/connector/testfiles" "-w" > "/<>/debian/build/connector/testworkingdir" > 1: Working Directory: /<>/debian/build/connector > 1: Test timeout computed to be: 1000 > 1: /<>/connector/testfiles/ > 1: /<>/connector/testfiles/ > 1: ./testfiles/ > 1: Directory used to store working copies: > 1: /<>/debian/build/connector/testworkingdir/ > 1: [1mExecuting test cases ...[0m > 1: . > 1: - Setup configuration for Syncthing tests ... > 1: - No timeout factor set, defaulting to 1 > 1:(set environment variable SYNCTHING_TEST_TIMEOUT_FACTOR to specify a > factor to run tests on a slow machine) > 1: > 1: - Launching Syncthing: syncthing -gui-address=http://127.0.0.1:4001 > -gui-apikey=syncthingtestinstance > -home=/<>/debian/build/connector/testworkingdir/testconfig > -no-browser -verbose > 1: [1;34mInfo: [0m[1mLaunched process, PID: 1655520[0m > 1: > 1: - Preparing connection ... > 1: > 1: - Error handling in case of insufficient configuration ... > 1: - Connection error: Connection configuration is insufficient. > 1: - Connection status changed to: disconnected > 1: > 1: - Error handling in case of inavailability ... > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: [start] 2024/01/15 20:12:46 INFO: syncthing v1.27.2-ds4 "Gold Grasshopper" > (go1.21.5 linux-amd64) debian@debian 2024-01-06 14:38:16 UTC > 1: [start] 2024/01/15 20:12:46 INFO: Generating ECDSA key and certificate for > syncthing... > 1: [start] 2024/01/15 20:12:46 INFO: Archiving a copy of old config file > format at: > /<>/debian/build/connector/testworkingdir/testconfig/config.xml.v28 > 1: [GUZKE] 2024/01/15 20:12:46 INFO: My ID: > GUZKEQZ-NUIVT6O-EAK4SLK-PICXPBH-NRMSN67-NO2HK4C-KKZSBJF-DRNQKAX > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to:
Processed: src:path.py: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 16.9.0-1 Bug #1061089 [src:path.py] src:path.py: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions path.py/16.9.0-1. Bug #1061089 [src:path.py] src:path.py: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1061089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061089: src:path.py: fails to migrate to testing for too long: autopkgtest regression
Source: path.py Version: 16.7.1-1 Severity: serious Control: close -1 16.9.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:path.py has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=path.py OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:python-anyio: fails to migrate to testing for too long: autopkgtest issues
Processing control commands: > close -1 4.1.0-1 Bug #1061088 [src:python-anyio] src:python-anyio: fails to migrate to testing for too long: autopkgtest issues Marked as fixed in versions python-anyio/4.1.0-1. Bug #1061088 [src:python-anyio] src:python-anyio: fails to migrate to testing for too long: autopkgtest issues Marked Bug as done -- 1061088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061088: src:python-anyio: fails to migrate to testing for too long: autopkgtest issues
Source: python-anyio Version: 3.7.0-1 Severity: serious Control: close -1 4.1.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-anyio has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest and triggers failures in python-watchgod. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-anyio OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1060993: marked as done (distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept')
Your message dated Wed, 17 Jan 2024 20:56:38 + with message-id <20240117205638.7rtexm5uyrzve...@satie.tumbleweed.org.za> and subject line Re: Bug#1060993: distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' has caused the Debian Bug report #1060993, regarding distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' 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.) -- 1060993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 1.7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > py3versions: no X-Python3-Version in control file, using supported versions > cd python && python3.12 setup.py test > 1..35 > testAll > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testDevel > testOldstable > testStable > testSupported > testLTS > testELTS > testUnsupported > testTesting > testFullname > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > WARNING: The wheel package is not available. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > test_all
Processed: notfound 1060993 in 1.7
Processing commands for cont...@bugs.debian.org: > notfound 1060993 1.7 Bug #1060993 [src:distro-info] distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' No longer marked as found in versions distro-info/1.7. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el
Processing control commands: > close -1 0.29.1+ds-1 Bug #1061086 [src:bpfcc] src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions bpfcc/0.29.1+ds-1. Bug #1061086 [src:bpfcc] src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el Marked Bug as done -- 1061086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061086: src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el
Source: bpfcc Version: 0.26.0+ds-1 Severity: serious Control: close -1 0.29.1+ds-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:bpfcc has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build on ppc64el. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=bpfcc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied
Hi Santiago, Santiago Vila (2023-12-05): > […] Thanks for the report. The relevant part didn't appear in the excerpt so I'm quoting the full build log below: > === RUN TestOneShot/permission_denied > file_test.go:234: > Error Trace: > /<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/cstest/utils.go:25 > > /<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/file/file_test.go:234 > Error: An error is expected but got nil. > Test: TestOneShot/permission_denied > === RUN TestOneShot/ignored_directory > === RUN TestOneShot/glob_syntax_error > === RUN TestOneShot/no_matching_files > === RUN TestOneShot/test.log > === RUN TestOneShot/test.log.gz > === RUN TestOneShot/unexpected_end_of_gzip_stream > === RUN TestOneShot/deleted_file > --- FAIL: TestOneShot (0.00s) > --- FAIL: TestOneShot/permission_denied (0.00s) > --- PASS: TestOneShot/ignored_directory (0.00s) > --- PASS: TestOneShot/glob_syntax_error (0.00s) > --- PASS: TestOneShot/no_matching_files (0.00s) > --- PASS: TestOneShot/test.log (0.00s) > --- PASS: TestOneShot/test.log.gz (0.00s) > --- PASS: TestOneShot/unexpected_end_of_gzip_stream (0.00s) > --- PASS: TestOneShot/deleted_file (0.00s) I'll investigate shortly. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Processed: [libsass-python] RC Bug #1058362: forward to upstream commit that fixes the FTBFS
Processing commands for cont...@bugs.debian.org: > forwarded 1058362 > https://github.com/sass/libsass-python/commit/f0dc392782754e0f5632190c2e9940cc282eef53 Bug #1058362 [src:libsass-python] libsass-python: FTBFS: TypeError: not all arguments converted during string formatting Set Bug forwarded-to-address to 'https://github.com/sass/libsass-python/commit/f0dc392782754e0f5632190c2e9940cc282eef53'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058381: casa-formats-io: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, > ERRORS > > _ ERROR collecting > .pybuild/cpython3_3.12_casa-formats-io/build/casa_formats_io/glue_factory.py _ > /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call > result: Optional[TResult] = func() > /usr/lib/python3/dist-packages/_pytest/runner.py:372: in > call = CallInfo.from_call(lambda: list(collector.collect()), "collect") > /usr/lib/python3/dist-packages/pytest_doctestplus/plugin.py:250: in collect > module = import_path(fspath, root=self.config.rootpath) > /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path > importlib.import_module(module_name) > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > :1387: in _gcd_import > ??? > :1360: in _find_and_load > ??? > :1331: in _find_and_load_unlocked > ??? > :935: in _load_unlocked > ??? > :994: in exec_module > ??? > :488: in _call_with_frames_removed > ??? > casa_formats_io/glue_factory.py:7: in > from glue.core import Data > /usr/lib/python3/dist-packages/glue/__init__.py:22: in > from .config import load_configuration > /usr/lib/python3/dist-packages/glue/config.py:2: in > import imp > E ModuleNotFoundError: No module named 'imp' > === short test summary info > > ERROR casa_formats_io/glue_factory.py - ModuleNotFoundError: No module named > ... > Interrupted: 1 error during collection > > === 1 error in 1.37s > === The issue comes from glue's source code. 'imp' module was removed from Python 3.12 [1] Kind Regards [1] https://docs.python.org/3/whatsnew/3.12.html#imp
Bug#1058432: glyphslib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 > rootdir: /<>/.pybuild/cpython3_3.12/build > configfile: pyproject.toml > collected 0 items / 29 errors > > ERRORS > > ERROR collecting tests/classes_test.py > > ImportError while importing test module > '/<>/.pybuild/cpython3_3.12/build/tests/classes_test.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > tests/classes_test.py:23: in > from glyphsLib.classes import ( > glyphsLib/__init__.py:21: in > from glyphsLib.classes import GSFont, __all__ as __all_classes__ > glyphsLib/classes.py:26: in > import openstep_plist > /usr/lib/python3/dist-packages/openstep_plist/__init__.py:1: in > from .parser import load, loads, ParseError > E ModuleNotFoundError: No module named 'openstep_plist.parser' ... ... after python-openstep-plist/0.3.1-1 entered in unstable [1], your package builds fine locally in a sid chroot environment and autopkg tests pass as well. Please consider to close this bug when you are able to confirm that. Kind Regards [1] https://tracker.debian.org/media/packages/p/python-openstep-plist/changelog-0.3.1-1
Bug#1058388: fontmake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, > fontmake/font_project.py:946: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > fontmake/font_project.py:1006: in _run_from_designspace_static > ufos.extend( > fontmake/font_project.py:744: in interpolate_instance_ufos > from glyphsLib.interpolation import apply_instance_data_to_ufo > /usr/lib/python3/dist-packages/glyphsLib/__init__.py:21: in > from glyphsLib.classes import GSFont, __all__ as __all_classes__ > /usr/lib/python3/dist-packages/glyphsLib/classes.py:26: in > import openstep_plist > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > > > from .parser import load, loads, ParseError > E ModuleNotFoundError: No module named 'openstep_plist.parser' > > /usr/lib/python3/dist-packages/openstep_plist/__init__.py:1: > ModuleNotFoundError after python-openstep-plist/0.3.1-1 entered in unstable [1], your package builds fine locally in a sid chroot environment. Please consider to close this bug when you are able to confirm that. Kind Regards [1] https://tracker.debian.org/media/packages/p/python-openstep-plist/changelog-0.3.1-1
Bug#1060989: marked as done (astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2)
Your message dated Wed, 17 Jan 2024 19:04:26 + with message-id and subject line Bug#1060989: fixed in astap 2024.01.16-1 has caused the Debian Bug report #1060989, regarding astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 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.) -- 1060989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astap Version: 2022.12.09-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lazbuild --widgetset=qt5 astap_linux.lpi > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /<>/tmphome/.lazarus/environmentoptions.xml > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $55E0224A2B7A > $55E02249DB65 > $55E0223F9F2E > $55E022A4B713 > $55E0225ADC83 > $55E0225981DE > $55E0225980D8 > $55E0223FE13D > $55E0223FBD64 > $55E0223FA3EB > $55E0223FFC93 > $55E022402979 > $55E02242475C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/astap_2022.12.09-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=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: astap Source-Version: 2024.01.16-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of astap, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated astap 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: Tue, 16 Jan 2024 22:30:51 +0100 Source: astap Architecture: source Version: 2024.01.16-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Thorsten Alteholz Closes: 1060989 Changes: astap (2024.01.16-1) unstable; urgency=medium . * new upstream version * debian/control: add new dependency: lazarus-src (Closes: #1060989) Checksums-Sha1: eb2ea21ba1d9a53ec6f445a3341a8d4cf0fdc501 2176 astap_2024.01.16-1.dsc 575455ff734069b9119472382a19878bf08bb9d0 2322526 astap_2024.01.16.orig.tar.gz 5d0c55fffaac59f2c0b6bb63d154c3c4ad1500ac 5564 astap_2024.01.16-1.debian.tar.xz db9dfbcc7c0d43d33260935676d9462312b023a4 14447 astap_2024.01.16-1_amd64.buildinfo Checksums-Sha256: 7ba5651aa63e09be0512d564d2fa5ad3fa3000e81395ed4df92037fbe657f70d 2176 astap_2024.01.16-1.dsc 7b3d99d5a2bd4dce58bd71a743e6fe96e97985f35bf4abbe69065d23c7153bfb 2322526 astap_2024.01.16.orig.tar.gz 4cf721fc6fdedaad8714e4a8c9c536fe9e613530d8880c6d495a80312915312d 5564 astap_2024.01.16-1.debian.tar.xz 97bec200fbf97aa2b50ecb8f42fa97ffcca834045e5ab8145205561bbc23e86b 14447 astap_2024.01.16-1_amd64.buildinfo Files: 0d627922810977614569f1a13d1054a0 2176 science optional astap_2024.01.16-1.dsc cd15fadab04b929906a2cfe20267b709 2322526 science optional
Bug#1060740: marked as done (regripper: autopkgtest failure with Perl 5.38: changed diagnostics)
Your message dated Wed, 17 Jan 2024 19:05:34 + with message-id and subject line Bug#1060740: fixed in regripper 3.0~git20221205.d588019+dfsg-1.1 has caused the Debian Bug report #1060740, regarding regripper: autopkgtest failure with Perl 5.38: changed diagnostics 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.) -- 1060740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: regripper Version: 3.0~git20221205.d588019+dfsg-1 Severity: serious Tags: trixie sid User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails its autopkgtest checks with Perl 5.38 (currently in unstable.) https://ci.debian.net/packages/r/regripper/testing/amd64/41787955/ 27s autopkgtest [07:40:54]: test listplugins: [--- 28s autopkgtest [07:40:55]: test listplugins: ---] 28s autopkgtest [07:40:55]: test listplugins: - - - - - - - - - - results - - - - - - - - - - 28s listplugins FAIL non-zero exit status 1 This is unfortunately terse, but looking into it, it boils down to a changed diagnostic when calling require() on a plugin with a syntax error: trixie# perl -E 'say $^V; eval "require q(/usr/lib/regripper/plugins/clsid_tln.pl)"; die $@' v5.36.0 syntax error at /usr/lib/regripper/plugins/clsid_tln.pl line 112, near "$scriptlet)" Compilation failed in require at (eval 1) line 1. vs. sid# perl -E 'say $^V; eval "require q(/usr/lib/regripper/plugins/clsid_tln.pl)"; die $@' v5.38.2 syntax error at /usr/lib/regripper/plugins/clsid_tln.pl line 112, near "$scriptlet)" Execution of /usr/lib/regripper/plugins/clsid_tln.pl aborted due to compilation errors. Compilation failed in require at (eval 1) line 1. Presumably the best fix is to correct the (longstanding) syntax error in the plugin. Sorry for not catching this earlier. I only checked packages with Testsuite: autopkgtest-pkg-perl or Testsuite-Triggers: perl. I suppose I should have looked at Depends:perl too. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: regripper Source-Version: 3.0~git20221205.d588019+dfsg-1.1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of regripper, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated regripper 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: Wed, 17 Jan 2024 19:48:47 CET Source: regripper Binary: Architecture: source Version: 3.0~git20221205.d588019+dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: gregor herrmann Description: Closes: 1060740 Changes: regripper (3.0~git20221205.d588019+dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix "autopkgtest failure with Perl 5.38: changed diagnostics": Add patch from upstream Git repo fixing a syntax error (stray parenthesis) in ./plugins/clsid_tln.pl. Additionally add the now fixed clsid_tln plugin to debian/tests/testfiles/regripper-plugins.csv, the file containing the expected plugins. (Closes: #1060740) Checksums-Sha256: 41283fb6b473733304d094634a0b14a23d53e59832c646cc1e11acefe9dbfcc5 2287 regripper_3.0~git20221205.d588019+dfsg-1.1.dsc ebf0fd44772b75712e5ac71c0ab1a5c3dcfbed747da132717afb460056597cd7 123856 regripper_3.0~git20221205.d588019+dfsg-1.1.debian.tar.xz d35017f42ee7e8131bd7bf5609ee842e49268785f3ad9041a5be4c36628806db 6377 regripper_3.0~git20221205.d588019+dfsg-1.1_sourceonly.buildinfo Checksums-Sha1: 8c1b9e20b3a19abc6d16d5aa859b709bd4e5b2ad 2287 regripper_3.0~git20221205.d588019+dfsg-1.1.dsc 6b075de48d40900cf9c5bfceeefb2686ec2ee82d 123856 regripper_3.0~git20221205.d588019+dfsg-1.1.debian.tar.xz 902fae457e1c2a6414793b1101815cb963b3d3c6 6377 regripper_3.0~git20221205.d588019+dfsg-1.1_sourceonly.buildinfo Files: 934f976b0361942484f62dd771dec8ca 2287 utils optional regripper_3.0~git20221205.d588019+dfsg-1.1.dsc
Bug#1060999: marked as done (octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25)
Your message dated Wed, 17 Jan 2024 18:50:26 +
with message-id
and subject line Bug#1060999: fixed in octave-sockets 1.4.1-3
has caused the Debian Bug report #1060999,
regarding octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25
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.)
--
1060999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-sockets
Version: 1.4.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> /usr/bin/mkoctfile --verbose socket.cc
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protectionsocket.cc -o /tmp/oct-DW4tFF.o
> Extracting tests from socket.cc ...
> g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o socket.oct /tmp/oct-DW4tFF.o
> -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu -shared
> -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/socket.oct
> /<>/./src/socket.cc-tst
> /<>/./inst/x86_64-pc-linux-gnu-api-v58
> For information about changes from previous versions of the sockets package,
> run 'news sockets'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> Checking C++ files ...
> [src/socket.cc]
> > /<>/src/socket.cc
> * test
> ## Server socket
> server = socket (AF_INET, SOCK_STREAM, 0);
> assert (server >= 0);
>
> rc = bind (server, 9001);
> assert (rc, 0);
>
> rc = listen (server, 1);
> assert (rc, 0);
>
> ## Client socket
> client = socket (AF_INET, SOCK_STREAM, 0);
> assert (client >= 0);
>
> ## Create the connection and accept the connection
> server_info = struct ("addr", "127.0.0.1", "port", 9001);
> rc = connect (client, server_info);
> assert (rc, 0);
>
> server_data = accept (server);
> assert (server_data >= 0);
>
> ## Send and receive data
>
> ## Send as string from client
> msg = "Hello socket-land!";
> rc = send (client, msg);
> assert (rc,length (msg));
>
> ## Receive at server
> [msg_s, len_s] = recv (server_data, 100);
> assert (msg_s != -1);
> assert (len_s, length (msg));
>
> ## Send back out from server
> rc = send (server_data, msg_s);
> assert (rc, length (msg_s));
>
> ## Receive at client
> [msg_c, len_c] = recv (client, 100);
> assert (msg_c != -1);
> assert (len_c, length (msg));
>
> ## Compare original string with recv string
> assert (msg, num2str (msg_c, "%c"));
>
> assert (shutdown (client, SHUT_WR), 0);
> assert (shutdown (client, SHUT_RD), 0);
> assert (shutdown (client, SHUT_RDWR), 0);
>
> assert (disconnect (client), 0);
> assert (disconnect (server_data), 0);
> assert (disconnect (server), 0);
> * test
> ## UDP
> sock = socket (AF_INET, SOCK_DGRAM, 0);
> assert (sock >= 0);
>
> rc = bind (sock, 9001);
> assert (rc, 0);
>
> msg = "Hello socket-land!";
> addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
> rc = sendto (sock, msg, 0, addrinfo);
> assert (rc,length (msg));
>
> [msg_c, len_c, addr_c] = recvfrom (sock, 100);
> assert (msg_c != -1);
> assert (len_c, length (msg));
> assert (addr_c.port, 9001);
>
> assert (msg, num2str (msg_c, "%c"));
>
> assert (disconnect (sock), 0);
> * test
> assert (SOL_SOCKET != 0)
> assert (MSG_WAITALL != 0)
> assert (MSG_PEEK != 0)
> assert (SO_REUSEADDR != 0)
> assert (SO_KEEPALIVE != 0)
> assert (SO_TYPE != 0)
> assert (SHUT_RD, 0)
> assert (SHUT_WR, 1)
> assert (SHUT_RDWR, 2)
> * test
> ## select
> sock = socket (AF_INET, SOCK_DGRAM, 0);
> assert (sock >= 0);
>
> rc = bind (sock, 9001);
> assert (rc, 0);
>
> [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [sock], [sock], 1);
> assert(ret, 1);
> assert(rdfs, []);
> # initial open
> assert(wdfs, [sock]);
> assert(edfs, []);
>
> msg = "Hello socket-land!";
> addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
> rc = sendto (sock, msg,
Bug#1060740: regripper: diff for NMU version 3.0~git20221205.d588019+dfsg-1.1
Dear maintainer,
I've prepared and uploaded an NMU for regripper (versioned as
3.0~git20221205.d588019+dfsg-1.1). The diff is attached to this
message.
Sorry for the rush, this was one of the last blockers of the ongoing
perl 5.38 migration.
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru regripper-3.0~git20221205.d588019+dfsg/debian/changelog regripper-3.0~git20221205.d588019+dfsg/debian/changelog
--- regripper-3.0~git20221205.d588019+dfsg/debian/changelog 2022-12-11 09:36:06.0 +0100
+++ regripper-3.0~git20221205.d588019+dfsg/debian/changelog 2024-01-17 19:45:41.0 +0100
@@ -1,3 +1,16 @@
+regripper (3.0~git20221205.d588019+dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "autopkgtest failure with Perl 5.38: changed diagnostics":
+Add patch from upstream Git repo fixing a syntax error (stray
+parenthesis) in ./plugins/clsid_tln.pl.
+Additionally add the now fixed clsid_tln plugin to
+debian/tests/testfiles/regripper-plugins.csv, the file containing the
+expected plugins.
+(Closes: #1060740)
+
+ -- gregor herrmann Wed, 17 Jan 2024 19:45:41 +0100
+
regripper (3.0~git20221205.d588019+dfsg-1) unstable; urgency=medium
[ Jan Gruber ]
diff -Nru regripper-3.0~git20221205.d588019+dfsg/debian/patches/1060740.patch regripper-3.0~git20221205.d588019+dfsg/debian/patches/1060740.patch
--- regripper-3.0~git20221205.d588019+dfsg/debian/patches/1060740.patch 1970-01-01 01:00:00.0 +0100
+++ regripper-3.0~git20221205.d588019+dfsg/debian/patches/1060740.patch 2024-01-17 19:32:16.0 +0100
@@ -0,0 +1,22 @@
+From ca9d83387e10854093f066a1ebe80cfc6852c832 Mon Sep 17 00:00:00 2001
+From: Andreas Hunkeler
+Date: Tue, 21 Mar 2023 19:18:29 +0100
+Subject: [PATCH] fix: remove unneeded parenthesis in clsid_tln.pl
+
+---
+ plugins/clsid_tln.pl | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/plugins/clsid_tln.pl b/plugins/clsid_tln.pl
+index adfe2df..eb57770 100644
+--- a/plugins/clsid_tln.pl
b/plugins/clsid_tln.pl
+@@ -109,7 +110,7 @@ sub pluginmain {
+
+ eval {
+ my $scriptlet = $s->get_subkey("ScriptletURL")->get_value("")->get_data();
+- ::rptMsg($s->get_subkey("ScriptletURL")->get_timestamp())."|REG|||CLID - ".$name."\\ScriptletURL: ".$scriptlet);
++ ::rptMsg($s->get_subkey("ScriptletURL")->get_timestamp()."|REG|||CLID - ".$name."\\ScriptletURL: ".$scriptlet);
+ };
+ }
+ }
diff -Nru regripper-3.0~git20221205.d588019+dfsg/debian/patches/series regripper-3.0~git20221205.d588019+dfsg/debian/patches/series
--- regripper-3.0~git20221205.d588019+dfsg/debian/patches/series 2022-12-11 09:36:06.0 +0100
+++ regripper-3.0~git20221205.d588019+dfsg/debian/patches/series 2024-01-17 19:32:16.0 +0100
@@ -1 +1,2 @@
10_modify-paths-in-srcs.patch
+1060740.patch
diff -Nru regripper-3.0~git20221205.d588019+dfsg/debian/tests/testfiles/regripper-plugins.csv regripper-3.0~git20221205.d588019+dfsg/debian/tests/testfiles/regripper-plugins.csv
--- regripper-3.0~git20221205.d588019+dfsg/debian/tests/testfiles/regripper-plugins.csv 2022-12-11 09:36:06.0 +0100
+++ regripper-3.0~git20221205.d588019+dfsg/debian/tests/testfiles/regripper-plugins.csv 2024-01-17 19:45:09.0 +0100
@@ -250,3 +250,4 @@
gpohist,,Software,Collects system/user GPO history
imagedev,20140104,System, --
winrar,20200526,NTUSER.DAT,Get WinRAR\ArcHistory entries
+clsid_tln,20200526,Software, USRCLASS.DAT,Get list of CLSID/registered classes
signature.asc
Description: Digital Signature
Bug#1060710: marked as done (dnsenum: autopkgtest failure with Perl 5.38: Smartmatch is deprecated)
Your message dated Wed, 17 Jan 2024 18:49:08 + with message-id and subject line Bug#1060710: fixed in dnsenum 1.3.1-1.1 has caused the Debian Bug report #1060710, regarding dnsenum: autopkgtest failure with Perl 5.38: Smartmatch is deprecated 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.) -- 1060710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnsenum Version: 1.3.1-1 Severity: serious User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails its autopkgtest checks with Perl 5.38 (currently in unstable.) 28s autopkgtest [21:35:23]: test command1: - - - - - - - - - - results - - - - - - - - - - 28s command1 FAIL stderr: Smartmatch is deprecated at /usr/bin/dnsenum line 749. 29s autopkgtest [21:35:24]: test command1: - - - - - - - - - - stderr - - - - - - - - - - 29s Smartmatch is deprecated at /usr/bin/dnsenum line 749. 29s Smartmatch is deprecated at /usr/bin/dnsenum line 751. Sorry for not catching this earlier. I only checked packages with Testsuite: autopkgtest-pkg-perl or Testsuite-Triggers: perl. I suppose I should have looked at Depends:perl too. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: dnsenum Source-Version: 1.3.1-1.1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of dnsenum, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated dnsenum 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: Wed, 17 Jan 2024 19:28:17 CET Source: dnsenum Binary: Architecture: source Version: 1.3.1-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: gregor herrmann Description: Closes: 1060710 Changes: dnsenum (1.3.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix "autopkgtest failure with Perl 5.38: Smartmatch is deprecated": add patch perl5.38_smartmatch.patch, replacing smartmatch with a plain grep(). (Closes: #1060710) Checksums-Sha256: 2673484c7e8fb343bae95626000d4cbcd9163e02e198720f221edcc232da1fba 2080 dnsenum_1.3.1-1.1.dsc 1ee1263668f1b40f494a47a347ab04a8409e3e60a07e36e164195b08e5ffc2fe 5612 dnsenum_1.3.1-1.1.debian.tar.xz 37ebdbcc78fc9a46a3b7df989e04b2c1f67ca462942af108521479f862b9a4f8 6172 dnsenum_1.3.1-1.1_sourceonly.buildinfo Checksums-Sha1: a0139257cab1a07c018d983c56056815958e4719 2080 dnsenum_1.3.1-1.1.dsc e2a2fb11abf836f48284179c7aa82e9c9133e681 5612 dnsenum_1.3.1-1.1.debian.tar.xz b28310bddb6637f0e717eb6689eac3d3cf0abcb0 6172 dnsenum_1.3.1-1.1_sourceonly.buildinfo Files: d61cb6ba024e9a7706950b439cdd9bb9 2080 net optional dnsenum_1.3.1-1.1.dsc f738baa6ae6143d63c87f951fbbb37dd 5612 net optional dnsenum_1.3.1-1.1.debian.tar.xz bf96215c0fadea3fa170bc891864ef09 6172 - - dnsenum_1.3.1-1.1_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmWoHEFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZjvA//b79DkCO8PMnNw+ljvmku52Q2YX7tzVS3nKC73Nt/vtkThEdrEjk+jJ05 54ODBl2NvEQWdkqy2wVxJKvAtpkrH6c3azqwLHAt4PKvNQKSmQVmWc/bSdm5hD3c o4FciRcfAa1N4dI9Z03giWuNvSw42SN7rFPodS4uafkolMmCUFndSAv1qZ+07Cyh 7U87Dx2CsF1MIx5mOYENeUQHmV5tkftuwtKo3mL9BjMOpzyNdWSwtb6niwhNqS8z deBTlWoQtuEY8KLpZsuMPiXhIO4qSjt3fCxWBZ92a6rMyIBIKAT7ecvQ6/kMXJXT Xu48h8NTdeM02Qbbjh2h9JpkjAdC+Dyx0H3vkVOa2+BDpGZtBSAx12/kyVyd1We6 l+Nk00gDiBMfpKtP3xkI9fNq9PyGOQ+m0IUHj8cAUuYX0/1GTB7n8upDBkob71CC /rTrD5C84SV9dKh+sTm18pBaOlvbxVjRg76DG5wVsX4aEtUkRH8Nc4sfXNYKEg7D codyw5QaJ42+f+Ha1Na+tm16Ty37K+4zp3S6I5xTtZ5fKEnVBeORcobUMu0EuSo+ giHkhaxhIj5TW6YTsnZxMUSR0U2Bw02SioxPVga1xxRmSN/pXqxWGYSPx/0mEbAb z1upFX17fszDWzHBHJywW/t/R/tFqQlm0yP97t/kCx4E9bSsl7U= =/Dmk -END PGP SIGNATURE End Message ---
Processed: Bug#1060999 marked as pending in octave-sockets
Processing control commands: > tag -1 pending Bug #1060999 [src:octave-sockets] octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25 Added tag(s) pending. -- 1060999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060999: marked as pending in octave-sockets
Control: tag -1 pending Hello, Bug #1060999 in octave-sockets 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/pkg-octave-team/octave-sockets/-/commit/44fae34e9dbd1c278da7db507e5f8c50258c45f0 Build documentation using upstream Makefile + d/p/add-mkfuncdocs-py.patch: New patch + d/rules: Make doc/mkfuncdocs.py executable and build the documentation files (PDF, HTML, and INFO) from the sources + d/control: Build-depend on python3 Gbp-Dch: Full Closes: #1060999 (this message was generated automatically) -- Greetings https://bugs.debian.org/1060999
Bug#1060709: marked as done (dh-runit: autopkgtest failure with Perl 5.38: given is deprecated)
Your message dated Wed, 17 Jan 2024 18:34:13 + with message-id and subject line Bug#1060709: fixed in dh-runit 2.16.2 has caused the Debian Bug report #1060709, regarding dh-runit: autopkgtest failure with Perl 5.38: given is deprecated 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.) -- 1060709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dh-runit Version: 2.15.2 Severity: serious User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails its autopkgtest checks with Perl 5.38 (currently in unstable.) autopkgtest [21:33:45]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL stderr: given is deprecated at /usr/bin/dh_runit line 50. autopkgtest [21:33:45]: test command1: - - - - - - - - - - stderr - - - - - - - - - - Sorry for not catching this earlier. I only checked packages with Testsuite: autopkgtest-pkg-perl or Testsuite-Triggers: perl. I suppose I should have looked at Depends:perl too. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: dh-runit Source-Version: 2.16.2 Done: Lorenzo Puliti We believe that the bug you reported is fixed in the latest version of dh-runit, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lorenzo Puliti (supplier of updated dh-runit 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: Wed, 17 Jan 2024 19:16:08 CET Source: dh-runit Binary: Architecture: source Version: 2.16.2 Distribution: unstable Urgency: medium Maintainer: Lorenzo Puliti Changed-By: Lorenzo Puliti Description: Closes: 1060709 Changes: dh-runit (2.16.2) unstable; urgency=medium . * dh_runit: stop using given/when. + Thanks: gregor herrmann (Closes: #1060709) * minor update to dh_runit manpage * update copyright years Checksums-Sha256: 91223002eef4aab4600758256c37156a2b6ebd1a64191d0cb90b1cc37d7ea76a 1916 dh-runit_2.16.2.dsc a5590ae23455cd65708954422b5d0c5f51d694b7f08b278c1325b971f1e96d9d 17408 dh-runit_2.16.2.tar.xz 30b56f59810cbdd90dcc250910d8afc701e1ddb265590bca56a056217979a1f1 7550 dh-runit_2.16.2_sourceonly.buildinfo Checksums-Sha1: 212f1dead2498c199d1f058756314d043ce2d979 1916 dh-runit_2.16.2.dsc bdb4eb771697b8a5b9c6c9de5c1bfeb682574241 17408 dh-runit_2.16.2.tar.xz e88b596c23c579e1a5c57dd4236e0d71ffaf74b7 7550 dh-runit_2.16.2_sourceonly.buildinfo Files: 1982b1a2b55fbb6439df57455e3400b4 1916 admin optional dh-runit_2.16.2.dsc 078516e77a3ff919fafeb7f67ceead6e 17408 admin optional dh-runit_2.16.2.tar.xz e96fdea2ca79cddce1a1715692795d00 7550 - - dh-runit_2.16.2_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmWoGWhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgY1vA/7Bymjmz5QgDGKBWdxkegZCgE3oaMF/jNtuyUe/naOzv5h23ktVEjvukFb 7/5KiAL1r/Wl9rdykuu11ZQAkAaL1aETZRp3xIan4uxjbK6xnCXFGfBPhvsaeRdx pXbSJTge27/O/SCxMvJRFShPIm1LwCMdzhtWDGeVk07GiOm5sEKUQ8hjZgoONDhs LtG2/OVr0tYbEKTTdGLGHzGQlgMZXrk6/Q56nWg/reTAi317eUaDsFS5hbIuO4M6 uAQ2mZMHK0Qm98y2YXq1EnSRSQn9A+PJTyBzDX+9oubLu6f4KlkwFfgeNxgXxgz2 CVnNK4e/iD9dz+vvMT0Z4b0sHybdkh61dxToJ3KUgxlx+oIISbAnVQ0+NMMG3986 Bhe0L2+pLtegm6bMv9zgNMrfPG/N3eD7LYWko0tKhbBhAaKVUDZRygGEd3j1XfBF P457mdsEDXcEuIlqHtOPn2zP/PLLfCeIImgDQtfyMv57gUT/Lai1jTr6WFK7rOe6 EKm9FZaDITbKHv+oJz9o8ibOrlvgK8GjzNvXVUBTfdxYgKtl8Vo+4XZHemWsbIA9 xIEDr9gGbAMCFa526a3Uh/tTmhVDG3WO7iB/bfE+YysTE0EZPl7OO7MQqQ0p6RrF xQAAeR6yZ5T0Zgb8BNfkU5piau/Y26RfwFSGT4QMv24LNqbXk1w= =iCnw -END PGP SIGNATURE End Message ---
Bug#1060710: dnsenum: diff for NMU version 1.3.1-1.1
Dear maintainer,
I've prepared an NMU for dnsenum (versioned as 1.3.1-1.1). The diff
is attached to this message.
Sorry for the rush, this was one of the last blockers of the ongoing
perl 5.38 migration.
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru dnsenum-1.3.1/debian/changelog dnsenum-1.3.1/debian/changelog
--- dnsenum-1.3.1/debian/changelog 2022-10-25 19:05:15.0 +0200
+++ dnsenum-1.3.1/debian/changelog 2024-01-17 19:27:32.0 +0100
@@ -1,3 +1,13 @@
+dnsenum (1.3.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "autopkgtest failure with Perl 5.38: Smartmatch is deprecated":
+add patch perl5.38_smartmatch.patch, replacing smartmatch with a plain
+grep().
+(Closes: #1060710)
+
+ -- gregor herrmann Wed, 17 Jan 2024 19:27:32 +0100
+
dnsenum (1.3.1-1) unstable; urgency=medium
* New upstream version 1.3.1.
diff -Nru dnsenum-1.3.1/debian/patches/perl5.38_smartmatch.patch dnsenum-1.3.1/debian/patches/perl5.38_smartmatch.patch
--- dnsenum-1.3.1/debian/patches/perl5.38_smartmatch.patch 1970-01-01 01:00:00.0 +0100
+++ dnsenum-1.3.1/debian/patches/perl5.38_smartmatch.patch 2024-01-17 19:21:35.0 +0100
@@ -0,0 +1,32 @@
+Description: Stop using smartmatch
+ smartmatch is deprecated in perl 5.38, throwing warnings,
+ and will be removed in perl 5.42
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/1060710
+Author: gregor herrmann
+Last-Update: 2024-01-13
+
+--- a/dnsenum.pl
b/dnsenum.pl
+@@ -50,9 +50,6 @@
+ use strict;
+ use warnings
+ ; #it complains about uninitialized values when it doesn't find address in RR; need to fix later
+-no
+- if $] >= 5.018, 'warnings',
+- "experimental::smartmatch";# Mute Experimental Warning
+ use Config;
+ use Term::ANSIColor;
+ use Getopt::Long;
+@@ -746,9 +743,9 @@
+ ##we only print / add the result if it doesn't match the wildcardaddress
+ if (
+ !(
+-$rr->can('address') && $rr->address ~~ @wildcardaddress
++$rr->can('address') && grep { $_ eq $rr->address } @wildcardaddress
+ )
+-&& !( $rr->name ~~ @wildcardcname )
++&& !( grep { $_ eq $rr->name } @wildcardcname )
+ )
+ {
+ printrr( $rr->string );
diff -Nru dnsenum-1.3.1/debian/patches/series dnsenum-1.3.1/debian/patches/series
--- dnsenum-1.3.1/debian/patches/series 2022-10-25 19:05:15.0 +0200
+++ dnsenum-1.3.1/debian/patches/series 2024-01-17 19:21:35.0 +0100
@@ -1 +1,2 @@
010_fix-usage-output.patch
+perl5.38_smartmatch.patch
signature.asc
Description: Digital Signature
Bug#1060276: marked as done (pygalmesh: autopkgtest regression in testing)
Your message dated Wed, 17 Jan 2024 18:22:17 +
with message-id
and subject line Bug#1060276: fixed in pygalmesh 0.10.6-2
has caused the Debian Bug report #1060276,
regarding pygalmesh: autopkgtest regression in testing
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.)
--
1060276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygalmesh
Version: 0.10.6-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime between 2023-11-08 and 2023-12-06, pygalmesh's autopkgtests
started to fail in testing [1][2]. I've copied what I hope is the
relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/p/pygalmesh/testing/amd64/
[2] https://ci.debian.net/packages/p/pygalmesh/testing/armhf/
98s === FAILURES
===
98s ___ test_inr
___
98s
98s def test_inr():
98s this_dir = pathlib.Path(__file__).resolve().parent
98s # mesh = pygalmesh.generate_from_inr(
98s # this_dir / "meshes" / "skull_2.9.inr",
max_cell_circumradius=5.0, verbose=False
98s # )
98s with tempfile.TemporaryDirectory() as tmp:
98s out_filename = str(pathlib.Path(tmp) / "out.vtk")
98s pygalmesh._cli.cli(
98s [
98s "from-inr",
98s str(this_dir / "meshes" / "sphere.inr"),
98s out_filename,
98s "--max-cell-circumradius",
98s "1.0",
98s "--quiet",
98s ]
98s )
98s mesh = meshio.read(out_filename)
98s
98s vals_refs = [
98s (max(mesh.points[:, 0]), 9.00478554e00),
98s (min(mesh.points[:, 0]), -4.25843196e-03),
98s (max(mesh.points[:, 1]), 9.00332642e00),
98s (min(mesh.points[:, 1]), -4.41271299e-03),
98s (max(mesh.points[:, 2]), 9.00407982e00),
98s (min(mesh.points[:, 2]), -3.98639357e-03),
98s ]
98s for val, ref in vals_refs:
98s > assert abs(val - ref) < 1.0e-3 * (1.0 + abs(ref)), f"{val:.8e}
!= {ref:.8e}"
98s E AssertionError: -4.99461079e-03 != -3.98639357e-03
98s E assert 0.0010082172201632787 < (0.001 * (1.0 + 0.00398639357))
98s E + where 0.0010082172201632787 = abs((-0.004994611 - -0.00398639357))
98s E + and 0.00398639357 = abs(-0.00398639357)
98s
98s tests/test_inr.py:38: AssertionError
--- End Message ---
--- Begin Message ---
Source: pygalmesh
Source-Version: 0.10.6-2
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
pygalmesh, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated pygalmesh 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: Wed, 17 Jan 2024 12:44:41 +0100
Source: pygalmesh
Architecture: source
Version: 0.10.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 1060276
Changes:
pygalmesh (0.10.6-2) unstable; urgency=medium
.
* update debian patch test_relax_tolerance.patch to relax tolerance
in test_inr. Closes: #1060276.
* Standards-Version: 4.6.2
Checksums-Sha1:
82ab558072ac2596702790df2eb9e6a0e54274de 2237 pygalmesh_0.10.6-2.dsc
1ccc8f7ca44283254e382a6054bcc98eb95378c5 4896 pygalmesh_0.10.6-2.debian.tar.xz
Checksums-Sha256:
36e0867ed74a8e2e394d7a50133e7ffda8b38b6c392554c0257124a8fffba40c 2237
pygalmesh_0.10.6-2.dsc
b3645ea0c6447f151b8a26b3be262d79c16e835874c00dcbf41a179a9ae25304 4896
pygalmesh_0.10.6-2.debian.tar.xz
Files:
92b2f9287a793c6ed93cf6c610593e57 2237 python optional pygalmesh_0.10.6-2.dsc
777b06154328d3bacf9bb179257eb1b7 4896 python optional
pygalmesh_0.10.6-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmWoFjMACgkQVz7x5L1a
AfoG2hAAiFK6kGTuxk/0tqVUc920eXoIVWQpcPAUyH6PLSkd/0dUioRa5xUmH9R7
o0CmeqWW8FbYwWoqfqtpzERcJdYa/wIun8Q0wrD1tHnet6TJPOTDxRpk/xEOtSHd
JvKbn7n5YEBLquayl6t+g6l4BIWLswXK0sqA5TRw8DQYG75AVJp2Jm+A2aWviIUW
t2ZAUbIMMLyLSWcd4XGDFIIULfdSBnygnGicH6JY0BZ5zJVx+c6MgoBw4/dtZB6R
HmrC6nlRT4S89wBLysT1dmHI3G3Eiw3mbYJtMCdDyOpZdWl4cezT8jgeG1EyCBm9
Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build
On 2024-01-17 09:33, Matthias Klose wrote: > Package: src:h5py > Version: 3.10.0-1 > Severity: serious > Tags: sid trixie > > armhf: h5py's tests expose unaligned memory accesses during the build, this > not seen with with the 3.9.0 version. You don't see this on the Debian > buildds itself, because they ignore these misalignments. While it is something to fix for performance issues, I hardly see how it is a serious issue. It is not possible to deactivate alignment fixups on a armhf kernel. The Debian arm64 kernels (and not just the buildds) therefore have the COMPAT_ALIGNMENT_FIXUPS kernel option enabled to reproduce the same behaviour for 32-bit processes. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Processed: Bug#1061035 marked as pending in libconfig-model-dpkg-perl
Processing control commands: > tag -1 pending Bug #1061035 [src:libconfig-model-dpkg-perl] libconfig-model-dpkg-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255 Added tag(s) pending. -- 1061035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061035: marked as pending in libconfig-model-dpkg-perl
Control: tag -1 pending Hello, Bug #1061035 in libconfig-model-dpkg-perl 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/perl-team/modules/packages/libconfig-model-dpkg-perl/-/commit/9a1eac67854c15b47e70ddef065d204404dd39e3 fix grant/by-dir test The convertion from "-present" to current year is tested in Software::Copyright tests. There's no need to test this here. Closes: #1061035 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061035
Bug#1060983: marked as done (dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26))
Your message dated Wed, 17 Jan 2024 16:06:38 + with message-id and subject line Bug#1060983: fixed in dwarf2sources 0.2.4-1 has caused the Debian Bug report #1060983, regarding dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26) 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.) -- 1060983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dwarf2sources Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), dh-cargo, > librust-anyhow-1-dev, librust-fallible-iterator-0-dev, > librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), > librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, > librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), > librust-typed-arena-2-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), dh-cargo, > librust-anyhow-1-dev, librust-fallible-iterator-0-dev, > librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), > librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, > librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), > librust-typed-arena-2-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [916 B] > Get:5 copy:/<>/apt_archive ./ Packages [949 B] > Fetched 2474 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-gimli-0+indexmap-dev (>= > 0.26) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/01/15/dwarf2sources_0.2.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=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: dwarf2sources Source-Version: 0.2.4-1 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of dwarf2sources, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated dwarf2sources package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact
Bug#1061077: golang-github-gookit-color: FTBFS in ubuntu due to unknown TERM env
Package: golang-github-gookit-color Version: 1.5.4-2 Severity: serious Tags: ftbfs patch Justification: fails to build from source X-Debbugs-Cc: paul.m...@canonical.com Dear Maintainer, In ubuntu this package FTBFS because the TERM env var is set to unknown, thus preventing some tests from working properly. This is fixed by setting TERM to a "valid" value. Here is a patch: diff -Nru golang-github-gookit-color-1.5.4/debian/rules golang-github-gookit-color-1.5.4/debian/rules --- golang-github-gookit-color-1.5.4/debian/rules 2023-10-23 19:08:31.0 +0200 +++ golang-github-gookit-color-1.5.4/debian/rules 2024-01-17 15:54:30.0 +0100 @@ -3,5 +3,7 @@ export DH_GOLANG_EXCLUDES := _examples/ export DH_GOLANG_INSTALL_EXTRA := README.md +export TERM=xterm-256color + %: dh $@ --builddirectory=_build --buildsystem=golang --with=golang -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-14-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1061076: kbtin: FTBFS with stack-clash-protection on armhf due to valgrind segfault
Source: kbtin Version: 2.1-2 Severity: serious Tags: patch User: debian-...@lists.debian.org Usertags: 32bit-stackclash Hi, kbtin currently fails to build from source on armhf. The failure is due to an incompatibility between valgrind and stack-clash-protection on 32bit arm reported upstream at: https://bugs.kde.org/show_bug.cgi?id=479699 While waiting for valgrind to get updated, please cosider addressing the immediate issue by disabling stack-clash-protection on armhf with the following snippet in d/rules: ifeq ($(DEB_TARGET_ARCH),armhf) export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash else export DEB_BUILD_MAINT_OPTIONS = hardening=+all endif You can find the full build logs at: http://qa-logs.debian.net/2024/01/11/armhf/kbtin_2.1-2_unstable-armhf.log The error is: 3: ==1751922== 3: ==1751922== Process terminating with default action of signal 11 (SIGSEGV) 3: ==1751922== Access not within mapped region at address 0xFEC93DC8 3: ==1751922==at 0x118336: read_rc_file.isra.0 (main.c:301) 3: ==1751922==by 0x10F025: read_rc (main.c:319) 3: ==1751922==by 0x10F025: main (main.c:374) 3: ==1751922== If you believe this happened as a result of a stack 3: ==1751922== overflow in your program's main thread (unlikely but 3: ==1751922== possible), you can try to increase the size of the 3: ==1751922== main thread stack using the --main-stacksize= flag. 3: ==1751922== The main thread stack size used in this run was 8388608. 3: --- "/<>/tests/data/#chr, #ord, #hexord (7-bit ASCII).out" 2022-11-06 21:51:48.0 + Thanks, Emanuele
Bug#1000068: libapache2-mod-auth-cas: depends on obsolete pcre3 library
Hi, > Your package still depends on the old, obsolete PCRE3[0] libraries > (i.e. libpcre3-dev). Thanks for the report. Indeed there's work ongoing upstream to fix this. I'm monitoring this and we hope to get a working version well in time for trixie. Kind regards, Thijs
Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: Bug#1060658: megapixels don't start could not find any config file
Hi, On Wed, Jan 17, 2024 at 02:17:53PM +0530, Pirate Praveen wrote: > > > On 16/01/24 10:01 pm, Arnaud Ferraris wrote: > > Hi, > > > > Le 12/01/2024 à 10:37, Pirate Praveen a écrit : > > > Package: megapixels > > > Version: 1.7.0-1 > > > Severity: grave > > > > > > Running megapixels from commandline on mobian trixie fails with this error > > > > > > /usr/share/megapixels/config/purism,librem5r4.ini not found. > > > > This is expected, megapixels doesn't support the L5 (yet?). > > I was looking at a blog post for QR code readers and mega pixel was > mentioned > > https://forums.puri.sm/t/qr-code-scanning-via-megapixels/14408 > > Found another reference now https://blog.brixit.nl/megapixels-2-0/ > > but seems this never finished. On the L5 you can use millipixels (which is a fork of megapixels) for QR code scanning. I've filed #1060921 to track L5 support in megapixels. Cheers, -- Guido > > ___ > Debian-on-mobile-maintainers mailing list > debian-on-mobile-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers
Bug#1061067: marked as done (qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict)
Your message dated Wed, 17 Jan 2024 14:50:11 + with message-id and subject line Bug#1061067: fixed in qt6-scxml 6.6.1-2 has caused the Debian Bug report #1061067, regarding qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict 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.) -- 1061067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qml6-module-qtscxml,qml6-module-qtqml-statemachine Version: 6.6.1-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libqt6scxmlqml6 libqt6statemachineqml6 qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libQt6StateMachineQml.so.6 is contained in the packages * libqt6statemachineqml6 * 6.4.2-2 as present in bookworm * 6.4.2-2~bpo11+1 as present in bullseye-backports * 6.4.2-4 as present in trixie|unstable * qml6-module-qtqml-statemachine/6.6.1-1 as present in experimental The file /usr/lib/x86_64-linux-gnu/libQt6ScxmlQml.so.6 is contained in the packages * libqt6scxmlqml6 * 6.4.2-2 as present in bookworm * 6.4.2-2~bpo11+1 as present in bullseye-backports * 6.4.2-4 as present in trixie|unstable * qml6-module-qtscxml/6.6.1-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: qt6-scxml Source-Version: 6.6.1-2 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of qt6-scxml, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated qt6-scxml 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: Wed, 17 Jan 2024 15:36:56 +0100 Source: qt6-scxml Architecture: source Version: 6.6.1-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1061067 Changes: qt6-scxml (6.6.1-2) experimental; urgency=medium . [ Patrick Franz ] * Add missing Breaks+Replaces for libqt6scxmlqml6 and libqt6statemachineqml6 (Closes: #1061067). Checksums-Sha1: 0c9899368ae685cc2f7111eff91722345f20f213 3003 qt6-scxml_6.6.1-2.dsc 9aeef98c0143c1777ee304e5dd2d314f13c75fcf 14504 qt6-scxml_6.6.1-2.debian.tar.xz f8f98e3d469cabe69405f929dd23989282898613 13232 qt6-scxml_6.6.1-2_source.buildinfo Checksums-Sha256: c1af5a879ac87d091225078f70858807432ce9d239723601fa3e60c808d91cdb 3003 qt6-scxml_6.6.1-2.dsc e27dc9c7f86c365dc29984ff694dbc62c8124160661190b75e48fefc26cc0c9a 14504 qt6-scxml_6.6.1-2.debian.tar.xz 86ca472f07f185df94fd95dd08c7ab893d0d833c13543a64f62e8b1e1dc0073b 13232 qt6-scxml_6.6.1-2_source.buildinfo Files: 51b07ad7650c7b7514a12697f144dc8b 3003 libs optional qt6-scxml_6.6.1-2.dsc 08725d51d85b6440da2c7caa44d48224 14504 libs optional qt6-scxml_6.6.1-2.debian.tar.xz f5017f7ca7c9565857c85ed49004d931 13232 libs optional qt6-scxml_6.6.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmWn5p0ACgkQnp96YDB3 /lY2iw//f1wNgtsO5Zk6FfMVgr0DiCOi03hHC4Y1G8AA9TNCoposgiJ7SkyTTAsg IzKf1RGecDAY2gIRNpyc1kFGVAIF0302XZR+OgEtxHzwvpNNF4eoLjLa4U2GESP2 pC4ziYQQGZQ/i5fF01IrivOFiPGPwNsZ1VDayEVR4tvz+IuoOqPEZg8ClNQ12uSH Er/zlCYZb3vyC765yAVnONmlrCnKmsedO6UY6bpOFYNc3y6/BZL7JUOaNlJjh2bE aqmaAlETiOCRKGgmieYkMMqfTJJazRgipLY7f3ch+1i3wQSeFWV+jXGeuKS3HclN 9Idb/C1qr+kadDityg8tepVqN8uj3POlNaVhl7x+Z7RalfmkbRcyYOvnTEE+zQNT
Bug#1058937: Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts
On Fri, Jan 12, 2024 at 01:31:18PM +0100, Helmut Grohne wrote: > The relevant situation is not entirely trivial to construct: > > * Package $first contains an aliased file $file and this is moved to >package $second in an update. >OR >Package $first diverts aliased location $file normally owned by >package $second. > > * An update to package $second moves $file to its physical location >below /usr. > > * Package $second declares a versioned conflict for package $first with >any version that contains or diverts the aliased $file. > > Then we can construct a file loss scenario: > > * Install package $first. > * Schedule $first for removal: >echo "$first remove" | dpkg --set-selections > * Install the updated $second: >dpkg --unpack $second.deb I somehow missed how Ben's libnfsidmap bug #1058937 works slightly simpler. Given that $second has a conflict with the installed version of $first, one can skip that second step and instead install $second directly with dpkg -i. So no, this weird selections stuff is not technically necessary. In general, when doing these dances there are two outcomes. Either, $first is unpacked (or removed) before $second is unpacked or the other way round. The latter case always shows a message like this: dpkg: considering removing $first in favour of $second ... dpkg: yes, will remove $first in favour of $second It is these cases that exhibit the buggy behaviour. > In most upgrade scenarios, apt will remove/upgrade package $first before > performing the unpack of $second. In these cases, no loss happens. I tried to get an idea of what "most" means precisely. For one thing, I constructed various bullseye->bookworm and bookworm->unstable upgrades followed by dpkg --verify. This included large installations such as task-gnome-desktop with recommends and targeted cases where I hoped to find problems such as upgrading molly-guard or nfs-ganesha or and a few more. In none of the cases (where doing plain apt-get dist-upgrade), I was able to make dpkg --verify unhappy. Another route was searching for existing evidence. piuparts has lots of logs of upgrading packages and in >= bookworm, I found exactly one having that "yes, will remove" content. It was https://piuparts.debian.org/testing2sid/pass/rubber_1.6.0-2.log and that's due to texlive-base declaring a versioned Conflict with texlive-latex-base and texlive-latex-base declaring versioned Breaks with texlive-base. This is the mutual Conflicts case that also broke stuff in a draft patch for molly-guard. This data point confirms what David Kalnischkies said about this earlier: In the absence of mutual conflicts, apt removes $first before unpacking $second. I also tried a web search for "yes, will remove" and really most of logs I found, dpkg was used directly (though without --set-selections). That texlive mutual conflict was an exception. Evidently, this is rarely happening on real installations. > Therefore, I hope that the loss cannot be experienced when upgrading > with apt or frontends using apt such as aptitude, but there is no proof > of this. So all the evidence I found confirms the guess that the problem cannot be observed with apt unless mutual conflicts exist. On the flip side, simply installing a package that declares Conflicts occasionally triggers this and if you happen to do this to a package that replaces aliased files, then your files vanish. In particular, this raises the question whether we consider the upgrade that Ben describes in #1058937 as supported or whether we can close the bug. In effect, that's the question to ask here. I note that netplan.io/0.107.1-2/#1060661 just opted for not doing Conflicts and instead employed protective diversions (M8). In principle, we could generally prefer M8 (for P1, but not for P7) and thereby reduce the problem at the cost of making the mitigation more complex. At least for the essential set, there is not much choice as employing Conflicts is known to lead to bad things. > One takeaway from the CTTE meeting was that this loss should be > mitigated when it may make a system unbootable. That is a property that > is difficult to capture and would likely require mitigating half of the > conflicts. While this may seem like an obvious rule-of-thumb, it very much is not. For many of the packages, one can plausibly construct crazy boot schemes involving them. Though cryptsetup quite clearly falls within scope. > The way of mitigation also is non-trivial. In the window between unpack > of files that will be lost and actual loss, no maintainer script is run > reliably. Hence, copies of affected files have to be installed > elsewhere: > * systemd-sysv looses only symlinks whose target is specified in >postinst. > * gzip looses shell scripts that will be embedded in its postinst. > * For larger files such as dhclient, we consider moving the file to an >unaffected location and then pointing a symlink at it such that
Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type
On Wednesday, January 17, 2024 9:03:29 AM EST Richard Rosner wrote: > I've updated all mariadb packages to 10.11.6 and all postfix packages. > Everything still working. > Excellent news. Thanks for testing. Scott K signature.asc Description: This is a digitally signed message part.
Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type
I've updated all mariadb packages to 10.11.6 and all postfix packages. Everything still working. Am Mittwoch, 17. Januar 2024 00:34 CET, schrieb Scott Kitterman : They accepted mariadb 10.11.6 as a proposed update and I rebuilt postfix again. Updated packages (and the first ones also, note the slightly different revision number) at the same location: https://kitterman.com/debian/ I'm not sure if you'll need to upgrade your mariadb packages. If so, they can currently be found in incoming: http://incoming.debian.org/debian-buildd/pool/main/m/mariadb/ After the next dinstall they will be available in the bookworm-proposed updates repository. For incoming, you'll need to wget the binaries and use dpkg to install them. For bookworm-proposed-updates, you can use apt with an appropriate entry in your sources.list. Please test and let me know how it goes: Thanks, Scott K On Tuesday, January 16, 2024 3:39:43 PM EST Richard Rosner wrote: > Good to know. Thanks. > > > Am Dienstag, 16. Januar 2024 21:00 CET, schrieb Scott Kitterman > : So, the magic needed to build the new update > exceeds my grasp, but it's debian/changelog discusses fixing regressions. > On that basis, I think the thing to do is reassign the bug to mariadb and > mark it as affecting postfix. I'll also bring it to the stable release > manager's attention. > > Scott K > > On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote: > > Excellent. On that basis, I think blaming mariadb for the regression is > > appropriate. I see there's another mariadb update pending. If would up for > > another test, I'd like to see if that update solves the problem. I'll > > build another set of packages against that and if that works, then we just > > need to make sure we get that update accepted and rebuild postfix. > > > > Scott K smime.p7s Description: S/MIME cryptographic signature
Processed: Bug#1058097 marked as pending in python-openstackclient
Processing control commands: > tag -1 pending Bug #1058097 [src:python-openstackclient] python-openstackclient: FTBFS: AttributeError: module 'sys' has no attribute 'builtin_module_names' Added tag(s) pending. -- 1058097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058097: marked as pending in python-openstackclient
Control: tag -1 pending Hello, Bug #1058097 in python-openstackclient 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/openstack-team/clients/python-openstackclient/-/commit/88f9b4d6b973e611289eb55e303384bccbb86cdc Blacklist tests.unit.common.test_module.TestModuleList (Closes: #1058097). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058097
Bug#1060943: marked as done (mricron: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory)
Your message dated Wed, 17 Jan 2024 13:34:30 + with message-id and subject line Bug#1060943: fixed in mricron 1.2.20211006+dfsg-5 has caused the Debian Bug report #1060943, regarding mricron: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory 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.) -- 1060943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mricron Version: 1.2.20211006+dfsg-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # first the non-gui parts > cp common/notgui.inc common/isgui.inc > # and now the gui parts > cp common/gui.inc common/isgui.inc > lazbuild --build-all --ws=qt5 --pcp=/etc/lazarus mricron.lpi > InitializeFppkg failed: Unable to create file > "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $557F6D9BFB7A > $557F6D9BAB65 > $557F6D916F2E > $557F6DF68713 > $557F6DACAC83 > $557F6DAB51DE > $557F6DAB50D8 > $557F6D91B13D > $557F6D918D64 > $557F6D9173EB > $557F6D91CC93 > $557F6D91F979 > $557F6D94175C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/mricron_1.2.20211006+dfsg-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=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: mricron Source-Version: 1.2.20211006+dfsg-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mricron, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mricron 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: Wed, 17 Jan 2024 14:07:57 +0100 Source: mricron Architecture: source Version: 1.2.20211006+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1046546 1060943 Changes: mricron (1.2.20211006+dfsg-5) unstable; urgency=medium . * Team upload. * Build-Depends: lazarus-src-3.0 * Fix build Closes: #1060943 * Fix clean target Closes: #1046546 Checksums-Sha1: c05c64ca9ec33d4346b7cca6e612ba1d00937705 2355 mricron_1.2.20211006+dfsg-5.dsc 1fe302b10d094e98295e2087009b89df87a5441c 7604 mricron_1.2.20211006+dfsg-5.debian.tar.xz 4981736f6b7ee73fd2532c8328b8b4a0b90f07cc 15251 mricron_1.2.20211006+dfsg-5_amd64.buildinfo Checksums-Sha256: 3efc0374c5d07f6d9566035d6e7fa815dd3bb95cda0528b9b626507f1e911599 2355 mricron_1.2.20211006+dfsg-5.dsc 3fd50cff6dee06f7b66aea0149b25643cab8ef10968b65f0bf2aacacb2b8f588 7604 mricron_1.2.20211006+dfsg-5.debian.tar.xz 16727de254b69f36388c12de97310344c32ee3f9223d67940c81e70d20372943 15251
Bug#1060101: Boost 1.81 removal
On 14 January 2024 at 06:49, Dirk Eddelbuettel wrote: | | FYI two days before you filed #1060101 I actually happened to have updated | r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version | released in December as Boost releases every four months) using 1.83: | |r-cran-bh (1.84.0-1) unstable; urgency=medium | | * debian/control: Update Depends back to libboost-dev which will ensure |use of Boost 1.83 matching the just-updated BH package at CRAN which |is now at Boost 1.84 (released in December) which should be close |enough for our needs; a versioned name is no longer needed as the |default is now 1.83.0-2+b2 | | * debian/control: Set Build-Depends: to current R version | * debian/control: Switch to virtual debhelper-compat (= 13) | | -- Dirk Eddelbuettel Wed, 10 Jan 2024 07:20:09 -0600 | | So this should sort itself out by itself in a matter of days. r-cran-bh is | healthy: | |https://tracker.debian.org/pkg/r-cran-bh And it did, as expected. So no issues from r-cran-bh. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1056420: marked as done (logbook's autopkg tests fail with Python 3.12)
Your message dated Wed, 17 Jan 2024 13:59:10 +0100
with message-id
and subject line last upload does build
has caused the Debian Bug report #1056420,
regarding logbook's autopkg tests fail with Python 3.12
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.)
--
1056420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:logbook
Version: 1.5.3-5.2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
logbook's autopkg tests fail with Python 3.12:
[...]
332s === FAILURES
===
332s __ test_warning_redirections
___
332s
332s def test_warning_redirections():
332s from logbook.compat import redirected_warnings
332s with logbook.TestHandler() as handler:
332s redirector = redirected_warnings()
332s redirector.start()
332s try:
332s from warnings import warn, resetwarnings
332s resetwarnings()
332s warn(RuntimeWarning('Testing' +
str(next(test_warning_redirections_i
332s finally:
332s redirector.end()
332s
332s > assert len(handler.records) == 1
332s E assert 2 == 1
332s E+ where 2 = len([0x7f8f80d180b0>, ])
332s E+where [0x7f8f80d180b0>, ] =
.records
332s
332s tests/test_logging_compat.py:86: AssertionError
332s _ test_mail_handler_arguments
__
332s
332s def test_mail_handler_arguments():
332s with patch('smtplib.SMTP', autospec=True) as mock_smtp:
332s
332s # Test the mail handler with supported arguments before
changes to
332s # secure, credentials, and starttls
332s mail_handler = logbook.MailHandler(
332s from_addr='f...@example.com',
332s recipients='t...@example.com',
332s server_addr=('server.example.com', 465),
332s credentials=('username', 'password'),
332s secure=('keyfile', 'certfile'))
332s
332s > mail_handler.get_connection()
332s
332s tests/test_mail_handler.py:126:
332s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
332s /usr/lib/python3/dist-packages/logbook/handlers.py:1380: in
get_connection
332s con.starttls(keyfile=keyfile, certfile=certfile)
332s /usr/lib/python3.12/unittest/mock.py:1132: in __call__
332s self._mock_check_sig(*args, **kwargs)
332s /usr/lib/python3.12/unittest/mock.py:131: in checksig
332s sig.bind(*args, **kwargs)
332s /usr/lib/python3.12/inspect.py:3259: in bind
332s return self._bind(args, kwargs)
332s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
332s
332s self = , args = ()
332s kwargs = {'certfile': 'certfile', 'keyfile': 'keyfile'}
332s
332s def _bind(self, args, kwargs, *, partial=False):
332s """Private method. Don't use directly."""
332s
332s arguments = {}
332s
332s parameters = iter(self.parameters.values())
332s parameters_ex = ()
332s arg_vals = iter(args)
332s
332s while True:
332s # Let's iterate through the positional arguments and
corresponding
332s # parameters
332s try:
332s arg_val = next(arg_vals)
332s except StopIteration:
332s # No more positional arguments
332s try:
332s param = next(parameters)
332s except StopIteration:
332s # No more parameters. That's it. Just need to
check that
332s # we have no `kwargs` after this while loop
332s break
332s else:
332s if param.kind == _VAR_POSITIONAL:
332s # That's OK, just empty *args. Let's start
parsing
332s # kwargs
332s break
332s elif param.name in kwargs:
332s if param.kind == _POSITIONAL_ONLY:
332s msg = '{arg!r} parameter is positional
only, ' \
332s 'but was passed as a keyword'
332s msg = msg.format(arg=param.name)
332s raise TypeError(msg) from None
332s parameters_ex = (param,)
332s
Bug#1056814: marked as done (logbook: ftbfs with cython 3.0.x)
Your message dated Wed, 17 Jan 2024 13:59:10 +0100 with message-id and subject line last upload does build has caused the Debian Bug report #1056814, regarding logbook: ftbfs with cython 3.0.x 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.) -- 1056814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:logbook Version: 1.5.3-5.2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Version: 1.7.0-1.0 last upload does build with Python 3.12--- End Message ---
Bug#1055691: marked as done (logbook ftbfs with Python 3.12)
Your message dated Wed, 17 Jan 2024 13:59:10 +0100 with message-id and subject line last upload does build has caused the Debian Bug report #1055691, regarding logbook ftbfs with Python 3.12 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.) -- 1055691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:logbook Version: 1.5.3-5.2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 logbook ftbfs with Python 3.12. Not that cython was also upgraded to 3.0.5. [...] debian/rules execute_before_dh_auto_build make[1]: Entering directory '/<>' make cybuild make[2]: Entering directory '/<>' cython3 logbook/_speedups.pyx Error compiling Cython file: ... return getattr(obj.group, self.name) def __set__(self, obj, value): setattr(obj, self._name, value) def __del__(self, obj): ^ logbook/_speedups.pyx:54:4: Special method __del__ has wrong number of arguments (2 declared, 1 expected) make[2]: *** [Makefile:31: logbook/_speedups.so] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:15: execute_before_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Version: 1.7.0-1.0 last upload does build with Python 3.12--- End Message ---
Processed: Re: Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134
Processing control commands: > block -1 by 1061049 Bug #1061018 [src:octave-splines] octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134 1061018 was not blocked by any bugs. 1061018 was not blocking any bugs. Added blocking bug(s) of 1061018: 1061049 -- 1061018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134
Control: block -1 by 1061049 Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > Source: octave-splines > Version: 1.3.5-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > debian/rules binary > > dh binary --buildsystem=octave > >dh_update_autotools_config -O--buildsystem=octave > >dh_autoreconf -O--buildsystem=octave > >dh_octave_version -O--buildsystem=octave > > Checking the Octave version... ok > >dh_auto_configure -O--buildsystem=octave > >dh_auto_build -O--buildsystem=octave > >dh_auto_test -O--buildsystem=octave > >create-stamp debian/debhelper-build-stamp > >dh_testroot -O--buildsystem=octave > >dh_prep -O--buildsystem=octave > >dh_auto_install --destdir=debian/octave-splines/ -O--buildsystem=octave > > octave --no-gui --no-history --silent --no-init-file --no-window-system > > /usr/share/dh-octave/install-pkg.m > > /<>/debian/octave-splines/usr/share/octave/packages > > /<>/debian/octave-splines/usr/lib/x86_64-linux-gnu/octave/packages > > For information about changes from previous versions of the splines > > package, run 'news splines'. > >dh_octave_check -O--buildsystem=octave > > Checking package... > > Run the unit tests... > > Checking m files ... > > [inst/tps_val_der.m] > > > > > > > /<>/inst/tps_val_der.m > > * shared a,b,x,y,x1,x2,y1,c,dy,dy0 > > a = 2; b = -3; x = ([1:2:10 10.5 11.3])'; y = a*x; > > c = tpaps(x,y,1); > > * assert (a*ones(size(x)), tps_val_der(x,c,x), 1E3*eps); > > [x1 x2] = meshgrid(x, x); > > y1 = a*x1+b*x2; > > c = tpaps([x1(:) x2(:)],y1(:),0.5); > > dy = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)]); > > dy0 = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)],false); > > * assert (a*ones(size(x1(:))), dy(:, 1), 1E3*eps); > > * assert (b*ones(size(x2(:))), dy(:, 2), 1E3*eps); > > * assert (dy0, dy, 1E3*eps); > > 4 tests, 4 passed, 0 known failure, 0 skipped > > [inst/bin_values.m] > > > > > > > /<>/inst/bin_values.m > > * shared x, y, x_bin, y_bin, w_bin, n_bin > > x = [1; 2; 2; 3; 4]; > > y = [0 0; 1 1; 2 1; 3 4; 5 NaN]; > > [x_bin y_bin w_bin n_bin] = bin_values(x, y); > > * assert (x_bin, [1; 7/3]); > > * assert (y_bin, [0 0; 2 2]); > > * assert (!any(isfinite(w_bin(1, :; > > * assert (w_bin(2, :), [3 1]); > > * assert (n_bin, [1; 3]); > > 5 tests, 5 passed, 0 known failure, 0 skipped > > [inst/csaps_sel.m] > > > > > > > /<>/inst/csaps_sel.m > > * shared x,y,ret,p,sigma2,unc_y > > x = [0:0.01:1]'; y = sin(x); > > [ret,p,sigma2,unc_y] = csaps_sel(x,y,x); > > malloc(): invalid size (unsorted) > > fatal: caught signal Aborted -- stopping myself... > > Aborted > > make: *** [debian/rules:5: binary] Error 134 Thanks. This is a consequence of the ABI break in libcholmod5. Tagging accordingly. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134
Processing control commands: > block -1 by 1061049 Bug #1061017 [src:octave-divand] octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 1061017 was not blocked by any bugs. 1061017 was not blocking any bugs. Added blocking bug(s) of 1061017: 1061049 -- 1061017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134
Control: block -1 by 1061049 Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > Source: octave-divand > Version: 1.1.2+dfsg-6 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > debian/rules binary > > dh binary --buildsystem=octave > >dh_update_autotools_config -O--buildsystem=octave > >dh_autoreconf -O--buildsystem=octave > >dh_octave_version -O--buildsystem=octave > > Checking the Octave version... ok > >dh_auto_configure -O--buildsystem=octave > >dh_auto_build -O--buildsystem=octave > >dh_auto_test -O--buildsystem=octave > >create-stamp debian/debhelper-build-stamp > >dh_testroot -O--buildsystem=octave > >dh_prep -O--buildsystem=octave > >dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave > > octave --no-gui --no-history --silent --no-init-file --no-window-system > > /usr/share/dh-octave/install-pkg.m > > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages > > > > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages > > For information about changes from previous versions of the divand package, > > run 'news divand'. > >dh_octave_check -O--buildsystem=octave > > Checking package... > > Run the unit tests... > > Checking m files ... > > [inst/statevector_init.m] > > > > > > > /<>/inst/statevector_init.m > > * test > > mask = rand(10,10) > .5; > > mask_u = rand(9,10) > .5; > > mask_v = rand(10,9) > .5; > > sv = statevector_init(mask,mask_u,mask_v); > > var = rand(10,10); > > var(mask==0) = 0; > > var_u = rand(9,10); > > var_u(mask_u==0) = 0; > > var(mask==0) = 0; > > var_v = rand(10,9); > > var_v(mask_v==0) = 0; > > [E] = statevector_pack(sv,var,var_u,var_v); > > [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E); > > assert(Ezeta2,var) > > assert(Eu2,var_u) > > assert(Ev2,var_v) > > 1 test, 1 passed, 0 known failure, 0 skipped > > Checking C++ files ... > > Run tests in debian/check.m > > [test_divand] > > run test_interp_1d: (max difference=2.77556e-16) [42m OK [0m > > run test_interp_2d: (max difference=2.22045e-16) [42m OK [0m > > run test_interp_regular: (max difference=2.22045e-16) [42m OK [0m > > run test_sparse_diff: (max difference=0) [42m OK [0m > > run test_1dvar: malloc(): invalid size (unsorted) > > fatal: caught signal Aborted -- stopping myself... > > Aborted > > make: *** [debian/rules:5: binary] Error 134 Thanks. This is a consequence of the ABI break in libcholmod5. Tagging accordingly. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 1060990 src:libwacom Bug #1060990 [src:wacomtablet] wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2 Bug reassigned from package 'src:wacomtablet' to 'src:libwacom'. No longer marked as found in versions wacomtablet/3.2.0-5. Ignoring request to alter fixed versions of bug #1060990 to the same values previously set > forcemerge 1060687 1060990 Bug #1060687 [src:libwacom] libwacom-dev: Needs Depends: libevdev-dev Bug #1060990 [src:libwacom] wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2 Added indication that 1060990 affects src:gnome-control-center,src:gnome-settings-daemon Marked as found in versions libwacom/2.9.0-1. Bug #1060687 [src:libwacom] libwacom-dev: Needs Depends: libevdev-dev Added tag(s) sid and trixie. Merged 1060687 1060990 > affects 1060687 libwacom-dev src:wacomtablet Bug #1060687 [src:libwacom] libwacom-dev: Needs Depends: libevdev-dev Bug #1060990 [src:libwacom] wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2 Added indication that 1060687 affects libwacom-dev and src:wacomtablet Added indication that 1060990 affects libwacom-dev and src:wacomtablet > thanks Stopping processing here. Please contact me if you need assistance. -- 1060687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 1060990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042681: marked as done (logbook: FTBFS with Sphinx 7.1, docutils 0.20: intersphinx inventory '/usr/share/doc/python2.7/html/objects.inv' not fetchable due to : [Errno 2
Your message dated Wed, 17 Jan 2024 11:34:00 +
with message-id
and subject line Bug#1042681: fixed in logbook 1.7.0-1.0
has caused the Debian Bug report #1042681,
regarding logbook: FTBFS with Sphinx 7.1, docutils 0.20: intersphinx inventory
'/usr/share/doc/python2.7/html/objects.inv' not fetchable due to : [Errno 2] No such file or directory:
'/usr/share/doc/python2.7/html/objects.inv'
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.)
--
1042681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logbook
Version: 1.5.3-5.2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
logbook fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v7.1.1
> making output directory... done
> loading intersphinx inventory from
> /usr/share/doc/python2.7/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python2.7/html/objects.inv' not
> fetchable due to : [Errno 2] No such file or
> directory: '/usr/share/doc/python2.7/html/objects.inv'
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 24 source files that are out of date
> updating environment: [new config] 24 added, 0 changed, 0 removed
> [2Kreading sources... [ 4%] api/base
> [2Kreading sources... [ 8%] api/compat
> [2Kreading sources... [ 12%] api/handlers
> [2Kreading sources... [ 17%] api/index
> [2Kreading sources... [ 21%] api/internal
> [2Kreading sources... [ 25%] api/more
> [2Kreading sources... [ 29%] api/notifiers
> [2Kreading sources... [ 33%] api/queues
> [2Kreading sources... [ 38%] api/ticketing
> [2Kreading sources... [ 42%] api/utilities
> [2Kreading sources... [ 46%] changelog
> [2Kreading sources... [ 50%] compat
> [2Kreading sources... [ 54%] cookbook
> [2Kreading sources... [ 58%] designdefense
> [2Kreading sources... [ 62%] designexplained
> [2Kreading sources... [ 67%] features
> [2Kreading sources... [ 71%] index
> [2Kreading sources... [ 75%] libraries
> [2Kreading sources... [ 79%] performance
> [2Kreading sources... [ 83%] quickstart
> [2Kreading sources... [ 88%] setups
> [2Kreading sources... [ 92%] stacks
> [2Kreading sources... [ 96%] ticketing
> [2Kreading sources... [100%] unittesting
>
> /<>/docs/api/handlers.rst:9: WARNING: duplicate object
> description of logbook, other instance in api/base, use :noindex: for one of
> them
> /<>/docs/api/utilities.rst:9: WARNING: duplicate object
> description of logbook, other instance in api/handlers, use :noindex: for one
> of them
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [ 4%] api/base
>
> Theme error:
> An error happened in rendering the page api/base.
> Reason: UndefinedError("'logo' is undefined")
> make[2]: *** [Makefile:40: html] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/logbook_1.5.3-5.2_unstable_sphinx-exp.log
Please see [1] for Sphinx changelog and [2] for Docutils changelog.
Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.
Some notable changes in Sphinx 6 and Sphinx 7:
- Sphinx no longer includes jquery.js and underscore.js by default.
Please use python3-sphinxcontrib.jquery package if you are using a custom
template and it still needs jquery.
- The setup.py build_sphinx command was removed. Please instead call
sphinx-build or "python3 -m sphinx" directly.
- For packages using the extlinks extension, the caption should contain
exactly one "%s" placeholder (if caption is not None).
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]:
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]:
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
Bug#1061067: qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict
Package: qml6-module-qtscxml,qml6-module-qtqml-statemachine Version: 6.6.1-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libqt6scxmlqml6 libqt6statemachineqml6 qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libQt6StateMachineQml.so.6 is contained in the packages * libqt6statemachineqml6 * 6.4.2-2 as present in bookworm * 6.4.2-2~bpo11+1 as present in bullseye-backports * 6.4.2-4 as present in trixie|unstable * qml6-module-qtqml-statemachine/6.6.1-1 as present in experimental The file /usr/lib/x86_64-linux-gnu/libQt6ScxmlQml.so.6 is contained in the packages * libqt6scxmlqml6 * 6.4.2-2 as present in bookworm * 6.4.2-2~bpo11+1 as present in bullseye-backports * 6.4.2-4 as present in trixie|unstable * qml6-module-qtscxml/6.6.1-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict
Processing control commands: > affects -1 + libqt6scxmlqml6 libqt6statemachineqml6 Bug #1061067 [qml6-module-qtscxml,qml6-module-qtqml-statemachine] qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict Added indication that 1061067 affects libqt6scxmlqml6 and libqt6statemachineqml6 -- 1061067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060775: marked as done (tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError)
Your message dated Wed, 17 Jan 2024 10:35:19 +
with message-id
and subject line Bug#1060775: fixed in tmuxp 1.34.0-2
has caused the Debian Bug report #1060775,
regarding tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError
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.)
--
1060775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tmuxp
Version: 1.31.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails. I'm seeing a pattern that it happens more often
on our amd64 host ci-worker13 and often on our s390x which are rather
powerful hosts. The test fails in different locations, but as far as I
saw always on a line that asserts capture_pane (see example below).
Could it be that the code (either the real code or the test code) should
wait a bit until the "pane" has been substantiated? Or maybe that
comment earlier is of interest: Give slow shells some time to settle as
otherwise tests might fail.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
From
https://ci.debian.net/packages/t/tmuxp/testing/s390x/41364351/
59s @pytest.mark.skipif(
59s has_lt_version("3.0"),
59s reason="needs -e flag for new-window and split-window
introduced in tmux 3.0",
59s )
59s def test_environment_variables(session: Session) -> None:
59s workspace = ConfigReader._from_file(
59s
test_utils.get_workspace_file("workspace/builder/environment_vars.yaml")
59s )
59s workspace = loader.expand(workspace)
59s
59s builder = WorkspaceBuilder(session_config=workspace,
server=session.server)
59s builder.build(session)
59s # Give slow shells some time to settle as otherwise tests
might fail.
59s time.sleep(0.3)
59s
59s assert session.getenv("FOO") == "SESSION"
59s assert session.getenv("PATH") == "/tmp"
59s
59s no_overrides_win = session.windows[0]
59s pane = no_overrides_win.panes[0]
59s pane.send_keys("echo $FOO")
59s assert pane.capture_pane()[1] == "SESSION"
59s
59s window_overrides_win = session.windows[1]
59s pane = window_overrides_win.panes[0]
59s pane.send_keys("echo $FOO")
59s assert pane.capture_pane()[1] == "WINDOW"
59s
59s pane_overrides_win = session.windows[2]
59s pane = pane_overrides_win.panes[0]
59s pane.send_keys("echo $FOO")
59s assert pane.capture_pane()[1] == "PANE"
59s
59s both_overrides_win = session.windows[3]
59s pane = both_overrides_win.panes[0]
59s pane.send_keys("echo $FOO")
59s > assert pane.capture_pane()[1] == "WINDOW"
59s E IndexError: list index out of range
59s
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tmuxp
Source-Version: 1.34.0-2
Done: Sebastien Delafond
We believe that the bug you reported is fixed in the latest version of
tmuxp, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastien Delafond (supplier of updated tmuxp 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: Wed, 17 Jan 2024 11:08:43 +0100
Source: tmuxp
Architecture: source
Version: 1.34.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond
Changed-By: Sebastien Delafond
Closes: 1060775
Changes:
tmuxp (1.34.0-2) unstable; urgency=medium
.
[ Sébastien Delafond ]
* test_environment_variables: raise timeout from 0.3s to 3s (Closes:
#1060775)
Checksums-Sha1:
Bug#1058226: marked as done (python-qmix: FTBFS: ImportError: Numba could not be imported.)
Your message dated Wed, 17 Jan 2024 10:19:25 +
with message-id
and subject line Bug#1058226: fixed in python-qmix 1.0.6-6
has caused the Debian Bug report #1058226,
regarding python-qmix: FTBFS: ImportError: Numba could not be imported.
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.)
--
1058226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-qmix
Version: 1.0.6-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py", line
> 4, in
> from numba.core.typeconv import _typeconv
> ImportError: cannot import name '_typeconv' from 'numba.core.typeconv'
> (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/<>/setup.py", line 11, in
> import qmix
> File "/<>/qmix/__init__.py", line 10, in
> import qmix.exp
> File "/<>/qmix/exp/__init__.py", line 4, in
> from qmix.exp.exp_data import (RawData, RawData0,
> File "/<>/qmix/exp/exp_data.py", line 41, in
> from qmix.harmonic_balance import harmonic_balance
> File "/<>/qmix/harmonic_balance.py", line 23, in
> from qmix.qtcurrent import interpolate_respfn, qtcurrent
> File "/<>/qmix/qtcurrent.py", line 24, in
> import numba as nb
> File "/usr/lib/python3/dist-packages/numba/__init__.py", line 73, in
>
> from numba.misc.special import (
> File "/usr/lib/python3/dist-packages/numba/misc/special.py", line 3, in
>
> from numba.core.typing.typeof import typeof
> File "/usr/lib/python3/dist-packages/numba/core/typing/__init__.py", line
> 1, in
> from .context import BaseContext, Context
> File "/usr/lib/python3/dist-packages/numba/core/typing/context.py", line
> 11, in
> from numba.core.typeconv import Conversion, rules
> File "/usr/lib/python3/dist-packages/numba/core/typeconv/rules.py", line 2,
> in
> from .typeconv import TypeManager, TypeCastingRules
> File "/usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py", line
> 16, in
> raise ImportError(msg)
> ImportError: Numba could not be imported.
>
> If you are seeing this message and are undertaking Numba development work,
> you may need to rebuild Numba.
> Please see the development set up guide:
>
> https://numba.readthedocs.io/en/stable/developer/contributing.html.
>
>
> If you are not working on Numba development, the original error was: 'cannot
> import name '_typeconv' from 'numba.core.typeconv'
> (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'.
> For help, please visit:
>
> https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported
>
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-qmix_1.0.6-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=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: python-qmix
Source-Version: 1.0.6-6
Done: Yogeswaran Umasankar
We believe that the bug you reported is fixed in
Processed: tagging 1054813
Processing commands for cont...@bugs.debian.org: > tags 1054813 + pending Bug #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 Ignoring request to alter tags of bug #1054813 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1054813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1054813 marked as pending in python-dmidecode
Processing control commands: > tag -1 pending Bug #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 Added tag(s) pending. -- 1054813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054813: marked as pending in python-dmidecode
Control: tag -1 pending Hello, Bug #1054813 in python-dmidecode 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/python-team/packages/python-dmidecode/-/commit/ef19e12e5c2db3c280dd08d17bf96ef4c8b7810e fix FTBFS (Closes: #1054813) (this message was generated automatically) -- Greetings https://bugs.debian.org/1054813
Bug#1061064: tomopy: FTBFS with two supported python versions
Source: tomopy Version: 1.14.1+ds1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, tomopy FTBFS if there are two supported python versions because the target wildcard expands to more than one directory: debian/rules execute_before_dh_auto_test make[1]: Entering directory '/build/tomopy-1.14.1+ds1' cp debian/python3-tomopy//usr/lib/python3/dist-packages/tomopy/util/extern/*.so /build/tomopy-1.14.1+ds1/.pybuild/cpython*/build/tomopy/util/extern cp: -r not specified; omitting directory '/build/tomopy-1.14.1+ds1/.pybuild/cpython3_3.11_tomopy/build/tomopy/util/extern' make[1]: *** [debian/rules:44: execute_before_dh_auto_test] Error 1 Andreas tomopy_1.14.1+ds1-1.log.gz Description: application/gzip
Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: megapixels don't start could not find any config file
On 16/01/24 10:01 pm, Arnaud Ferraris wrote: Hi, Le 12/01/2024 à 10:37, Pirate Praveen a écrit : Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found. This is expected, megapixels doesn't support the L5 (yet?). I was looking at a blog post for QR code readers and mega pixel was mentioned https://forums.puri.sm/t/qr-code-scanning-via-megapixels/14408 Found another reference now https://blog.brixit.nl/megapixels-2-0/ but seems this never finished.
Bug#1059669: marked as done (python-sure: autopkgtest failure with Python 3.12)
Your message dated Wed, 17 Jan 2024 08:36:01 + with message-id and subject line Bug#1059669: fixed in python-sure 2.0.1-0.1 has caused the Debian Bug report #1059669, regarding python-sure: autopkgtest failure with Python 3.12 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.) -- 1059669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-sure Version: 2.0.0-3 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-sure's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/python-sure/testing/amd64/ 49s - 49s 1) ERROR: Failure: ImportError (cannot import name 'assert_equals' from 'nose.tools' (/usr/lib/python3/dist-packages/nose/tools/__init__.py)) 49s 49sTraceback (most recent call last): 49s /usr/lib/python3/dist-packages/nose/failure.py line 39 in runTest 49s raise self.exc_val.with_traceback(self.tb) 49s /usr/lib/python3/dist-packages/nose/loader.py line 416 in loadTestsFromName 49s module = self.importer.importFromPath( 49s /usr/lib/python3/dist-packages/nose/importer.py line 47 in importFromPath 49s return self.importFromDir(dir_path, fqname) 49s /usr/lib/python3/dist-packages/nose/importer.py line 94 in importFromDir 49s mod = load_module(part_fqname, fh, filename, desc) 49s /usr/lib/python3/dist-packages/zombie_imp/imp_3_11.py line 238 in load_module 49s return load_source(name, filename, file) 49s /usr/lib/python3/dist-packages/zombie_imp/imp_3_11.py line 175 in load_source 49s module = _load(spec) 49s line 966 in _load 49s 49s line 935 in _load_unlocked 49s 49s line 994 in exec_module 49s 49s line 488 in _call_with_frames_removed 49s 49s tests/test_old_api.py line 27 in 49s from nose.tools import assert_equals, assert_raises 49sImportError: cannot import name 'assert_equals' from 'nose.tools' (/usr/lib/python3/dist-packages/nose/tools/__init__.py) --- End Message --- --- Begin Message --- Source: python-sure Source-Version: 2.0.1-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python-sure, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python-sure 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: Wed, 17 Jan 2024 08:44:38 +0100 Source: python-sure Architecture: source Version: 2.0.1-0.1 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Matthias Klose Closes: 1059669 Changes: python-sure (2.0.1-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version. Closes: #1059669. * Fix build with Python 3.12. * Disable two failing tests for now. * Remove .coverage when cleaning. Checksums-Sha1: bcfbf35a02e2c7e18b39ef937e8b831095850340 2164 python-sure_2.0.1-0.1.dsc 026e3ae927fadf7b134edde6c6684b07d0d14d2d 48467 python-sure_2.0.1.orig.tar.gz 0d0652af47075028fe383c1ddf96808a753168c8 4412 python-sure_2.0.1-0.1.debian.tar.xz c433743ce8a6e07c9cbee40b74686730b318f2f8 7155 python-sure_2.0.1-0.1_source.buildinfo Checksums-Sha256: 2fb9d5a57cc9c91bc0b575097bc9f7b7df20e9e6710df1b0613d21dfdd1160c6 2164 python-sure_2.0.1-0.1.dsc c8fc6fabc0e7f6984eeabb942540e45646e5bef0bb99fe59e02da634e4d4b9ca 48467 python-sure_2.0.1.orig.tar.gz 852f4045a0a124d311c6d684cde2c802f3f9187f08dcf08bfc8f134398b13b64 4412 python-sure_2.0.1-0.1.debian.tar.xz 14ed0bce52da4ac7c720e97207507d602d231ccff43ac92588a63f3c8d1a491a 7155 python-sure_2.0.1-0.1_source.buildinfo Files: 8a66c8da14327f6b4ea4a54c82d7644a 2164 python optional python-sure_2.0.1-0.1.dsc ec12c1e6a50cfac8dbe119943a4ddc6f 48467 python optional python-sure_2.0.1.orig.tar.gz 45e294effb917ccbbdc06d59924f4d7c 4412 python optional
Processed: affects 1061049
Processing commands for cont...@bugs.debian.org: > affects 1061049 + octave ceres-solver Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added indication that 1061049 affects octave and ceres-solver > thanks Stopping processing here. Please contact me if you need assistance. -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1061049
Processing commands for cont...@bugs.debian.org: > affects 1061049 + libdogleg2 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added indication that 1061049 affects libdogleg2 > thanks Stopping processing here. Please contact me if you need assistance. -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build
Package: src:h5py Version: 3.10.0-1 Severity: serious Tags: sid trixie armhf: h5py's tests expose unaligned memory accesses during the build, this not seen with with the 3.9.0 version. You don't see this on the Debian buildds itself, because they ignore these misalignments. Already happens with Python 3.11. [...] build/h5py/_debian_h5py_serial/tests/test_dims_dimensionproxy.py::TestItems::test_empty PASSED [ 53%] build/h5py/_debian_h5py_serial/tests/test_dtype.py::TestVlen::test_compound PASSED [ 53%] build/h5py/_debian_h5py_serial/tests/test_dtype.py::TestVlen::test_compound_vlen_bool Fatal Python error: Bus error Current thread 0xf7959020 (most recent call first): File "/<>/.pybuild/cpython3_3.11_h5py_serial/build/h5py/_debian_h5py_serial/_hl/dataset.py", line 841 in __getitem__ File "/<>/.pybuild/cpython3_3.11_h5py_serial/build/h5py/_debian_h5py_serial/tests/test_dtype.py", line 60 in test_compound_vlen_bool File "/usr/lib/python3.11/unittest/case.py", line 579 in _callTestMethod File "/usr/lib/python3.11/unittest/case.py", line 623 in run File "/usr/lib/python3.11/unittest/case.py", line 678 in __call__ File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 333 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 169 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 192 in console_main File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in File "", line 88 in _run_code File "", line 198 in _run_module_as_main
Processed: tagging 1061049 ...
Processing commands for cont...@bugs.debian.org: > tags 1061049 + upstream Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added tag(s) upstream. > forwarded 1061049 > https://github.com/DrTimothyAldenDavis/SuiteSparse/issues/741 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Set Bug forwarded-to-address to 'https://github.com/DrTimothyAldenDavis/SuiteSparse/issues/741'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"
Thanks. In case you're unaware, there're tools that can report ABI and API breaks. I usually use abi-compliance-checker (works great). And there's also abigail (have't tried it myself, but supposedly works well). Both are in Debian. Cheers.
Processed: notfound 1061049 in 1:7.3.1+dfsg-2, found 1061049 in 1:7.4.0+dfsg-1
Processing commands for cont...@bugs.debian.org: > notfound 1061049 1:7.3.1+dfsg-2 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" No longer marked as found in versions suitesparse/1:7.3.1+dfsg-2. > found 1061049 1:7.4.0+dfsg-1 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Marked as found in versions suitesparse/1:7.4.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 1051592, fixed 1051592 in 0.9.8-3.1+deb11u2, tagging 1051592
Processing commands for cont...@bugs.debian.org:
> unarchive 1051592
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables]
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Unarchived Bug 1051592
> fixed 1051592 0.9.8-3.1+deb11u2
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables]
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Marked as fixed in versions nftables/0.9.8-3.1+deb11u2.
> tags 1051592 + bullseye bookworm
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables]
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Added tag(s) bookworm and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1057717 to libuv1: io_uring support randomly segfaults after signal on ppc64el/ppc64 ...
Processing commands for cont...@bugs.debian.org: > retitle 1057717 libuv1: io_uring support randomly segfaults after signal on > ppc64el/ppc64 Bug #1057717 [libuv1] cmake ftbfs on ppc64el (and ppc64) Changed Bug title to 'libuv1: io_uring support randomly segfaults after signal on ppc64el/ppc64' from 'cmake ftbfs on ppc64el (and ppc64)'. > severity 1057717 serious Bug #1057717 [libuv1] libuv1: io_uring support randomly segfaults after signal on ppc64el/ppc64 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1057717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
