Bug#1026980: pyqt5: FTBFS on mipsel (MemoryError)
On 12/25/22 16:13, Dmitry Shachnev wrote: I noticed that code generation with Python 3.11 succeeded, and failed only with Python 3.10. My hypothesis is that it happened because we do not generate .pyi files with non-default Python versions. I will try to disable .pyi generation completely and see if the package builds on a porterbox. Dropping the --pep484-pyi option for the default Python and updating the .install files accordingly fixes the build failure on eller. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1024064: marked as done (cypari2 FTBFS with Python 3.11 as supported version)
Your message dated Mon, 26 Dec 2022 02:35:00 + with message-id and subject line Bug#1024064: fixed in cypari2 2.1.2-4 has caused the Debian Bug report #1024064, regarding cypari2 FTBFS with Python 3.11 as supported version 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.) -- 1024064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cypari2 Version: 2.1.2-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cypari2&ver=2.1.2-3%2Bb1 ... cypari2/convert.c: In function ‘__pyx_f_7cypari2_7convert_PyLong_FromINT’: cypari2/convert.c:3388:21: error: lvalue required as unary ‘&’ operand 3388 | __pyx_v_sizeptr = &Py_SIZE(((PyObject *)__pyx_v_x)); | ^ error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: /usr/bin/python3.11 setup.py build --- End Message --- --- Begin Message --- Source: cypari2 Source-Version: 2.1.2-4 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of cypari2, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated cypari2 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: Sun, 25 Dec 2022 22:03:37 -0400 Source: cypari2 Architecture: source Version: 2.1.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Stefano Rivera Closes: 1024064 Changes: cypari2 (2.1.2-4) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Python 3.11 support. (Closes: #1024064) . [ Debian Janitor ] * Use correct machine-readable copyright file URI. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit. * Drop unnecessary dependency on dh-autoreconf. * Update standards version to 4.6.0, no changes needed. Checksums-Sha1: 844e3863f989eeffea343063fa1ed0607d6434ac 1749 cypari2_2.1.2-4.dsc 932db08a68fe3e2a4f67bbb7f9c72e1890579a88 6248 cypari2_2.1.2-4.debian.tar.xz 16bd69ca2ee6dc3ff0ba34daf7f079f041e26a0c 6817 cypari2_2.1.2-4_source.buildinfo Checksums-Sha256: e2d049bd584a4e01ed18e2ba31e36bcf1f46c80e17472dc9edd863f1cce20509 1749 cypari2_2.1.2-4.dsc 0abec15c50e3d1d964f2424d6f032b59ec9ece05d10986fece019394c85d7002 6248 cypari2_2.1.2-4.debian.tar.xz d2c23a37ad4e5d745507144b1696017c1c3ccc5adc94167eb2e2bc6014f32a9e 6817 cypari2_2.1.2-4_source.buildinfo Files: 27cff02cff7adf9531d67f08fe9cf9a8 1749 python optional cypari2_2.1.2-4.dsc d9c9708972deea5d368595084663bbee 6248 python optional cypari2_2.1.2-4.debian.tar.xz ad70e9df7abf8f7242f616225f1f30ba 6817 python optional cypari2_2.1.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY6kBQxQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2A2XAP4hqJ+OKOY/UykRzdJ3up2NALrsQl0C a6Nq2dL+CCwBxQD+PvGmi2NLYj5rgR9HQzTIaLFi2+ZhpkwxbBsj3ca+Ggg= =iLR6 -END PGP SIGNATURE End Message ---
Bug#1026748: marked as done (dacite: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Mon, 26 Dec 2022 00:04:12 +
with message-id
and subject line Bug#1026748: fixed in dacite 1.7.0-1
has caused the Debian Bug report #1026748,
regarding dacite: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dacite
Version: 1.6.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/__init__.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/core.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/exceptions.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/config.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/data.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/types.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/dataclasses.py ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> copying dacite/py.typed ->
> /<>/.pybuild/cpython3_3.11_dacite/build/dacite
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/__init__.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/core.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/exceptions.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/config.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/data.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/types.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/dataclasses.py ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
> copying dacite/py.typed ->
> /<>/.pybuild/cpython3_3.10_dacite/build/dacite
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_dacite/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> collected 168 items
>
> tests/test_dataclasses.py .. [
> 3%]
> tests/test_types.py [
> 34%]
> .F. [
> 52%]
> tests/core/test_base.py .[
> 60%]
> tests/core/test_collection.py . [
> 70%]
> tests/core/test_config.py ...[
> 79%]
> tests/core/test_init_var.py .. [
> 80%]
> tests/core/test_literal.py [
> 83%]
> tests/core/test_optional.py .. [
> 91%]
> tests/core/test_type.py .[
> 92%]
> tests/core/test_union.py .
> [100%]
>
> === FAILURES
> ===
> ___ test_is_instance_with_empty_tuple_and_not_matching_type
>
>
> def test_is_instance_with_empty_tuple_and_not_matching_type():
> > assert not is_instance((1, 2), Tuple[()])
> E assert not True
> E+ where True = is_instance((1, 2), typing.Tuple[()])
>
> tests/test_types.py:297: AssertionError
> === short test summary info
>
> FAILED
> tests/test_types.py::test_is_instance_with_emp
Bug#1022742: marked as done (multipath-tools: CVE-2022-41973 CVE-2022-41974)
Your message dated Sun, 25 Dec 2022 23:49:36 + with message-id and subject line Bug#1022742: fixed in multipath-tools 0.9.4-1 has caused the Debian Bug report #1022742, regarding multipath-tools: CVE-2022-41973 CVE-2022-41974 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.) -- 1022742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: multipath-tools Version: 0.9.0-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.7.9-3 Hi, The following vulnerabilities were published for multipath-tools. CVE-2022-41973[0]: | Symlink attack CVE-2022-41974[1]: | Authorization bypass If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-41973 https://www.cve.org/CVERecord?id=CVE-2022-41973 [1] https://security-tracker.debian.org/tracker/CVE-2022-41974 https://www.cve.org/CVERecord?id=CVE-2022-41974 [2] https://www.openwall.com/lists/oss-security/2022/10/24/2 Regards, Salvatore --- End Message --- --- Begin Message --- Source: multipath-tools Source-Version: 0.9.4-1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of multipath-tools, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated multipath-tools 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: Sun, 25 Dec 2022 23:19:21 + Source: multipath-tools Architecture: source Version: 0.9.4-1 Distribution: unstable Urgency: medium Maintainer: Debian DM Multipath Team Changed-By: Chris Hofstaedtler Closes: 1022742 Changes: multipath-tools (0.9.4-1) unstable; urgency=medium . * [369b812] New upstream version 0.9.4 (Closes: #1022742) * [ee2206e] Refresh patches * [bcb0b07] Rework build steps to follow upstream changes. And install libmpathutil.so. * [f8ef90a] Use upstream-supported way of disabling systemd (for udeb) * [8785eef] Update lintian-overrides Checksums-Sha1: 710ea95f53bc8496ca19c227c23148338bb93973 2572 multipath-tools_0.9.4-1.dsc 1819f3b176c4d224b1820c973bc98a4bdd008164 554381 multipath-tools_0.9.4.orig.tar.gz e3182ffd58ccc6f2a204dfcd700ef07d56feea32 28968 multipath-tools_0.9.4-1.debian.tar.xz 7a9d72482a658abdaa5c7cbafb56a01dce9a1f14 7008 multipath-tools_0.9.4-1_source.buildinfo Checksums-Sha256: 7b6faffb54cc834fb1059c132c20b05ade8f6a399e3e52d250c817d79ea51e74 2572 multipath-tools_0.9.4-1.dsc 6ed3cf6e786da20a451d9747cbd4c5817815388b8fc8022d1074b3018479031d 554381 multipath-tools_0.9.4.orig.tar.gz 9d105621faa16849c9a84b7d3e30635b53ae085c18fc595a5772dbcca2d5834f 28968 multipath-tools_0.9.4-1.debian.tar.xz 02303e514a39846e43ebafe9b71b91ad459b63c3bc9a4217778b1f814c41ab47 7008 multipath-tools_0.9.4-1_source.buildinfo Files: bdc855a8771cb091fb50f45ce2edfc41 2572 admin optional multipath-tools_0.9.4-1.dsc db72eeaabb3859b68c2fdacb38502a52 554381 admin optional multipath-tools_0.9.4.orig.tar.gz 1c7b402fc9959bf52261a7e23a846c59 28968 admin optional multipath-tools_0.9.4-1.debian.tar.xz d419d363beb9f72b90a9ca73a69c7780 7008 admin optional multipath-tools_0.9.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmOo29gACgkQXBPW25MF LgPIOQ/+MY0ni2/LOwdCFepUHgueSLs+xgPjhmqn+ey0UaZEOz4nIiCV6/cUg0qS ohJkiHgKcQDYBKlQvlMWubQckVYzc8jMYVFtxpNoB/gkv0NSOSWAebKhaPUF97LP GKO0ZY9/z05ehOJyufwyw9AZIXcVy8VjTf/Za4xey1wH65KYZzTj4pMJ7hx0k9X8 AN5as5Nt8E+6bV631YdY2+CAnFhfn+mIQN76oF7X5o39hw/fyXTG7RG4SvOOmN6p D2Ymc+i+lWoO3V9e5zV/exg39RFuX8Qrcv5no089w5rflHQgkBKTkg2TTJA5/HBY B0RecSJP2GN2sBDgP/mCgzB94t5A3uRTYY/quFujFnTYzYpOQlyQnCYyEVJTrR7e xxNyPU2yiVZmCKqZeiy0DgeOMadkI1uaIEz0HUs8C9OrIJweb2Fd/cpvOtyY8TLz jm+4JzeaeCDrNbfwqTozQU+Rhfc2NMYcipilmJEDpEG8XneReCfMPyyu9DTBcBP0 0uuK+XlJK3/tbuRjQgxdGl3DDJrfQG1NRZ8kyo/kB1xRDDjog1hhIQu
Processed: affects 1024261
Processing commands for cont...@bugs.debian.org: > affects 1024261 src:util-linux Bug #1024261 [debhelper] debhelper: dbgsym packages contain directory writable by build user Added indication that 1024261 affects src:util-linux > thanks Stopping processing here. Please contact me if you need assistance. -- 1024261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026936: marked as done (davmail-server: trying to overwrite '/etc/davmail/davmail.properties', which is also in package davmail)
Your message dated Sun, 25 Dec 2022 23:04:16 + with message-id and subject line Bug#1026936: fixed in davmail 6.0.1.3390-3 has caused the Debian Bug report #1026936, regarding davmail-server: trying to overwrite '/etc/davmail/davmail.properties', which is also in package davmail 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.) -- 1026936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: davmail-server Version: 6.0.1.3390-2 Severity: serious Justification: fails to install -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When updating davmail from 6.0.1.3390-1.1 to 6.0.1.3390-2, davmail-server is pulled in as a new dependency, and it fails to install: Preparing to unpack .../davmail-server_6.0.1.3390-2_all.deb ... Unpacking davmail-server (6.0.1.3390-2) ... dpkg: error processing archive /var/cache/apt/archives/davmail-server_6.0.1.3390-2_all.deb (--unpack): trying to overwrite '/etc/davmail/davmail.properties', which is also in package davmail 6.0.1.3390-1.1 Cheers, gregor - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages davmail-server depends on: ii adduser 3.129 ii default-jre-headless [java9-runtime-headless] 2:1.17-73 hi init-system-helpers 1.64 ii libcommons-codec-java 1.15-1 ii libcommons-logging-java 1.2-3 ii libhtmlcleaner-java 2.26-1 ii libhttpclient-java4.5.14-1 ii libjackrabbit-java2.20.3-1 ii libjcifs-java 1.3.19-2 ii libjettison-java 1.5.1-1 ii libjna-java 5.12.1-1 ii liblog4j1.2-java 1.2.17-11 ii libmail-java 1.6.5-1 ii libslf4j-java 1.7.32-1 ii libstax2-api-java 4.1-1 ii libwoodstox-java 1:6.2.1-1 ii logrotate 3.21.0-1 ii openjdk-11-jre-headless [java9-runtime-headless] 11.0.17+8-2 ii openjdk-17-jre-headless [java9-runtime-headless] 17.0.5+8-2 ii sysvinit-utils [lsb-base] 3.06-2 davmail-server recommends no packages. davmail-server suggests no packages. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmOm47JfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qga1rw/+NMw8fcQDIYDtlJh9TMjfdnJwmLb3DYtliWPWbdeJSqihIzjI+AP8vYtk AXmYYfovDLqwhK4X94wPOz35VJFQQsVcDnx2LCEgg6z0hUJz2a9wJX49ErgIi2qt ZlJekxIfNgFm9FSkcEhUyR6NtVznWBHCti5vYlqDhZymx6gmMpJTGElEb/8Yu96r ehIyDdgGo4IrcRyz8+yxCOh8K2RcDV8PKKr5muQueqTApJ1QF2e6ZOK3uvHt6V0R y9rj6Ejk7eA4PS37FK3wOj5mbB7/ZLLtWP4sihZ3uZ6BCr/Pl4dVk23WpNGkNbbI nTmmriW5nlaIezlIw7X3d2aPC9t0UetInWSNQrg4YSuOvsdMCL4InRjM1lKX7PNB fTcuUXaMwuVLi3Z05OxMU0v1UOqL+kL7GppMJyFLxeRggFhMGNCMYvsI88AcLeZm 9Ck8y8l7hxionXoyGwZc8ZB1Cm2jjiPWEb7sJ84OqYaG2HlXWdk5ec1uHUFrTFpe waBU6go7U9pq17l33kpNIONFf5SApyvv/fqiXTiLXa8P6xCyP3xJ2I9z3M8IBP40 lyzF2ETwiyCT/+53B39ZuejJQDYt5GioiG0X5F8kWZGDzh03M8J+dVRlsMCRP92s UtzaPeY7YrfXRAaoBPJaJTLk3LYAWp3JMOXGD/y2p5KTGik+t64= =Xdst -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: davmail Source-Version: 6.0.1.3390-3 Done: Alexandre Rossi We believe that the bug you reported is fixed in the latest version of davmail, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian dist
Processed: Re: Bug#1026159: okular: Bogus memory allocation size error - some pages not displayed
Processing control commands:
> severity -1 normal
Bug #1026159 {Done: Aurélien COUDERC } [okular] okular: Bogus
memory allocation size error - some pages not displayed
Severity set to 'normal' from 'serious'
--
1026159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026159: okular: Bogus memory allocation size error - some pages not displayed
control: severity -1 normal Le 25 décembre 2022 18:27:26 GMT+01:00, Marco Mattiolo a écrit : >I am not the package's maintainer and maybe I am not so much into the topic, >but this bug report is barely understandable: what is being reported? > >Is this package failing to build from source? How is it being built? What's >the error message? > >Or is this about okular failing to display some pages of a specific PDF >document? On which okular version? Does this deserve a serious severity? > >If you are facing two issues, please file two separate bug reports... Yes agreed, please provide more detailed information and file different big reports for different issues. Happy hacking, -- Aurélien
Bug#1008328: marked as done (ipywidgets: FTBFS: ERROR: Failure: ModuleNotFoundError (No module named 'ipython_genutils'))
Your message dated Sun, 25 Dec 2022 21:50:29 + with message-id and subject line Bug#1008328: fixed in ipywidgets 6.0.0-10 has caused the Debian Bug report #1008328, regarding ipywidgets: FTBFS: ERROR: Failure: ModuleNotFoundError (No module named 'ipython_genutils') 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.) -- 1008328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipywidgets Version: 6.0.0-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > nosetests3 ipywidgets > E > == > ERROR: Failure: ModuleNotFoundError (No module named 'ipython_genutils') > -- > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest > raise self.exc_val.with_traceback(self.tb) > File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in > loadTestsFromName > module = self.importer.importFromPath( > File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in > importFromPath > return self.importFromDir(dir_path, fqname) > File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in > importFromDir > mod = load_module(part_fqname, fh, filename, desc) > File "/usr/lib/python3.9/imp.py", line 244, in load_module > return load_package(name, filename) > File "/usr/lib/python3.9/imp.py", line 216, in load_package > return _load(spec) > File "", line 711, in _load > File "", line 680, in _load_unlocked > File "", line 850, in exec_module > File "", line 228, in _call_with_frames_removed > File "/<>/ipywidgets/__init__.py", line 25, in > from .widgets import * > File "/<>/ipywidgets/widgets/__init__.py", line 4, in > from .widget import Widget, CallbackDispatcher, register, > widget_serialization, handle_version_comm_opened > File "/<>/ipywidgets/widgets/widget.py", line 17, in > from ipython_genutils.py3compat import string_types, PY3 > ModuleNotFoundError: No module named 'ipython_genutils' > > -- > Ran 1 test in 0.000s > > FAILED (errors=1) > make[1]: *** [debian/rules:41: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/03/26/ipywidgets_6.0.0-9_unstable.log 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 marking 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: ipywidgets Source-Version: 6.0.0-10 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ipywidgets, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ipywidgets 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: Sun, 25 Dec 2022 22:42:11 +0100 Source: ipywidgets Architecture: source Version: 6.0.0-10 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jochen Sprickerhof Closes: 1008328 Changes: ipywidgets (6.0.0-10) unstable; urgency=medium . * Team upload. * Add missing build dependency (Closes: #1008328) Checksums-Sha1: 04c332f8251dc3153c43ec61ca0737fe7a06f934 2994 ipywidgets_6.0.0-10.dsc 159303df0489af54704cfe1a34667bbe665fd386 136964 ipywidgets_6.0.0-10.debian.tar.xz 8a6af6e00da6e964a6ad2eb9421d3
Bug#1026339: marked as done (go-gir-generator: FTBFS randomly because of Makefile bug)
Your message dated Sun, 25 Dec 2022 21:50:12 + with message-id and subject line Bug#1026339: fixed in go-gir-generator 2.2.0-1 has caused the Debian Bug report #1026339, regarding go-gir-generator: FTBFS randomly because of Makefile bug 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.) -- 1026339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:go-gir-generator Version: 2.0.2-1 Severity: serious Tags: bullseye ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: dh_auto_build -a make -j2 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' mkdir -p out/src/pkg.deepin.io/gir/ cp -r lib.in/gobject-2.0 out/src/pkg.deepin.io/gir/ cp: cannot create directory 'out/src/pkg.deepin.io/gir/': No such file or directory make[1]: *** [Makefile:22: copyfile] Error 1 make[1]: *** Waiting for unfinished jobs cd src/gir-generator && go build -o /<>/out/gir-generator make[1]: Leaving directory '/<>' dh_auto_build: error: make -j2 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:8: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 This happens because I was using parallel build and there is a bug in the upstream Makefile: build: glib-2.0 gobject-2.0 gio-2.0 gudev-1.0 copyfile It may happen (and in fact it happened to me), that copyfile is tried before the other dependencies of build, in which case not only $(OUT_GIR_DIR) does not exist yet, but maybe also the things we want to copy have not been created yet. To reproduce the bug, try putting copyfile first, like this: build: copyfile glib-2.0 gobject-2.0 gio-2.0 gudev-1.0 and try to build with a single CPU to force sequential order, maybe this is enough: export DEB_BUILD_OPTIONS=parallel=1; dpkg-buildpackage etc etc The attached patch may help, but I've not tested it. You might want to forward this upstream and apply the official patch, whatever it will be. Thanks.--- a/Makefile +++ b/Makefile @@ -11,7 +11,8 @@ export GOPATH = $(CURDIR):$(CURDIR)/out GENERATOR = out/gir-generator -build: glib-2.0 gobject-2.0 gio-2.0 gudev-1.0 copyfile +build: glib-2.0 gobject-2.0 gio-2.0 gudev-1.0 + $(MAKE) copyfile generator: mkdir -p $(OUT_GIR_DIR) --- End Message --- --- Begin Message --- Source: go-gir-generator Source-Version: 2.2.0-1 Done: Arun Kumar Pariyar We believe that the bug you reported is fixed in the latest version of go-gir-generator, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arun Kumar Pariyar (supplier of updated go-gir-generator 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: Mon, 26 Dec 2022 03:18:54 +0545 Source: go-gir-generator Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Arun Kumar Pariyar Changed-By: Arun Kumar Pariyar Closes: 1026339 Changes: go-gir-generator (2.2.0-1) unstable; urgency=medium . * New upstream release. * debian/control: Bump Standards-Version to 4.6.2. * debian/copyright: Refresh copyright info. * Update path in install files. * Add vendor directory to debian/clean. * debian/patches: Refresh patches. (Closes: #1026339) Checksums-Sha1: 980c2c21d6fc30f621727adfef8bce82e383b408 2490 go-gir-generator_2.2.0-1.dsc 519cdf1519fe45c21072d63674794195dfad1616 263451 go-gir-generator_2.2.0.orig.tar.gz fdd096150200804b9ce2487de41ed4174af556bb 4836 go-gir-generator_2.2.0-1.debian.tar.xz b53df3842083293e1a734261c1d3b1ff2a740c6e 16290 go-gir-generator_2.2.0-1_amd64.buildinfo Checksums-Sha256: d9b89027ad623ca46f7030c8c755f941bbeaca583942a8a2d35acc126f6ca41d 2490 go-gir-generator_2.2.0-1.dsc c49bd39acf9eb9efc071c36ab5b0e9ed7211484ced4557b45b412a593a61979b 263451 go-gir-generator_2.2.0.orig.tar.gz a975da1a855db3d39839c662184ba857baacadc1fe6a2002a3cbaba291914043 4836 go-gir-generator_2.2.0-1.debian.tar.xz 473ca352adce61c361
Processed: Bug#1008328 marked as pending in ipywidgets
Processing control commands: > tag -1 pending Bug #1008328 [src:ipywidgets] ipywidgets: FTBFS: ERROR: Failure: ModuleNotFoundError (No module named 'ipython_genutils') Added tag(s) pending. -- 1008328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008328: marked as pending in ipywidgets
Control: tag -1 pending Hello, Bug #1008328 in ipywidgets 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/ipywidgets/-/commit/9fd66791f7337cd507ab57be439f857640bf863e Add missing build dependency Closes: #1008328 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008328
Bug#1026636: marked as done (bottleneck: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Sun, 25 Dec 2022 21:19:03 +
with message-id
and subject line Bug#1026636: fixed in bottleneck 1.3.5+ds1-1
has caused the Debian Bug report #1026636,
regarding bottleneck: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bottleneck
Version: 1.3.2+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py build_ext --inplace
> running build_ext
> running config
> building 'bottleneck.reduce' extension
> creating build
> creating build/temp.linux-x86_64-cpython-310
> creating build/temp.linux-x86_64-cpython-310/bottleneck
> creating build/temp.linux-x86_64-cpython-310/bottleneck/src
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include
> -I/usr/include/python3.10 -Ibottleneck/src -c bottleneck/src/reduce.c -o
> build/temp.linux-x86_64-cpython-310/bottleneck/src/reduce.o -O2
> creating build/lib.linux-x86_64-cpython-310
> creating build/lib.linux-x86_64-cpython-310/bottleneck
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-cpython-310/bottleneck/src/reduce.o
> -L/usr/lib/x86_64-linux-gnu -o
> build/lib.linux-x86_64-cpython-310/bottleneck/reduce.cpython-310-x86_64-linux-gnu.so
> building 'bottleneck.move' extension
> creating build/temp.linux-x86_64-cpython-310/bottleneck/src/move_median
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include
> -I/usr/include/python3.10 -Ibottleneck/src -c bottleneck/src/move.c -o
> build/temp.linux-x86_64-cpython-310/bottleneck/src/move.o -O2
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include
> -I/usr/include/python3.10 -Ibottleneck/src -c
> bottleneck/src/move_median/move_median.c -o
> build/temp.linux-x86_64-cpython-310/bottleneck/src/move_median/move_median.o
> -O2
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-cpython-310/bottleneck/src/move.o
> build/temp.linux-x86_64-cpython-310/bottleneck/src/move_median/move_median.o
> -L/usr/lib/x86_64-linux-gnu -o
> build/lib.linux-x86_64-cpython-310/bottleneck/move.cpython-310-x86_64-linux-gnu.so
> building 'bottleneck.nonreduce' extension
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include
> -I/usr/include/python3.10 -Ibottleneck/src -c bottleneck/src/nonreduce.c -o
> build/temp.linux-x86_64-cpython-310/bottleneck/src/nonreduce.o -O2
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-cpython-310/bottlene
Bug#1026545: marked as done (automat: FTBFS: /bin/sh: 1: dot: not found)
Your message dated Sun, 25 Dec 2022 20:34:12 + with message-id and subject line Bug#1026545: fixed in automat 22.10.0-1 has caused the Debian Bug report #1026545, regarding automat: FTBFS: /bin/sh: 1: dot: not found 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.) -- 1026545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: automat Version: 20.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm 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 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > running config > I: pybuild base:240: python3.10 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3.11 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/__init__.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/_methodical.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/_discover.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/_visualize.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/_core.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > copying automat/_introspection.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat > creating /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/__init__.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/test_methodical.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/test_visualize.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/test_core.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/test_trace.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > copying automat/_test/test_discover.py -> > /<>/.pybuild/cpython3_3.11_automat/build/automat/_test > running egg_info > writing Automat.egg-info/PKG-INFO > writing dependency_links to Automat.egg-info/dependency_links.txt > writing entry points to Automat.egg-info/entry_points.txt > writing requirements to Automat.egg-info/requires.txt > writing top-level names to Automat.egg-info/top_level.txt > reading manifest file 'Automat.egg-info/SOURCES.txt' > adding license file 'LICENSE' > writing manifest file 'Automat.egg-info/SOURCES.txt' > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/__init__.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/_methodical.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/_discover.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/_visualize.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/_core.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > copying automat/_introspection.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat > creating /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/__init__.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/test_methodical.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/test_visualize.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/test_core.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/test_trace.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > copying automat/_test/test_discover.py -> > /<>/.pybuild/cpython3_3.10_automat/build/automat/_test > running egg_info > writing Automat.egg-info/PKG-INFO > writing dependency_links to Automat.egg-info/dependency_links.txt > writing entry points to Automat.egg-info/entry_points.txt > writing requirements to Automat.egg-info/requires.txt > writing top-level names to Automat.egg-info/top_level.txt > reading manifest file 'Automat.egg-info/SOURCES.txt' > adding license file 'LICENSE' > wri
Processed: reassign 1023569 to src:dpdk, fixed 1023569 in 22.11~rc2-1, fixed 1023569 in 22.11.1-2 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1023569 src:dpdk 21.11-5
Bug #1023569 {Done: Luca Boccassi } [librte-net-af-xdp22]
librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
Warning: Unknown package 'librte-net-af-xdp22'
Bug reassigned from package 'librte-net-af-xdp22' to 'src:dpdk'.
No longer marked as found in versions dpdk/21.11-5.
No longer marked as fixed in versions dpdk/22.11~rc2-1 and dpdk/22.11.1-2.
Bug #1023569 {Done: Luca Boccassi } [src:dpdk]
librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
Marked as found in versions dpdk/21.11-5.
> fixed 1023569 22.11~rc2-1
Bug #1023569 {Done: Luca Boccassi } [src:dpdk]
librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
Marked as fixed in versions dpdk/22.11~rc2-1.
> fixed 1023569 22.11.1-2
Bug #1023569 {Done: Luca Boccassi } [src:dpdk]
librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
Marked as fixed in versions dpdk/22.11.1-2.
> notfixed 83 2:4.13.0+dfsg-1
Bug #83 {Done: Michael Tokarev } [samba-common-bin]
samba-common-bin: samba-tool classic update w/LDAP - parsing error
There is no source info for the package 'samba-common-bin' at version
'2:4.13.0+dfsg-1' with architecture ''
Unable to make a source version for version '2:4.13.0+dfsg-1'
No longer marked as fixed in versions 2:4.13.0+dfsg-1.
> fixed 83 2:4.13.2+dfsg-1
Bug #83 {Done: Michael Tokarev } [samba-common-bin]
samba-common-bin: samba-tool classic update w/LDAP - parsing error
Marked as fixed in versions samba/2:4.13.2+dfsg-1.
> tags 1015626 - bookworm sid
Bug #1015626 {Done: Patrick Franz }
[src:qt6-virtualkeyboard] qt6-virtualkeyboard: ftbfs with LTO (link time
optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015624 - bookworm sid
Bug #1015624 {Done: Patrick Franz } [src:qt6-scxml]
qt6-scxml: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> notfixed 782628 2:4.13.0+dfsg-1
Bug #782628 {Done: Michael Tokarev } [samba] samba: bsd
virtual printers doesnt works on clients win2k or winxp
There is no source info for the package 'samba' at version '2:4.13.0+dfsg-1'
with architecture ''
Unable to make a source version for version '2:4.13.0+dfsg-1'
No longer marked as fixed in versions 2:4.13.0+dfsg-1.
> fixed 782628 2:4.13.2+dfsg-1
Bug #782628 {Done: Michael Tokarev } [samba] samba: bsd
virtual printers doesnt works on clients win2k or winxp
Marked as fixed in versions samba/2:4.13.2+dfsg-1.
> notfixed 767896 2:4.13.0+dfsg-1
Bug #767896 {Done: Michael Tokarev } [samba] samba: cannot
access shared directories with a literal asterisk character in their name
There is no source info for the package 'samba' at version '2:4.13.0+dfsg-1'
with architecture ''
Unable to make a source version for version '2:4.13.0+dfsg-1'
No longer marked as fixed in versions 2:4.13.0+dfsg-1.
> fixed 767896 2:4.13.2+dfsg-1
Bug #767896 {Done: Michael Tokarev } [samba] samba: cannot
access shared directories with a literal asterisk character in their name
Marked as fixed in versions samba/2:4.13.2+dfsg-1.
> notfixed 770019 4.0.0+dfsg1-1
Bug #770019 {Done: Michael Tokarev } [samba] samba: Adding
Printer Drivers to [print$] fails
There is no source info for the package 'samba' at version '4.0.0+dfsg1-1' with
architecture ''
Unable to make a source version for version '4.0.0+dfsg1-1'
No longer marked as fixed in versions 4.0.0+dfsg1-1.
> fixed 770019 2:4.0.0+dfsg1-1
Bug #770019 {Done: Michael Tokarev } [samba] samba: Adding
Printer Drivers to [print$] fails
There is no source info for the package 'samba' at version '2:4.0.0+dfsg1-1'
with architecture ''
Unable to make a source version for version '2:4.0.0+dfsg1-1'
Marked as fixed in versions 2:4.0.0+dfsg1-1.
> notfixed 426700 4.0.0+dfsg1-1
Bug #426700 {Done: Michael Tokarev } [samba] samba: Samba
incorrectly remembers defunct IP addresses when running as a WINS server
There is no source info for the package 'samba' at version '4.0.0+dfsg1-1' with
architecture ''
Unable to make a source version for version '4.0.0+dfsg1-1'
No longer marked as fixed in versions 4.0.0+dfsg1-1.
> fixed 426700 2:4.0.0+dfsg1-1
Bug #426700 {Done: Michael Tokarev } [samba] samba: Samba
incorrectly remembers defunct IP addresses when running as a WINS server
There is no source info for the package 'samba' at version '2:4.0.0+dfsg1-1'
with architecture ''
Unable to make a source version for version '2:4.0.0+dfsg1-1'
Marked as fixed in versions 2:4.0.0+dfsg1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1015624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015624
1015626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015626
1023569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023569
426700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426700
767896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767896
770019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770019
782628: https://bugs.debian.org/c
Bug#1026992: graphite-web: CVE-2022-4728 CVE-2022-4729 CVE-2022-4730
Source: graphite-web Version: 1.1.8-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for graphite-web. Filling with RC severity is slightly borderline, but we should assure graphite-web is oon that regard uptodate in bookworm. CVE-2022-4728[0]: | A vulnerability has been found in Graphite Web and classified as | problematic. This vulnerability affects unknown code of the component | Cookie Handler. The manipulation leads to cross site scripting. The | attack can be initiated remotely. The exploit has been disclosed to | the public and may be used. The name of the patch is | 2f178f490e10efc03cd1d27c72f64ecab224eb23. It is recommended to apply a | patch to fix this issue. VDB-216742 is the identifier assigned to this | vulnerability. CVE-2022-4729[1]: | A vulnerability was found in Graphite Web and classified as | problematic. This issue affects some unknown processing of the | component Template Name Handler. The manipulation leads to cross site | scripting. The attack may be initiated remotely. The exploit has been | disclosed to the public and may be used. The name of the patch is | 2f178f490e10efc03cd1d27c72f64ecab224eb23. It is recommended to apply a | patch to fix this issue. The associated identifier of this | vulnerability is VDB-216743. CVE-2022-4730[2]: | A vulnerability was found in Graphite Web. It has been classified as | problematic. Affected is an unknown function of the component Absolute | Time Range Handler. The manipulation leads to cross site scripting. It | is possible to launch the attack remotely. The exploit has been | disclosed to the public and may be used. The name of the patch is | 2f178f490e10efc03cd1d27c72f64ecab224eb23. It is recommended to apply a | patch to fix this issue. The identifier of this vulnerability is | VDB-216744. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-4728 https://www.cve.org/CVERecord?id=CVE-2022-4728 [1] https://security-tracker.debian.org/tracker/CVE-2022-4729 https://www.cve.org/CVERecord?id=CVE-2022-4729 [2] https://security-tracker.debian.org/tracker/CVE-2022-4730 https://www.cve.org/CVERecord?id=CVE-2022-4730 Regards, Salvatore
Processed: Re: Bug#414092: airport-utils: Tools start and quit immediately without working
Processing control commands: > severity -1 grave Bug #414092 [airport-utils] airport-utils: Tools start and quit immediately without working Severity set to 'grave' from 'important' > found -1 airport-utils/2-8 Bug #414092 [airport-utils] airport-utils: Tools start and quit immediately without working Marked as found in versions airport-utils/2-8. -- 414092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023712: why3 breaks frama-c (autopkgtest): missing versioned Breaks?
Hi Paul, On Wed, Dec 21, 2022 at 09:16:32PM +0100, Paul Gevers wrote: > Control: reassign -1 frama-c > > Dear maintainers, > > On Tue, 8 Nov 2022 21:53:18 +0100 Paul Gevers wrote: > > [kernel] User Error: cannot load plug-in 'frama-c-wp': cannot load module > >Details: implementation mismatch on Why3 > > [kernel] User Error: Deferred error message was emitted during > > execution. See above messages for more information. > > [kernel] Frama-C aborted: invalid user input. > > autopkgtest [20:18:19]: test eva > > I'm now seeing the above error message in the frama-c test in testing, so it > seems that the issue is rather that the autopkgtest of frama-c doesn't > properly declare it's *versioned* test dependency on why3? Should the > Recommends be versioned? (Not sure if that actually works as intended, but > apparently the tested plug-in only works correctly with the right version of > why3). Sorry for not replying earlier, the last weeks have been very busy at work. The problem is that for some reason the package build of frama-c does not pick up the versioned dependency on libwhy3-ocaml-dev (this should be done by dh_ocaml). I'm looking into this now. Cheers -Ralf.
Bug#1025181: qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
I see this is fixed upstream in around 0.11, by https://github.com/Qiskit/qiskit-ibmq-provider/pull/779 Given #1008627 and the deprecation upstream, should we just drop the package, entirely? SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Processed: tagging 1025181
Processing commands for cont...@bugs.debian.org: > tags 1025181 + fixed-upstream Bug #1025181 [src:qiskit-ibmq-provider] qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025117: marked as done (python-pyramid: (autopkgtest) needs update for python3.11: 'Translations' object has no attribute 'lgettext')
Your message dated Sun, 25 Dec 2022 18:49:54 +
with message-id
and subject line Bug#1025117: fixed in python-pyramid 2.0+dfsg-2
has caused the Debian Bug report #1025117,
regarding python-pyramid: (autopkgtest) needs update for python3.11:
'Translations' object has no attribute 'lgettext'
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.)
--
1025117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyramid
Version: 2.0+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-pyramid fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-pyramid from testing2.0+dfsg-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pyramid/28750382/log.gz
=== FAILURES
===
___ TestTranslations.test_ldgettext
self =
def test_ldgettext(self):
t = self._makeOne()
self.assertEqual(t.ldgettext('messages', 'foo'), b'Voh')
tests/test_i18n.py:426: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , domain = 'messages', message = 'foo'
def ldgettext(self, domain, message):
"""Like ``lgettext()``, but look the message up in the specified
domain.
"""
return self._domains.get(domain, self).lgettext(message)
E AttributeError: 'Translations' object has no attribute 'lgettext'
/usr/lib/python3/dist-packages/pyramid/i18n.py:342: AttributeError
___ TestTranslations.test_ldngettext
___
self =
def test_ldngettext(self):
t = self._makeOne()
self.assertEqual(t.ldngettext('messages', 'foo1', 'foos1', 1), b'Voh1')
tests/test_i18n.py:441: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , domain = 'messages', singular = 'foo1'
plural = 'foos1', num = 1
def ldngettext(self, domain, singular, plural, num):
"""Like ``lngettext()``, but look the message up in the specified
domain.
"""
return self._domains.get(domain, self).lngettext(singular, plural, num)
E AttributeError: 'Translations' object has no attribute 'lngettext'
/usr/lib/python3/dist-packages/pyramid/i18n.py:360: AttributeError
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pyramid
Source-Version: 2.0+dfsg-2
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-pyramid, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-pyramid
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: Sun, 25 Dec 2022 14:24:55 -0400
Source: python-pyramid
Architecture: source
Version: 2.0+dfsg-2
Distribution: unstable
Urgency: medi
Bug#1025179: marked as done (pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local')
Your message dated Sun, 25 Dec 2022 14:34:57 -0400 with message-id <20221225183457.2yk442e34rbah...@haydn.kardiogramm.net> and subject line Re: Bug#1025179: pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local' has caused the Debian Bug report #1025179, regarding pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local' 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.) -- 1025179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyvows Version: 3.0.0-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of pyvows fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 pyvows from testing3.0.0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyvows/28796433/log.gz === python3.11 === Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/lib/python3/dist-packages/pyvows/__main__.py", line 12, in sys.exit(main()) ^^ File "/usr/lib/python3/dist-packages/pyvows/cli.py", line 184, in main result = run( File "/usr/lib/python3/dist-packages/pyvows/cli.py", line 136, in run from pyvows.core import Vows File "/usr/lib/python3/dist-packages/pyvows/core.py", line 20, in from pyvows.decorators import _batch, async_topic, capture_error, skip_if File "/usr/lib/python3/dist-packages/pyvows/decorators.py", line 15, in from pyvows.runner import SkipTest File "/usr/lib/python3/dist-packages/pyvows/runner/__init__.py", line 10, in from pyvows.runner.gevent import VowsParallelRunner as VowsRunner File "/usr/lib/python3/dist-packages/pyvows/runner/gevent.py", line 27, in from gevent.pool import Pool File "/usr/lib/python3/dist-packages/gevent/__init__.py", line 86, in from gevent._hub_local import get_hub File "/usr/lib/python3/dist-packages/gevent/_hub_local.py", line 101, in import_c_accel(globals(), 'gevent.__hub_local') File "/usr/lib/python3/dist-packages/gevent/_util.py", line 148, in import_c_accel mod = importlib.import_module(cname) ^^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ModuleNotFoundError: No module named 'gevent._gevent_c_hub_local' autopkgtest [01:16:00]: test unittests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi Paul (2022.11.30_15:58:04_-0400) > ModuleNotFoundError: No module named 'gevent._gevent_c_hub_local' This seems to have been resolved. Presumably it was an issue in the gevent stack. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272--- End Message ---
Bug#1025117: marked as pending in python-pyramid
Control: tag -1 pending Hello, Bug #1025117 in python-pyramid 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-pyramid/-/commit/198c2961b51f17d7768b675cd072ac319310d906 Patch: Add support for Python 3.11 (Closes: #1025117) (this message was generated automatically) -- Greetings https://bugs.debian.org/1025117
Processed: Bug#1025117 marked as pending in python-pyramid
Processing control commands: > tag -1 pending Bug #1025117 [src:python-pyramid] python-pyramid: (autopkgtest) needs update for python3.11: 'Translations' object has no attribute 'lgettext' Added tag(s) pending. -- 1025117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026521: marked as done (python-randomize: FTBFS: AssertionError: 'test_C (fixtures.Tests.test_C) ... ok' != 'test_C (fixtures.Tests) ... ok')
Your message dated Sun, 25 Dec 2022 18:20:47 + with message-id and subject line Bug#1026521: fixed in python-randomize 0.14-3 has caused the Debian Bug report #1026521, regarding python-randomize: FTBFS: AssertionError: 'test_C (fixtures.Tests.test_C) ... ok' != 'test_C (fixtures.Tests) ... ok' 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.) -- 1026521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-randomize Version: 0.14-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > make: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > dh build --buildsystem=pybuild --with python3 >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > running config > I: pybuild base:240: python3.10 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3.11 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_randomize/build/randomize > copying randomize/plugin.py -> > /<>/.pybuild/cpython3_3.11_randomize/build/randomize > copying randomize/__init__.py -> > /<>/.pybuild/cpython3_3.11_randomize/build/randomize > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_randomize/build/randomize > copying randomize/plugin.py -> > /<>/.pybuild/cpython3_3.10_randomize/build/randomize > copying randomize/__init__.py -> > /<>/.pybuild/cpython3_3.10_randomize/build/randomize >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.11_randomize/build; python3.11 -m nose > -v tests > runTest (tests.test_randomize.TestRandomizePlugin.runTest) ... FAIL > runTest (tests.test_randomize.TestRandomizePluginLooseTestFunctions.runTest) > ... ok > runTest (tests.test_randomize.TestRandomizePluginMultipleTestClasses.runTest) > ... SKIP: Skipping test until the classes can be shuffled > runTest (tests.test_randomize.TestRandomizePluginNoTUnitTestBased.runTest) > ... ok > runTest (tests.test_randomize.TestRandomizePluginNoTestFunctions.runTest) ... > ok > > == > FAIL: runTest (tests.test_randomize.TestRandomizePlugin.runTest) > -- > Traceback (most recent call last): > File > "/<>/.pybuild/cpython3_3.11_randomize/build/tests/test_randomize.py", > line 37, in runTest > self.assertEqual(line.strip(), expect.pop(0)) > AssertionError: 'test_C (fixtures.Tests.test_C) ... ok' != 'test_C > (fixtures.Tests) ... ok' > - test_C (fixtures.Tests.test_C) ... ok > ? --- > + test_C (fixtures.Tests) ... ok > > >> begin captured stdout << - > Using 2531 as seed > test_C (fixtures.Tests.test_C) ... ok > test_B (fixtures.Tests.test_B) ... ok > test_A (fixtures.Tests.test_A) ... ok > test_D (fixtures.Tests.test_D) ... ok > > -- > Ran 4 tests in 0.002s > > OK > > > - >> end captured stdout << -- > > -- > Ran 5 tests in 0.070s > > FAILED (SKIP=1, failures=1) > E: pybuild pybuild:386: test: plugin distutils failed with: exit code=1: cd > /<>/.pybuild/cpython3_3.11_randomize/build; python3.11 -m nose > -v tests > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.10_randomize/build; python3.10 -m nose > -v tests > runTest (tests.test_randomize.TestRandomizePlugin) ... ok > runTest (tests.test_randomize.TestRandomizePluginLooseTestFunctions) ... ok > runTest (tests.test_randomize.TestRandomizePluginMultipleTestClasses) ... > SKIP: Skipping test until the classes can be shuffled > runTest (tests.test_randomize.TestRandomizePluginNoTUnitTestBased) ... ok > runTest (tests.test_randomize.TestRandomizePluginNoTestFunctions) ... ok > > -- > Ran 5 tests in 0.075s > > OK (SKIP=1) > dh_auto_test: e
Bug#1003648: marked as done (php-horde-ansel: (autopkgtest) needs update for php8.1: deprecation warnings on stderr)
Your message dated Sun, 25 Dec 2022 18:20:05 + with message-id and subject line Bug#1003648: fixed in php-horde-prefs 2.9.0-9 has caused the Debian Bug report #1003648, regarding php-horde-ansel: (autopkgtest) needs update for php8.1: deprecation warnings on stderr 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.) -- 1003648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-horde-ansel Version: 3.0.10+debian1-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Dear maintainer(s), We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-horde-ansel fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-horde-anselfrom testing3.0.10+debian1-2 versioned deps from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. The test itself passes, but the autopkgtest fails because of deprecation warnings on stderr. Output on stderr makes autopkgtest fail by default, unless `allow-stderr` is added to the set of restrictions. As a flood of deprecation warnings in server logs my be very unwanted, I'm not saying that adding the restriction to autopkgtest is the right answer to this issue, but because of the php8.1 transition, it needs to be resolved one way or the other. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-ansel/18254587/log.gz PHPUnit 9.5.11 by Sebastian Bergmann and contributors. Runtime: PHP 8.1.1 Configuration: /tmp/autopkgtest-lxc.d6lnqxiq/downtmp/build.0rr/src/ansel-3.0.10/test/Ansel/phpunit.xml Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.d6lnqxiq/downtmp/build.0rr/src/ansel-3.0.10/test/Ansel/Unit/ImageTest.php Class name was 'Ansel_Unit_ImageTest', expected 'ImageTest' PHP Deprecated: Return type of Horde_Support_Stub::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 111 PHP Deprecated: Return type of Horde_Support_Stub::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 98 PHP Deprecated: Return type of Horde_Support_Stub::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 105 PHP Deprecated: Return type of Horde_Support_Stub::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 118 PHP Deprecated: Return type of Horde_Support_Stub::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 126 PHP Deprecated: Return type of Horde_Support_Stub::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 135 PHP Deprecated: Return type of Horde_Pref
Processed: notfixed 1020851 in 0.1.4-1, found 1026312 in 0.64.1-1.1, tagging 1025529
Processing commands for cont...@bugs.debian.org:
> notfixed 1020851 0.1.4-1
Bug #1020851 {Done: Sean Whitton } [elpa-ement]
elpa-ement: fails to install along emacs
No longer marked as fixed in versions 0.1.4-1.
> found 1026312 0.64.1-1.1
Bug #1026312 [src:meson] Setuptools 65.5.0-1.1 breaks installing Python
modules/extensions via meson
Marked as found in versions meson/0.64.1-1.1.
> tags 1025529 + experimental
Bug #1025529 [src:llvm-toolchain-14] llvm-toolchain-14: FTBFS with grpc 1.51+
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020851
1025529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025529
1026312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026655: marked as done (python-oslo.i18n: FTBFS: testtools.matchers._impl.MismatchError: 1 != 2)
Your message dated Sun, 25 Dec 2022 18:04:22 + with message-id and subject line Bug#1026655: fixed in python-oslo.i18n 5.1.0-3 has caused the Debian Bug report #1026655, regarding python-oslo.i18n: FTBFS: testtools.matchers._impl.MismatchError: 1 != 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.) -- 1026655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-oslo.i18n Version: 5.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_test --no-py2 'oslo_i18n\.tests.*' > + PKGOS_TEST_PARALLEL=yes > + PKGOS_TEST_SERIAL=no > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + TEST_SERIAL_OPT= > + echo WARNING: --no-py2 is deprecated, and always on. > WARNING: --no-py2 is deprecated, and always on. > + shift > + py3versions -vr > + PYTHON3S=3.11 3.10 > + [ yes = no ] > + [ no = yes ] > + [ 3.11 = disabled ] > + echo 3.11 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python (python3) > ===> Testing with python (python3) > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + [ -x /usr/bin/python3-stestr ] > + STESTR=stestr > + rm -rf .stestr > + PYTHON=python3.11 stestr run --parallel+ --subunit oslo_i18n\.tests.* > subunit2pyunit > INFO [localehander_logger] A message to be logged > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message > ... ok > INFO [localehander_logger] A message to be logged Arg to be logged > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message_with_args > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message_with_args > ... ok > INFO [localehander_logger] A message to be logged Arg1 to be logged > $(arg2)s > oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_default > oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_default ... ok > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message_with_named_args > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_emit_translated_message_with_named_args > ... ok > oslo_i18n.tests.test_gettextutils.GettextTest.test__gettextutils_install > oslo_i18n.tests.test_gettextutils.GettextTest.test__gettextutils_install ... > ok > oslo_i18n.tests.test_gettextutils.GettextTest.test_cached_find > oslo_i18n.tests.test_gettextutils.GettextTest.test_cached_find ... ok > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_set_formatter > oslo_i18n.tests.test_handler.TranslationHandlerTestCase.test_set_formatter > ... ok > oslo_i18n.tests.test_public_api.PublicAPITest.test_create_factory > oslo_i18n.tests.test_public_api.PublicAPITest.test_create_factory ... ok > oslo_i18n.tests.test_gettextutils.GettextTest.test_get_available_languages > oslo_i18n.tests.test_gettextutils.GettextTest.test_get_available_languages > ... ok > oslo_i18n.tests.test_gettextutils.GettextTest.test_gettext_does_not_blow_up > oslo_i18n.tests.test_gettextutils.GettextTest.test_gettext_does_not_blow_up > ... ok > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_change_lazy > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_change_lazy ... ok > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_lazy > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_lazy ... ok > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_log_level_domain_name > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_log_level_domain_name > ... ok > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_not_lazy > oslo_i18n.tests.test_factory.TranslatorFactoryTest.test_not_lazy ... ok > oslo_i18n.tests.test_message.MessageTestCase.test_add_disabled > oslo_i18n.tests.test_message.MessageTestCase.test_add_disabled ... ok > oslo_i18n.tests.test_locale_dir_variable.LocaleDirVariableTest.test_make_variable_name(simple) > oslo_i18n.tests.test_locale_dir_variable.LocaleDirVariableTest.test_make_variable_name(simple) > ... ok > oslo_i18n.tests.test_locale_dir_variable.LocaleDirVariableTest.test_make
Bug#1026521: marked as pending in python-randomize
Control: tag -1 pending Hello, Bug #1026521 in python-randomize 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/python/python-randomize/-/commit/a1dd1e30ac2cf4aa6bcd9b4298a98d6a3569e22e Fixed unit testing with Python 3.11 (Closes: #1026521). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026521
Processed: Bug#1026521 marked as pending in python-randomize
Processing control commands: > tag -1 pending Bug #1026521 [src:python-randomize] python-randomize: FTBFS: AssertionError: 'test_C (fixtures.Tests.test_C) ... ok' != 'test_C (fixtures.Tests) ... ok' Added tag(s) pending. -- 1026521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1026655 marked as pending in python-oslo.i18n
Processing control commands: > tag -1 pending Bug #1026655 [src:python-oslo.i18n] python-oslo.i18n: FTBFS: testtools.matchers._impl.MismatchError: 1 != 2 Added tag(s) pending. -- 1026655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026655: marked as pending in python-oslo.i18n
Control: tag -1 pending Hello, Bug #1026655 in python-oslo.i18n 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/oslo/python-oslo.i18n/-/commit/fa787ad4fd59850ef75de26ba5604f34252d5ac6 Blacklist test_translate_message_bad_translation() (Closes: #1026655). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026655
Bug#1026487: libvigraimpex: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
On 2022-12-20 Lucas Nussbaum wrote: > Source: libvigraimpex > Version: 1.11.1+dfsg-10 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > Hi, > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > executing test file > > /<>/obj.x86_64-linux-gnu/vigranumpy/test/test_arraytypes.py > > .EEE.EE. [...] > > ERROR: test_arraytypes.testImage1 > > -- > > Traceback (most recent call last): > > File > > "/<>/obj.x86_64-linux-gnu/vigranumpy/vigra/arraytypes.py", > > line 1271, in __getitem__ > > res = numpy.ndarray.__getitem__(self, index) > > IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis > > (`None`) and integer or boolean arrays are valid indices > > > > During handling of the above exception, another exception occurred: [...] This is caused/triggered by the recent numpy upgrade from 1:1.21.5-2 to 1:1.23.5-2. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1026159: okular: Bogus memory allocation size error - some pages not displayed
Hi, I am not the package's maintainer and maybe I am not so much into the topic, but this bug report is barely understandable: what is being reported? Is this package failing to build from source? How is it being built? What's the error message? Or is this about okular failing to display some pages of a specific PDF document? On which okular version? Does this deserve a serious severity? If you are facing two issues, please file two separate bug reports... Kind regards Marco
Bug#1025111: marked as done (python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed)
Your message dated Sun, 25 Dec 2022 17:08:19 +
with message-id
and subject line Bug#1025111: fixed in python-omegaconf 2.2.2-2.1
has caused the Debian Bug report #1025111,
regarding python-omegaconf: (autopkgtest) needs update for python3.11: mutable
default for field params is not allowed
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.)
--
1025111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-omegaconf
Version: 2.2.2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-omegaconf fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-omegaconf from testing2.2.2-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-omegaconf/28750377/log.gz
+
PYTHONPATH=/tmp/autopkgtest-lxc.4vq75_au/downtmp/build.XHu/src/debian/tmp/usr/lib/python3/dist-packages
http_proxy=127.0.0.1:9 https_proxy=127.0.0.9:9 HTTP_PROXY=127.0.0.1:9
HTTPS_PROXY=127.0.0.1:9 PYTHON=python3.11 python3.11 -m pytest tests -v
ImportError while loading conftest
'/tmp/autopkgtest-lxc.4vq75_au/downtmp/build.XHu/src/tests/conftest.py'.
tests/__init__.py:96: in
@dataclass
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
/usr/lib/python3.11/dataclasses.py:815: in _get_field
raise ValueError(f'mutable default {type(f.default)} for field '
E ValueError: mutable default 'tests.ConcretePlugin.FoobarParams'> for field params is not allowed:
use default_factory
autopkgtest [23:15:46]: test unittests
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-omegaconf
Source-Version: 2.2.2-2.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-omegaconf, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-omegaconf
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: Sun, 25 Dec 2022 12:42:17 -0400
Source: python-omegaconf
Architecture: source
Version: 2.2.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Stefano Rivera
Closes: 1025111
Changes:
python-omegaconf (2.2.2-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Patch: Support Python 3.11. (Closes: #1025111)
Checksums-Sha1:
880ad619541bf6c67c1abc01d39e1afa11414fbe 1710 python-omegaconf_2.2.2-2.1.dsc
c40322903380f68e8245bbe5c919d750a53e36ad 9028
python-omegaconf_2.2.2-2.1.debian.tar.xz
8502eeaf6d81d799a9e5eedda0d95d2f2b9ba4a4 6282
python-omegaconf_2.2.2-2.1_source.buildinfo
Checksums-Sha256:
869a536abcd54b1152dfa04dbc0ace0bd231165f5025158cc475270aadf05bc5 1710
pyth
Bug#1025107: marked as done (python-limits: (autopkgtest) needs update for python3.11: AssertionError)
Your message dated Sun, 25 Dec 2022 17:08:08 + with message-id and subject line Bug#1025107: fixed in python-limits 2.8.0-1 has caused the Debian Bug report #1025107, regarding python-limits: (autopkgtest) needs update for python3.11: AssertionError 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.) -- 1025107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-limits Version: 2.7.0-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-limits fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-limits from testing2.7.0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-limits/28750372/log.gz Traceback (most recent call last): File "/tmp/autopkgtest-lxc.mnkehych/downtmp/autopkgtest_tmp/memcached_storage.py", line 12, in assert True == fixed_window.hit(one_per_second, "test_namespace", "foo") AssertionError autopkgtest [23:14:41]: test python3-tests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-limits Source-Version: 2.8.0-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-limits, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-limits 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: Sun, 25 Dec 2022 12:28:08 -0400 Source: python-limits Architecture: source Version: 2.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1025107 Changes: python-limits (2.8.0-1) unstable; urgency=medium . * Team upload. * New upstream release. * Refresh patches. * Build-Depend on python3-typing-extensions. * Echo the python version being tested in python3-tests. * Flush memcached storage between Python versions in python3-tests. (Closes: #1025107) * Update copyright. * Declare Rules-Requires-Root: no. Checksums-Sha1: 9eb2557cd334a6de741200edd57b895c6514b298 1960 python-limits_2.8.0-1.dsc 3c64c4def3f90f7780297039bc6a5211bbf82e30 92364 python-limits_2.8.0.orig.tar.gz 75658db7da82fb1c5c91fbebb8a7b2a98eaa6e58 6048 python-limits_2.8.0-1.debian.tar.xz 9101476750f364614ec7cb09bdf3b6bef4c65e03 7782 python-limits_2.8.0-1_source.buildinfo Checksums-Sha256: e0d5aa60969b976bccc6158cebcb430ebf604d8efd5cdeb602a2669d77be76b6 1960 python-limits_2.8.0-1.dsc b60df1d2e9fda55067a9183f529bd275df650901d18cfaa2d7b1f69bc2c254bc 92364 python-limits_2.8.0.orig.tar.gz 7a155f38ba40763bac067bfd91aa5522813ddcb1ed10d261e013de0559ca2055 6048 python-limits_2.8.0-1.debian.tar.xz 080a410e2aab8e117a6b987361c85e59e430936b15047590e97f895ac8ad6c55 7782 python-limits_2.8.0-1_source.buildinfo Files: aed77814f81b60461a570f3056571f3c 1960 python optional python-limits_2.8.0-1.dsc 0cb7268c3764c7a924f1a62acf5474b3 92364 pytho
Bug#1005435: marked as done (gpr: FTBFS: configure: error: Must have libppd installed to compile gpr)
Your message dated Sun, 25 Dec 2022 17:07:45 + with message-id and subject line Bug#1005435: fixed in libppd 2:0.10-9 has caused the Debian Bug report #1005435, regarding gpr: FTBFS: configure: error: Must have libppd installed to compile gpr 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.) -- 1005435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpr Version: 0.15deb-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for unistd.h... yes > checking ppd.h usability... yes > checking ppd.h presence... yes > checking for ppd.h... yes > checking for ppd_file_new in -lppd... no > configure: error: Must have libppd installed to compile gpr The full build log is available from: http://qa-logs.debian.net/2022/02/12/gpr_0.15deb-2_unstable.log 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 marking 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: libppd Source-Version: 2:0.10-9 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of libppd, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated libppd 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: Sun, 25 Dec 2022 16:54:57 +0100 Source: libppd Architecture: source Version: 2:0.10-9 Distribution: unstable Urgency: medium Maintainer: Christoph Biedl Changed-By: Christoph Biedl Closes: 1005435 Changes: libppd (2:0.10-9) unstable; urgency=medium . * autoconf: Probe for glib-2.0 in order to create proper symbols. Closes: #1005435 Checksums-Sha1: 8ad041bb960240d4613a0a048af798ec32d3e6f9 1865 libppd_0.10-9.dsc 9c84722614205ea352925917416798718dbc60a4 9228 libppd_0.10-9.debian.tar.xz a44c4118b2080d7ee2713d0f1814fc39212d7577 7877 libppd_0.10-9_armel.buildinfo Checksums-Sha256: 2285ce12a86d20e6ae2d55916df15075e40599ccf142049786a9fe71d11576ec 1865 libppd_0.10-9.dsc ff03b59c9131769edd36ba7344079764a6c1b797a1a0b6c62ababdc7febd3831 9228 libppd_0.10-9.debian.tar.xz a44ed8b60309c7c8066f0367eec926eab7b82805663517fcaac361b2f7d6b6b6 7877 libppd_0.10-9_armel.buildinfo Files: 936a2ba49e57d6956e28041e08abbe94 1865 libs optional libppd_0.10-9.dsc 3f85029cfddbbe4780f2f73026ad8fff 9228 libs optional libppd_0.10-9.debian.tar.xz cfc9caf1ca3286db776191aec4953014 7877 libs optional libppd_0.10-9_armel.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmOoe6EACgkQxCxY61kU kv0v+g/5ARO1H8UDTSn75e7hwVZ/f0yrHgVRS3yjAgdJBnNECrq0SH5DWcj6yJJP rRlV2b2wE7YLTvs7vgfJwZzXvUyH0rHXQ8U4fFZ+6pPFeKXDK7xMvnz1PjxIuQ8L TugwpdUMUpvNHdehm/8ZJOzGvi7yMgJ+jLOW+gKGNalWlhgtdE9bN7UDwJ0fh1VP VdVaw+2BFUDEnqgyH9gP1PpqaPVgBf9XDm6oyncydPBthBubtBn5Zhv/CsFGaocE QYHJVKJzR1/EgSBXM/2QUrmnr90lDrTvyQXtE5GtibUkx3ki/fQW7xo8PQuqla+v Xoc8K7WSI76ucGEkkgtrRUlCIfIM5xyKmPlapqlrEfAuY5AeY841xhabIG2tOmj0 Bxpep79rzXjyArhZp97g34PjdlRB32UXqZU+dQGQHU4A+q6ZeYLio8cK9zpB2Lcf ebH9MDOClhC3xT8oD+4WOKeqpe6CZZKm1IQJXmFBv6aBz1cBHHR07pdjn+Pz3pem cAjpjQTgfvkfrhdHo2p2c4ozY6dLBExMFh2OpOSzIj4ftCASdluJYONIneANKyEC cvAKwjYL6ZHnwtjjS62Fc5edvPXOlNkwDVtf3kL3XMPaTIWHoX4p8fP29yhjvSwM 8E4pTi+FAf9tCFxVsE7Xoi4PlQw7u1iBWFNn7TtNTT7/lLGONbA= =7B5/ -END PGP SIGNATURE End Message ---
Bug#1025111: python-omegaconf: diff for NMU version 2.2.2-2.1
Control: tags 1025111 + patch
Dear maintainer,
I've prepared an NMU for python-omegaconf (versioned as 2.2.2-2.1). The diff
is attached to this message.
Regards.
SR
diff -Nru python-omegaconf-2.2.2/debian/changelog python-omegaconf-2.2.2/debian/changelog
--- python-omegaconf-2.2.2/debian/changelog 2022-10-26 06:24:04.0 -0400
+++ python-omegaconf-2.2.2/debian/changelog 2022-12-25 12:42:17.0 -0400
@@ -1,3 +1,10 @@
+python-omegaconf (2.2.2-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch: Support Python 3.11. (Closes: #1025111)
+
+ -- Stefano Rivera Sun, 25 Dec 2022 12:42:17 -0400
+
python-omegaconf (2.2.2-2) unstable; urgency=medium
* Fixed VCS URLs (Closes: #1016890).
diff -Nru python-omegaconf-2.2.2/debian/patches/python-3.11.patch python-omegaconf-2.2.2/debian/patches/python-3.11.patch
--- python-omegaconf-2.2.2/debian/patches/python-3.11.patch 1969-12-31 20:00:00.0 -0400
+++ python-omegaconf-2.2.2/debian/patches/python-3.11.patch 2022-12-25 12:41:57.0 -0400
@@ -0,0 +1,1184 @@
+Description:
+ This PR updates OmegaConf's tests and metadata for compatibility with python3.11.
+ .
+ There are no changes to the omegaconf source code.
+ .
+ The changes to the test are motivated by python3.11 dataclasses dropping
+ support for mutable default arguments. This means dataclasses with mutable
+ default arguments must use default_factory.
+ .
+ I've updated the dataclasses in the test suite to use default_factory, and
+ I've added a file tests/structured_conf/dataclasses_pre_311.py that contains
+ old-style dataclasses that do not use default_factory for mutable dataclass
+ defaults. This pre_311 file is run only when python version < 3.10.
+ .
+ Commits:
+ tests/structured_config module fixture: use pytest.param
+ test dataclass with mutable default: skip if python>=3.11
+ tests/structured_conf: default_factory for mutable dataclass args
+ python3.11: add news fragment & update metadata
+ python3.11: update docs
+
+Author: Jasha <8935917+jash...@users.noreply.github.com>
+Origin: upstream, https://github.com/omry/omegaconf/pull/1032
+Bug-Debian: https://bugs.debian.org/1025111
+
+--- a/tests/structured_conf/test_structured_basic.py
b/tests/structured_conf/test_structured_basic.py
+@@ -1,8 +1,9 @@
+ import re
++import sys
+ from importlib import import_module
+ from typing import Any, Optional
+
+-from pytest import fixture, mark, raises
++from pytest import fixture, mark, param, raises
+
+ from omegaconf import (
+ DictConfig,
+@@ -20,10 +21,17 @@
+
+ @fixture(
+ params=[
+-"tests.structured_conf.data.dataclasses",
+-"tests.structured_conf.data.attr_classes",
++param("tests.structured_conf.data.dataclasses", id="dataclasses"),
++param(
++"tests.structured_conf.data.dataclasses_pre_311",
++id="dataclasses_pre_311",
++marks=mark.skipif(
++sys.version_info >= (3, 11),
++reason="python >= 3.11 does not support mutable default dataclass arguments",
++),
++),
++param("tests.structured_conf.data.attr_classes", id="attr_classes"),
+ ],
+-ids=["dataclasses", "attr_classes"],
+ )
+ def module(request: Any) -> Any:
+ return import_module(request.param)
+--- a/tests/structured_conf/test_structured_config.py
b/tests/structured_conf/test_structured_config.py
+@@ -29,10 +29,17 @@
+
+ @fixture(
+ params=[
+-"tests.structured_conf.data.dataclasses",
+-"tests.structured_conf.data.attr_classes",
++param("tests.structured_conf.data.dataclasses", id="dataclasses"),
++param(
++"tests.structured_conf.data.dataclasses_pre_311",
++id="dataclasses_pre_311",
++marks=mark.skipif(
++sys.version_info >= (3, 11),
++reason="python >= 3.11 does not support mutable default dataclass arguments",
++),
++),
++param("tests.structured_conf.data.attr_classes", id="attr_classes"),
+ ],
+-ids=["dataclasses", "attr_classes"],
+ )
+ def module(request: Any) -> Any:
+ return import_module(request.param)
+--- /dev/null
b/tests/structured_conf/data/dataclasses_pre_311.py
+@@ -0,0 +1,879 @@
++import dataclasses
++import sys
++from dataclasses import dataclass, field
++from pathlib import Path
++from typing import Any, Dict, List, Optional, Tuple, Union
++
++from pytest import importorskip
++
++from omegaconf import II, MISSING, SI
++from tests import Color, Enum1
++
++if sys.version_info >= (3, 8): # pragma: no cover
++from typing import TypedDict
++
++# skip test if dataclasses are not available
++importorskip("dataclasses")
++
++
++class NotStructuredConfig:
++name: str = "Bond"
++age: int = 7
++
++def __eq__(self, other: Any) -> Any:
++if isinstance(other, type(self)):
++return self.name == other.name and self.age == other.age
++return
Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs
On Sun, 7 Feb 2021 20:32:08 -0800 Felix Lechner wrote: > Hi Chris, > > On Sun, Feb 7, 2021 at 9:22 AM Chris Hofstaedtler wrote: > > > > friendly ping here, are you planning to fix this for bullseye? > > Thanks for the reminder! I will probably include efivars in the next > couple of days. > > Kind regards > Felix > You probably want to include efivarfs (efivars is obsolete and removed in linux kernel 6). Thus the current patch has no effect on bullseye- backports, testing and up. efivarfs is available since linux 3.10. So maybe including efivarfs only is a better option (since with efivars being removed I get a warning at boot from initramfs that it cannot load unavailable efivars module. Cheers, Alban
Processed: python-omegaconf: diff for NMU version 2.2.2-2.1
Processing control commands: > tags 1025111 + patch Bug #1025111 [src:python-omegaconf] python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed Added tag(s) patch. -- 1025111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1025111
Processing commands for cont...@bugs.debian.org: > #in 2.3.0 > tags 1025111 + fixed-upstream Bug #1025111 [src:python-omegaconf] python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013933: Keep xsane out of Debian releases
On Thu, 8 Dec 2022 17:29:53 + (UTC) Alexis PM wrote: > Please consider reducing the severity of the bug to allow the inclusion of xsane in the next stable release. > > xsane has no equivalent software available. Its GUI allows you to use advanced features of SANE not available graphically in other GUIs. > > xsane is usable in the currently packaged version (removed in testing due to this bug). It does not have any bug that prevent me from using it on a daily basis. > > At https://popcon.debian.org/by_inst xsane is ranked 2346, by comparison sane is ranked 7457. > > Its development is low in the last years, the last commit is from 6 months ago ( https://gitlab.com/sane-project/frontend/xsane ), but this is not a reason to remove a software that is useful, usable, popular and no equivalent available. > > Thank you very much. > > I agree. As long as there are no alternative, please keep xsane in the bookworm release. While the GUI has it's flaws it does NOT render the entire package unusable so removing it (when no alternative exist) is a bit drastic. -- - Regards Svein Engelsgjerd
Bug#1025107: marked as pending in python-limits
Control: tag -1 pending Hello, Bug #1025107 in python-limits 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-limits/-/commit/45af8aedb841c17c638942f9fff0e0c9e052b37a Flush memcached storage between Python versions in python3-tests. (Closes: #1025107) (this message was generated automatically) -- Greetings https://bugs.debian.org/1025107
Processed: Bug#1025107 marked as pending in python-limits
Processing control commands: > tag -1 pending Bug #1025107 [src:python-limits] python-limits: (autopkgtest) needs update for python3.11: AssertionError Added tag(s) pending. -- 1025107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1005435: gpr: FTBFS: configure: error: Must have libppd installed to compile gpr
Processing control commands: > tags 1005435 pending Bug #1005435 [src:gpr] gpr: FTBFS: configure: error: Must have libppd installed to compile gpr Added tag(s) pending. -- 1005435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005435: gpr: FTBFS: configure: error: Must have libppd installed to compile gpr
Control: tags 1005435 pending Lucas Nussbaum wrote... > Source: gpr > Version: 0.15deb-2 > Severity: serious > Justification: FTBFS > > configure: error: Must have libppd installed to compile gpr This was caused by yours truly as a result of updating src:libppd almost a year ago. Fix is underway. Christoph signature.asc Description: PGP signature
Bug#1026894: marked as done (ruby-haml-rails: FTBFS: unsatisfiable build-dependency: ruby-haml (< 6.0) but 6.1.1-1 is to be installed)
Your message dated Sun, 25 Dec 2022 15:20:42 + with message-id and subject line Bug#1026894: fixed in ruby-haml-rails 2.1.0-1 has caused the Debian Bug report #1026894, regarding ruby-haml-rails: FTBFS: unsatisfiable build-dependency: ruby-haml (< 6.0) but 6.1.1-1 is to be installed 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.) -- 1026894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-haml-rails Version: 2.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable build dependencies. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, > ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= > 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, > ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= > 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, > 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 [580 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [776 B] > Get:5 copy:/<>/apt_archive ./ Packages [808 B] > Fetched 2164 B in 0s (0 B/s) > Reading package lists... > Get:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease > Ign:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease > Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B] > Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B] > Get:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg > Ign:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: ruby-haml (< 6.0) but 6.1.1-1 is > to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-haml-rails Source-Version: 2.1.0-1 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of ruby-haml-rails, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated ruby-haml-rails 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: Sun, 25 Dec 2022 11:58:29 -0300 Source: ruby-haml-rails Architecture: source Version: 2.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 1026894 Changes: ruby-haml-rails (2.1.0-1) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Set field Upstream-Contact in debian/copyright. * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright). * Update standards version to 4.5.0,
Processed: bug 1026980 is forwarded to https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html
Processing commands for cont...@bugs.debian.org: > forwarded 1026980 > https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html Bug #1026980 [src:pyqt5] pyqt5: FTBFS on mipsel (MemoryError) Ignoring request to change the forwarded-to-address of bug#1026980 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 1026980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026980: pyqt5: FTBFS on mipsel (MemoryError)
Control: forwarded -1 https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html Hi Bas! On Sun, Dec 25, 2022 at 03:57:22PM +0100, Bas Couwenberg wrote: > Source: pyqt5 > Version: 5.15.7+dfsg-2 > Severity: serious > Tags: upstream ftbfs > Control: block 1025863 by -1 > > Dear Maintainer, > > Your package FTBFS on mipsel, even on buildds where it built successfully > before, during the qtbase-opensource-src transition: > > Generating the _QOpenGLFunctions_2_0 bindings... > sip-build: An internal error occurred... > [...] > MemoryError I have contacted upstream about this, but I do not expect quick reply because of the holidays. I noticed that code generation with Python 3.11 succeeded, and failed only with Python 3.10. My hypothesis is that it happened because we do not generate .pyi files with non-default Python versions. I will try to disable .pyi generation completely and see if the package builds on a porterbox. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#1026980: pyqt5: FTBFS on mipsel (MemoryError)
Processing control commands: > forwarded -1 > https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html Bug #1026980 [src:pyqt5] pyqt5: FTBFS on mipsel (MemoryError) Set Bug forwarded-to-address to 'https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html'. -- 1026980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025023: marked as done (python-boltons: (autopkgtest) needs update for python3.11: new through_method __getstate__?)
Your message dated Sun, 25 Dec 2022 15:05:11 + with message-id and subject line Bug#1025023: fixed in python-boltons 21.0.0-2 has caused the Debian Bug report #1025023, regarding python-boltons: (autopkgtest) needs update for python3.11: new through_method __getstate__? 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.) -- 1025023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-boltons Version: 21.0.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-boltons fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-boltons from testing21.0.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-boltons/28728882/log.gz === FAILURES === _ test_frozendict_api __ def test_frozendict_api(): # all the read-only methods that are fine through_methods = ['__class__', '__cmp__', '__contains__', '__delattr__', '__dir__', '__eq__', '__format__', '__ge__', '__getattribute__', '__getitem__', '__gt__', '__init__', '__iter__', '__le__', '__len__', '__lt__', '__ne__', '__new__', '__or__', '__reduce__', '__reversed__', '__ror__', '__setattr__', '__sizeof__', '__str__', 'copy', 'get', 'has_key', 'items', 'iteritems', 'iterkeys', 'itervalues', 'keys', 'values', 'viewitems', 'viewkeys', 'viewvalues'] fd = FrozenDict() ret = [] for attrname in dir(fd): if attrname == '_hash': # in the dir, even before it's set continue attr = getattr(fd, attrname) if not callable(attr): continue if getattr(FrozenDict, attrname) == getattr(dict, attrname, None) and attrname not in through_methods: assert attrname == False E AssertionError: assert '__getstate__' == False tests/test_dictutils.py:515: AssertionError === short test summary info FAILED tests/test_dictutils.py::test_frozendict_api - AssertionError: assert ... 1 failed, 389 passed in 2.32s = autopkgtest [23:01:36]: test upstream OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-boltons Source-Version: 21.0.0-2 Done: Stefano Rivera We believe that the bug you
Processed: pyqt5: FTBFS on mipsel (MemoryError)
Processing control commands: > block 1025863 by -1 Bug #1025863 [release.debian.org] transition: qtbase-opensource-src 1025863 was not blocked by any bugs. 1025863 was blocking: 1026254 Added blocking bug(s) of 1025863: 1026980 -- 1025863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025863 1026980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026980: pyqt5: FTBFS on mipsel (MemoryError)
Source: pyqt5
Version: 5.15.7+dfsg-2
Severity: serious
Tags: upstream ftbfs
Control: block 1025863 by -1
Dear Maintainer,
Your package FTBFS on mipsel, even on buildds where it built successfully
before, during the qtbase-opensource-src transition:
Generating the _QOpenGLFunctions_2_0 bindings...
sip-build: An internal error occurred...
Traceback (most recent call last):
File "/usr/bin/sip-build", line 33, in
sys.exit(load_entry_point('sip==6.7.5', 'console_scripts', 'sip-build')())
File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 37, in
main
handle_exception(e)
File "/usr/lib/python3/dist-packages/sipbuild/exceptions.py", line 81, in
handle_exception
raise e
File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 34, in
main
project.build()
File "/usr/lib/python3/dist-packages/sipbuild/project.py", line 244, in build
self.builder.build()
File "/usr/lib/python3/dist-packages/sipbuild/builder.py", line 48, in build
self._generate_bindings()
File "/usr/lib/python3/dist-packages/sipbuild/builder.py", line 277, in
_generate_bindings
buildable = bindings.generate()
File "/usr/lib/python3/dist-packages/sipbuild/bindings.py", line 166, in
generate
spec, sip_files = parse(self.sip_file, SIP_VERSION, encoding,
File "/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser.py",
line 36, in parse
protected_is_public, include_dirs, sip_module, is_strict).parse(
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 1505, in parse
self._parser.parse(self._read(sip_file, raw_sip_file),
File "/usr/lib/python3/dist-packages/ply/yacc.py", line 331, in parse
return self.parseopt(input, lexer, debug, tracking, tokenfunc)
File "/usr/lib/python3/dist-packages/ply/yacc.py", line 823, in parseopt
p.callable(pslice)
File "/usr/lib/python3/dist-packages/sipbuild/generator/parser/rules.py",
line 765, in p_include_simple
pm.push_file(p, 1)
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 1685, in push_file
self._lexer.input(self._read(sip_file, raw_sip_file))
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 2120, in _read
self._input = f.read()
File "/usr/lib/python3.10/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
MemoryError
https://buildd.debian.org/status/fetch.php?pkg=pyqt5&arch=mipsel&ver=5.15.7%2Bdfsg-2%2Bb1&stamp=1671914840&raw=0
Kind Regards,
Bas
Bug#1025106: marked as done (python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1))
Your message dated Sun, 25 Dec 2022 10:51:48 -0400
with message-id <20221225145148.bpzjekyciymxm...@haydn.kardiogramm.net>
and subject line Re: Bug#1025106: python-icecream: (autopkgtest) needs update
for python3.11: ValueError: not enough values to unpack (expected 2, got 1)
has caused the Debian Bug report #1025106,
regarding python-icecream: (autopkgtest) needs update for python3.11:
ValueError: not enough values to unpack (expected 2, got 1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1025106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-icecream
Version: 2.1.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-icecream fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-icecreamfrom testing2.1.3-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-icecream/28750371/log.gz
FFF.EE.EFEFFEEF.E.FF.FFFEFE
==
ERROR: testComments (tests.test_icecream.TestIceCream.testComments)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 291, in testComments
assert lineIsContextAndTime(err.getvalue())
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 115, in lineIsContextAndTime
context, time = line.split(' at ')
^
ValueError: not enough values to unpack (expected 2, got 1)
==
ERROR: testComplicated (tests.test_icecream.TestIceCream.testComplicated)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 308, in testComplicated
assert lineIsContextAndTime(err.getvalue().splitlines()[0])
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 115, in lineIsContextAndTime
context, time = line.split(' at ')
^
ValueError: not enough values to unpack (expected 2, got 1)
==
ERROR: testContextAbsPathMultiLine
(tests.test_icecream.TestIceCream.testContextAbsPathMultiLine)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 502, in testContextAbsPathMultiLine
assert lineIsAbsPathContext(firstLine)
^^^
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 142, in lineIsAbsPathContext
int(lineNumber) > 0 and
^^^
ValueError: invalid literal for int() with base 10: ' Failed to access
the underlying source code for analysis. Was ic() invoked'
==
ERROR: testDifferentName
(tests.test_icecream.TestIceCream.testDifferentName)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-l
Processed: Bug#1025023 marked as pending in python-boltons
Processing control commands: > tag -1 pending Bug #1025023 [src:python-boltons] python-boltons: (autopkgtest) needs update for python3.11: new through_method __getstate__? Added tag(s) pending. -- 1025023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025023: marked as pending in python-boltons
Control: tag -1 pending Hello, Bug #1025023 in python-boltons 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-boltons/-/commit/118228847c8175b4392c6a7a2f42e5ee51c7f02e Patch: Python 3.11 support. Closes: #1025023 (this message was generated automatically) -- Greetings https://bugs.debian.org/1025023
Bug#1026895: marked as done (ruby-html2haml: FTBFS with ruby-haml 6.1.1: ERROR: Test "ruby3.1" failed: Could not find 'haml' (>= 4.0, < 6) among 102 total gem(s) (Gem::MissingSpecError))
Your message dated Sun, 25 Dec 2022 14:37:08 + with message-id and subject line Bug#1026895: fixed in ruby-html2haml 2.3.0-1 has caused the Debian Bug report #1026895, regarding ruby-html2haml: FTBFS with ruby-haml 6.1.1: ERROR: Test "ruby3.1" failed: Could not find 'haml' (>= 4.0, < 6) among 102 total gem(s) (Gem::MissingSpecError) 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.) -- 1026895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-html2haml Version: 2.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block > in activate_dependencies': Could not find 'haml' (>= 4.0, < 6) among 102 > total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /<>/debian/ruby-html2haml/usr/share/rubygems-integration/all/specifications/html2haml-2.2.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'haml' (>= 4.0, < 6) - did find: [haml-6.1.1] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > base64 (default: 0.1.1) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (default: 2.3.7) > cgi (default: 0.3.1) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > did_you_mean (default: 1.6.1) > digest (default: 3.1.0) > drb (default: 2.1.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > erubis (2.7.0) > etc (default: 1.3.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > haml (6.1.1) > io-console (default: 0.5.11) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.1) > ipaddr (default: 1.2.4) > irb (default: 1.4.1) > json (default: 2.6.1) > logger (default: 1.5.0) > matrix (0.4.2) > mini_portile2 (2.8.0) > minitest (5.15.0) > mutex_m (default: 0.1.1) > net-ftp (0.1.3) > net-http (default: 0.2.0) > net-imap (0.2.3) > net-pop (0.1.1) > net-protocol (default: 0.1.2) > net-smtp (0.3.1) > net-telnet (0.1.1) > nkf (default: 0.1.1) > nokogiri (1.13.10) > observer (default: 0.1.1) > open-uri (default: 0.2.0) > open3 (default: 0.1.1) > openssl (default: 3.0.0) > optparse (default: 0.2.0) > ostruct (default: 0
Bug#1024915: marked as done (i3pystatus: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec')
Your message dated Sun, 25 Dec 2022 14:35:04 +
with message-id
and subject line Bug#1024915: fixed in i3pystatus 3.35+git20191126.5a8eaf4-2.1
has caused the Debian Bug report #1024915,
regarding i3pystatus: (autopkgtest) needs update for python3.11: module
'inspect' has no attribute 'getargspec'
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.)
--
1024915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: i3pystatus
Version: 3.35+git20191126.5a8eaf4-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
i3pystatus fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
i3pystatus from testing3.35+git20191126.5a8eaf4-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/i/i3pystatus/28726233/log.gz
=== FAILURES
===
CallbacksMetaTest.test_callback_set_post_instanciation
self = testMethod=test_callback_set_post_instanciation>
def test_callback_set_post_instanciation(self):
counter = self.NoDefaultCounter()
# set callbacks
counter.on_leftclick = "update_counter"
counter.on_rightclick = ["update_counter", 2]
counter.on_upscroll = [print, "i3 is", "awesome"]
counter.on_downscroll = ["update_counter", -1]
self.assertEqual(counter.counter, 0)
counter.on_click(1) # left_click
self.assertEqual(counter.counter, 1)
E AssertionError: 0 != 1
tests/test_callbacks.py:60: AssertionError
-- Captured log call
---
CRITICAL i3pystatus.test_callbacks.NoDefaultCounter:modules.py:174
Exception while processing button callback: AttributeError("module
'inspect' has no attribute 'ArgSpec'")
CRITICAL i3pystatus.test_callbacks.NoDefaultCounter:modules.py:176
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.x02ylk16/downtmp/build.9fM/src/i3pystatus/core/modules.py",
line 124, in call_callback
args_spec = inspect.getargspec(tmp_cb)
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.x02ylk16/downtmp/build.9fM/src/i3pystatus/core/modules.py",
line 162, in __button_callback_handler
call_callback(getattr(self, cb), *args, **kwargs)
File
"/tmp/autopkgtest-lxc.x02ylk16/downtmp/build.9fM/src/i3pystatus/core/modules.py",
line 126, in call_callback
args_spec = inspect.ArgSpec([], None, None, None)
^^^
AttributeError: module 'inspect' has no attribute 'ArgSpec'
test_clicks[events1-leftclick]
events = ((0.4, 1),), expected = 'leftclick'
@pytest.mark.parametrize("events, expected", [
# Fast click
(((0, left_click),),
'no action'),
# Slow click
(((0.4, left_click),),
'leftclick'),
# Slow double click
(((0.4, left_click),
(0.4, left_click),),
'leftclick'),
# Fast double click
(((0.2, left_click),
(0, left_click),),
'doubleleftclick'),
# Fast double click + Slow click
(((0.2, left_click),
(0, left_click),
(0.3, left_click),),
'leftclick'),
Bug#1025016: onedrivesdk: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
The upstream has declared the project deprecated, and there are no reverse-depends. Time to remove it from Debian? SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Processed: dpdk
Processing commands for cont...@bugs.debian.org: > close 1024354 22.11-1 Bug #1024354 [dpdk] DPDK: missing riscv64 build Marked as fixed in versions dpdk/22.11-1. Bug #1024354 [dpdk] DPDK: missing riscv64 build Marked Bug as done > close 1019589 Bug #1019589 [src:dpdk] dpdk: CVE-2022-28199 CVE-2022-2132 Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1019589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019589 1024354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: i3pystatus: diff for NMU version 3.35+git20191126.5a8eaf4-2.1
Processing control commands: > tags 1024915 + patch Bug #1024915 [src:i3pystatus] i3pystatus: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added tag(s) patch. -- 1024915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024915: i3pystatus: diff for NMU version 3.35+git20191126.5a8eaf4-2.1
Control: tags 1024915 + patch
Dear maintainer,
I've prepared an NMU for i3pystatus (versioned as
3.35+git20191126.5a8eaf4-2.1). The diff
is attached to this message.
Regards.
SR
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog 2019-11-27 12:39:56.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog 2022-12-25 09:33:18.0 -0400
@@ -1,3 +1,10 @@
+i3pystatus (3.35+git20191126.5a8eaf4-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add support for Python 3.11. (Closes: #1024915)
+
+ -- Stefano Rivera Sun, 25 Dec 2022 09:33:18 -0400
+
i3pystatus (3.35+git20191126.5a8eaf4-2) unstable; urgency=medium
[ EstebanB ]
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch 1969-12-31 20:00:00.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch 2022-12-25 09:33:09.0 -0400
@@ -0,0 +1,33 @@
+From 1a54a8332e9398f18c6c4f8258f4853f2cc53013 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera
+Date: Sun, 25 Dec 2022 09:26:31 -0400
+Subject: [PATCH] Migrate to inspect.getfullargspec()
+
+getargspec() was deprecated in 3.0 and removed in 3.11.
+
+Forwarded: https://github.com/enkore/i3pystatus/pull/844
+Bug-Debian: https://bugs.debian.org/1024915
+---
+ i3pystatus/core/modules.py | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+--- a/i3pystatus/core/modules.py
b/i3pystatus/core/modules.py
+@@ -121,13 +121,14 @@
+ tmp_cb = cb
+
+ try:
+-args_spec = inspect.getargspec(tmp_cb)
++args_spec = inspect.getfullargspec(tmp_cb)
+ except Exception:
+-args_spec = inspect.ArgSpec([], None, None, None)
++args_spec = inspect.FullArgSpec(
++[], None, None, None, None, None, {})
+
+ # Remove all variables present in kwargs that are not used in the
+ # callback, except if there is a keyword argument.
+-if not args_spec.keywords:
++if not args_spec.varkw:
+ kwargs = {k: v for k, v in kwargs.items()
+ if k in args_spec.args}
+ cb(*args, **kwargs)
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series 1969-12-31 20:00:00.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series 2022-12-25 09:32:32.0 -0400
@@ -0,0 +1 @@
+0001-Migrate-to-inspect.getfullargspec.patch
Processed: RC bug #1026562 forwarded to upstream fix
Processing commands for cont...@bugs.debian.org: > forwarded 1026562 https://github.com/coleifer/wtf-peewee/issues/55 Bug #1026562 [src:wtf-peewee] wtf-peewee: FTBFS: ImportError: cannot import name 'HTMLString' from 'wtforms.widgets' (/usr/lib/python3/dist-packages/wtforms/widgets/__init__.py) Set Bug forwarded-to-address to 'https://github.com/coleifer/wtf-peewee/issues/55'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025529: llvm-toolchain-14: FTBFS with grpc 1.51+
Le 06/12/2022 à 10:36, László Böszörményi (GCS) a écrit : Source: llvm-toolchain-14 Version: 1:14.0.6-9 Severity: important Usertags: grpc1_51 Tags: ftbfs bookworm sid Hi, I'm going to start the gRPC transition real soon. Your package FTBFS with it. Main reason is that during stage 2 build bin/clangd-index-server-monitor needs to link with -lgpr and -labsl_synchronization as well. Due to time constraints I can't (yet) provide you a drop-in patch - but the solution is provided above. Please look into it and be prepared to take core of it when time comes. thanks Do you know why libgrpc++.so doesn't reference them anymore? Thanks Sylvestre
Bug#1026937: marked as done (python3-grpcio: ImportError: undefined symbol: _ZN4absl7debian313hash_internal15MixingHashState5kSeedE)
Your message dated Sun, 25 Dec 2022 10:34:37 + with message-id and subject line Bug#1026937: fixed in grpc 1.51.1-3 has caused the Debian Bug report #1026937, regarding python3-grpcio: ImportError: undefined symbol: _ZN4absl7debian313hash_internal15MixingHashState5kSeedE 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.) -- 1026937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-grpcio Version: 1.51.1-2 Severity: serious The Python modules included in python3-grpcio are underlinked and cannot be imported: >>> import grpc Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/grpc/__init__.py", line 22, in from grpc import _compression File "/usr/lib/python3/dist-packages/grpc/_compression.py", line 20, in from grpc._cython import cygrpc ImportError: /usr/lib/python3/dist-packages/grpc/_cython/cygrpc.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN4absl7debian313hash_internal15MixingHashState5kSeedE This issue causes autopkgtest regressions for python-tooz. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: grpc Source-Version: 1.51.1-3 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of grpc, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated grpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Dec 2022 18:05:35 +0100 Source: grpc Architecture: source Version: 1.51.1-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1026937 Changes: grpc (1.51.1-3) unstable; urgency=medium . * Link Python gRPC module with all needed Abseil libraries (closes: #1026937). Checksums-Sha1: 381b24995403267dce1f5e9d1b9f0cddb5bc3138 2811 grpc_1.51.1-3.dsc 0f12774a0b22f18960f860eba0abd90d2e1704db 20704 grpc_1.51.1-3.debian.tar.xz Checksums-Sha256: b402e403c08b74110390391bd384704c8018db88e8ae5277dc8c864e060720a0 2811 grpc_1.51.1-3.dsc 767b69da166bae708a54c4740056d9e847d57d89885173016bfc57ebbf154b2d 20704 grpc_1.51.1-3.debian.tar.xz Files: 61d8bb0c1c56b3ea760a4e10a6b7d997 2811 libs optional grpc_1.51.1-3.dsc 39b2f8019473b404478f393b8fef4e6e 20704 libs optional grpc_1.51.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmOoI40ACgkQ3OMQ54ZM yL8gEg/8D70qtsYZtVvxqRfKgjgWZvpxE2Onm42HxkOnYlZ9VB3f7fypeDD0Rphm F7cfmMznu4YFCZl7wyesF3YSwaEjOi3ppr1aAKy3Ff/8IglnBcypCVR5OkEoHsPg VYYLJZ3PHBgCP3XXvm5cx+jPegU4ZQN0Em/yRu6hRmVza7zjhseMQRo8K/v8y2Rw 14A0abjDslDiDOFZpfQ8ao1UHH1YLRo56NmrvdD+VQzWx0IxtXvMQdSRe/Uh7hkP I+fdG4Et0S+ASId7EU3/9wgprlEXL7+3mdjRzDZ9o7yAIG4OX1TD4XewH3bIk7S5 3Egy9iQSJ3iFxAqHHtf5MOYNS/53TXnuIdYYFSWEA1odGE6I6uAf4yaEldP5LLgx apTwMFzbLJWqtOus4cyrBhuWBBYLnzfGLee0bn6YYfAMRiraqsgjPa8G02vuhWE2 oquBCE4AY6op4IPjw0Y4QG5P30tTo+gQp7VIRdPro77nduuvlzyzXeKuJIMd8Pvq PRVuSOFoj8aDU2py/7KsrXAItaMeBhOn3Fkn4Ms+yW7ggB1TVaz7AOcSJVuJYi+e TCnmpVukcwhdy3aVSHJUHREWbURQOFxuo4aW/Sm2i76smd8tdrzELJ54uF3eJDpp infnJKS2d7TLbbx8YIypC/7w2D9edfpeUC8Hl9x1aflq98YYwkI= =eG0U -END PGP SIGNATURE End Message ---
Processed: reopen 962844- efivars removed from kernel 6
Processing commands for cont...@bugs.debian.org:
> package mdadm
Limiting to bugs with field 'package' containing at least one of 'mdadm'
Limit currently set to 'package':'mdadm'
> unarchive 962844
Bug #962844 {Done: Felix Lechner } [mdadm] mdadm:
Assembling RAID using IMSM in initrd fails due to lack of module efivarfs
Unarchived Bug 962844
> reopen 962844
Bug #962844 {Done: Felix Lechner } [mdadm] mdadm:
Assembling RAID using IMSM in initrd fails due to lack of module efivarfs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mdadm/4.1-11.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
962844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1026535
Processing commands for cont...@bugs.debian.org:
> close 1026535
Bug #1026535 [src:ipykernel] ipykernel: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026535: closing 1026535
close 1026535 thanks I can't reproduce this, probably the same as #1024916 which was closed in the meantime.
