Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 1024157 1:7.4.2-3
Bug #1024157 {Done: Adrian Bunk } [src:libreoffice]
libreoffice/experimental FTBFS with dragonbox 1.1.3
Marked as found in versions libreoffice/1:7.4.2-3.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1024157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1022253: marked as done (swi-prolog breaks logol autopkgtest on s390x)
Your message dated Wed, 16 Nov 2022 12:33:22 +0500 with message-id <877czvical.fsf@localhost> and subject line Close #1022253 has caused the Debian Bug report #1022253, regarding swi-prolog breaks logol autopkgtest on s390x 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.) -- 1022253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swi-prolog, logol Control: found -1 swi-prolog/8.4.3+dfsg-2 Control: found -1 logol/1.7.9+dfsg-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of swi-prolog the autopkgtest of logol fails in testing when that autopkgtest is run with the binary packages of swi-prolog from unstable. It passes when run with only packages from testing. In tabular form: passfail swi-prolog from testing8.4.3+dfsg-2 logol from testing1.7.9+dfsg-5 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that the last changelog for swi-prolog mentions endianness, s390x is our only big endian release architecture. Currently this regression is blocking the migration of swi-prolog to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=swi-prolog https://ci.debian.net/data/autopkgtest/testing/s390x/l/logol/27384041/log.gz calling logol with parameters -g 1799.logol -s 1799.fasta -dna log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied) at java.base/java.io.FileOutputStream.open0(Native Method) at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298) at java.base/java.io.FileOutputStream.(FileOutputStream.java:237) at java.base/java.io.FileOutputStream.(FileOutputStream.java:158) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) at org.apache.log4j.LogManager.(LogManager.java:127) at org.apache.log4j.Logger.getLogger(Logger.java:117) at org.irisa.genouest.logol.Logol.(Unknown Source) For help, use option -h INFO org.irisa.genouest.logol.Logol - Using configuration file: /usr/share/logol/prolog/logol.properties INFO org.irisa.genouest.logol.Logol - option g called with 1799.logol INFO org.irisa.genouest.logol.Logol - option s called with 1799.fasta INFO org.irisa.genouest.logol.Logol - No maximum solutions defined, using defaults INFO org.irisa.genouest.logol.Logol - option dna called INFO org.irisa.genouest.logol.Logol - Start analyse to create grammar analyser Executing prolog for pre-analyse java.io.FileNotFoundException: /tmp/1799.logol.f7104ea4-749d-45b1-8375-321313c4c203.pre.res (No such file or directory) at java.base/java.io.FileInputStream.open0(Native Method) at java.base/java.io.FileInputStream.open(FileInputStream.java:219) at java.base/java.io.FileInputStream.(FileInputStream.java:157) at java.base/java.io.FileReader.(FileReader.java:75) at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown Source) at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown Source) at org.irisa.genouest.logol.Logol.analyse(Unknown Source) at
Bug#1023453: marked as done (pgcli: Can't handle PostgreSQL "special" commands)
Your message dated Wed, 16 Nov 2022 05:19:32 + with message-id and subject line Bug#1023453: fixed in pgcli 3.5.0-3 has caused the Debian Bug report #1023453, regarding pgcli: Can't handle PostgreSQL "special" commands 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.) -- 1023453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgcli Version: 3.5.0-2 Severity: normal Hi, PostgreSQL "special" command (like `\d`) executed inside pgcli fails with this error: 'ProtocolSafeCursor' object has no attribute 'mogrify' The behaviour was changed during the psycopg3 port [1] and I suppose that the problem comes form the fact that the python3-pgspecial is still in the version using psycopg2. It's not a big problem and we can wait that python3-pgspecial is updated, I'm just submitting this bug so that users can understand why the special commands fail. Best, Yannick [1] https://github.com/dbcli/pgcli/commit/18071754bc0c79a7109c5ccfdaa74ed913c343ba -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.6 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pgcli depends on: ii python3 3.10.6-1 ii python3-cli-helpers 2.3.0-1 ii python3-click 8.1.3-0.1 ii python3-configobj 5.0.6-5 ii python3-pendulum2.1.2-4 ii python3-pgspecial 1.13.0-0.1 ii python3-pkg-resources 65.5.0-1 ii python3-prompt-toolkit 3.0.31-1 ii python3-psycopg33.1.3-0.1 ii python3-pygments2.12.0+dfsg-2 ii python3-setproctitle1.3.1-1 ii python3-sqlparse0.4.2-1 ii python3-tabulate0.8.9-1 ii python3-terminaltables 3.1.10-1 pgcli recommends no packages. pgcli suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pgcli Source-Version: 3.5.0-3 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of pgcli, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated pgcli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Nov 2022 05:57:41 +0100 Source: pgcli Architecture: source Version: 3.5.0-3 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1023453 Changes: pgcli (3.5.0-3) sid; urgency=medium . * Uploading to sid. * Depending on updated python3-pgspecial (Closes: #1023453). Checksums-Sha1: 5dbe3fc6624d7b8dcf1d376d1071ccc9dc23dfbb 1984 pgcli_3.5.0-3.dsc 329f7c65b728217b43407efff78456a6f5e15639 4292 pgcli_3.5.0-3.debian.tar.xz b313e325cf47b65a05a2972a79516b5916931935 6685 pgcli_3.5.0-3_amd64.buildinfo Checksums-Sha256: 9524b0d8595f5f844066fb90eeb02aec2953389c2b6063927f8b092bb8f909b7 1984 pgcli_3.5.0-3.dsc cec26a7c6ae0b11c0b134a54016379ee7bb45d2250865122e559a8758b037f55 4292 pgcli_3.5.0-3.debian.tar.xz 1ecacfcdf3164cc1d16b5ab2364d3827cfaa6e13fdf774e19758733dfc92e942 6685 pgcli_3.5.0-3_amd64.buildinfo Files: 49c037d1e75b128558b97b57c15eda82 1984 database optional pgcli_3.5.0-3.dsc 4ba9fcf6aebe8da591584215b3d8f940 4292 database optional pgcli_3.5.0-3.debian.tar.xz f3742e130591fd36788e83344c8caa6e 6685 database optional pgcli_3.5.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmN0b84ACgkQVc8b+Yar ucegrQ/+NOXqhhHezbMZKiIwiFN0taZ70p5J/CP+eYcF2IyUqaLumyEpdCMpnH+G E14XpbYBKX7YJqa8iR7LytjxAvk0X5uqcpbHK6/ojcm097Rtr2TsS4u6jQmDqbUc qTMS1t06+EK3LZ32NefRrU75n2pdbs78RJ+ymac2uw/Vk9+qjOreKBV4MLMLs1Fr BF4KR5hGtwsOyFzUWXSf0PiPgQwSYSk32aKNTXC8+hOjOO3EuFejfJwRESsHC/W0
Bug#985264: marked as done (librust-html2text-dev: depends on unavailable librust-clippy-0.0.302+default-dev)
Your message dated Wed, 16 Nov 2022 02:57:50 + with message-id and subject line Bug#985264: fixed in rust-html2text 0.4.4-1 has caused the Debian Bug report #985264, regarding librust-html2text-dev: depends on unavailable librust-clippy-0.0.302+default-dev 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.) -- 985264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-html2text-dev Version: 0.2.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is not installable in sid: The following packages have unmet dependencies: librust-html2text-dev : Depends: librust-clippy-0.0.302+default-dev but it is not installable Cheers, Andreas --- End Message --- --- Begin Message --- Source: rust-html2text Source-Version: 0.4.4-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-html2text, 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 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-html2text package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Nov 2022 01:15:16 + Source: rust-html2text Architecture: source Version: 0.4.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 985264 Changes: rust-html2text (0.4.4-1) unstable; urgency=medium . * Team upload. * Package html2text 0.4.4 from crates.io using debcargo 2.5.0 (Closes: #985264) * Disable a couple of tests when the html_trace feature is enabled to avoid stack overflows. Checksums-Sha1: 2ccbdf7ee74e6a1317482a72b97d600077541c36 2513 rust-html2text_0.4.4-1.dsc e1e1c854a974048be8523fd02491e7bfdc92dfa1 44096 rust-html2text_0.4.4.orig.tar.gz f0cb960429534f4fabec2577e79a26f636ed915b 3280 rust-html2text_0.4.4-1.debian.tar.xz 4399feeeca92d5fae2ecd91a0ac626bbad304beb 11171 rust-html2text_0.4.4-1_source.buildinfo Checksums-Sha256: 3113c337a0c491c672092d4d2c2bf08147aeff202153bc61f98384d4bd8b7d57 2513 rust-html2text_0.4.4-1.dsc 63009e2578b64b51d15a23fc5e440e3952eafba3d1e20ec76dd3f63221d95ed1 44096 rust-html2text_0.4.4.orig.tar.gz 5812fce6d74b9e088dec545e96b43e35abd878f02f6fc4f9c1c494657da6 3280 rust-html2text_0.4.4-1.debian.tar.xz fbe3e4efbc1ae2d3262f0c75b7ebc02fe3cb39e7fdd45f5deec2f8179e716cf9 11171 rust-html2text_0.4.4-1_source.buildinfo Files: 9a687459713f9155ae96a2dcc9ae9c91 2513 rust optional rust-html2text_0.4.4-1.dsc 28e41233aec0327c6d6839e65e2368e7 44096 rust optional rust-html2text_0.4.4.orig.tar.gz b50020111828be5921710f574a1df30c 3280 rust optional rust-html2text_0.4.4-1.debian.tar.xz f1334e6e9da76453875cda96e2539195 11171 rust optional rust-html2text_0.4.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmN0PpoUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtU7w//dzsojp4cKMN1/LGkFcdQm4oxTnaq A90HvObptFbRKShj6oke14Uwjo0IoxFOhoRwOur4V+vEQD2SkrJ3o6XzjsHyMOio Vo9jzbU5CdV9h783GsK4harKpG6M0HFd9VJ+H/iyEK4VhyghgrzbNLXTFIzgNXyw HhzK8XviM8648Vq594S+bEp5KBxZh0TyVim6N16QNUNSO5EYoRym+qXBikyGAQaF /absxAE3ng0IlL1EM8dXmrs0ZxTdB/Mf+3VUHto16hDrOQSh1ipVnaYh8XgIjwL8 6Vfc3QwwEsuhzOOHo5NMpocWArf60wYd8yhfbT+ngTP5hIOibVkVTExZj+k673mK 2WmvthVNQ34lzCXiR1skGISS1deqtrIyt3CsEUt+0gRm9tRsA+v7ThNPw+z9Qn// z2ZmVIh4iATcuAZIN8JKVwZIx8wVncRSudjZQXDu1IUNp0MuIS758ZM0ZztGhhOX wg8Dgq4K+0WIfUVy6ULuM+XiO3c8OU0arnEnjcqVXiRcXWgO3mCQwJColdjRJ7ot vH/XBAVYPLs0dxz9v8hyknxtn+9ihjlCqViv5KbdpQfHNPuiZptTJlASp7N0wQHO pNMv1yQ9mkmmlwaddFSVxFs+ePzq0fPd2jC97UCFVuoAaWV8LW36OsU2E8+llJIK W3TF7t4cz+HAw/U= =ekfi -END PGP SIGNATURE End Message ---
Bug#1023908: marked as done (pyfltk FTBFS with SWIG 4.1.0)
Your message dated Wed, 16 Nov 2022 02:56:36 + with message-id and subject line Bug#1023908: fixed in pyfltk 1.3.8+repack-3 has caused the Debian Bug report #1023908, regarding pyfltk FTBFS with SWIG 4.1.0 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.) -- 1023908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyfltk Version: 1.3.8+repack-2 Severity: serious Tags: ftbfs Forwarded: https://sourceforge.net/p/pyfltk/code/597/ https://buildd.debian.org/status/logs.php?pkg=pyfltk=1.3.8%2Brepack-2%2Bb1 ... Running command: ['swig', '-w302', '-w312', '-w325', '-w362', '-w389', '-w401', '-w473', '-w509', '-I./swig', '-I/usr/include/libpng16', '-I/usr/include/freetype2', '-I/usr/include/uuid', '-I/usr/include/pixman-1', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/glib-2.0', '-I/usr/include/cairo', '-I/usr/include/libpng16', '-I/usr/include/freetype2', '-I/usr/include/uuid', '-I/usr/include/libpng16', '-I/usr/include/freetype2', '-I/usr/include/uuid', '-I/usr/include/pixman-1', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/glib-2.0', '-I/usr/include/cairo', '-I/usr/include', '-DFL_EXPORT', '-DPYTHON', '-DPYTHON3', '-py3', '-c++', '-python', '-shadow', '-fastdispatch', '-outdir', 'fltk', '-o', 'fltk/fltk_wrap.cpp', './swig/fltk.i'] Deprecated command line option: -py3. Ignored, this option is no longer supported. /usr/include/FL/Fl_Export.H:35: Error: Macro 'FL_EXPORT' redefined, :1: Error: previous definition of 'FL_EXPORT'. ... --- End Message --- --- Begin Message --- Source: pyfltk Source-Version: 1.3.8+repack-3 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of pyfltk, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated pyfltk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 18:17:56 -0800 Source: pyfltk Architecture: source Version: 1.3.8+repack-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Dima Kogan Closes: 1023908 Changes: pyfltk (1.3.8+repack-3) unstable; urgency=medium . * Build with swig 4.1 (Closes: #1023908) Checksums-Sha1: be0ecb0d9d0745f2ee069d91ebaccc1f8168f773 2138 pyfltk_1.3.8+repack-3.dsc 7af4fc49f89eeb350c006416b26926acd3bc0998 5376 pyfltk_1.3.8+repack-3.debian.tar.xz 53c63d6ed8056b1e4341bfcff16d8292cddf2f27 10662 pyfltk_1.3.8+repack-3_amd64.buildinfo Checksums-Sha256: ed63e41a31f418978150c1fb767ed7ca6da69a2ccb1321acef982815485d1872 2138 pyfltk_1.3.8+repack-3.dsc 1765aae4b52a66b7485e97e9d45c1bf51be355b69035b8abb20405bfe44b3bbe 5376 pyfltk_1.3.8+repack-3.debian.tar.xz f61188910e6e4f95cab6b498f34954d2c9d0f21b6a9add88d6ef86b6ed879038 10662 pyfltk_1.3.8+repack-3_amd64.buildinfo Files: 539817337540a62e8ef31576c69b65d5 2138 python optional pyfltk_1.3.8+repack-3.dsc 9241e2c11f80a58896c948d1d9dd63cc 5376 python optional pyfltk_1.3.8+repack-3.debian.tar.xz 9979f72be9993e351e58e01568129709 10662 python optional pyfltk_1.3.8+repack-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmN0TQcACgkQrMfCzzCU EYiQcA//aGbMM79Ip2PJkBdkrHoj1jtlwAnjM3MGNPBFhRvAUxMhQBo+tHSZTYkY HVF9PZfo4aLKbr9y21hXs10N1Ja2YWd2vTLyghKbT2LHtI62qe1YyLK54ed8mTIZ NmmvJLPbneX3To9q/YmIcRvX/qGIdVzbHutDLBLg0IiOU1S9OSa//yPdCGxB28tu vMuBQab0GmHvDUEl1nIPyNQf77nTDr1US/NpEj0wWCbggtoDpAv+ZFIb0GoF4Y6G gDRvQ5I6zJlRzbdwPb0HiQX896zuJCSUcol2Oo49GM7CJUiJH2n0Yxdi0eVqmY7S p4CYuiSG3rrTEyKFkW/7C3Pc7eGuKVoId3pHAl7J5IwQCNFuFX8arIB1A79DzW3H 8T8MW+WGBEOT8Xif8HtdaQ9GxEIPLSbfs0MGxwmUyRQ8M9lY9IrDLZN786Q7VhWg omT/xoNqIKZxImWqm1Ln4G2HO8lN06CMpag+GlkdoZ9XyDRCrjCMFpFzjIWoJZjM Y2IXzqWjFybGt+dIkU5ZXqPn55XwZ55UxKz1WL8ehnGpyYxW2x54Vlo4pqy3BUSY WQwjZ+g3cRyR+/HMc+B4XuBg80o4hh4rxLvgUtx9R8n7gnHYRW9bqI5jy3R2tZxm Okvzv0g9aUx3rUm3NHD18qYsRViQL9ZjU/DEk+bbYQ1yL3/dlOg= =9Wij -END PGP SIGNATURE End Message ---
Bug#1024207: beancount FTBFS with Python 3.11 as supported version
Source: beancount
Version: 2.3.5-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=beancount=amd64=2.3.5-1%2Bb1=1668564409=0
...
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build;
python3.11 -m pytest -v
= test session starts ==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack --
/usr/bin/python3.11
cachedir: .pytest_cache
rootdir: /<>
collecting ... collected 1723 items / 1 error
ERRORS
_ ERROR collecting
.pybuild/cpython3_3.11/build/beancount/prices/sources/tsp_test.py _
beancount/prices/sources/tsp_test.py:12: in
from beancount.prices.sources import tsp
beancount/prices/sources/tsp.py:44: in
csv.register_dialect('tsp',
E TypeError: "quotechar" must be a 1-character string
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/bottle.py:38
/usr/lib/python3/dist-packages/bottle.py:38: DeprecationWarning: 'cgi' is
deprecated and slated for removal in Python 3.13
import base64, cgi, email.utils, functools, hmac, itertools, mimetypes,\
../../../../../../usr/lib/python3/dist-packages/pyparsing/core.py:26
/usr/lib/python3/dist-packages/pyparsing/core.py:26: DeprecationWarning:
module 'sre_constants' is deprecated
import sre_constants
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info
ERROR beancount/prices/sources/tsp_test.py - TypeError: "quotechar" must be a...
Interrupted: 1 error during collection
= 2 warnings, 1 error in 2.07s =
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=2: cd
/<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest -v
Processed: tagging 1023039
Processing commands for cont...@bugs.debian.org: > tags 1023039 + ftbfs Bug #1023039 [python-xmlsec] python-xmlsec: FTBFS with xmlsec1 1.2.35 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024206: ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32
Source: ogre-1.9 Version: 1.9.0+dfsg1-13 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/OGRECave/ogre/pull/1592 https://buildd.debian.org/status/fetch.php?pkg=ogre-1.9=armhf=1.9.0%2Bdfsg1-13=1668553225=0 ... /<>/OgreMain/src/OgrePlatformInformation.cpp:46:18: fatal error: sys/sysctl.h: No such file or directory 46 | #include | ^~ compilation terminated. make[3]: *** [OgreMain/CMakeFiles/OgreMain.dir/build.make:1563: OgreMain/CMakeFiles/OgreMain.dir/src/OgrePlatformInformation.cpp.o] Error 1
Bug#1010140: marked as done (aqsis: FTBFS on arm{el,hf})
Your message dated Wed, 16 Nov 2022 01:21:10 +
with message-id
and subject line Bug#1024176: Removed package(s) from unstable
has caused the Debian Bug report #1010140,
regarding aqsis: FTBFS on arm{el,hf}
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.)
--
1010140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aqsis
Version: 1.8.2+git20210815-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
aqsis FTBFS on armel and armhf:
[ 34%] Building CXX object
libs/tex/CMakeFiles/aqsis_tex.dir/filtering/occlusionsampler.cpp.o
cd /<>/obj-arm-linux-gnueabi/libs/tex && /usr/bin/c++
-DAQSIS_TEX_EXPORTS -DAQSIS_USE_PNG -DBOOST_ALL_NO_LIB
-DBOOST_FILESYSTEM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DUSE_OPENEXR
-Daqsis_tex_EXPORTS -I/<>/include
-I/<>/obj-arm-linux-gnueabi/include
-I/<>/libs/tex/filtering -I/<>/libs/tex/io
-I/<>/libs/tex/maketexture -I/usr/include/OpenEXR -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -fopenmp -fPIC -MD -MT
libs/tex/CMakeFiles/aqsis_tex.dir/filtering/occlusionsampler.cpp.o -MF
CMakeFiles/aqsis_tex.dir/filtering/occlusionsampler.cpp.o.d -o
CMakeFiles/aqsis_tex.dir/filtering/occlusionsampler.cpp.o -c
/<>/libs/tex/filtering/occlusionsampler.cpp
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::glTranslate(const V3f&)’:
/<>/tools/ptview/ptview.cpp:66:5: error: ‘glTranslatef’ was not
declared in this scope; did you mean ‘glTranslate’?
66 | glTranslatef(v.x, v.y, v.z);
| ^~~~
| glTranslate
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::glVertex(const V3f&)’:
/<>/tools/ptview/ptview.cpp:71:5: error: ‘glVertex3f’ was not
declared in this scope; did you mean ‘glVertex’?
71 | glVertex3f(v.x, v.y, v.z);
| ^~
| glVertex
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::glVertex(const V2f&)’:
/<>/tools/ptview/ptview.cpp:76:5: error: ‘glVertex2f’ was not
declared in this scope; did you mean ‘glVertex’?
76 | glVertex2f(v.x, v.y);
| ^~
| glVertex
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::glColor(const C3f&)’:
/<>/tools/ptview/ptview.cpp:81:5: error: ‘glColor3f’ was not
declared in this scope; did you mean ‘glColor’?
81 | glColor3f(c.x, c.y, c.z);
| ^
| glColor
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::glLoadMatrix(const M44f&)’:
/<>/tools/ptview/ptview.cpp:86:5: error: ‘glLoadMatrixf’ was not
declared in this scope; did you mean ‘glLoadMatrix’?
86 | glLoadMatrixf((GLfloat*)m[0]);
| ^
| glLoadMatrix
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::drawDisk(Imath_2_5::V3f, Imath_2_5::V3f, float)’:
/<>/tools/ptview/ptview.cpp:308:5: error: ‘glPushMatrix’ was not
declared in this scope; did you mean ‘glLoadMatrix’?
308 | glPushMatrix();
| ^~~~
| glLoadMatrix
/<>/tools/ptview/ptview.cpp:311:5: error: ‘glScalef’ was not
declared in this scope
311 | glScalef(r,r,r);
| ^~~~
/<>/tools/ptview/ptview.cpp:319:5: error: ‘glRotatef’ was not
declared in this scope
319 | glRotatef(angle, v.x, v.y, v.z);
| ^
/<>/tools/ptview/ptview.cpp:320:5: error: ‘glColor3f’ was not
declared in this scope; did you mean ‘glColor’?
320 | glColor3f(1, 0, 0);
| ^
| glColor
/<>/tools/ptview/ptview.cpp:321:5: error: ‘glBegin’ was not
declared in this scope
321 | glBegin(GL_LINE_LOOP);
| ^~~
/<>/tools/ptview/ptview.cpp:328:13: error: ‘glVertex3f’ was not
declared in this scope; did you mean ‘glVertex’?
328 | glVertex3f(scale*cos(angle), scale*sin(angle), 0);
| ^~
| glVertex
/<>/tools/ptview/ptview.cpp:330:5: error: ‘glEnd’ was not declared
in this scope
330 | glEnd();
| ^
/<>/tools/ptview/ptview.cpp:331:5: error: ‘glPopMatrix’ was not
declared in this scope; did you mean ‘glLoadMatrix’?
331 | glPopMatrix();
| ^~~
| glLoadMatrix
/<>/tools/ptview/ptview.cpp: In function ‘void
Aqsis::drawCubeEnvFace(Imath_2_5::V2f, GLubyte*, int)’:
/<>/tools/ptview/ptview.cpp:436:55: error: ‘GL_CLAMP’ was not
declared in this scope
436 |
Bug#1017559: marked as done (aqsis FTBFS with openexr 3.1.5)
Your message dated Wed, 16 Nov 2022 01:21:10 + with message-id and subject line Bug#1024176: Removed package(s) from unstable has caused the Debian Bug report #1017559, regarding aqsis FTBFS with openexr 3.1.5 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.) -- 1017559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aqsis Version: 1.8.2+git20210815-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=aqsis=1.8.2%2Bgit20210815-1%2Bb2 ... CMake Error at libs/shadervm/CMakeLists.txt:5 (message): Aqsis shadervm requires boost regex and OpenEXR to build -- Configuring incomplete, errors occurred! ... //Location of the Half OpenEXR library AQSIS_HALF_LIBRARY:FILEPATH=AQSIS_HALF_LIBRARY-NOTFOUND //Location of the Iex OpenEXR library AQSIS_IEX_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libIex.so //Location of the IlmImf OpenEXR library AQSIS_ILMIMF_LIBRARY:FILEPATH=AQSIS_ILMIMF_LIBRARY-NOTFOUND //Location of the IlmThread OpenEXR library AQSIS_ILMTHREAD_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libIlmThread.so //Location of the Imath OpenEXR library AQSIS_IMATH_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libImath.so //Name of the main aqsis configuration file AQSIS_MAIN_CONFIG_NAME:STRING=aqsisrc //Location of the NSIS executable AQSIS_NSIS_EXECUTABLE:FILEPATH=AQSIS_NSIS_EXECUTABLE-NOTFOUND //Location of the OpenEXR headers AQSIS_OPENEXR_INCLUDE_DIR:PATH=/usr/include //Semi-colon separated list of paths to search for openexr libraries AQSIS_OPENEXR_LIBRARIES_DIR:PATH= ... --- End Message --- --- Begin Message --- Version: 1.8.2+git20210815-1+rm Dear submitter, as the package aqsis has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1024176 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1016494: marked as done (python2-pip: don't ship python2.7 with bookworm)
Your message dated Wed, 16 Nov 2022 01:20:37 + with message-id and subject line Bug#1024159: Removed package(s) from unstable has caused the Debian Bug report #1016494, regarding python2-pip: don't ship python2.7 with bookworm 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.) -- 1016494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python2-pip Version: 20.3.4+dfsg-4 Severity: serious Dear maintainers, I'm surprised to see there's no RC bug against python2-pip yet, but we're trying to not ship python2.7 with bookworm, which means this package has to go too, right? Paul --- End Message --- --- Begin Message --- Version: 20.3.4+dfsg-4+rm Dear submitter, as the package python2-pip has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1024159 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1004654: marked as done (ruby-rack-mount: FTBFS with ruby-rack 2.2.3 "http://josh.backpackit.com/host">(UTF-8) expected but was <"http://example.org/host">(ASCII-8BIT))
Your message dated Wed, 16 Nov 2022 01:18:46 +
with message-id
and subject line Bug#1018910: Removed package(s) from unstable
has caused the Debian Bug report #1004654,
regarding ruby-rack-mount: FTBFS with ruby-rack 2.2.3
"http://josh.backpackit.com/host;>(UTF-8) expected but was
<"http://example.org/host;>(ASCII-8BIT)
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.)
--
1004654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rack-mount
Version: 0.8.3-3
Severity: serious
ruby-rack-mount now ftbfs and fails autopkgtest with ruby-rack 2.2.3
test_generate_host: F
===
Failure: test_generate_host(TestGeneration)
/<>/test/test_generation.rb:74:in `test_generate_host'
71: assert_equal ['josh.backpackit.com', {}], @app.generate(:host,
:controller => 'account', :account => 'josh')
72: assert_equal [{:host => 'josh.backpackit.com', :path_info =>
'/host'}, {}], @app.generate(:all, :controller => 'account', :account
=> 'josh')
73: assert_equal [{:request_method => 'GET', :path_info =>
'/login'}, {}], @app.generate(:all, :login)
=> 74: assert_equal 'http://josh.backpackit.com/host', @app.url(@env,
:controller => 'account', :account => 'josh')
75: end
76:
77: def test_generate_full_url
<"http://josh.backpackit.com/host;>(UTF-8) expected but was
<"http://example.org/host;>(ASCII-8BIT)
diff:
? http://j osh.backpackit.com/host
? example. rg
? Encoding: UTF -8
? ASCII BIT
===
: (0.007321)
full log
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rack-mount/18822994/log.gz
(same error in clean build too)
This is now a leaf package, the package that build dependended on it no
longer use it and it is not maintained upstream.
I think we can safely request its removal if no one wants to fix this
bug
https://lists.debian.org/debian-ruby/2022/01/msg00019.html
--- End Message ---
--- Begin Message ---
Version: 0.8.3-3+rm
Dear submitter,
as the package ruby-rack-mount has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1018910
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1024060: emacs: FTBFS for architecture all: test-undo-region fails / unexpected lisp/simple-tests.log
control: tag -1 + pending Hello, On Tue 15 Nov 2022 at 06:24PM +01, Andreas Beckmann wrote: > Control: severity -1 serious > > On Mon, 14 Nov 2022 12:50:53 -0700 Sean Whitton > wrote: >> There are a number of flaky tests atm. Ideally we'd patch them out, but >> it's not RC. > > -5 so far has failed 8 times on arch:all. > Feel free to downgrade the severity again once the build succeeded. Thanks. Next upload will disable the test. -- Sean Whitton signature.asc Description: PGP signature
Processed: Re: Bug#1024060: emacs: FTBFS for architecture all: test-undo-region fails / unexpected lisp/simple-tests.log
Processing control commands: > tag -1 + pending Bug #1024060 [src:emacs] emacs: FTBFS for architecture all: test-undo-region fails / unexpected lisp/simple-tests.log Added tag(s) pending. -- 1024060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Move where it was fixed
Processing commands for cont...@bugs.debian.org: > reassign 1019996 python3 Bug #1019996 [src:lxml] lxml: FTBFS: ModuleNotFoundError: No module named 'lxml' Bug reassigned from package 'src:lxml' to 'python3'. No longer marked as found in versions lxml/4.9.1-1. Ignoring request to alter fixed versions of bug #1019996 to the same values previously set > affects 1019996 src:lxml Bug #1019996 [python3] lxml: FTBFS: ModuleNotFoundError: No module named 'lxml' Added indication that 1019996 affects src:lxml > close 1019996 3.10.6-3 Bug #1019996 [python3] lxml: FTBFS: ModuleNotFoundError: No module named 'lxml' Marked as fixed in versions python3-defaults/3.10.6-3. Bug #1019996 [python3] lxml: FTBFS: ModuleNotFoundError: No module named 'lxml' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1019996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938322: Python 2 support for Bullseye
When qtwebengine-opensource-src is removed a lot of packages will have a problem because they are not ready for qt6. Is it a bookworm release goal to remove the python2 interpreter also for packages that just build-depend on it? If so, the FreeBSD patch (or a backport from the qt6 package) might be worth a look.
Bug#1023697: Keep out of testing
Hi, On Tue, Nov 8, 2022 at 12:00 PM Moritz Muehlenhoff wrote: > > open security issues I also just uploaded a backport for bullseye. Kind regards, Felix Lechner
Processed: raise severity (Policy violation)
Processing commands for cont...@bugs.debian.org: > severity 1012631 serious Bug #1012631 [src:tcp-wrappers] tcp-wrappers: d/copyright is incomplete Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1012631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Just a short addition: There is already an upstream bug reported: https://github.com/csound/csound/issues/1651 Kind regards, Bernhard
Bug#1024201: hcloud-python: python-setuptools will trigger autoremove (NMU)
Source: hcloud-python Severity: serious Version: 1.18.1-2 You python3 package build-depends on python-setuptools (python2) even though it is not needed. I am going to upload a DELAYED/3 NMU to get rid of it.
Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Dear Maintainer, this looks like caused by a disaggrement about the size of type OPARMS. In libcsound64-6.0 it has 264 bytes, but in csound-plugins only 260 bytes. This difference is caused by the last member "mp3_mode", that is missing in the OPARMS type used in csound-plugins. It got introduced in commit [1] and caused this ABI break. Attached are relevant parts of the debugging. Kind regards, Bernhard [1] https://github.com/csound/csound/commit/11df83f60d6afa51e5e0d25dc5efe5b2beec621e (rr) bt #0 0xb7a1e4f6 in memcpy (__len=264, __src=0x10d3de0, __dest=0xbfb5aee8) at /usr/include/i386-linux-gnu/bits/string_fortified.h:29 #1 csoundGetOParms (csound=, p=0xbfb5aee8) at ./Top/csound.c:230 #2 0xb51310c0 in csoundModuleInit (csound=0x10c61a0) at ./widgets/winFLTK.c:73 #3 0xb7b6388a in csoundInitModule (csound=csound@entry=0x10c61a0, m=m@entry=0x11baed8) at ./Top/csmodule.c:249 #4 0xb7b63a51 in csoundInitModules (csound=0x10c61a0) at ./Top/csmodule.c:825 #5 0xb7a233f5 in csoundReset (csound=) at ./Top/csound.c:3554 #6 0xb7a23af4 in csoundCreate (hostdata=0x0) at ./Top/csound.c:1361 #7 0x004c24c7 in main (argc=3, argv=0xbfb5b224) at ./Frontends/csound/csound_main.c:322 # Unstable i386 qemu VM 2022-11-15 apt update apt dist-upgrade apt install systemd-coredump gdb rr autopkgtest dpkg-dev csound csound-plugins python3-csound csound-plugins-dbgsym libcsound64-6.0-dbgsym csound-dbgsym $ autopkgtest csound-plugins --shell-fail -- null autopkgtest [23:05:23]: starting date and time: 2022-11-15 23:05:23+0100 autopkgtest [23:05:23]: version 5.27 autopkgtest [23:05:23]: host debian; command line: /usr/bin/autopkgtest csound-plugins --shell-fail -- null autopkgtest [23:05:23]: testbed dpkg architecture: i386 autopkgtest [23:05:23]: testbed running kernel: Linux 6.0.0-4-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.0.8-1 (2022-11-11) autopkgtest [23:05:23]: apt-source csound-plugins gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: Schlüsselblockhilfsmittel`/tmp/dpkg-verify-sig.OC9zItqO/trustedkeys.kbx': General error gpgv: Signatur vom Mi 28 Sep 2022 09:29:57 CEST gpgv:mittels RSA-Schlüssel 7405E745574809734800156DB65019C47F7A36F8 gpgv: Signatur kann nicht geprüft werden: No public key dpkg-source: Warnung: Signatur ./csound-plugins_1.0.2~dfsg1-2.dsc kann nicht überprüft werden autopkgtest [23:05:24]: testing package csound-plugins version 1.0.2~dfsg1-2 autopkgtest [23:05:24]: build not needed autopkgtest [23:05:24]: test command1: preparing testbed autopkgtest [23:05:24]: test command1: csound --nosound py/examples/embeddedCtcsound.csd autopkgtest [23:05:24]: test command1: [--- *** stack smashing detected ***: terminated csound command: Aborted csound command: Segmentation fault autopkgtest [23:05:25]: test command1: ---] autopkgtest [23:05:25]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 1 autopkgtest [23:05:25]: - - - - - - - - - - running shell - - - - - - - - - - benutzer@debian:/tmp/autopkgtest.2VfrCV/build.Tvx/src$ rr record csound --nosound py/examples/embeddedCtcsound.csd rr: Saving execution to trace directory `/home/benutzer/.local/share/rr/csound-0'. *** stack smashing detected ***: terminated csound command: Aborted csound command: Segmentation fault $ rr replay -o -q csound-0 Reading symbols from /usr/bin/csound... (No debugging symbols found in /usr/bin/csound) Really redefine built-in command "restart"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "jump"? (y or n) [answered Y; input not from terminal] Remote debugging using 127.0.0.1:3587 Reading symbols from /lib/ld-linux.so.2... Reading symbols from /usr/lib/debug/.build-id/9b/f5ef863480886a4c2159e109d63c656ca30739.debug... BFD: warning: system-supplied DSO at 0x6fffd000 has a section extending past end of file 0xb7f40450 in _start () from /lib/ld-linux.so.2 (rr) cont Continuing. *** stack smashing detected ***: terminated Program received signal SIGABRT, Aborted. 0x7002 in syscall_traced () (rr) bt #0 0x7002 in syscall_traced () #1 0xb7f1513d in _raw_syscall () at /build/rr-Rm2x32/rr-5.6.0/src/preload/raw_syscall.S:34 #2 0xb7f10b33 in traced_raw_syscall (call=0x681fffd8) at ./src/preload/syscallbuf.c:338 #3 0xb7f12c4d in sys_recvfrom (call=) at ./src/preload/syscallbuf.c:2952 #4 syscall_hook_internal (call=0x681fffd8) at ./src/preload/syscallbuf.c:3843 #5 syscall_hook (call=0x681fffd8) at ./src/preload/syscallbuf.c:3949 #6 syscall_hook (call=) at ./src/preload/syscallbuf.c:3933 #7 0xb7f10361 in _syscall_hook_trampoline () at /build/rr-Rm2x32/rr-5.6.0/src/preload/syscall_hook.S:131 #8 0xb7f103d2 in _syscall_hook_trampoline_90_90_90 () at /build/rr-Rm2x32/rr-5.6.0/src/preload/syscall_hook.S:211 #9 0x6005 in __kernel_vsyscall () #10 0xb768a1d7 in __pthread_kill_implementation
Bug#938794: marked as done (vmm: Python2 removal in sid/bullseye)
Your message dated Tue, 15 Nov 2022 22:35:06 + with message-id and subject line Bug#938794: fixed in vmm 0.7.0-0.1 has caused the Debian Bug report #938794, regarding vmm: Python2 removal in sid/bullseye 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.) -- 938794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vmm Version: 0.6.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:vmm If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: vmm Source-Version: 0.7.0-0.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of vmm, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated vmm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 22:33:27 +0100 Source: vmm Architecture: source Version: 0.7.0-0.1 Distribution: unstable Urgency: medium Maintainer: martin f. krafft Changed-By: Bastian Germann Closes: 938794 1015976 Changes: vmm (0.7.0-0.1) unstable; urgency=medium . * Non-maintainer upload. . [ Pascal Volk ] * [21e54b2] Added a note about the usage of CRAM-MD5. * [cc74979] VMM/config: Corrected a setting name in an error msg. * [8bfdcf2] doc/web: dovecot_configuration: corrected 'user_query`. * [a6b0589] VMM/cli/clihelp: Two small improvements: - Unified `wild card search' help messages. - Added a comment for xgettext, so it should no longer make a wrong decision about `python-format'. * [b1a8e5b] po: Regenerated vmm.pot * [af13262] VMM/cli/subcommands: Moved the TP comment to the right place. * [94cb908] po: Regenerated vmm.pot * [b6e6f86] po: Updated German translation (translated by Mario Blättermann). * [29430ff]
Bug#1015976: marked as done (Should vmm be removed?)
Your message dated Tue, 15 Nov 2022 22:35:06 + with message-id and subject line Bug#1015976: fixed in vmm 0.7.0-0.1 has caused the Debian Bug report #1015976, regarding Should vmm be removed? 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.) -- 1015976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vmm Version: 0.6.2-2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2017, removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz --- End Message --- --- Begin Message --- Source: vmm Source-Version: 0.7.0-0.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of vmm, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated vmm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 22:33:27 +0100 Source: vmm Architecture: source Version: 0.7.0-0.1 Distribution: unstable Urgency: medium Maintainer: martin f. krafft Changed-By: Bastian Germann Closes: 938794 1015976 Changes: vmm (0.7.0-0.1) unstable; urgency=medium . * Non-maintainer upload. . [ Pascal Volk ] * [21e54b2] Added a note about the usage of CRAM-MD5. * [cc74979] VMM/config: Corrected a setting name in an error msg. * [8bfdcf2] doc/web: dovecot_configuration: corrected 'user_query`. * [a6b0589] VMM/cli/clihelp: Two small improvements: - Unified `wild card search' help messages. - Added a comment for xgettext, so it should no longer make a wrong decision about `python-format'. * [b1a8e5b] po: Regenerated vmm.pot * [af13262] VMM/cli/subcommands: Moved the TP comment to the right place. * [94cb908] po: Regenerated vmm.pot * [b6e6f86] po: Updated German translation (translated by Mario Blättermann). * [29430ff] po: Updated Finnish translation (translated by Jorma Karvonen). . [ Bernd Zeimetz ] * [c14a6ee] New upstream version 0.7.0 (Closes: #938794, #1015976). Checksums-Sha1: 2ddb6d78862e165046f0fee9c4be6684c18bf86f 1709 vmm_0.7.0-0.1.dsc a5982b7c0da7f71db5f86775fe42c65216d7735b 180480 vmm_0.7.0.orig.tar.xz aa386fbd90d611956272c1b436958b7dfc3c1f1f 8936 vmm_0.7.0-0.1.debian.tar.xz c3d2003e11d75cf98c7a0f6d1c014b360ff5fd06 7105 vmm_0.7.0-0.1_source.buildinfo Checksums-Sha256: 5fec1d2cebd627bca1454ccb014eaf5d4c5b7398172e989621a5270ad2670fb8 1709 vmm_0.7.0-0.1.dsc cfeabf68db1a6ae2eca93ad627b69817f48126da94ee04c039d48ef460ddb802 180480 vmm_0.7.0.orig.tar.xz a2d470b970187467c43719dc59bb60c40e5bd9abc3964935c12081278625f683 8936 vmm_0.7.0-0.1.debian.tar.xz 184a0246044b80c9587da892f79a829ecca5afcd5f73e63b7b2d97d49bf5788a 7105 vmm_0.7.0-0.1_source.buildinfo Files: 86e1a0db37516742cafa82fe3221d871 1709 mail extra vmm_0.7.0-0.1.dsc 9cac100e42a8e1392e5e78f6fb15b4f2 180480 mail extra vmm_0.7.0.orig.tar.xz 35a37d48862bb9dbc61cc52d5f775866 8936 mail extra vmm_0.7.0-0.1.debian.tar.xz aa2a32277b973ae8f12c99e1ed54f04c 7105 mail extra vmm_0.7.0-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmN0DoQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFME8DACGWhywr8BHzMpuMYA3Q1RRPrI1r+uhElLw 0eeYa8MRRcwYZT2bPikutFmD7qAG1Fd2R3EZcd7fmYWnF9rmH+wIZfzBv8zQglgd PlStWu1oNa3tjkxerMlChiDNHoY1LvRo59tNwUgB6ps06VXhLxQC6KqE0XuMuv/f SPiGUkJmq2z2eIzMcmSrlfn4zt1HCz3voYcEwv82WyycZVpjUHJGUmS0POSE71jo W3BREnpUMfchEkT6z+w+OgdrpftPDHVPLX7ebMF9kL6Dmg2MGxTCkPUtwD2XnAg4
Bug#1024044: marked as done (python-ltfatpy FTBFS with Python 3.11 as supported version)
Your message dated Tue, 15 Nov 2022 22:30:54 +
with message-id
and subject line Bug#1024044: fixed in python-ltfatpy 1.0.16-8
has caused the Debian Bug report #1024044,
regarding python-ltfatpy 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.)
--
1024044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ltfatpy
Version: 1.0.16-7
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=python-ltfatpy=sid
...
=== FAILURES ===
TestGabWin.test_composed_dictionnaries_entries
self =
def test_composed_dictionnaries_entries(self):
a = random.randint(10, 40)
M = random.randint(10, 40)
L = lcm(a, M)
# default
self.assertRaises(TypeError, gabwin, {'name': 1}, a, M, L)
# dual psech
tfr = 10
gd = {'name': ('dual', 'sech'), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertFalse(info['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(psech(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)
# dual pgauss
tfr = 10
gd = {'name': ('dual',), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertTrue(info['auxinfo']['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(pgauss(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)
# dual fir
> name = random.sample(arg_firwin(), 1)[0]
ltfatpy/tests/gabor/test_gabwin.py:356:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
population = {'bartlett', 'blackman', 'blackman2', 'cosine', 'hamming', 'hann',
...}
k = 1
def sample(self, population, k, *, counts=None):
"""Chooses k unique random elements from a population sequence.
Returns a new list containing elements from the population while
leaving the original population unchanged. The resulting list is
in selection order so that all sub-slices will also be valid random
samples. This allows raffle winners (the sample) to be partitioned
into grand prize and second place winners (the subslices).
Members of the population need not be hashable or unique. If the
population contains repeats, then each occurrence is a possible
selection in the sample.
Repeated elements can be specified one at a time or with the optional
counts parameter. For example:
sample(['red', 'blue'], counts=[4, 2], k=5)
is equivalent to:
sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5)
To choose a sample from a range of integers, use range() for the
population argument. This is especially fast and space efficient
for sampling from a large population:
sample(range(1000), 60)
"""
# Sampling without replacement entails tracking either potential
# selections (the pool) in a list or previous selections in a set.
# When the number of selections is small compared to the
# population, then tracking selections is efficient, requiring
Bug#1024155: libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)
Andreas Beckmann writes: > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. Good catch, thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1024173: python-cfg-diag breaks remrun autopkgtest: 'Config' object has no attribute 'diag_'
On Tue, Nov 15, 2022 at 09:43:48PM +0100, Paul Gevers wrote: > Source: python-cfg-diag, remrun > Control: found -1 python-cfg-diag/0.4.0-1 > Control: found -1 remrun/0.2.2-1 > Severity: serious > Tags: sid bookworm > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of python-cfg-diag the autopkgtest of remrun fails in > testing when that autopkgtest is run with the binary packages of > python-cfg-diag from unstable. It passes when run with only packages from > testing. In tabular form: > >passfail > python-cfg-diagfrom testing0.4.0-1 > remrun from testing0.2.2-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 python-cfg-diag to > testing [1]. Due to the nature of this issue, I filed this bug report > against both packages. Can you please investigate the situation and reassign > the bug to the right package? Hi, Thanks for filing this bug report, and thanks for working on all the infrastructure related to debci, autopkgtest, and ci.debian.org; it has made working on Debian easier and more pleasant! I am indeed aware that version 0.4.x of python-cfg-diag will break remrun-0.2.2; that's the reason I uploaded remrun-0.2.3 on the very next day - it includes a bumped dependency on python-cfg-diag >= 0.4 in both debian/control and debian/tests/control. I just realized that maybe I should have given a hint about that breakage in the python-cfg-diag package itself; would it be a good idea to upload a new Debian revision with `Breaks: remrun < 0.2.3`? G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1024188: hcloud-python: Stale build dependency on python-setuptools
Source: hcloud-python Version: 1.18.1-2 Severity: serious hcloud-python has a stale build dependency on python-setuptools, which will soon be removed from bookworm. What is actually used is the already existing build dependency on python3-setuptools.
Processed: tagging 932820
Processing commands for cont...@bugs.debian.org: > tags 932820 + bookworm sid Bug #932820 [vanguards] vanguards: Migrate to PyPy3 (Python 3) Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 932820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023219: marked as done (src:psychtoolbox-3: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Tue, 15 Nov 2022 21:53:32 + with message-id and subject line Bug#1023219: fixed in psychtoolbox-3 3.0.18.12.dfsg1-1.1 has caused the Debian Bug report #1023219, regarding src:psychtoolbox-3: fails to migrate to testing for too long: uploader built arch:all binaries 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.) -- 1023219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: psychtoolbox-3 Version: 3.0.18.9.dfsg1-1 Severity: serious Control: close -1 3.0.18.12.dfsg1-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:psychtoolbox-3 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=psychtoolbox-3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: psychtoolbox-3 Source-Version: 3.0.18.12.dfsg1-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of psychtoolbox-3, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated psychtoolbox-3 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: Mon, 31 Oct 2022 20:21:52 +0100 Source: psychtoolbox-3 Architecture: source Version: 3.0.18.12.dfsg1-1.1 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Paul Gevers Closes: 1023219 Changes: psychtoolbox-3 (3.0.18.12.dfsg1-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1023219) Checksums-Sha1: 3c36bff92d38fac84f5782a37eadff55f26c5500 3039 psychtoolbox-3_3.0.18.12.dfsg1-1.1.dsc 9127b6805543d7d2c70db11bba94a331fae1e422 52660 psychtoolbox-3_3.0.18.12.dfsg1-1.1.debian.tar.xz Checksums-Sha256: 64b707096e7576e4e4e40a936a5f1ff4d43fe0c3dbfd23917907585144f98511 3039 psychtoolbox-3_3.0.18.12.dfsg1-1.1.dsc fdf12f75b1f934cb5458930d5477049e76d4724860e95624fe35606f88fb8d1e 52660 psychtoolbox-3_3.0.18.12.dfsg1-1.1.debian.tar.xz Files: 8b116f4f7621638a4dd96aa97c22c4e8 3039 science optional psychtoolbox-3_3.0.18.12.dfsg1-1.1.dsc 0ee8cefff0703519b554dec2f0f7ea8d 52660 science optional psychtoolbox-3_3.0.18.12.dfsg1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmNgIHgACgkQnFyZ6wW9 dQr2BQgAwSQN9Wz19l5pi/pbLHBnn7xVAfsNPyvPseOwhpaH23CQ+Oz6pnDnw65S aoZiRgsrMijs4W/S8DN/1/vHDUvHkA3mSX0/y2w4ttzRal4MyT9E4j4GaTCnLfzw
Bug#1022464: marked as done (pykafka: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)
Your message dated Tue, 15 Nov 2022 21:53:48 +
with message-id
and subject line Bug#1022464: fixed in pykafka 2.7.0-2.1
has caused the Debian Bug report #1022464,
regarding pykafka: FTBFS: distutils.errors.DistutilsSetupError: each element of
'ext_modules' option must be an Extension instance or 2-tuple
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.)
--
1022464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pykafka
Version: 2.7.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=pybuild --with
> python3
> dh: error: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose
> from: binary binary-arch binary-indep build build-arch build-indep clean
> install install-arch install-indep)
> 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.10 setup.py config
> /<>/setup.py:22: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<>/setup.py:22: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/__init__.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/topic.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/managedbalancedconsumer.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/exceptions.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/client.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/membershipprotocol.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/common.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/handlers.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/balancedconsumer.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/cluster.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/protocol.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/simpleconsumer.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/producer.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying pykafka/partition.py ->
> /<>/.pybuild/cpython3_3.10_pykafka/build/pykafka
> copying
Processed: severity of 932820 is serious
Processing commands for cont...@bugs.debian.org: > severity 932820 serious Bug #932820 [vanguards] vanguards: Migrate to PyPy3 (Python 3) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 932820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024168: cruft-ng: autopkgtest failure: /usr/libexec/cruft/init-system-helpers: 4: file: not found
Hi, I m waiting for a bug to be fixed in placage that impact cruft-ng plupart run. The "file" bug is fixed by next upload where à RFS has been filed (I m only DM) So with this one this makes 4 bugs total, for which I can not do much more. I m on Holliday, you can nmu if it bothers you. Greetings Le mar. 15 nov. 2022, 20:57, Paul Gevers a écrit : > Source: cruft-ng > Version: 0.9.47 > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainer(s), > > You recently added an autopkgtest to your package cruft-ng, great. > However, it fails. Currently this failure is blocking the migration to > testing [1]. Can you please investigate the situation and fix it? >
Bug#1024187: heimdal: CVE-2022-44640 CVE-2022-42898 CVE-2022-3437 CVE-2021-44758
Source: heimdal
Version: 7.7.0+dfsg-6
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for heimdal.
CVE-2022-44640[0]:
| Invalid free in ASN.1 codec
CVE-2022-42898[1]:
| krb5_pac_parse() buffer parsing vulnerability
CVE-2022-3437[2]:
| Buffer overflow in Heimdal unwrap_des3()
CVE-2021-44758[3]:
| spnego: send_reject when no mech selected
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
>From the 7.7.1 release notes[4]:
| This release fixes the following Security Vulnerabilities:
|
| CVE-2022-42898 PAC parse integer overflows
|
| CVE-2022-3437 Overflows and non-constant time leaks in DES{,3} and arcfour
|
| CVE-2021-44758 NULL dereference DoS in SPNEGO acceptors
|
| CVE-2022-44640 Heimdal KDC: invalid free in ASN.1 codec
|
| Note that CVE-2022-44640 is a severe vulnerability, possibly a 10.0
| on the Common Vulnerability Scoring System (CVSS) v3, as we believe
| it should be possible to get an RCE on a KDC, which means that
| credentials can be compromised that can be used to impersonate
| anyone in a realm or forest of realms.
|
| Heimdal's ASN.1 compiler generates code that allows specially
| crafted DER encodings of CHOICEs to invoke the wrong free function
| on the decoded structure upon decode error. This is known to impact
| the Heimdal KDC, leading to an invalid free() of an address partly
| or wholly under the control of the attacker, in turn leading to a
| potential remote code execution (RCE) vulnerability.
|
| This error affects the DER codec for all extensible CHOICE types
| used in Heimdal, though not all cases will be exploitable. We have
| not completed a thorough analysis of all the Heimdal components
| affected, thus the Kerberos client, the X.509 library, and other
| parts, may be affected as well.
|
| This bug has been in Heimdal's ASN.1 compiler since 2005, but it may
| only affect Heimdal 1.6 and up. It was first reported by Douglas
| Bagnall, though it had been found independently by the Heimdal
| maintainers via fuzzing a few weeks earlier.
|
| While no zero-day exploit is known, such an exploit will likely be
| available soon after public disclosure.
|
| CVE-2019-14870: Validate client attributes in protocol-transition
|
| CVE-2019-14870: Apply forwardable policy in protocol-transition
|
| CVE-2019-14870: Always lookup impersonate client in DB
(CVE-2019-14870 was already fixed earlier in unstable)
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2022-44640
https://www.cve.org/CVERecord?id=CVE-2022-44640
[1] https://security-tracker.debian.org/tracker/CVE-2022-42898
https://www.cve.org/CVERecord?id=CVE-2022-42898
[2] https://security-tracker.debian.org/tracker/CVE-2022-3437
https://www.cve.org/CVERecord?id=CVE-2022-3437
[3] https://security-tracker.debian.org/tracker/CVE-2021-44758
https://www.cve.org/CVERecord?id=CVE-2021-44758
[4] https://github.com/heimdal/heimdal/releases/tag/heimdal-7.7.1
Regards,
Salvatore
Bug#1024019: marked as done (iminuit FTBFS with Python 3.11 as supported version)
Your message dated Tue, 15 Nov 2022 21:22:17 +
with message-id
and subject line Bug#1024019: fixed in iminuit 2.11.2-3
has caused the Debian Bug report #1024019,
regarding iminuit 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.)
--
1024019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iminuit
Version: 2.11.2-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=iminuit=2.11.2-2%2Bb2
...
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from /<>/src/application.cpp:3:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from
/<>/extern/pybind11/include/pybind11/numpy.h:12,
from /<>/src/type_caster.hpp:2,
from /<>/src/fcn.cpp:2:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from /<>/src/fcn.hpp:2,
from /<>/src/fcn.cpp:1:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from /<>/src/contours.cpp:5:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from
/<>/extern/pybind11/include/pybind11/operators.h:12,
from /<>/src/functionminimum.cpp:9:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame =
Processed: refpolicy breaks selint autopkgtest: syntax error, unexpected DASH
Processing control commands: > found -1 refpolicy/2:2.20221101-1 Bug #1024185 [src:refpolicy, src:selint] refpolicy breaks selint autopkgtest: syntax error, unexpected DASH Marked as found in versions refpolicy/2:2.20221101-1. > found -1 selint/1.2.1-1 Bug #1024185 [src:refpolicy, src:selint] refpolicy breaks selint autopkgtest: syntax error, unexpected DASH Marked as found in versions selint/1.2.1-1. -- 1024185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024185: refpolicy breaks selint autopkgtest: syntax error, unexpected DASH
Source: refpolicy, selint Control: found -1 refpolicy/2:2.20221101-1 Control: found -1 selint/1.2.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of refpolicy the autopkgtest of selint fails in testing when that autopkgtest is run with the binary packages of refpolicy from unstable. It passes when run with only packages from testing. In tabular form: passfail refpolicy from testing2:2.20221101-1 selint from testing1.2.1-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 refpolicy to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=refpolicy https://ci.debian.net/data/autopkgtest/testing/amd64/s/selint/28320913/log.gz Warning: Failed to load modules from selinux-policy-src/modules.conf: 9 kernel.if: 1673: (F): syntax error, unexpected DASH (F-001) 1673 | init_write_mountpoint_files($1, -proc_type) | ^ kernel.if: 1673: (F): Error: Invalid statement (F-001) 1673 | init_write_mountpoint_files($1, -proc_type) | ^ Error: Failed to parse files autopkgtest [09:25:21]: test refpolicy-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1024183: llvm-toolchain-13: autopkgtest regression: /usr/lib/llvm-13/bin/mlir-tblgen doesn't exist
Source: llvm-toolchain-13 Version: 1:13.0.1-9 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of llvm-toolchain-13 the autopkgtest of llvm-toolchain-13 fails in testing when that autopkgtest is run with the binary packages of llvm-toolchain-13 from unstable. It passes when run with only packages from testing. In tabular form: passfail llvm-toolchain-13 from testing1:13.0.1-9 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=llvm-toolchain-13 https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-13/28320845/log.gz -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1535 (message): The imported target "mlir-tblgen" references the file "/usr/lib/llvm-13/bin/mlir-tblgen" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/llvm-13/cmake/LLVMConfig.cmake:300 (include) CMakeLists.txt:3 (find_package) -- Configuring incomplete, errors occurred! See also "/tmp/autopkgtest-lxc.pmp7rkht/downtmp/autopkgtest_tmp/build/CMakeFiles/CMakeOutput.log". autopkgtest [09:20:41]: test cmake-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1024182: ogre-1.9: Do not include in release "bookworm", out of date
Source: ogre-1.9 Version: 1.9.0+dfsg1-12.1 Severity: serious X-Debbugs-Cc: m...@debian.org This package has been outdated for a few years, nowadays 1.12 should be used. It should not be included in the next stable release, bookworm. -- Manuel A. Fernandez Montecelo
Processed: pngcheck: autopkgtest needs update for new version of zlib: warning on stderr
Processing control commands: > affects -1 src:zlib Bug #1024180 [src:pngcheck] pngcheck: autopkgtest needs update for new version of zlib: warning on stderr Added indication that 1024180 affects src:zlib -- 1024180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024036: nipy FTBFS with Python 3.11 as supported version
Control: tags -1 upstream Control: forwarded -1 https://github.com/nipy/nipy/issues/496 Control: severity -1 important Hi, I prepared an upload which reduces nipy python support to python3-dev, currently python3.10, so this fixes the failure to build from source until it comes back to bite us when python3.11 becomes the new default. I reduce the severity in the meantime. Hopefully bringing back support to python3-all-dev will be doable in the end. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/6, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Re: nipy FTBFS with Python 3.11 as supported version
Processing control commands: > tags -1 upstream Bug #1024036 [src:nipy] nipy FTBFS with Python 3.11 as supported version Added tag(s) upstream. > forwarded -1 https://github.com/nipy/nipy/issues/496 Bug #1024036 [src:nipy] nipy FTBFS with Python 3.11 as supported version Set Bug forwarded-to-address to 'https://github.com/nipy/nipy/issues/496'. > severity -1 important Bug #1024036 [src:nipy] nipy FTBFS with Python 3.11 as supported version Severity set to 'important' from 'serious' -- 1024036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024180: pngcheck: autopkgtest needs update for new version of zlib: warning on stderr
Source: pngcheck Version: 3.0.2-2 Severity: serious X-Debbugs-CC: z...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:zlib Dear maintainer(s), With a recent upload of zlib the autopkgtest of pngcheck fails in testing when that autopkgtest is run with the binary packages of zlib from unstable. It passes when run with only packages from testing. In tabular form: passfail zlib from testing1:1.2.13.dfsg-1 pngcheck from testing3.0.2-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Your test *only* fails because of a warning. The default behavior of autopkgtest is to fail when there is output on stderr, unless the allow-stderr restriction is added. In this case, I'd try to avoid the warning altogether, because this is something that can happen easily in Debian. Currently this regression is blocking the migration of zlib to testing [1]. Of course, zlib shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in zlib was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from zlib should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=zlib https://ci.debian.net/data/autopkgtest/testing/amd64/p/pngcheck/28323432/log.gz zlib warning: different version (expected 1.2.11, using 1.2.13) OK: debian/tests/openlogo-nd-100.png (101x124, 8-bit palette, non-interlaced, 88.5%). autopkgtest [11:15:19]: test command2 OpenPGP_signature Description: OpenPGP digital signature
Bug#1024179: zlib breaks libcompress-raw-zlib-perl autopkgtest: 02zlib.t fails
Source: zlib, libcompress-raw-zlib-perl Control: found -1 zlib/1:1.2.13.dfsg-1 Control: found -1 libcompress-raw-zlib-perl/2.202-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of zlib the autopkgtest of libcompress-raw-zlib-perl fails in testing when that autopkgtest is run with the binary packages of zlib from unstable. It passes when run with only packages from testing. In tabular form: passfail zlib from testing1:1.2.13.dfsg-1 libcompress-raw-zlib-perl from testing2.202-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 zlib to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=zlib https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcompress-raw-zlib-perl/28323429/log.gz t/02zlib.t . 1..353 [...] not ok 126 # Failed test (t/02zlib.t at line 498) # got: 1 # expected: -3 ok 127 ok 128 ok 129 ok 130 ok 131 ok 132 ok 133 - expected compressed output not ok 134 # Failed test (t/02zlib.t at line 532) # got: 1 # expected: -3 OpenPGP_signature Description: OpenPGP digital signature
Processed: zlib breaks libcompress-raw-zlib-perl autopkgtest: 02zlib.t fails
Processing control commands: > found -1 zlib/1:1.2.13.dfsg-1 Bug #1024179 [src:zlib, src:libcompress-raw-zlib-perl] zlib breaks libcompress-raw-zlib-perl autopkgtest: 02zlib.t fails Marked as found in versions zlib/1:1.2.13.dfsg-1. > found -1 libcompress-raw-zlib-perl/2.202-1 Bug #1024179 [src:zlib, src:libcompress-raw-zlib-perl] zlib breaks libcompress-raw-zlib-perl autopkgtest: 02zlib.t fails Marked as found in versions libcompress-raw-zlib-perl/2.202-1. -- 1024179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024175: ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1
Source: ruby-omniauth-gitlab Version: 4.0.0-1 Severity: serious X-Debbugs-CC: ruby-omniauth-oau...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-omniauth-oauth2 Dear maintainer(s), With a recent upload of ruby-omniauth-oauth2 the autopkgtest of ruby-omniauth-gitlab fails in testing when that autopkgtest is run with the binary packages of ruby-omniauth-oauth2 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-omniauth-oauth2 from testing1.8.0-1 ruby-omniauth-gitlab from testing4.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 ruby-omniauth-oauth2 to testing [1]. Of course, ruby-omniauth-oauth2 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-omniauth-oauth2 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-omniauth-oauth2 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-omniauth-oauth2 https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-omniauth-gitlab/28323425/log.gz ┌──┐ │ Checking Rubygems dependency resolution on ruby3.0 │ └──┘ GEM_PATH= ruby3.0 -e gem\ \"omniauth-gitlab\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'omniauth-oauth2' (~> 1.7.1) among 119 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' at: /usr/share/rubygems-integration/all/specifications/omniauth-gitlab-4.0.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 'omniauth-oauth2' (~> 1.7.1) - did find: [omniauth-oauth2-1.8.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.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 `' OpenPGP_signature Description: OpenPGP digital signature
Processed: ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1
Processing control commands: > affects -1 src:ruby-omniauth-oauth2 Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1 Added indication that 1024175 affects src:ruby-omniauth-oauth2 -- 1024175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024174: ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1)
Source: ruby-omniauth-dingtalk-oauth2 Version: 1.0.0-2 Severity: serious X-Debbugs-CC: ruby-omniauth-oau...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-omniauth-oauth2 Dear maintainer(s), With a recent upload of ruby-omniauth-oauth2 the autopkgtest of ruby-omniauth-dingtalk-oauth2 fails in testing when that autopkgtest is run with the binary packages of ruby-omniauth-oauth2 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-omniauth-oauth2from testing1.8.0-1 ruby-omniauth-dingtalk-oauth2 from testing1.0.0-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 ruby-omniauth-oauth2 to testing [1]. Of course, ruby-omniauth-oauth2 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-omniauth-oauth2 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-omniauth-oauth2 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-omniauth-oauth2 https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-omniauth-dingtalk-oauth2/28323424/log.gz ┌──┐ │ Checking Rubygems dependency resolution on ruby3.0 │ └──┘ GEM_PATH= ruby3.0 -e gem\ \"omniauth-dingtalk-oauth2\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'omniauth-oauth2' (~> 1.7.1) among 105 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' at: /usr/share/rubygems-integration/all/specifications/omniauth-dingtalk-oauth2-1.0.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 'omniauth-oauth2' (~> 1.7.1) - did find: [omniauth-oauth2-1.8.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.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.0) benchmark (default: 0.1.1) bigdecimal (default: 3.0.0) bundler (default: 2.2.33) cgi (default: 0.2.1) csv (default: 3.1.9) date (default: 3.1.3) dbm (default: 1.1.0) debug (default: 0.2.1) delegate (default: 0.2.0) did_you_mean (default: 1.5.0) digest (default: 3.0.0) drb (default: 2.0.5) english (default: 0.7.1) erb (default: 2.2.0) etc
Processed: ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1)
Processing control commands: > affects -1 src:ruby-omniauth-oauth2 Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1) Added indication that 1024174 affects src:ruby-omniauth-oauth2 -- 1024174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024173: python-cfg-diag breaks remrun autopkgtest: 'Config' object has no attribute 'diag_'
Source: python-cfg-diag, remrun
Control: found -1 python-cfg-diag/0.4.0-1
Control: found -1 remrun/0.2.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-cfg-diag the autopkgtest of remrun fails
in testing when that autopkgtest is run with the binary packages of
python-cfg-diag from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-cfg-diagfrom testing0.4.0-1
remrun from testing0.2.2-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 python-cfg-diag
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-cfg-diag
https://ci.debian.net/data/autopkgtest/testing/amd64/r/remrun/28323415/log.gz
=== python3.10
. at 0x7f449f1f8ee0>
. at 0x7f449f1f8ee0>
. at 0x7f449f1f8ee0>
. at 0x7f449f1f8ee0>
Generating public/private ed25519 key pair.
Your identification has been saved in
/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/run_sshd_test.rn9f88xi/server/ssh_host_key
Your public key has been saved in
/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/run_sshd_test.rn9f88xi/server/ssh_host_key.pub
The key fingerprint is:
SHA256:WLaSGvQdL24ckYIBGqnsuMOZNQVVvPUoqDwIb6Rcu5Y root@ci-319-53d9076c
The key's randomart image is:
+--[ED25519 256]--+
|o.o. |
|.o . o . o |
|+ + o O o |
|o..o + X * . |
|=++ = = S . |
|o+oB o + o |
|.o+ * +|
|o+ E . |
| .. |
+[SHA256]-+
. at 0x7f449f1f8ee0>
Generating public/private ed25519 key pair.
Your identification has been saved in
/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/run_sshd_test.rn9f88xi/home/.ssh/id
Your public key has been saved in
/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/run_sshd_test.rn9f88xi/home/.ssh/id.pub
The key fingerprint is:
SHA256:Zla0mYWTO4tlZOdxJgCfm6yhAj85yJ386oHz2XF3uSc root@ci-319-53d9076c
The key's randomart image is:
+--[ED25519 256]--+
|..o+.|
| o**+ o |
| oB= = |
| o=o.|
| . S++o |
| . B o =.o. . |
| = @ o o . o|
| o O o . .E.. |
| .=.o .o |
+[SHA256]-+
. at 0x7f449f1f8ee0>
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File
"/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/tests/python/run_sshd_test/__main__.py",
line 543, in
main()
File
"/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/tests/python/run_sshd_test/__main__.py",
line 525, in main
ssh_cfg = create_ssh_config(cfg, addr, port, tempd)
File
"/tmp/autopkgtest-lxc.w6kc1nuq/downtmp/build.5Lm/src/tests/python/run_sshd_test/__main__.py",
line 172, in create_ssh_config
cfg.diag_("Copying the client public key to the authorized keys file")
AttributeError: 'Config' object has no attribute 'diag_'. Did you mean:
'diag'?
autopkgtest [11:15:18]: test upstream-sshd-simple
OpenPGP_signature
Description: OpenPGP digital signature
Processed: python-cfg-diag breaks remrun autopkgtest: 'Config' object has no attribute 'diag_'
Processing control commands: > found -1 python-cfg-diag/0.4.0-1 Bug #1024173 [src:python-cfg-diag, src:remrun] python-cfg-diag breaks remrun autopkgtest: 'Config' object has no attribute 'diag_' Marked as found in versions python-cfg-diag/0.4.0-1. > found -1 remrun/0.2.2-1 Bug #1024173 [src:python-cfg-diag, src:remrun] python-cfg-diag breaks remrun autopkgtest: 'Config' object has no attribute 'diag_' Marked as found in versions remrun/0.2.2-1. -- 1024173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023789: marked as done (thunderbird: FTBFS: error: no matching function for call to 'arc4random_buf')
Your message dated Tue, 15 Nov 2022 20:34:11 + with message-id and subject line Bug#1023789: fixed in thunderbird 1:102.5.0-1 has caused the Debian Bug report #1023789, regarding thunderbird: FTBFS: error: no matching function for call to 'arc4random_buf' 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.) -- 1023789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thunderbird Version: 1:102.4.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=thunderbird=amd64=1%3A102.4.1-1%2Bb1=1668054836=0 /usr/bin/clang++ -std=gnu++17 -o exploitability_win.o -c -I/<>/obj-thunderbird/dist/system_wrappers -include /<>/config/gcc_hidden.h -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fstack-clash-protection -DNDEBUG=1 -DTRIMMED=1 -DBPLOG_MINIMUM_SEVERITY=SEVERITY_CRITICAL -DNO_STABS_SUPPORT -I/<>/toolkit/crashreporter/google-breakpad/src/processor -I/<>/obj-thunderbird/toolkit/crashreporter/google-breakpad/src/processor -I/<>/toolkit/crashreporter/breakpad-client -I/<>/toolkit/crashreporter/google-breakpad/src -I/<>/obj-thunderbird/dist/include -I/usr/include/nspr -I/usr/include/nss -I/usr/include/nspr -I/<>/obj-thunderbird/dist/include/nss -DMOZILLA_CLIENT -include /<>/obj-thunderbird/mozilla-config.h -Qunused-arguments -Wdate-time -D_FORTIFY_SOURCE=2 -Qunused-arguments -Wall -Wbitfield-enum-conversion -Wdeprecated-this-capture -Wempty-body -Wformat-type-confusion -Wignored-qualifiers -Wpointer-arith -Wshadow-field-in-constructor-modified -Wsign-compare -Wtype-limits -Wno-error=tautological-type-limit-compare -Wunreachable-code -Wunreachable-code-return -Wunused-but-set-parameter -Wno-invalid-offsetof -Wclass-varargs -Wempty-init-stmt -Wfloat-overflow-conversion -Wfloat-zero-conversion -Wloop-analysis -Wno-range-loop-analysis -Wc++2a-compat -Wcomma -Wenum-compare-conditional -Wimplicit-fallthrough -Wstring-conversion -Wno-inline-new-delete -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=backend-plugin -Wno-error=free-nonheap-object -Wno-error=return-std-move -Wno-error=atomic-alignment -Wno-error=deprecated-copy -Wformat -Wformat-security -Wno-gnu-zero-variadic-macro-arguments -Wno-psabi -Wthread-safety -Wno-unknown-warning-option -fno-sized-deallocation -fno-aligned-new -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-exceptions -fPIC -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -gdwarf-4 -O2 -fomit-frame-pointer -funwind-tables -Wno-unused-local-typedefs -Wno-deprecated-declarations -Wno-bool-compare -Wno-unused-but-set-variable -Wno-c++11-narrowing -Wno-implicit-fallthrough -fno-strict-aliasing -ffp-contract=off -MD -MP -MF .deps/exploitability_win.o.pp /<>/toolkit/crashreporter/google-breakpad/src/processor/exploitability_win.cc toolkit/crashreporter/google-breakpad/src/processor/Unified_cpp_src_processor0.o In file included from Unified_cpp_client0.cpp:47: /<>/toolkit/crashreporter/client/ping.cpp:56:3: error: no matching function for call to 'arc4random_buf' arc4random_buf(id, sizeof(UUID)); ^~ /usr/include/stdlib.h:542:13: note: candidate function not viable: no known conversion from 'CrashReporter::UUID' to 'void *' for 1st argument; take the address of the argument with & extern void arc4random_buf (void *__buf, size_t __size) ^ 1 error generated. make[5]: *** [/<>/config/rules.mk:669: Unified_cpp_client0.o] Error 1 make[5]: Leaving directory '/<>/obj-thunderbird/toolkit/crashreporter/client' make[4]: *** [/<>/config/recurse.mk:72: toolkit/crashreporter/client/target-objects] Error 2 make[4]: *** Waiting for unfinished jobs Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: thunderbird Source-Version: 1:102.5.0-1 Done: Carsten Schoenert We believe that the bug you reported is fixed in the latest version of thunderbird, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated thunderbird
Bug#1024171: diffoscope: autopkgtest regression: 'NoneType' object has no attribute 'add_comment'
Source: diffoscope
Version: 226
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of diffoscope the autopkgtest of diffoscope fails
in testing when that autopkgtest is run with the binary packages of
diffoscope from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
diffoscope from testing226
versioned deps [0] 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 to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
diffoscope/226. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=diffoscope
https://ci.debian.net/data/autopkgtest/testing/amd64/d/diffoscope/28319467/log.gz
=== FAILURES
===
_ test_no_differences
__
self = <
/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html>
other = <
/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html>
source = None
def compare(self, other, source=None):
difference = super().compare(other, source)
# Show text-only differences as a sub-diff.
try:
text = Difference.from_operation(Htmltotext, self.path, other.path)
__class__ =
difference = None
other = <
/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html>
self = <
/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html>
source = None
/usr/lib/python3/dist-packages/diffoscope/comparators/html.py:44: _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
klass =
path1 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
path2 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
args = (), kwargs = {}
@staticmethod
def from_operation(klass, path1, path2, *args, **kwargs):
return Difference.from_operation_exc(
klass, path1, path2, *args, **kwargs
)[0]
args = ()
klass =
kwargs = {}
path1 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
path2 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
/usr/lib/python3/dist-packages/diffoscope/difference.py:267: _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
klass =
path1 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
path2 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
args = (), kwargs = {}, ignore_returncodes = ()
operation_and_feeder = Difference.from_operation_exc..operation_and_feeder at
0x7f3447054a60>
@staticmethod
def from_operation_exc(klass, path1, path2, *args, **kwargs):
operation_args = kwargs.pop("operation_args", [])
ignore_returncodes = kwargs.pop("ignore_returncodes", ())
def operation_and_feeder(path):
operation = None
if path == "/dev/null":
feeder = feeders.empty()
else:
operation = klass(path, *operation_args)
feeder = feeders.from_operation(operation)
if operation_excluded(operation.full_name()):
return None, None, True
operation.start()
return feeder, operation, False
> feeder1, operation1, excluded1 = operation_and_feeder(path1)
args = ()
ignore_returncodes = ()
klass =
kwargs = {}
operation_and_feeder = Difference.from_operation_exc..operation_and_feeder at
0x7f3447054a60>
operation_args = []
path1 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
path2 =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
/usr/lib/python3/dist-packages/diffoscope/difference.py:288: _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
path =
'/tmp/autopkgtest-lxc.0soup5pu/downtmp/autopkgtest_tmp/tests/data/test1.html'
def operation_and_feeder(path):
operation = None
if path == "/dev/null":
feeder = feeders.empty()
else:
operation = klass(path, *operation_args)
feeder =
Bug#1024170: mcl breaks roary autopkgtest: different output
Source: mcl, roary Control: found -1 mcl/1:22-282+ds-1 Control: found -1 roary/3.13.0+dfsg-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of mcl the autopkgtest of roary fails in testing when that autopkgtest is run with the binary packages of mcl from unstable. It passes when run with only packages from testing. In tabular form: passfail mclfrom testing1:22-282+ds-1 roary from testing3.13.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 mcl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=mcl https://ci.debian.net/data/autopkgtest/testing/amd64/r/roary/28320848/log.gz Use of uninitialized value in require at /usr/share/perl5/HTTP/Headers.pm line 302. Use of uninitialized value in require at /usr/lib/x86_64-linux-gnu/perl/5.36/Encode.pm line 70. Please cite Roary if you use any of the results it produces: Andrew J. Page, Carla A. Cummins, Martin Hunt, Vanessa K. Wong, Sandra Reuter, Matthew T. G. Holden, Maria Fookes, Daniel Falush, Jacqueline A. Keane, Julian Parkhill, "Roary: Rapid large-scale prokaryote pan genome analysis", Bioinformatics, 2015 Nov 15;31(22):3691-3693 doi: http://doi.org/10.1093/bioinformatics/btv421 Pubmed: 26198102 2022/11/15 09:16:56 Cannot find the mcxdeblast executable, please ensure its in your PATH 2,6c2,6 < out/_blast_results < out/_clustered < out/_clustered.clstr < out/_combined_files < out/_combined_files.groups --- out/accessory.header.embl out/accessory.tab out/accessory_binary_genes.fa out/accessory_binary_genes.fa.newick out/accessory_graph.dot 7a8,18 out/clustered_proteins out/core_accessory.header.embl out/core_accessory.tab out/core_accessory_graph.dot out/gene_presence_absence.Rtab out/gene_presence_absence.csv out/number_of_conserved_genes.Rtab out/number_of_genes_in_pan_genome.Rtab out/number_of_new_genes.Rtab out/number_of_unique_genes.Rtab out/summary_statistics.txt autopkgtest [09:16:57]: test test-installed OpenPGP_signature Description: OpenPGP digital signature
Processed: mcl breaks roary autopkgtest: different output
Processing control commands: > found -1 mcl/1:22-282+ds-1 Bug #1024170 [src:mcl, src:roary] mcl breaks roary autopkgtest: different output Marked as found in versions mcl/1:22-282+ds-1. > found -1 roary/3.13.0+dfsg-1 Bug #1024170 [src:mcl, src:roary] mcl breaks roary autopkgtest: different output Marked as found in versions roary/3.13.0+dfsg-1. -- 1024170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1023848: kodi-pvr-hts: Packet requires kodi-api-pvr but is not available in sid
Processing control commands: > close -1 Bug #1023848 [kodi-pvr-hts] kodi-pvr-hts: Packet requires kodi-api-pvr but is not available in sid Marked Bug as done -- 1023848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023848: kodi-pvr-hts: Packet requires kodi-api-pvr but is not available in sid
Control: close -1 Hi Leela, The new versions of addons are uploaded to sid and will be built overnight. I am closing this bug in hope the api version mismatch is now resolved. Please re-open this bug if it is not the case! -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Bug#1018203: marked as done (kodi-inputstream-adaptive: FTBFS on ppc64el (regression in endian detection))
Your message dated Tue, 15 Nov 2022 19:54:25 + with message-id and subject line Bug#1018203: fixed in kodi-inputstream-adaptive 20.3.1+ds1-1 has caused the Debian Bug report #1018203, regarding kodi-inputstream-adaptive: FTBFS on ppc64el (regression in endian detection) 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.) -- 1018203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kodi-inputstream-adaptive Version: 20.2.0+ds1-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Hi Vasyl, The kodi-inputstream-adaptive package is failing to build on ppc64el in Debian because it fails to detect the endianness of the platform. The attached patch fixes this build failure by making use of the general-purpose macros that are exported by default by gcc. (This also fixes the build on riscv64, which is not a release architecture in Debian but is in Ubuntu.) Please consider applying this patch in Debian. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs --- kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs 1969-12-31 16:00:00.0 -0800 +++ kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs 2022-08-26 14:04:30.0 -0700 @@ -0,0 +1,18 @@ +Description: fix endian detection to be portable to all gcc archs +Author: Steve Langasek +Last-Update: 2022-08-26 +Forwarded: no + +Index: kodi-inputstream-adaptive-20.2.0+ds1/bento4-embedded/Source/C++/Core/Ap4Config.h +=== +--- kodi-inputstream-adaptive-20.2.0+ds1.orig/bento4-embedded/Source/C++/Core/Ap4Config.h kodi-inputstream-adaptive-20.2.0+ds1/bento4-embedded/Source/C++/Core/Ap4Config.h +@@ -56,7 +56,7 @@ + #if defined(_M_IX86) || defined(_M_X64) || defined(_M_ARM) || defined(_M_ARM64) + #define AP4_PLATFORM_BYTE_ORDER AP4_PLATFORM_BYTE_ORDER_LITTLE_ENDIAN + #endif +-#elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) || defined(__arm64__) || defined(__aarch64__) ++#elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) || defined(__arm64__) || defined(__aarch64__) || (__BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__) + #define AP4_PLATFORM_BYTE_ORDER AP4_PLATFORM_BYTE_ORDER_LITTLE_ENDIAN + #endif + #endif diff -Nru kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series --- kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series 2022-08-04 00:19:38.0 -0700 +++ kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series 2022-08-26 13:54:03.0 -0700 @@ -1,2 +1,3 @@ 0001-Use-packaged-libwebm.patch 0002-CVE-2019-17452-2021-32265-etc.patch +byte-order-all-archs --- End Message --- --- Begin Message --- Source: kodi-inputstream-adaptive Source-Version: 20.3.1+ds1-1 Done: Vasyl Gello We believe that the bug you reported is fixed in the latest version of kodi-inputstream-adaptive, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vasyl Gello (supplier of updated kodi-inputstream-adaptive 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, 16 Oct 2022 05:43:00 + Source: kodi-inputstream-adaptive Architecture: source Version: 20.3.1+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Vasyl Gello Closes: 1018203 Changes: kodi-inputstream-adaptive (20.3.1+ds1-1) unstable; urgency=medium . * New upstream version 20.3.1+ds1 * d/watch: Switch to git tags *
Bug#1004783: marked as done (kodi-inputstream-ffmpegdirect: FTBFS in ffmpeg 5.0)
Your message dated Tue, 15 Nov 2022 19:54:34 +
with message-id
and subject line Bug#1004783: fixed in kodi-inputstream-ffmpegdirect
20.5.0+ds1-1
has caused the Debian Bug report #1004783,
regarding kodi-inputstream-ffmpegdirect: FTBFS in ffmpeg 5.0
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.)
--
1004783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi-inputstream-ffmpegdirect
Version: 19.0.0+ds1-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0
kodi-inputstream-ffmpegdirect FTBFS with ffmpeg 5.0 in experimental:
[ 62%] Building CXX object
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o
/usr/lib/ccache/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON
-DFFMPEGDIRECT_VERSION=19.0.0 -Dinputstream_ffmpegdirect_EXPORTS -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DTARGET_POSIX
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1
-std=c++14 -MD -MT
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -MF
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o.d -o
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -c
/<>/src/stream/TimeshiftStream.cpp
In file included from /<>/src/stream/FFmpegStream.h:13,
from /<>/src/stream/FFmpegStream.cpp:8:
/<>/src/stream/DemuxStream.h:36:7: warning:
‘ffmpegdirect::DemuxStream’ declared with greater visibility than the type of
its field ‘ffmpegdirect::DemuxStream::cryptoSession’ [-Wattributes]
36 | class DemuxStream
| ^~~
In file included from /<>/src/stream/FFmpegStream.h:14,
from /<>/src/stream/FFmpegStream.cpp:8:
/<>/src/stream/CurlInput.h:23:7: warning:
‘ffmpegdirect::CurlInput’ declared with greater visibility than the type of its
field ‘ffmpegdirect::CurlInput::m_pFile’ [-Wattributes]
23 | class CurlInput
| ^
/<>/src/stream/FFmpegStream.cpp: In member function ‘bool
ffmpegdirect::FFmpegStream::Open(bool)’:
/<>/src/stream/FFmpegStream.cpp:684:37: error: invalid conversion
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
684 | iformat = av_find_input_format("mpeg");
| ^~~~
| |
| const AVInputFormat*
/<>/src/stream/FFmpegStream.cpp:686:37: error: invalid conversion
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
686 | iformat = av_find_input_format("mpeg");
| ^~~~
| |
| const AVInputFormat*
/<>/src/stream/FFmpegStream.cpp:688:37: error: invalid conversion
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
688 | iformat = av_find_input_format("mpegts");
| ^~
| |
| const AVInputFormat*
/<>/src/stream/FFmpegStream.cpp:690:37: error: invalid conversion
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
690 | iformat = av_find_input_format("mjpeg");
| ^
| |
| const AVInputFormat*
/<>/src/stream/FFmpegStream.cpp:737:40: error: assignment of
member ‘AVInputFormat::flags’ in read-only object
737 | m_pFormatContext->iformat->flags |= AVFMT_NOGENSEARCH;
|^
/<>/src/stream/FFmpegStream.cpp:789:30: error:
‘AVFMT_FLAG_KEEP_SIDE_DATA’ was not declared in this scope
789 | m_pFormatContext->flags |= AVFMT_FLAG_KEEP_SIDE_DATA;
| ^
/<>/src/stream/FFmpegStream.cpp:831:72: error: ‘AVStream’ {aka
‘struct AVStream’} has no member named ‘codec_info_nb_frames’
831 | if
Processed: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Processing control commands: > found -1 csound/1:6.18.0+dfsg-2 Bug #1024169 [src:csound, src:csound-plugins] csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated Marked as found in versions csound/1:6.18.0+dfsg-2. > found -1 csound-plugins/1.0.2~dfsg1-2 Bug #1024169 [src:csound, src:csound-plugins] csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated Marked as found in versions csound-plugins/1.0.2~dfsg1-2. -- 1024169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Source: csound, csound-plugins Control: found -1 csound/1:6.18.0+dfsg-2 Control: found -1 csound-plugins/1.0.2~dfsg1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of csound the autopkgtest of csound-plugins fails in testing when that autopkgtest is run with the binary packages of csound from unstable. It passes when run with only packages from testing. In tabular form: passfail csound from testing1:6.18.0+dfsg-2 csound-plugins from testing1.0.2~dfsg1-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 csound to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=csound https://ci.debian.net/data/autopkgtest/testing/arm64/c/csound-plugins/28320936/log.gz *** stack smashing detected ***: terminated csound command: Aborted csound command: Segmentation fault autopkgtest [17:15:52]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1024168: cruft-ng: autopkgtest failure: /usr/libexec/cruft/init-system-helpers: 4: file: not found
Source: cruft-ng Version: 0.9.47 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package cruft-ng, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=cruft-ng https://ci.debian.net/data/autopkgtest/testing/amd64/c/cruft-ng/27781367/log.gz /usr/libexec/cruft/init-system-helpers: 4: file: not found cruft report: Wed Nov 2 09:12:53 2022 missing: dpkg unexplained: / /etc/apt/apt.conf.d/02periodic /etc/apt/apt.conf.d/75retry /etc/apt/apt.conf.d/90always-include-phased-updates /etc/apt/apt.conf.d/90nolanguages /etc/apt/apt.conf.d/90retry /etc/apt/preferences.d/autopkgtest-default-release /etc/apt/preferences.d/autopkgtest-unstable /etc/apt/sources.list.d/autopkgtest-add-apt-release-unstable.list /etc/dpkg/dpkg.cfg.d/autopkgtest /etc/inittab /etc/rc0.d/K01hwclock.sh /etc/rc0.d/K01networking /etc/rc2.d/S01dbus /etc/rc2.d/S01ssh /etc/rc3.d/S01dbus /etc/rc3.d/S01ssh /etc/rc4.d/S01dbus /etc/rc4.d/S01ssh /etc/rc5.d/S01dbus /etc/rc5.d/S01ssh /etc/rc6.d/K01hwclock.sh /etc/rc6.d/K01networking /etc/rcS.d/K01hwclock.sh /etc/rcS.d/S01networking /etc/rcS.d/S01procps /etc/runit/runsvdir/default/ssh /selinux /selinux/enforce /usr/local/lib/python3.10 /usr/local/lib/python3.10/dist-packages /usr/sbin/autopkgtest-reboot /var/lib/python /var/lib/python/python3.10_installed /var/log/bootstrap.log /var/tmp/debci.pkg end. autopkgtest [09:12:54]: test basic OpenPGP_signature Description: OpenPGP digital signature
Bug#1024166: blist: dead upstream, no maintainer upload since 2015
Package: src:blist Severity: serious X-Debbugs-CC: s...@debian.org Hi, The blist package, currently team-maintained by the Debian Python Team, has not been updated by its maintainer since 2015. 4 uploads fixing either important bugs, or making sure it respects the DPT policy have been made since then. As such, I consider this package is not currently maintained by anyone, and thus violates the DPT policy. Moreover, blist is dead upstream: no commit has been made to the project since 2014. This is problematic, as we are now carrying patches for Python 3.9, 3.10 and 3.11. As such, I don't think this package should make it to Bookworm. It probably should eventually be RMed too. I'm CC-ing Sebastien Delafond explicitly, as he seems to be the maintainer of all the packages in the archive that depend or build-depend on blist (python-raccoon, python-panwid, elastalert). In a perfect world, those packages should migrate away from blist in time for the freeze. If not possible, it would be nice if it could have an active maintainer again. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1023620: marked as done (new upstream required for pgcli)
Your message dated Tue, 15 Nov 2022 19:20:36 + with message-id and subject line Bug#1015148: fixed in python-pgspecial 2.0.1-1 has caused the Debian Bug report #1015148, regarding new upstream required for pgcli 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.) -- 1015148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pgspecial Version: 1.11.10+dfsg1-2 Hi, thank you for maintaining python-pgspecial in Debian. Could you please update it to the current upstream version (1.13.0) that has been ported to psycopg3. The current relases of pgcli require this and are unfortunately broken until python-pgspecial is updated. As you might know, python-pgspecial is prominently used by pgcli, one of the "dbcli"/prompt-toolkit programs which I'm maintaining all of them in Debian. Since I'm uploading all of them "together" in sync, except for python-pgspecial, it might make sense that I could also upload python-pgspecial to keep the roundtrips short, what do you think? Regards, Daniel --- End Message --- --- Begin Message --- Source: python-pgspecial Source-Version: 2.0.1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-pgspecial, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-pgspecial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 19:39:33 +0100 Source: python-pgspecial Architecture: source Version: 2.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1015148 Changes: python-pgspecial (2.0.1-1) unstable; urgency=medium . * Team upload. * New upstream version 2.0.1 (Closes: #1015148). * Replace CI config with central file. Checksums-Sha1: a1e586c990cf86708230af69dd41507c812b83e1 1959 python-pgspecial_2.0.1-1.dsc 20af39d6bbd44cd8b694191c39d995fe8328f610 49682 python-pgspecial_2.0.1.orig.tar.gz 015659eabc6aa36cf537f4a5cff1cede5d03e0fe 3016 python-pgspecial_2.0.1-1.debian.tar.xz 6b4e95c48908cd35058f62d40f1760e67ecb31bf 6331 python-pgspecial_2.0.1-1_source.buildinfo Checksums-Sha256: 0d58d97bc2d68d89dd93115c73e0e5870a296fce13faf74832bcc4fe38fa0b45 1959 python-pgspecial_2.0.1-1.dsc 64443bbc9ad09b57d0f4dcbb38eff44d52853b7418c9ea52f5857abe1bb534ec 49682 python-pgspecial_2.0.1.orig.tar.gz 972a414c470bd65e61c31d21396b16358994c9f0bfaeda4cee6edb41a67393b4 3016 python-pgspecial_2.0.1-1.debian.tar.xz c212bea370e3ef9a3e30e99269c5c156462ae16631f31a5c989d45df126386bb 6331 python-pgspecial_2.0.1-1_source.buildinfo Files: 166128693926ec98b879b423914508d1 1959 python optional python-pgspecial_2.0.1-1.dsc 4816d89987052bcbd7657baa6f1f080e 49682 python optional python-pgspecial_2.0.1.orig.tar.gz 514bbe3b811dd8e779f971afa1dd1e82 3016 python optional python-pgspecial_2.0.1-1.debian.tar.xz 4be3bb841284866134accd89b80f2bb6 6331 python optional python-pgspecial_2.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNz4r0QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFG8YC/93O1GOMhHAlxnAaO5DCc+Z4uWT96U06LQg pHvfDu+SqhvA37NXJkrTA5P1jqHjJnuIsdWxsY2czftL2H1uDTkWiGOzioZEz4tL XMahD/Dc65ri8Jaq+YIW2LnLmMDkr2xSsjh395JNy6dxaT6SiVR+qxPBovL67fXE qcH46sot04ZVzVcvphBOkgSIVnFzlRjj1c8Tg2ODoVO7lLhfWulUp6PfPB3lwnjP N0XBk2ML9t26fhP80ho37mdfNpAVl/oX2A6BF+1a27OGL+1dkmMtZNYfZ/sGYexP oQGpjFEPUBzYAaHk8yDBHE5LXkerW2i01fSp7tFALNqgSedtqSeche1lnOhG6Bpd TbQzpcJMG6A3w+uI/HfcNcIweYN+oP6FqJPHo+QEXHEQkeiHUroft6QRAelE5QwV 0D0P0DvehMzHQyD7oJW/HlJuypGdsIrIFHewBRq1N7FWzV3X/6MLe5NGxxRveofG gZMCH9umaMo2jMI+ksrCyqTAZ7IFcBE= =ympP -END PGP SIGNATURE End Message ---
Bug#1015148: marked as done (new upstream (2.x))
Your message dated Tue, 15 Nov 2022 19:20:36 + with message-id and subject line Bug#1015148: fixed in python-pgspecial 2.0.1-1 has caused the Debian Bug report #1015148, regarding new upstream (2.x) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pgspecial Hi, thank you for maintaining python-pgspecial in Debian. While I happen to maintain all other packages from dbcli in Debian, I noticed, that pgspecial is rather outdated. Would you mind updating it to the current upstream release? Just in case, I'm happy to help out if you'd like. Regards, Daniel --- End Message --- --- Begin Message --- Source: python-pgspecial Source-Version: 2.0.1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-pgspecial, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-pgspecial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 19:39:33 +0100 Source: python-pgspecial Architecture: source Version: 2.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1015148 Changes: python-pgspecial (2.0.1-1) unstable; urgency=medium . * Team upload. * New upstream version 2.0.1 (Closes: #1015148). * Replace CI config with central file. Checksums-Sha1: a1e586c990cf86708230af69dd41507c812b83e1 1959 python-pgspecial_2.0.1-1.dsc 20af39d6bbd44cd8b694191c39d995fe8328f610 49682 python-pgspecial_2.0.1.orig.tar.gz 015659eabc6aa36cf537f4a5cff1cede5d03e0fe 3016 python-pgspecial_2.0.1-1.debian.tar.xz 6b4e95c48908cd35058f62d40f1760e67ecb31bf 6331 python-pgspecial_2.0.1-1_source.buildinfo Checksums-Sha256: 0d58d97bc2d68d89dd93115c73e0e5870a296fce13faf74832bcc4fe38fa0b45 1959 python-pgspecial_2.0.1-1.dsc 64443bbc9ad09b57d0f4dcbb38eff44d52853b7418c9ea52f5857abe1bb534ec 49682 python-pgspecial_2.0.1.orig.tar.gz 972a414c470bd65e61c31d21396b16358994c9f0bfaeda4cee6edb41a67393b4 3016 python-pgspecial_2.0.1-1.debian.tar.xz c212bea370e3ef9a3e30e99269c5c156462ae16631f31a5c989d45df126386bb 6331 python-pgspecial_2.0.1-1_source.buildinfo Files: 166128693926ec98b879b423914508d1 1959 python optional python-pgspecial_2.0.1-1.dsc 4816d89987052bcbd7657baa6f1f080e 49682 python optional python-pgspecial_2.0.1.orig.tar.gz 514bbe3b811dd8e779f971afa1dd1e82 3016 python optional python-pgspecial_2.0.1-1.debian.tar.xz 4be3bb841284866134accd89b80f2bb6 6331 python optional python-pgspecial_2.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNz4r0QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFG8YC/93O1GOMhHAlxnAaO5DCc+Z4uWT96U06LQg pHvfDu+SqhvA37NXJkrTA5P1jqHjJnuIsdWxsY2czftL2H1uDTkWiGOzioZEz4tL XMahD/Dc65ri8Jaq+YIW2LnLmMDkr2xSsjh395JNy6dxaT6SiVR+qxPBovL67fXE qcH46sot04ZVzVcvphBOkgSIVnFzlRjj1c8Tg2ODoVO7lLhfWulUp6PfPB3lwnjP N0XBk2ML9t26fhP80ho37mdfNpAVl/oX2A6BF+1a27OGL+1dkmMtZNYfZ/sGYexP oQGpjFEPUBzYAaHk8yDBHE5LXkerW2i01fSp7tFALNqgSedtqSeche1lnOhG6Bpd TbQzpcJMG6A3w+uI/HfcNcIweYN+oP6FqJPHo+QEXHEQkeiHUroft6QRAelE5QwV 0D0P0DvehMzHQyD7oJW/HlJuypGdsIrIFHewBRq1N7FWzV3X/6MLe5NGxxRveofG gZMCH9umaMo2jMI+ksrCyqTAZ7IFcBE= =ympP -END PGP SIGNATURE End Message ---
Processed: src:gmsh: unsatisfied build dependency in testing: libgmm++-dev
Processing control commands: > block -1 by 1023788 Bug #1024164 [src:gmsh] src:gmsh: unsatisfied build dependency in testing: libgmm++-dev 1024164 was not blocked by any bugs. 1024164 was not blocking any bugs. Added blocking bug(s) of 1024164: 1023788 -- 1024164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024164: src:gmsh: unsatisfied build dependency in testing: libgmm++-dev
Source: gmsh Version: 4.8.4+ds2-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Control: block -1 by 1023788 Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. In this case, src:getfem took over from src:getfem++ but it is blocked because if fails to build from source on s390x, see bug #1023788. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1024163: src:freefem++: unsatisfied build dependency in testing: libgmm++-dev
Source: freefem++ Version: 4.11+dfsg1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Control: block -1 by 1023788 Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. In this case, src:getfem took over from src:getfem++ but it is blocked because if fails to build from source on s390x, see bug #1023788. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Processed: src:freefem++: unsatisfied build dependency in testing: libgmm++-dev
Processing control commands: > block -1 by 1023788 Bug #1024163 [src:freefem++] src:freefem++: unsatisfied build dependency in testing: libgmm++-dev 1024163 was not blocked by any bugs. 1024163 was not blocking any bugs. Added blocking bug(s) of 1024163: 1023788 -- 1024163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:csound-plugins: unsatisfied build dependency in testing: libgmm++-dev
Processing control commands: > block -1 by 1023788 Bug #1024162 [src:csound-plugins] src:csound-plugins: unsatisfied build dependency in testing: libgmm++-dev 1024162 was not blocked by any bugs. 1024162 was not blocking any bugs. Added blocking bug(s) of 1024162: 1023788 -- 1024162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024162: src:csound-plugins: unsatisfied build dependency in testing: libgmm++-dev
Source: csound-plugins Version: 1.0.2~dfsg1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Control: block -1 by 1023788 Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. In this case, src:getfem took over from src:getfem++ but it is blocked because if fails to build from source on s390x, see bug #1023788. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1023905: marked as done (blist FTBFS with Python 3.11 as supported version)
Your message dated Tue, 15 Nov 2022 19:19:10 + with message-id and subject line Bug#1023905: fixed in blist 1.3.6-9 has caused the Debian Bug report #1023905, regarding blist 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.) -- 1023905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blist Version: 1.3.6-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=blist=1.3.6-8%2Bb2 ... blist/_blist.c: In function ‘py_blist_sort’: blist/_blist.c:6597:25: error: lvalue required as left operand of assignment 6597 | Py_TYPE() = _Type; | ^ blist/_blist.c: In function ‘init_blist_types1’: blist/_blist.c:7384:32: error: lvalue required as left operand of assignment 7384 | Py_TYPE(_Type) = _Type; |^ blist/_blist.c:7385:36: error: lvalue required as left operand of assignment 7385 | Py_TYPE(_Type) = _Type; |^ blist/_blist.c:7386:36: error: lvalue required as left operand of assignment 7386 | Py_TYPE(_Type) = _Type; |^ blist/_blist.c:7387:43: error: lvalue required as left operand of assignment 7387 | Py_TYPE(_Type) = _Type; | ^ 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: blist Source-Version: 1.3.6-9 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of blist, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated blist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 20:56:33 +0200 Source: blist Architecture: source Version: 1.3.6-9 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1023905 Changes: blist (1.3.6-9) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. . [ Debian Janitor ] * Set field Upstream-Name in debian/copyright. * Update standards version to 4.6.1, no changes needed. . [ Stefano Rivera ] * Patch: Python 3.11 support (Closes: #1023905). Checksums-Sha1: b89e91d967df942da9b1a55f52e1eed94eacaffd 1377 blist_1.3.6-9.dsc e3e4e7af46df64135dc6ca9f8266a49cb0abdfb4 7580 blist_1.3.6-9.debian.tar.xz 663d52062e26180139049de5403851544d539ca9 6389 blist_1.3.6-9_source.buildinfo Checksums-Sha256: 404845e00093ce25e9c6f099cba05cea4a27f1e37d071801689cab67ccd7b0e7 1377 blist_1.3.6-9.dsc 5182ee6e88e1c4f90fbda4614ad870a619ed48f4cda23bfd0585e5e2dad85cfb 7580 blist_1.3.6-9.debian.tar.xz 0b1a5fd39a9dde8136eb969f01f0347428c4d7c850d342b2eb8a7d5b2dfb7d5a 6389 blist_1.3.6-9_source.buildinfo Files: 7c299b4180f36cb4b103ffeb92db92c7 1377 python optional blist_1.3.6-9.dsc 3a8eb1754573e845d279c8e0055d26ae 7580 python optional blist_1.3.6-9.debian.tar.xz 2b036a141b6c334fe03098e100af04c5 6389 python optional blist_1.3.6-9_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY3Pg/BQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2BcZAP47U6IXQds83nox4wl1SBr1hQztvo4e txeAHY5EYPMetgEApRsh+iR53b5gZAiuK56HVZFjNjg8vaO4Rae4KOG6YQ8= =WdLj -END PGP SIGNATURE End Message ---
Bug#1024161: src:billiard: please add a versioned Breaks on celery
Source: billiard Version: 4.0.2-3 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:billiard has been trying to migrate for 63 days [2]. Hence, I am filing this bug. Your package causes autopkgtest regression in celery, which has been fixed in unstable. However, to avoid issued during upgrades, please add a versioned Breaks on the version of celery in testing. Once that's added, the autopkgtest will stop blocking the migration, because it will be scheduled with the version of celery from unstable and celery and billiard can migrate together. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=billiard OpenPGP_signature Description: OpenPGP digital signature
Bug#1023905: marked as pending in blist
Control: tag -1 pending Hello, Bug #1023905 in blist 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/blist/-/commit/3b2ef89642e7daa02ea7c35d398d76a6e791409d Patch: Python 3.11 support (Closes: #1023905). (this message was generated automatically) -- Greetings https://bugs.debian.org/1023905
Processed: Bug#1023905 marked as pending in blist
Processing control commands: > tag -1 pending Bug #1023905 [src:blist] blist FTBFS with Python 3.11 as supported version Added tag(s) pending. -- 1023905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022176: marked as done (jpy: FTBFS with Python 3.11 as a supported version)
Your message dated Tue, 15 Nov 2022 18:49:37 + with message-id and subject line Bug#1022176: fixed in jpy 0.13.0-1 has caused the Debian Bug report #1022176, regarding jpy: FTBFS with Python 3.11 as a 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.) -- 1022176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpy Version: 0.9.0-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.11 Hi Maintainer jpy will FTBFS once Python 3.11 is added as a supported version. I've copied what I hope is the relevant part of the log below. You can verify this by installing python3.11 from testing or unstable and adding the following line to debian/rules: export DEBPYTHON3_SUPPORTED=3.10,3.11 Regards Graham x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -> src/main/c/jpy_jobj.c: In function ‘JType_InitSlots’: src/main/c/jpy_jobj.c:684:22: error: lvalue required as left operand of assignment 684 | Py_TYPE(typeObj) = NULL; | ^ src/main/c/jpy_jobj.c:685:22: error: lvalue required as left operand of assignment 685 | Py_SIZE(typeObj) = 0; | ^ 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: jpy Source-Version: 0.13.0-1 Done: Bo YU We believe that the bug you reported is fixed in the latest version of jpy, 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. Bo YU (supplier of updated jpy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 18:26:08 + Source: jpy Architecture: source Version: 0.13.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bo YU Closes: 1022176 Changes: jpy (0.13.0-1) unstable; urgency=medium . * Team upload. . [ Stefano Rivera ] * Update Homepage and URLs to new GitHub org, jpy-consortium. . [ Edward Betts ] * d/control: Remove .git from end of github URL in Homepage field. . [ Debian Janitor ] * Update standards version to 4.6.0, no changes needed. * Update standards version to 4.6.1, no changes needed. . [ Bo YU ] * New Upstream Release. Fix ftbfs on python3.11. Closes: #1022176 Checksums-Sha1: 3af4f8b56e9ff67a6933cd26017c74bccb010025 1396 jpy_0.13.0-1.dsc bc2de2dad2f0659cf0a7aebe968dedcc9f1d50f2 176996 jpy_0.13.0.orig.tar.xz 12c25454b967b106cfa93b6c97c3d0383fd1c145 5800 jpy_0.13.0-1.debian.tar.xz ae073ad1b06653012134549cad65f6339747702e 6385 jpy_0.13.0-1_source.buildinfo Checksums-Sha256: 073b888c6c5b1f8e0f33c13ea95d41a2ce5314c60188709c8951067834f6f799 1396 jpy_0.13.0-1.dsc ab4d0e8a762be96e7fa0d392c0eac6f2b637b5dc0252f1609ecc3ba99445cda1 176996 jpy_0.13.0.orig.tar.xz a69f6d13ada777b145e1b4e25f252f0d54ac490b10c4beac366c760eddb593d9 5800 jpy_0.13.0-1.debian.tar.xz b2ce33c1427d5c523c16b65c0506389dd89e0c96fc41643c793eafc4e0476520 6385 jpy_0.13.0-1_source.buildinfo Files: d821bb67f8a883debba9902c33dd47bd 1396 python optional jpy_0.13.0-1.dsc b0595e608b22c4ccb4d2047c13bb4fd9 176996 python optional jpy_0.13.0.orig.tar.xz 2eb91fbf11fce1fdf7ea21b16ce4aac4 5800 python optional jpy_0.13.0-1.debian.tar.xz 626a20e9f0d69df9ebcbf7cbe3b5af25 6385 python optional jpy_0.13.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY3PbIRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2PqOAQCJY8up7e8WYBlvR/kkROzMtbrVgwqP meVpdugYMVJncwD9GRTznncAcdW95h1187QEmCuMJHOlvZBZp2umKzPXiwM= =azkp -END PGP SIGNATURE End Message ---
Bug#1019996: lxml: FTBFS: ModuleNotFoundError: No module named 'lxml'
Hello, lxml maintainer. This bug comes from obsolete module usage in "python3-defaults" package. Please examine my merge request at: https://salsa.debian.org/cpython-team/python3-defaults/-/merge_requests/12 -- YOKOTA Hiroshi
Bug#1022025: Fwd: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
> 5.10.149-2 was no help with A10-7850K Radeon R7. Yes, My PC didn't boot with amdgpu yet, on linux-image-5.10.0-19-amd64. I'm using Radeon R7 Graphics too. I'm a man that 1st post in this thread. Sorry, I was so busy for a while. Attached /var/log/messages when didn't boot. Nov 15 05:30:19 muumatch-computer kernel: [0.00] Linux version 5.10.0-19-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-2 (2022-10-21) Nov 15 05:30:19 muumatch-computer kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 root=UUID=ed31f180-e855-42c2-ba9c-36e3a1b7cb9d ro quiet radeon.si_support=0 amdgpu.si_support=1 Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-provided physical RAM map: Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x0010-0x9d236fff] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9d237000-0x9d266fff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9d267000-0x9d276fff] ACPI data Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9d277000-0x9d7b3fff] ACPI NVS Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9d7b4000-0x9e3aefff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9e3af000-0x9e3a] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9e3b-0x9e5b5fff] ACPI NVS Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9e5b6000-0x9e9f2fff] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9e9f3000-0x9eff3fff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x9eff4000-0x9eff] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xfeb8-0xfec01fff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0xff00-0x] reserved Nov 15 05:30:19 muumatch-computer kernel: [0.00] BIOS-e820: [mem 0x0001-0x00021eff] usable Nov 15 05:30:19 muumatch-computer kernel: [0.00] NX (Execute Disable) protection: active Nov 15 05:30:19 muumatch-computer kernel: [0.00] SMBIOS 2.7 present. Nov 15 05:30:19 muumatch-computer kernel: [0.00] DMI: System manufacturer System Product Name/A88XM-A, BIOS 3001 03/09/2016 Nov 15 05:30:19 muumatch-computer kernel: [0.00] tsc: Fast TSC calibration failed Nov 15 05:30:19 muumatch-computer kernel: [0.00] last_pfn = 0x21f000 max_arch_pfn = 0x4 Nov 15 05:30:19 muumatch-computer kernel: [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Nov 15 05:30:19 muumatch-computer kernel: [0.00] last_pfn = 0x9f000 max_arch_pfn = 0x4 Nov 15 05:30:19 muumatch-computer kernel: [0.00] found SMP MP-table at [mem 0x000fd720-0x000fd72f] Nov 15 05:30:19 muumatch-computer kernel: [0.00] Using GB pages for direct mapping Nov 15 05:30:19 muumatch-computer kernel: [0.00] RAMDISK: [mem 0x305c9000-0x342dbfff] Nov 15 05:30:19 muumatch-computer kernel: [0.00] ACPI: Early table checksum verification
Bug#1024157: libreoffice/experimental FTBFS with dragonbox 1.1.3
Hi, Am 15.11.22 um 19:09 schrieb Adrian Bunk: ... checking which dragonbox to use... external checking for dragonbox/dragonbox.h... no configure: error: dragonbox/dragonbox.h not found. install dragonbox Error running configure at ./autogen.sh line 322. make: *** [debian/rules:2149: debian/stampdir/build-arch] Error 1 Yes, I know, since rc2 is supposed to be there this week I didn't do an upload just for this in experimental as I did for sid and 1:7.4.2-4. Regards, Rene
Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]
Hi all! программист некто (in CC) reported this bug a few weeks back in Debian. Since I applied the bundle of filesystem bounds-checking fixes a few months back, he can't run grub-install. He's done the work to determine that the patch that breaks things for him is 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end of nat journal entries The full thread of our discussion is at https://bugs.debian.org/1021846 I don't have any knowledge of f2fs to go any further here. Help please! :-) - Forwarded message from программист некто - From: программист некто To: sub...@bugs.debian.org Date: Sat, 15 Oct 2022 23:54:36 +0300 Subject: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem Message-Id: <3168731665867...@wf4nrjvtssjecb53.iva.yp-c.yandex.net> Package: grub-pc Version: 2.06-3~deb11u1 Severity: critical Hello. Since version 2.06-3, grub-install is broken: it fails with "error: unknown filesystem". I test command /usr/sbin/grub-install -v /dev/sda in some versions. Results in mail attachments. Versions older than 2.06-3 works without error (2.06-2 and lower). Tested versions: 2.04-20, 2.06-1, 2.06-2, 2.06-3~deb10u1, 2.06-3~deb11u1, 2.06-4. Disk partitions: # fdisk --list-details Disk /dev/sda: 29,82 GiB, 32017047552 bytes, 62533296 sectors Disk model: TS32GSSD370S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc7177f7e Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs /dev/sda1 2048 22763519 22761472 83 Linux 4/4/1 1023/254/2 /dev/sda2 * 25866240 62531583 36665344 7 HPFS/ 1023/254/2 1023/254/2 80 $ disktype /dev/sda1 --- /dev/sda1 Block device, size 10.85 GiB (11653873664 bytes) F2FS file system (version 1.14) $ disktype /dev/sda2 --- /dev/sda2 Block device, size 17.48 GiB (18772656128 bytes) NTFS file system Volume size 17.48 GiB (18772652032 bytes, 36665336 sectors) - End forwarded message - -- Steve McIntyre, Cambridge, UK.st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty
Processed: libreoffice/experimental FTBFS with dragonbox 1.1.3
Processing control commands: > close -1 1:7.4.2-4 Bug #1024157 [src:libreoffice] libreoffice/experimental FTBFS with dragonbox 1.1.3 Marked as fixed in versions libreoffice/1:7.4.2-4. Bug #1024157 [src:libreoffice] libreoffice/experimental FTBFS with dragonbox 1.1.3 Marked Bug as done -- 1024157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024157: libreoffice/experimental FTBFS with dragonbox 1.1.3
Source: libreoffice Version: 1:7.4.3~rc1-2 Severity: serious Tags: ftbfs Control: close -1 1:7.4.2-4 https://buildd.debian.org/status/fetch.php?pkg=libreoffice=ppc64el=1%3A7.4.3%7Erc1-2=1668227063=0 ... checking which dragonbox to use... external checking for dragonbox/dragonbox.h... no configure: error: dragonbox/dragonbox.h not found. install dragonbox Error running configure at ./autogen.sh line 322. make: *** [debian/rules:2149: debian/stampdir/build-arch] Error 1
Processed: tagging 1024102, found 1021846 in 2.06-3, found 1021273 in 0.3.1+dfsg-1, tagging 1024154 ...
Processing commands for cont...@bugs.debian.org:
> tags 1024102 + sid bookworm
Bug #1024102 [src:polyphone] polyphone: QCustomPlot transition
Added tag(s) bookworm and sid.
> found 1021846 2.06-3
Bug #1021846 [grub-pc] grub-install is broken since 2.06-3: error: unknown
filesystem
Marked as found in versions grub2/2.06-3.
> found 1021273 0.3.1+dfsg-1
Bug #1021273 [src:nomad] nomad: CVE-2021-37218 CVE-2021-43415 CVE-2022-24683
CVE-2022-24684 CVE-2022-24685 CVE-2022-24686
Marked as found in versions nomad/0.3.1+dfsg-1.
> tags 1024154 + upstream
Bug #1024154 [src:llvm-toolchain-14] llvm-toolchain-14: FTBFS: testsuite hangs
on i386, x32
Added tag(s) upstream.
> forwarded 1024154 https://github.com/llvm/llvm-project/issues/58357
Bug #1024154 [src:llvm-toolchain-14] llvm-toolchain-14: FTBFS: testsuite hangs
on i386, x32
Set Bug forwarded-to-address to
'https://github.com/llvm/llvm-project/issues/58357'.
> tags 898109 =
Bug #898109 {Done: Debian FTP Masters }
[src:openbsc] package fails to build with -O3
Removed tag(s) sid, bookworm, bullseye, and buster.
> reassign 980957 src:binutils 2.35.1-2
Bug #980957 {Done: Matthias Klose } [src:llvm-toolchain-11]
llvm-toolchain-11 autopkgtest segfaults on armhf
Bug reassigned from package 'src:llvm-toolchain-11' to 'src:binutils'.
No longer marked as found in versions llvm-toolchain-11/1:11.0.0-2.
No longer marked as fixed in versions 2.39-6.
Bug #980957 {Done: Matthias Klose } [src:binutils]
llvm-toolchain-11 autopkgtest segfaults on armhf
Marked as found in versions binutils/2.35.1-2.
> affects 980957 = src:llvm-toolchain-11
Bug #980957 {Done: Matthias Klose } [src:binutils]
llvm-toolchain-11 autopkgtest segfaults on armhf
Removed indication that 980957 affects src:binutils
Added indication that 980957 affects src:llvm-toolchain-11
> fixed 980957 2.39-6
Bug #980957 {Done: Matthias Klose } [src:binutils]
llvm-toolchain-11 autopkgtest segfaults on armhf
Marked as fixed in versions binutils/2.39-6.
> fixed 980957 2.38-1
Bug #980957 {Done: Matthias Klose } [src:binutils]
llvm-toolchain-11 autopkgtest segfaults on armhf
Marked as fixed in versions binutils/2.38-1.
> tags 1023986 + sid bookworm
Bug #1023986 [python3-parso] parso: too old to parse Python 3.11
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1021273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021273
1021846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846
1023986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023986
1024102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024102
1024154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024154
898109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898109
980957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1020739: autopkgtest regression with flask 2.2.2
Processing control commands: > severity -1 serious Bug #1020739 [src:flask-appbuilder] autopkgtest regression with flask 2.2.2 Severity set to 'serious' from 'important' -- 1020739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1020823: 0.0~git20170823.95fe63b+ds-2: autopkgtest regression with flask 2.2.2
Processing control commands: > severity -1 serious Bug #1020823 [src:searx-admin] 0.0~git20170823.95fe63b+ds-2: autopkgtest regression with flask 2.2.2 Severity set to 'serious' from 'important' -- 1020823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1024060: emacs: FTBFS for architecture all: test-undo-region fails / unexpected lisp/simple-tests.log
Processing control commands: > severity -1 serious Bug #1024060 [src:emacs] emacs: FTBFS for architecture all: test-undo-region fails / unexpected lisp/simple-tests.log Severity set to 'serious' from 'important' -- 1024060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024154: llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32
Le 15/11/2022 à 17:55, Andreas Beckmann a écrit : Source: llvm-toolchain-14 Version: 1:14.0.6-8 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, llvm-toolchain-14 recently started to fail to build on i386 and x32: the build gets killed after 150 minutes of inactivity while running the testsuite. This does not seem to be a flaky test, but happenes every time. https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-14=i386 What's interesting is that the buildds report nearly twice as much disk usage (8.69 GB) for the failed builds than for previous succeeding builds (4.44 GB). Fun. i didn't know it was failing with -14 too. I opened this bug a month ago https://github.com/llvm/llvm-project/issues/58357 S
Bug#1024155: libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)
Package: libngs-c++-dev Version: 3.0.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libngs-c++-dev_3.0.0+dfsg-1_amd64.deb ... Unpacking libngs-c++-dev:amd64 (3.0.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/include/ngs/Alignment.hpp', which is also in package libngs-sdk-dev:amd64 2.11.2-4 Errors were encountered while processing: /var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb Preparing to unpack .../libngs-c++-dev_3.0.0+dfsg-1_amd64.deb ... Unpacking libngs-c++-dev:amd64 (3.0.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libncbi-ngs-c++.a', which is also in package libncbi-vdb-dev:amd64 2.11.2+dfsg-6 Errors were encountered while processing: /var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb cheers, Andreas libncbi-vdb-dev=2.11.2+dfsg-6_libngs-c++-dev=3.0.0+dfsg-1.log.gz Description: application/gzip
Bug#1024154: llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32
Source: llvm-toolchain-14 Version: 1:14.0.6-8 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, llvm-toolchain-14 recently started to fail to build on i386 and x32: the build gets killed after 150 minutes of inactivity while running the testsuite. This does not seem to be a flaky test, but happenes every time. https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-14=i386 What's interesting is that the buildds report nearly twice as much disk usage (8.69 GB) for the failed builds than for previous succeeding builds (4.44 GB). Andreas
Bug#1017938: marked as done (RM: python-pmw -- RoQA, unmaintained, RC-buggy)
Your message dated Tue, 15 Nov 2022 17:20:47 +0100 with message-id <1079df55-0e19-4f9d-248f-73f37bd17...@debian.org> and subject line Re: RM: python-pmw -- RoQA, unmaintained, RC-buggy has caused the Debian Bug report #1017938, regarding RM: python-pmw -- RoQA, unmaintained, RC-buggy 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.) -- 1017938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pmw Version: 1.3.2-6 Severity: serious User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, This package is de-facto unmaintained as simce 2011. Appearantly, there are a newer upstream versions than that in Debian, but they have never been pacakaged. It has no reverse dependencies in Debian. It is currently RC buggy with those bugs: #886617 [S|U|♙♔] [src:python-pmw] python-pmw: Please package version 2.1 and include Python 3 support #938036 [S|U|♙♔] [src:python-pmw] python-pmw: Python2 removal in sid/bullseye #966783 [S|U|♙♔] [src:python-pmw] python-pmw: Unversioned Python removal in sid/bullseye I therefore propose to RM the package. There is an ITS (CC'ed), but that ITS seems to have stalled. If you disagree, just close this bug, but please show the package some love. If you agree, reassign the bug to ftp.debian.org If there is no answer, I will reassing the bug in exactly 3 months to ftp.debian.org to make the RM happen. -- tobi --- End Message --- --- Begin Message --- I am going to complete the ITP process that was opened by Boyuan.--- End Message ---
Bug#1021665: marked as done (lnav: FTBFS on mipsel: cc1plus: out of memory allocating 189688476 bytes after a total of 28327936 bytes)
Your message dated Tue, 15 Nov 2022 16:07:28 + with message-id and subject line Bug#1021665: fixed in lnav 0.11.1-1~exp2 has caused the Debian Bug report #1021665, regarding lnav: FTBFS on mipsel: cc1plus: out of memory allocating 189688476 bytes after a total of 28327936 bytes 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.) -- 1021665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lnav Version: 0.11.1~rc1-1~exp1 Severity: serious Tags: help Justification: FTBFS X-Debbugs-Cc: car...@debian.org,debian-m...@lists.debian.org Hi lnav/0.11.1~rc1-1~exp1 in experimental with the new upstream version 0.11.1~rc1 FTBFS on mipsel: https://buildd.debian.org/status/package.php?p=lnav=experimental Help from mips* porters would be very welcome! Regards, Salvatore --- End Message --- --- Begin Message --- Source: lnav Source-Version: 0.11.1-1~exp2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of lnav, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated lnav package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 16:39:16 +0100 Source: lnav Architecture: source Version: 0.11.1-1~exp2 Distribution: experimental Urgency: medium Maintainer: Salvatore Bonaccorso Changed-By: Salvatore Bonaccorso Closes: 1021665 Changes: lnav (0.11.1-1~exp2) experimental; urgency=medium . * Produce no debug information for mipsel builds (Closes: #1021665) Checksums-Sha1: 16f601aae05c018733b7b10953a20dab03470d7f 2127 lnav_0.11.1-1~exp2.dsc 761cead23ceb91150862a1ddf0c3aa7249071d43 9312 lnav_0.11.1-1~exp2.debian.tar.xz Checksums-Sha256: 843c0b0f3f4beaaa6d1c4aba957bbab41046a4f5444cd33108464ab13a109c4e 2127 lnav_0.11.1-1~exp2.dsc bd76541bf6b6ca3408a4163f568edf6c9a1c9acdf16ad69fdc9365a6079b2bf3 9312 lnav_0.11.1-1~exp2.debian.tar.xz Files: b8c07bf48dc198df02ccdda240bcb9bd 2127 admin optional lnav_0.11.1-1~exp2.dsc 1237cb25ea457f467759d1df24b6572f 9312 admin optional lnav_0.11.1-1~exp2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNztoZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EvP4P/R7LQtYC0qSFb7fGX5lgxRtllyWtnza1 WAGfUrSB/p0CMr6R1pFky6YkJ61h5jjuad4yYu11pgjf4C6nfi6098xxu93wwaKT ekjOrHQgDqtYUv6Jx96xfHMtUhe8g8HRfz81LdsY9Y2ihYzgruNw+OhIrcsuEWCn SOZDZfAkFqFiJ4NhxKlhPUT3mkaP+vmOu7gB4gSH9EHyXqzlc85wZU+ioCpmCNHy R2LanQT9ZuBRp3YT81WUyA5fsbHcakjEP0C5B0q22gCxHo8ec/MaLy/+QmD9k+uR 8ScBdURsCmbAi6V0RhEsEifNxkGSenCZ/Cs4Ctq973cHdMHkJCbqK/LczLrJA1Uk mokRPMpqDtGsRN03tVQq2a9cBDBCESVUwSsPnDql9C3dtOfTSrqal2YWWWkmDT8U 0DbYWGGJhZ2pC13h4XXZK2W5Km0dZuWZx59B5ZnRQ/Nu3QWfcTDoD4luLhMrftY/ aHYN5eEl2O7SlYldIr1+iOMC3GUg5+sgz1WI7isAH1rVZnL+z181VzVtiCA7B+p9 R4ea9RBDpJ44NTB8CL/1oLAo80NikhUe3xzKxkLYiczN+pGx6spxDtyBuYXCWk8N LLBhCrbNl803E4kPy/CwF78jdVHgxS9BCu+uFTHJCUFjyQSFTMI4u3WQPwZC05Jg HDk8br8GRVp5 =Teuv -END PGP SIGNATURE End Message ---
Processed: python3-coverage: Python 3.11 support incomplete due to ignored error during build
Processing control commands: > block 1021984 by -1 Bug #1021984 [release.debian.org] (some kind of) transition: add python3.11 as a supported python3 version 1021984 was blocked by: 1023965 1021871 1023986 1023039 1023972 1021984 was not blocking any bugs. Added blocking bug(s) of 1021984: 1024148 -- 1021984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021984 1024148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024148: python3-coverage: Python 3.11 support incomplete due to ignored error during build
Package: python3-coverage
Version: 6.2+dfsg1-2
Severity: serious
Control: block 1021984 by -1
$ python3.11-coverage
Traceback (most recent call last):
File "/usr/bin/python3.11-coverage", line 33, in
sys.exit(load_entry_point('coverage==6.2', 'console_scripts',
'python3.11-coverage')())
^^^
File "/usr/bin/python3.11-coverage", line 25, in importlib_load_entry_point
return next(matches).load()
^
StopIteration
$
Caused by:
https://buildd.debian.org/status/fetch.php?pkg=python-coverage=amd64=6.2%2Bdfsg1-2%2Bb2=1668240618=0
...
coverage/ctracer/tracer.c: In function ‘CTracer_handle_call’:
coverage/ctracer/util.h:20:42: error: ‘struct _PyInterpreterFrame’ has no
member named ‘f_lasti’
20 | #define MyFrame_lasti(f)((f)->f_frame->f_lasti * 2)
| ^~
coverage/ctracer/tracer.c:526:9: note: in expansion of macro ‘MyFrame_lasti’
526 | if (MyFrame_lasti(frame) < 0) {
| ^
coverage/ctracer/tracer.c: In function ‘CTracer_handle_return’:
coverage/ctracer/tracer.c:692:56: error: ‘PyCodeObject’ has no member named
‘co_code’; did you mean ‘_co_code’?
692 | PyObject * pCode = MyFrame_GetCode(frame)->co_code;
|^~~
|_co_code
coverage/ctracer/util.h:20:42: error: ‘struct _PyInterpreterFrame’ has no
member named ‘f_lasti’
20 | #define MyFrame_lasti(f)((f)->f_frame->f_lasti * 2)
| ^~
coverage/ctracer/tracer.c:693:25: note: in expansion of macro ‘MyFrame_lasti’
693 | int lasti = MyFrame_lasti(frame);
| ^
**
** Couldn't install with extension module, trying without it...
** BuildFailed: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
**
...
Bug#1023671: marked as done (afl++ silently drops gcc_plugin support when gcc-X-plugin-dev build dependency not on the default gcc)
Your message dated Tue, 15 Nov 2022 14:49:50 + with message-id and subject line Bug#1023671: fixed in aflplusplus 4.02c-2 has caused the Debian Bug report #1023671, regarding afl++ silently drops gcc_plugin support when gcc-X-plugin-dev build dependency not on the default gcc 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.) -- 1023671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: afl++ Version: 4.02c-1 Severity: serious Control: block 1023666 by -1 https://buildd.debian.org/status/fetch.php?pkg=aflplusplus=amd64=4.02c-1=1662644587=0 ... [*] Checking for gcc plugin development header files... [-] Oops, can't find gcc header files. Be sure to install 'gcc-X-plugin-dev'. make[3]: *** [GNUmakefile.gcc_plugin:125: test_deps] Error 1 ... This should be an error, which would then result in someone updating the build dependency when the default gcc changes. --- End Message --- --- Begin Message --- Source: aflplusplus Source-Version: 4.02c-2 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of aflplusplus, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sophie Brun (supplier of updated aflplusplus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 14:58:34 +0100 Source: aflplusplus Architecture: source Version: 4.02c-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sophie Brun Closes: 1023671 Changes: aflplusplus (4.02c-2) unstable; urgency=medium . * Do not ignore gcc plugin failures (Closes: #1023671) * Update build-dep to gcc-12-plugin-dev Checksums-Sha1: 4c6661d6a7aea66496ef1bd54ad66d195799ccf0 2451 aflplusplus_4.02c-2.dsc 58af8a3019448eec71e01d4d68b1dfff4002211d 9580 aflplusplus_4.02c-2.debian.tar.xz 83c573d53f6eda311dfcbc37a50eff2ca92e16ee 8811 aflplusplus_4.02c-2_source.buildinfo Checksums-Sha256: 78e4db33b4d8b2fa535cce3f13ef788b7092ef4b243bdea85b38e241663c4849 2451 aflplusplus_4.02c-2.dsc 362da1b7c8debebb7d4d02e34f9d2f3e163c1d202ebbfc32883b21dc6ca0265d 9580 aflplusplus_4.02c-2.debian.tar.xz 23d8fedf811f4287cb10fa2634587f095d088557073a0b50974f7a7546a141b2 8811 aflplusplus_4.02c-2_source.buildinfo Files: 1e0347626bbcbe4c5148863cb16302f3 2451 devel optional aflplusplus_4.02c-2.dsc 766ea6fb993118c07bd658a97b616147 9580 devel optional aflplusplus_4.02c-2.debian.tar.xz 384a461119682b138ab7861525e0b409 8811 devel optional aflplusplus_4.02c-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Sophie Brun iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmNznwgACgkQV5J4OyBv 7jCa9A/9H3K/MlZzqWLXiWe88fmdrIaPooQfBSd3rBG5gI+F3HIsAV9H4vL+gt15 6jnPHQq8CD+Bv7IhLPBKUaPPXZIKBl1e1L7d4D/Jd2TDupQaOlo8+N3eueSK8yOx dfSjOTphqSqrsGfEiBnMqDfQ4siDzXYa7RuPYoF+DgwxMUmHpG9uFQPah/IrHNWe afw3yaewAa4KxpwN8mnpkyt/HweXdj5wD1Qf/LvgSc2+JKxItpnwOaSsc46YFnfE VIDW61Lu5DYVSxRdWkly4xwKPibivIgis+VE3LIz/PwMMkLzuXvYD6PnzziUcrah xquc9KMHMRNVAqrIwgy3aASWpugWOFNEv1mXRZ3Uh4We44RjZf7j9SC6HqAlsT3b 6bk3OX5fou2wi+UXRZTemsu+ZScVWWUkm6+X7ebGKxzkIeWcTX1Pwe3P7K/WTVhN M4HUPWtQVCidqn6DeM5CDcrnftf2IsBaYgMLo5ug0n+6f3aFIzB+YpFX1NM3K6+r ztYetZ4QTVJGHa6GjKvsXYZ1yXfoHrwGPosEKpNHSVR6KRdknZf+vZKx6J0GkZ0u u5U/w+m6EPNOXU5GCFx2wZH6xfKqfjV+6GUusMOU4uK97r2X7K7AjfDr/tAgChXu DhbTFS+IBUOMkylK2YxqcoskG3gppbF0k37hshMan2yibgVB7c4= =2umu -END PGP SIGNATURE End Message ---
Bug#1021665: marked as pending in lnav
Control: tag -1 pending Hello, Bug #1021665 in lnav 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/carnil/lnav/-/commit/801c99ac3b8a912c78cf6181c4f407d79db28619 Produce no debug information for mipsel builds Closes: #1021665 (this message was generated automatically) -- Greetings https://bugs.debian.org/1021665
Processed: Bug#1021665 marked as pending in lnav
Processing control commands: > tag -1 pending Bug #1021665 [src:lnav] lnav: FTBFS on mipsel: cc1plus: out of memory allocating 189688476 bytes after a total of 28327936 bytes Added tag(s) pending. -- 1021665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023548: marked as done (pyopengl: migrate to libglut3.12)
Your message dated Tue, 15 Nov 2022 13:20:36 + with message-id and subject line Bug#1023548: fixed in pyopengl 3.1.6+dfsg-1 has caused the Debian Bug report #1023548, regarding pyopengl: migrate to libglut3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1023548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyopengl Version: 3.1.5+dfsg-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 1023419 by -1 pyopengl hardcodes the dependency on freeglut3. As the transition from freeglut3 to libglut3.12 is currently ongoing, pyopengl needs to be fixed. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: pyopengl Source-Version: 3.1.6+dfsg-1 Done: Picca Frédéric-Emmanuel We believe that the bug you reported is fixed in the latest version of pyopengl, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated pyopengl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 13:51:09 +0100 Source: pyopengl Architecture: source Version: 3.1.6+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Picca Frédéric-Emmanuel Closes: 1023548 Changes: pyopengl (3.1.6+dfsg-1) unstable; urgency=medium . * New upstream version 3.1.6+dfsg * d/rules: Activated the unittest * Use secure URI in Homepage field. * Bug fix: "migrate to libglut3.12", thanks to Sebastian Ramacher (Closes: #1023548). * Added autopkgtests Checksums-Sha1: 2efa808f16ebedf8f5488ac1037ab7809ed7f6f5 2447 pyopengl_3.1.6+dfsg-1.dsc c01e5a38a212ecab9aa432c2d936e854f0374c0e 636756 pyopengl_3.1.6+dfsg.orig.tar.xz 9106b6d617a975592d71819ba90b4a72af8b5bd0 10392 pyopengl_3.1.6+dfsg-1.debian.tar.xz Checksums-Sha256: 2563cb1b601db9dfb1787e936e19c372b653c99ff0fbb1b81200cae318757e28 2447 pyopengl_3.1.6+dfsg-1.dsc b554bf6b4c066b6c82243f14fcd5393fb8812bdacf723e4840efe797094996b5 636756 pyopengl_3.1.6+dfsg.orig.tar.xz 54b65ede89536d25c741b585beb1ba924078a66b35675fbae350c5db931b676d 10392 pyopengl_3.1.6+dfsg-1.debian.tar.xz Files: b93ebeaaf0865a91f43289ddfffcbbc4 2447 python optional pyopengl_3.1.6+dfsg-1.dsc 8c294dd3edb4dcb4245ea5c28f3f6182 636756 python optional pyopengl_3.1.6+dfsg.orig.tar.xz 0fd0840e27bc9b299e14071e887e5cde 10392 python optional pyopengl_3.1.6+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmNzi8URHHBpY2NhQGRl Ymlhbi5vcmcACgkQW/VOXhK5ALulNg/9E9satXyjMrmgQc43p1N4FZ16ZKQNIvBl +HOovTeqbQsMqBiNdnWxHlpKx5rS0b415ty+179N1c0hscIgH5tbY2u2MdwdVI/x Kmi53LF9isZIH+h86PkFwjV+lh4Y0DjjU1/piSmHRappbD1r+vYVFCSGa0dx/htX AkCjydyGkXfykrPb4FpzRcy7zHXyhPxFtUxEY+DnTNOGPxXpCbLC7Qv2eIa+1ePs tfVnRUO3BUxlXm0Qft1dGU3dHe5IzgOVbExuFHptcl3jXEa7BEpRodWRa+iCASqG buuQmOmVH1/WSVCbvfKbKfFJ1gjH5XkkUA5jNqR+5GR3ciHNvMlI/4Gm63DC24Nf xzgJTmbGKkYZ9/0vNq4P2hly2AUXwv43o+WxeoYIqFtQIzXTnOrnNJz61PToZXr8 2s+733ZFkO8EQcfcbVg8mUJNKvvSEo75ABr72Z3sZqsJ8tbL7eGSWRcvO0Y6Fp2f /qahQmV7YpWR8Qp3of6JmYkpem9+6BJcMCeRKTdSULEir3QrfIEMhsTx05YDBpPV l0wgLClSA54wHIP9KbP3eryy86eC1vJaUFuK3KWwj7GVwR4jfGNWXcnwtXyrlWBc yvYYLacl7C4VJKi7cQDnWFaSdWM1a0eYGsCUriBR9oFR5hyolsVVzbbhYVql/oEp 0UsgHoxN+Mg= =OQHn -END PGP SIGNATURE End Message ---
Bug#1023961: marked as done (s2geometry doesn't build for all supported python versions, and ftbfs on ppc64el/s390x)
Your message dated Tue, 15 Nov 2022 11:06:33 + with message-id and subject line Bug#1023961: fixed in s2geometry 0.10.0-3 has caused the Debian Bug report #1023961, regarding s2geometry doesn't build for all supported python versions, and ftbfs on ppc64el/s390x 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.) -- 1023961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:s2geometry Version: 0.10.0-2 Severity: serious Tags: sid bookworm ftbfs User: debian-pyt...@lists.debian.org Usertag: python3.11 two issues: - the package build depends on python3-all-dev, but only builds for the default python version. - the package ftbfs on ppc64el and s390x See https://buildd.debian.org/status/package.php?p=s2geometry --- End Message --- --- Begin Message --- Source: s2geometry Source-Version: 0.10.0-3 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of s2geometry, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated s2geometry package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 11:35:56 +0100 Source: s2geometry Architecture: source Version: 0.10.0-3 Distribution: unstable Urgency: medium Maintainer: DebianOnMobile Team Changed-By: Jochen Sprickerhof Closes: 1023961 Changes: s2geometry (0.10.0-3) unstable; urgency=medium . * Team upload. . [ Sebastian Spaeth ] * d/control: Fix typo in Maintainer name * libs2-dev depends upon libabsl-dev (>= 0~20220623) * d/control: -dev package requires libssl-dev * Fix FTBS for s390x . [ Jochen Sprickerhof ] * Fix build on ppc64el * Fix compilation for multiple Python versions (Closes: #1023961) * Add MA hint from the MA hinter Checksums-Sha1: 91163085f6ea8284302d3a37cc1fe2b13e135e7e 2513 s2geometry_0.10.0-3.dsc da705ba12a97712617c8bd0ff59faf920b6b5a32 5084 s2geometry_0.10.0-3.debian.tar.xz 7c1cdc7ed6d4bdbf6f039b47c0f4ff5986aed16d 7991 s2geometry_0.10.0-3_source.buildinfo Checksums-Sha256: eb14a3e7e29b8514678eca3fc7156a3c9b4cb6ceff040899622ba06fc53f66ee 2513 s2geometry_0.10.0-3.dsc 48399aee0413696aa3208dbc5bad38f7aa57aec0ae64939f8b7b80a473b201e2 5084 s2geometry_0.10.0-3.debian.tar.xz 5f3096d7796d9abe19617dbca67aba9fb9d235d8059147382f8599795809b3bd 7991 s2geometry_0.10.0-3_source.buildinfo Files: 825e77d2553ce31c7351c80fbff43cf3 2513 libs optional s2geometry_0.10.0-3.dsc d1d6c092197a8840141267d6b843f6f3 5084 libs optional s2geometry_0.10.0-3.debian.tar.xz 50b98decabe005feb499a77233ee5eba 7991 libs optional s2geometry_0.10.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmNzb1AACgkQW//cwljm lDPxPBAAobgKl9YAnfUexHJ+VtMid9aau2PkbYwSEY7SQIAmkMrIIrmiTlAebPqo MfYXLmIAZDKGzSgaQ/MxkzX7fbKEUhcTLIx7UZCJQtid8dOkUprY4NzLFLe77r4s 7YZm5eWZPwK2wObhxd1FUptLYXYe8zo0DZ+KE98LbgE2OuNfkaSrnEnqBrlV1srA zP6j0H4n0R5mqOqsivtyS01Ie25nIa8006vveIVZoyLKcVBke8SJ3M7VIdjIVVnl o3vDGVy/dQ/IhyxSrkFPbG8/ZnnF6HRi685YJGRuTPC6UjlEDodeO1QsRC94PAHE Mn7I1nL8v3rUAVKoM8kTV7dFUR7y3Om+LJXwkP1wjrVxnmWf1qvDItNAkQtQstcC 7+iz/hUDdbLVPKCWKnn9MOg7QmqarfOffUke0IMrc3YGb45QgFpqR52Q9HSJ/1fD PBxNUpfPl2uyrZgKF2t5YL4StGjylNE2ljAWXb5dFD0gBelFw1W6wXFgyCn3hOv8 E4QJ8J6Yn4LDy2e0i99cqPJlI2VhVq/8VVw7lRPlpi4VtLdYpFwNhqGGzNsaH9X1 /Uo3IMX64uRnnGTtSqM7KU9FApl8IDFa9huQDPDFqSq8I0GSYBg2kosnJZClamkr ko479sgEVK1LxEtBnK2PQZdXWtFsYHPimnUkOpvGwIemrkbl3kQ= =RX8S -END PGP SIGNATURE End Message ---
Bug#1022480: marked as done (python-peachpy: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)
Your message dated Tue, 15 Nov 2022 10:20:12 +
with message-id
and subject line Bug#1022480: fixed in python-peachpy
0.0~git20211013.257881e-1.1
has caused the Debian Bug report #1022480,
regarding python-peachpy: FTBFS: distutils.errors.DistutilsClassError: command
class must subclass Command
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.)
--
1022480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-peachpy
Version: 0.0~git20211013.257881e-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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,sphinxdoc --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.10 setup.py config
> /<>/setup.py:3: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> import distutils.log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<>/setup.py:3: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> import distutils.log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
> File "/<>/setup.py", line 50, in
> setup(
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
> setup
> return distutils.core.setup(**attrs)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
> 172, in setup
> ok = dist.parse_command_line()
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class '__main__.BuildGenerateInstructions'> must subclass Command
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:8: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-peachpy_0.0~git20211013.257881e-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
Bug#1024106: traceshark: QCustomPlot transition
Hi Filippo, On Mon, Nov 14, 2022 at 9:15 PM Filippo Rusconi wrote: > > Source: traceshark > Version: 0.9.12~beta-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) I think this should not have "Severity: serious" yet. The qcustomplot transition has not yet started. imho, It will start when Sebastian confirms and its uploaded to unstable and then these are serious severity. -- Regards Sudip
Bug#1024081: marked as done (extinction must build depend on python3-all-dev)
Your message dated Tue, 15 Nov 2022 09:36:05 + with message-id and subject line Bug#1024081: fixed in extinction 0.4.6-3 has caused the Debian Bug report #1024081, regarding extinction must build depend on python3-all-dev 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.) -- 1024081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: extinction Version: 0.4.6-2 Severity: serious Tags: ftbfs Control: affects -1 src:sncosmo Only building for the default python can make other packages FTBFS during a Python transition: https://buildd.debian.org/status/fetch.php?pkg=sncosmo=amd64=2.9.0-1%2Bb1=1668431912=0 ... I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest sncosmo ImportError while loading conftest '/<>/.pybuild/cpython3_3.11/build/sncosmo/conftest.py'. sncosmo/__init__.py:134: in from .models import * sncosmo/models.py:11: in import extinction E ModuleNotFoundError: No module named 'extinction' E: pybuild pybuild:379: test: plugin distutils failed with: exit code=4: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest sncosmo --- End Message --- --- Begin Message --- Source: extinction Source-Version: 0.4.6-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of extinction, 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. Ole Streicher (supplier of updated extinction package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 09:57:32 +0100 Source: extinction Architecture: source Version: 0.4.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1024081 Changes: extinction (0.4.6-3) unstable; urgency=medium . * Build-depend on python-all-dev (Closes: 1024081) Checksums-Sha1: d1f52cbfd49d663cdb75681f2ae196a68ad6e4ed 2041 extinction_0.4.6-3.dsc c4124d90639ebb5c01b35e355f174b9bca912059 2056 extinction_0.4.6-3.debian.tar.xz Checksums-Sha256: db5054dda3a51c38491b317762d959f9312c69292f4faaa5c2a963f9988d99a9 2041 extinction_0.4.6-3.dsc 755cd37d21665b4e14e06cd98d2a185235abc78510888f6c0ce3ec6854848717 2056 extinction_0.4.6-3.debian.tar.xz Files: bb98e31ece53be6b61e60b161d4d87e9 2041 python optional extinction_0.4.6-3.dsc 87c85ee976d08fc2158b5927f40b5995 2056 python optional extinction_0.4.6-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmNzVP0ACgkQcRWv0HcQ 3PeSnw//UHk33h2s6PZW+BEzFXVPzwqQUhGnEj0f8ltg65jWKZ97dtB9fGxp2jUH L/7OYsnJlGntyyRJ7h+F9LLKkKwP4ELnnH0Kgn2KagOUMgWfOWe6RrLx9x3ko/Jc A+nHuoe0XxiihKiwD8DcXPrx2atgwSskrvCS84yhyOAVxeurD1lZvmi47wDqojBf fOFNx1+jLTET7bybytNjLd4VrNXGSzZ+do096CYyjPfBFPPt98aLLCEgACJ0LBio 12Xrcro44CM2q8/SJ2EhNvMkObqQPGfMhlZBxLNi/f0shMKUr9OsV/V1hvHq+joA vlaBeozKMK2i3QDV9bkqKPcEuSmIYxpKbhQrpjo6qGA/s8rYfRLRdu0RxDh4Y861 SwSgWhcLSCEIGGOTGy+Xl4Gp1GhtCse44pe34JA+uERpHW39P7bjKspYABfoNHb8 jTxTr94TBA+clGiQomwjhpgE12Ipv32d1XFJRor4Ko5nmjgKkTXk9S/mTbVRuLWd Vbqi3LSGfV04FX5CvjVR+PzUSZtQVz/rz8arzzm5zEZiN+7ScxTQ0c3ycMrboRLe x4Pe4w8/lybKmC1VeLJBaQ4EBAG0mQHG4HbFguhL07nxP0asikgJ+VYo6tK3rc7Y AJLtbECcuhPQLYBNewtNvL91pUtipsGEqok759GEMFZ/tRLW6iQ= =DyKf -END PGP SIGNATURE End Message ---
